GPIB ENET Interface not recognized

Bonjour.
Je désire savoir si votre contrôleur GPIB-ENET est compatible avec les nouveaux réseaux dont le taux de transfert est au moins de 100 Mbytes/s avec une connectique RJ45. En effet, la led READY du notre ne cesse de clignoter quelque soit la position des switches DIN sauf lorsque le 6 est à ON et tous les autres sont à OFF. Le test du contrôleur échoue à la phase "GPIB Interfaces Sequentially" et m'informe que l'adresse IP est manquante. Or il lui est bien attribué une telle adresse. Enfin, si je décide de lui assigner une nouvelle adresse et que j'allume le switch 5 et éteinds tous les autres, la led READY ne cesse de clignoter.
Je vous remercie de votre réponse.
J. LEFEVRE
Ecole Polytechnique
djbarbados@hotma
il.fr

Hey bro -- I am probably a minority here in my complete dislike and distrust of MOTU products, but the same thing happened to me when I bought an 8pre -- it just stopped functioning and no one, at MOTU or anywhere, could figure out why. (And even when it did work it was sort of klugey). Luckily I was able to return it. Recently had a similar crap situation with a MOTU fastlane MIDI/USB interface: downloaded the most current drivers from MOTUs site and it stubbornly refused to appear. Returned it an bought and Edirol, which I had up and running, and connected a MCU to, in minutes.
All I could recommend is check their web site and see if there are new drivers. Or leave a message with their rech support via the site -- they do respond, eventually (within 48 hours in my experience).
Good luck.

Similar Messages

Interface not recognized

Hello!I have an iMac (Version10.6.8) and i've been using it with a M-audio fast track ultra interface,since i updated the iMac,the interface was not recognized by the iMac,i've tried all the drivers for this version i found, but it's still the same,any help?Thanks!

Hey bro -- I am probably a minority here in my complete dislike and distrust of MOTU products, but the same thing happened to me when I bought an 8pre -- it just stopped functioning and no one, at MOTU or anywhere, could figure out why. (And even when it did work it was sort of klugey). Luckily I was able to return it. Recently had a similar crap situation with a MOTU fastlane MIDI/USB interface: downloaded the most current drivers from MOTUs site and it stubbornly refused to appear. Returned it an bought and Edirol, which I had up and running, and connected a MCU to, in minutes.
All I could recommend is check their web site and see if there are new drivers. Or leave a message with their rech support via the site -- they do respond, eventually (within 48 hours in my experience).
Good luck.

MIDI interface not recognized after Mavericks install

Hi,
I was using a Midisport UNO with OSX 10.6, connecting my keyboard with the Mac Pro and using programs such as Live and Garageband. After the Mavericks install, I have a bunch of obsoleted hardware. I understand that Midisport have not come up with a driver to support Mavericks just yet. But that is not my issue.
Today, I purchased a new MIDI interface, one that is class compliant and so requires no driver software. According to everything that I have read, from external literature to the interface's literature, the device should work just fine. But my Mac Pro doesn't recognize the device in the Audio and MIDI Setup utility. In fact, it recognizes the Midisport UNO just fine but that device is greyed out and I guess this means there is no correct driver.
I have noticed that the Mac Pro seems to turn off ports when supplying power to USB devices. Sometimes, the front USB ports will not connect my iPhone to iTunes, for example. When I restart, the power sometimes returns. So is this a power issue or does my connectivity problem lie with the MIDI interface?
Thank you

I just purchased a new iMac running Mavericks. I have an M-Audio Keystation 49e, I have the same issue. It won't work or be recognized in adui/midi setup. It is there, just greyed out. I have searched everywhere for a fix. All you find is delete this, delete that. It worked fine on Mountain Lion, now it is useless to me. I have tried running it through a hub, doesn't fix the issue. I use power as opposed to just the USB, doesn't fix the issue. Can someone please point us in the right direction so we don't have to go spend more money on a midi keyboard because of Mavericks?

Firewire input interface not recognized by GB

The external interface I am using for my microphone input appears in System Preferences. The microphone works with ichat. In GB, however, the only input that appears in the GB preferences is built-in mic. Suggestions?

Thank You.
Completely escaped my attention thanks to some devilishly clever packaging by MOTU.
Cheers

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.

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.

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-USB-B device not recognized by Windows XP

I am using an HP Compaq nx9010 notebook with Windows XP Pro. When I plug in the the GPIB-USB-B, I get an error message telling me that 'The Device has not been Recognized'. I hjave followed all the instructions and have updated the bios and drivers of the notebook, but to no avail. I have uninstalled and reinstaleld the drivers several times to no effect. I have also tried running the device on an older Windows 98 PC, but the interface is not recognized there either! Is it broken?

Hi Andrew,
It's Pete from NIUK Tech. support department here. From what you've described it does sound like there may be something wrong with your product.
Firstly, I would just like to make a couple of checks to make sure. If it is broken, we can then organise for it to be repaired/replaced.
1. Has the GPIB-USB-B ever been working. i.e. how long have you had it, was it working when you got and has since stopped working or has it never worked.
2. Are you plugging in the GPIB-USB-B before the computer is switched on. This shouldn't actually matter as it is a plug and play device. It would just be useful to know if it works when you switch the computer on with the device plugged in.
3. I know you've tried it on a couple of computers with differen
t operating systems, have you also tried different USB plug and play devices on the same USB port as your plugging this device into.
These questions are just to cover all the bases before we send it back to the factory for repair. If we do need to RMA the device then I will need to speak to you in person to get some more details. If and when this is needed, it would probably be easier for you to either give me your e-mail address or phone into the department and ask for me.
Anyway, if you get back to me with the answers to these questions then we can carry on from there.
Best regards,
Peter H
Applications Engineer.
National Instruments.

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!

My older iPod is not recognized by cars with a newer iPod interface

And my new iPod Classic is not recognized by cars with the older interface.
I purchased a new iPod when I realized my new car wouldn't wouldn't recognize my older iPod. Now I find my two older cars won't recognize the new device. Is there an interface cable adapter out there anywhere?

The Jaguar there is nothing you can do, and the new interface from the dealer are not compatible
For the BMW, you have to find out what brand interface was installed in the vehicle
can be dension or original BMW in the x5, if dension you can get something call
Scosche passPORT if BMW brand you can get a new cable from Bmw with the usb and dual power supply,
In the Mini if DIce brand you will need a new cable or new iPod interface, now they have a usb plug to do updates in case iPhone 5 is release in the future or any other updates from iTunes
http://www.oemautosound.com/pc-457-164-dice-i-bmw-t5v-mini-cooper-2002-2008-to-i pod-text-ready.aspx

Instrument not recognized - computer too fast for AT-GPIB/TNT board

I have a problem with a potentiostat (PAR 283) connected to ISA AT-GPIB/TNT (not pnp) board. I recently upgraded to a motherboard with 1.8GHz AMD processor. Potentiostat is recognized by other software as "28PD", "28PE" or sometimes just some garbage characters, instead of "283". I'm using driver version 1.6 (1.7 could not recognize the board). In "Measurement&Automation" potentiostat doesn't respond to *IDN? query (error EAB0). FRA analyzer connected to the same board is recognized without a problem. None of the Windows programs can control potentiostat (it's not recognized as "283). One DOS program, however, is able to recognize and control the potentiostat. I tested the whole system with 166MHz compu
ter, and everything worked fine.
My operating system is Win98
Does anyone have idea what could solve the problem?
Thanks
Darko

I don't necessarily have an answer to your problem, but I want to assure you those usually these problems are with the instrument. The IEEE 488.1 standard defines a 3-wire interlocked handshake to prevent any problems due to computer/device speeds.
However, some devices violate this protocol. They rely on internal timing to determine when things should occur on the bus. For example, the talker asserts the DAV hardware line to indicate that data is valid on the bus. Following that, the listener is supposed to latch the data from the bus and then assert NDAC to indicate that it has taken the data from the bus. At the moment that NDAC has been asserted, the talker is allowed to modify the data lines since they have already been latched. However, some devices have noted in the past that their is usually X amount of time that passes from when NDAC is asserted until the data is removed from the wire. In order to improve peformance, they actually assert NDAC sometime before the data has been latched, assuming that the data will be there when they are actually ready to receive this data. In the case of moving to a faster computer, this data is actually staying on the bus for a shorter period of time than expected and the device receives garbage data.
A similar phenomenon can occur when the device is the talker where is violates the proper 3-wire handshake.
Note that not all failures are intential on the side of the device, it could be a legitimate bug.
Now that I have given a somewhat long-winded description of how problems like this can manifest, I can give you a few recommendations.
1) Obtain a GPIB bus analyzer and examine the handshake sequence to determine where the failure is.
2) Talk to the equipment manufacturer to see if they have any updates
3) Modify the bus timing in NI-488.2 from 500ns to 2ms. This is not likely to work since you are on the receiving end.
4) Try to procure a GPIB-PCII/IIA board. This is a slower board that overall responds to handshaking slower than the AT-GPIB/TNT board and may mask the problem.
5) Increase your cable length (including to "illegal" lengths such as 8m). This can add propegation delays that can mask this problem. I have seen work in teh past with troubled instruments.
Good luck.

Yamaha p200+motu fastlane midi interface=GB not recognizing midi device =0(

tried hooking up my motu fastlane midi interface to my yamaha p200 and to my mac mini for use in garageband. GB is not recognizing a midi interface. i read elsewhere that i may need a driver, but would it be for the yamaha p200 (keyboard) or the motu fastlane midi interface? or is it a driver for garageband??
please help!!

You need Motu's midi driver...Go to their site for the current version...in the Downloads section.
You will need to log-in or register if you haven't already.
Once installed and restarted you need to set up your midi connection in Apple's: Audio Midi Setup utility and connect the Fastlane to the Yamaha...
Link here if helpful:
http://www.showmeprotools.com/apple-ams-audio-midi-setup-for-pro-tools/
Just imagine the Pro-Tools interface is the Fastlane...
Typically the manufacturer model and names are no longer supplied in the Properties window. You can enter whatever names you want in that section. It doesn't matter. So don't worry if it's blank or not as shown in the link.
If you want to use the internal sounds of the P200 then you will need to use the analog output connections from the P200 into the analog inputs of an audio interface...using a real instrument track.

Gpib-enet v1.3 does not work under Solaris 8

Recently I have updated my Sparc-workstation from solaris 7 to Solaris 8. I have installed GPIB-ENET version 1.3. Wenn I started ibic->ibfind gpib1, an error ENEB appeared. The gpib even did not respond to ping. After reset the gpib, it can respond to ping, but the ibic did not work.

Referring to http://www.ni.com/support/gpib/versions.htm#sun you need the driver version 1.4

After installing 11.2.2.3 iPod Classc. is wiped/"dead" (not recognized by iTunes, Win7 find the unit in explorer) and my iPod Touch refuse to comm with iPod interface in the car. Just wait for a iTunes update?

Hi,
I installed 11.2.2.3 2 days ago and have since then not been able to sync my iPod Classic (not recognized by iTunes anymore and alll data has been wiped but show up in Win explorer when in Disk mode with my label on it "Nik's iPod") my old iPod Touch appear to have all data left but doesn't communicate with my car anymore.
Nedless to say none of the other Apple devices in our house will be updated or connected until this is resolved.
Is this related to the iTunes update?
If so should I just wait for a new update to come out that can help me get these things sorted?
I have tried most of the different remedies listed in this forum to no avail and being computer illiterate (not comepletely but anyway) I just want to know if this is a known problem that I can successfully fix with a bit of fiddling or if its time to seek out a genius bar somewhere and get some help.
Nik

Hi Jeff,
Thanks for the help but I am unfortunately still not able to get my iPod Classic to connect. I have tried all the tricks in the article that you linked to.
One thing is that when I reset the iPod (menu and center until the logo pops up) I get a critical error in iTunes and it shuts down. Could that indicate that my problem is with the iTunes installation rather than the iPod?
I have tried to re-install iTunes before but maybe I shpuld give it a go again?
Brgds,
Nik

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

GPIB ENET Interface not recognized

Similar Messages

Maybe you are looking for