09-26-2007 05:59 PM
09-27-2007 10:28 AM
09-27-2007 10:49 AM
Hi Meghan,
The problem with your suggestion is that my customer considers this issue to be my problem, not his. Our products are very expensive, so telling him to go work the problem himself is not an option. In fact, we are trying to find out what bus extender he is using so that we can buy one and attempt to duplicate the problem.
The only thing that comes to mind with this issue is a timing problem. I believe that all timing parameters in the TNT4882 are at their default values. Is there anything related to timing that you suggest I investigate?
Regards,
Steve
09-28-2007 10:25 AM
10-01-2007 02:22 PM
SteveW
The best thing to do would be to get a GPIB analyzer capture on both sides of the extender. I'm sure that the problem doesn't happen with a simple program (*idn? in a while loop), but you should check the simple programs first. Make sure that you enable timing, handshaking, and control lines so that we can tell anytime the bus changes. I agree with Meghan that this could be better over email.
Thanks,
Steven T.
10-01-2007 03:57 PM
Hi Steven,
Our customer is shipping us both our equipment and the bus entender they are using. It will take a week or two, as it was installed outside the US. Supposedly it will not even respond to a *idn?. As soon as we get the equipment, we will test it and if the problem is not obvious, will request assistance via e-mail. Thanks to all for your responses.
Regards,
Steve