[wiregate] Timestamp issue in telegram logging

[martenss]

I noticed that Eib telegram log file /var/log/eib.log does not always show the correct timestamp reflecting the telegram arrival.

See an example in attachment, or in short:
A telegram with time-stamp:
2011-03-21 09:07:53.975,A_GroupValue_Write,0.0.0,5/3/203,<...>
is being followed by a telegram with an earlier time-stamp:
2011-03-21 09:07:53.101,A_GroupValue_Write,0.0.0,5/3/122,<...>

It is not just a matter of sorting the file, as I did observe the first one coming in earlier than the second one on another Eib connected device (having a slightly misaligned clock though):
2011-03-21 09:07:46, 1/1/1, '5/3/203'f16, <...>
2011-03-21 09:07:47, 1/1/1, '5/3/122'f16, <...>

Looks like the time seconds are not correctly incremented when receiving a burst of messages.

Kind regards, martenss

[makki]

Thanks, scary.. Indeed a function returned the last 3 digits of microseconds instead of the expected milliseconds
Fixed in next update..

Makki

P.S.: Looks like noone yet looked on the ms-precision of the logging