GQ has not disclosed the location of their new, extra "calibration" points, and I cannot find them. It will take more effort; I think I'll pass on this for the moment. See my Reply #1 in this GQ-forum post: http://www.gqelectronicsllc.com/forum/topic.asp?TOPIC_ID=10240
Last edit: ullix 2023-07-10
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yep! Just think how much better the quality, repetability and accuracy of GQ geiger counters
would be if Ullix was on the payroll and the software, well he already has them beat there.
Bob
😄
2
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@Bob, I am lacking words after reading your Reply #2 on GQ topic http://www.gqelectronicsllc.com/forum/topic.asp?TOPIC_ID=10240 . This triple-underlines the competencies of GQ's programmers. What a difference to the Radiacode software - not to mention GeigerLog ;-).
I'd like to take another look at the GMC-600 configuration. Please, use the latest pre49 version
With the GMC-600 connected, just start GL with python geigerlog -dvw devel, log for a few seconds, and stop. Post the geigerlog.proglog file. Nothing else needed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Darn, you had it running on your slow computer? This limits the proglog file size to 100k in your case, and it had already created the zip file, which contains the file with the info which I need :-(
Please, always post both, the geigerlog.proglog and the geigerlog.proglog.zip file.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK here is your request using my faster machine. On this machine no .zip file was written.
BTW I am going to reach out to GQ and request a replacement 600+ based on your findings that the clock is "Kaput" LOL!
I removed the database file I forgot that you did not need it.
Bob
It matches the "Standard Software" data (as expected) but shows no trace of "Pro Software" data!
When you have a chance, I'd like to get some more data:
Use the counter directly, and go to its "calibration" settings. There open each "Calibration point" and write down the values you find for "CPM" and for "µSv" (should be "µSv/h" but this is a different matter). Then post all 6 value pairs.
LOL! Love the new thread name.
I mailed off my 600+ back to GQ electronics today for servicing. I asked if they will include a calibration certificate and Mark at GQ stated that they will. I also included this statement in a reply: "Please ensure your team does a good job. I am sure Ullix will have me
run it through it's paces upon it's return LOL!"
I hope it arrives back soon I have vacation trips planned for the first two weeks of August.
I'll report back at the new thread once I and my 600+ are available to do so.
Bob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Opening the file as 'rb' in Python... the index of interest:
print(hist_data[97046:97046+4].hex(" ")) # 55 aa 05 55
print(hist_data[97137:97137+4].hex(" ")) # 55 aa 05 00
It was luck that between those two indices I added a note (manually via tedious device buttons) "ULLIX" so it's easy to spot in the "Show History with Parse Comments" view.
I saved the uploaded file directly from geigerlog connection to device.
This is meant to be a place which allows data uploads you can't do anywhere else.
You can post as "Anonymous" without registering at SourceForge, but registering makes things easier.
Last edit: ullix 2023-04-22
Here is the configuration file data from my 600+ as requested at the GQ forum thread.
Bob
GQ has not disclosed the location of their new, extra "calibration" points, and I cannot find them. It will take more effort; I think I'll pass on this for the moment. See my Reply #1 in this GQ-forum post:
http://www.gqelectronicsllc.com/forum/topic.asp?TOPIC_ID=10240
Last edit: ullix 2023-07-10
Ok thank you Sir. I read through your post at the GQ forum above, lets see if the GQ folks reply.
Bob
Thank Ullix for the great work! I have seen your reply! Hilarious!
Yep! Just think how much better the quality, repetability and accuracy of GQ geiger counters
would be if Ullix was on the payroll and the software, well he already has them beat there.
Bob
@Bob, I am lacking words after reading your Reply #2 on GQ topic http://www.gqelectronicsllc.com/forum/topic.asp?TOPIC_ID=10240 . This triple-underlines the competencies of GQ's programmers. What a difference to the Radiacode software - not to mention GeigerLog ;-).
I'd like to take another look at the GMC-600 configuration. Please, use the latest pre49 version
NOTE: Development Versions are now in forum GeigerLog Development Versions
With the GMC-600 connected, just start GL with
python geigerlog -dvw devel, log for a few seconds, and stop. Post thegeigerlog.proglogfile. Nothing else needed.It is not detecting my GMC 600+ I did enable it in the Config file? See files.
Bob
Last edit: Bob 2023-07-19
Oh sh.., I forgot to reset one setting. In the config file
geigerlog.cfgsearch forGMC_ID. You'll find:set it back to:
Then try it again, sorry.
Last edit: ullix 2023-07-19
NP That did it! see file below.
Bob
Darn, you had it running on your slow computer? This limits the proglog file size to 100k in your case, and it had already created the zip file, which contains the file with the info which I need :-(
Please, always post both, the
geigerlog.proglogand thegeigerlog.proglog.zipfile.OK here is your request using my faster machine. On this machine no .zip file was written.
BTW I am going to reach out to GQ and request a replacement 600+ based on your findings that the clock is "Kaput" LOL!
I removed the database file I forgot that you did not need it.
Bob
Last edit: Bob 2023-07-20
I got what I needed, thank you.
It matches the "Standard Software" data (as expected) but shows no trace of "Pro Software" data!
When you have a chance, I'd like to get some more data:
Use the counter directly, and go to its "calibration" settings. There open each "Calibration point" and write down the values you find for "CPM" and for "µSv" (should be "µSv/h" but this is a different matter). Then post all 6 value pairs.
P.S.: please post those new data at the new topic GMC Counter Calibration Chaos
Last edit: ullix 2023-07-21
LOL! Love the new thread name.
I mailed off my 600+ back to GQ electronics today for servicing. I asked if they will include a calibration certificate and Mark at GQ stated that they will. I also included this statement in a reply: "Please ensure your team does a good job. I am sure Ullix will have me
run it through it's paces upon it's return LOL!"
I hope it arrives back soon I have vacation trips planned for the first two weeks of August.
I'll report back at the new thread once I and my 600+ are available to do so.
Bob
Hi, This is the data related to https://gqelectronicsllc.com/forum/topic.asp?TOPIC_ID=10389
@wikiliciuos: attached the *** .bin** data after parsing by GeigerLog into the * .hisdb format.
Load into GeigerLog and select "Show History Data with Parse Comments" to see the parsing comments.
Opening the file as 'rb' in Python... the index of interest:
It was luck that between those two indices I added a note (manually via tedious device buttons) "ULLIX" so it's easy to spot in the "Show History with Parse Comments" view.
I saved the uploaded file directly from geigerlog connection to device.