Issue:
What could have cause the Magelis target to get a timeout error when communicating to the Somachine controller using the Somachine protocol?
Product Line:
M238, M241, M251, M258, HMISTO/STU, HMIGTO/GTU, XBTGH/GK/GT, Panel PC, Box PC
Resolution:
Most communications issues between the Magelis and Somachine controller has to do with the Nodename of the controller does not match. Go to the Vijeo Designer, for MyController under the Somachine protocol of the IO Manager. The node name in that field must match the controller Node name. Once that has been modified, download to the Magelis and see if the communications will establish.
What could have cause the Magelis target to get a timeout error when communicating to the Somachine controller using the Somachine protocol?
Product Line:
M238, M241, M251, M258, HMISTO/STU, HMIGTO/GTU, XBTGH/GK/GT, Panel PC, Box PC
Resolution:
Most communications issues between the Magelis and Somachine controller has to do with the Nodename of the controller does not match. Go to the Vijeo Designer, for MyController under the Somachine protocol of the IO Manager. The node name in that field must match the controller Node name. Once that has been modified, download to the Magelis and see if the communications will establish.
發佈於:施耐德電機Taiwan
