I did a couple of tests in which I saw real time CPM reading up to 31000. I was also saving the data in "Every Second" mode.
But then when I downloaded the data the highest CPM data was around 9000. I am not sure what is happening?
The test duration was 5 minutes long (i.e. long enough) and the data logging mode was in "Every Second' mode. It seems the data that is logged is always far more lower than the real-time readings that is displayed for such high CPM cases. I repeated the test a couple of times and with different peak count values as well...and in each case the logged data was far more lower (for the cases with high CPMs).
Also, in each case it took more than 3 mins (almost 4 minutes) for the real-time CPM data to get back/decay to the natural background value... Other users had reported similar behaviour in TOPIC_ID=3661 as well. ( http://www.gqelectronicsllc.com/forum/topic.asp?TOPIC_ID=3661 )
Did you turn off the speaker at that high level? I am just wondering if your sound used more power than it should be. And it affects the data recording.
I noticed a discrepancy between the GCM-300 and GQ GMCounter PRO software when monitoring real time. For example: This morning, I turned on the GMC-300 and started the software in real time mode. After about 3 hours, the GMC-300 has a total count of just over 3000. The software total count shows just over 6000. The CPM on the GMC-300 is 21 and the software shows 16.4.
Great. Thank you. I installed it and now the counts are working correctly. I have been running for just over 1 hour and the software shows .1uSv/h (estimate) but the GMC-300 shows .01uSV/h. I know the measurement is an estimate but I'm just reporting what I see. One more minor thing is that I'm using COM3 and have to manually set that every time I start the software. It's not a big deal but I think the version I was previously using maintained the port setting. Thanks again for the outstanding support. And thanks for the contributions of others in the community. Megatron
If readings are different between the GMC-300 and software, then mst likely the software has a different calibration data. Check the calibration data and synchronize those data with your GMC-300.
In my tests the sound/speaker was turned off. So, I do not think the issue was due to speaker circuitry consuming lots of power.
I had done 5 tests with different target peak CPM values, and for the cases with high CPM counts the logged data was somehow always significantly lower than what I was observing real-time on the LCD screen.