GPIB-USB-HS power failure error

[zerotolerance]

I keep getting the power failure error for the gpib-usb hs. We have 5 of these converters, and all 5 seem to have the same issue.

There was another thread reported for this issue but I can longer find it.

This power failure is only occurring when continuous polling SPOLL in intervals of 8 ms or less is used. If I have the SPOLL interval to occur every 10 ms than the issue disappears, but as soon as the card is made to work faster than 10 ms than the issue persist. I have to then close everything and restart the labview in order to continue. I've updated to the latest drivers, switched computers, switched the cards (all 5 of them) and the same problem is still there. Since I now keep my communications with the GPIB instrument within this 10 ms rule, the program is working. But I can only think that this must be a hardware glitch. This sounds like the lack of power going to GPIB card when continuously used. I don't know the PC specs ( I can find out), but since this is repeated in multiple PC's (that are newly issued and don't have the same specs.) I'm blaming the USB-GPIB card design problem.  

Can anyone else confirm this?

[JasonSmith]

Can you provide any more information about exactly what you are doing to generate the failure? I threw together a few different VIs to try to approximate your use-case, but none of the fail on my system.

Some questions that would help understand the issue better:

1. What model of instrument are you serial polling?

2. Have you only tried this with a single type of instrument, or can you reproduce it with different instrument models as well?

3. Which operating system and NI-488.2 version are you using?

4. Are the computers where you see failures laptops or desktops?

5. How long does it take to reproduce the failure? Are you present to see it fail, or you see the failure when you come back later?

6. Can you provide a capture of the error from NI I/O Trace?

7. Can you provide a very simple VI which can reproduce the failure without any special equipment requirements?

Thanks,

Jason Smith

[zerotolerance]

Thanks Jason for your reply.

1. I'm polling an Orbit FR multi axes controller with built in PCU (attached manual).

2. I've only done this with the above instrument. Havn't tried it with other instruments. But I can try with the other.

3. Operating system is  Windows 7. As for the NI-488.2 version, I have updated it to the latest version 2 weeks ago. But I can give you the number when I'm in the Lab again.

4. All the computers I've tried were Desktop PC and not failures. The were bought new specifically for our department less than 1 month ago.

5. If less than 5 ms was used for SPOLL, than the error occours within seconds.

6. I can, again not untill I go to the Lab. Tomorrow I suspect I can get this info.

7. Attached is the simple VI that generates this error.

Thanks

Kas

[zerotolerance]

The NI-488.2 I currently am using is -  Windows 7/Vista/XP/2000 778927-01. I believe this is the latest version.

I have also tried it with other instruments, i.e. VNA, PNA etc. and while the error is reduced (i.e. happens once every 5 mins or so) it isn't completely gone.

Regards

Kas

[Ali_Bailey]

Hi Kas,

This is Alistair, we spoke over the phone yesterday.

I have been trying to replicate the issue without success I am afraid.  I have a couple more things that I am going to try but I was wondering if you can send me a screenshot of the error when you get it to occur please?

Also, with the other instruments, was there still the 10ms 'rule' or were you able to go faster?

[IanS]

Hi Kas,

I'm aware this forum is a little old, but was just wondering if you had any more infomation. If you could provide a screenshot of the error it would be useful for resolving this issue, as Ali said we are unable to replicate the problem here at the moment. Otherwise we will close the issue in a few days time.

[zerotolerance]

Thanks for your reply. I've just recieved a confirmation email from the ORBIT FR manufacturers, and the issue seems to be with the orbit FR controller. The manual states that the controller can handle comunication speed of up to 1 ms. However, the polling mechanism of the hardware seems to be the problem. 

Thanks for your help so far.

Kas

[JÞB]

Zero-

Check the windows power management options for the USB Hubs (From the Device manager.)

The Magic-8 ball says you left them at the default setting of "Let Windows automatically shut down power to this hub to save power."