Table of Contents
  1. 1 Hardware
  2. 2 Communication Protocol v1
    1. 2.1 Commands and Responses
    2. 2.2 Log Interpretation
  3. 3 Communication Protocol v2
    1. 3.1 Commands and Responses
    2. 3.2 Log Interpretation
  4. 4 Floating Point Representation
    1. 4.1 Examples
  5. 5 Linux Software: GammaScoutUtil
    1. 5.1 Prerequisites
    2. 5.2 Getting Started
    3. 5.3 Downloads

1 Hardware

That's the device this page is all about:

Gamma Scout W/ALERT with some Thorium welding electrodes

This is a picture of the "Gamma Scout with Alert" Geiger Counter. It has a USB interface on the bottom which can be used to connect the device to a PC in order to query the logged radiation data. There are also other members of the Gamma Scout Family:

  1. Gamma Scout without Alert ("Gamma Scout Basic")
  2. Gamma Scout with Alert ("Gamma Scout Alert")
  3. Gamma Scout with Alert and Online Mode ("Gamma Scout Online")

The devices most likely differ only in their firmwares, the hardware seems quite identical. Some of the devices have a RS232 interface via a 9-pin SUB-D connector and others (most new ones) have USB. There also are at least two different protocol versions around (from hereon referred to a protocol v1 and protocol v2) which are both supported by the GammaScoutUtil. There seems to be a correlation between the firmware version, the number of digits in the display and the protocol version. As someone suggested on the Internet (I'm unsure how reliable that information is), all Gamma Scouts with firmware version <= 5.43 have a 3-digit display and use protocol version v1. All Gamma Scouts with firmware version >= 6.02 have a 4-digit display and use protocol version v2. You can find out the firmware version by pressing the "Battery" button and then the "Enter" button. For the "Gamma Scout Online", the GammaScoutUtil only supports the features that the "Gamma Scout Alert" also has (i.e. Online Mode is not supported at the moment). This is only because I have no access to a online device -- if anybody has such a device and wants to get it running, drop me a note with some details and I'll try to include support for it.

For the USB versions, the hardware which is used is a FTDI FT232RL is used which is nicely supported by Linux already:

joequad joe [~]: lsusb -v
[...]
Bus 001 Device 017: ID 0403:d678 Future Technology Devices International, Ltd 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0         8
  idVendor           0x0403 Future Technology Devices International, Ltd
  idProduct          0xd678 
  bcdDevice            6.00
  iManufacturer           1 Dr Mirow
  iProduct                2 GammaScout USB
  iSerial                 3 GSNJR316
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              2 GammaScout USB
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
Device Status:     0x0000
  (Bus Powered)
joequad joe [~]: dmesg
[...]
usb 1-3.2: new full speed USB device using ehci_hcd and address 17
ftdi_sio 1-3.2:1.0: FTDI USB Serial Device converter detected
usb 1-3.2: Detected FT232RL
usb 1-3.2: Number of endpoints 2
usb 1-3.2: Endpoint 1 MaxPacketSize 64
usb 1-3.2: Endpoint 2 MaxPacketSize 64
usb 1-3.2: Setting MaxPacketSize 64
usb 1-3.2: FTDI USB Serial Device converter now attached to ttyUSB0

It therefore appears as a serial interface (/dev/ttyUSBn). A query I did with the vendor (Dr. Mirow) in order to get access to the protocol details remained unanswered. Therefore I re-engineered the v2-protocol and wrote a device driver with which you can use the device. Luckily, the protocol was quite easy to understand. For the protocol v1 some info could be found on the net and I had the help of Jörg Wartenberg, who kindly provided the test data from his device (since I do not own a protocol v1 Gamma Scout)

2 Communication Protocol v1

2.1 Commands and Responses

Older models of the Gamma Scout family use the v1 protocol. This is, as the v2, based on ASCII communication, but a little bit more limited. Most notably, the PC cannot initiate the connection, but the "PC mode" has to be activated first by pressing the according button of the Gamma Scout. This makes the Gamma Scout with a v1-protocol virtually useless for continuous data logging. Communication is performed with 2400 baud, 7E1, no echo. Note that every response (in contrast to the v2 protocol) is not only preceded by "\r\n", but also by a space character (denoted explicitly as \s for more clarity). Here's the command list:

Command Description Response Example
"v"
76
Get version of device "\r\n\sVersion 5.43\r\n"
v
 Version 5.43
"d" + DDMMYY
64 [...]
Sets the current date "\r\n\sDatum gestellt\s\r\n" Example to set date to 2011-10-02:
d021011
 Datum gestellt
"u" + HHMM
75 [...]
Sets the current time "\r\n\sZeit gestellt\s\r\n" Example to set time to 12:34:
u1234
 Zeit gestellt
"z"
7a
Clear the recorded logs "\r\n\sProtokollspeicher wieder frei\s\r\n"
z
 Protokollspeicher wieder frei
"i"
69
Reset and self-test the device. No response.
i
"b"
62
Dump the recorded logs Multiple lines of hex-dump (started by "\r\n\sGAMMA-SCOUT Protokoll\s\r\n\r\n")
b
 GAMMA-SCOUT Protokoll 

 0000 03 02 01 ff ff ff ff ff ff ff ff ff ff ff ff ff
 0010 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 0020 31 01 ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 0030 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 0040 ff ff ff ff ff ff ff ff de ad be ef ff ff ff ff
 0050 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 0060 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 0070 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[...]
 0100 fe 40 08 28 06 11 f2 04 07 03 ae 03 c6 ff 0f 00
 0110 00 f8 f0 3c 22 3c 2a 3c 2a 3c 2f 3c 21 3c 1a 3c
 0120 12 37 f4 37 ed 37 ee 3c 08 3c 05 3c 05 37 f7 37
 0130 ff 02 da 02 ef 02 e3 02 bd 02 b6 02 fe 02 f4 02
 0140 c6 02 ce 02 f6 02 db 02 e4 02 b9 02 e5 02 eb 02
 0150 dd 02 eb 02 e6 02 e4 02 e4 02 bc 02 d3 02 e2 02
 0160 a6 03 08 02 dd 02 d1 02 c9 02 bd 02 e1 03 03 03
 0170 02 02 e2 02 e7 02 ee 02 da 02 e4 02 d3 02 e0 02
 0180 f1 02 ef 02 d0 02 ba 02 d5 02 c0 03 0a 02 e4 02
 0190 f0 02 ee 02 e8 02 be 02 f8 02 cd 02 c1 02 e7 02
 01a0 f6 02 c7 02 ea 02 c8 02 f5 02 f0 02 c7 02 a2 02
 01b0 e8 02 d8 03 03 02 d8 02 ee 02 cb 02 98 02 bb 02
 01c0 bf 03 00 02 f7 03 23 02 c6 02 c3 02 e0 02 dd 02
 01d0 d1 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 01e0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[...]
 07f0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff

2.2 Log Interpretation

In contrast to the protocol version 2, special command codes are slightly different. The first three bytes of the log encode the serial number of the device in little endian using the "decimal interpreted as hexadecimal" representation (i.e. for the above device, that serial would be 10203). At position 0x20 a uint16 value is stored in little endian byte order indicating the first invalid address in the log. The actual log then starts at 0x100. For the example above, the first invalid log address is 0x131 (the uint16 value at position 0x20), therefore the log is from 0x100 to 0x130 (inclusively). The log itself contains encoded command codes and impulse counts. The command codes always have 0xf in the first nibble of the first byte (i.e. every hex-sequence that starts with 0xf? is a command code, everything else is a impulse count):

Command Description Example
fe [mm] [hh] [DD] [MM] [YY]
New date and time has been set. Note that all values are decimal values in hexadecimal representation, or in other words: To get the actual values of each byte, you have to calculate:
byte = 10 * ((byte & 0xf0) >> 4) + (byte & 0x0f)
fe ef 59 23 31 12 11
Encodes that the date will be from this point in the log 2011-12-31 23:59
ff [GG GG] [CC CC]
Encodes that there is a gap in the logs. GG GG is the gap time in minutes, given in little endian byte order. The impulse count CC CC encodes the amount of impulses counted in that given period of time. The impulses are encoded in floating point represantation, for a detailled description see the section "Floating Point Representation"
ff 0f 00 00 f8
Encodes that a gap of 15 minutes occurred, i.e. 0x000f. In this interval, 248 impulses were counted.
f4
Encodes that the acquisition interval will be 1 minute from now on.  
f3
Encodes that the acquisition interval will be 10 minutes from now on.  
f2
Encodes that the acquisition interval will be 1 hour from now on.  
f1
Encodes that the acquisition interval will be 1 day from now on.  
f0
Encodes that the acquisition interval will be 7 days from now on.  
[CC CC]
Encodes an impulse count. Impulse counts are encoded in floating point represenation with a 6 bit exponent and 10 bit mantissa. The values are decoded according to the description in the "Floating Point Representation" section. See "Floating Point Representation" section.

3 Communication Protocol v2

3.1 Commands and Responses

The communication protocol v2 the Gamma Scout uses is trivially easy to understand and implement. Communication is done with 9600 baud, 7E1, no echo. The protocol is ASCII-based, you can use for example picocom to play around with it a little. Here is a list of commands that you can issue and the according responses:

Command Modes / Description Response Example
"v"
76
PC, Acquisition: Get version and mode information of device
  • Acquisition mode: response will be "\r\nStandard\r\n"
  • PC mode: response will be "\r\nVersion 6.05 012345 000b 02.10.11 20:07:43\r\n"
    • "6.05" indicates the current software version
    • "012345" indicates the serial number of the device in decimal
    • "000b" is the amount of EEPROM that is currently used by the log, in this case 11 bytes
    • This is followed by the current date and time of the device
Acquisition mode:
v
Standard
PC connected mode:
v
Version 6.05 012345 000d 02.10.11 20:11:26
"P"
50
Acquisition: Switch to PC mode "\r\nPC-Mode gestartet\r\n"
P
PC-Mode gestartet
"X"
58
PC: Switch to Acquisition mode "\r\nPC-Mode beendet\r\n"
X
PC-Mode beendet
"t" + YYMMDDHHMMSS
74 [...]
PC: Set date and time of the device to desired value. Note that this command has to be sent extremely slowly, i.e. about 500ms between each character, or the device will lose single characters. Note also that the date and time is not checked for plausibility whatsoever, so it is perfectly possible to set the date to ff-55-99 90:60:90. "\r\nDatum und Zeit gestellt\r\n" Example to set time to 2011-10-02 20:19:00:
t021011201900
Datum und Zeit gestellt
"c"
63
PC: Get some configuration data from the device Multiple lines of hex-dump Since I have no clue what these values encode, I blacked them partially out. They're just some hexdump with four lines of data, then all zeroes. The first line of data looks somewhat special:
c
00000000000000000000
00000000000000000000
00000000000000000000
00000000000000000000
00000000000000000000
"b"
62
PC: Dump the recorded logs Multiple lines of hex-dump
b
GAMMA-SCOUT Protokoll
f5ef5719021011f508007a0084007e007cf5ef11200210110087f5ee0600002236
f50c00010006000600040004000400010006000600010004000400020005000239
0002000300057700840077f5ee05000012f501f5ee890c1ec9f5080074007c00b8
"z"
7a
PC: Clear the recorded logs "\r\nProtokollspeicher wieder frei\r\n"
z
Protokollspeicher wieder frei
"i"
69
PC: Reset and self-test the device. Completely erases the log and date/time settings. Performs a quite lengthy self-test after issued where it counts from 0x0 to 0xffff in steps of 0x400 about four times. No response.
i

3.2 Log Interpretation

The log that is issued upon sending the "b" command is also quite easy to understand. First it is necessary to know that the log does not get reset when it is cleared, only the pointer gets reset to the beginning. Therefore it is necessary to query how much data is valid by using the "v" command before issuing "b". Each line contains 33 bytes of data (i.e. 66 characters + "\r\n", so 68 bytes per line). The first 32 bytes in each line are actual protocol data. The last byte is the checksum, which can be calculated by taking the sum of the preceding 32 bytes modulo 256. Then while traversing the log, if the first byte is 0xf5, it indicates a special command and has variable length. If it does not start with 0xf5, it is a impulse count, coded in big endian format. Here's the list of special commands:

Command Description Example
f5 ef [mm] [hh] [DD] [MM] [YY]
New date and time has been set. Note that all values are decimal values in hexadecimal representation, or in other words: To get the actual values of each byte, you have to calculate:
byte = 10 * ((byte & 0xf0) >> 4) + (byte & 0x0f)
f5 ef 59 23 31 12 11
Encodes that the date will be from this point in the log 2011-12-31 23:59
f5 ee [GG GG] [CC CC]
Encodes that there is a gap in the logs. This occurs whenever the interval was changed. For example, when having the device in 7-day acquisition mode and changing to 5-minute acquisition mode after 3 days, the amount of time (3 days) will be recorded and the amount of counts recorded so far will also be recorded. The gap is coded in little endian (!) in 10-second intervals, but the counts are encoded in big endian floating point representation (detailled description in section "Floating Point Representation").
f5 ee 68 00 01 9a
Encodes that a gap of 17:20 (minutes:seconds) occurred, i.e. 0x0068 * 10 seconds (1040 seconds). In this interval, 410 impulses were counted (0x019a).
f5 0c
Encodes that the acquisition interval will be 10 seconds from now on.  
f5 0b
Encodes that the acquisition interval will be 30 seconds from now on.  
f5 0a
Encodes that the acquisition interval will be 1 minute from now on.  
f5 09
Encodes that the acquisition interval will be 2 minutes from now on.  
f5 08
Encodes that the acquisition interval will be 5 minutes from now on.  
f5 07
Encodes that the acquisition interval will be 10 minutes from now on.  
f5 06
Encodes that the acquisition interval will be 30 minutes from now on.  
f5 05
Encodes that the acquisition interval will be 1 hour from now on.  
f5 04
Encodes that the acquisition interval will be 2 hours from now on.  
f5 03
Encodes that the acquisition interval will be 12 hours from now on.  
f5 02
Encodes that the acquisition interval will be 1 day from now on.  
f5 01
Encodes that the acquisition interval will be 3 days from now on.  
f5 00
Encodes that the acquisition interval will be 7 days from now on.  
f5 f3
Unknown. Occurs in the log after the device has been reset.  
f5 f4
Unknown. Occurs in the log after the device has been reset.  
[CC CC]
Encodes an impulse count. Impulse counts are encoded in floating point represenation with a 6 bit exponent and 10 bit mantissa. The values are decoded according to the description in the "Floating Point Representation" section. See "Floating Point Representation" section.

4 Floating Point Representation

Impulse counts are encoded in floating point represenation with a 6 bit exponent and 10 bit mantissa. First, the value is converted using big endian decoding (most significant byte first):

value = (data[0] << 8) | data[1]
Then the exponent and mantissa can be extracted (format is eeeeeemm mmmmmmmm):
exponent = (value & 0xfc00) >> 10
mantissa = (value & 0x03ff)
The two least significant bits of the exponent are then mangled together:
exponent = (exponent + 1) // 2
If the resulting exponent is zero, the impulse count is the mantissa value. Otherwise, the impulse count is retrieved by adding 210 to the mantissa and then multiplying by 2exponent - 1. In other words:
if exponent == 0:
    counts = mantissa
else:
    counts = (mantissa + (2 ** 10)) * (2 ** (exponent - 1))

4.1 Examples

00 aa = 170
01 bb = 443
02 cc = 716
03 dd = 989
04 ee = 1262
05 ff = 1535
12 34 = 3176
ab cd = 2094006272

For the last example (ab cd), converting to big endian yields 0xabcd. The exponent and mantissa therefore are 42 and 973. After mangling the two least significant bits of the exponent together, the exponent is 21. Therefore, the result is: (973 + 1024) * 220 = 1997 * 220 = 2094006272.

Thanks to Martin Bönsch, who noticed an error in the above calculation and corrected it.

5 Linux Software: GammaScoutUtil

5.1 Prerequisites

Here's what's required to get GammaScoutUtil running:

For Ubuntu:

joequad joe [~/GammaScoutUtil-0.04]: sudo apt-get install python3 python-serial

5.2 Getting Started

After plugging in the Gamma Scout into your USB port, check with dmesg which device it is recognized as. Usually this will be /dev/ttyUSB0. Then, you can call gammascoututil to check if it finds your Gamma Scout. Putting the Gamma Scout into PC mode beforehand is actually not necessary, the software takes care of that.

joequad joe [~/GammaScoutUtil-0.04]: ./gammascoututil
Nothing to do.

./gammascoututil (-d Device) (-p Protocol) (-v) [Cmd1] ([Cmd2]) ([Cmd3]) ...
   -d Device     Specifies the serial device that the Gamma Scout is
                 connected to. Default is /dev/ttyUSB0
   -p Protocol   Specifies the device protocol the connected Gamma Scout
                 uses. Either 'v1' or 'v2'. Default is 'v2'.
   -v            Outputs debug information
   --help        Displays this help page

  Commands:
     identify
         Displays information like the Gamma Scout software version and
         serial number of the device
     synctime
         Synchronizes the time with the current local system time
     syncutctime
         Synchronizes the time with the current time in UTC (GMT+0)
     settime:YYYY-MM-DD-HH-MM-SS
         Sets the time to the user defined value
     readlog:[txt|sqlite|csv|xml|bin]:[Filename]
         Reads out Gamma Scout log in text format, sqlite format, CSV, XML
         or binary format and writes the results to the specified filename
     clearlog
         Deletes the Gamma Scout log
     readcfg:Filename
         Reads out the configuration blob and writes it in the specified
         file in binary format
     devicereset
         Completely resets the device to its factory defaults. Do not perform
         this operation unless you have a good reason to.

  Examples:
     ./gammascoututil -p v1 -d /dev/ttyS0 identify
     ./gammascoututil -d /dev/ttyUSB3 identify
     ./gammascoututil readlog:sqlite:/home/joe/foobar.sqlite clearlog
joequad joe [~/GammaScoutUtil-0.04]: ./gammascoututil identify
Current date and time: 2011-10-02 19:53:49
Serial number        : 12345
Software version     : 6.05
Log buffer fill      : 75 bytes

Then, let's first read out the internal log into a text file:

joequad joe [~/GammaScoutUtil-0.04]: ./gammascoututil readlog:txt:counter.txt
joequad joe [~/GammaScoutUtil-0.04]: cat counter.txt
From                   To                    Counts Seconds    CPM     CPS
--------------------------------------------------------------------------------
2011-10-02 18:23:00    2011-10-02 18:28:00      105     300   21.0   0.350
2011-10-02 18:28:00    2011-10-02 18:33:00      181     300   36.2   0.603
2011-10-02 18:33:00    2011-10-02 18:38:00      126     300   25.2   0.420
2011-10-02 18:38:00    2011-10-02 18:43:00      104     300   20.8   0.347
2011-10-02 18:43:00    2011-10-02 18:48:00      120     300   24.0   0.400
2011-10-02 18:48:00    2011-10-02 18:53:00      100     300   20.0   0.333
2011-10-02 18:53:00    2011-10-02 18:58:00      112     300   22.4   0.373
2011-10-02 18:58:00    2011-10-02 19:03:00      125     300   25.0   0.417
2011-10-02 19:03:00    2011-10-02 19:08:00      129     300   25.8   0.430
2011-10-02 19:08:00    2011-10-02 19:13:00      118     300   23.6   0.393
2011-10-02 19:13:00    2011-10-02 19:18:00      121     300   24.2   0.403
2011-10-02 19:18:00    2011-10-02 19:23:00      115     300   23.0   0.383
2011-10-02 19:23:00    2011-10-02 19:28:00      116     300   23.2   0.387
2011-10-02 19:28:00    2011-10-02 19:33:00      119     300   23.8   0.397
2011-10-02 19:33:00    2011-10-02 19:38:00      117     300   23.4   0.390
2011-10-02 19:38:00    2011-10-02 19:43:00      119     300   23.8   0.397
2011-10-02 19:43:00    2011-10-02 19:48:00      132     300   26.4   0.440
2011-10-02 19:48:00    2011-10-02 19:53:00      119     300   23.8   0.397

What you might want to do if your have the tool running via a cronjob (i.e. have the setting log in a small interval and clear the data nightly) is log into a database. For this you can directly query into a sqlite database. Also note that you can supply multiple commands on one command line (for example, readout and clear the database afterwards):

joequad joe [~/GammaScoutUtil-0.04]: ./gammascoututil readlog:sqlite:counter.sqlite clearlog
joequad joe [~/GammaScoutUtil-0.04]: sqlite counter.sqlite .dump
PRAGMA foreign_keys=OFF;
BEGIN TRANSACTION;
CREATE TABLE data (
			id integer PRIMARY KEY,
			tfrom timestamp NOT NULL,
			tto timestamp NOT NULL,
			counts integer NOT NULL,
			CHECK(tto > tfrom),
			CHECK(counts >= 0)
		);
INSERT INTO "data" VALUES(1,'2011-10-02 18:23:00','2011-10-02 18:28:00',105);
INSERT INTO "data" VALUES(2,'2011-10-02 18:28:00','2011-10-02 18:33:00',181);
INSERT INTO "data" VALUES(3,'2011-10-02 18:33:00','2011-10-02 18:38:00',126);
INSERT INTO "data" VALUES(4,'2011-10-02 18:38:00','2011-10-02 18:43:00',104);
INSERT INTO "data" VALUES(5,'2011-10-02 18:43:00','2011-10-02 18:48:00',120);
INSERT INTO "data" VALUES(6,'2011-10-02 18:48:00','2011-10-02 18:53:00',100);
INSERT INTO "data" VALUES(7,'2011-10-02 18:53:00','2011-10-02 18:58:00',112);
INSERT INTO "data" VALUES(8,'2011-10-02 18:58:00','2011-10-02 19:03:00',125);
INSERT INTO "data" VALUES(9,'2011-10-02 19:03:00','2011-10-02 19:08:00',129);
INSERT INTO "data" VALUES(10,'2011-10-02 19:08:00','2011-10-02 19:13:00',118);
INSERT INTO "data" VALUES(11,'2011-10-02 19:13:00','2011-10-02 19:18:00',121);
INSERT INTO "data" VALUES(12,'2011-10-02 19:18:00','2011-10-02 19:23:00',115);
INSERT INTO "data" VALUES(13,'2011-10-02 19:23:00','2011-10-02 19:28:00',116);
INSERT INTO "data" VALUES(14,'2011-10-02 19:28:00','2011-10-02 19:33:00',119);
INSERT INTO "data" VALUES(15,'2011-10-02 19:33:00','2011-10-02 19:38:00',117);
INSERT INTO "data" VALUES(16,'2011-10-02 19:38:00','2011-10-02 19:43:00',119);
INSERT INTO "data" VALUES(17,'2011-10-02 19:43:00','2011-10-02 19:48:00',132);
INSERT INTO "data" VALUES(18,'2011-10-02 19:48:00','2011-10-02 19:53:00',119);
COMMIT;

5.3 Downloads

Filename Last Changed Description
GammaScoutUtil-0.04.tar.gz 2012-01-06
  • Fixed a bug which would record incorrect count amounts for the v2-Protocol of the Gamma Scout for counts >2^11 per interval (thanks go to Benjamin Knispel for the bug report and provided test data)
  • Included a script "fix_counts_v0.03.py" which fixes incorrectly recorded count data
  • The v1 and v2 protocol have nothing to do with the Basic/Alert variant of the counter. Renamed everything and changed command line parameters to do the right thing (also thanks to Benjamin Knispel for reporting this).
  • Synchronizing time to Gamma Scout is now possible in UTC ("syncutctime" command)
  • SQLite output backend added a metadata table which contains version information (in case this shall be automatically upgraded in the future)
  • Fixed a hang for v2 protocol that would occur if no Gamma Scout was connected to the PC
GammaScoutUtil-0.03.tar.gz 2011-10-26
  • Added support for "Gamma Scout Basic" (aka "Gamma Scout without Alert")
  • Added very simple simulation data feature for Gamma Scout Basic (data kindly provided by Jörg Wartenberg)
  • Added XML export functionality
  • Proper error messages when device times out
  • No file is generated when device does not support reading the configuration blob
  • Time in log now not time_t, but realtive to first message and relative to last message
GammaScoutUtil-0.02.tar.gz 2011-10-02
  • First release, supports the Gamma Scout w/Alert USB device
  • Textfile, Binary, CSV and Sqlite3-export of data is possible
  • Licensed under the GNU General Public License v3