Rad Pro: Geiger-Müller tube profiles

[PlasmaHH]

So I have tinkered with my gc-01 and basically almost done with creating a version with pluggable tubes (still need to 3d print somet stuff for that).

So I don't know if that would be something for others, or if it would fit in the gc01 firmware (looks like the 40? k are pretty full already), but nevertheless here is my idea (also maybe someone creates a really nice open source geiger counter hardware that uses radpro and this feature).

The idea is to have "real" HV profiles. I think its not really necessary to be able to create them in the device GUI itself, it can be serial commands as well, but it should provide user settable values of everything interesting for one tube:

• The name
• The PWM Frequency
• The PWM Duty Cycle
• The Factor to go from CPS -> µSv/h (or whatever other units)
• The dead time value

I think it would be nice if they were alongside the currently available "factory" and "energy saving" profiles, and are saved in the eeprom too. Upon selection all the values listed above would be loaded at once, that way when someone changes the tube "in the field" it is a matter of seconds to apply all the new settings (especially if the desired value is not directly available in the GUI like for example the GUI offers 20kHz or 40kHz but I might have determined that 21145Hz is the best for me ;) )

[Gissio]

Build a custom release. You just need to modify settings.h.

[PlasmaHH]

Yes I know I can implement that feature myself, but I thought it might be useful for others, maybe not? From looking at the project code it seems to be a bit more to add runtime selectable profiles than to add a bit to the settings.h though, things like tube sensitivity and dead time seem to be handled totally differently than the pwm settings.

[Gissio]

Understood.

[PlasmaHH]

I have modified my gc01 to plug in different probes, and I noticed that I also change the warnings/alarm thresholds. If someone ever implements such a profile feature it should probably either include these settings too, or the settings should always internally be in µSv/h or similar because the profile part that calculates this from the cps would then work too.