|T O P I C R E V I E W
||Posted - 08/12/2017 : 06:31:21
If you ever reach more than 200 counts per second (CPS=200, CPM=12000) on your Geiger counter, don't rely on GQ's Data Viewer software, as it may swallow most of your counts.
I fed a signal from a signal generator to the counter as described here http://www.gqelectronicsllc.com/forum/topic.asp?TOPIC_ID=4613 but this time I watched the counts using GQ's DMC Data Viewer Software 2.35 (2016). At 200Hz DV gives the correct answer of CPS=200 and CPM=12006. Calling 'GETCPM' in the GQ Terminal gives 2E E6 in hex, which is 12006 in decimal. OK.
But when you increase the signal to 500Hz, which should give you CPS=500 and CPM=30000, you only get 245 and 14656, resp.! However, again calling 'GETCPM' from the GQ Terminal gives the proper 75 3E or CPM=30014, ok for an ~500Hz signal.
When you increase the signal to 1kHz and 2kHz, your count rate in Data Viewer actually drops to CPM~ 12000...14000, and while at 1kHz the Terminal again gives the correct answer (CPM=60000), at 2kHz the Terminal instead of 120000 gives only 54508. The latter, however, is the consequence of the numeric overflow, which is due to the design of the firmware, and is already known http://www.gqelectronicsllc.com/forum/topic.asp?TOPIC_ID=4613
But why the GQ DMC Data Viewer even ruins a perfectly good count reported by the firmware remains a mystery. I wonder whether the paid-for version of GQ does have this bug too?
In contrast to DV, my program GeigerLog does it correctly ;-)
|1 L A T E S T R E P L I E S (Newest First)
||Posted - 09/30/2017 : 21:31:48
This will be investigated.