AnsweredAssumed Answered

FW: vrf Serial problem

Question asked by VRFuser on Sep 13, 2005
Latest reply on Sep 13, 2005 by VRFuser
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML><HEAD><TITLE>Message</TITLE><META http-equiv=Content-Type content="text/html; charset=us-ascii"><META content="MSHTML 6.00.2800.1505" name=GENERATOR></HEAD><BODY><DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2></FONT> </DIV><SPAN class=168114022-13092005></SPAN><FONT face=Arial><FONT color=#0000ff><FONT size=2>Appologies if you get this twice.  I never saw it come across.  Dave<SPAN class=168114022-13092005></SPAN></FONT></FONT></FONT><BR><DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><HR tabIndex=-1><FONT face=Tahoma size=2><B>From:</B> Andersen, Dave-P26278 <BR><B>Sent:</B> Tuesday, September 13, 2005 2:40 PM<BR><B>To:</B> 'Findley, Robin'; VRF<BR><B>Subject:</B> RE: [vrf] Serial problem<BR></FONT><BR></DIV><DIV></DIV><DIV dir=ltr align=left><SPAN class=202302921-13092005><FONT face=Arial color=#0000ff size=2>Well, unless the device was sending garbage or I have a very noisy line, one app I was using was a transmit only one-way communication setup.  This was a homemade device using a PIC controller.  A bus monitor never showed anything returning.</FONT></SPAN></DIV><DIV dir=ltr align=left><SPAN class=202302921-13092005><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV><DIV dir=ltr align=left><SPAN class=202302921-13092005><FONT face=Arial color=#0000ff size=2>Dave</FONT></SPAN></DIV><BR><DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><HR tabIndex=-1><FONT face=Tahoma size=2><B>From:</B> Findley, Robin [mailto:rfindley@harris.com] <BR><B>Sent:</B> Tuesday, September 13, 2005 2:04 PM<BR><B>To:</B> VRF<BR><B>Subject:</B> RE: [vrf] Serial problem<BR></FONT><BR></DIV><DIV></DIV><DIV><SPAN class=743485120-13092005><FONT face=Arial color=#0000ff size=2>Dan,</FONT></SPAN></DIV><DIV><SPAN class=743485120-13092005><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV><DIV><SPAN class=743485120-13092005><FONT face=Arial color=#0000ff size=2>Maybe you are onto something...  I never had problems with VEE's serial interface until I started communicating with a device that continually dumps data.  My most recent project involves one such piece of equipment, and VEE has been giving me the same SICL timeout error.  Since I was unable to solve the problem, I started using MsComm instead, and haven't had any problems since.</FONT></SPAN></DIV><DIV><SPAN class=743485120-13092005><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV><DIV><SPAN class=743485120-13092005><FONT face=Arial color=#0000ff size=2>Has anyone had this error while using equipment that _doesn't_ fill the receive buffer?</FONT></SPAN></DIV><DIV><SPAN class=743485120-13092005><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV><DIV><SPAN class=743485120-13092005><FONT face=Arial color=#0000ff size=2>-Robin</FONT></SPAN></DIV><BLOCKQUOTE style="MARGIN-RIGHT: 0px">  <DIV></DIV>  <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT   face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Williams, Dan   [mailto:Dan.Williams@analog.com] <BR><B>Sent:</B> Tuesday, September 13, 2005   12:25 PM<BR><B>To:</B> VRF<BR><B>Subject:</B> RE: [vrf] Serial   problem<BR><BR></FONT></DIV>  <DIV><SPAN class=292401017-13092005><FONT face=Arial color=#0000ff size=2>I   don't know if it's of any use but in programming an RS232 to I2c interface I   had a year of intermittent problems. What I eventually discovered was the VEE   routines written for the interface by a co-op were allowing garbage data to   build up in the buffer of the interface so most of the time it would work well   and once in a while the timing of input/output would be off and the buffer   would send out data generated by a previous error condition. I fixed it   by writing a routine that at the beginning of an operation continuously   reads from the buffer and releases when the end of buffer error is   generated ensuring no left over data to bung up the works. Since I do   characterization the time penalty for doing this is minimal. You production   guys will feel otherwise I'm sure.</FONT></SPAN></DIV>  <DIV><SPAN class=292401017-13092005><FONT face=Arial color=#0000ff   size=2></FONT></SPAN> </DIV>  <DIV><SPAN class=292401017-13092005><FONT face=Arial color=#0000ff size=2>This   should have been easy to figure out but it's intermittent nature made it a   bear to find.</FONT></SPAN></DIV>  <DIV><SPAN class=292401017-13092005><FONT face=Arial color=#0000ff   size=2></FONT></SPAN> </DIV>  <DIV><SPAN class=292401017-13092005><FONT face=Arial color=#0000ff size=2>Dan   Williams</FONT></SPAN></DIV>  <DIV><SPAN class=292401017-13092005><FONT face=Arial color=#0000ff   size=2>Analog Devices </FONT></SPAN></DIV>  <DIV><SPAN class=292401017-13092005><FONT face=Arial color=#0000ff size=2>High   Speed Networking</FONT></SPAN></DIV>  <BLOCKQUOTE style="MARGIN-RIGHT: 0px">    <DIV></DIV>    <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT     face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> George Tyrrell     [mailto:tdllc01@earthlink.net] <BR><B>Sent:</B> Tuesday, September 13, 2005     12:52 PM<BR><B>To:</B> VRF<BR><B>Subject:</B> RE: [vrf] Serial     problem<BR><BR></FONT></DIV>    <DIV>I have 4 WinNT 4.0 workstations with all the latest updates running VEE     5.01.  All of the workstations are networked to common shared     resources.  I send data out of the serial port to a B&B RS-232 to     CAN converter for DeviceNet support.</DIV>    <DIV> </DIV>    <DIV>Only one of these workstations displays this problem.       Restarting VEE does not help.  Rebooting does not help.      Disconnecting the network does not help.   Changing to another CAN     converter does not help.  Upgrading the IO libraries version does not     help.  Changing to the other internal COM port works briefly.</DIV>    <DIV> </DIV>    <DIV>What DOES work is to disconnect the RS-232 port from the B&B     converter, then send out serial data and attempt to receive serial data from     that open port.  This deliberately generates another error.  </DIV>    <DIV> </DIV>    <DIV>Following the deliberate error, communication through the serial port     is restored until the same error occurs again, usually a week later.      My technicians have instructions on how to reset using this technique.</DIV>    <DIV> </DIV>    <DIV>I don't understand why only one of my computers has this problem.      They are all of the same manufacturer (HP), configured the same way.      Apparently this problem is still lurking in the background, and is OS     independent.  But is it still in the later VEE revisions?  I'm     suspecting that it may be hardware timing dependent.</DIV>    <DIV> </DIV>    <DIV>George Tyrrell</DIV>    <DIV>TestDynamics LLC</DIV>    <DIV>Thornton, Colorado<BR><BR><BR>-----Original Message----- <BR>From:     "Andersen, Dave-P26278" <DAVE.ANDERSEN@GDC4S.COM><BR>Sent: Sep 13, 2005     10:17 AM <BR>To: VRF <VRF@AGILENT.COM><BR>Subject: RE: [vrf] Serial problem     <BR><BR></DIV><ZZZHTML><ZZZHEAD><ZZZMETA     content="text/html; charset=us-ascii" http-equiv="Content-Type"><ZZZMETA     content="MSHTML 6.00.2800.1505" name="GENERATOR"></ZZZHEAD><ZZZBODY>    <DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN     class=604280616-13092005>I have run into this problem also and I do not have     any other program running and am using a real com port.  In fact, I can     run the program, stop it (with an execute close), and when I restart I get     the message.  Could this be an XP issue?  I don't recall this     problem before running XP.</SPAN></FONT></DIV>    <DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN     class=604280616-13092005></SPAN></FONT> </DIV>    <DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN     class=604280616-13092005>Dave</SPAN></FONT></DIV>    <DIV><BR></DIV>    <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>    <HR tabIndex=-1>    <FONT face=Tahoma size=2><B>From:</B> g.nied@gn-software.de     [mailto:g.nied@gn-software.de] <BR><B>Sent:</B> Monday, September 12, 2005     2:53 AM<BR><B>To:</B> VRF<BR><B>Subject:</B> Re: [vrf] Serial     problem<BR></FONT><BR></DIV>    <DIV></DIV>    <DIV style="FONT: 10pt Courier New; COLOR: #000000">Tim,</DIV>    <DIV style="FONT: 10pt Courier New; COLOR: #000000"> </DIV>    <DIV style="FONT: 10pt Courier New; COLOR: #000000">the error message is     leading you to the wrong direction. It only means that VEE cannot     communicate with the port through the SICL library.</DIV>    <DIV style="FONT: 10pt Courier New; COLOR: #000000">So the problem might     be:</DIV>    <DIV style="FONT: 10pt Courier New; COLOR: #000000">- another program took     control over that specific serial port and did not close it</DIV>    <DIV style="FONT: 10pt Courier New; COLOR: #000000">- if the serial port is     only a virtual one (USB) and the USB connection was disturbed</DIV>    <DIV style="FONT: 10pt Courier New; COLOR: #000000">In those cases a restart     of VEE might be the solution, because SICl checks for the ports only     once at VEE start.</DIV>    <DIV style="FONT: 10pt Courier New; COLOR: #000000"> </DIV>    <DIV style="FONT: 10pt Courier New; COLOR: #000000">I hope that helps a     bit,</DIV>    <DIV style="FONT: 10pt Courier New; COLOR: #000000"> </DIV>    <DIV style="FONT: 10pt Courier New; COLOR: #000000">    <DIV>    <DIV> </DIV>    <DIV>best regards,</DIV>    <DIV> </DIV>    <DIV>Georg</DIV>    <DIV> </DIV>    <DIV> </DIV>    <DIV><IMG src="cid:604280616@13092005-03BF"></DIV>    <DIV><FONT face="Century Gothic">Georg     Nied · Software-Development · Hansestr.     7 · 51149 Cologne · Germany</FONT></DIV>    <DIV><FONT face="Century Gothic">Tel: +49 (2203) 9770915 · Fax: +49 (2203)     9770924 · E-Mail: </FONT><A href="mailto:info@gn-software.de"><FONT     face="Century Gothic">info@gn-software.de</FONT></A></DIV></DIV></DIV>    <DIV style="FONT: 10pt Courier New; COLOR: #000000"> </DIV>    <BLOCKQUOTE     style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">      <TABLE id=tobit_repfor       style="BORDER-RIGHT: #e0e0e0 1px solid; BORDER-TOP: #e0e0e0 1px solid; FONT: 10pt Arial; BORDER-LEFT: #e0e0e0 1px solid; COLOR: black; BORDER-BOTTOM: 0px"       cellSpacing=0 cols=3 cellPadding=0 width="99%" border=0>        <TBODY>        <TR borderColor=#dfdfdf borderColorLight=#dfdfdf bgColor=#dfdfdf>          <TD           style="PADDING-LEFT: 4px; PADDING-BOTTOM: 1px; PADDING-TOP: 1px; BORDER-BOTTOM: #ffffff 1px solid"           width=140 colSpan=2 height=22>            <DIV style="FONT: bold 9pt Arial">Original             Message     </DIV></TD>          <TD style="BORDER-BOTTOM: #ffffff 1px solid" align=right>            <DIV style="FONT: 8pt Arial">            <DIV style="FONT: 8pt Arial"><STRONG><FONT             color=#808080>   processed by David             InfoCenter</FONT></STRONG> </DIV></DIV></TD></TR></TBODY></TABLE>      <TABLE id=tobit_repfor2       style="BORDER-RIGHT: #e0e0e0 1px solid; BORDER-TOP: 0px; FONT: 8pt Tahoma; BORDER-LEFT: #e0e0e0 1px solid; COLOR: black; BORDER-BOTTOM: #e0e0e0 1px solid"       cellSpacing=0 cols=2 cellPadding=0 width="99%" border=0>        <TBODY>        <TR style="PADDING-BOTTOM: 2px">          <TD style="PADDING-LEFT: 6px; BORDER-BOTTOM: #ffffff 1px solid"           width=68 bgColor=#efefef height=18>            <DIV style="FONT: 8pt Tahoma">Subject: </DIV></TD>          <TD style="PADDING-LEFT: 4px; BORDER-BOTTOM: #efefef 1px solid"           bgColor=#ffffff>            <DIV style="FONT: 8pt Tahoma">[vrf] Serial problem (09-Sep-2005             16:08)</DIV></TD></TR>        <TR style="PADDING-BOTTOM: 2px">          <TD style="PADDING-LEFT: 6px; BORDER-BOTTOM: #ffffff 1px solid"           width=68 bgColor=#efefef height=18>            <DIV style="FONT: 8pt Tahoma">From:    </DIV></TD>          <TD style="PADDING-LEFT: 4px; BORDER-BOTTOM: #efefef 1px solid"           bgColor=#ffffff>            <DIV style="FONT: 8pt Tahoma"><A             href="mailto:Tim.Fisher@gdc4s.com">Tim.Fisher@gdc4s.com</A></DIV></TD></TR>        <TR style="PADDING-BOTTOM: 0px">          <TD style="PADDING-LEFT: 6px" width=68 bgColor=#efefef height=17>            <DIV             style="FONT: 8pt Tahoma">To:      </DIV></TD>          <TD style="PADDING-LEFT: 4px" bgColor=#ffffff>            <DIV style="FONT: 8pt Tahoma"><A             href="mailto:vrf@agilent.com">vrf@agilent.com</A></DIV></TD></TR></TBODY></TABLE>      <DIV> </DIV><ZZZ!-- -- format rtf text from Converted>      <P><FONT face=Arial size=2>Hello all,</FONT> </P>      <P><FONT face=Arial size=2>I am receiving a serial error which I'm sure       has come up before for others, so maybe I can get some advice.  I am       receiving a VEE Run Time Error</FONT></P>      <P><FONT face=Arial color=#ff0000 size=2>I/O error or timeout occurred       SICL call made with bad parameter</FONT> </P>      <P><FONT face=Arial color=#ff0000 size=2>Unable to set receive buffer size       of X bytes</FONT> <BR><FONT face=Arial color=#ff0000 size=2>In transaction       number 1</FONT> </P>      <P><FONT face=Arial size=2>I have tried a wide range of values for the       receive buffer (X = 32 to 8192)</FONT> <BR><FONT face=Arial size=2>But       none of the values have worked.  Also the problem only seems to occur       when the remote host is connected to a shared network.</FONT></P>      <P><FONT face=Arial size=2>Any help would be appreciated.</FONT> </P>      <P><FONT face=Arial size=2>Thanks,</FONT> <BR><FONT face=Arial size=2>Tim       Fisher</FONT> </P></BLOCKQUOTE></ZZZBODY></ZZZHTML>--- You are currently     subscribed to vrf as: Dan.Williams@analog.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". Search the     "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".   </BLOCKQUOTE><BR>--- <BR>You are currently subscribed to vrf as:   rfindley@harris.com <BR>To subscribe send a blank email to   "join-vrf@it.lists.it.agilent.com". <BR>To unsubscribe send a blank email to   "leave-vrf@it.lists.it.agilent.com". <BR>To send messages to this mailing   list, email "vrf@agilent.com". <BR>If you need help with the mailing list send   a message to "owner-vrf@it.lists.it.agilent.com". <BR>Search the "unofficial   vrf archive" at "www.oswegosw.com/vrf_archive/". </BLOCKQUOTE><BR>--- <BR>You are currently subscribed to vrf as: Dave.Andersen@gdc4s.com <BR>To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com". <BR>To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com". <BR>To send messages to this mailing list, email "vrf@agilent.com". <BR>If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com". <BR>Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/". <BR>---<BR>You are currently subscribed to vrf as: rsb@soco.agilent.com<BR>To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".<BR>To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".<BR>To send messages to this mailing list,  email "vrf@agilent.com".  <BR>If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".<BR>Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".</BODY></HTML>  

Outcomes