Software bug in Czechrads

34 views
Skip to first unread message

Rob Oudendijk

unread,
Sep 7, 2025, 1:37:44 AMSep 7
to Safecast Device Discussions and Support
Jan,

I am stared to wonder how the CPM counts are calculated in the Czechrad. Many submitted drives have at the start levels that seems not accurate. Are you using 5 seconds, 12 bucket system and averaging over 1 minute.  Like we use in the bGeigieNano and bGeigieZen ?


Import 1.jpg
Import 2.jpg

Import 3.jpg
Import 4.jpg

Warm regards
Rob



Jan Helebrant

unread,
Sep 8, 2025, 2:04:23 PMSep 8
to Safecast Device Discussions and Support
Dear Rob,
not sure about this, but asked our technician for details and will let you know.

regards

Jan

Dne neděle 7. září 2025 v 7:37:44 UTC+2 uživatel oudend...@gmail.com napsal:

Jan Helebrant

unread,
Sep 10, 2025, 9:05:28 AMSep 10
to Safecast Device Discussions and Support
Dear Rob,
initial versions of CzechRad firmware used CPM calculation from 5s pulses (e.g. CPM = CP5s * 12). Current version uses moving average.

I would also like to point out that we advise users to turn on CzechRad in advance so that the GPS drift can be corrected. Those "bad" starting points are no longer part of the uploaded LOG file.

regards

Jan

Dne pondělí 8. září 2025 v 20:04:23 UTC+2 uživatel Jan Helebrant napsal:

Rob Oudendijk

unread,
Sep 10, 2025, 9:24:51 AMSep 10
to Jan Helebrant, Safecast Device Discussions and Support
Dear Jan,

Thank you for the explanation. The new version is called Czechrad V2.0.0?

Warm Regards
Rob





Regards,
Rob Oudendijk Yuka Hayashi
tel +81 80-22605966  Skype: robouden  Facebook:robouden linkedin:robouden  


--
You received this message because you are subscribed to a topic in the Google Groups "Safecast Device Discussions and Support" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/safecast-devices/CqXxlcUjrpk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to safecast-devic...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/safecast-devices/09ab1a03-5794-4358-80d7-f052040c112an%40googlegroups.com.

Jan Helebrant

unread,
Sep 13, 2025, 9:09:32 AMSep 13
to Safecast Device Discussions and Support
Dear Rob,
As far as I know, this only reflects major firmware version changes - i.e. 1.x vs 2.x - but unfortunately not minor version changes.

So you won't recognize data from a device with firmware version 2.0.1. from version 2.0.3. This may be partly due to the concern that the API might not accept a file with a different string in the header.

But if it's not a problem, I'll ask our technician/developer if the FW version couldn't be included in the file header in the future firmware versions.

regards

Jan

Dne středa 10. září 2025 v 15:24:51 UTC+2 uživatel oudend...@gmail.com napsal:
Reply all
Reply to author
Forward
0 new messages