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: | Handling Ethernet-to-Serial Connection when vendor SDK expects tty device |
From: | "Wlodek, Jakub via Tech-talk" <tech-talk at aps.anl.gov> |
To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Tue, 6 Apr 2021 13:34:28 +0000 |
Good morning EPICS community,
I had the following question regarding one of the devices that I am currently working on supporting. Essentially, I am using an asynPortDriver
based driver integrated with the device vendor SDK. The vendor SDK has a connection function that expects a string representing either identification
for the USB device to communicate over the USB bus (this I have working fine), or a TTY serial device for communicating over serial (ex. /dev/ttyS0, COM1 on Windows).
When connected directly to the serial port of the target machine, the device connects and this works OK.
However, ideally, we would prefer to use a MOXA ethernet-to-serial adapter to talk to the device, and I am not sure what the best approach for this is. Traditionally,
for say a StreamDevice IOC I would use drvAsynIPPortConfigure(), and then configure the MOXA to communicate via serial on the other end, but given that
the device needs a serial device to connect, I wasn't sure how to handle that. I know there is external software I could use to create a virtual serial device from
an ethernet connection, but is there a way to do this from within EPICS?
Thanks,
Jakub
|