Bosean FS-5000: Suggestions

[NuclearPhoenixx]

Hey there, I recently got myself hands on an FS-5000 with your great firmware on it, so first off thanks for all your work, I like it a lot.

I was playing around with the device and had a look at the menus, settings and your documentation here on GitHub, as well as shortly had a go at some other threads regarding this device here in the discussions. However, I have a couple of questions or ideas, remarks, whatever you wanna call it.

• Can you turn the ticker on and off in the main screen without having to go into the settings? The same may also apply to the alarm.
• It would also be interesting to see if you could manually dismiss the current alarm until the next one goes off for example, kind of like a temporary mute button.
• I think it would be very useful to have icons on the main page that show whether the ticker and especially(!) the alarm are activated. I think the original firmware had something like that. Because I often change it depending on my needs and expected environment, so therefore I always have to go into the settings to see if it's on or off.
• Is there any way to set the alarm to ONLY vibrate or ONLY sound? As far as I can see, there is only general on/off and the alarm threshold (with vibration and sound at the same time). This would be an AMAZING addition to the software. Kind of like the menu points in the "pulse" menu, but just for the alarm to have control over vibration and sound.
• Is there information about the firmware version used in every menu? That would be really useful, e.g. under the statistics. I know it is displayed very briefly at the start, but it is so short that you can't read it. I think that would be a no-brainer to have in the stats settings menu, just so that we can see what version we're running to update or for debugging.
• How does the dead time compensation setting work? For me, after several hours under statistics, it only says <66µs, which is obviously not specific enough to set the value for compensation since there are a lot of values from 40 up to ~66. Do I pick the lowest value as to not over-compensate or do I pick a value close to 66?
• Also I just noticed that we have a "max" indicator in the instantaneous dose rate screen, but no "min", would be nice to have a minimum dose rate figure too.

I hope that's not too much, these were just my first thoughts when using the device and for which I couldn't really find documentation or such. It's possibly that I might have overlooked something even with my searches, so if that's the case sorry to waste your time.

Other than that, I think the firmware and layout of all the menus, the controls and such are awesome. It's quite a useful little device with a lot of control over its behavior and such, great! :)

[NuclearPhoenixx]

Update: Some of the requests have already been merged it seems like, thanks a lot! 🎉

As far as I'm aware this has not been mentioned so far, please correct me if I overlooked something, I searched the most recent commits:

• Can you turn the ticker on and off in the main screen without having to go into the settings?
• I think that would be a no-brainer to have in the stats settings menu instead of only briefly at startup, just so that we can see what version we're running to update or for debugging.
• How does the dead time compensation setting work? For me, after several hours under statistics, it only says <66µs, which is obviously not specific enough to set the value for compensation since there are a lot of values from 40 up to ~66. Do I pick the lowest value as to not over-compensate or do I pick a value close to 66?
• I noticed that we have a "max" indicator in the instantaneous dose rate screen, but no "min", would be nice to have a minimum dose rate figure too.

[Gissio]

Q1: You can't for now.
Q2: Won't be implemented.
Q3: Dead-time compensation is only important if you measure high levels of radiation. I suggest you please RTFM the manual: https://github.com/Gissio/radpro/blob/main/docs/manual.md#dead-time-and-dead-time-compensation .
Q4: I don't see any scenario where this would make any sense.

[NuclearPhoenixx]

Q3: Dead-time compensation is only important if you measure high levels of radiation. I suggest you please RTFM the manual: https://github.com/Gissio/radpro/blob/main/docs/manual.md#dead-time-and-dead-time-compensation .

That manual does not answer my question above.

For me, after several hours under statistics, it only says <66µs, which is obviously not specific enough to set the value for compensation since there are a lot of values from 40 up to ~66. Do I pick the lowest value as to not over-compensate or do I pick a value close to 66?

[Gissio]

Let me quote from the manual:

Rad Pro employs the non-paralyzable model for dead-time compensation:

$$n = \frac{m}{1 - m \tau}$$

Here, the corrected cps value $$n$$ is calculated from the raw cps value $$m$$ by dividing it by $$(1 - m \tau)$$, where $$\tau$$ is the dead-time parameter of the model.

If $$\tau$$ is overestimated, the model will overcompensate, resulting in cps values higher than the actual radiation level. Conversely, if $$\tau$$ is underestimated, the compensation will be insufficient, leading to lower than actual cps values.

Rad Pro gives you an upper bound for the dead time, measured as the minimum interval between detected events. This can serve as a good starting point for $$\tau$$.

For a more precise measurement of dead time, consider using the two-sources method. Here's a resource that explains this approach in detail: https://yadda.icm.edu.pl/baztech/element/bwmeta1.element.baztech-6a2e8fea-a85d-4b52-b632-8550444b9109/c/domanski_i_in._dead_time_IAPGOS_nr_1_2018.pdf

[NuclearPhoenixx]

Thank you for the paper

[technils]

I would like to thank the developers of the Rad Pro firmware. The user-friendly interface and the many different functions and settings combined with the large, sensitive pancake detector made my Bosean FS-5000 a truly excellent device for a low price.
The only suggestion I have is to add a 5-10 second pause to average the pulse rate before displaying the first readings on the display when turning on the device or resetting measurements. Sometimes when turning on or resetting, the device gives inflated readings, which are expressed in unwanted peaks on the graph

[Gissio]

Great idea!

[STGitUser]

Uh, the Bosean FS-5000 does not have a pancake detector. It's just a glass GM tube like the rest of the supported devices.

[technils]

I've printed a new enclosure and installed a beta-2 detector
https://www.thingiverse.com/thing:6961118

[Ilja-code-art]

1. When You turning on the device: the Firmware version should be longer show on the main screen. Now is too short.
2. Bosean FS-5000 Settings -> Geiger Tube -> Sensitivity -> J305 (After flashing the firmware)
   It should be set as J321 (default).
   Please fix this with new release.
   After Flashing firmware on FS-5000 the J321 should be set as default.
3. Date displayed anywhere
4. New measurement units R (Roentgen (unit)) added.

[ICantMakeThings]

I made a video about flashing the fs-5000 with radpro using a stlink, https://youtu.be/Ney8Cb1XnZk
if you think it would be right, you could add it in https://github.com/Gissio/radpro/blob/main/docs/devices/Bosean%20FS-5000/install.md as a video tutorial. if not then thats fine, just a suggestion, great work btw Gissio!

[Gissio]

The line "Error: couldn't open IMAGE_PATH" indicates that the flash script is not correctly replacing the variable IMAGE_PATH. I'll test it on Ubuntu and let you know.

[Gissio]

ICantMakeThings: I just found an error in the flash scripts and updated radpro2.2beta2.zip (available at https://github.com/Gissio/radpro/releases/tag/2.2beta2 ). Could you download it and try again?

[ICantMakeThings]

very sory for the late, been quite busy, I'll will check hopefully tomorrow and get back to you

[ICantMakeThings]

Everything works! here's the log:

user@user:~$ bosean-fs5000-update.sh
Available language codes: bg cs da de el en es fi fr hr hu it ja ko nl pl pt ro ru sk sl sv tr uk vi zh_CN
Enter language code for Rad Pro installation: en
../bosean/firmware/radpro-bosean-fs5000_portrait-en-2.2beta2.bin
Backing up old firmware image...
xPack Open On-Chip Debugger 0.12.0+dev-01850-geb6f2745b-dirty (2025-02-07-10:08)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
DEPRECATED: OpenOCD support for ST-Link HLA transport will be dropped soon!
Consider updating your ST-Link firmware to a version >= V2J24 (2015)
Info : auto-selecting first available session transport "hla_swd". To override use 'transport select '.
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
Info : clock speed 500 kHz
Info : STLINK V2J39S7 (API v2) VID:PID 0483:3748
Info : Target voltage: 3.176197
Info : [stm32l4x.cpu] Cortex-M4 r0p1 processor detected
Info : [stm32l4x.cpu] target has 6 breakpoints, 4 watchpoints
Info : [stm32l4x.cpu] Examination succeed
Info : [stm32l4x.cpu] starting gdb server on 3333
Info : Listening on port 3333 for gdb connections
Info : Unable to match requested speed 500 kHz, using 480 kHz
Info : Unable to match requested speed 500 kHz, using 480 kHz
[stm32l4x.cpu] halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x0800069c msp: 0x2000c000
Flashing new firmware image...
xPack Open On-Chip Debugger 0.12.0+dev-01850-geb6f2745b-dirty (2025-02-07-10:08)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
DEPRECATED: OpenOCD support for ST-Link HLA transport will be dropped soon!
Consider updating your ST-Link firmware to a version >= V2J24 (2015)
Info : auto-selecting first available session transport "hla_swd". To override use 'transport select '.
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
Info : clock speed 500 kHz
Info : STLINK V2J39S7 (API v2) VID:PID 0483:3748
Info : Target voltage: 3.185511
Info : [stm32l4x.cpu] Cortex-M4 r0p1 processor detected
Info : [stm32l4x.cpu] target has 6 breakpoints, 4 watchpoints
Info : [stm32l4x.cpu] Examination succeed
Info : [stm32l4x.cpu] starting gdb server on 3333
Info : Listening on port 3333 for gdb connections
Info : Unable to match requested speed 500 kHz, using 480 kHz
Info : Unable to match requested speed 500 kHz, using 480 kHz
[stm32l4x.cpu] halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x0800069c msp: 0x2000c000
Info : Unable to match requested speed 500 kHz, using 480 kHz
Info : Unable to match requested speed 500 kHz, using 480 kHz
[stm32l4x.cpu] halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x0800069c msp: 0x2000c000
** Programming Started **
Info : device idcode = 0x10016435 (STM32L43/L44xx - Rev Z : 0x1001)
Info : RDP level 0 (0xAA)
Info : flash size = 256 KiB
Info : flash mode : single-bank
** Programming Finished **
Info : Unable to match requested speed 500 kHz, using 480 kHz
Info : Unable to match requested speed 500 kHz, using 480 kHz

[Gissio]

Nice!

[Ilja-code-art]

Bosean FS-5000 -> When you push two side buttons (to turn off the sound) there is no ICON that sound is off.

[Gissio]

Thanks for your contribution.

[Ilja-code-art]

The voltage is 2.475V ant the FS-5000 is still working.... There was no warning that battery is empty....

[Ilja-code-art]

Thanks for your report. Will be fixed in the coming release!

Thank you for fixing the bugs :) I like to test on FS-5000 :)

[Gissio]

That's great! Can you also test #254?

[Ilja-code-art]

That's great! Can you also test #254?

Yes, I can.
Now I have 2.1.1 do i need to install radpro-2.2beta2? If yes there is no problem for me.

[Gissio]

Stick with 2.1.1 and let us know if brightness is allright.

[Ilja-code-art]

Stick with 2.1.1 and let us know if brightness is allright.
All four settings are pretty linear and precise.
I want that High level will be more brighter then now it is.
Maybe it is possible to do not 4 brightness levels to chose but like a slide switch with 10 positions?
By the way is there a option to donate?