| T O P I C R E V I E W |
| toplard |
Posted - 09/30/2017 : 12:00:36
Dear All,
My GQ GMC320+v4.25 is working perfectly with GQ Data Logger, so the USB serial link must be wokring fine.
I want to use rrdtool to poll it periodically write to an RRD and graph it on a web server.
But... when I use the commands in the readme I get the following results which I cannot fathom. It works for some commands but not others - some respond, others not, others respond with garbage, so it makes no sense.
Setup is RPi, Fedora 25 Server armv7, 115200 8N1.
I get the same results under windows 10 using Putty.
See link for screen shot: https://photos.app.goo.gl/OiW5tMoMfBsDmLfx1
<GETVER>> OK
<HEARTBEAT1>> OK
<HEARTBEAT0>> OK
<POWEROFF>> OK
<FACTORYRESET>> OK
<REBOOT>> OK
<POWERON>> OK
Heartbeat returns garbage
<GETCPM>>
<GETVOLT>> returns a *
<SPIR[A2][A1][A0][L1][L0]>> returns garbage
<GETCFG>> returns garbage
<ECFG>>
<WCFG[A0][D0]>>
<key[D0]>>
<GETSERIAL>> returns garbage
<CFGUPDATE>>
<SETDATEYY[D0]>>
<SETDATEMM[D0]>>
<SETTIMEHH[D0]>>
<SETTIMEMM[D0]>>
<SETTIMESS[D0]>>
<SETDATETIME[YYMMDDHHMMSS]>>
<GETDATETIME>>
<GETTEMP>>
<GETGYRO>> returns garbage
* blanks = no response
Thoughts anyone?
|
| 2 L A T E S T R E P L I E S (Newest First) |
| ullix |
Posted - 10/01/2017 : 02:31:40
An even better documentation is available on Phil Gillaspy's site as GQ-GMC-ICD.* documents ( https://sourceforge.net/projects/gqgmc/files/gqgmc/ )
My GeigerLog program's device interaction is largely based an his docu. If you understand Python, look into GeigerLog's source code for programming details (file gcommands.py). Note that some firmware bugs and firmware design don't make this straight forward; further complicated by differences in the 500 model. Explained in the GeigerLog manual.
All found here: https://sourceforge.net/projects/geigerlog/
|
| ZLM |
Posted - 09/30/2017 : 21:02:09
Some commands return data in hexdecimal value. See details from GQ-RFC1201 protocol:
http://www.gqelectronicsllc.com/downloads/download.asp?DownloadID=62
|
|
|
