There is no reason to use an NOE over an NOC that I know of.
Ethernet remote I/O for the M340 is an awkward thing if you want the same BMX I/O modules at the remote that you have locally on the processor.
I've used the PRA with M340. The PRA is a strange product. It isn't a true remote I/O adaptor at all. It is a reduced size Ethernet CPU that has to have a program developed for it just like the M340 Ethernet CPU. The NOC or NOE can do I/O scanning to it but you have to put code into the PRA to map the data to it's I/O. You have to keep a program file for it just like the M340 processor because that is exactly what it is - a smaller size M340 processor. You have to write code for at least one and probably both sides to detect communications failures and shut down the I/O on the remote end. You can solve some logic out there at the remote end if you want to - so there is some flexibility that may be desirable in some cases. The only advantage that the PRA has over putting a separate CPU out there is less cost - although it may add an extra item to your spare parts inventory. It's uncertain if I will ever use a PRA again.
I've use a lot of Advantys STB Modbus TCP remote I/O with good results. Almost all the time I've been able to use the default addressing for the modules and the role-name dhcp to load the IP. This results in a remote drop that is completely electrician changeable including the NIP without needing to use the Advantys configuration software. Schneider's official position seems to be that you must use the Advantys software to configure an island. I know from experience on 40+ islands over the years that in most cases that is not true. I want a remote I/O system that can be smashed with a forktruck and the electricians bolt in the parts, set the address switches, and get it going without calling me to bring the laptop. Advantys can do this. Most of my experience with STB has been on Quantum but some has been on M340.
Ethernet/IP configuration for remote devices on an NOC module initially seems to be clumsy compared to Rockwell but the results seem to be good once you figure out how it works. Around 7 years ago I had a lot of Ethernet/IP stuff hooked to various combinations of AB ControlLogix and Modicon M340. The Schneider phone support people were wondering why I was using Ethernet/IP to go from an M340 to a Schneider VFD. I'm a fan of Modbus in some situations but I wasn't interested in using a 50+ year old protocol for that installation. Now it has a mixture of Schneider and AB cpus with motor control from AB, Schneider, Weg, Cutler, and some others. Ethernet/IP has lived up to it's promises.
- - -
The executive summary of my opinion is - skip the PRA and use Ethernet/IP with an NOC module. Expect a reasonable amount of learning curve.
There is no reason to use an NOE over an NOC that I know of.
Ethernet remote I/O for the M340 is an awkward thing if you want the same BMX I/O modules at the remote that you have locally on the processor.
I've used the PRA with M340. The PRA is a strange product. It isn't a true remote I/O adaptor at all. It is a reduced size Ethernet CPU that has to have a program developed for it just like the M340 Ethernet CPU. The NOC or NOE can do I/O scanning to it but you have to put code into the PRA to map the data to it's I/O. You have to keep a program file for it just like the M340 processor because that is exactly what it is - a smaller size M340 processor. You have to write code for at least one and probably both sides to detect communications failures and shut down the I/O on the remote end. You can solve some logic out there at the remote end if you want to - so there is some flexibility that may be desirable in some cases. The only advantage that the PRA has over putting a separate CPU out there is less cost - although it may add an extra item to your spare parts inventory. It's uncertain if I will ever use a PRA again.
I've use a lot of Advantys STB Modbus TCP remote I/O with good results. Almost all the time I've been able to use the default addressing for the modules and the role-name dhcp to load the IP. This results in a remote drop that is completely electrician changeable including the NIP without needing to use the Advantys configuration software. Schneider's official position seems to be that you must use the Advantys software to configure an island. I know from experience on 40+ islands over the years that in most cases that is not true. I want a remote I/O system that can be smashed with a forktruck and the electricians bolt in the parts, set the address switches, and get it going without calling me to bring the laptop. Advantys can do this. Most of my experience with STB has been on Quantum but some has been on M340.
Ethernet/IP configuration for remote devices on an NOC module initially seems to be clumsy compared to Rockwell but the results seem to be good once you figure out how it works. Around 7 years ago I had a lot of Ethernet/IP stuff hooked to various combinations of AB ControlLogix and Modicon M340. The Schneider phone support people were wondering why I was using Ethernet/IP to go from an M340 to a Schneider VFD. I'm a fan of Modbus in some situations but I wasn't interested in using a 50+ year old protocol for that installation. Now it has a mixture of Schneider and AB cpus with motor control from AB, Schneider, Weg, Cutler, and some others. Ethernet/IP has lived up to it's promises.
- - -
The executive summary of my opinion is - skip the PRA and use Ethernet/IP with an NOC module. Expect a reasonable amount of learning curve.
Thank you so much !
