Gpib-enet driver

I recently got a gpib-enet from an auction and after I got the box, I
found out the gpib-enet driver is not downloadable from NI site for
win2k/xp. Since the place I bot the gpib-enet from owned the
multi-user driver from NI, I asked NI to transfer me the ownership of
the driver after I gave them a valid serial number and all. But NI
refused to send me a copy even though it is a valid serial number that
they found on their database. I am very angry at NI on charging people
twice on the driver.
Would someone please help me out by email me a copy? thanks
Ahgu
[email protected]

There are drivers for the ENET for just about about every operating system under the sun. Development of these drivers cost quite a bit of time and money, above the cost of the hardware. Charging for these drivers is the method of recovering these development costs. Other GPIB drivers are purchased with the hardware, but the ENET is a special case because several computers can access one piece of hardware. There is a single-user license for Windows that can be purchased (P/N 778220-02).
Randy Solomonson
Application Engineer
National Instruments

Similar Messages

  • Gpib-enet driver 1.2 for win2k/xp

    I recently got a gpib-enet from an auction and after I got the box, I
    found out the gpib-enet driver is not downloadable from NI site for
    win2k/xp. Since the place I bot the gpib-enet from owned the
    multi-user driver from NI, I asked NI to transfer me the ownership of
    the driver after I gave them a valid serial number and all. But NI
    refused to send me a copy even though it is a valid serial number that
    they found on their database. I am very angry at NI on charging people
    twice on the driver.
    Would someone please help me out by email me a copy? thanks
    Ahgu
    [email protected]

    I had no trouble downloading the software. Just ignore the stuff that says you need a license.

  • 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.

  • GPIB-ENET not working in Windows NT 4.0

    I have a GPIB-ENET device and I want to configure it with Windows NT4.0 I
    have install everything like it is said in the NI web site and everything
    seems to be fine. When I try to talk to the instruments with Win32
    Interactive Control (IBIC) it works.
    I have created an application (In Visual C++ and the ComponentWorks++) to
    communicate with the GPIB device wich work perfecly on Windows 98, and I
    have a VI who also works well with Windows 98 but none of them works on
    Windows NT4.0. When I connect to the GPIB device I use "GPIB0::2::INSTR" as
    the address of the GPIB instruments and it work with win98, but doesn't with
    NT.
    I can see the GPIB-ENET device but where or how can I see the instruments
    that are pluged i
    n the GPIB-ENET? What are there connection string
    "GPIB0::????"
    Is the problem in my application or in the configuration of Windows NT?
    Anybody had this problem?
    thanks in advance
    [email protected]

    I has similar problem before update GPIB-ENET driver to version 1.2, On some
    systems with NT4 downgrade VISA 2.6 to VISA 2.5 may help - from old CDs for
    LV5.1
    "Eric Clermont" wrote in message
    news:[email protected]..
    > I have a GPIB-ENET device and I want to configure it with Windows NT4.0 I
    > have install everything like it is said in the NI web site and everything
    > seems to be fine. When I try to talk to the instruments with Win32
    > Interactive Control (IBIC) it works.
    >
    > I have created an application (In Visual C++ and the ComponentWorks++) to
    > communicate with the GPIB device wich work perfecly on Windows 98, and I
    > have a VI who also works well with Windows 98 but none of them works on
    > Windows NT4.0. When I conn
    ect to the GPIB device I use "GPIB0::2::INSTR"
    as
    > the address of the GPIB instruments and it work with win98, but doesn't
    with
    > NT.
    >
    > I can see the GPIB-ENET device but where or how can I see the instruments
    > that are pluged in the GPIB-ENET? What are there connection string
    > "GPIB0::????"
    >
    > Is the problem in my application or in the configuration of Windows NT?
    > Anybody had this problem?
    >
    > thanks in advance
    >
    > [email protected]
    >
    >

  • Interface specification for GPIB-ENET

    I have several GPIB-ENET Ethernet<->IEEE 488 controllers (P/N 181950L-01). For an embedded application, I need to write a driver for this device (preferably in Perl or Python). Where can I find the documentation of the protocol that the GPIB speaks over its Ethernet interface?
    Alternatively, if such protocol documentation is not available, source code for Unix/Linux tools and libraries for the GPIB-ENET might also serve my needs.
    I can't use any of the binary-only drivers or utilities supplied by NI, because my application does not run on a standard operating system. I need to write a very simple version of a GPIB-ENET driver myself, which I hope should not be too difficult, given the right documentation.
    Any help would be greatly appreciated,
    Markus

    Hi Markus
    There are C source code libraries available for purchase, which should allow you to create a driver for the GPIB-ENET device. This package is called ESP-488. Please see the following links:
    http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/430d8f6dae0f500f862568380057cbaa?OpenDocument
    http://digital.ni.com/softlib.nsf/954feaeea92d90918625674b00658b83/f519b04553e2b464862569ef00034db0?OpenDocument
    Hope this helps!

  • Solaris driver for PCI-GPIB and GPIB/ENET

    We have written a Java wrapper to communicate with the Solaris PCI-GPIB driver. Now we need to support the GPIB/ENET device. According to ibconf we are running the following driver (NI-488.2 Sol2 2.2). Is there a driver to support both? Our current wrapper supports the following commands: ibConfig, ibFind, SendIFC, Send & Receive.
    Thanks in advance,
    Paul

    Hey Paul,
    Unfortunately, we do not offer a driver that will support the PCI-GPIB and the ENET at the same time. In order to use the ENET you will need to use NI-488.2 Version 1.4 (http://digital.ni.com/softlib.nsf/websearch/67f3a​445bc3b87c3862569f2005855d9?opendocument).
    We recommend you do not install both of these drivers at the same time, because each driver was designed to run independently and some of the files would be overwritten.
    However, the functions will be the same for both drivers, so the code you�re developing should be interchangeable. There are a few additional functions the ENET supports, but they are just used to get information about the ENET and do not need to be in your application. The only difference is that you will need to link t
    he code to a different library when it is compiled. This information is located inside of the getting started guide.
    http://www.ni.com/pdf/manuals/322989a.pdf
    I hope this helps out.
    JoshuaP
    National Instruments

  • Is there an easy way to find out if the GPIB/ENET adapter is connected to the computer?

    I'm using Component Works for Visual Basic and have no problem with my software on computers with PCMCIA GPIB adapters. The GPIB driver seems to know if the adapter is in the computer or not.
    When my software is used on a computer where the GPIB/ENET adapter is not powered on, the software seems to lock up but eventually comes back with an error. Since there doesn't seem to be an easy way to determine if an adapter is present my code just assumes it's there, which doesn't work with the GPIB/ENET GPIB dll. Is there any way I can look for the board before querying for instuments on the bus?

    Hello David,
    One possible solution would be to ping the ENET box. If you know the IP of the box, a simple ping should immediatly let you know the status of the box.
    Best Regards,
    Aaron K.
    Application Engineer
    National Instruments

  • Questions re: GPIB-ENET, LabView 5 and 7, license and Win XP

    We have a full development version of LabView 5.0 on a Win 98 SE machine, and just acquired a GPIB-ENET box that came with Solaris drivers. I loaded the GPIB and VISA software on LabView 5.0 and tried to connect to test the setup to no avail. It appears that all of the drivers are present. I believe that my problem is that I can�t get the IPAssign network driver bound to the 3Com ethernet card. When I load it in network properties, it doesn�t offer any hardware to bind to it. If I run IPAssign anyway, it claims the only networking hardware available is dialup, and sits forever (probably waiting to connect to a dialup line).
    The ultimate plan is to upgrade to LabView 7, and install it with the GPIB-EN
    ET box on a Win XP system. I have a demo version of 6.1, so I loaded that on the XP machine and tried again. LabView 6.1 appears to be missing drivers for GPIB-ENET, and looking through the knowledge base tells me a driver bug leaves Win XP incapable of assigning an IP address to GPIB-ENET anyway.
    My questions are:
    1. Should it be possible to get LabView 5.0 with 98SE talking to the older GPIB-ENET box, at least to set the IP address? Is this failing because I need to download the license (p/n 778258-02)?
    2. If I order LabView 7 and install it on Win XP, will I still need to download the license to run it, or is that included in version 7?
    3. Once I get LabView 7 and the driver and the license (if necessary) will I be able to assign the IP address with this setup?
    4. If the answer to #1 is �yes, with a license� and to #3 is �no�, then can I download the license, use it to assign an IP address on LabView 5 and transfer it to LabView 7/ Win XP when I get it to use the GPIB-EN
    ET box?
    Thanks.

    Hello,
    Which version of the GPIB drivers are you using? We recommend using NI-488.2 v2.0 for your GPIB-ENET device (for Windows XP and Windows 98).
    1. Should it be possible to get LabView 5.0 with 98SE talking to the older GPIB-ENET box, at least to set the IP address? Is this failing because I need to download the license (p/n 778258-02)?
    A: If you have version 2.0 of the drivers, you should be able to assign the IP okay. Do you see a pattern in the LEDs flashing? Check the READY LED and see if you see a pattern, as this indicates an error code. The following formula can be used to find the error code:
    error code= (long flashes-1)(short flashes-1)example: 3 long flashes, and 9 short flashes = (3-1)(9-1) = 28
    If the READY LED does not stop flashing, it indicates that the GPIB-ENET does not have a valid IP address assigned to it. According to this KB:
    The problem is the Ethernet address. The field for the Ethernet address in the IPAssign Utility is meant for the last four digits of the Ethernet address on your GPIB-ENET (the first part of the address is the same for all GPIB-ENETs, so it is pre-filled for you). If you run the IPAssign Utility again and fill in the last four digits of your GPIB-ENET's Ethernet address (in the format: xx:xx), then you should be able to assign it an IP address successfully.
    More details: The Receive LED flashes because the Ethernet header for the packet is correct and the GPIB-ENET recognizes that; However, the header was actually duplicated when you entered the Ethernet address in the IPAssign Utility, so it did not match the exact Ethernet address of that particular GPIB-ENET. The only numbers that need to be entered into the Ethernet address field in the IPAssign Utility are the last 4 numbers in the format: xx:xx.
    Note: The user must decide what the IP address is going to be. Your IT department could probably help.The Ethernet Address however, is statically programmed into each ENET. It's usually labeled at the bottom of the unit.
    Also, refer to this KB regarding some IP issues we've had with some of the older GPIB-ENET devices.
    2. If I order LabView 7 and install it on Win XP, will I still need to download the license to run it, or is that included in version 7?
    A: You should uninstall and reinstall NI-488.2 v2.0. If you already have this driver, you will not need to re-license it. The driver is not included with LabVIEW 7.0 by default.
    3. Once I get LabView 7 and the driver and the license (if necessary) will I be able to assign the IP address with this setup?
    A: You should be able to assign the IP fine. Look at the response for first question above to make sure you are assigning the IP correctly.
    Anu Saha
    Academic Product Marketing Engineer
    National Instruments

  • 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

  • Mac gpib-enet/10

    Hi,
    I am looking for a way for my Mac OSX computers to communicate via GPIB to instruments.
    I cannot use PCI, since the computers don't have that bus. I already have several GPIB-ENET/10 and would rather not spend > $1000 on a new module.
    Is it possible to use the GPIB-ENET/10 with MacOSX? The driver only indicates compatibility with the /100 unit. Is it partially compatible?
    Thank you
    Lukas

    The latest version of Mac OS that the GPIB-ENET (GPIB-ENET/10) is supported on is Mac OS 9.1.x. To the best of my knowledge, it will not work in Mac OSX.
    Logan S.

  • Polling gpib/enet unit over tcp/ip using java

    I understand that there is a linux driver for the gpib/enet product. Since I assume this device is polled over a tcp/ip connection, do I need to do this in C, ot can I establish a socket connection using java ? If so, what is the driver for ? is it just to assign an ip address and other setup functions ?
    Thanks
    John Adams

    Hi John,
    You do not need to do this in C. In fact you can do it in just about any language. The librarys are exported to a shared object, so as long as your language can make calls to a .so, you are good to go. I am positive that java has this capability.
    Hope this helps out! If you need the driver, it is available at www.ni.com/linux.
    Best Regards,
    Aaron K.
    Application Engineer
    National Instruments

  • 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.

  • GPIB-ENET

    We have a GPIB-ENET box and are trying to interface with it on WinXP. I've downloaded and installed the latest drivers (2.2) but when I setup the device in MAX it sees three but only successfully identifies 1 of them (the first one). I even set it up as a GPIB-ENET/100 device and got the same results. I thought that maybe the driver was incorrect so I came back and checked and found this note for the GPIB-ENET interface:
    Note 4: The IP Assign Utility for the GPIB-ENET must be performed on Windows 98/Me or Windows 2000. After the IP address is successfully assigned, the GPIB-ENET can be accessed on Windows XP.
    How can I assign the IP address in another system when XP is all that is on the comp? Am I reading this wrong or does this basically say you have to setup and install the device then upgrade you computer to XP to get it working in XP. Obviously this creates some problems. One other thing, I've setup the IPAssign Protocol on my network settings but when I try to run the application I get a message telling me I need to setup the IPAssign protocol and instructions on how to do it.

    Gary,
    The GPIB-ENET assign utility can only be performed on those operating systems. You would have to go to a machine with one of those OSs installed to set the IP address.
    GPIB-ENET on WinXP
    Craig H.

  • Comms Failure detection on GPIB-ENET 10/100

    Hi,
    I'm using GPIB-ENET 10/100 units on my network to connect to test equipment via software written in C++ on Linux. I'm using the latest Linux driver on SuSE 8.0. Everything seems to be working fine.
    However, for some high availability processing, we would like to be able to switch to an alternate GPIB-ENET controller if we lose the network on a particular GPIB-ENET device. Both devices are connected to the same GPIB bus.
    When testing, I've found that I can do this when I first start my program - I get an EDVR error and switch to the other controller - no problem. However when I unplug the ethernet cable (or turn the unit off) after having been communicating with te device for a while, the "Send" command just hangs th
    ere. If I plug the cable back in after a minute or two, it picks back up and completes the command. I'd like to get the same error so I can switch to the next controller, but I don't. This halts all my processing, since it blocks on that command.
    Has anyone seen this behavior? Is there anything I can do to fix it?
    Thanks in advance for any help!
    - Joe Kralicky

    Hi Ray,
    Thanks for your reply.
    I don't think my program could sustain a 3-4 minute blockage like this. I may have to do some low level network stuff to make sure it's still alive before I talk to it.
    Thanks!
    Joe

  • 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

Maybe you are looking for