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  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017 
<== Date ==> <== Thread ==>

Subject: !RE: Modbus help
From: <emma.shepherd@diamond.ac.uk>
To: <rivers@cars.uchicago.edu>, <tech-talk@aps.anl.gov>
Date: Fri, 27 Nov 2009 13:36:19 -0000
Hi all,

Just a quick thanks to everyone for their helpful suggestions.  In the
end I dismantled the rack and connected the IOC directly to the RS485
terminals on one of the devices and the modbus comms worked perfectly.
It looks like an issue with the daisy chain wiring.

Keep me updated with the V2-0 status Mark - if I can get this wiring
fixed I'll be your first customer!

All the best,
Emma


> -----Original Message-----
> From: Mark Rivers [mailto:rivers@cars.uchicago.edu] 
> Sent: 25 November 2009 18:35
> To: Shepherd, Emma (DLSLtd,RAL,DIA); tech-talk@aps.anl.gov
> Subject: RE: Modbus help
> 
> 
> Emma,
> 
> Once you get the communication with a single device working, 
> you are going to run into problems trying to communicate with 
> multiple RS-485 devices through a single serial port.  The 
> reason is that I am using the asynInterposeInterface layer to 
> add the RTU header with the slave address.  But asyn only 
> allows a single interposeInterface for each asyn port, which 
> restricts one to a single slave address.
> 
> Yves Lussignol from CEA has fixed this problem, by moving the 
> slave address management to layer 2 (asyn port driver) from 
> layer 3 (interpose interface).  He sent me a modified version 
> of the driver with this fix back in March 2009, but I have 
> been remiss in not testing it and releasing a new version of 
> the driver.  It does change the syntax of the 
> drvModbusAsynConfigure command, so it will be a major 
> release, i.e. 2-0.
> 
> I will try to get a new release out in the next couple of weeks.
> 
> Mark
> 
> 

-- 
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.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. 
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
 





Replies:
Mobus R2-0 available Mark Rivers
References:
RE: Modbus help Mark Rivers

Navigate by Date:
Prev: CA problem w EPICS 3.14.11 & VxWorks 6.7 GOURNAY Jean-Francois
Next: Mobus R2-0 available Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017 
Navigate by Thread:
Prev: RE: Modbus help Mark Rivers
Next: Mobus R2-0 available Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017 
ANJ, 31 Jan 2014 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·