1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 <2009> 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 <2009> 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | RE: asyn problem |
From: | "Mark Rivers" <[email protected]> |
To: | "tanushyam bhattacharjee" <[email protected]>, <[email protected]> |
Date: | Thu, 12 Nov 2009 10:12:31 -0600 |
When it stops working, what do you see? Here are some things to try: - When it stops working, issue the following command: asynReport 10,“L16” This asks for a detailed report on the state of that asyn
port. Next, issue the following commands: asynSetTraceIOMask “L16”,0,2 That enables TraceEscape output, printing ASCII plus escape
sequences. asynSetTraceMask “L16”,0,255 That turns on all trace output for your asyn port on address
0. If you are using other addresses you might need to issue commands like: asynSetTraceMask “L16”,2,255 for address 2, etc. This should tell you if you are getting disconnected from
the terminal server (TCP/IP disconnect) or if the device is sending garbage,
etc. Mark From:
[email protected] [mailto:[email protected]] On Behalf Of tanushyam bhattacharjee
Keep up with people you care about with Yahoo! India Mail. Learn how. |