Posts by phys Add sensor

1) Message boards : Science : Data logging in offline mode (Message 3232)
Posted 3260 days ago by phys

Now a had a look on the source code of the 2.61 Kit, as a know where to look for.(usbconfig.h)

#define USB_CFG_VENDOR_ID 0xc0, 0x16 /* = 0x16c0 */
/* USB vendor ID for the device, low byte first. If you have registered your
* own Vendor ID, define it here. Otherwise you may use one of obdev's free
* shared VID/PID pairs. Be sure to read USB-IDs-for-free.txt for rules!
* *** IMPORTANT NOTE ***
* This template uses obdev's shared VID/PID pair for Vendor Class devices
* with libusb: 0x16c0/0x5dc. Use this VID/PID pair ONLY if you understand
* the implications!
*/
#define USB_CFG_DEVICE_ID 0xdf, 0x05 /* = 0x05df */
/* This is the ID of the product, low byte first. It is interpreted in the
* scope of the vendor ID. If you have registered your own VID with usb.org
* or if you have licensed a PID from somebody else, define it here. Otherwise
* you may use one of obdev's free shared VID/PID pairs. See the file
* USB-IDs-for-free.txt for details!
* *** IMPORTANT NOTE ***
* This template uses obdev's shared VID/PID pair for Vendor Class devices
* with libusb: 0x16c0/0x5dc. Use this VID/PID pair ONLY if you understand
* the implications!
*/
#define USB_CFG_DEVICE_VERSION 0x61, 0x02
/* Version number of the device: Minor number first, then major number. */
//#define USB_CFG_VENDOR_NAME 'o','b','d','e','v','.','a','t' //8
#define USB_CFG_VENDOR_NAME 'r','a','d','i','o','a','c','t','i','v','e','a','t','h','o','m','e','.','o','r','g' //21
#define USB_CFG_VENDOR_NAME_LEN 21
/* These two values define the vendor name returned by the USB device. The name
* must be given as a list of characters under single quotes. The characters
* are interpreted as Unicode (UTF-16) entities.
* If you don't want a vendor name string, undefine these macros.
* ALWAYS define a vendor name containing your Internet domain name if you use
* obdev's free shared VID/PID pair. See the file USB-IDs-for-free.txt for
* details.
*/
//#define USB_CFG_DEVICE_NAME 'r','a','d','i','o','a','c','t','i','v','e','a','t','h','o','m','e','.','o','r','g',' ','G','R','S' //25 signs
#define USB_CFG_DEVICE_NAME 'R','a','d','i','a','t','i','o','n',' ','D','e','t','e','c','t','o','r',' ','K','I','T' //22
#define USB_CFG_DEVICE_NAME_LEN 22
/* Same as above for the device name. If you don't want a device name, undefine
* the macros. See the file USB-IDs-for-free.txt before you assign a name if
* you use a shared VID/PID.
*/
/*#define USB_CFG_SERIAL_NUMBER 'N', 'o', 'n', 'e' */

So the team (ignored all warnings) and used VID=16c0 with a new PID=05df.

Note to myself: In the published source code of the v3.01 Sensor the VID and PID was changed to XXXX. If I ever want to compile it on my own or change anything, I have to insert PID and VID again because they were deleted.

3) Message boards : Number crunching : Read data from the sensor with Python scripts ... (Message 3015)
Posted 3372 days ago by phys

Look into the http://radioactiveathome.org/boinc/forum_thread.php?id=223 thread.

5) Message boards : News : Firmware sources (Message 3013)
Posted 3372 days ago by phys

Please tell us more infos. At least a change log.

This files comes with an Firmware31_0026o archive. It's a PIC, not AVR.

So, is this for a v2.50 Sensor? Upcoming v3.1?
But not v2.6, the modified v2 AVR Sensor?

Is this a newer firmware than the one shipped with the v2.5 one?

7) Message boards : Science : Data logging in offline mode (Message 2389)
Posted 3702 days ago by phys

I have put a script together, to access the device in your favourite operating system (Win, Linux, Arm,..) using the cross platform library hidapi and python. You can get this python module on http://https://github.com/trezor/cython-hidapi/ and compile it yourself. For your convenience and windows users I have put it together with the script in the zip file. Put the hid.pyd module into C:\Python27\Lib\site-packages.(Please use the IDLE python GUI in windows, or you might get an error on the MS-CMD-Prompt)

A sample output looks like

==============================
Radiactive At Home Test Script
==============================

Show you all the HID devices on your PC
interface_number : -1
manufacturer_string : microchip
path : \\?\hid#vid_04d8&pid_f6fe#7&8095337&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
product_id : 63230
product_string : radioactiveathome.org GRS
release_number : 769
serial_number : Љ
usage : 1
usage_page : 65280
vendor_id : 1240

Opening selected device
Manufacturer: microchip
Product: radioactiveathome.org GRS
[0, 184, 160, 46, 0, 28, 135, 0]
Realtime clock: 3055.8s
Counts: 34588
Realtime clock: 3065.8s, Counts: 34705
Realtime clock: 3075.8s, Counts: 34823
Realtime clock: 3085.81s, Counts: 34927
Realtime clock: 3095.81s, Counts: 35055
679.402 CPM, 3.96847 mikroSv/h
Corrected 680.944 CPM, 3.97748+-0.0211957 mikroSv/h
Closing device
Done

You can get the package here and extend it to your own needs.

Happy hacking!

9) Message boards : Science : Data logging in offline mode (Message 2385)
Posted 3703 days ago by phys

It is a shame none of the devs answered your questions. I want to give you some hints:

The device uses a HID interface. A free tool to communicate with HID devices is HIDAPI, also available as phyton module, so you may use certain commands on the command line without making a whole C-program. Firstly, you must get the VID and PID of your device, eg for v3 Detector: 0x04d8,0xf6fe.

The correct data transfer mode is "Feature report". Not Interrupt in or interrupt out. The report ID is 0. This is a special ID, the only bidirectional one. The report size is 0x80 or 128 (probably 129?). If you get the feature report, you will see two changing fields over several bytes. One is the time in milliseconds, the other one the detected counts.

To send commands to the device, you put the control command on the first place in the feature report and send the buffer to the HID.

The control commands are
#define GM_SUPPLY_ON 0xa1
#define GM_SUPPLY_OFF 0xa0
#define RESET_COUNTERS 0xa2
#define LCD_BACKLIGHT_ON 0x11
#define LCD_BACKLIGHT_OFF 0x10
#define BUZZER_ON 0x41
#define BUZZER_OFF 0x40
#define BUZZER_ALERT 0x42 //switch on the buzzer on reading >0.3
#define LCD_OPT_0 0x50 //old-style LCD update - 35s
#define LCD_OPT_1 0x51 //running average, display updated every 3s
#define LCD_OPT_2 0x52 //350s average

Happy hacking! And please post your code.