| T O P I C R E V I E W |
| ullix |
Posted - 02/21/2023 : 01:08:33
It looks like GQ is replacing their old Geiger counters with model names GMC-300E+, GMC-320+, and GMC-320+V5 with the "S"-series.
At present it looks like the new counters use the same motherboards as the old ones. They should already be recognized by GeigerLog.
However, I do not know what - if any - changes were applied to the firmware, which might make GeigerLog stumble in working with them.
If you own one of these new counters, please post here and we can figure out any changes!
Some more info on these counters is found in this topic:
http://www.gqelectronicsllc.com/forum/topic.asp?TOPIC_ID=10112
|
| 31 L A T E S T R E P L I E S (Newest First) |
| ullix |
Posted - 03/10/2023 : 09:37:32
It looks like something is messed up. I suggest to delete the complete GeigerLog installation ( simply delete the folder), and start over.
No need for admin!
|
| tedssled |
Posted - 03/10/2023 : 07:04:29
GeigerLog runs fine. It was when I tried to run it in debug mode that I got a whole bunch of error messages at the command line. They appear to all be related to not having permission to write to the log file.
I have been running it without Admin permissions but when I was trying to produce the debug info for ullix since I have a new 320S I got all those errors. That's why I tried it using an Admin command prompt
I now understand why I couldn't get to Extended Info. I was logging at the time. Once I stopped and restarted GeigerLog I was able to get the Extended Info.
Two different problems. One was getting the Extended Info which is resolved and one with the generation of the geigerlog.prolog information which is not resolved. |
| ihab17 |
Posted - 03/10/2023 : 02:41:50
quote:
Originally posted by tedssled
However, the geigerlog.proglog file had issues. Lots of issues. It looks like a bunch of permission issues. I started GeigerLog from an Admin Command Prompt and from the subdir that GeigerLog is located in and I also checked and assigned full control to the file for all users.
I captured the output but it's big and I don't want to post it here.
Would it be valuable to you if I upload it to the Sourceforge site?
There are tons of lines similar to this:
PermissionError: [Errno 13] Permission denied: 'C:\\geigerlog-v1.4.1\\geigerlog\\data\\geigerlog.proglog'
09 11:20:38.438 EXCEPTION in WriteFileA appending: [Errno 13] Permission denied: 'C:\\geigerlog-v1.4.1\\geigerlog\\data\\geigerlog.proglog'
From what you wrote, it looks you are using Windows OS to run GeigerLog. Make sure you read Ullix's post here https://www.gqelectronicsllc.com/forum/topic.asp?TOPIC_ID=6771 and also see reply # 19, where I posted the necessary steps to successfully run GeigerLog on Windows |
| ullix |
Posted - 03/10/2023 : 01:34:38
I am confused about the steps you took, and about which results relate to which action :-(
First, GeigerLog NEVER NEEDS admin rights! Start it only as regular user! Doing otherwise results in problems related to the type of installation of Python itself.
Second, the "Extended Info" on a GMC counter is inaccessible when you are logging. This is because all GMC counter get a hiccup when you do both reading and writing. Stop logging, and you get the full info.
Third, don't hesitate to post even lengthy stuff on SourceForge.
Lastly, when posting any "fixed-width font text", such as what is in the NotePad, to this GQ forum, it is always better to frame it inside
"code" brackets by clicking the "#" button in the editor. It preserves the layout and makes reading easier.
The good news: I know now how the 320S counter is responding. I replaced the update file on https://sourceforge.net/p/geigerlog/discussion/general/thread/94272a7434/
with a new "gdev_gmc.py - update to GL1.4.3-pre2.zip". Install this first before starting GL as regular(!) user.
|
| tedssled |
Posted - 03/09/2023 : 09:32:40
However, the geigerlog.proglog file had issues. Lots of issues. It looks like a bunch of permission issues. I started GeigerLog from an Admin Command Prompt and from the subdir that GeigerLog is located in and I also checked and assigned full control to the file for all users.
I captured the output but it's big and I don't want to post it here.
Would it be valuable to you if I upload it to the Sourceforge site?
There are tons of lines similar to this:
PermissionError: [Errno 13] Permission denied: 'C:\\geigerlog-v1.4.1\\geigerlog\\data\\geigerlog.proglog'
09 11:20:38.438 EXCEPTION in WriteFileA appending: [Errno 13] Permission denied: 'C:\\geigerlog-v1.4.1\\geigerlog\\data\\geigerlog.proglog' |
| tedssled |
Posted - 03/09/2023 : 09:26:37
When I restarted GeigerLog with the debug switches I was able to access the Extended Info.
==== Monitor Server Properties =======================================================
Autostarted at: 192.168.0.194 / 8080
==== Connect GMC Device ==============================================================
GMC Device 'GMC-320SRe 1.03' was detected at port: COM4 and baudrate: 115200
ATTENTION A GMC device 'GMC-320SRe 1.03' was detected, but of a so far unknown model!
Review the 'Extended Info' for this GMC device. You may have to edit the
configuration file geigerlog.cfg to adapt the settings to this new device.
Device successfully connected
==== Device Mappings =================================================================
Mappings as configured in GeigerLog's configuration file geigerlog.cfg.
Device : CPM CPS CPM1st CPS1st CPM2nd CPS2nd CPM3rd CPS3rd Temp Press Humid Xtra
--------------------------------------------------------------------------------------
GMC : - - M M - - - - - - - -
Mapping is valid
==== GMC Device Info Extended ========================================================
Configured Connection: Port:'COM4' Baud:115200 Timeouts[s]: R:3 W:1
Connected Device: GMC-320SRe 1.03
Configured Variables: CPM1st, CPS1st
Applicable Tube Sensitivity:
CPM1st / CPS1st: 154 CPM / (µSv/h)
Computer Date & Time: 2023-03-09 11:16:25.315
Device Date & Time: 2023-03-09 11:16:38
Device is faster than computer by 12.7 sec
Device Power State: ON
Extended Info:
Device Alarm State: OFF
Device Alarm Level CPM: Selected : CPM: 100 (= µSv/h: 0.649)
Device Alarm Level µSv/h: NOT selected: µSv/h: 0.500 (= CPM: 77 )
Device Speaker State: ON
Device Light State: Light: ON
Device Hist. Saving Mode: CPS, save every second
Device Max CPM: 65535 (invalid if equal to 65535!)
Device Battery Voltage: 4.1 Volt
Device Battery Type Setting: ReChargeable
Device Gyro data: X=0xffb0, Y=0xff30, Z=0xc3d0 (65456, 65328, 50128)
(only GMC-320 Re.3.01 and later)
Device Hist. Threshold Mode: CPM
Device Hist. Threshold CPM: 100
Device Hist. Threshold µSv/h: 0.500
Device Hist. Write position: Byte #90201 (@8.602% of memory)
Device Serial Number: F7F4C57911CEBB
Device Calibration Points: CPM = µSv/h CPM / (µSv/h) µSv/h/CPM
Calibration Point #1: 105 = 0.650 161.54 0.00619
Calibration Point #2: 1050 = 6.500 161.54 0.00619
Calibration Point #3: 10500 = 65.000 161.54 0.00619
GeigerLog's Configuration for Counter's Firmware:
Memory (bytes): 1,048,576
SPIRpage Size (bytes): 4,096
SPIRbugfix (True | False): True
Config Size (bytes): 256
Voltagebytes (1 | 5): 1
Endianness (big | little): little
Bytes in CP* records: 2 |
| tedssled |
Posted - 03/09/2023 : 08:45:48
The Extended Info item is grayed out.
I will follow the instructions for a bug report before I do the update to 1.4.3
It may take me a day or two.
|
| ullix |
Posted - 03/09/2023 : 02:41:37
quote:
Originally posted by tedssled
Can I help in any way?
Yes, you can: Please, start GeigerLog with your counter 320S connected. Then click on the menu: Device --> Connect Devices. If successful, click: Device --> GMC Series --> Show Extended Info.
This will print a bunch of lines into NotePad. Copy all of this and post here.
If not successful, please follow the advice given in chapter "Bug report" in the GeigerLog manual. Posting the resulting files is not possible in this GQ forum, so please go to the GeigerLog discussion site https://sourceforge.net/p/geigerlog/discussion/general/
and create a new topic (Being a member of SourceForge makes this easier, but you don't have to be. Your topic will then be held back until I formally approve it.)
Edit:
I just created a prerelease update to accommodate the "S" series counter.
Follow instructions at topic: "GeigerLog Prerelease Update from 1.4.1 to 1.4.3" from https://sourceforge.net/p/geigerlog/discussion/general/thread/94272a7434/
@tedssled: your data can be posted at this topic as well
|
| ullix |
Posted - 03/09/2023 : 01:53:24
@EmfDev: So my shiny new 300S has firmware 1.03, and so has the new 320S from Daniel (see Reply #1). And this firmware is already outdated? Can I get the new firmware version?
Even if the 320S-WiFi is not released yet, I am sure you already have its future configuration?
Once the 300E devices will have this firmware, what will their version become? You can't use the existing "1.03" numbering, as the "1.xyz" numbers are already taken on even older versions?
It would make it so much easier if you present a clear outline of your firmware plans!
|
| EmfDev |
Posted - 03/08/2023 : 16:54:00
@ullix new values are not present on older versions. These enums are for both 300S and 320S and soon will be used by 300E and 320V4 to avoid confusion. So far we did not release any 320S-V5 yet.
|
| tedssled |
Posted - 03/08/2023 : 10:56:08
I just received a 320S. It seems to be working with GeigerLog although there is a warning when the unit is detected that it is an unknown device. I am running v 1.4.1. I installed Python, GeigerLog, edited the cfg file to enable discovery of the GC devices and that's it.
Can I help in any way?
|
| ullix |
Posted - 03/08/2023 : 00:35:04
@EmfDev: Many thanks!
If I am not mistaken then these enums are only for the 300S? Or also for the 320S?
They are not for the 320S-WiFi, as there aren't any entries needed for WiFi! And also, those can't be taken from the old 320E-WiFi, as some config positions, which previously had been used for WiFi, are now in use for FET, RTC, alarmVol at positions 69, 70, 71.
Could you please also provide the enums for the 320S-Wifi model?
Re the RTC: This 300S has a Real-Time-Clock? I have to say I doubt it, because the clock is as bad or worse than the clock from the old 300E+, at a deviation increase of approx 10 sec per day. I can't imagine a real RTC chip is as bad as that?
EDIT:
Actually, this can't be the right enums. I am comparing with "GMC-300SRe 1.03", where I find this config memory read out by GeigerLog:
==== GMC Device Configuration ========================================================
The size of the configuration memory is: 256 bytes
|Index | |------------ HEX -------------| |------------------ DEC ------------------|
0:000: 00 00 00 02 01 00 00 64 00 69 0 0 0 2 1 0 0 100 0 105
10:00A: 66 66 26 3f 04 1a 00 00 d0 40 102 102 38 63 4 26 0 0 208 64
20:014: 29 04 00 00 82 42 00 00 00 00 41 4 0 0 130 66 0 0 0 0
30:01E: 3f 00 01 00 00 00 00 00 FF FF 63 0 1 0 0 0 0 0 255 255
40:028: FF FF FF FF 00 01 00 78 15 FF 255 255 255 255 0 1 0 120 21 255
50:032: FF 3c 00 02 FF 01 00 fc 0a 00 255 60 0 2 255 1 0 252 10 0
60:03C: 01 0a FF FF FF FF FF FF FF 3c 1 10 255 255 255 255 255 255 255 60
70:046: 17 03 07 0a 36 19 23 3 7 10 54 25
Remaining 180 values up to address 255 are all '0xFF=255'
You see that FET value 60(dec) at position 69dec is immediately followed by Date&Time (2023-03-07 10:54:25). There is no RTC and AlarmVol setting! So, what is the firmware of the given enums?
|
| EmfDev |
Posted - 03/07/2023 : 16:06:16
EEPOM_PowerOnOff,
EEPOM_AlarmOnOff, //1
EEPOM_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,
nPowerSavingMode,
nSensitivityMode, //45
nCOUNTER_DELAY_HiByte,
nCOUNTER_DELAY_LoByte,
nDisplayContrast,
MAX_CPM_HIBYTE,
MAX_CPM_LOBYTE, //50
nSensitivityAutoModeThreshold,
nLargeFontMode,
nLCDBackLightLevel,
nReverseDisplayMode,
nMotionDetect, //55
bBatteryType,
nBaudRate,
nCPMSpeakerOnOffCalib,
nGraphicDrawingMode,
nLEDOnOff,
nHCPMCAL,
nSaveThresholdValueuSv_m_nCPM_HIBYTE,
nSaveThresholdValueuSv_m_nCPM_LOBYTE,
nSaveThresholdMode,
nSaveThresholdValue3,
nSaveThresholdValue2,
nSaveThresholdValue1,
nSaveThresholdValue0,
FAST_ESTIMATE_TIME,
RTC_OFFSET,
ALARM_VOLUME,
//this one uses 6 byte space and always keep it at last
Save_DateTimeYear, //this one uses 6 byte space and always keep it at last
Save_DateTimeMonth,
Save_DateTimeDate,
Save_DateTimeHour,
Save_DateTimeMinute,
Save_DateTimeSecond,
Disregard the numberings and some of those may have been obsolete. |
| ullix |
Posted - 03/07/2023 : 09:18:45
quote:
Originally posted by EmfDev
I will check it with our devs about the header files.
Any chance to ever get them? |
| EmfDev |
Posted - 02/27/2023 : 12:46:09
I will check it with our devs about the header files. |
| ullix |
Posted - 02/27/2023 : 03:43:52
In continuing my checks of the 300S counter, I tested another famous source of radioactivity: Cocoa Powder, the very stuff which is used to prepare chocolate drinks, much liked by kids (of all ages).
Cocoa is rich in potassium, much richer than the famous bananas. See my successful but cumbersome work with bananas "Going Banana" : https://sourceforge.net/projects/geigerlog/files/Articles/GeigerLog-Going%20Banana-v1.0.pdf/download
I tested cocoa power like this one: https://www.amazon.de/Bensdorp-Kakao-Kakaopulver-Trinkschokolade-Getr%C3%A4nkepulver/dp/B003SGDC8U
If you want to repeat the experiment, get cocoa similar to the above. But avoid everything which claims to be "enriched" by whatsoever - you want it as pure and clean as possible!
Cocoa is a breeze to test with any Geiger counter, and the GMC-300S fared very well. Here is the result. C1 and C2 are two variants of cocoa powder, both from the supermarket. The higher counts (C1) come from the above linked-to Bensdorp variety.
Of course I checked Poisson on all sections, and all are fine. FET had been switched off (i.e. set to 60[sec]).
But this showed a new problem with this counter. As so far the FET setting had been located in the upper half of the 512 bytes configuration memory, and now the "S" variants have only 256 bytes (like the old 300E series), the FET setting is at a new location (which is 69dec). And since it is now sitting on a place which previously was used by the WiFi setting, several settings will have to move to accommodate the "S" series.
@EmfDev: You had posted an enum setting for the other counters in Reply#2 of http://www.gqelectronicsllc.com/forum/topic.asp?TOPIC_ID=10080
This is obviously not valid for the "S" series. Can you please post an update which includes the "S" series?
|
| ullix |
Posted - 02/27/2023 : 01:36:56
Ah, come on. This is a highly reputable business, which also "develops, produces, and deals with suitcases, bags, and textiles"
https://firmeneintrag.creditreform.de/91052/8191024500/SCHEUFER_TECHNOLOGIES_GMBH
When you read further, you find:
quote:
Die letzte Änderung im Handelsregister wurde am 11.01.2023 vorgenommen. Das Unternehmen wird derzeit von einem Manager ( 1 x Liquidator) geführt
Google translates this as:
quote:
The last change in the commercial register was made on January 11, 2023. The company is currently run by one manager (1 x liquidator).
Oooopsy. If I am not mistaken, since January 11 of this year this business is in liquidation :-/
Today this company is no longer listed on Amazon. I guess returning the counter may no longer be an option?
Another company is now offering the 300S for 112 + 54(!) shipping. Yeehaw, what a deal. Looks like a really bad start for GQ.
|
| Damien68 |
Posted - 02/26/2023 : 07:54:04
Googling "SCHEUFER Technologies Gmbh" it found it at the right address and it says it's an electric bike store. pity there is no street view.
I expected a screwdriver factory :=) |
| ullix |
Posted - 02/26/2023 : 01:23:29
On my counter - neither the counter itself nor anywhere on the box, nor on any paper stuff inside - is a "Made in ..." label.
The box carries this imprint at the side, which looks like an address to a German distributor (note the Chinese sounding email name Mark Zhang):
The interesting part is, when you try to open "scheufer.com" in a browser. First it's redirecting you to https://european-recycling.de/, and gives this output:
One can ping this site, and gets:
quote:
ping european-recycling.de
ping: european-recycling.de: Name or service not known
So, this site does not even exist!
One can ping and "whois" the scheufer.com site. This site does exist, and it is registered in Germany, but that's all one can find.
Yeah, this is the way to build confidence in the consumer!
|
| traveler |
Posted - 02/25/2023 : 22:28:21
No USA on the case... but what does it matter it wasn't made in the usa either, was it? |
| Daniel Burnette |
Posted - 02/25/2023 : 12:17:17
quote:
Originally posted by ullix
Yes, that tube may well be a "J305", due to the fact that the tube manufacturer saves labeling efforts by giving different tubes the same name :-/. There is a short (~90mm) and a long (~107mm) variant of the tube, both named identically "J305".
The black wrapper is supposed to mitigate the light-sensitivity of the tubes; don't take it off. I haven't yet tested it for efficiency ;-)
@ullix: Interesting. Thank you for the valuable information. |
| ullix |
Posted - 02/25/2023 : 01:05:58
Yes, that tube may well be a "J305", due to the fact that the tube manufacturer saves labeling efforts by giving different tubes the same name :-/. There is a short (~90mm) and a long (~107mm) variant of the tube, both named identically "J305".
The black wrapper is supposed to mitigate the light-sensitivity of the tubes; don't take it off. I haven't yet tested it for efficiency ;-)
I am now proud owner of a GMC-300S! I'll do a review later, but first impressions:
- the case is basically identical in size to the old 300E counters (actually a half mm smaller in each dimension).
- the electronic board looks identical at first glance. The CPU is smaller (couldn't read the print)
- the keys are as lousy as on the old 300E. You press the up- or down-key, and the cursor jumps not 1 but 2 or even 3 steps. You can reach a certain menu item only "iteratively" by alternating between going up and down until you made it. De-bouncing a switch is one of the microchip programming-beginner's practice tasks. Frustrating.
- GeigerLog can deal with these "S" counters by simply replacing the "E" for an "S" in the counter-recognition part of the software. I'll release an GeigerLog update later when I have done a few more tests. If you need this urgently, tell me, and I'll give a temporary workaround.
- the firmware now includes the not only annoying but plainly wrong "FET" setting, on by default in its worst setting.
- the clock is as bad as in the old "E", losing about 10 sec per day.
- the tube sensitivity set in the firmware is now 162 CPM/(uSv/h) compared to the old M4011 setting of 154. Meaningful? Who knows. I still think that neither tube has ever been calibrated.
Bottom line: really no difference between "E" and "S". What should you buy? Draw your conclusion based on this:
|
| Daniel Burnette |
Posted - 02/24/2023 : 12:02:12
I just got off the phone with John at GQ ELECTRONICS (206)-829-8093 in Seattle.
I asked what GC Tube is installed in the GMC-320S as it has a black film wrapped around and i did not want to take it off?
I wanted to go to the source since there was really no confirming information on what GC Tube was installed. Even on Amazon. Reviewers stating incorrect info as well.
John stated he would edit the listings to reflect which GC Tube is installed.
John stated the GMC-320S has the J305 installed in this unit.
|
| Daniel Burnette |
Posted - 02/23/2023 : 11:16:30
@ullix - Thanks for the heads up. I will stay away from him and not trust his info. You guys know best. Thanks -DB
quote:
Originally posted by ullix
Yeah, this "Vlad S." is a copy&paste BS producer. Ignore all of him.
|
| Damien68 |
Posted - 02/23/2023 : 06:36:07
quote:
Originally posted by ihab17
quote:
Originally posted by ullix
Yeah, this "Vlad S." is a copy&paste BS producer. Ignore of all him.
Totally agree with you. His review seems to be an expert reviewer wannabe. Here is his original review. https://www.amazon.com/gp/customer-reviews/R2FNWIFHS10454?ref=va_cr_lb
#MeToo, totally agree. :=) |
| ihab17 |
Posted - 02/23/2023 : 05:32:38
quote:
Originally posted by ullix
Yeah, this "Vlad S." is a copy&paste BS producer. Ignore of all him.
Totally agree with you. His review seems to be an expert reviewer wannabe. Here is his original review. https://www.amazon.com/gp/customer-reviews/R2FNWIFHS10454?ref=va_cr_lb |
| ullix |
Posted - 02/23/2023 : 00:51:14
Yeah, this "Vlad S." is a copy&paste BS producer. Ignore all of him. |
| ihab17 |
Posted - 02/22/2023 : 23:48:39
quote:
Originally posted by Daniel Burnette
quote:
The GQ GMC-320S is equipped with an M4011 Geiger-Muller tube that is sensitive to alpha, beta, and gamma radiation.
ALPHA??????? heck no! This is incorrect
|
| Daniel Burnette |
Posted - 02/22/2023 : 10:43:13
@ullix: Thanks for the GeiderLog software link. Good info. I will check it out.
***Amazon Reviewer Vlad S. Stated GQ GMC-320S is equipped with an M4011 Geiger-Muller tube. Not sure how reliable his info is, but he does have 900 Reviews.
Vlad S. - VINE VOICE
4.0 out of 5 stars Reliable consumer grade Geiger counter with some very cool features. But it has a few shortcomings.
Reviewed in the United States #127482;#127480; on November 2, 2022
The GQ GMC-320S is equipped with an M4011 Geiger-Muller tube that is sensitive to alpha, beta, and gamma radiation. It doesn't tell us what kind of radiation is being detected though, just the total amount. A tube is located at the bottom of the device along a series of vents on the back. This tube isn't extremely sensitive to alpha rays because even a piece of paper can block alpha radiation, it can't even penetrate human skin. The tube is wrapped in some sort of thin foil to counter the problem that the M4011 tube can be sensitive to light, which can result in higher readings. This meter makes a distinctive ticking sound when it detects a radioactive particle. This is really a simulation of the sound that first-gen Geiger counters produced as part of their detection process and became the de facto standard for such devices.
AMAZON SELLER RESPONSE TO DIFFERENCE 300S vs 320S:
Question: Difference between this unit and 300s other than price?
Answer: This version has larger internal memory for data logging. The temperature sensor for temperature checking. Also, it has direction sensor to rotate the display when unit is upside down. The GMC-320S also has more graphic display option for users to choose.
By GQ Electronics LLC SELLER on February 17, 2023
Much larger data saving memory. Gyro/Swivel display. Threshold Data Logging etc..
By GQ Electronics LLC SELLER on February 17, 2023.
|
| ullix |
Posted - 02/22/2023 : 01:25:00
The best information would be found by using my GeigerLog software. It is Python based software, so it will run on Windows, Linux, Mac and others. https://sourceforge.net/projects/geigerlog/
If you don't want to install it: some limited info can be had from GQ software, but it is not straight forward.
The firmware version would be a first step, but likely not enough.
According to EmfDev, the tube is NOT a M4011 (http://www.gqelectronicsllc.com/forum/topic.asp?TOPIC_ID=10112 Reply #14) but he doesn't say what it is. I find this secrecy around tech specs rather annoying.
|
| Daniel Burnette |
Posted - 02/21/2023 : 15:53:25
I have one of the 320S Units. I needed one for my Evac Backpack. I have had it nearly 2 months now from Amazon. I really like it. It has everything i need in a GC. M4011 Tube. Just the basics, there is no wi-fi connectivity so i can not connect. I must enter my readings manually which is fine. Dated June 2022. Revision: 1.03 - Not sure where to look for firmware. I will check the menu. |
|
|
