Timestamp when server is offline about bw3-core HOT 5 CLOSED

I think I have got it working. By enable --timestamp in inputBase.py
mmProc.addArgument("--timestamp")
and in pocsagDecoder.py extract the timestamp and add the timestamp to the packet. The the packet has the timestamp when it was received. Before it was None and the server added timestamp when it was received.

from bw3-core.

I am not sure what this flag should change here.

The decoder creates a bwPacket and here the timestamp is generated.

And after sending, the string representation of this packet is feeded to the constructer of the bwPacket and should be read from the packet.

The real problem is, that the clients atm don't read the mm-stream if there is no connection.
So this means, decoding is paused if connection got lost.

from bw3-core.

In my case the client didnt send timestamp before and the server created it because it was None. If the server was down and when the que arrived all alarm got time from server, not from client. With my new code i get a timestamp from client when it was received and
pocsag-files.zip

not when server created timestamp.
Hard to explain but for me it works now. My code is very bad but it works,

from bw3-core.

it is not NONE or shouldn't be :-D
but the client will receive the packets from a MM-buffer at the moment, the client is reconnected and set the timestamp at this moment. That's a architecture problem in my opinion.

from bw3-core.

from bw3-core.