Closed gc01noob closed 2 months ago
observation 1: the apm 1.6 bin is 63.5kb radpro 2.0 is 147kb could this be why it completely ignores the 2.0 bin file? is it too big? no matter what i try it acts like there's no new bin file on the drive with 2.0
observation 2: my device had a manufacturer sticker on the box showing it was a 2024 production batch, (the clock was set to 2022 and the LCD ribbon cable dated 2018) - could they have prevented the install of 3rd party firmware on the newer devices coming out the factory?
note: the time/date and all settings were preserved all through this. removing the 1220 battery only resets the clock back to 2022 removing the lithium does nothing removing both does nothing but reset the clock back to 2022, all other settings remain intact.
I'm a bit worried now to remove both batteries and do a long-press on the reset button - this used to work on some other devices like motherboards to fully drain any flash but could also brick other devices for good.
As I don't have a programmer maybe I should just give up until someone else experiences this behaviour......or not.
thanks anyway.
if I copy the 2.0rc5 file (112kb), then unmount and remount the text file changes to be "UNKNOWN.TXT"
2.0 often said "APPERR.TXT" when remounted
after reboot it will say "READY.TXT"
it always needs the reset pressed after any connection to turn off the LED and it then boots.
observations: if i copy radpro 2.0 over (READY.TXT) then unmount then remount (UNKNOWN.TXT) and copy again, unmount, remount (APPERR.TXT) copy again it will disconnect and brick the device. ie no boot just BOOTLOADER to fix it i need to reset, mount (READY.TXT), copy 1.6, unmount, remount (UNKNOWN.TXT), then copy 1.6 again, it will then disconnect the drive, press reset to stop the LED and it boots into 1.6-2 again, keeping all settings and time.
I give up.
ok just before i fully give up: I read the post about a low powered 1220 cell causing issues. I don't seem to have any issues with the RTC, boot times or clock settings or meaured cell voltage but have ordered a new Energizer 1220 cell anyway, should arrive over the weekend, for £2 it's worth a shot. I'll update with my findings.....
official FNIRSI firmware update video looks like WIndows 8 or 10, can anyone confirm they have managed to actually see the drive in Windows 11 23H2 Home or Pro?
not sure why you just closed this....anyway....
Here is how you install on Ubuntu 22.04 if you have the same issues I had above ie not seen in any Windows versions and copying the .bin does nothing, device shows black screen with constant LED....etc. (extra info. This was using a USB 3.1 port on a Dell Precision Xeon laptop with M2200)
viola the GC01 restarts with RadPro 2.0.
it's literally that simple, so here's a wee trick that might be worth sharing with others "copy it twice" before going down the programmer/flashing route.
observation: for some strange reason it stopped my USB keyboard from working properly even after the GC01 was disconnected, was like a 40-50second lag, mouse, ethernet, hdmi etc were all fine, just the keyboard, reboot sorts it.
btw 2.0 seems to work perfectly, I'll try the 2.01 in a few days.
just to add - changed the tube to J321 from the default J613 my background is now back to what it was from the factory ie around 0.18-0.20 uSv/h (correct for my location)
great work btw it all really improves the device (will try PC logging next week)
thanks @Gissio
for completion:
live CPM data is displayed as it updates in the graph window
data displayed in NotePad: ==== Monitor Server Properties ======================================================= Autostarted at: 192.168.0.100 / 8080
==== Connect Rad Pro Device ========================================================== Device successfully connected
Rad Pro : - M - - - - - - - - - -
Mapping is valid
==== Rad Pro Device Info Extended ====================================================
Configured Connection: Port:"COM4"
Device connected.
Hardware ID : FNIRSI GC-01 (APM32F103CB)
Software ID : Rad Pro 2.0
Device ID : 796xx278
Device battery voltage : 4.240V
Device time : 2024-06-22 22:20:25
Tube life time : 3:26:54
Tube life pulse count : 5261
Tube rate : 31.750 CPM
Tube conversion factor : 153.800 CPM/µSv/h
Tube dead time : 0.0876950 s
Tube dead-time compensation : 0.0000000 s
Tube background compensation : 0.000 CPM
Tube HV PWM frequency : 47058.82 Hz
Tube HV PWM duty cycle : 0.5000 %
==== Quick Log ======================================================================= Start logging using Quick Log database 'default.logdb'
==== Get Log ========================================================================= Log database: E:\temp\FNIRSI_GC01_geigercounter\geigerlog-radpro-1.4.3d-windows\data\default.logdb LogFile newly created - available for writing
==== Start Logging ===================================================================
Windows 11 23H2 never sees the GC01 as a USB drive but all seems to work fine in GeigerLog
again thanks @Gissio you've made this into a really useful device.
(if I don't update again it's safe to assume the 2.01 upgrade went well - I'll use the Ubuntu copy twice method from now on)
Hi, I have the APM version with J321 GM tube and standard screen When it booted from new it said "ver 1.6" and read a background between 12-18uSv/hr
Windows 11 would not show the drive, USB 2 or 3 Pro or Home version no matter what buttons I tried. Tried on different PCs too, different hubs, ports etc. Device just boots with no drive created no matter what buttons pressed. eg Hold the power button and it boots then powers off.
In Ubuntu 22.04 it shows the BOOTLOADER drive when powered on - on any USB port. Steps I took: copied the RadPro 2 (later repeated with 2.01b3) - text file said READY.txt but no reboot, just showed 2 files on the drive. red LED stays lit and wouldn't boot removed the cable - also tried unmounting but made no difference red LED stays lit and wouldn't boot pressed reset button. LED goes off but still wouldn't boot but did give BOOTLOADER drive with ERRAPP.txt file each time.
tried 100 different things eg every GC01 firmware, bootloader you shared to try and un-brick it. sometimes the text in the drive says ERRAPP.txt sometimes it said READY.txt always stayed constant red LED and required the reset button and a black screen. LED was constant, longest I left it was 10mins.
copied the 1.6 version from the docs/device/GC01/firmware 2nd time i did this and pulled the cable, then pressed reset it finally booted
it now shows ver 1.6-2 when it boots and my background readings vary from 16-58uSv/hr now.
I'm stumped!
any help would be appreciated as your firmware looks great but i'm scared I brick it again.