ManofBedford
Member
Hello PLCNeters,
In the past I have read quite a few topics in regards to different things to help me on this website. But it has come time to post my first post on this website. Just a small background on me , in the 3rd year of my 4 year apprenticeship in control "softwaring" and still learning everyday about what/how to do things.
Which brings me to my problem, I am been given the task of sorting out the Smarteye sensors that read the smarteye identification labels on the carriers in a factory. We are using a Schneider M340 for the PLC to control the surrounding systems and so the smarteye data needs to be "fed" back to it from a T-netx(dual sensor controller) to then be used by other things late on. But my question is (having never done any like this before) , what would be the best option to use for the T-netx control unit? Either the Ethernet/IP option or the TCP/IP version? After looking around I am still unsure which would be best to use in partner with the M340 PLC .
Thanks already,
ManofBedford
In the past I have read quite a few topics in regards to different things to help me on this website. But it has come time to post my first post on this website. Just a small background on me , in the 3rd year of my 4 year apprenticeship in control "softwaring" and still learning everyday about what/how to do things.
Which brings me to my problem, I am been given the task of sorting out the Smarteye sensors that read the smarteye identification labels on the carriers in a factory. We are using a Schneider M340 for the PLC to control the surrounding systems and so the smarteye data needs to be "fed" back to it from a T-netx(dual sensor controller) to then be used by other things late on. But my question is (having never done any like this before) , what would be the best option to use for the T-netx control unit? Either the Ethernet/IP option or the TCP/IP version? After looking around I am still unsure which would be best to use in partner with the M340 PLC .
Thanks already,
ManofBedford