Support for TRDP over TSN for the NG-TCMS:
- Processing of PD communication must not grow with number of publishers or subscribers
- Sending/Receiving of TSN PD telegrams must depend on application's timing -> synchronous operation mode must be introduced
- Socket for TSN PD must bind to a different (virtual) interface, e.g. tsn0 opposed to eth0;
currently, a session binds to a specific IP address, not to a driver or an interface
- Additional Communication Parameter attribute could be used to determine TSN port
- for synchronous, timed sending of telegrams, tlp_put() would send the data directly instead of just updating the network buffer and relying on tlc_process() to walk through the queue
- the latency of the socket interface (to the HW-interface) must be known or the TSN-aware Ethernet driver must be called directly from the TRDP/VOS layer
Diff:
TSN support has been added as socket extensions and RT (cyclic) thread handling to the POSIX/Linux target. Cyclic threads are implemented on Windows, too - mainly to support the new high-performance version of TRDP with PD receive and send thread separation.