3S_ARTI_NG driver: the runtime does not react on interaction when the PLC is disconnected or not available. In DiagViewer you can find an entry '100ms timer has not cycled for xxxxx ms' when the PLC is disconnected/set to HW without proper connection.
3S_ARTI_NG driver: the runtime does not react on interaction when the PLC is disconnected or not available. In DiagViewer you can find an entry '100ms timer has not cycled for xxxxx ms' when the PLC is disconnected/set to HW without proper connection.
The driver does not wait for the return from ARTI-API calls, as long as there are blocking Runtime events handled by the driver these are not interrupted anymore.