AnsweredAssumed Answered

vrf Strange 53152A problem

Question asked by VRFuser on Oct 4, 2004

Like • Show 0 Likes0
Comment • 0

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML><HEAD><META http-equiv=Content-Type content="text/html; charset=us-ascii"><META content="MSHTML 6.00.2800.1458" name=GENERATOR></HEAD><BODY><DIV dir=ltr align=left>One question, what's that stuff after the query? </DIV><DIV dir=ltr align=left> </DIV><DIV dir=ltr align=left>Also, once the read is activated, it will wait for the data, however, as already stated, ya don't want to read too fast so a small delay between read and write is needed. Now VEE has another bad habit, memory leaks, esp at the i/o pins. So what you think you get, even errors, is sometimes not what's there, just stuck. I know, I know, how in the H*&*& could that happen. I dunno. I've seen it twice, ask my boss. And when its stuck, it'll stay there until you reboot VEE. I don't see this anymore, 'cause I always separate reads from writes.</DIV><DIV dir=ltr align=left> </DIV><DIV dir=ltr align=left> </DIV><DIV dir=ltr align=left>Rufus</DIV> <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><HR tabIndex=-1>From: Andersen Dave-P26278 [mailto:Dave.Andersen@gdds.com] Sent: Monday, October 04, 2004 3:41 PM To: VRF Subject: [vrf] RE: Strange 53152A problem </DIV><DIV></DIV><DIV>That may be the case, but my rule stems from a problem I had getting a reading (I forget what instrument I was using) and not getting anything consistent until I separated the read from the write. There were no write transactions following the read.</DIV><BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> <DIV class=OutlookMessageHeader dir=ltr align=left>-----Original Message----- From: Les Hammer [mailto:Les.Hammer@CompleteTest.com] Sent: Monday, October 04, 2004 12:29 PM To: Andersen Dave-P26278; VRF Subject: RE: [vrf] RE: Strange 53152A problem </DIV> <DIV>> Yup, I've seen this, too, even on other pieces of equipment. </DIV> <DIV>> In fact, I have made it a "rule" to never have a read transaction in an I/O box with anything else.</DIV> <BLOCKQUOTE> <DIV>> > Try putting the read in a different I/O box. I have see a problem where I have an I/O </DIV> <DIV>> box with a write and read, followed by another I/O box with a write, ...</DIV> <DIV> </DIV> <DIV>The problem there is the write after the read, not the read after the write.</DIV> <DIV>It's an old parser problem.</DIV> <DIV>The first WRITE works ok - instrument responds with data.</DIV> <DIV>READ - takes data from the instrument. The bus is cleared. GPIB tells program it is done. Parser has not yet cleared the instrument's flag.</DIV> <DIV>Program WRITES. Parser bug tells it to check the input buffer (before the output flag clears) - BOOM gets an error because the output buffer flag isn't cleared yet. (Anything in the error queue after the timeout?)</DIV> <DIV> </DIV> <DIV>A 10 ms wait between READ and the next WRITE usually clears that up. </DIV> <DIV> </DIV> <DIV>Les Hammer</DIV></BLOCKQUOTE></BLOCKQUOTE>--- You are currently subscribed to vrf as: rwarren@amti.net To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com". To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com". To send messages to this mailing list, email "vrf@agilent.com". If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com". --- You are currently subscribed to vrf as: rsb@soco.agilent.com To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com". To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com". To send messages to this mailing list, email "vrf@agilent.com". If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".</BODY></HTML>

No one else has this question

vrf Strange 53152A problem

Outcomes

Related Content

Recommended Content