| Author |
 Topic  |
|
|
ullix
Germany
1221 Posts |
 Posted - 08/21/2025 : 05:44:32
|
@EmfDev: I notice some descrepancies in the counter's configuration in firmware:
gmc600+ Re 2.53
gmc500+ Re 2.49
It looks to me like the configuration has changed. Could you please post the most recent configuration of the firmware? |
|
| Reply #1
ullix
Germany
1221 Posts |
Posted - 09/09/2025 : 04:00:12
|
But please, don't block me!
I repeat my request:
@EmfDev: I notice some descrepancies in the counter's configuration in firmware:
gmc600+ Re 2.53
gmc500+ Re 2.49
It looks to me like the configuration has changed. Could you please post the most recent configuration of the firmware? |
 |
|
| Reply #2
EmfDev
2356 Posts |
Posted - 09/09/2025 : 10:47:32
|
EEPOM_PowerOnOff,
EEPOM_AlarmOnOff,
EEPOM_SpeakerOnOff,
EEPROM_IdleDisplayMode,
EEPROM_BackLightTimeoutSeconds,
EEPROM_IdleTitleDisplayMode,
EEPROM_AlarmCPMValueHiByte,
EEPROM_AlarmCPMValueLoByte,
EEPROM_CalibrationCPMHiByte_0,
EEPROM_CalibrationCPMLoByte_0,
EEPROM_CalibrationuSvUcByte3_0,
EEPROM_CalibrationuSvUcByte2_0,
EEPROM_CalibrationuSvUcByte1_0,
EEPROM_CalibrationuSvUcByte0_0,
EEPROM_CalibrationCPMHiByte_1,
EEPROM_CalibrationCPMLoByte_1, //15
EEPROM_CalibrationuSvUcByte3_1,
EEPROM_CalibrationuSvUcByte2_1,
EEPROM_CalibrationuSvUcByte1_1,
EEPROM_CalibrationuSvUcByte0_1,
EEPROM_CalibrationCPMHiByte_2,
EEPROM_CalibrationCPMLoByte_2,
EEPROM_CalibrationuSvUcByte3_2,
EEPROM_CalibrationuSvUcByte2_2,
EEPROM_CalibrationuSvUcByte1_2,
EEPROM_CalibrationuSvUcByte0_2,
EEPROM_IdleTextState,
EEPROM_AlarmValueuSvByte3,
EEPROM_AlarmValueuSvByte2,
EEPROM_AlarmValueuSvByte1,
EEPROM_AlarmValueuSvByte0,
EEPROM_AlarmType,
EEPROM_SaveDataType,
EEPROM_SwivelDisplay,
EEPROM_ZoomByte3,
EEPROM_ZoomByte2,
EEPROM_ZoomByte1,
EEPROM_ZoomByte0,
EEPROM_SPI_DataSaveAddress2,
EEPROM_SPI_DataSaveAddress1,
EEPROM_SPI_DataSaveAddress0,
EEPROM_SPI_DataReadAddress2,
EEPROM_SPI_DataReadAddress1,
EEPROM_SPI_DataReadAddress0,
EEPROM_nPowerSavingMode,
EEPROM_nSensitivityMode,
EEPROM_nCOUNTER_DELAY_HiByte,
EEPROM_nCOUNTER_DELAY_LoByte,
EEPROM_nDisplayContrast,
EEPROM_MAX_CPM_HIBYTE,
EEPROM_MAX_CPM_LOBYTE,
EEPROM_nSensitivityAutoModeThreshold,
EEPROM_nLargeFontMode,
EEPROM_nLCDBackLightLevel,
EEPROM_nReverseDisplayMode,
EEPROM_nMotionDetect,
EEPROM_bBatteryType,
EEPROM_nBaudRate,
EEPROM_nCPMSpeakerOnOffCalib,
EEPROM_nGraphicDrawingMode,
EEPROM_nLEDOnOff,
EEPROM_nHCPMCAL,
EEPROM_nSaveThresholdValueuSv_m_nCPM_HIBYTE,
EEPROM_nSaveThresholdValueuSv_m_nCPM_LOBYTE,
EEPROM_nSaveThresholdMode,
EEPROM_nSaveThresholdValue3,
EEPROM_nSaveThresholdValue2,
EEPROM_nSaveThresholdValue1,
EEPROM_nSaveThresholdValue0,
EEPROM_SSID_0,
//...
EEPROM_SSID_63 = EEPROM_SSID_0 + 63,
EEPROM_Password_0,
//...
EEPROM_Password_63 = EEPROM_Password_0 + 63,
EEPROM_Website_0,
//....
EEPROM_Website_31 = EEPROM_Website_0 + 31,
EEPROM_URL_0,
//....
EEPROM_URL_31 = EEPROM_URL_0 + 31,
EEPROM_UserID_0,
//...........
EEPROM_UserID_31 = EEPROM_UserID_0 + 31,
EEPROM_CounterID_0,
//....
EEPROM_CounterID_31 = EEPROM_CounterID_0 + 31,
EEPROM_Period,
EEPROM_WIFIONOFF,
EEPROM_TEXT_STATUS_MODE,
EEPROM_FAST_ESTIMATE_TIME,
EEPROM_THIRD_PARTY_OUTPUT, //for sending 0xFF per count via serial. This data format used on NETC.com software
EEPROM_HIGH_VOLTAGE_LEVEL_TUBE1,
EEPROM_HIGH_VOLTAGE_LEVEL_TUBE2,
EEPROM_CPM_TUBE_MODE,
EEPROM_CPM_TUBE_DISPLAY,
EEPROM_VOLTAGE_DISPLAY,
EEPROM_DEADTIME_ENABLE,
EEPROM_DEADTIME_TUBE1_HIBYTE,
EEPROM_DEADTIME_TUBE1_LOWBYTE,
EEPROM_DEADTIME_TUBE2_HIBYTE,
EEPROM_DEADTIME_TUBE2_LOWBYTE,
EEPROM_MEDIUMTHRESHOLD_HB,
EEPROM_MEDIUMTHRESHOLD_LB,
EEPROM_HIGHTHRESHOLD_HB,
EEPROM_HIGHTHRESHOLD_LB,
EEPROM_SpeakerVolume,
EEPROM_HV_READING,
EEPROM_TARGET_HV_MSB,
EEPROM_TARGET_HV_LSB,
EEPROM_HV_CALIB,
EEPROM_SS1_0,
EEPROM_SS1_5 = EEPROM_SS1_0 + 5,
EEPROM_SS2_0,
EEPROM_SS2_5 = EEPROM_SS2_0 + 5,
EEPROM_SS3_0,
EEPROM_SS3_5 = EEPROM_SS3_0 + 5,
EEPROM_SS4_0,
EEPROM_SS4_5 = EEPROM_SS4_0 + 5,
EEPROM_ACCURACY_DISPLAY,
EEPROM_DOSE_ALARM_0,
EEPROM_DOSE_ALARM_1,
EEPROM_DOSE_ALARM_2,
EEPROM_DOSE_ALARM_3,
EEPROM_LANGUAGE,
EEPROM_CALIBRATION_CPM_MSB_0,
EEPROM_CALIBRATION_CPM_LSB_5 = EEPROM_CALIBRATION_CPM_MSB_0 + 23,
EEPROM_CALIBRATION_USV0_BYTE3,
EEPROM_CALIBRATION_USV5_BYTE0 = EEPROM_CALIBRATION_USV0_BYTE3 + 23,
EEPROM_DOSIMETER_UNIT,
EEPROM_Save_DateTimeStamp,
EEPROM_Save_DateTimeStamp_SS = EEPROM_Save_DateTimeStamp + 5,
EEPROM_MaximumBytes, |
|
|
| Reply #3
ullix
Germany
1221 Posts |
Posted - 09/10/2025 : 00:48:36
|
Many thanks!
And this is really valid for
gmc600+ Re 2.53
gmc500+ Re 2.49
firmwares?
Because I don't see changes over fw 2.41, yet counters with above firmware do not respond in agreement with 2.41?
|
|
|
| Reply #4
3z_phoenix
7 Posts |
Posted - 09/22/2025 : 12:39:02
|
quote:
Originally posted by ullix
Many thanks!
And this is really valid for
gmc600+ Re 2.53
gmc500+ Re 2.49
firmwares?
Because I don't see changes over fw 2.41, yet counters with above firmware do not respond in agreement with 2.41?
hi ullix,
my hardware is a gmx500+ Re2.42 hardware V5.4
solid running for good a year now.
In traveling through Germany, by time i check the local naturaly background readings in compare with the provided public data on ODL-network:
https://odlinfo.bfs.de/ODL/EN/topics/location-of-measuring-stations/map/map_node.html
until now i found it realy good match inner measuring-tolerance of my device, so i found no need to change anything in firmware until now.
Sure this point for GQelectronics.
I give them my thumbs up :)
kind regards, 3z_phoenix
|
[first rules from my survival-handbook]
1. ...the difference between democracy and anarchy are 3 canceled main meals ~ONLY~
2. ...better have it - but not need, as need it - but not have!
|
|
|
| |
Topic |
|
|
|
New GMC counter configuration?
