GPIB-ENET/100 lockup... how to Reset

[JeanPierre]

I can reinstall the NI-drivers but when the GPIB-ENET/100 lockups, there are problems from both my computer and the computer on which the application runs. For the moment, the GPIB-ENET/100 is working properly, I'll wait for the next failure... "RPM4" is an alias for "GPIB0::10::INSTR" GPIB0 obviously being the GPIB-ENET/100
Thanks for your time investigating this issue.

Message Edité par JeanPierre le 05-18-2006 08:35 AM

[Chris_R.]

Hello,
Okay, please repost if this happens again.  I am hoping a reinstall of the drivers will fix something that is going wrong here, but at least it is working for now. 

Have a great day!

Chris R.

[JeanPierre]

I have reinstalled NI-488 2.4.2 drivers.  In the attached capture file you'll see I started NI-MAX then the Troubleshooting Wizard and then "Find Instruments". Both locked on the ibfind(GPIB0) but this time the calls returned after few minutes with a driver error. I can't swear I waited that long on previous trials before aborting the application(s).

I powered cycle the GPIB-ENET/100 and then the Troubleshooting Wizard test was successful. "Find Instruments" failed at first attemp but succeeded at second.

[Chris_R.]

Hi JeanPierre,

This actually sounds like a network issue.  If you want to do a network capture with a program that monitors the network traffic, I can take a look at it and see if I can see anything that may be causing this.  One commonly used network analyzer is called Etherreal.  Although you are able to ping your device, my guess is that if you were to ping it right around the time of the error, the ping would fail as well.  This suggests that the network connectivity is at fault.  So, if you do want to do a network capture, please post it here and I will take a look at it for you.

Have a great day!

[JeanPierre]

Hi Chris,

here is a capture of relevant packets using Etherreal. My PC is 192.168.0.2 and ENET/100 is 192.168.0.155

I did a ping and a Scan for Instrument from MAX. MAX returned immediatly with an error on ibfind(gpib0)) that the device was not properly configured.

[Chris_R.]

Hi JeanPierre,

I looked at the network capture and unfortunately, I can't tell much of what may be going wrong.  One thing you can try it to use a dedicated network to troubleshoot it.  You can do this by using a ethernet crossover cable to directly attach the GPIB-ENET/100 to your PC.  If this causes the ENET/100 to work properly, then there is probably a network problem that needs to be addressed.  If you see the same behavior here too, you can then do another network capture so the two can be compared to each other to see what may be causing this.  Try this out and let me know how it goes.

Have a great day!