Announcement

**pcca-matrix** · August 4, 2008, 02:07 PM

Hello michael,
The probe is now recognized but works strangly.
Probe report only Temp , Humidity , and Battery status , no time , no mode (comfort,wet,dry)
for sure this is not critical , the most important is temp and humidity of course
the second strange thing is that:

each time it detect the probe 5 times with 5 different ID ??
same for humidity and battery but all have the same value.

This probe has a large advantage compared to the others Oregon i have, it less frequently "speaks" (1 time each 60 second) What limits the collisions when have a lot of probe.

Anyway thanks for this update Michael.

**pcca-matrix** · August 4, 2008, 05:32 PM

Hello michael,
The probe is now recognized but works strangly.

Probe report only Temp , Humidity , and Battery status , no time , no mode (comfort,wet,dry)

for sure this is not critical , the most important is temp and humidity of course
the second strange thing is each time it detect the probe 5 times with 5 different ID ?? (see pic)
same for humidity and battery but all have the same value.

This probe has a large advantage compared to the others Oregon i have, it less frequently "speaks" (1 time each 60 second) What limits the collisions when have a lot of probe.

Anyway thanks for this update Michael.

Attached Files

**Michael McSharry** · August 4, 2008, 06:21 PM

The variable ID is my coding problem and I fixed it and uploaded it. For the remainder of the information you will need to get back to Bert as I have implemented all that he had defined as of Rev 11.3 of the OS formats. There were many ? in the decode for this device.

**pseudolionel** · September 7, 2008, 04:00 PM

Gr101

I will buy Oregon scientific GR101
is what it is compatible with RFXCOM and xapmcsrf ?
many people ask themselves the question.
There is a big market in France from Oregon Scientific.

Thank you for your reply
(sorry for my English approximate)

greetings

**Michael McSharry** · September 7, 2008, 09:24 PM

Yes it is compatible. The decode is present in xapmcsRF. I do not recall if anybody has yet tested it with xapmcsRF, but if there are any issues they will be very easy to resove when real data is available.

**pseudolionel** · September 15, 2008, 10:54 AM

Hello Michael,

I bought GR101.

I have a concern.

RFreceiver is OK :
40D36C421406388406 WEIGHT2[6] GR101 0684380614426CD3 Weight: 24900 = 62.1 kg bits=64

Windows I/O XapMcsRf :
17:45:13 | 40, D3, 6C, 42, 14
17:45:13 | 06, 3D, 04, 08 | Discarding D3 while trying to sync on byte-count byte | Discarding 6C while trying to sync on byte-count byte | Discarding 42 while trying to sync on byte-count byte | Discarding 14 while trying to sync on byte-count byte | Discarding 06 while trying to sync on byte-count byte | Discarding 3D while trying to sync on byte-count byte | Discarding 04 while trying to sync on byte-count byte | Discarding 08 while trying to sync on byte-count byte
17:45:13 | 40
17:45:13 | D3, 6C, 42, 14, 06, 3D, 04
17:45:13 | 08 | Discarding D3 while trying to sync on byte-count byte | Discarding 6C while trying to sync on byte-count byte | Discarding 42 while trying to sync on byte-count byte | Discarding 14 while trying to sync on byte-count byte | Discarding 06 while trying to sync on byte-count byte | Discarding 3D while trying to sync on byte-count byte | Discarding 04 while trying to sync on byte-count byte | Discarding 08 while trying to sync on byte-count byte
17:45:14 | 40, D3, 6C, 42, 14, 06, 3D
17:45:14 | 04, 08 | Discarding D3 while trying to sync on byte-count byte | Discarding 6C while trying to sync on byte-count byte | Discarding 42 while trying to sync on byte-count byte | Discarding 14 while trying to sync on byte-count byte | Discarding 06 while trying to sync on byte-count byte | Discarding 3D while trying to sync on byte-count byte | Discarding 04 while trying to sync on byte-count byte | Discarding 08 while trying to sync on byte-count byte
17:45:15 | 40, D3, 6C
17:45:15 | 42, 14, 06, 3D, 04, 08 | Discarding D3 while trying to sync on byte-count byte | Discarding 6C while trying to sync on byte-count byte | Discarding 42 while trying to sync on byte-count byte | Discarding 14 while trying to sync on byte-count byte | Discarding 06 while trying to sync on byte-count byte | Discarding 3D while trying to sync on byte-count byte | Discarding 04 while trying to sync on byte-count byte | Discarding 08 while trying to sync on byte-count byte
17:45:15 | 40, D3, 6C, 42, 14, 06
17:45:15 | 3D, 04, 08 | Discarding D3 while trying to sync on byte-count byte | Discarding 6C while trying to sync on byte-count byte | Discarding 42 while trying to sync on byte-count byte | Discarding 14 while trying to sync on byte-count byte | Discarding 06 while trying to sync on byte-count byte | Discarding 3D while trying to sync on byte-count byte | Discarding 04 while trying to sync on byte-count byte | Discarding 08 while trying to sync on byte-count byte
17:45:16 | 40
17:45:16 | D3, 6C, 42, 14, 06, 3D, 04, 08 | Discarding D3 while trying to sync on byte-count byte | Discarding 6C while trying to sync on byte-count byte | Discarding 42 while trying to sync on byte-count byte | Discarding 14 while trying to sync on byte-count byte | Discarding 06 while trying to sync on byte-count byte | Discarding 3D while trying to sync on byte-count byte | Discarding 04 while trying to sync on byte-count byte | Discarding 08 while trying to sync on byte-count byte
17:45:16 | 40, D3, 6C, 42, 14
17:45:16 | 06, 3D, 04, 08 | Discarding D3 while trying to sync on byte-count byte | Discarding 6C while trying to sync on byte-count byte | Discarding 42 while trying to sync on byte-count byte | Discarding 14 while trying to sync on byte-count byte | Discarding 06 while trying to sync on byte-count byte | Discarding 3D while trying to sync on byte-count byte | Discarding 04 while trying to sync on byte-count byte | Discarding 08 while trying to sync on byte-count byte

Can you help me ?

**Michael McSharry** · September 20, 2008, 11:53 AM

The current version of xapmcsRF is 1.10.1. Is that what you are running? For message length 64 (40 hex) all data should be accepted and the sync message should not be delivered.

**pseudolionel** · September 20, 2008, 01:34 PM

Yes i use <small>V1.10.1

</small>I do not understand the other conditions.
Does that tick or choose?

Here is my setup:
http://www.secourisme.info/pour_mkl1.jpg

I would also like you to report an anomaly in the display.

look:

http://www.secourisme.info/pour_mkl2.jpg

Thank

**Michael McSharry** · September 20, 2008, 02:09 PM

I believe I found the problem. Try again with the new version that has been uploaded.

Can you tell what type of sensor is assocaited with your display problem?

**pseudolionel** · September 20, 2008, 02:37 PM

ok i try.
I will tell

I do not know whitch sensor display problem.
I deleted the entire directory xapmcsrf and I reinstalled a virgin. It ok.

**pseudolionel** · September 21, 2008, 02:41 PM

1.10.2 = problem with Gr101, other problem but problem

RFreveiver :
21/09/2008 21:25:58= 40D36CC20800004017 WEIGHT2[6] GR101 1740000008C26CD3 Weight: 140 = 0.3 kg bits=64
21/09/2008 21:25:58= 40D36CC20800004017 WEIGHT2[6] GR101 1740000008C26CD3 Weight: 140 = 0.3 kg bits=64

XapMCSRf :
21:28:10 | 40, F3, 6C, C2, 08, 00, 00, 00
21:28:10 | 35
21:28:10 | 40, F3, 6C, C2
21:28:10 | 08, 00, 00, 00, 35
21:28:12 | 40, F3, 6C, C2, 08, 00, 00
21:28:12 | 00, 35
21:28:12 | 40, F3
21:28:12 | 6C, C2, 08, 00, 00, 00, 35
21:28:13 | 40, F3, 6C, C2, 08
21:28:13 | 00, 00, 00, 35
21:28:13 | 40
21:28:13 | F3, 6C, C2, 08, 00, 00, 00, 35
21:28:14 | 40, F3, 6C, C2
21:28:14 | 08, 00, 00, 00, 35
21:28:14 | 40, F3, 6C, C2, 08, 00, 00, 00
21:28:14 | 35
21:28:15 | 40, F3, 6C
21:28:15 | C2, 08, 00, 00, 00, 35
21:28:15 | 40, F3, 6C, C2, 08, 00, 00
21:28:15 | 00, 35
21:28:17 | 40, F3
21:28:17 | 6C, C2, 08, 00, 00, 00, 35
21:28:17 | 40, F3, 6C, C2, 08, 00, 00, 00, 35
21:28:18 | 40
21:28:18 | F3, 6C, C2, 08, 00, 00, 00
21:28:18 | 35
21:28:18 | 40, F3, 6C, C2
21:28:18 | 08, 00, 00, 00, 35
21:28:19 | 40, F3, 6C, C2, 08, 00, 00
21:28:19 | 00, 35
21:28:19 | 40, F3, 6C
21:28:19 | C2, 08, 00, 00, 00, 35
21:28:20 | 40, F3, 6C, C2, 08, 00
21:28:20 | 00, 00, 35
21:28:20 | 40, F3
21:28:20 | 6C, C2, 08, 00, 00, 00, 35
21:28:22 | 40, F3, 6C, C2, 08
21:28:22 | 00, 00, 00, 35
21:28:22 | 40
21:28:22 | F3, 6C, C2, 08, 00, 00, 00
21:28:22 | 35
21:28:24 | 50, 1A, 2D

**Michael McSharry** · September 21, 2008, 09:01 PM

I do not see what you believe the problem to be. Per Bert's document the 8th byte (D3 vs 35) is unknown. The first nibble (D3 vs F3) is part of the checksum and will vary based upon the other bits.

At the same time the 62.1 kg and 0.3 kg in your two examples do not match the decode specification.

Perhaps Bert can chime in and describe how the byte pattern translates to 62.1 and 0.3 kg.

**b_weijenberg** · September 22, 2008, 04:03 AM

I've sent an email to Michael.

**Michael McSharry** · September 24, 2008, 11:40 AM

V1.10.3 contains the new decoding for the GR101

**pseudolionel** · September 24, 2008, 12:22 PM

result of 1st test:

19:16:47 | 40, F3
19:16:47 | 6C, 42, 0E, 46, 13, C3, 0B | 0003_06_K = 136.4
19:16:48 | 50, 1A, 2D, 10, 0D
19:16:48 | 30, 25, 20, 04, 2E, 23 | 1A2D_10D = 25.3 | 1A2D_10D_H = 42 | 1A2D_10D_P = 0 | OSBattery 1A2D100D302520042E23 Not reported because no change
19:16:48 | 38, 1A, 2D, 10, 0D, 30, 25
19:16:48 | 20 | OSScale ignored because checks digits do not match
19:16:48 | 40
19:16:49 | F3, 6C, 42, 0E, 46, 13, C3, 0B | 0003_06_K = 136.4
19:16:50 | 40, F3, 6C, 42
19:16:50 | 0E, 46, 13, C3, 0B | 0003_06_K = 136.4
19:16:50 | 40, F3, 6C, 42, 0E, 46, 13
19:16:50 | C3, 0B | 0003_06_K = 136.4
19:17:01 | 50, 1A, 2D, 10

I continue testing tonight.
I will keep you informed.

thank you for these changes

Announcement

xapmcsRF - W800 / RFXCOM xAP Node

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment