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: | support for Moxa ioLogik modules |
From: | "Pearson, Matthew R. via Tech-talk" <tech-talk at aps.anl.gov> |
To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Wed, 17 Nov 2021 16:54:20 +0000 |
Hi, I see there is a recent message about using the Modbus module to talk to Moxa ioLogik devices. This might be good time to announce that we've developed support for various Moxa ioLogik modules and put it on GitHub at: https://github.com/ornl-epics/moxa It includes support for: E1210 - 16 DI E1214 - 6 DI, 6 Relay E1240 - 8 AI E1241 - 4 AO E1242 - 4 DI, 4DIO, 4 AI It's light on documentation, but there is an example IOC showing how to use it, and it's simply: file E1214.template { pattern {P, R, PORT, IP_PORT} {mkp:, E1214:, m1, m1ip} } And the st.cmd file would contain: #E1214 Unit (6 DI and 6 Relay) epicsEnvSet("IP_ADDR","192.168.200.177:502") epicsEnvSet("IP_PORT","m1ip") epicsEnvSet("PORT","m1") < $(MOXA)/st_scripts/st_common.cmd So the st_common.cmd script hides away the details of setting up the TCP port and the Asyn Modbus ports. A range of Modbus ports are created, each with different word sizes and read/write settings, and then the module specific database
templates choose which ones they need to use for the module in question. Also includes a set of CS-Studio BOY/DisplayBuilder screens (example attached). Cheers, Matt STS Integrated Control System Lead Engineer Spallation Neutron Source Oak Ridge National Lab |
Attachment:
moxa_screenshot.JPG
Description: moxa_screenshot.JPG