Experimental Physics and
Industrial Control System
| 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 | 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 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | IP520 not communcating with baud rates other than 9600bps |
| From: | Mrinal Bera via Tech-talk <tech-talk at aps.anl.gov> |
| To: | Tech-talk <tech-talk at aps.anl.gov> |
| Cc: | Daniel Henry Solz Kerr <danielhskerr at uchicago.edu> |
| Date: | Thu, 21 Dec 2023 19:39:03 +0000 |
|
Dear All,
I would like to bring to your attention some issues that we are facing while setting up IP520 with AVME 9600 for serial ports with
1) vxWorks 6.9.4.1 2) EPICS 7.0.7
3) asyn-R4-42
4) ipac-2-16
5) ip-R2-21-1
6) compiled on the host running CentOS Stream 9
Here is the part of the startup script we used to set the serial with IP520:
ipacAddAvme96XX("0x0800,4 R”)
IP520Drv(1) IP520ModuleInit("UART1", "232", 0x81, 1, 0) IP520DevCreate("serial9", "UART1", 0, 512, 512) drvAsynSerialPortConfigure("serial9","serial9",0,0,0) asynSetOption("serial9", -1, "baud", "9600") asynSetOption("serial9", -1, "bits", 8) asynSetOption("serial9", -1, "parity", "none") asynSetOption("serial9", -1, "stop", "1") asynSetOption("serial9", -1, "clocal", "Y") asynSetOption("serial9", -1, "crtscts", "N") asynOctetSetInputEos("serial9", -1, "\r") asynOctetSetOutputEos("serial9", -1, "\r”) With the above settings, everything works fine in terms of communicating with the serial port both with loopback and with any device. Then we found that if we change the baud rate setting of the serial port in any of the following ways the communication stopped working: 1) Change the baud rate settings through asynRecord.adl after booting vxWorks with 9600bps as shown in the settings above. 2) Boot vxWorks with a baud rate setting of the serial port other than 9600bps. The only way to make the serial port work again is to reboot the vxWorks with the baud rate of 9600pbs. We tried to look at the signal from IP520 using an oscilloscope and we found that the signal out of IP520 changes normally as the baud rates are changed. Hence, we suspect that the problem is with the reading of the signals by IP520 when set up with baud rates other than 9600bps. Did anybody try other baud rates than 9600bps with IP520? Thanks and regards, Mrinal Mrinal Kanti Bera, PhD
Beamline Scientist & Research Associate Professor NSF’s ChemMatCARS, Pritzker School of Molecular Engineering University of Chicago 9700 S Cass Ave Bldg 434D Argonne, IL-60439 United States Phone: +1-630-252-0472 |
- Navigate by Date:
- Prev: Re: asyn ioctestIPServer prints many accept errors after IOC exit? J. Lewis Muir via Tech-talk
- Next: Re: Steps for installing any EPICS Device Support module Eusebio Naif Al-Soliman Fuentes via Tech-talk
- 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
- Navigate by Thread:
- Prev: Re: asyn ioctestIPServer prints many accept errors after IOC exit? J. Lewis Muir via Tech-talk
- Next: StreamDevice+regex for escaping and unescaping HEX messages Sebastian Eckert via Tech-talk
- 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
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·