How to solve problem when setting two routes to a TwinCAT3 system
Auteur Gareth Green | Dernière modification 3/12/2024 par Gareth Green en cours de rédaction ⧼frevu-button-review-label⧽
How to solve problem when setting two routes to a TwinCAT3 system
Cannot_set_dual_TwinCAT_route_Screenshot_2023-02-08_103723.jpg
Historically, it has been possible to set up a system system where a Beckhoff CX5120 PC has a front end windows PC AND a second windows “diagnostic” PC attached to it.
This allows connection of the “diagnostic “ PC remotely via teamviewer, to log on to the PLC and monitor all data
Meanwhile the front end PC (operating the HMI) is uninterrupted in production using a route to the PLC.
This situation has stopped working on two recent setups. The Twincat router refuses to run the two routes simultaneously. As soon as a route on the second PC is connected, it drops out the first and vice versa.
"AMS Net Id"s of the Front End and Back End PCs are the same.
These are easily checked and modified by right clicking the TwinCAT icon in the task bar
There are 3 PCs on newer machines, and factories can have more than one machine. Therefore a system to uniquely identify each AMS Net Id is needed. The is easily achieved using the build number xxx in the AMS Net Id in the 4th octet position.
In the extremely unlikely event that a factory has two machines with the same build number, then use the 2nd octet to make the id unique. n=1, n=2, etc
PC | AMS Net Id |
---|---|
BE - Beckhoff or Backend | 10.n.0.xxx.1.1 |
FE - Front End PC | 10.n.1.xxx.1.1 |
VM - Virtual Machine | 10.n.2.xxx.1.1 |
Example:
Z056 and F056 share the same network
Z056BE = 10.1.0.56.1.1
Z056FE = 10.1.1.56.1.1
Z056FE = 10.1.2.56.1.1
F056BE = 10.2.0.56.1.1
F056FE = 10.2.1.56.1.1
F056FE = 10.2.2.56.1.1
en none 0
Draft
Vous avez entré un nom de page invalide, avec un ou plusieurs caractères suivants :
< > @ ~ : * € £ ` + = / \ | [ ] { } ; ? #