You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to be able to talk to the beckhoff via a network cable. this ticket is to physically connect the beckhoff in the blockhouse, set up an ADS route and then confirm that the beckhoff can be talked to (now confirmed, though the controller is off)
we have set up all of the TC ioc macros in globals.txt like the galils as the inter tank will always need to be used and the configuration does not yet exist.
To review, right click the twincat icon in the system try, hit "edit routes" and see that there is a route added for MCU_014. it may show as disconnected at the moment as it's likely to be physically switched off.
The text was updated successfully, but these errors were encountered:
For info, beckhoff is plugged into the INT_04 port, which is patched into the private network. the IP of the controller is 192.168.1.221 as per the usual commissioning steps
We need to be able to talk to the beckhoff via a network cable. this ticket is to physically connect the beckhoff in the blockhouse, set up an ADS route and then confirm that the beckhoff can be talked to (now confirmed, though the controller is off)
we have set up all of the TC ioc macros in globals.txt like the galils as the inter tank will always need to be used and the configuration does not yet exist.
To review, right click the twincat icon in the system try, hit "edit routes" and see that there is a route added for MCU_014. it may show as disconnected at the moment as it's likely to be physically switched off.
The text was updated successfully, but these errors were encountered: