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: .RE: Configuring serial communication with Lakeshore 331 via Moxa (Mark Rivers) |
From: | "Bradnick, Ben \(DLSLtd, RAL, LSCI\) via Tech-talk" <tech-talk at aps.anl.gov> |
To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>, mark.koennecke <mark.koennecke at psi.ch>, Mark Rivers <rivers at cars.uchicago.edu> |
Date: | Thu, 3 Feb 2022 14:46:10 +0000 |
Hi,
We have an EPICS support module that allows us to view and configure the mentioned port parameters of our Moxa and older ACS terminal servers using SNMP and uses autosave to store/restore the configuration.
I could upload it if there's any interest.
Kind regards,
Ben
From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Mark Rivers via Tech-talk <tech-talk at aps.anl.gov>
Sent: 03 February 2022 14:18 To: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>; mark.koennecke <mark.koennecke at psi.ch> Subject: Re: .RE: Configuring serial communication with Lakeshore 331 via Moxa (Mark Rivers)
> And I always configure
the serial port settings on the terminal server and just use the drvAsynIPPortConfigure() to talk to the device through
the network.
> Much simpler that way, no need for cumbersome protocols.
The advantage of putting the serial port configuration (baud, bits, parity, etc.) in the startup script is that it will then normally be under source release control, and hence difficult
to lose. If the settings are only inside the non-volatile memory of the terminal server they are less likely to be recorded. When the terminal server fails (and they do) the settings need to be recreated.
The protocol as implemented in drvAsynIPPort is not cumbersome: the serial port configuration commands in the startup script are identical to those for local serial ports, and the API for
writing and reading data is identical, whether or not the COM modifier to drvAsynIPPortConfigure is used.
Mark
From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Koennecke Mark (PSI) via Tech-talk <tech-talk at aps.anl.gov>
Sent: Thursday, February 3, 2022 1:15 AM
To: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov> Subject: .RE: Configuring serial communication with Lakeshore 331 via Moxa (Mark Rivers) Dear Jakub,
I work with Moxa terminal servers a lot. We have a lot of 1990 style serial hardware…. And I always configure the serial port settings on the terminal server and just use the drvAsynIPPortConfigure() to talk to the device through the network. Much simpler that way, no need for cumbersome protocols. Best Regards, Mark Koennecke
-- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. |