Chris Wetzler

Commitment: We do use one one single "ownIP" (TRDP_SESSION_T.realIP) for each TRDP-session. This means, that the TSN (time sensitive networking) examples does use TWO sessions now, to establish standard-PD and TSN-PD traffic in parallel. And it leads to additional parameters / options when calling the TSN example code. See parameter-help of: - trdp/example/TSN/sendTSN.c - trdp/example/TSN/receiveTSN.c Commitment: We use CLOCK_REALTIME most of the time, since the realtime clock is the one synchronized...

Updating TSN / VLAN / RT-thread code

aggregates tickets #325 + #341 and TSN main-ticket #342: we committed to use distinct IP addresses inside a consist, even over different VLANs and we use preconfigured VLANs and PCP priorities to select preconfigured TSN timeslots on the network

Commitment: We do use one one single "ownIP" (TRDP_SESSION_T.realIP) for each TRDP-session. This means, that the TSN (time sensitive networking) examples does use TWO sessions now, to establish standard-PD and TSN-PD traffic in parallel. And it leads to additional parameters / options when calling the TSN example code. See parameter-help of: - trdp/example/TSN/sendTSN.c - trdp/example/TSN/receiveTSN.c Commitment: We use CLOCK_REALTIME most of the time, since the realtime clock is the one synchronized...

Commitment: We do use one one single "ownIP" (TRDP_SESSION_T.realIP) for each TRDP-session. This means, that the TSN (time sensitive networking) examples does use TWO sessions now, to establish standard-PD and TSN-PD traffic in parallel. And it leads to additional parameters / options when calling the TSN example code. See parameter-help of: - trdp/example/TSN/sendTSN.c - trdp/example/TSN/receiveTSN.c Commitment: We use CLOCK_REALTIME most of the time, since the realtime clock is the one synchronized...

Improved implementation due to commitment on how to use IP addresses and how to configure interfaces and VLANs for use with TSN TSN tests were done using Kontron KBox C-102-2 TSN Starterkit Use of static local variables instead of static structs inside of function vos_getInterfaceIP() to store interface informations (name, IP, VLAN, MAC) Reduce calls to vos_getInterfaces() reducing calls to system function getifaddrs() vos_ifnameFromVlanId() now uses the already stored interface

VOS socket options: QoS/Priorities setting do not set kernel queues

Closed, due to commitment on how to use IP addresses and how to configure interfaces and VLANs for use with TSN. See Ticket #342