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
 GQ Geiger Muller Counter
 Data in configuration block
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

lyda

Ireland
3 Posts

Posted - 02/01/2017 :  15:34:24  Show Profile  Reply with Quote
I have a GMC-300E. Based on Phil Gillaspy's C++ implementation and a review of the newer data sheet, I've written a version in Go which exports out a Prometheus endpoint.

However when I look at the data block I receive from a
<GETCFG>>
request, there clearly is some data past byte 59.

From Phil's project there's an "External Interface Control Document" which documents the config block in detail, but it's out of date. I can't find a more recent one. I did find a more up to date GQ-RFC1201.txt document on the GQ site, but the other document doesn't seem to be anywhere.

Also I'd be interested in feedback from people with other GMC devices. I've tried to make the code play nice with other models, but only have my own to test with. It's still a work in progress but issues and merge requests are welcome.
Reply #1

ZLM

1062 Posts

Posted - 02/07/2017 :  20:14:14  Show Profile  Reply with Quote
CFG data Offset table. Start from 0
==========================================
PowerOnOff, //to check if the power is turned on/off intended
AlarmOnOff, //1
SpeakerOnOff,
GraphicModeOnOff,
BackLightTimeoutSeconds,
IdleTitleDisplayMode,
AlarmCPMValueHiByte, //6
AlarmCPMValueLoByte,
CalibrationCPMHiByte_0,
CalibrationCPMLoByte_0,
CalibrationuSvUcByte3_0,
CalibrationuSvUcByte2_0, //11
CalibrationuSvUcByte1_0,
CalibrationuSvUcByte0_0,
CalibrationCPMHiByte_1,
CalibrationCPMLoByte_1, //15
CalibrationuSvUcByte3_1,
CalibrationuSvUcByte2_1,
CalibrationuSvUcByte1_1,
CalibrationuSvUcByte0_1,
CalibrationCPMHiByte_2, //20
CalibrationCPMLoByte_2,
CalibrationuSvUcByte3_2,
CalibrationuSvUcByte2_2,
CalibrationuSvUcByte1_2,
CalibrationuSvUcByte0_2, //25
IdleDisplayMode,
AlarmValueuSvByte3,
AlarmValueuSvByte2,
AlarmValueuSvByte1,
AlarmValueuSvByte0, //30
AlarmType,
SaveDataType,
SwivelDisplay,
ZoomByte3,
ZoomByte2, //35
ZoomByte1,
ZoomByte0,
SPI_DataSaveAddress2,
SPI_DataSaveAddress1,
SPI_DataSaveAddress0, //40
SPI_DataReadAddress2,
SPI_DataReadAddress1,
SPI_DataReadAddress0,
PowerSavingMode,
Reserved, //45
Reserved,
Reserved,
DisplayContrast,
MAX_CPM_HIBYTE,
MAX_CPM_LOBYTE, //50
Reserved,
LargeFontMode,
LCDBackLightLevel,
ReverseDisplayMode,
MotionDetect, //55
bBatteryType,
BaudRate,
Reserved,
GraphicDrawingMode,
LEDOnOff,
Reserved,
SaveThresholdValueuSv_m_nCPM_HIBYTE,
SaveThresholdValueuSv_m_nCPM_LOBYTE,
SaveThresholdMode,
SaveThresholdValue3,
SaveThresholdValue2,
SaveThresholdValue1,
SaveThresholdValue0,
Save_DateTimeStamp, //this one uses 6 byte space
Go to Top of Page
Reply #2

lyda

Ireland
3 Posts

Posted - 02/08/2017 :  05:24:00  Show Profile  Reply with Quote
Thanks!
Go to Top of Page
Reply #3

ullix

Germany
83 Posts

Posted - 02/15/2017 :  03:32:05  Show Profile  Reply with Quote
Thx. I can see the calibration Hi and Lo byte for CPM, and think this is a 16 bit unsigned Integer?

But how is the format for CalibrationuSvUcByte3 ... 1?
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.05 sec. Snitz Forums 2000