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
With the ads module, it is possible to setup an output record, e.g. BO (EnableAxis), to control a BOOL variable (bEnable) in a Beckhoff PLC. It is possible to add an info tag to the record definition to allow callbacks to update the BO record in case the PLC variable has been updated from the PLC. See example:
Problem:
*A state machine is used in the PLC to govern if the BOOL variable bEnable is allowed to only be FALSE.
*A pvput is made to EnableAxis to turn the value to TRUE: pvput EnableAxis 1
*The requested value of TRUE is directly overwritten by the state machine in the PLC to FALSE.
=> The callback is not updating the BO record to FALSE, but remains TRUE.
The text was updated successfully, but these errors were encountered:
Yes, the question mark is needed to enable the readback functionality
inside the driver.
The "old" codebase (v2.0.2) did rely on notifications, which do not work.
The "new" codebase (v2.1.0) allows to use a 1 second poll instead.
I need to figure out, how to configure it.
With the ads module, it is possible to setup an output record, e.g. BO (EnableAxis), to control a BOOL variable (bEnable) in a Beckhoff PLC. It is possible to add an info tag to the record definition to allow callbacks to update the BO record in case the PLC variable has been updated from the PLC. See example:
Problem:
*A state machine is used in the PLC to govern if the BOOL variable bEnable is allowed to only be FALSE.
*A pvput is made to EnableAxis to turn the value to TRUE: pvput EnableAxis 1
*The requested value of TRUE is directly overwritten by the state machine in the PLC to FALSE.
=> The callback is not updating the BO record to FALSE, but remains TRUE.
The text was updated successfully, but these errors were encountered: