Experimental Physics and Industrial Control System

Hi Paul,

I'm not a PLC Expert but in one project we used the s7plc driver to
integrate S7-300 PLC in EPICS environment defining several sockets in
SEND/RECV operating mode.

On EPICS side, into the ioc startup script we defined the sockets
provided by the PLC:

# Configure S7plc EPICS Direct Driver
epicsEnvSet("PLC_IP_ADDR","1.2.3.4")
epicsEnvSet("PLC_NAME1","P2000")
epicsEnvSet("PLC_NAME2","P2001")
epicsEnvSet("PLC_NAME3","P2002")
epicsEnvSet("PLC_NAME4","P2003")

# Socket Communincation:
s7plcConfigure $(PLC_NAME1), $(PLC_IP_ADDR),2000,2032,2032,1,4000,1000
s7plcConfigure $(PLC_NAME2), $(PLC_IP_ADDR),2001,998,998,1,4000,1000
s7plcConfigure $(PLC_NAME3), $(PLC_IP_ADDR),2002,1388,1388,1,4000,1000
s7plcConfigure $(PLC_NAME4), $(PLC_IP_ADDR),2003,1592,1592,1,4000,1000


On PLC side, we defined the different sockets adding "New Connections"
on your CPU/CP, specifying the port desired for every entry. After that
we could define the Communication Blocks in our PLC software according
to our requests and pointing to the sockets previously implemented.

In our case we used a S7-300 PLC equipped with Communication Processor
(CP) card where we defined the TCP server with the 4 sockets.

If I don't make a mistake, we also checked the PLC cycle time was still
suitable for managing the data exchange among all the sockets we
defined.

Hope this helps.

Regards,

- Maurizio
 



on Oct 20, 2017 07:28 PM, Paul Sichta <[email protected]> wrote:

> OK, thanks I'll see what the PLC guys says about that. That was my
> first
> thought, but then I didn't see how on the PLC side to direct the
> send-block
> mechanism to an ipaddr:port .
> 
> 
> -ps
> 
> 
> On Fri, Oct 20, 2017 at 1:24 PM, Zimoch Dirk (PSI)
> <[email protected]>
> wrote:
> 
> > Hello Paul,
> >
> > If you cannot increase the block size (the driver has no limit on
> > this but
> > maybe the PLC) you can have two blocks on the PLC running on
> > different
> > ports. To the IOC this would look like two devices.
> >
> > Dirk
> >
> > Am 20.10.2017 um 19:18 schrieb Paul Sichta <[email protected]>:
> >
> > I have been using s7plc driver for years with one SND and one RCV
> > block on
> > the PLC. Now, we need to send more data than can fit in the (max
> > size)
> > 240-byte block.  How can I send more data to EPICS?
> >
> > Regards,
> > -ps
> >
> >



~~ Maurizio Montis - Control System Engineer ~~
   office: +39 0498068558
   mobile: +39 3408428089
   mail: [email protected]
   skype: maurizio_montis

Istituto Nazionale di Fisica Nucleare - Laboratori Nazionali di Legnaro
   V.le dell'Universita', 2
   35020 LEGNARO (PD) - ITALY 							

References:

s7plc more than one 240-byte PDU Paul Sichta

Re: s7plc more than one 240-byte PDU Zimoch Dirk (PSI)

Re: s7plc more than one 240-byte PDU Paul Sichta

Navigate by Date:

Prev: Re: Online EPICS training Mark Rivers

Next: Re: Question about the module named caffi.ca Wang Xiaoqiang

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 

Navigate by Thread:

Prev: Re: s7plc more than one 240-byte PDU Zimoch Dirk (PSI)

Next: Question about the module named caffi.ca lzf neu

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