wwwald

Thanks for the fast response! I think we're working with 3.0.0.33 - can't check right now as our measurement setup is elsewhere. Has anything changed in time/timezone handling in the new 3.0.1.43? We can still consider upgrading at this stage. In any case - our filename versus measurement times are definitely different. We'll try to experiment further with Windows timezone config and report back when we know more! Again, thanks for thinking along!

I have a question regarding timestamps & timezones in Realterm. We're using Realterm on a Windows 7 computer, for logging data from a LoRa-based wireless dust sensor setup. This computer is configured with timezone "Europe/Brussels" Capture files are auto-named with an included timestamp, but there is a difference with the recorded UNIX timestamp in the actual measurements. Example: filename mentions 16-16 as hour (4:16 pm) data entries have a UNIX timestamp corresponding to times starting from 18:16...