GPIB Enet/100 with PCI-GPIB

Is the a timeframe with the release of a GPIB Driver
capable of supporting both the Enet device and an installed GPIB-PCI card within the same computer?

The next version of the 488.2 driver will support the ENET and PCI GPIB cards together for Win 2000/NT/XP. We canot give a release date at this time but it will be on the web when we do.

Similar Messages

GPIB ENET/100 and PCMCIA GPIB+ pictures

Has anyone some pictures of GPIB ENET/100 and PCMCIA GPIB+ controllers
with a higher resolution than the pictures on the website?

Hi,
We don't have any other pictures available than the ones on the online datasheets. Is there something specific you want to know about a feature of this hardware?
I not, that maybe someone on the forum, that has the hardware available, can take a digital picture of it.
Regards.
JV
NI Belgium

Gpib-enet/100 no longer recognizes equipment

Hi, first of all, we purchased a company and they sent us their Automated test setup. It was functional, with thier old network, until the IS dept came and switched their old network to our current.
Now when I start the software ATE, it pops up a message saying, the power meter cannot be found. I tried to let the system continue, but then it seems unable to see any of the other instruments connected to the setup!
Can anybody out there help me?
When I try to detect the gpib-enet/100 with labview, it does not see the device attached to the system...

Hello,
I think that you're having general connectivity issues with your GPIB-ENET/100. My first guess would be that your IP addressing scheme changed when the new network was setup, so you probably need to re-assign a valid IP address to the ENET and reconfigure your computer to find the ENET. These are steps that are outlined in the "Getting Started" manual for the operating system that you're using, and you should be able to find that at the link below. A first troubleshooting step is to look in MAX (Measurement and Automation Explorer) to examine your setup. Your ENET/100 box should show up as "GPIB0" or something like that under "Devices and Interfaces". From here, you can do a "Scan For Instruments" to try to talk to the box and also see what instruments a
re out there.
There is also a lot of information about general setup and troubleshooting of your ENET device right here.
Scott

GPIB-ENET/100 Issues with Red Hat Enterprise Linix 3.0

Does anyone know of issues with Red Hat Enterprise Linux 3.0?
Using Red Hat Linux 8.0, I am able to run EthernetConfig and identify all the GPIB-ENET/100 devices on my Ethernet.
Running EthernetConfig under Enterprise Linux does not work properly. No devices are detected.
Everything else appears to be working.
I can ping the device.
I can also detect the device using my Windows based program NI-488.2M for Windows NT/GPIB-ENET100 Utilities/Device Configuration.

I do not know of any issues with RHEL 3.0 and the Beta 488.2 driver. I believe that you have started a support request via e-mail so I will deal with your issue there.
Thanks,
Scott B.
Applications Engineer
National Instruments

Why do I get timeouts with a GPIB-ENET/100 under Solaris that I did not get with GPIB-ENET.

We have an existing application that works fine under Solaris 2.6 and Solaris 7 with a GPIB-ENET. When we swap the GPIB-ENET with a GPIB-ENET/100, we get devices timeouts all the time.

Hello-
Unfortunately, it's difficult to determine any possible cause for this occurance. It was mentioned in a previous email that the instrument will communicate for a few commands. When does the timeout happen? What command fails? Also, what type of instrument is connected (make, model, etc)? Is this a timeout from the write or read? What is the distance of the Ethernet from the host? Is it possible that another machine is accessing the GPIB-ENET/100? Would it be possible to include the code that communicates with this instrument? Does ibic or VISAic communicate with the instrument without timeouts?
Hopefully, this information can pinpoint the exact cause of the timeout.
Randy Solomonson
Applications Engineer
National Instruments

Is there a way to communicate across subnets with the GPIB-ENET/100?

I have a GPIB-ENET/100 that I am using. It is sitting on my engineering subnet. My PC is sitting on my corporate subnet and I am trying to communicate between the two. I can ping the device from my PC but the MAX cannot discover it. I noticed there is a message saying that this utility will only discover devices on the same subnet but was wondering if there has been any work arounds done or s/w upgrades available that will allow this to work?

MAX will certainly not discover it because it does so by sending out a broadcast packet and routers between subnets are designed to ignore broadcast packets (rightfully so, otherwise all broadcast packets from every subnet in the world would propogate over the entire internet).
I believe that you will be able to get this working by manually specifying the IP address (or hostname) of the GPIB-ENET/100 once you have it setup in MAX. If it is setup as, say, GPIB0, right click on that in MAX, go to Properties, and go to the Network Settings tab. In that field you can specify whatever IP Address/hostname you'd like. As the text points out, you cannot auto-discover using the "Search" utility since you are on a different subnet, but if you know your ENET/100 IP add
ress then you should not need that.
Let me know how this goes.
Scott B.
GPIB Software
National Instruments

Is the GPIB-ENET/100 VXI-11 compliant?

Hello,
I've written some code in C/C++ to impement a VXI-11 client. The code works with the Agielnt E2050A and E5810A fine.
Now I've tried to use the NI GPIB-ENET/100, too.
If I run my programm I get a "RPC connection refused" error.
The code is similar to this
CLIENT *rpcClient;
static char *svName = "lanhpib2";
rpcClient = clnt_create(svName, DEVICE_CORE, DEVICE_CORE_VERSION, "tcp");
if (rpcClient == NULL)
clnt_pcreateerror(svName);
return 1;
The clnt_create(...) function aborts with a RPC connection refused error.
Is the ENET/100 not VXI-11 compliant?
Why is it not possible to open a RPC connection to the ENET/100?
CU,
Gerald

The GPIB-ENET/100 is not a VXI-11.2 device. Instead, it uses a proprietary NI-488.2 ethernet protocol to provide a seamless transition from a plug-in (PCI-GPIB, AT-GPIB/TNT, etc.) type of board to an ethernet board with zero code changes. You can use NI-488.2 or NI-VISA to communicate to the instrument as a GPIB instrument.

Dell Laptop Won't Communicate w/GPIB-ENET/100

I have a GPIB-ENET/100 that works great when controlled from a desktop computer on our network, yet when I try to control it with a laptop, it won't pass the third test (GPIB Interfaces Sequentially Verified) in the MAX NI-488.2 Trouble-Shooting Wizard. NI-Spy reports iberr EDVR(0):
> 1. ibfind(GPIB0)
> Process ID: 0x000007FC Thread ID: 0x00000360
> Start Time: 09:18:36.876 Call Duration: 00:00:02.323
> ibsta: 0x8000 iberr: 0 ibcntl: -519700367(0xe1060071)
The laptop is a Dell Latitude C510/C610 running Windows XP and NI-488.2 2.10. I've also verified that I have the latest BIOS and drivers.
Has anyone else ever seen anything like this?
Thanks!
Matt

Hello gpibtester,
That was it, although I could swear that was one of the first things I checked, and neither the hostname nor the IP address seemed to work. I must be losing my mind. ;-)
To summarize, it appears that although a hostname can be specified in the "Device Configuration" via...
1. Invoke MAX
2. Right-click on the GPIB-ENET/100 in the Devices & Interfaces list.
3. Select "Device Configuration" from the drop-down list.
4. Select the IP address/hostname of the GPIB-ENET/100 in the new window that appears.
5. Click the "Properties" button.
...it cannot be used to address the device in the "Network Settings" accessed in the 5 steps you described above. I had to use the actual IP address of the GPIB-ENET/100.
Th
anks again!
(I've attached screen shots of the device configuration and working and non-working network settings for anyone else that may have the same problem I did.)
Matt
Attachments:
GPIBENET100_device_config.gif ‏9 KB
GPIBENET100_net_settings_not_working.gif ‏8 KB
GPIBENET100_net_settings_working.gif ‏8 KB

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

Can't see GPIB/ENET-100 on MAX

I am trying to test some modified code (new switch drivers) with the new switch in LabVIEW 6.1 before integrating with a delivered test set. I'm using a GPIB/ENET-100 to connect to the switch, with NI488.2 version 1.2, which is what is being used in the delivered product. The operating system is Windows 2000.
I've configured the IP address and subnet mask on both the computer and the GPIB/ENET-100 so that they can communicate, and configured the GPIB on the computer to set the ENET box as GPIB0. The GPIB diagnostic passes. But when I launch Measurement and Automation Explorer (version 2.2, which was installed with LabVIEW 6.1) it doesn't show GPIB0, even after refreshing. If I bring up VISA interactive control I see a GPIB0, but not the switch modules which are connected to it.
What am I overlooking?

If your end system is on a Win2K machine, why aren't you using the current NI-488.2 driver? I know this may not look like the answer to your question, but the 1.2 driver is five years old, and whatever problems you may currently have, or may have in the future, may very likely have been addressed and corrected in the later revisions of the driver. You can download NI-488.2 v2.3 here.

What is blinking code 88 on GPIB-ENET/100 mean?

Hi,
This is a continuation of the post "What is EDVR error 0xE1060077?" from a few days ago, which is still unresolved. I have recently noticed that the GPIB-ENET/100 was blinking code 88. Thinking that it might be code 89, I updgraded its firmware to C.9. However, this has not changed anything. I still get EDVR error 0xE1060077 using ibic. There are very brief (a minute or two) moments when it seems the GPIB-ENET/100 is working fine. Otherwise, it fails in the NI GPIB troubleshooting program. As for blinking code 88, I haven't spotted it yet; but I only saw it once before the other day, after leaving the GPIB-ENET/100 on for a while.

coopee,
Is your device still displaying an error code, or did it go away after you upgraded the firmware to C9? Error code 89 was a common error with the GPIB-ENET/100 which is why we released the C9 firmware. I would imagine that if you haven't seen an error code since you upgraded the firmware that you actually saw error 89. If you are still seeing an error code verify that it is indeed 8 long pulses, and 8 short pulses.
As far as your EDVR issue and sequentially verified failing. Is your GPIB-ENET/100 configured with DHCP, or a static IP address? Since you have two ENET/100s, and one is working, check to see if there is any difference in how they are configured. Are they both configured with DHCP or static? Are they both on the same subnet as your computer?
I suspect like Scott suggested that you are experiencing a networking issue.
Shawn B.
National Instruments
Use NI products on Linux? Come join the NI Linux Users Community

My GPIB ENET/100 Controller doesn't boot reliably.

I am using version 2.0 of the NI 488.2 software.
The GPIB ENET/100 controller is running firmware version B9

Hi Bojangles,
Can you describe what is going on with your controller? When you turn it on it does not respond? Are the lights on it flashing? If you give us some more information, I am sure we can get to the bottom of this!
Best Regards,
Aaron K.
Application Engineer
National Instruments

Does GPIB-ENET/100 also use RARP?

Our existing UNIX network has several older GPIB-ENET devices which get their IP addresses from our server using RARP. We are going to add several new GPIB-ENET/100 devices. The Getting Started manual states that the new devices use DHCP to get their IP addresses.
My question: If we don't have DHCP enabled on our server, will the newer GPIB-ENET/100 devices "default" down to using RARP to get their addresses?

Thanks for your reply. Yes, our fallback plan is to use static IP addresses. We are going to have a mix of older units and new units at the same time in the system we are maintaining. I was hoping that the new units would use RARP such that all the units would work equivalently. I have since found that RARP and DHCP are quite different, so I will investigate configuring DHCP.
Using static IP addresses has several drawbacks for us. The units are located in remote areas which makes static programming difficult. If a unit fails and a spare unit has to be dropped in, it's much easier (with RARP) to just slap in the unit and update the /etc/ethers file. With a static address we'd have to make sure the unit is in programming mode and then set the static value
s. Not difficult for us, but the end users will need very exact procedures.
Based on how difficult DHCP is to configure/update/maintain we'll make a decision whether to use that or go with static addresses. Of course then we'll have to decide whether to switch the older devices over to static addresses for consistency, etc. That's progress for you!

What is error 89 on the GPIB ENET/100?

My GPIB ENET/100 controller is signalling error #89 through PWR/RDY LED signalling. What does this message mean?

Hello,
Create a service request and send an email to NI support; it will be handled most appropriately in that manner.
Best Regards,
JLS
Best,
JLS
Sixclear

Problems when the GPIB-ENET/100 is powered off.

Is there a way, other than Ping, to prevent the long timeout periods when a GPIB-ENET/100 is in or enters a bad state such as powered off?
Attachments:
GPIB_Power_Problem.doc ‏23 KB

Hi,
I did some tests and searched through the documentation, but I couldn't find any NI-488.2 function that would explicitly verify if the IP address is valid.
An EDVR means that an operating system error occured. Some function within the driver failed and the error code returned by the function is store in ibcnt.
You could use this error to as a signal that the ENET is not there or it is off. Any EDVR means some fatal error occur, so you can assume you need to restablish communication. It doesn't matter if the ENET is off or the network is failing, in any case the EDVR will indicate a fatal condition.
You can then call a function that handles this situation by calling ibonl(ud,0) to close the handle (which i think will also return an EDVR error)
and then try to restablish communication using the ibdev function.
The reason the timeout value doesn't affect the time it takes for the function to return is that the timeout is used to abort GPIB operations, not function calls. The timeout value is used by the ENET firmware to determine when to abort an I/O operation on the GPIB bus. The driver doesn't use this value to timeout the network communication.
Finally, you could use the windows socket API in your code to determine if the IP address is valid. You could probably find some simple ping code that you could include in your application.
Hope this helps.
Diego

GPIB Enet/100 with PCI-GPIB

Similar Messages

Maybe you are looking for