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  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  <20232024  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  <20232024 
<== Date ==> <== Thread ==>

Subject: RE: Allen-Bradley PLC question
From: Mark Rivers via Tech-talk <tech-talk at aps.anl.gov>
To: Matt Rippa <matt.rippa at noirlab.edu>, Maren Purves <m.purves at eaobservatory.org>
Cc: Talk EPICS Tech <tech-talk at aps.anl.gov>
Date: Wed, 8 Feb 2023 17:44:27 +0000

Folks,

 

I wanted to provide an update on this.  I bought two of the MVI46-MNET modules on eBay.  I have tested them running on a SLC5/03 PLC and they work great.  EPICS is writing and reading values in the PLC using the EPICS Modbus driver over TCP/IP.  It will be a simple change in my ladder logic and EPICS databases to switch from the 1747-DCM addresses to the addresses for the MVI46-MNET.  I will then no longer need the VME system to talk to the PLC from EPICS.

 

The latest version of the ProSoft Configuration Builder worked fine to configure the MVI46-MNET over a Windows serial port.  That configuration only needs to be done once.

 

The bad news is that I seem to have purchased the last 2 MVI46-MNET modules I can find for sale anywhere!

 

Mark

 

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Mark Rivers via Tech-talk
Sent: Wednesday, February 1, 2023 10:47 AM
To: Matt Rippa <matt.rippa at noirlab.edu>; Maren Purves <m.purves at eaobservatory.org>
Cc: Talk EPICS Tech <tech-talk at aps.anl.gov>
Subject: RE: Allen-Bradley PLC question

 

Hi Matt,

 

Thanks very much for sharing that.

 

Since my tech-talk post I found that there is a third-party module for the SLC500 series PLCs that implements Modbus TCP/IP Server, the Prosoft MVI46_MNET.

https://www.prosoft-technology.com/prosoft/download/695/6439/file/MVI46_MNET_Datasheet.pdf

https://www.prosoft-technology.com/content/download/898/7470/file/mvi46_mnet_user_manual.pdf

 

This should work with the EPICS Modbus module, which is a Modbus client.  It would require some minor changes to the ladder logic to put the data to/from EPICS in a different location.

 

The module is no longer manufactured but is available on the used market.

 

The User Manual says that a Windows configuration program is required to initially configure the module.  I have sent an inquiry to Prosoft asking if that program is still available, and what version of Windows is required.

 

Thanks,

Mark

 

 

 

From: Matt Rippa <matt.rippa at noirlab.edu>
Sent: Wednesday, February 1, 2023 10:07 AM
To: Maren Purves <m.purves at eaobservatory.org>
Cc: Mark Rivers <rivers at cars.uchicago.edu>; Talk EPICS Tech <tech-talk at aps.anl.gov>
Subject: Re: Allen-Bradley PLC question

 

Hi Mark and Maren,

 

We have the abdf1 driver which we converted to use OSI about 5 years ago. Jeff helped us at the time. It depends on drvserial, which was also converted.

 

 

 

You may also be able to supplement the PLC with an Ethernet module. I don't know if that's something that works for your exact model. I think we're using PLC5. With this setup we used a Linux compatible driver from ORNL. I believe it's the enetOrnlPLC5 driver. I'll find out and let you know. It's on one of our older build systems.

 

-Matt

 

 

On Tue, Jan 31, 2023, 9:01 AM Maren Purves via Tech-talk <tech-talk at aps.anl.gov> wrote:

Hi Mark,

 

finding it listed with no contact at https://epics.anl.gov/modules/bus.php#RS%2d232%2dABDF1, I can produce a tarball if nobody else comes forward.

 

Maren Purves
Head of Instrument and Telescope Software
East Asian Observatory / JCMT

 

On Tue, Jan 31, 2023 at 8:46 AM Mark Rivers <rivers at cars.uchicago.edu> wrote:

Hi Maren and all,

 

Is that abdf1 driver available for download anywhere?

 

It looks like one option is the ProSoft MVI46-MNET which is a module that plugs into the SLC chassis and provide a Modbus TCP/IP sever in the PLC.  That should directly work with EPICS, and require just a small change to my ladder logic.  The module is not made anymore, but there appear to be quite a few available on the used market.

 

Thanks,

Mark

 

 

From: Maren Purves <m.purves at eaobservatory.org>
Sent: Tuesday, January 31, 2023 12:34 PM
To: Mark Rivers <rivers at cars.uchicago.edu>
Cc: tech-talk at aps.anl.gov
Subject: Re: Allen-Bradley PLC question

 

Hi Mark,

 

we're still using the abdf1 driver that originated from Jeff Hill in 1995 (says the code) and that I recently asked about. I know that the communication goes through the serial line (which in our case is connected to a console switch and Ethernet from thereon). I don't know anything about the PLC hardware (or internal software) off the top of my head.

 

Maren Purves
Head of Instrument and Telescope Software
East Asian Observatory / JCMT

 

On Tue, Jan 31, 2023 at 7:30 AM Mark Rivers via Tech-talk <tech-talk at aps.anl.gov> wrote:

Folks,

 

I have two old Allen-Bradley SLC 500 PLCs with the SLC 5/03 processors.  These are communicating with EPICS via the VME 6008-SV1 scanner card, which is connected to a 1747-DCM “Direct Communication Module” in the PLC.  These communicate via the Remote I/O (RIO) protocol.  We are planning to eliminate the VME crates on our beamline, but really hope to avoid spending the $50K or so that it would cost to replace the PLCs.

 

I am therefore looking for another way to communicate from EPICS to the PLCs. I am not aware of any device that replaces the VME 6008-SV1, for example a PCI-E card or an Ethernet adapter device.  Does anyone else know of one?

 

The SLC-5/03 has an RS-232 serial port 0 that normally uses the DF1 protocol.  It is how we program it from a PC, for example.  It also has an RS-485 port 1 that uses the DH-485 protocol.  It does not have an Ethernet connection.

 

The RS-232 port can be configured to use be a Modbus master.  Unfortunately it cannot be configured to be a Modbus slave, which would allow simple connection to EPICS via the Modbus module.  However, I could enhance the Modbus module to add support for acting as a Modbus slave, and the PLC could then connect to the EPICS IOC and send and receive data.

 

Does anyone know of another option, for example with the DH-485 port?

 

Thanks,

Mark

 


References:
Allen-Bradley PLC question Mark Rivers via Tech-talk
Re: Allen-Bradley PLC question Maren Purves via Tech-talk
RE: Allen-Bradley PLC question Mark Rivers via Tech-talk
Re: Allen-Bradley PLC question Maren Purves via Tech-talk
Re: Allen-Bradley PLC question Matt Rippa via Tech-talk
RE: Allen-Bradley PLC question Mark Rivers via Tech-talk

Navigate by Date:
Prev: PVXS release 1.1.2 Michael Davidsaver via Tech-talk
Next: Re: Weird behaviour in wait=True when using epics.Motor.get(something, something, wait=True) Marco A. Barra Montevechi Filho via Tech-talk
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  <20232024 
Navigate by Thread:
Prev: RE: Allen-Bradley PLC question Mark Rivers via Tech-talk
Next: Quickstart Error trying P4P Matt Rippa via Tech-talk
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  <20232024 
ANJ, 08 Feb 2023 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·