Hi,

the machine I am working at has a D445.

The customer wanted to have safety checksums of the axes shown in our custom vizualisation (no WinCC). I accomplished this by:

- first using the readdrivemultiparameter function

- doing marshalling with anytype_to_littlebytearray and bigbytearray_to_anytype

- and finally converting it to HEX as a string

This worked and all the checksums are the same as if you would look at them in the expert parameter list. 

My problem now is that i accidently also converted timestamps to hex, which is kind of useless. 
And i cannot find the correlation between the Hex value and the number which is shown in the parameter list. 
For example:

r9782[0]: 1690h in the parameter list, as HEX: 44D338A8
r9782[1]: 1336h in the parameter list, as HEX: 44A6FADD

Even if I calculate it backwards to get the DWORD I receive using the readdrivemultiparameter function I don't understand how Simotion Scout displays it in that hour format then. It's not like the value is in ms or seconds.

Unfortunately this is a machine I can only rarely have to make changes, so I can't really test around on the machine.
Can somebody please explain how the time and HEX value correlate?

Thank you.