Spurious 0xff after timestamp (EL3500)

[steffen-AEI]

Having been a Linux guy for the past 25 years, I was very happy to find this code, which made it possible to read out an EL3500 that had been purchased about ten years ago (I still have a 512MB SDcard for it). Thank you!

After successfully recording over 4 days, and reading out the internal memory of my logger daily, I this morning found some very high wattage values reported by el4000.py.

A closer inspection showed that there had been two startcodes (nothing unusual), and following the second one and the corresponding timestamp, there was an extra 0xff byte inserted, This kind of desynchronisation obviously caused the nonsensical values.

Not very familiar with Python programming, I had to doctor the file using an editor - and removing the extra byte put me back on track, with completely sensible values. Phew ;)

Did this happen to others as well? Would it be correct to ignore any 0xff bytes in front of any 5-byte record? Is it perhaps too late to ask for a patch? - Thanks.

(I seem to be unable to upload the file in any format allowed. Please advise how to provide it.)