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  <20092010  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  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: uptodate version of modtcp?
From: Burkhard Kolb <[email protected]>
To: Mark Rivers <[email protected]>
Cc: [email protected]
Date: Fri, 14 Aug 2009 15:51:53 +0200
Mark Rivers wrote:
Hi Burkhard,
I'm glad to hear it is working for you. I remembered what indicated a potential problem with Wago controllers in the NSLS driver. It appears that the address to read a particular register is different from the address to write that register. Normally each of my Modbus port drivers only reads or writes, not both. The exception is output drivers which can be configured to read once at iocInit to allow for a "bumpless" reboot, i.e. the output record value will match the current state of the hardware. If the Modbus addresses for write and read are not the same then this will not work. Have you tested this, i.e. do output records obtain the current values in the Modbus hardware when the IOC boots? Cheers,
Mark
________________________________

From: Burkhard Kolb [mailto:[email protected]]
Sent: Fri 8/14/2009 7:51 AM
To: Mark Rivers
Subject: Re: uptodate version of modtcp?



Mark Rivers wrote:
Hi,

I have an EPICS module called "modbus".  It uses asyn, and works on all supported EPICS architectures (Linux, Windows, vxWorks, etc.).  It supports TCP, serial RTU, and serial ASCII.  It has been tested on a variety of Modbus devices, but probably not WAGO.   Are you using a WAGO?  I looked at the NSLS WAGO support when I was writing my package, and I recall that there was something strange about the way WAGO treated addresses.  I didn't have a WAGO to test, so the driver may need a small addition to work on WAGO.

Here is the link:

http://cars.uchicago.edu/software/epics/modbus.html

Mark

Hi Mark,

thanks, it works out of the box also with WAGO. We have a 750-341
controller and several 750-460 (4 ch Pt100) modules. All I had to do
was modifying the startup script and the database.

Best regards,
Burkhard
--
Dr. Burkhard Kolb
HADES and CBM
E-Mail: [email protected]
Tel: +49-(6159)-71-2667 / Fax: +49-(6159)-71-2155

GSI Helmholtzzentrum für Schwerionenforschung GmbH
Planckstraße 1 / D-64291 Darmstadt / www.gsi.de

Gesellschaft mit beschränkter Haftung
Sitz der Gesellschaft: Darmstadt
Handelsregister: Amtsgericht Darmstadt, HRB 1528

Geschäftsführer: Professor Dr. Horst Stöcker, Christiane Neumann
Vorsitzende des Aufsichtsrates: Dr. Beatrix Vierkorn-Rudolph
Stellvertreter: Ministerialdirigent Dr. Rolf Bernhardt


Hi Mark,

no I could not test this. The modules I have are input registers
only (function code 4).
Cheers, Burkhard



References:
uptodate version of modtcp? Burkhard Kolb
RE: uptodate version of modtcp? Mark Rivers
RE: uptodate version of modtcp? Mark Rivers

Navigate by Date:
Prev: RE: uptodate version of modtcp? Mark Rivers
Next: TDS3000 Support for edm Mathew Hicks
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: uptodate version of modtcp? Mark Rivers
Next: RE: uptodate version of modtcp? So, Sung-Leung
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 31 Jan 2014 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·