1)
Message boards :
Number crunching :
using a GMC-300 for a project detector?
(Message 2088)
Posted 3813 days ago by [AF>Amis des Lapins] Papoun37 The protocol is the same for all GQ 3xx and it works I tested it on visual basic http://www.gqelectronicsllc.com/download/GQ-RFC1201.txt may be that he will guide you: I found the old version of gmc300.exe started up every time I booted the offcial GQ heatbeat properly before and I took care of them out using function exit |
2)
Message boards :
Number crunching :
using a GMC-300 for a project detector?
(Message 2086)
Posted 3813 days ago by [AF>Amis des Lapins] Papoun37 View1 with error gmc300.exe view2 with GMC official hearbeat without disconnect GMC320: |
3)
Message boards :
Number crunching :
using a GMC-300 for a project detector?
(Message 2084)
Posted 3813 days ago by [AF>Amis des Lapins] Papoun37 Error on open com, reading version is not correct. (But after close gmc300.exe, the official "GQ GMC Data Viewer" can read heartbeat) Radioactive@Home app rev $Rev: 178 $ for GMC-300 starting... COM5 opened for read/write gmc_GetVersion(): read failed Connected to («! (revision int: 1) GetCommState failed: error 6 Unable to open port COM5 OR Radioactive@Home app rev $Rev: 178 $ for GMC-300 starting... COM5 opened for read/write gmc_GetVersion(): read failed Connected to ,ª. (revision int: 1) |
4)
Message boards :
Number crunching :
using a GMC-300 for a project detector?
(Message 2071)
Posted 3824 days ago by [AF>Amis des Lapins] Papoun37 Two weeks is the daily time to receive it. If you want, see my sensor graph :sensor number 9476. Boinc say task is invalid but it keep it on graph See that, I think we should add tests in the application to stop and restart if the com port forwarding errors of this kind and perhaps Boinc start to fast the application and a daily time to run gmc300.exe open com port is necessary... (sorry for my English..) Stderr output <core_client_version>7.0.64</core_client_version> <![CDATA[ <stderr_txt> Debug: Using port number: 5 Radioactive@Home app rev $Rev: 585 $ for GMC-300 starting... COM5 opened for read/write Debug: Port timeouts: ReadTotalTimeoutConstant: 1000 ReadIntervalTimeout: 0 ReadTotalTimeoutMultiplier: 100 WriteTotalTimeoutMultiplier: 100 WriteTotalTimeoutConstant: 1000 <GETVER>> returned GMC-320Re 3.12 <GETCPM>> returned -128 0 CPM value: -32768 1000,4294966204,2013-11-7 4:29:24,0,f,0 <GETCPM>> returned 0 22 CPM value: 22 242000,4294966292,2013-11-7 4:33:25,0,n,0 <GETCPM>> returned -128 0 CPM value: -32768 483000,4294834673,2013-11-7 4:37:26,0,n,0 <GETCPM>> returned -128 0 CPM value: -32768 724000,4294703054,2013-11-7 4:41:27,0,n,0 Debug: trickle sent Trickle sent <GETCPM>> returned -128 0 CPM value: -32768 965000,4294571435,2013-11-7 4:45:28,0,n,0 <GETCPM>> returned -128 0 CPM value: -32768 1206000,4294439816,2013-11-7 4:49:29,0,n,0 <GETCPM>> returned -128 1 CPM value: -32767 1447000,4294308201,2013-11-7 4:53:30,0,n,0 Debug: trickle sent Trickle sent <GETCPM>> returned -128 0 CPM value: -32768 1688000,4294176582,2013-11-7 4:57:31,0,n,0 <GETCPM>> returned -128 1 CPM value: -32767 1929000,4294044967,2013-11-7 5:1:32,0,n,0 <GETCPM>> returned -128 0 CPM value: -32768 2170000,4293913348,2013-11-7 5:5:33,0,n,0 Debug: trickle sent Trickle sent <GETCPM>> returned -128 0 CPM value: -32768 2411000,4293781729,2013-11-7 5:9:34,0,n,0 <GETCPM>> returned -128 1 CPM value: -32767 2652000,4293650114,2013-11-7 5:13:35,0,n,0 <GETCPM>> returned -128 0 CPM value: -32768 2893000,4293518495,2013-11-7 5:17:36,0,n,0 Debug: trickle sent Trickle sent <GETCPM>> returned -128 2 CPM value: -32766 3134000,4293386884,2013-11-7 5:21:37,0,n,0 <GETCPM>> returned -128 0 CPM value: -32768 3375000,4293255265,2013-11-7 5:25:38,0,n,0 <GETCPM>> returned -128 0 CPM value: -32768 3616000,4293123646,2013-11-7 5:29:39,0,n,0 Debug: trickle sent Trickle sent <GETCPM>> returned -128 0 CPM value: -32768 3857000,4292992027,2013-11-7 5:33:40,0,n,0 <GETCPM>> returned -128 1 CPM value: -32767 4098000,4292860412,2013-11-7 5:37:41,0,n,0 <GETCPM>> returned -128 1 CPM value: -32767 4339000,4292728797,2013-11-7 5:41:42,0,n,0 Debug: trickle sent Trickle sent <GETCPM>> returned -128 0 CPM value: -32768 4580000,4292597178,2013-11-7 5:45:43,0,n,0 <GETCPM>> returned -128 0 CPM value: -32768 4821000,4292465559,2013-11-7 5:49:44,0,n,0 <GETCPM>> returned -128 0 CPM value: -32768 5062000,4292333940,2013-11-7 5:53:45,0,n,0 Debug: trickle sent Trickle sent <GETCPM>> returned -128 1 CPM value: -32767 5303000,4292202325,2013-11-7 5:57:46,0,n,0 <GETCPM>> returned -128 0 CPM value: -32768 5544000,4292070706,2013-11-7 6:1:47,0,n,0 <GETCPM>> returned -128 0 CPM value: -32768 5785000,4291939087,2013-11-7 6:5:48,0,n,0 Debug: trickle sent Trickle sent <GETCPM>> returned -128 0 CPM value: -32768 6026000,4291807468,2013-11-7 6:9:49,0,n,0 <GETCPM>> returned -128 0 CPM value: -32768 6267000,4291675849,2013-11-7 6:13:50,0,n,0 <GETCPM>> returned -128 0 CPM value: -32768 6508000,4291544230,2013-11-7 6:17:51,0,n,0 Debug: trickle sent Trickle sent <GETCPM>> returned -128 1 CPM value: -32767 6749000,4291412615,2013-11-7 6:21:52,0,n,0 <GETCPM>> returned -128 1 CPM value: -32767 6990000,4291281000,2013-11-7 6:25:53,0,n,0 <GETCPM>> returned -128 0 CPM value: -32768 7231000,4291149381,2013-11-7 6:29:54,0,n,0 Debug: trickle sent Trickle sent Done - calling boinc_finish() 07:29:54 (4900): called boinc_finish </stderr_txt> ]]> |
5)
Message boards :
Number crunching :
using a GMC-300 for a project detector?
(Message 2067)
Posted 3833 days ago by [AF>Amis des Lapins] Papoun37 Do Someone can help me. Whith GMC exe for a GMC-320 and Boinc 7.0.64,when i turn on my PC after a turn off in a middle of a work unit, Boinc don't restart a new work of R@H automatically. Example today: my PC is turn on at 10h08 but now 12h58 R@H is always stopped: But if I restart Boinc, R@H restart and only at this time i can see canonical result on my profile: <core_client_version>7.0.64</core_client_version> <![CDATA[ <stderr_txt> Debug: Using port number: 5 Radioactive@Home app rev $Rev: 585 $ for GMC-300 starting... COM5 opened for read/write Debug: Port timeouts: ReadTotalTimeoutConstant: 1000 ReadIntervalTimeout: 0 ReadTotalTimeoutMultiplier: 100 WriteTotalTimeoutMultiplier: 100 WriteTotalTimeoutConstant: 1000 <GETVER>> returned GMC-320Re 3.12 <GETCPM>> returned 0 27 CPM value: 27 1000,0,2013-10-29 22:21:25,0,f,0 <GETCPM>> returned 0 17 CPM value: 17 242000,68,2013-10-29 22:25:26,0,n,0 .... .... <GETCPM>> returned 0 22 CPM value: 22 6274000,2118,2013-10-30 0:5:58,0,n,0 <GETCPM>> returned 0 21 CPM value: 21 6515000,2202,2013-10-30 0:9:59,0,n,0 Debug: trickle sent Trickle sent Debug: Using port number: 5 Radioactive@Home app rev $Rev: 585 $ for GMC-300 starting... Found previously created output file, workunit almost completed - exiting 10:08:03 (3216): called boinc_finish </stderr_txt> ]]> Is it a bad setting of Boinc? |
6)
Message boards :
Cafe :
Our map on Android devices
(Message 2066)
Posted 3834 days ago by [AF>Amis des Lapins] Papoun37 Hello Krzysztof, Is it possible to advance the smartphone application to notify in real time if a sensor on the worldmap returned a value higher than 0.8mSH? |
7)
Message boards :
Number crunching :
using a GMC-300 for a project detector?
(Message 2065)
Posted 3834 days ago by [AF>Amis des Lapins] Papoun37 Yippee My GMC-320 works now under number 9476 sensor. It's a bit difficult to understand that message # 1800 is the final message for the download of the application and its installation procedure, but with a little patience and google translation is done by understanding |
8)
Message boards :
Number crunching :
using a GMC-300 for a project detector?
(Message 2061)
Posted 3843 days ago by [AF>Amis des Lapins] Papoun37 English Version I ordered a GMC-320 today. Although this is not the GCM-300 I will try to make it work for Radioactive @ home. I should receive it on November 22. The location will be in France at 5 km from the sensor 7905. See you soon. French version: J'ai commandé un GMC-320 aujourd'hui. Même si ce n'est pas le GCM-300 j'essaierai de le faire fonctionner pour Radioactive@home. Je doit le recevoir le 22 novembre. La localisation sera en france à 5 kilometres du sensor 7905. A bientot. |