Closed KathrynBaker closed 6 years ago
The support/ether_ip/master module is currently building as part of our EPICS system but has not been tested - it looks to have been designed with windows support in mind, so a good chance it will work. There are some notes on usage at https://ics-web.sns.ornl.gov/kasemir/etherip/index.html
There has been a further update:
We have been progressing the design further and there is uncertainty as to whether this device will give us all of the functionality that we would like, re HMIs and networking. It appears that HMIs have to connect to it via Modbus RTU. However when there is an Ethernet port connected it disables the serial port so I cannot use both. Is it possible to use a serial/Ethernet converter and then talk to it via Modbus over Ethernet?
The device is on the network, and the IP address can be obtained from @KathrynBaker
How many serial ports does it have? We have connected a MOXA to the RS232 on the Schneider PLC and that worked OK with Modbus RTU but you can't share moxa ports so it would need a second RS232 on the Cr30 for the terminal etc.
I've had a go at getting basic comms going. The device seems to reply, but asking for any tags yields a "Service not supported" response. This suggests that we're asking for the wrong tags or that the PLC is not properly configured to publish any information. I tried asking for a selection of the tags listed on pages 189-190 of the manual (on shared drive).
My attempts at creating an IOC for it are in the pull requests linked above - as I say, it doesn't currently communicate properly but it might be a useful starting point for someone later on, as it does at least build and make an attempt to communicate.
A direction for continuing this ticket would be to discuss with Peter Barnes (?) to find out exactly how the PLC is currently configured, but since this ticket is timeboxed I'll leave it at that for now. There is also a question (see comments above) about whether we end up using Ether/IP at all.
I emailed Peter Barnes on 26/2 with some suggestions, mainly about using the web interface via the HMI as it looked like having the CR30 on any sort of ethernet at all was an issue.
From: Baker, Kathryn (STFC,RAL,ISIS) Sent: 15 March 2018 13:07 To: Akeroyd, Freddie (STFC,RAL,ISIS); Woods, Kevin (Tessella,RAL,ISIS) Cc: Willemsen, Thomas (Tessella,RAL,ISIS) Subject: RE: #2933 ZOOM: Ensure basic comms on the Ethernet/IP with a CR30 PLC
Peter is due to be off on Paternity (or is already off), this is something that the ZOOM team are aware of. This ticket was put back into the backlog (3 weeks ago) as there was a lack of detail of what the safety team were/are planning.
This is still coming up at ZOOM Planning meetings, and if I ever get any actual information I will pass it on/alter the tickets/create tickets as appropriate.
Regards, Kathryn
It seems the PLC guys are looking for an EPICS solution, but to my knowledge aren't actually interacting with us, Peter is now away, and Antonio should be looking at this, but this is rumour/info being gathered at planning meetings. Instrument Scientists are aware of the situation.
I think we should shortcut the rumour mill and simply arrange a meeting with Antonio directly.
I have since met with Antonio, and there is some discussion still to be had, but it looks like this will now be a dedicated piece of data acquisition hardware. Specifics to be agreed. As such, this is now no longer needed.
As someone involved with motion on ZOOM I want to be able to read the status of the CR30.
Acceptance Criteria
Notes