monkeyhead
Member
So I'm faced with either buying what I want -> ControlLogix 1756-L61 with the 1756-EWEB capable of non-CIP, raw TCP sockets.
Or what I'll most likely be allowed in my budget -> An rs-232 module for an existing spare SLC and a serial to IP converter by the likes of Moxa or B&B electronics.
So I don't need a blistering fast ethernet connection, but I do need to be able to connect to some existing software that uses a raw TCP socket connection and an ASCII based protocol. I only need to send and receive up to 5 messages a second (all less than 32 bytes) so the serial speeds should be more than capable of this.
But is the SLC + Serial/IP converter idea worth pursuing? I definately do not want a PC playing middle man between the PLC and the Existing software. I'm also limited to AB on this one. I'm just worried about it working the way I'm expecting it to.
Can you fellas see any obvious pitfall I'm over looking in this approach to raw TCP sockets for the SLC?
Or what I'll most likely be allowed in my budget -> An rs-232 module for an existing spare SLC and a serial to IP converter by the likes of Moxa or B&B electronics.
So I don't need a blistering fast ethernet connection, but I do need to be able to connect to some existing software that uses a raw TCP socket connection and an ASCII based protocol. I only need to send and receive up to 5 messages a second (all less than 32 bytes) so the serial speeds should be more than capable of this.
But is the SLC + Serial/IP converter idea worth pursuing? I definately do not want a PC playing middle man between the PLC and the Existing software. I'm also limited to AB on this one. I'm just worried about it working the way I'm expecting it to.
Can you fellas see any obvious pitfall I'm over looking in this approach to raw TCP sockets for the SLC?
Last edited: