Re: .RE: Configuring serial communication with Lakeshore 331 via Moxa (Mark Rivers)

[Mark Rivers via Tech-talk <tech-talk at aps.anl.gov>]

> 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