GQ Electronics Technical Support Forum


GQ Electronics Technical Support Forum
Home | Profile | Register | Active Topics | Members | Search | FAQ
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 GQ Electronics Forums
 2.GQ Geiger Muller Counter
 Some questions/hints GMC 300E+
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

Erwin55

Germany
9 Posts

Posted - 06/27/2018 :  23:19:29  Show Profile  Reply with Quote
Dear All,

some behavior (bug or feature?) of the GMC-300E+ (Re 4.20), record mode every minute:

1. When writing a comment in the counter memory it is not issued once in the dataset but repeatedly issued every hour in the dataset. Even if you change the comment to blank you will get ",,," as comment every hour. The only chance is to switch the unit off to clear the comment completely. I think this behavior is unusual/annoying and should be changed in a later firmware to write once.

2. I expected, that the memory is working like a ring buffer. When my counter reached the memory limits after approx. 50 days (record mode every minute), the whole memory was cleared (FF) and it starts recording at zero. Hence if you know it, you can life with that but a behavior like a ring buffer would be better.

Cheers Alex
Reply #1

ZLM

1193 Posts

Posted - 06/29/2018 :  07:18:22  Show Profile  Reply with Quote
Thanks for the information.

1. that need to be checked.
2. the memory works like ring. When the maximum memory used, it will back to beginning. But it will not erase entire memory, only erase the part needed.
Go to Top of Page
Reply #2

ullix

Germany
346 Posts

Posted - 06/30/2018 :  01:27:47  Show Profile  Reply with Quote
My own GMC-300E+ initially had Firmware 4.20, and it did work as a ring-buffer. There is an in-depth explanation to its working in the manual of my GeigerLog software, Appendix E, available here: https://sourceforge.net/projects/geigerlog/

You can see it for yourself by downloading the history with GeigerLog and then look at the created *.his file with an editor. If there had been an overflow, and the ring-buffer did kick into action, the file may look like this (total number of lines ~30000):

#HEADER, File created from History Download Binary Data
#ORIGIN: Downloaded 2018-06-30 11:10:34.568 from device 'GMC-300Re 4.22'
#FORMAT: '<#>ByteIndex,Date&Time, CPM' (Line beginning with '#' is comment)
#45186,2018-05-20 03:56:26, Date&Time Stamp; Type:'CPS, save every second', Interval:1 sec
 45198,2018-05-20 03:56:27,    420
 45199,2018-05-20 03:56:28,    840
.....
 65642,2018-05-20 09:14:36, 130980
 65647,2018-05-20 09:14:37, 135540
 65652,2018-05-20 09:14:38, 126480
#  121,2018-06-24 17:43:36, Date&Time Stamp; Type:'CPM, save every minute', Interval:60 sec
   133,2018-06-24 17:44:36,   2137
   138,2018-06-24 17:45:36,   2188
   143,2018-06-24 17:46:36,   2210
.....
 45183,2018-06-30 13:25:15,     12
 45184,2018-06-30 13:26:15,     10
 45185,2018-06-30 13:27:15,      8

You see that it begins at index 45186 and increases to 65652, when it switches to the beginning at 121. From there it increases to 45185, the last index before the first in this file. Truly a ring buffer.

If your output does not look similar, then try a FACTORYRESET. If still no change a repair may be needed.
Go to Top of Page
Reply #3

Erwin55

Germany
9 Posts

Posted - 08/16/2018 :  21:49:21  Show Profile  Reply with Quote
Thank you ullix and ZLM,

in fact the counter memory works like a ring buffer. At the last cycles the ring buffer worked perfectly. I don't know what had happend some months ago and why.

Thanks
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
GQ Electronics Technical Support Forum © Copyright since 2011 Go To Top Of Page
Generated in 0.08 sec. Snitz Forums 2000