| Author |
Topic  |
|
|
ullix
    
Germany
1255 Posts |
Posted - 07/04/2026 : 05:08:20
|
The GMC-800 is being sold now in a fully new hardware version. It reports itself as GMC-800Re2.00, and is incompatible with previous versions of GeigerLog and RadPro!
GeigerLog has now been adapted; its latest version is available as a pre-release on GeigerLog's development site. Use pre08 or later: https://sourceforge.net/p/geigerlog/discussion/devel2/
The use of a new microchip raises hopes for getting fast performance. Well, the opposite was the case! For the first time ever I had in insert delays (!) at various stages of the GeigerLog code, just to accomododate this one counter. Imagine, even the old GQ clunkers GMC-300 were faster!
Adapting RadPro might take a bit longer; GQ has resorted to grinding off all labels on the chips, which does throw a few extra wrenches into anyone's attempts to create alternative firmware. 

And the much dreaded FET "feature" has been runied even further. The picture shows the outcome for a Poisson test for FET=5 in the top pic. This is supposed to look like the bottom pic, which is the History read out from the very same GMC-800Re2.00. The data are there; they are just ruined by GQ's infamous algorithm !

Draw your own conclusions.
|
|
| Reply #1
ullix
    
Germany
1255 Posts |
Posted - 07/07/2026 : 00:54:44
|
This counter keeps buggy surprises: Every now and then it shows a bold message across the screen, reading:
WiFi Busy ...
To my knowledge, this GMC-800Re2.00 counter does NOT have WiFi? So, just another bug? |
 |
|
| Reply #2
BrianBurns

1 Posts |
Posted - 07/09/2026 : 04:20:28
|
| All good now? |
:) |
Edited by - BrianBurns on 07/09/2026 04:21:08 |
 |
|
| Reply #3
ullix
    
Germany
1255 Posts |
Posted - 07/10/2026 : 00:05:36
|
| No. |
 |
|
| Reply #4
ullix
    
Germany
1255 Posts |
Posted - 07/25/2026 : 04:30:05
|
@EmfDev: if I am not mistaken then counter GMC-800Re2.00 has Ome rearragenemt in the firmware, also making it incompatible with previous version.
In particular the 512 Bytes configuration has changed. At least location and or format of calibration is different.
Would you mind to post the new configuration setting? Is it using BIG or LITTLE coding? |
Edited by - ullix on 07/26/2026 00:46:31 |
 |
|
| Reply #5
ullix
    
Germany
1255 Posts |
Posted - 07/26/2026 : 00:53:10
|
Well, it looks like nothing has really changed, except that the firmware is loaded with bull****! How else would you call this "calibration"?

This is what is read out by GeigerLog, and I verified at the device that is shows exactly the same. Negative CPM values, yeah, that is the ticket for a successful calibration!
Perhaps GQ hasn't noticed it yet, but there is this very new concept for Quality Control. Highly recommended?
How can such utter nonsense possibly pass the release of a new device?
|
 |
|
| |
Topic  |
|