EPICS Controls Argonne National Laboratory

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  <20232024  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  <20232024 
<== Date ==> <== Thread ==>

Subject: Moxa terminal server question
From: Kuldeep Joshi via Tech-talk <tech-talk at aps.anl.gov>
To: tech-talk at aps.anl.gov
Date: Fri, 17 Feb 2023 10:02:33 +0000
Hello Mark,
I have faced a similar problem, however in my case I am using a Tibbo device, and the TCP connection was being closed due to inactivity. I suspect it is a VSPDL driver issue, and did not have the bandwidth to get into it.Ultimately I programmed the controller to operate on Modbus TCP and worked around the problem.
I feel in your case looking into the Moxa driver would help.

Regards,
Kuldeep

I have an Allen-Bradley SLC5/03 PLC.  I use an RS-232 connection from a Windows PC to the PLC for programming it.  This works fine when I connect to a real serial port on the PC.  However, that is inconvenient because that is over 50 meters from the PC, and I have 2 PLCs and only 1 serial port, so I need an A/B switch.  I would like to use a multi-port Moxa terminal server instead.  I have installed the Moxa software on the PC that makes COM2 appear as a Windows COM port, using one of the serial ports on the terminal server.

I then try to configure the Allen-Bradley RSLinux software to use COM2 with their DF1 protocol using the "Auto-Configure" option.  This "almost" works.  If I disconnect the serial cable from the Moxa to the PLC and run Auto-Configure it fails to find the matching baud rate and parity.  This is expected of course, since it is not communicating at all.  If I connect the cable it does correctly find the baud rate and parity, so it is communicating OK.  However it then reports "Failed to dine error checking mode!".  There are 2 choices for error checking, BCC, and CRC.  Both fail.

I don't understand this, since I think the BCC and CRC are both done in software on the PC end.   If the Moxa is providing sufficient emulation of a COM port to allow the baud rate and parity to be configured OK, why it is failing to configure the error checking?

Any ideas are welcome!

Thanks,
Mark

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.aps.anl.gov/pipermail/tech-talk/attachments/20230216/5e756718/attachment.html>

------------------------------

Subject: Digest Footer

_______________________________________________
Tech-talk mailing list Tech-talk at aps.anl.gov
https://mailman.aps.anl.gov/mailman/listinfo/tech-talk


------------------------------

End of Tech-talk Digest, Vol 17, Issue 90
*****************************************

Navigate by Date:
Prev: Moxa Terminal Server question Koennecke Mark via Tech-talk
Next: RE: Moxa Terminal Server question Mark Rivers 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  <20232024 
Navigate by Thread:
Prev: RE: Moxa Terminal Server question Mark Rivers via Tech-talk
Next: node-epics-ca: A Channel Access client for Node.js (FFI implementation) Wang, Lin 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  <20232024 
ANJ, 20 Feb 2023 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·