AT-GPIB/TNT on eCS1.2 (OS/2 kernel) anyone tried this?

I'm woking on upgrading the PC's on some manufacturing tools. The proprietary software i'm interfacing with is written for OS/2 Warp. I'm attempting to use eCS1.2 as my OS and am having trouble getting AT-GPIB/TNT installed. I'm using the atos2v22.zip driver from your archive and according to the tech support from eCS, the OS is based fully on the OS/2 kernel, and is compatible with programs written for it. IBTEST.exe -just starts its check, then hangs up. GPIBINST.exe -Shows the driver loaded at boot. I made sure the IRQ/DMA's and base I/O address are matching between the software and the jumpers. I did try other IRQ/DMA settings. I even tried different cards. Did not try different base I/O. If
you have any ideas, I'd love to hear them. Attached are some screenshots.
System:
PIII 1.3Ghz
VIA 82C694T/82C686B chipset
OS: eComStation 1.2
GPIB: AT-GPIB/TNT assy181830E-01
Attachments:
IBCONF.JPG ‏120 KB
GPIBINST.JPG ‏58 KB
IBTEST.JPG ‏53 KB

KMcCuen,
Are you communicating with these robot controllers through GPIB? If so then are you able to send valid 488 commands? Also which errors are you seeing specifically (are they generated by the driver or by the controllers themselves).
While it's not much the following Knowledge Base can be helpful in establishing basic communication through GPIB:
http://zone.ni.com/devzone/conceptd.nsf/webmain/1CB672F654DF474C8625681E00732401?opendocument
Let me know if that helps!
Craig H.
NI Applications Engineering

Similar Messages

W2K crashes with PCI-GPIB

I am using a PCI-GPIB card under W2K, with driver version 1.60. All diagnostics
indicate that the card is functioning correctly, and there are no hardware
conflicts. I am able to use WaveStar to communicate with the Tektronix 694C
scope. When using Excel/VBA macros to control an oscope, W2K crashes to
a blue screen, with the message:
Hardware Failure
Please Contact Hardware Vendor
A hard reset is required to re-start the system. There is no error logged
by W2K, and using NI Spy reveals no consistent macro command that is causing
the failure. I have followed all the suggestions in the Troubleshooter,
Knowledge Base, etc. I have tried a different PCI-GPIB card from an known-good
system. I have tried this card in a
different, identical system. Any other
suggestions would be greatly appreciated.
Thanks,
Cory Allen

I am using a Pentium III 733/Intel VC820 motherboard/256M RAM/Matrox Millenium
G400 that was built by our IT dept. In addition to the GPIB card, there
is an Intel PRO/100+ network card, an In-Target Probe (ITP) card, and a SoundBlaster
Live (which has since been removed, reducing the frequency of the crashes,
but not eliminating them.). I have tried a variety of PCI slot configurations.
Thanks,
Cory
"Eric Singer" wrote:
>What type of computer are you running? Please indicate the make and model.>>Thanks,>Eric
Singer>"Cory Allen" wrote in message>news:[email protected]..>>>>
I am using a PCI-GPIB card under W2K, with driver version 1.60. All>diagnostics>>
indicate that the card is functioning correctl
y, and there are no hardware>>
conflicts. I am able to use WaveStar to communicate with the Tektronix>694C>>
scope. When using Excel/VBA macros to control an oscope, W2K crashes to>>
a blue screen, with the message>>> Hardware Failure>>>> Please
Contact Hardware Vendor>>>> A hard reset is required to re-start the system.
There is no error logged>> by W2K, and using NI Spy reveals no consistent
macro command that is>causing>> the failure. I have followed all the suggestions
in the Troubleshooter,>> Knowledge Base, etc. I have tried a different PCI-GPIB
card from an>known-good>> system. I have tried this card in a different,
identical system. Any>other>> suggestions would be greatly appreciated.>>>>
Thanks,>> Cory Allen>>>>

NI GPIB driver support for linux 2.4

Is the NI linux GPIB driver compatible with the Linux 2.4 kernel? Does the NI linux GPIB driver provide a generic device interface (i.e. independent of LabVIEW)? I would like to access the driver using the POSIX interface (i.e. read/write/mmap etc.) via a standard device node (i.e. in '/dev'). We are looking to add a PCI-GPIB interface to our generic control and monitor system. The initial application will involve special purpose software interfacing with external test equipment (scope, power supply, etc.). The current platform is an Intel based industrial PC running Linux 2.4. This system will NOT be able to support data visualization via LabVIEW.

Unfortunately, the current BETA driver (0.6) released by NI does not support version 2.4.x of the Linux kernel. There are plans for support in the future but no timeline has been specified. I would suggest checking back with NI on occassion at http://www.ni.com/linux for the latest news and support of the Linux OS.
Ryan Mosley
National Instruments, Applications Engineer
http://www.ni.com/exchange

Blue Screen (STOP: 0x00000050) when using multiple Agilent34970A devices with a single GPIB

Hi,
I am using two test fixtures that contain two Agilent34970A Multimeters and two Sorensen Power Supplies (each test fixture is contaning one Multimeter and one Sorensen Power Supply) that are connected via GPIB cables to a single PCI-GPIB card. Below I have attached two VI's. GPIB_Communication_Experiment_1.vi (Test Fixture 1) and
GPIB_Communication_Experiment_2.vi (Test Fixture 2) are used to run self test on the
Agilent34970A multimeters. GPIB_Communication_Experiment_1.vi is talking to one of the Agilent Multimeters and one of the Sorensen Power Supplies (Address 9 for Agilent Multimeter and Address 2 for Sorensen Power Supply) whereas GPIB_Communication_Experiment_2.vi talks to the second Agilent Multimeter and its Sorensen Power Supply (Address 10 for the Multimeter and Address 3 for the Sorense Power Supply).
The Problem occurs when I try to run these two VI's simultaneously where it generates a "blue screen of death" with a Technical Information : STOP: 0x00000050 (0xF8AC00440, 0x00000000, 0x8041889, 0x00000000).
This Problem only occurs when trying to run the executables that were built from the attached VI's.
I have tried to use VISA CLEAR within the while loop as you can see in the VI however it did not improve things.
I have also uninstalled and re-installed the software for my PCI-GPIB card but that seemed not to work either.
At this point I am confused. If I try to run only one Test Fixture at a time I have no problem doing the Self Test on the Agilent Multimeter, yet every single time if I try to run the two test fixtures together I am gettig the blue screen.
Besides the two executable VI's I have also attached the regular VI's
I would really appreciate your help, thanks in advance for your time.
Attachments:
GPIB_Communication_Experiment_1.vi ‏23 KB
GPIB_Communication_Experiment_2.vi ‏23 KB

Hello aps7828:
If I read that correct, you only get the error when you run the executables and not the VIs. Can you take a look at your processor level while one .exe is running. I am wondering if that is the source of the problem.
Regards,
Roland A.
Applications Engineer
National Instruments
Check out VI Roadshow

GPIB-ENET driver 1.10 no longer works under Windows 2000 service pack 2

I have used my GPIB-ENET adapters with Windows 2000. However, since I installed service pack 2, the GPIB driver 1.10 no longer works. It seems to install correctly and puts the GPIB icon in the Control Panel. After a reboot, however, the icon is gone from the control panel ! It is even gone from the install/remove programs box. I have tried this on two PC's with the same result. This is really bad as my GPIB-ENET boxes are now useless. Can you help with this?

Thanks for the advice, but the 1.20 drivers cannot be downloaded. They must be purchased for $80 US. I have already paid many thousands of dollars for three GPIB-ENET adapters plus LabVIEW. This is really shabby. I know of no other company that charges for driver updates once you have bought the hardware. I should have bought the Tektronix adapters instead.

I have problems with pci-gpib card under windows me, What I need to know what to do in order to fix this problems?

Hi, I have installed a pci-gpib card in my computer, I have a problem with
installation, the message of troubleshooting wizard is as follow:
"One or more missing GPIB interfaces.
There are several reasons why you might encounter this problem:
Reason: Your GPIB interface is incorrectly installed.
Solution: Please verify that your GPIB interface is correctly installed
and rerun the NI-488.2 Troubleshooting Wizard.
Reason: You are using a non-Plug-and-Play interface (e.g., AT-GPIB/TNT,
GPIB-PCII/IIA, GPIB-ENET) and you did not use the Add New Hardware Wizard
to add the interface to your system properly.
Solution: Click th
e Add Hardware button and the Add GPIB Hardware wizard
will guide you through the process of adding GPIB hardware.
Reason: For the GPIB-USB and GPIB-1394, the host controller (USB or 1394)
must be working properly in order to use the GPIB interface.
Solution: Click on the System Details button for details about the USB and
1394 host controllers.
Reason: For the PCMCIA-GPIB and PCMCIA-GPIB+, the PCMCIA host controller
must be working properly in order to use the GPIB interface.
Solution: Use the Windows Device Manager to verify that your PCMCIA host
controller is functioning correctly. Start the control panel by selecting
"Start>>Settings>>Control Panel", open the System icon and select the
Device Manager page. If you select "View devices by type", you can look at
the PCMCIA socket properties to ensure it is correctly enabled."
And on system details the message is the next:
"USB Driver type: USB universal host controller"
"This version of windows does not su
pport IEEE 1394."
I am using Windows Me, so i want to know what i need to do to fix this
problems.
Best regards.

If you have a PCI-GPIB card, you needn't worry about the USB port or whether or not Windows ME supports 1394. All you need in NI-488.2 version 1.70 from National Instruments. Install this driver and then insert your card. Windows should detect the card and find the proper driver.
If this did not happen in the proper sequence, look in the device manager and see if the card was installed as an "other device". If this happens, remove the card in the device manager and have windows redetect it. If this is not a solution, you may consider the ask an engineer page at www.ni.com/ask. Provide as many details as possible.

GPIB read freezing when running vi without debug light ... (it works with the light)

I have a gpib read that spits out two values at a offset. This is in a loop thats defined by the initial , final and step size parameters. My question is, why does the gpib read freezes (or doesn't exectue; whenever I turn the debug light on(after it's been run), it 'lights' up only till the gpib read and nothing further). I replaced the gpib read with visa read , it doesn't freeze anymore but it only records zeros (when I can clearly see my system outputting some values). Any help would be appreciated.
*there was a similar topic about debug light and the reasoning was made to be a race condition. but I dont see how my situation is a race condition.
Thanks,
kb.
Solved!
Go to Solution.
Attachments:
racecond.PNG ‏37 KB

kb003 wrote:
Cleaning up...for me thats the cleaned up version. I'm still figuring out labview.
Stacked sequence made the perfect sense in a 1-2-3 logical reasoning.
<snip>
I wrote my code from an ancient driver set. I figured why to mess with something that's already working. So, I built it all on gpib.
This brings up an ancient scrap I have with National Instruments. Namely, they advertize LabVIEW as something so easy to use, you can dive right in. Well the truth is, you can dive right in, but it's guaranteed you will be writing horrible code, and much more easily than with any other programming language.
In reality, you really have to have training, formal (classes) or informal (books on LabVIEW), just like with any other programming language. Because NI keeps promoting the LabVIEW Falsehood, you get managers that assign newbies to write complex code, and then you have issues like the one the poster has above.
I'll get off my soapbox now and return you to your local programming, already in progress...
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

VISA and GPIB

Hi all,
It seems that all example code found online to use VISA to write to GPIB will send string (command and data). I wonder if this is how it design or we can change that to use binary data instead? Now to send 100 8-bit data (ranged from 100 to 200), I have to converted 3 character for each number so it will be at least 3 times more than sending the binary data.

dragondriver wrote:
Hi all,
It seems that all example code found online to use VISA to write to GPIB will send string (command and data). I wonder if this is how it design or we can change that to use binary data instead? Now to send 100 8-bit data (ranged from 100 to 200), I have to converted 3 character for each number so it will be at least 3 times more than sending the binary data.
As Dennis said, you send the data in whatever format the instrument wants it in. If it wants ASCII digits, then use the Decimal Number to String to convert to a string to send. If the instrument wants binary data, then just use Byte Array to String and send that.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions

GPIB error in the instrument while no communication error

I am developing a test system by connecting several measurement instruments through GPIB with LabVIEW 6.i. The driver is written by using VISA command. GPIB control card is NI PCMCIA. When using laptop everything runs fine. When using an old PC with something like EISA to PCI converting card for slotting in the NI PCMCIA card. One instrument always displays an GPIB error. The error is instrument specific, no further detail is given by the manual. When the error comes out, no GPIB or VISA error exists. If only the driver for this instrument is installed so that the software only communicates with this particular instrument, no error. With other driver installed, there is no error in the first or two commnunication
. Later on the error is surely out and display in the instrument screen only. Once again, no any other GPIB or VISA communication error. Anybody can help on this ? Thanks a lot.

Hi JLS,
First of all, thank you very much for your prompt response. I am not sure some of your questions because our hardware engineer is away for a week. I am trying to explain what I know and see whether you could help to figure out the reason.
0. The operation system in the old PC is Win98. The CPU is PII 350MHz, 32G Hard disk and 320M RAM. The reason why we are using the old PC is that we have a 3rd party motion controller. Its control card is a ISA card.
1. The conversion device is a kind of card, put in the ISA slot in the PC extention I/O bus. We can slot in 2 PCMCIA cards in the conversion device. The driver for the NI PCMCIA card is supposed to be the same with that in laptop.
2. The driver that works with the instrument is developed by me by using NI-VISA. The instrument is a signal generator (SG) from Marconi instruments. Basically what the driver does is to turn on or turn off SG and read back its on-off status. When turning on SG, send setting frequency and signal level data as well. The calling of the driver is in a loop where frequency is stepping up.
3. There are other measuring instruments. e.g. electric field monitor probe to get the electric field strength etc. All these instruments' driver are developed by me by using NI-VISA. I also develop a set of dummy driver for all the instrument for demo purpose. Dummy drive did not communicate with instrument, inside, control is directly wired to status. When all other instruments except SG uses dummy driver, The running is OK. No error is displayed in the SG screen. If I use any of the other instrument's driver with that of SG, there is no problem at the first run (that means at the beginning of the loop), problem surely comes out later on. But it is OK when running in the laptop of which the OS is Win2000. The funny thing is if I takes out the status readback in SG driver, there will be no error at all even running with other instruments' driver in the old PC. I have compare through the GPIB card setting in the old PC and laptop, make sure that the EOI setting, primary address, EOS etc. to be the same in the two computer. It does not work.
4 & 5. The error displayed in the instrument screen is Error#403 "Data Expected". The manual said it is caused by the GPIB programming wrongly. No further explaination on how it may happen. Even there is such error display, no any GPIB or VISA error happens in my driver, the error cluster is clear. I debug the problem and find that the SG error appears when executing VISA resource open. I have also checked through all the NI GPIB help. It seems I could not find the answer.
6. I am not sure how to check the version of NI-488.2 and NI-VISA. NI-VISA is installed with the LabVIEW 6.i together.
Best Regards
Jason

JAVA + 32 bit Borland DLL + gpib-32.dll

Hello,
I develop a Java application, which - thanks to the Java Native
Interface - communicates with a 32 bit DLL (I called gpib-jni.dll)
I wrote this DLL with Borland C++ under Windows 98.
This DLL contains .cpp and .h files that make a link between Java
classes and another library for GPIB use: borland_gpib-32.obj
Actually, National Instruments (manufacturer of GPIB products) delivers
a gpib-32.dll file to control GPIB boards.
I installed my GPIB board and the gpib-32.dll file has been installed in
C:\WINDOWS\SYSTEM directory.
When I run my program, the Send() and Get() commands of the GPIB driver
don't work.
Perhaps there is something to do, in order gpib-32.dll understand
borland_gpib-32.obj content ?
I trie
d to include gpib-32.dll directly in my 32 bit DLL (gpib-jni.dll)
, but gpib-jni failed when linking operation.
Thanks for help.
Stephane Davy
Software & Signal Processing Engineer
Observatory of Paris - DESPA
92190 MEUDON
France

Hi,
File>Properties
what IE security zone does your page map to?
Tools>Internet Options>Security tab, security zone... by default Enhanced Protected mode is turned off for the Trusted and Intranet zones...
If your java rt app requires the 32bit environment... (viz will not run within a x64 browser process)..
then you need to add a feature test to your page.
If(navigator.platform.indexOf('32')>-1){// show message that browser is using an incompatible platform)
Usually IE will show a warning asking to remove a site from EPM (64bit mode), if it detects that no x64 bit version of the Java RT is available (installed/enabled).
Post questions about html, css and scripting for website development to the IE Web Development forum... include with your questions a link to your website or a mashup.
Regards.
Rob^_^

Why can't I communicate with both of my GPIB devices?

I have 1 NI PCI GPIB board in my computer
I have 2 identical devices (keithley 237) connected one at address 15 one at address 16
and 2 different programs one program to connect with 15 and 1 to connect with 16
after I tell the 1st labview program to communicate with 15 then I tell the 2nd labview program to communicate with 16. then both communications come back with error device timeout. one at a time, I can communicate find with either device.
Why can't I communicate with two different GPIB devices at the same time?

Hi mrutter,
first I would try some other addresses, e.g. 5 and 11. 15, 16 could be
a special address used by the controller.
Are there any other devices on the GPIB? If so then there could be
another instrument with the same ID. Do both (or all) devices show in
MAX, and can you communicate with them in MAX (e.g. query a *IDN? )
And are you sure that you *have* setup the correct addresses in the
Keithley instruments (look in the manuals if you don't know how to
change their addresses)? Some Keithley instrument are in local mode by
default, and you must explicitely set them in GPIB mode.
Sometimes, GPIB message termination can be an issue (although both the
GPIB cards and the instruments seem to get more tolerant of this).
Also, you must be very careful not to mix different versions of
LabView drivers and LabView version. I once had three different
LabView versions on a PC, it was terrible. We had to format the
harddisk and start afresh since we couldn't remove all of the older
versions.
I first try all GPIB instruments in MAX. If all devices appear there,
and I can query commands in MAX, then I usually write my own LabView
drivers with the standard GPIB-read and -write VIs. I write them with
my oldest LabView version (say 5.1), then I am sure they will work
with all versions up to 7.1
Actually I once had a project where *no* GPIB instrument worked 100%.
We could never really find out what was the problem (it was probably a
bad PC <-> Win98 <-> GPIB card <-> LabView 5.1 constellation).
Good luck.
Johannes
On Fri, 12 Nov 2004 13:49:31 -0600 (CST), "mrutter@contech"
wrote:
>I have 1 NI PCI GPIB board in my computer
>I have 2 identical devices (keithley 237) connected one at address 15
>one at address 16
>and 2 different programs one program to connect with 15 and 1 to
>connect with 16
>after I tell the 1st labview program to communicate with 15 then I
>tell the 2nd labview program to communicate with 16. then both
>communications come back with error device timeout. one at a time, I
>can communicate find with either device.
>
>Why can't I communicate with two different GPIB devices at the same
>time?

GPIB-ENET/100, NI-488.2 fails to be properly installed on Mac OSX.

I am trying to install a new GPIB-ENET/100 on my Mac iBook 600 MHz 384 MB running Mac OSX 10.3.2. The GPIB-ENET/100 will eventually be used with LabVIEW 7.0. After running the installation procedure, IP 192.168.0.12 is assigned to the GPIB-ENET/100 device. When I then run the Trouble Shooting Wizard the first two steps are passed but the third, "GPIB Interfacees Sequentially Verified" fails. I am instructed to click on the interface in the associated list to get help but the whole help system is dead in this installation. The firmware is B9.
The device does not seem to work from LabVIEW either.
Any help would be very much appreciated.
Lars Hellberg, Chalmers U. of Technology, Sweden

Scott,
Thank you for your response.
I am pleased to say that everything (except the 488.2 help) works now. The road here was not all straight however and strange things happen.
Firstly the "Troubleshooting Wizard" reports, even when the ethernet cable is REMOVED (as a test), that:
1) NI-488.2 Software Presence Verified-PASS (Seems ok to me)
2) GBIB Hardware Presence Verified-PASS (??????????? very odd to me)
3) GPIB Interfaces Sequentially Verified-FAIL
This is what made me look in the wrong direction as, to me, the test seemed to say that the GPIB-ENET/100 "box" was actually detected and the IP number settings was ok (my cable was NOT disconnected when I wrote the first time). Now I (think) I know that my problem was associated with incomplet
e IP-number settings in terms of "Sub net mask", "Gate way" and "DNS server" which caused the comunication to fail. This problem is related to my incompetence in the science of IP.
Secondly, now I know that the "Explore GPIB" program works equally well independent on whether or not the ethernet cable is connected. This further contributed confusion and added to the impression that the GPIB-ENET/100 "box" was actually detected and communicated with.
To sum up, if you are not using DHCP you have to be very careful with ALL the IP settings.
As far as the dead help function in all the NI-488.2 programs is concerned I have no clue at the moment but I will look in to it at a later time.
Regards
Lars
P.S.
"Sometimes, having a GPIB Instrument connected to your GPIB interface can cause the Sequentially Verified step to fail."
This doesn't seem to give me any promlems.
D.S

Difficulty in reading GPIB device(power meter)

I am using the following Vi attached. i am generating array of frequency writing it to the signal generator with GPIB address 28.afterawards reading powermeter with GPIB address.and finally writing it to the file.
the problem is some times this GPIB read does not work properly. i get error from the power meter. in the read array it displays trigger or Nrvs or some thing different. i thought may be it is due to initializing of power meter. i send SC1 command for power meter initialization. but it does not work. why ? i attached the manual of power meter and signal generator.
thanks for some help
Attachments:
27_10.zip ‏57 KB
manual.zip ‏13855 KB

yes you are right.but if i just execute this driver and afterwards i execute my VI i get some reading from power meter in the form of an string array. it is like this i write an array of frequencies to signal generator at GPIB address 28.and then other device(power meter) is connected at GPIB address 13.
this device returns reading in the form an array string. i thought that i must send/write some command to GPIB 13 device (power meter), so that it starts sending data.this is i am doing in my VI by sending SC1 command. may be i am using wrong command or may be i must send some sequence of command.
the problem with executing the driver, that you mentioned is that i have to execute this driver VI all the time just before my VI.if i execute this driver VI/DL
L then every thing is fine and my VI sends and read reading according to my wish. but what happened if all these devices are initialized or reset,my VI does not run any more. and because i dont know which part of this driver VI cause this activation to react, i just have to blindly execute the driver every time without understanding what should i do in my VI that i dont need to execute the driver any more and this VI would be independent of driver VI.
thanks

Populating list with connected GPIB interfaces

I'm working on the setup section of an APP in Delphi5.0 using the GPIB-32.DLL and am a little baffled. Ni supplied this little gizmo that searches for GPIB interfaces (not devices). I would like to emulate this functionality for my application in a setup wizard sort of way so the end user can simply select from a list of 'detected' interfaces. In looking at the DLL calls they all seem to require previous knowledge of the device location. So I'm wondering if there is a set range of possible Primary and Secondary addresses I can use to just loop through searching for an interface. I'm assuming here that anything that wouldn't toss a failure when sent a Pri/Sec Address would be a set of valid device ports. On that note...
are there some specific commands to issue that will return a string telling me exactly what it found on that Pri/Sec address?
Thanks!
CT

Ok.. I made some progress. Using SendIFC and ibfind, etc, watching NiSpy I have determined this is coming back as an Integer and other Ni applications use the Init_DA_Brds to obtain a translation of the integer to descriptive title. However I don't have access to that and the only reference I found of the device list codes is from 1999 which does not include some of the newest hardware including the USB based devices.
Is there a newer list of product codes available?

Labview and GPIB upgrade horror

Hello community,
I have to upgrade and extend an old LabView system. The old system
runs with LabView 4.01 and Win3.11 and has been working for years
without problems. It uses the standard GPIB VIs in LabView to
commumicate with measuring devices, sensors, supplies, heaters, etc.
I really can't understand why I get a GPIB error 3 with *most* of the
devices under LabView 5.1/Win98 and *exactly* the same GPIB devices
and VIs. The GPIB VIs just initialize the GPIB, and write strings,
then close the GPIB. No more. I don't understand why something that
worked with an *older* version of LabView systematically fails with a
newer version (I could understand it vice versa).
I know that the standard answer is 'you can't use a LabView 4.01
driver in LabView 5.1', but these 'drivers' are no real drivers. They
just form the string to write to GPIB for the GPIB device,
respectively. No more. And the string to write didn't change because
the GPIB devices didn't change.
Also, it doesn't seem to be a problem of an odd GPIB device (exotic or
ancient), but a general problem. Could it be that I miss something in
the configuration of the GPIB card? In LabView 5.1 I can configure the
GPIB in the Measurement and Automation Explorer (GPIB Properties). I
would like to verify the configuration with that used in LabView
4.01/Win3.11. I do not have an Automation Explorer in LabView
4.01/Win3.11. How do I get the same information there?
It is probably not even a LabView 4.01 -> LabView 5.1 problem. The old
system is on a 486 PC and certainly uses an older PCI GPIB card. The
newer system runs on a Pentium II and uses a brand new PCI GPIB card
from NI. I tried to installate LabView 4.01 on the newer PC (yes,
after having removed LabView 5.1), but the GPIB VIs didn't work
either. Note, however, that it is LabView 4.01 for Windows 3.1
(16bit), (we only have the 16bit version) so, I am actually not
surprised that it doesn't work with Win98. Some person suggested to
use a rather old GPIB card in the new system, but this can't be true
IMHO.
Another person pointed out that maybe NI changed the interface of the
GPIB write VI. That is, even if the VI has exactly the same appearance
and connectors in both LabView versions, some connectors that were
optional in LV4 could have become mandatory in LV5. I read the
documentation of the GPIB write VI in both versions. It is exactly the
same. It would be more than strange, anyway.
When I tried to write a GPIB 'driver' and I have a working driver for
an older version than I analysed the string the old VI writes to the
GPIB and I write exactly the same string to GPIB in the new driver.
It's very strange for me that this doesn't work.
Maybe another person has some experience and give me a hint what
*could* work (maybe with GPIB II or VISA).
Thanks very much.
Best regards
Johannes

Hi Joe,
On Mon, 8 Dec 2003 07:32:37 -0600 (CST), JoeLabView
wrote:
>Wow... That's a lot of info..
>
>First of all, let me understand the scenario.
>
>1. Newer PC from 486 to P-II.
>2. From Win-3.11 to Win-98.
>3. Newer GPIB cards.
>4. Upgrade to LV-5.1
>5. vi's remained unchanged from LV4.01.
>6. Instruments are the same, same cables, etc.
>
>The problem is the inability to communicate with the instruments or
>inability to configure them.
Correct.
>
>
>Let's look at the additional info:
>
>"I really can't understand why I get a GPIB error 3 with *most* of the
>devices under LabView 5.1/Win98 and *exactly* the same GPIB devices
>and VIs."
>
>So you are able to communicate with some of the devices.
Yes, with two of them, because I could get *working* LabView 5.1
drivers for these devices. I didn't have to write them myself. I have
looked at the drivers for these devices. One is a Keithley 2000
driver. Internally it uses the standard GPIB write VI. The other is a
VISA driver for a Toellner power supply.
>
>My first question would be:
>Q: Did you use MAX (Measurement & Automation eXplorer) to detect your
>GPIB card and find the instruments? The GPIB interface should show up
>under "Devices & Interfaces". It probably does since you are able to
>communicate with some.
Yes, I can find all instruments when I scan in the MAX, even if one
instrument (a Heraeus-Voetsch HT4004 oven) doesn't return an
identification string. But that is no error because the oven is
connected via a GPIB to serial interface converter (from the same
company.) and I guess they just wanted to get conversion done without
cosmetics
>Otherwise, I would recommend looking into the
>device driver info within "System" in Control Panel of Win-98 to
>determine if there is a conflict with the board..
I can even query the HT4004 for *IDN? and I don't get an error. (I
just get a white space (?) because the HT4004 doesn't return an
identification string as I wrote above, but I don't get an error).
In fact, this HT4004 is the last GPIB instrument that doesn't work,
because I have found a substitute or a workaround for *all other*
instruments that didn't work. But I *have* to use this HT4004. And it
is no instrument specific error because in the beginning I got this
error with allmost all GPIB instruments.
>"the GPIB devices didn't change."
>
>Did you install a new GPIB card? Device... you mean instrument,
>right?
Yes. The new LabView 5.1 system is running on another PC with another
brand new GPIB card from NI, but the GPIB instruments (measuring
devices, HT4004) didn't change.
>
>
>"Could it be that I miss something in
>the configuration of the GPIB card? In LabView 5.1 I can configure the
>GPIB in the Measurement and Automation Explorer (GPIB Properties). "
>
>Maybe.. So try this..
>
>In MAX, go to Devices and Instruments, select the "troublesome"
>instrument and click on "Communicate with Instrument". Here, you can
>send your string and see "manually" the response from the instrument
>or observe the behaviour of the instrument based on the command or
>string that you send it. That will tell you a lot about the
>communication over GPIB..
I have tried this, but nothing happens. The HT4004 should turn on a
ventilator and begin to warm up. Tomorrow, I will try it again, I am
not in the Lab today. But you mean that I should do a *write*, not a
*query* with the string?
>"I would like to verify the configuration with that used in LabView
>4.01/Win3.11. I do not have an Automation Explorer in LabView
>4.01/Win3.11. How do I get the same information there?"
>
>Focus on the newer LV5.1. You're stepping up...Don't turn back. ;o)
Yes. I just want to check if the configuration is special in the
LabView 4.01 system (maybe a check on 'send EOI with EOS or another
timing).
I would actually turn back to a 4.01 system that works instead of a
7.0 system that doesn't. However, I would definitely not turn back to
Win16.
>That would indicate that the problem is not the newer version of LV,
>but more likely related to the GPIB card or setting. Did you get
>those newer GPIB cards to work?
Hmm, it works with the Keithley and Toellner instruments. Also, I have
tried the whole system on a *third* PC with Win98/LabView5.1/PCI GPIB
card. Same error.
>Or can you try the "older" ISA GPIB
>card in the newer PC?
I think it is a PCI card. I will try that too, as a last step, since I
hesitate to destroy a running system...
Johannes

AT-GPIB/TN​T on eCS1.2 (OS/2 kernel) anyone tried this?

Similar Messages

Maybe you are looking for

AT-GPIB/TNT on eCS1.2 (OS/2 kernel) anyone tried this?