Bosean FS-600: Debugging

[Dsl71]

I tried the new 2.0 beta16 on a board revision KL7 820.403D. The display had all pixels set to black, no background light, text was only readable in a very steep angle. keyboard seems to fail also. Klicks were hearable, the LED was flashing also.

Back to 2.0beta10 everything worked again.

[Dsl71]

Already trying..

Regarding: https://github.com/Gissio/radpro/issues/17#issuecomment-2014498168

I think there should be some error handling too in the future. Otherwise you never know when a flash error occurs.

[Dsl71]

I am sorry. Note: data logging of 1 minute is also active. I set it to off and retry...

After about 12min same exception. Also Stop/Start Log operations in GeigerLog don't give any response anymore and always the exception. Only a reconnect solves the problem.

[Gissio]

Can you try geigerlog-radpro 1.4.3b?

I've changed the Rad Pro flash code once again. Now a page is only erased if writes fail at the start of the page. This improves recovery in case of an error.

[Dsl71]

geigerlog-radpro 1.4.3b runs for one hour now without any problems.

Next step: Flash the newest FW and retry...

[Dsl71]

Bug, see the two timestamps...

[Dsl71]

Bug , from a certain point "no data", no recovery.

Reconnect not possible, even after restarting GeigerLog.

Device is freezing, Power removed and restarted !!!

still last FW.

[Dsl71]

This is also very very unlikely: (CPS)

[Dsl71]

Again no data, device freezes, only pulse led is updated.

[Dsl71]

I think too those peaks are related to a time base problem (missing 1 sec interrupt or so)

This seems to me like a timer overflow. cyclic.

BTW this is with the newest FW.

[Gissio]

I don't like the freezing part. I will try to reproduce the problem locally (so far I had been testing with the GC-01 USB port, which seems to work quite well).

[Dsl71]

FYI: at least for the CPS the poisson fit seems to be good.

CPM is not lookin so good:

[Dsl71]

Last plot before freeze...

[Gissio]

Taken from geigerlog-radpro's page:

"CPM" data is Rad Pro's instantaneous counts per minute value. This value is averaged through Rad Pro's adaptive averaging algorithm.

"CPS" data is the low-level counts per second value. This value is not averaged.

It is therefore expected that statistics of the CPM data not conform to the Poisson distribution.

This should probably be stated in the radpro docs as well. Thanks for pointing this out.

[Gissio]

Can you try again?

radpro-bosean-fs600-2.0rc2-test1-install.bin.zip

Fixed a race condition and an error condition (involving the "ORE" flag) that led to interrupts being generated continuously.

[Dsl71]

Device freezes at connection attempt. Only pulse led is working later on.

[Gissio]

STM32G070 madness again... And now?

radpro-bosean-fs600-2.0rc2-test2-install.bin.zip

With GeigerLog 1.4.3c?

[Dsl71]

oje same as before...

Device freezes at connection attempt. Only pulse led is working later on.

[Gissio]

Ohje.

By the way, please tell the people in the other forum that the KL7 820.403A board has the pulse LED wired directly to the pulse detection circuit. Thus it can't be disabled by software.

The KL7 820.403D board has the pulse LED wired to the MCU, so it is possible to disable the pulse LED by software.

In order to keep things simple, I decided to provide the same firmware for both board revisions.

[Dsl71]

Ah,yes, a new title is welcome. btw happy easter...

[Dsl71]

Meanwhile i got a second Bosean FS-600. Should i send it to you for debugging purposes?

[Gissio]

Your offer is greatly appreciated!

But I don't think it is necessary. It's just that I'm just out of time these days. I don't think it will be hard to fix the serial port problem.

[Gissio]

I finally found some time to work on this. Here goes 2.0rc3test4 for the Bosean FS-600:

radpro-bosean-fs600-2.0rc3-test4.bin.zip

[Dsl71]

Same as before, user Interface freeze, GeigerLog does not recognize device. BTW nice bargraph, instantaneous values not correct. ( 3-7 µSV/h if an impulse comes in, then -.--- if no impulse comes in shortly afterwards.) Persistent settings are working still.

[Dsl71]

Average 4 µSv/h... Normal would be around 0,12 µSv/h here at my place. The new UI look i like a lot.

Statistics: with > 1000 pulses, dead time shows < 40µs. Device voltage: 0.336V.

With a little hoter source instantaneous value looks more correct.

[Gissio]

I found the communications bug! It was a silly "set" that should have been a "get".

I also fixed the instantaneous rate error, which slipped in in the last minute.

There goes 2.0rc6, packaged with the brand-new radpro-flashtool. Just start the flash-bosean-fs600.bat file.

radpro-flashtool-2.0rc3-test6.zip

[Dsl71]

hmm it says syntax error and there is no bin file in the zip Folder firmware is empty.

[Gissio]

Can you try again?

radpro-flashtool-2.0rc3-test6.zip

What version of Windows do you use? Can you post a screenshot of the error?

[Dsl71]

10 Pro 21H2. Flashing worked now.. instantaneous rate looks way better now.

[Dsl71]

AAAANNNNNDDDD... Geigerlog not freezing device hehe

[Dsl71]

Later more, now is 4AM here hehe

[Gissio]

BTW, did you check the display when the alarm goes off?

[Dsl71]

Now i did. Wow nice flashing. And the speed of the instantaneous, if you remove hotter sources... super

[Gissio]

Can we celebrate by closing this issue?

[Dsl71]

Yes, we should close, really great work. BTW flashing the FS 2011 with the new tool didn't work. I used the old method:

st-flash.exe write radpro-fs2011-gd32f150c8-2.0rc3-image.bin 0x08000000

[Gissio]

Can you post the radpro-flashtool messages log?

[Dsl71]

uff, at the next release, just closed the GC.

[Dsl71]

And under a new Topic...

[Gissio]

Closing this thread.

[Gissio]

Now i did. Wow nice flashing. And the speed of the instantaneous, if you remove hotter sources... super

Could you make a video and upload it to YouTube, showcasing your experience with Rad Pro? Would that be too much to ask?