GQ Electronics Technical Support Forum Active Users: / Visits Today:
Highest Active Users:
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
 Software Trouble with GMC-600

Note: You must be registered in order to post a reply.
To register, click here. Registration is FREE!

Screensize:
UserName:
Password:
Format Mode:
Format: BoldItalicizedUnderlineStrikethrough Align LeftCenteredAlign Right Horizontal Rule Insert HyperlinkInsert EmailInsert Image Insert CodeInsert QuoteInsert List Spell Checker
   
Message:

* HTML is OFF
* Forum Code is ON
Smilies
Smile [:)] Big Smile [:D] Cool [8D] Blush [:I]
Tongue [:P] Evil [):] Wink [;)] Clown [:o)]
Black Eye [B)] Eight Ball [8] Frown [:(] Shy [8)]
Shocked [:0] Angry [:(!] Dead [xx(] Sleepy [|)]
Kisses [:X] Approve [^] Disapprove [V] Question [?]

   Insert an Image File
Check here to include your profile signature.
    

T O P I C    R E V I E W
ullix Posted - 04/20/2024 : 21:50:39
Like before in the GMC-800 case (http://www.gqelectronicsllc.com/forum/topic.asp?TOPIC_ID=10394) it seems that firmware 2.52 for the GMC-600 is using a configuration memory with settings quite different from both the old 600 and the new 800 configurations? Quite unfortunate.

@EmfDev, could you please post the actual configuration definitions for 2.52 on a GMC-600?

And from which firmware version onward is this valid?
6   L A T E S T    R E P L I E S    (Newest First)
ullix Posted - 04/24/2024 : 04:14:44
Thanks!

This is now included in the latest pre-release pre78, which you find here: https://sourceforge.net/p/geigerlog/discussion/devel/

Should reflect both GMC-500 and GMC-600.
EmfDev Posted - 04/23/2024 : 09:40:08
For 500/600/+

6 point calibration is added with 2.44 rev.

500 and 600 shared the same config since 2.31

500+ new calibration has 6 points. 3 for tube 1, 3 for tube 2.



old 3 point calibration addresses are not used anymore.

PowerOnOff,
AlarmOnOff,
SpeakerOnOff,
IdleDisplayMode,
BackLightTimeoutSeconds,
IdleTitleDisplayMode,
AlarmCPMValueHiByte,
AlarmCPMValueLoByte,
CalibrationCPMHiByte_0,
CalibrationCPMLoByte_0,
CalibrationuSvUcByte3_0,
CalibrationuSvUcByte2_0,
CalibrationuSvUcByte1_0,
CalibrationuSvUcByte0_0,
CalibrationCPMHiByte_1,
CalibrationCPMLoByte_1,
CalibrationuSvUcByte3_1,
CalibrationuSvUcByte2_1,
CalibrationuSvUcByte1_1,
CalibrationuSvUcByte0_1,
CalibrationCPMHiByte_2,
CalibrationCPMLoByte_2,
CalibrationuSvUcByte3_2,
CalibrationuSvUcByte2_2,
CalibrationuSvUcByte1_2,
CalibrationuSvUcByte0_2,
IdleTextState,
AlarmValueuSvByte3,
AlarmValueuSvByte2,
AlarmValueuSvByte1,
AlarmValueuSvByte0,
AlarmType,
SaveDataType,
SwivelDisplay,
ZoomByte3,
ZoomByte2,
ZoomByte1,
ZoomByte0,
SPI_DataSaveAddress2,
SPI_DataSaveAddress1,
SPI_DataSaveAddress0,
SPI_DataReadAddress2,
SPI_DataReadAddress1,
SPI_DataReadAddress0,
nPowerSavingMode,
nSensitivityMode,
nCOUNTER_DELAY_HiByte,
nCOUNTER_DELAY_LoByte,
nDisplayContrast,
MAX_CPM_HIBYTE,
MAX_CPM_LOBYTE,
nSensitivityAutoModeThreshold,
nLargeFontMode,
nLCDBackLightLevel,
nReverseDisplayMode,
nMotionDetect,
bBatteryType,
nBaudRate,
nCPMSpeakerOnOffCalib,
nGraphicDrawingMode,
nLEDOnOff,
nHCPMCAL,
nSaveThresholdValueuSv_m_nCPM_HIBYTE,
nSaveThresholdValueuSv_m_nCPM_LOBYTE,
nSaveThresholdMode,
nSaveThresholdValue3,
nSaveThresholdValue2,
nSaveThresholdValue1,
nSaveThresholdValue0,

SSID_0,
//...
SSID_63 = SSID_0 + 63,

Password_0,
//...
Password_63 = Password_0 + 63,

Website_0,
//....
Website_31 = Website_0 + 31,

URL_0,
//....
URL_31 = URL_0 + 31,

UserID_0,
//...........
UserID_31 = UserID_0 + 31,

CounterID_0,
//....
CounterID_31 = CounterID_0 + 31,

Period,
WIFIONOFF,
TEXT_STATUS_MODE,
FAST_ESTIMATE_TIME,

THIRD_PARTY_OUTPUT, //for sending 0xFF per count via serial. This data format used on NETC.com software

HIGH_VOLTAGE_LEVEL_TUBE1, // for adjusting tube 1 voltage
HIGH_VOLTAGE_LEVEL_TUBE2, // for adjusting tube2 voltage
CPM_TUBE_MODE,
CPM_TUBE_DISPLAY,
VOLTAGE_DISPLAY,
DEADTIME_ENABLE,
DEADTIME_TUBE1_HIBYTE,
DEADTIME_TUBE1_LOWBYTE,
DEADTIME_TUBE2_HIBYTE,
DEADTIME_TUBE2_LOWBYTE,
MEDIUMTHRESHOLD_HB,
MEDIUMTHRESHOLD_LB,
HIGHTHRESHOLD_HB,
HIGHTHRESHOLD_LB,
SpeakerVolume,
HV_READING,
TARGET_HV_MSB,
TARGET_HV_LSB,
HV_CALIB,

SS1_0,
SS1_5 = SS1_0 + 5,
SS2_0,
SS2_5 = SS2_0 + 5,
SS3_0,
SS3_5 = SS3_0 + 5,
SS4_0,
SS4_5 = SS4_0 + 5,

ACCURACY_DISPLAY,

DOSE_ALARM_0,
DOSE_ALARM_1,
DOSE_ALARM_2,
DOSE_ALARM_3,

LANGUAGE,

CALIBRATION_CPM_MSB_0,
CALIBRATION_CPM_LSB_5 = CALIBRATION_CPM_MSB_0 + 23,
CALIBRATION_USV0_BYTE3,
CALIBRATION_USV5_BYTE0 = CALIBRATION_USV0_BYTE3 + 23,

DOSIMETER_UNIT,
ullix Posted - 04/23/2024 : 00:41:48
quote:
It is the same as GMC-500/+.

I'm afraid: No. Unless the 500 firmware also had a change.

Ihab17 has pointed out the most obvious difference, 6 calibration points instead of 3.

The 600 configuration in 2.52 is also different from the GMC-800 1.08, which also codes for 6 points.

Please, which are the current firmware versions for which counter? And what are they? And what are the first versions for the various counters, where this new coding applies?

ihab17 Posted - 04/23/2024 : 00:18:35
quote:
Originally posted by EmfDev

It is the same as GMC-500/+.




GMC 600+ Rev 2.52 has 6 calibration points (seen from the counter)
003541 CPM, 10 uSv/h
031870 CPM, 100 uSv/h
112584 CPM, 500 uSv/h
183243 CPM, 1000 uSv/h
228730 CPM, 2000 uSv/h
282307 CPM, 5000 uSv/h

Is this correct? Is this what GMC-500+ has?
wikilicious Posted - 04/22/2024 : 16:06:06
I really wish GQ would embrace GitHub...
It's a whole lot easier to browse revisions and file bugs/issues...
And most importantly, have a source of "truth"
EmfDev Posted - 04/22/2024 : 10:25:27
It is the same as GMC-500/+.

GQ Electronics Technical Support Forum © Copyright since 2011 Go To Top Of Page
Generated in 0.05 sec. Snitz's Forums 2000