AdvancedHMI Software
General Category => Open Discussion => Topic started by: Shark13 on January 29, 2020, 09:50:04 AM
-
I'm starting a new project on an old SLC 5/04 that is DH+ communication. I want to get rid of the old panelview and build an advanced HMI. I'll be incorporating a PC to run the HMI software, ect.
I use a usb to dh+ converter for the PLC and panelview programming, is there a driver out there to support an older system like this for advanced HMI? I've tried the built in ones and no luck getting communications to work. Am I doing something wrong? Or do I need to buy a EthernetIP to DH converter? Any help would be appreciated.
-
There are a few options that have been tested:
- Set the pass through bit in the SLC 5/04 and use the DF1 serial driver connected to the RS232 port
- Use an Equustek DL3500 to convert serial DF1 to DH+
- An old AB 1770-KF2
-
Ok, thanks for the response. My rs232 port is currently being used to go to an AB 1761-Net-ENI DF1 to Ethernet/IP converter for data acquisition. May be a silly question but is it possible to put a switch in right after that and go back through the converter EthernetIP to rs232 for the Advanced HMI?
-
Ok, thanks for the response. My rs232 port is currently being used to go to an AB 1761-Net-ENI DF1 to Ethernet/IP converter for data acquisition. May be a silly question but is it possible to put a switch in right after that and go back through the converter EthernetIP to rs232 for the Advanced HMI?
Not a silly question. I did something similar, but depending on the amount of connetions you use on the Ethernet side (the Net-ENI has a very limited amount of input connection, I think they are only two), you may be able to do it. If you type the Net-ENI IP address in your web browser you will be able to see some data like the actual connections to have a idea. Or you can just try with a sample app that reads a variable from your PLC, and see what happens.
There is another option I ended using, another interface like the Net-ENI but from a third party RTA Automation
https://www.rtautomation.com/product/515rtaeni-n34/ (https://www.rtautomation.com/product/515rtaeni-n34/)
It has a larger amount of connections available, and has some other useful features not present in AB's. Downside, is that did not work well with an Ingear communication driver we tried to use with. It did not work with AHMI at the beginning but as usual Archie responded with a great support and made changes that fixed it. I think he added the patch to main beta.
Anyway, I think using the Ethernet connection will be the correct route for you.
-
Not sure, but I think the basice modules can be used with DF1, that you could add to your rack and communicate using the a serial port.
Please anyone can correct me if I'm wrong.
-
Found that old post with the RTA Automation Net-ENI troubleshooting, just in case you are interested.
https://www.advancedhmi.com/forum/index.php?topic=2300.msg13425#msg13425 (https://www.advancedhmi.com/forum/index.php?topic=2300.msg13425#msg13425)
-
Ok, thanks for the response. My rs232 port is currently being used to go to an AB 1761-Net-ENI DF1 to Ethernet/IP converter for data acquisition. May be a silly question but is it possible to put a switch in right after that and go back through the converter EthernetIP to rs232 for the Advanced HMI?
Not a silly question. I did something similar, but depending on the amount of connetions you use on the Ethernet side (the Net-ENI has a very limited amount of input connection, I think they are only two), you may be able to do it. If you type the Net-ENI IP address in your web browser you will be able to see some data like the actual connections to have a idea. Or you can just try with a sample app that reads a variable from your PLC, and see what happens.
There is another option I ended using, another interface like the Net-ENI but from a third party RTA Automation
https://www.rtautomation.com/product/515rtaeni-n34/ (https://www.rtautomation.com/product/515rtaeni-n34/)
It has a larger amount of connections available, and has some other useful features not present in AB's. Downside, is that did not work well with an Ingear communication driver we tried to use with. It did not work with AHMI at the beginning but as usual Archie responded with a great support and made changes that fixed it. I think he added the patch to main beta.
Anyway, I think using the Ethernet connection will be the correct route for you.
I only need 1 more connection really for the AHMI communication. At that point would the EthernetIP for SLC driver work, or would I need to use something else?
-
We have a micrologix PLC with the Net-Eni, so I would conclude that you need the SLC Ethernet driver.
-
I tried that with no luck. I've matched the IP to the ENI, and I get a "Write Failed!No response from PLC during write" error.
-
I have also tried the 3.99y patch and get the same result.
-
Could an RS232/DF1 cable splitter be used at the PLC? One side goes out to the ENI, one is dedicated to the AHMI?
-
I tried that with no luck. I've matched the IP to the ENI, and I get a "Write Failed!No response from PLC during write" error.
Did you try disconecting the HMI and connecting the Ethernet cable directly to your PC? To make sure there is no other connection interfering. Put the IP address of the Net-Eni in the driver configuration. Try restarting the Net-ENI, I had bad experiences with it at it seems to keep the connections alive for some time thus blocking new connections for a while.
-
Could an RS232/DF1 cable splitter be used at the PLC? One side goes out to the ENI, one is dedicated to the AHMI?
Never used one myself, could not tell.
-
Ok, thanks for the response. My rs232 port is currently being used to go to an AB 1761-Net-ENI DF1 to Ethernet/IP converter for data acquisition. May be a silly question but is it possible to put a switch in right after that and go back through the converter EthernetIP to rs232 for the Advanced HMI?
Not a silly question. I did something similar, but depending on the amount of connetions you use on the Ethernet side (the Net-ENI has a very limited amount of input connection, I think they are only two), you may be able to do it. If you type the Net-ENI IP address in your web browser you will be able to see some data like the actual connections to have a idea. Or you can just try with a sample app that reads a variable from your PLC, and see what happens.
There is another option I ended using, another interface like the Net-ENI but from a third party RTA Automation
https://www.rtautomation.com/product/515rtaeni-n34/ (https://www.rtautomation.com/product/515rtaeni-n34/)
It has a larger amount of connections available, and has some other useful features not present in AB's. Downside, is that did not work well with an Ingear communication driver we tried to use with. It did not work with AHMI at the beginning but as usual Archie responded with a great support and made changes that fixed it. I think he added the patch to main beta.
Anyway, I think using the Ethernet connection will be the correct route for you.
I only need 1 more connection really for the AHMI communication. At that point would the EthernetIP for SLC driver work, or would I need to use something else?
I just checked and I used the driver "EthernetIPforSLCMicroCom1" to connect with the RTA Net-ENI, but it was the same used for the AB Net-ENI.
Edit: See Attached
-
I tried that with no luck. I've matched the IP to the ENI, and I get a "Write Failed!No response from PLC during write" error.
Did you try disconecting the HMI and connecting the Ethernet cable directly to your PC? To make sure there is no other connection interfering. Put the IP address of the Net-Eni in the driver configuration. Try restarting the Net-ENI, I had bad experiences with it at it seems to keep the connections alive for some time thus blocking new connections for a while.
I'm plugged directly in with my programming laptop to the Net ENI. Using the EthernetIP for SLC
-
I tried that with no luck. I've matched the IP to the ENI, and I get a "Write Failed!No response from PLC during write" error.
The ENI module should work, but there is a bug in the firmware. If a connection is not properly closed, the ENI module will not release it. Eventually it will tie up all connections. If possible cycle the power on the module and try again. Be sure to use the EthernetIPforSLCMicro driver.
-
I tried that with no luck. I've matched the IP to the ENI, and I get a "Write Failed!No response from PLC during write" error.
The ENI module should work, but there is a bug in the firmware. If a connection is not properly closed, the ENI module will not release it. Eventually it will tie up all connections. If possible cycle the power on the module and try again. Be sure to use the EthernetIPforSLCMicro driver.
Cycled power, still same thing. Write error failure. I'm using the EthernetIPforSLCMicro driver.
I'm probably just going to bite the bullet and spend the money to buy a 5/05 processor to get this ball rolling, unless you have another idea. We didn't want to do that because we are planning on doing a full controls overhaul in the coming future, which will be Beckhoff processor, ect.
-
You can still try with the RTA Net ENI, as is not that expensive as it is the SLC 505.
-
Can you do a Wireshark capture and post the file?
-
Can you do a Wireshark capture and post the file?
I apologize for the delay. I'm in a bit of a battle with the IT department trying to get wireshark installed so I can get the capture for you. They are fighting it.
-
Can you do a Wireshark capture and post the file?
I apologize for the delay. I'm in a bit of a battle with the IT department trying to get wireshark installed so I can get the capture for you. They are fighting it.
I am shocked, my IT department uses wire shark all the time. It's a great tool for them.
-
Can you do a Wireshark capture and post the file?
I apologize for the delay. I'm in a bit of a battle with the IT department trying to get wireshark installed so I can get the capture for you. They are fighting it.
I am shocked, my IT department uses wire shark all the time. It's a great tool for them.
I'm sure they use it, they just don't want it out there on the network.
I managed to find a spare SLC 5/05 processor for this project, so that is the route I am going so that I can get it done.
-
Good Luck!