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.

Similar Messages

  • 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

  • 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

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

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

  • 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

  • How to determine GPIB-ENET firmware version?

    I have several of the older GPIB-ENET units. I see the latest firmware binary on the FTP site is A5. I'm pretty sure our units have olders revs since they were installed several years ago. However the manual says to only update the firmware when necessary since there are a limited number of times the firmware can be updated.
    My question: Is there a way to determine the device firmware version so I'm positive I need to update?
    I notice the new EthernetConfig utility for GPIB-ENET/100 devices shows the firmware revision when you select the device. Can this utility also "see" older GPIB-ENET devices and show the firmware revision for these older devices as well?

    Hi,
    Could you email in to the technical support deparment? You can go to www.ni.com/ask. We'll try some alternatives.
    DiegoF
    National Instruments.

  • 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

  • 2 Network Analyzer over a single GPIB-Enet

    I've some trouble using a single GPIB-Enet interface to control two different Network Analyzer simultaneously. It looks like to be not possible (commands are sent to both the instruments even if they have different gpib addresses!). I'm trying to do this with Labview 6.1 under Windows XP. The goal is to make two different measurements and collect data on two different PCs at the same time. Thanks a lot.

    This should be possible for you to do. Many GPIB-based applications do this type of thing. Here's what I imagine you would do to get this sort of thing setup.
    1. Send data to instument A and instrument B to get them setup to take a measurement. While doing this, you can usually get them setup to start the measurement when you send a Group Execute Trigger (GET) command on the bus.
    2. Send the group execute trigger. Note, because you're using two instruments here, you may want to use the TriggerList vi to trigger more than one instrument.
    3. Read data from the two instruments.
    While you won't actually be sending the data across the bus fully simultaneously, it should be sufficient for your needs. I'd recommend using the 488.2 style vi's in
    LabVIEW, as these may be safer for avoiding re-addressing problems that you could run into if you were using all board-level calls.

  • Sometimes unable to talk to device with GPIB-ENET

    I am using a NI GPIB-ENET device with my own application on a VMS Alpha computer. It is issuing commands to the device correctly but if I restart quickly the application it sometimes does not work.It seems that if I wait long enough the it works ok. Are the sockets on the GPIB-ENET configured to linger ?

    Hi zemaitis,
    The GPIB-ENET device is not "configured" to linger, but it does have more lag time than, say, a PCI GPIB card. The reason is that you have an increased amount of lag time due to the time it takes to transmit data over the ethernet cable. Here is a link to a Knowledge Base article that does not address this issue directly, but does point out that the ENET device has a larger lag time than other GPIB devices:
    Knowledge Base 38M9C9FJ: Execution Difference Between GPIB-ENET and PCI-GPIB
    Because of this extra communication time, you may not be able to restart your application extremely quickly. I hope this information is useful to you. Have a g
    reat day.
    -John M

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

Maybe you are looking for