-
Notifications
You must be signed in to change notification settings - Fork 1
/
geigerlog.cfg
1784 lines (1564 loc) · 63 KB
/
geigerlog.cfg
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
## geigerlog.cfg - The GeigerLog configuration file
###############################################################################
## This file is part of GeigerLog.
##
## GeigerLog is free software: you can redistribute it and/or modify
## it under the terms of the GNU General Public License as published by
## the Free Software Foundation, either version 3 of the License, or
## (at your option) any later version.
##
## GeigerLog is distributed in the hope that it will be useful,
## but WITHOUT ANY WARRANTY; without even the implied warranty of
## MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
## GNU General Public License for more details.
##
## You should have received a copy of the GNU General Public License
## along with GeigerLog. If not, see <http://www.gnu.org/licenses/>.
###############################################################################
#__author__ = "ullix"
#__copyright__ = "Copyright 2016, 2017, 2018, 2019, 2020, 2021, 2022"
#__credits__ = [""]
#__license__ = "GPL3"
# Usage:
# All lines beginning with '#' are comments and will be ignored
#
# The structure is:
# [Section]
# # comment
# # Options: value1 | value2 | ...
# # Default = value
# parameter = value
#
# NOTE: non-acceptable values will be silently ignored, and replaced with
# defaults, but a debug message will be printed to the terminal and log file
#
# NOTE: There MUST NOT be more than one entry per parameter, or an error
# will be shown, and the program ends!
#
# NOTE: Exact Capitalization required key words !!!!
#
# NOTE: Don't need an option? Do NOT delete, leave as is.
#
#
# EDITING NOTE:
# If the percent-sign ('%') is to be used anywhere (not recommended), it
# must be entered in duplicate! So, e.g. in a password, having a single '%':
# WRONG: my%password
# RIGHT: my%%password
# The end result in GeigerLog will be a single '%' only: 'my%password'
# (a consequence of Python's string formatting)
[Logging]
# LOGCYCLE:
# GeigerLog's logging cycle in seconds. Can be changed while running GeigerLog
#
# Option auto defaults to 1. Any entry less than 0.1 will be replaced with default.
#
# Options: auto | <any number 0.1 or greater>
# Default = auto
logCycle = auto
[DataDirectory]
# Provide a relative or an absolute path to a folder used to store the data files.
#
#
# A relative path will be relative to the built-in default data folder.
# It must be given as:
# in Linux: beginning WITHOUT slash ('/')
# in Windows: beginning WITHOUT drive name (e.g. 'c:') AND
# beginning WITHOUT backslash ('\') or slash ('/')
#
# An absolute path must be given as:
# in Linux: beginning WITH slash ('/')
# in Windows: beginning WITH drive name (e.g. 'c:')
#
# Option auto defaults to folder 'data' as subdirectory to the GeigerLog folder
#
# Options: auto | <any folder name>
# Default = auto
DataDir = auto
[Network]
# SSID and PASSWORD for your local WiFi network
# SSID: max: 32 ASCII character: 123456789:123456789:123456789:12
# Password: max: 63 ASCII character: pp3456789:pp3456789:pp3456789:pp3456789:pp3456789:pp3456789:pp3
#
WiFiSSID = <mySSID>
WiFiPassword = <myPassword>
[Graphic]
# MOVING AVERAGE:
# Enter the smoothing period in sec.
# 60 sec = 1 min is adequate for seeing CPS recorded data as CPM
# 600 sec = 10 min is adequate for overnight recordings of CPM/CPS
#
# Options: <any number greater than 0 (zero)>
# Default = 600
MovingAverage = 600
[Plotstyle]
# If your plot does not come out as expected, check the geigerlog.proglog file
# for messages; you may have set something unrecognizeable.
# LINEWIDTH:
# The width of the line in points >= 0. A width of 0 (zero) makes the line
# invisible.
#
# Options: <any number greater or equal to 0 (zero)>
# Default = 1
linewidth = 1
# MARKERSYMBOL:
# See allowed symbols at: https://matplotlib.org/stable/api/markers_api.html
#
# Options: "o" (circle) | "s" (square) | "p" (pentagon) | "*" (star) |
# "h" (hexagon) | "+" (plus) | "x" (x) | "D" (diamond)
# Default = o (circle = small cap o, like in oscar)
markersymbol = o
# MARKERSIZE:
# The size of the marker for a datapoint. A marker size of x has the same
# diameter as a line of width x is wide, i.e. the marker would not be
# visible on the line!
#
# GeigerLog reduces the markersize with increasing number of data points. Here
# you specify the starting size. i.e. when only a single data point is shown.
#
# Options: <any number greater or equal to 0 (zero)>
# Default = 15
markersize = 15
[Window]
# HiDPI MONITORS
# High-Resolution Monitors of size 4k and 8k are becoming affordable, but
# represent a challenge for a lot of software. Details in the GeigerLog manual.
#
# This is work-in-progress and may need custom modifications if the auto
# settings do not work well (enough).
# HiDPIactivation
# This option should not give problems on any system.
#
# A known exception is the Raspberry 4 system (status August 2020), where the
# setting must be 'no' or the screen will be distorted and GeigerLog difficult
# to use.
#
# Option auto defaults to 'yes'
#
# Options: auto | yes | no
# Default = auto
HiDPIactivation = auto
# HiDPIscaleMPL
# This compensates any HiDPI scaling for the graphs generated by
# matplotlib. It may not work in all cases.
#
# For a FullHd screen the 'scaling' set in the operating system is typically 100%.
# Any different scaling must be compensated by HiDPIscaleMPL.
#
# For a HiDPI screen the scaling maybe 150%, 200%, 300%, or 400%. Numbers
# different from this list may result in problems in all software!
#
# If the 'auto' option does not give satisfactory results, try these settings:
# scaling: 150% -> HiDPIscaleMPL = 70
# scaling: 200% -> HiDPIscaleMPL = 50
# scaling: 300% -> HiDPIscaleMPL = 33
# scaling: 400% -> HiDPIscaleMPL = 25
# and modify until you find a satisfactory setting. Floating point values ok.
#
# Option auto defaults to a value calculated internally, which may or may not be
# appropriate.
#
# Options: auto | <any number greater than zero>
# Default = auto
HiDPIscaleMPL = auto
# WINDOW WIDTH AND HEIGHT:
# The window is positioned at the top right corner; Dimensions in pixel.
# Depending on Window manager and custom configuration, the default may not
# fit. Change to adapt for your screen and settings.
#
# Default assumes a hardware screen size of 1366x768 with 2 panels of
# height 24 and std window bar.
#
# Options: <any positive number>
# Default width = 1366
# height = 720
windowWidth = 1366
windowHeight = 720
# WINDOW SIZE:
# window size can be auto or maximized. On auto it will be tried to set to
# width x height as defined above. On maximized the window will be maximized.
#
# Option auto defaults to not-maximized
#
# Options: auto | maximized
# Default = auto
windowSize = auto
# WINDOW STYLE:
# The style determines Look & Feel. The default style is determined by the
# system itself. See GeigerLog manual, chapter: Appendix A – Look & Feel
#
# Option auto defaults to the style selected by the operating system.
# Styles perhaps available are: 'Windows', 'Fusion'.
# If an unavailable style is set, then the default is used.
#
# Options: auto | <see manual; correct capitalization required>
# Default = auto
windowStyle = auto
[Manual]
# Manual NAME:
# Filename of the GeigerLog Manual included with the code.
#
# Option auto defaults to the first found file in the GeigerLog
# directory with a filename beginning with 'GeigerLog-Manual'.
# If none found, GeigerLog looks online.
#
# Options: auto | <full name like: 'GeigerLog-Manual-v1.0.pdf'>
# Default = auto
ManualName = auto
[MonServer]
# MonServer will serve web pages to support monitoring GeigerLog with remote
# devices, like a smartphone.
#
# MonServer Autostart
# You can choose to autostart the MonServer by setting this option to yes,
# or to require manual activation by setting it to no
#
# Options: yes | no
# Default = yes
MonServerAutostart = yes
# MonServer SSL
# MonServer can be run either as regular (non-secure) server, or as secure (SSL secured) server.
#
# If SSL is activated here, then in addition a PEM file is needed, which stores the cryptographic
# keys. For details see GeigerLog manual in chapter "Web Enablement".
#
# Options: yes | no
# Default = no
MonServerSSL = no
# MonServer UTC Correction
# Browsers like Firefox and Chrome have the unfortunate property of converting all
# Javascript time formats as if they were UTC times. Other browsers may respond
# differently, so if the automatic correction fails, you can enter the proper
# correction here.
#
# The value entered here is ADDED to the times found by the browsers. E.g., Germany
# has a 1 h offset to UTC in wintertime, and 2h in summertime. So, in summertime
# correct with -2 * 3600 (= minus 7200) sec.
#
# Option auto defaults to the internal calculation.
#
# Options: auto | <any number from -43200 (=-12*3600) to +43200 (=+12*3600)>
# Default = auto
MonServerUTCcorr = auto
# MonServer Port
# While the MonServer's IP is the same as GeigerLog's IP and is autodetected, port numbers
# must be given. Only numbers in the range of 1024 ... 65535, including, are allowed.
# They can be changed during a run. Port numbers may already be in use by other programs,
# so we give it a range of numbers to choose from.
#
# Option auto defaults to the first available port number out of this sequence:
# 8080, 8081, 8082, 8083, 8085, 8086, 8087, 8088, 8089
#
# You can provide your own sequence of one or more comma separated port numbers. The first
# available port out of that number sequence will be taken.
#
# Options: auto | < <any allowed number> [, <any allowed number>] [, <any allowed number>] ... >
# Default = auto
MonServerPort = auto
# MonServerPort = 7070, 7071, 7072, 7073, 7074
# MonServer THRESHOLDS
# Set the threshold values for the Web Monitor gauge transition safe-to-
# caution (green to yellow), and caution-to-danger (yellow to red).
#
# For reasons to chose these levels see GeigerLog manual, chapter:
# "On what grounds do we set the radiation safety levels?"
# Low = 0.9; # 0.9 µSv/h (transition green to yellow)
# High = 6.0; # 6.0 µSv/h (transition yellow to red)
#
# Options auto defaults to: 0.9, 6.0
# NOTE: The first number must be greater than zero, and the second number must
# be greater than first, or both will be reset to default.
#
# Options: auto | < <1st: any number greater 0> , <2nd: any number greater 1st> >
# Default = auto
MonServerThresholds = auto
# MonServer PLOT CONFIG
# Determines what time frame the plots cover, and what variables are shown in the plots.
#
# Three values must be given, length, top plot variable, bottom plot variable.
# The variable numbers are counted from 0 to 11:
# 0=CPM, 1=CPS, 2=CPM1st, 3=CPS1st, 4=CPM2nd, 5=CPS2nd, 6=CPM3rd, 7=CPS3rd, 8=Temp, 9=Press,10=Humid, 11=Xtra
# first value: last minutes of records to show in plot (minimum: 0.1 min, maximum: 1500 min)
# second value: number of the variable for top plot
# third value: number of the variable for bottom plot
# Example: 10, 2, 3, which means: last 10 min, top: CPM1st, bottom: CPS1st
#
# Option auto defaults to 10, 2, 3
#
# Options: auto | < <last minutes>, <variable number top plot>, <variable number bottom plot> >
# Default = auto
# MonServerPlotConfig = auto
MonServerPlotConfig = 300, 6, 7
# MonServer DATA CONFIG
# Determines the averaging periods in minutes for the "Data" web page.
#
# Three values must be given, each is length in minutes for the average shown
# in the 1st, 2nd, 3rd data column.
#
# Option auto defaults to 1, 3, 10
#
# Options: auto | < <at least 1 >, <at least 2 >, <at least 3 > >
# Default = auto
MonServerDataConfig = auto
[Worldmaps]
# Currently only the GQ operated website http://www.gmcmap.com is supported.
# To use it, you have to register there and will obtain:
# - a UserID (probably 5 digits, like: 01234)
# - a CounterID (probably 11 digits like: 12345678901)
#
# WEBSITE and page
# GQ's gmcmap website "http://www.gmcmap.com" and ASP (Active Server Pages) file
# "log2.asp" will be combined with the data to form a typical command like:
# http://www.gmcmap.com/log2.asp?AID=01234&GID=12345678901&CPM=44&ACPM=46&uSV=0.30
# You can use it in any browser to upload any numbers, irrespective of the presence
# of a counter or the numbers being measured. They could be a complete fake!
#
# Website and asp file are the same as in the counter's default config.
# NOTE: the website name MUST NOT be preceded with 'http://'
#
# Options: <website and asp file>
# Default: Website = www.gmcmap.com
# Default: URL = log2.asp
gmcmapWebsite = www.gmcmap.com
gmcmapURL = log2.asp
# GMCMAP USER ID and GMCMAP COUNTER ID
# For testing purposes you can leave both user and counter ID empty or
# with any text. The gmcmap server will then reject any attempt to
# upload data with the response: 'Error! User not found.ERR1'
#
# Options: <any text; but valid is only what you got in registration>
# Default = <placeholder>
# gmcmapUserID = <myUserId>
# gmcmapCounterID = <myCounterID>
gmcmapUserID = <myUserId>
gmcmapCounterID = <myCounterID>
# PERIOD
# Minutes the counter will wait before uploading next values. The
# fastest is 1 min.
#
# Option auto will default to the GMC devices's default of 2.
#
# Options: auto | <any integer number greater 0 (zero) >
# Default = auto
gmcmapPeriod = auto
# WIFI SWITCH
# Switching WiFi of the counter ON or OFF (provided counter has WiFi)
#
# Options: ON | OFF
# Default = ON
gmcmapWiFiSwitch = ON
[ValueScaling]
# Allows to scale the data with a math formula. The formula may include
# math functions. The scaled data will be saved, not the original data!
# see GeigerLog manual chapter: ValueScaling and GraphScaling
#
# As example:
# A temperature sensor might have a known offset and read 0.3 °C too
# high. This could be corrected by setting: Temp = VAL - 0.3
#
# Option: val | <math formula> | <empty>
# Default: val
#
# If 'val' is the only thing entered, or <empty> (nothing entered), then
# no modification will be applied, and the original value will be kept.
#
CPM = val
CPS = val
CPM1st = val
CPS1st = val
CPM2nd = val
CPS2nd = val
CPM3rd = val
CPS3rd = val
Temp = val
Press = val
Humid = val
Xtra = val
[GraphScaling]
# This does ONLY change how the variable is plotted; it does NOT change the
# value of the variable as saved, different from the 'ValueScaling' case above!
#
# As example:
# The Air Pressure, which is mostly around 1000 +/- 30 hPa, will be
# plotted as: Press = Press - 1000 to better fit on the ambient scale
#
# Option: val | <math formula> | <empty>
# Default: val
#
# If 'val' is the only thing entered, or <empty> (nothing entered), then
# no modification will be applied, and the original value will be kept.
#
CPM = val
CPS = val
CPM1st = val
CPS1st = val
CPM2nd = val
CPS2nd = val
CPM3rd = val
CPS3rd = val
Temp = val
Press = val
# Press = val - 1000
Humid = val
Xtra = val/100
#
#
# Tubes
#
#
[TubeSensitivities]
# For a detailed discussion see GeigerLog manual in chapter: Appendix G – Calibration.
# This chapter also holds a list of some tubes and their known or claimed sensitivities,
# and gives help for conversions using a different system of units.
#
# Tube sensitivities are in units of "CPM / (µSv/h)", specified individually for each
# of a max of 4 tubes - the higher the number, the more sensitive the tube is!
#
# The tubes are strictly associated with variables, as shown in the Option list:
#
# Option auto defaults to these values:
# Value Naming Associated with
# [CPM / (µSv/h)] variables
# TubeSensitivityDef = 154.0 Default tube CPM, CPS
# TubeSensitivity1st = 154.0 1st tube CPM1st, CPS1st
# TubeSensitivity2nd = 2.08 2nd tube CPM2nd, CPS2nd
# TubeSensitivity3rd = 154.0 3rd tube CPM3rd, CPS3rd
#
# Any entries with values of 0 (zero) or negativ will be changed to default.
#
# Options: auto | <any positive number>
# Default: = auto
TubeSensitivityDef = auto
TubeSensitivity1st = auto
TubeSensitivity2nd = auto
TubeSensitivity3rd = auto
#
#
# DEVICES
#
#
[GMC_Device]
# This is valid for all GMC Geiger counter devices. The specific version of the
# counter will be auto-discovered.
#
# GMC ACTIVATION
# to use (yes) or not use (no) a GMC counter.
#
# Options: yes | no
# Default = no
GMC_Activation = no
# FIRMWARE BUGS
# GQ's firmware has bugs - no surprise for any software. What makes is bad is
# that GQ is dragging their feet when it comes to a complete disclosure of what
# the problem is, and which firmware versions are effected.
# This impacted not only GeigerLog but also their own Dataviewer software.
# So here is an attempt to allow at least for the GeigerLog user to add some
# work-arounds in case more versions should be affected than currently known.
# FIRMWARE BUGS: LOCATION BUG
# The "saving-to-memory" of the counters uses tags (special byte sequences) to
# itentify certain properties needed for the proper parsing of the data.
# Unfortunately, GQ changed the meaning of some tags when they introduced
# 3 and 4 byte storage values, making these firmwares incompatible with previous
# versions. This was reverted, but devices with that wrong firmware were sold.
# See Reply #50, 21.8.2018:
# http://www.gqelectronicsllc.com/forum/topic.asp?TOPIC_ID=5331
#
# Option auto defaults to: GMC-500+Re 1.18, GMC-500+Re 1.21
#
# Options: = auto | <Full Version ID>, <Full Version ID>, <Full Version ID>, ...
# Default = auto
GMC_locationBug = auto
# FIRMWARE BUGS: SPIR BUG:
# See the GeigerLog manual for an explanation of the firmware bugs.
#
# Option auto uses these device specific settings:
# 300 series: no
# 300E series: yes
# 320 series: yes
# 500 series: no
# 600 series: no
#
# Options: auto | yes | no
# Default = auto
GMC_SPIRbugfix = auto
# FIRMWARE BUGS: SPIRPAGE:
# The memory is organized in pages of 4k (4096) bytes. Due to firmware bugs,
# the history readout may or may not be possible in 4k pages, but only in 2k
# pages. In addition, a bugfix may have to be applied! See GeigerLog manual
# for details.
#
# Option auto uses these device specific settings:
# 300 series: 2k
# 300E series: 4k - bugfix needed!
# 320 series: 4k - bugfix needed!
# 500 series: 2k - may work also with 4k, 8k, 16k but better make sure!
# 500+ series: 4k - may work also with 8k, 16k but better make sure!
# 510 series: 2k - may work also with 4k, 8k, 16k but better make sure!
# 600 series: 2k - may work also with 4k, 8k, 16k but better make sure!
#
# Options: auto | 2k | 4k | 8k | 16k
# Default = auto
GMC_SPIRpage = auto
# FIRMWARE BUGS: FAST ESTIMATE TIME:
# "Fast EstimateTime" is a configuration setting in Device GMC-500+ version
# 2.24 and likely in all other models with a firmware supporting this mode.
# Fortunately it is not present in the GMC-300 and GMC-320 counters.
# This mode is active by default in its worst setting! It invokes an algorithm,
# which is not disclosed by GQ, and which results in a severe distortion of all
# CPM recordings, and may even create counts when there are none.
#
# It has settings of 60, 30, 20, 15, 10 and 5 seconds, plus a 'dynamic' (equal to 3)
# setting, which apparently simply stands for 3 seconds. The latter is the default
# and the worst setting.
#
# It looks like this algorithm is switched off at 60 seconds, therefore this
# setting is strongly recommended! GeigerLog gives a warning when a GMC counter
# is activated with this setting at anything besides 60 seconds.
#
# Option auto sets this to 60. Illegal options will be ignored and replaced with auto.
#
# Options: 3, 5, 10, 15, 20, 30, 60
# Default = auto
GMC_FastEstTime = auto
# MEMORY:
# This is the memory for data storage. It is 64kB in the older devices, and
# 1 MB in the newer ones. As long as the GMC counter can be recognized,
# GeigerLog will automatically make the correct setting. If for any reason
# this needs to be changed, it can be done here.
#
# 64kB = 2**16 = 65 536 Bytes; fixed setting
# 1MB = 2**20 = 1 048 576 Bytes; fixed setting
# auto = either 64kB or 1MB, set by GeigerLog depending on counter model
#
# Option auto uses these device specific settings:
# 300 series: 64 kB
# 320 series: 1 MB
# 500 series: 1 MB
# 600 series: 1 MB
#
# Options: auto | 64kB | 1MB
# Default = auto
GMC_memory = auto
# CONFIGURATION MEMORY SIZE:
# This is the configuration memory, not the data storage memory! On the older
# 3XX units it was 256 bytes. On the newer 500, 600 units it is 512 bytes.
#
# Option auto uses these device specific settings:
# 300 series: 256 bytes
# 320 series: 256 bytes
# 500 series: 512 bytes
# 600 series: 512 bytes
#
# Options: auto | 256 | 512
# Default = auto
GMC_configsize = auto
# VOLTAGE:
# This is the BATTERY voltage, NOT the ANODE voltage!
#
# In the 300 series the battery voltage is reported as a single byte, and the voltage
# is byte/10; e.g. a byte value of 41 is 4.1 Volt. In the 500 and 600 series the
# voltage is reported as a 5 byte ASCII byte string; e.g. b'3.76v' is 3.76 Volt.
#
# Option auto uses device specific settings
#
# Options: auto | 1 | 5
# Default = auto
GMC_voltagebytes = auto
# ENDIANNESS:
# For the three bytes of the calibration µSv/h values the order of bytes has
# changed in the latest firmware. It is now:
# 300 series: little-endian
# 500 / 600 series: big-endian
#
# Option auto uses these device specific settings
#
# Options: auto | little | big
# Default: = auto
GMC_endianness = auto
# NBYTES:
# The number of bytes returned by the CPM, CPS, CPM1st, CPS1st, CPM2nd, and
# CPS2nd commands. This is 2 bytes for the older 300 series counters, and
# 4 bytes for the newer ones series 500, 600 with firmware 1.18 or later.
#
# Options: auto | 2 | 4
# Default = auto
GMC_Bytes = auto
# WiFi Index:
# Points to the configuration setting to be used. If the WiFi settings read out
# by GeigerLog seem to be wrong, try another index.
#
# Current settings:
# none: 300 series (no WiFi)
# 2: only 320Re 5.XX
# 3: old 500er, 600er (firmware 1.x)
# 4: new 500er, 600er (firmware 2.x)
#
# Option auto uses above settings
#
# Options: auto | none | 2 | 3 | 4
# Default = auto
GMC_WifiIndex = auto
# GMC_DEVICE SERIAL PORT:
# This is the serial port used by the GMC Geiger Counters.
#
# When set to auto, GeigerLog will attempt to auto-detect the port. If it fails you
# can try to configure the port explicitly, but chances are something else is wrong.
#
# The name of the serial port is different in Linux and Windows, see:
# GeigerLog manual: Appendix B – Connecting Device and Computer using a Serial Connection
#
# Options: Linux: auto | /dev/ttyUSB0 | /dev/ttyUSB1 | /dev/geiger | ... and others
# Windows: auto | COM3 | COM4 | COM12 | ... and others
# Mac: auto | /dev/tty.USBSERIAL | /dev/tty.PL2303-xxx | ... and others
#
# Default = auto
GMC_usbport = auto
# GMC_DEVICE ID:
# This forces GeigerLog to connect only when the specified GMC device is present. The
# specification can be a version of given at any length (GMC-5, GMC-500, GMC-500+Re 1.27)
# and can in addition contain the serial number of the counter.
#
# Examples:
# GMC_ID = GMC-5, F4884567890ABCDE # use the first found GMC-500 or GMC-510 counter but
# # only when having the serial No F4884567890ABCDE
# GMC_ID = GMC-300, None # use the first found GMC-300 counter with any
# # serial No
#
# Option auto defaults to None, None
# (i.e. both Model and Serial Number are ignored; the first found GMC counter will be used)
#
# Options: auto | < <Model>, <Serial Number> >
# Default = auto
GMC_ID = auto
# VARIABLES:
# All GMC counter provide CPM and CPS readings. Only the GMC-500+ device,
# having 2 tubes installed, and with at least firmware 1.18, provides
# additional individual readings for each tube as counts per MINUTE (CPM1st
# and CPM2nd) and counts per SECOND (CPS1st and CPS2nd).
#
# The '1st' and '2nd' settings can be used for all other GMC counters as well,
# and will not result in an error, but will provide the exact same as CPM or
# CPS! For consistency, GeigerLog will use "CPM1st, CPS1st" as default variables
# for all GMC counters, even if they have only a single tube, like the 300 and
# 600 series.
#
# NOTE: On the GMC-500+ both CPM and CPS are useless numbers as they are the
# sum (!) of both tubes: CPM=CPM1st+CPM2nd, CPS=CPS1st+CPS2nd. This is
# no meaningful information!
#
# Option auto defaults to:
# only on 500+: CPM1st, CPS1st, CPM2nd, CPS2nd
# on all other: CPM1st, CPS1st
#
# Options: auto | <any combination of CPM, CPS, CPM1st, CPS1st, CPM2nd, CPS2nd>
# Default = auto
# GMC_Variables = auto
GMC_Variables = CPM1st, CPS1st
[AudioCounter]
# Using the PC's internal default audio input (often the microphone) or a USB
# Sound Card to listen to audioclicks from a Geiger counter.
#
# The clicks must reach close to the maximum of the default audio input. The
# input amplification of the PC's sound device should be adjusted accordingly.
# See the manual for pictures.
# AudioCounter ACTIVATION
# to use (yes) or not use (no) an AudioCounter
#
# Options: yes | no
# Default = no
AudioActivation = no
# AudioCounter DEVICE
# The audio device is specified with 2 values: 1st is input, 2nd is output.
# The available devices can be shown by running: 'python3 gdev_audio.py' in the
# GeigerLog directory. The output will be similar to this (some lines removed):
#
# Available Sound Devices:
# 0 HDA Intel HDMI: 0 (hw:0,3), ALSA (0 in, 8 out)
# ...
# 4 HDA Intel PCH: ALC887-VD Analog (hw:1,0), ALSA (2 in, 0 out)
# ...
# 7 USB Audio Device: - (hw:2,0), ALSA (1 in, 2 out)
# 8 hdmi, ALSA (0 in, 8 out)
# ...
# * 10 default, ALSA (32 in, 32 out)
#
# Here a total of 11 (0 ... 10) devices are available. Only #4, #7, and #10 have
# inputs available. The star in the leftmost column of #10 marks the default
# device. It also has the name 'default', but it can have any other name, and
# still be the default device! Device #7 is an USB sound card, while the others
# are devices internal to this desktop computer.
#
# If a device is specified as 'None', then the system's default will be used.
# Otherwise specify its name or its number, examples:
# None, None
# HDA Intel PCH, 10
# USB, hdmi
# 7, 8
# The last two lines specify the same devices in this example
#
# Option auto defaults to None, None
#
# Options: auto | None, None | < <InputDevice Name|Number>, <OutputDevice Name|Number> >
# Default = auto
AudioDevice = auto
# AudioCounter LATENCY
# Can be used to finetune the AudioCounter behavior. From experience, and
# dependent on the sound card, values in sec from 0.05 ... 2.0 may be helpful.
#
# Option auto defaults to 1.0, 1.0
#
# Options: auto | <<any number greater than zero> , <any number greater than zero>>
# Default = auto
AudioLatency = auto
# AudioCounter PULSEMAX
# The audio input is normally at zero, and for 16 bit resolution (as used here)
# the maximum signal is thus plus/minus 32768. However, depending on operating
# system this may be shown as plus/minus 1 or any other range.
# Confirm via menu: Device -> AudioCounter Series -> Plot Audio
#
# Option auto defaults to 32768
#
# Options: auto | <any number greater than zero>
# Default = auto
AudioPulseMax = auto
# AudioCounter PULSEDIR
# The audio input is normally at zero, and any pulses are either positive or
# negative. Pulses from a GMC300E+, or a SGP-001 are negative
# Confirm via menu: Device -> AudioCounter Series -> Plot Audio
#
# Option auto defaults to negative
#
# Options: auto | negative | positive
# Default = auto
AudioPulseDir = auto
# AudioCounter Threshold
# If possible the audio input should be adjusted such that the Geiger pulses
# reach the negative/positive limit, but does not exceed them. The number
# given here sets the percentage of the maximum possible signal which must
# be reached in order to trigger a count. 60[%] has been a good value so far.
# Confirm via menu: Device -> AudioCounter Series -> Plot Audio
#
# Option auto defaults to 60
#
# Options: auto | < a positive number less than 100>
# Default = auto
AudioThreshold = auto
# AudioCounter VARIABLES:
# All CPM* and CPS* are available (CPM, CPS, CPM1st, CPS1st, CPM2nd, CPS2nd,
# CPM3rd, CPS3rd), but only a max of 2 variables can be specified.
# If 2 variables are specified, then one must be of the M type, and one of
# the S type (per minute, per second).
#
# Option auto defaults to 'CPM3rd, CPS3rd'
#
# Options: auto | <any combination of CPM*, CPS*, see above>
# Default = auto
AudioVariables = auto
[RadMonPlusDevice]
# A device from here: https://sites.google.com/site/diygeigercounter/gk-radmon
#
# The RM+ can act as a Geiger counter providing CPM data, and with an optional
# BME280 sensor additionally acts as an environmental monitor for Temperature,
# Pressure, and Humidity. The RM+ must be configured to send its data to an
# MQTT server. This server's IP must be made known to GeigerLog.
#
# NOTE: The server must be using protocol=mqtt.MQTTv311! The RadMon device is
# not able to connect to a server using the protocol=mqtt.MQTTv31
#
# The RM+ update cycle can be configured at the RM+, but it is best set to
# 60 sec for CPM readings, and with an extra of about 7 sec for reading the
# environmental sensor and for sending the data, the total cycle is about 67 sec.
#
# GeigerLog connects to the MQTT server for new data and logs them. GeigerLog
# can read all 4 variables. If no new data are found, the log displays empty
# values, but they won't be saved in the records. Logging/displaying/analyzing
# will not be impacted.
#
# Demonstration Mode
# A Demo-Mmode can be activated in GeigerLog, which defines my personal
# RadMon+ device as active, and allows any user of GeigerLog to read genuine
# real-time data from a RadMon+.
# RadMonPlusDevice ACTIVATION
# to use (yes) or not use (no) a RadMonPlusDevice
#
# Options: yes | no
# Default = no
RMActivation = no
# RadMonPlusDevice SERVERIP:
# The server IP can be either a numerical IP like "10.0.0.81" (in local network),
# or "198.41.30.241", or a URL like "mqtt.eclipse.org".
#
# NOTES: previously used server "iot.eclipse.org" is out-of-service!
# previously used server "mqtt.eclipse.org" is out-of-service (since
# December 12, 2020)
#
# newly chosen server: "test.mosquitto.org", see: http://test.mosquitto.org/
#
# Other IP options: https://github.com/mqtt/mqtt.github.io/wiki/public_brokers
# - broker.hivemq.com (tested ok, see: http://www.mqtt-dashboard.com/)
#
# Test: If you have the mosquitto clients installed try:
# mosquitto_sub -h test.mosquitto.org -t "geigerlog/#" -v
#
# Option auto becomes "test.mosquitto.org" (IP: 5.196.95.208)
#
# Options: auto | <IP address>
# Default = auto
RMServerIP = auto
# RadMonPlusDevice SERVER PORT:
# Standard port is 1883
#
# Option auto becomes 1883
#
# Options: auto | <port number>
# Default = auto
RMServerPort = auto
# RadMonPlusDevice SERVER FOLDER:
# This must be the same folder as defined during the setup of the RadMon+
# device. For details search for MQTT. In MQTT these folders are called 'topics'.
# CAUTION: you may get flooded with useless messages when you enter no proper
# folder!
#
# A blank (' ') is not allowed in the folder name! If no final '/' is given, it
# will be auto-added
#
# Options: <folder as defined in your RadMon+ device, ending with '/'>
# Default = /
# Demo-Mode: = geigerlog/
RMServerFolder = geigerlog/
# RadMonPlusDevice TIMEOUT:
# establishing a connection in a local network takes ~10 milliseconds, but to a
# remote server on poor connections might take several hundred milliseconds.
# To be on the safe side a long timeout is set.
#
# Option auto defaults to 5 (sec)
# NOTE: any number zero or negative will be changed to default
#
# Options: auto | <any positive number>
# Default = auto
RMTimeout = auto
# RadMonPlusDevice VARIABLES:
# The RM+ can provide only CPM data, or only Temp, Press, Humid, Xtra (Temperature,
# Pressure, Humidity, RSSI) data, or all of them.
#
# The CPM values can be mapped to any of the CPM* variables. Any CPS* setting
# will be ignored.
#
# As the Temp, Press, Humid data come from one sensor, they are either all present
# or none, yet you can select or ignore them individually for logging.
#
# Xtra is the RSSI (WiFi strength) reported by the RadMon
#
# Option auto defaults to 'CPM3rd, Temp, Press, Humid'
#
# Options: auto | <any combination of Temp, Press, Humid, Xtra and one of (CPM, CPM1st, CPM2nd, CPM3rd)>
# Default = auto
RMVariables = auto
[AmbioMonDevice]
# A device in development. The AmbioMonDevice provides Geiger counter
# CPM / CPS data, and with its BME680 sensor provides environmental
# data for Temperature, Pressure, Humidity, and Air Quality.
#
# The AmbioMon Device acts as a web server and has its own IP Address.
# GeigerLog needs this address to connect to the AmbioMon Device via
# local or remote internet connection. GeigerLog can read and log all
# variables, and it can download any history stored on the AmbioMonDevice.
#
# AmbioMonDevice ACTIVATION
# to use (yes) or not use (no) an AmbioMonDevice
#
# Options: yes | no
# Default = no
AmbioActivation = no
# AmbioMonDevice SERVER IP:
# This must be given to GeigerLog, it cannot be auto-discovered. It can
# be numeric, like '198.41.30.241', or a domain name, like 'mydevice.com'.
#
# If you use auto, then GeigerLog will use the IP of the computer it is running
# on. See GeigerLog manual for how you can use that for a getVarIndexator device.
#