Gari

Our solution is attached in the Ticket and as I metioned before the added code is in the line 331: "iterPD->curSeqCnt = 0xFFFFFFFFu;"

No, in our case the redundant devices have different IPs but what Siddhi says does not work. I think that the source IP is not taken into account... where should this ip origin be taken from? From the configuration? Because we don't use the source IP filtering and we don't have any source IP in the configuration file. Or maybe there is a Bug?

The added code (line 331): "iterPD->curSeqCnt = 0xFFFFFFFFu;"

Sequence counter synchronization error working in redundancy mode

Hi Bernd! @bloehr: It's Linux.

@bloehr: We try to integrate the trunk implementation in our code to check it but we get some compilation errors related to the differences between both codes and we can´t verify it. However, the patch has been applied just as we reported, so it looks like it will work fine.

The original file (src/vos/posix/vos_thread.c)

Blocked indefinitely in the nanosleep() call