Announcement

**Michael McSharry** · December 30, 2006, 09:28 PM

Script should be OK now. Output also generated for debug. DisplayText key should be delivered in xAP messages. The referenced icons are not included in the archive. V1.5.3.

**bdickhaus** · December 30, 2006, 11:40 PM

Script is working. Debug has output values but so far all values have been decoded properly. Will watch for a problem, but I am wondering if it was an artifact of the now fixed decoding issues. I've rounded up a few icons, are they somewhere else in your vast library of xap or other products?

The baro value is still at 30, and is displayed as 30 in xapmcsRF browser window, it is 30.27 right now according to the sensor.

Are the _L values (for example 5A6D_2C3_L) the battery percentage values?

Thanks for all the great work on this, I am sure Bert also appreciates it!

Bill

**bdickhaus** · December 30, 2006, 11:42 PM

Forgot one, this is probably a typo, this is the icon for the _L value I was asking about: blank1.gif%20width=

**bdickhaus** · December 31, 2006, 12:04 PM

Here is one that came out -18.4 when it should be in the low 80's (83.1 right now).

12/31/2006 11:27:34 AM 41254.19 | xapmcsW800 Debug Data Received and Procesed: 60, 5A, 6D, 00, C3, 00, 28, 40, 06, A9, 61, 55, 2B | 5A6D_2C3 = -18.4 | 5A6D_2C3_H = 68 | 5A6D_2C3_B = 30 | 5A6D_2C3_F = Partly Cloudy | 5A6D_2C3_L = 100 | OSBattery 5A6D00C300284006A961552B Not reported because no change

**Michael McSharry** · December 31, 2006, 02:16 PM

With my other apps I use temperature icons and wind direction icons that are specific to the temperature and wind. As now implemented xapmcsRF only uses a single icon for each. I suspect I will move to be consistent with the others in the near future.

I included a few icons I had. I was surprised I did not have a barometer. Flip, Forecast, Temperature, WindDirection are the others that are not included.

The baro and tempertaure problems are fixed as well in V1.5.4.

**dos** · April 25, 2007, 02:22 PM

Hello,
I've just installed a "RFXCOM 433MHz/310MHz" ( master/slave) with "oregon", "ms13" and "ds10" sensor door 310MHz.
The rfxcom unit is installed and working with oregons and ms13 (sensor 310MHz) but not with "ds10".
If I open or close the door, I get data flowing in the rfreceiver (RFXCOM software) such as:

<TABLE bgColor=#c0c0c0><TBODY><TR><TD>A9151A05FA0D80 Visonic or DS10/90 Alert (battery low) addr:151A 0D/22696 bits=41 from SLAVE
A9151A05FA0D80 Visonic or DS10/90 Alert (battery low) addr:151A 0D/22696 bits=41 from SLAVE
A9151A05FA0D80 Visonic or DS10/90 Alert (battery low) addr:151A 0D/22696 bits=41 from SLAVE
A9151A05FA0D80 Visonic or DS10/90 Alert (battery low) addr:151A 0D/22696 bits=41 from SLAVE
A9151A05FA0D80 Visonic or DS10/90 Alert (battery low) addr:151A 0D/22696 bits=41 from SLAVE

</TD></TR></TBODY></TABLE>
=> door is open

<TABLE bgColor=#c0c0c0><TBODY><TR><TD>A9151A857A0D80 Visonic or DS10/90 Normal (battery low) addr:151A 0D/22696 bits=41 from SLAVE
A9151A857A0D80 Visonic or DS10/90 Normal (battery low) addr:151A 0D/22696 bits=41 from SLAVE
A9151A857A0D80 Visonic or DS10/90 Normal (battery low) addr:151A 0D/22696 bits=41 from SLAVE
A9151A857A0D80 Visonic or DS10/90 Normal (battery low) addr:151A 0D/22696 bits=41 from SLAVE
A9151A857A0D80 Visonic or DS10/90 Normal (battery low) addr:151A 0D/22696 bits=41 from SLAVE

</TD></TR></TBODY></TABLE>
=> door is close

If I open the "IO window" then I don't seem to get much going on at all (compared to the rf receiver):

<TABLE bgColor=#c0c0c0><TBODY><TR><TD>21:30:42 | A9, 15, 1A, 85, 7A, 0D | Discarding A9 while trying to sync on byte-count byte | Discarding 15 while trying to sync on byte-count byte | Discarding 1A while trying to sync on byte-count byte | Discarding 85 while trying to sync on byte-count byte | Discarding 7A while trying to sync on byte-count byte | Discarding 0D while trying to sync on byte-count byte 21:30:42 | 80 | Discarding 80 while trying to sync on byte-count byte</TD></TR></TBODY></TABLE>
=> door is open

<TABLE bgColor=#c0c0c0><TBODY><TR><TD>21:43:41 | A9 | Discarding A9 while trying to sync on byte-count byte
21:43:41 | 15, 1A, 85, 7A, 0D, 80 | Discarding 15 while trying to sync on byte-count byte | Discarding 1A while trying to sync on byte-count byte | Discarding 85 while trying to sync on byte-count byte | Discarding 7A while trying to sync on byte-count byte | Discarding 0D while trying to sync on byte-count byte | Discarding 80 while trying to sync on byte-count byte

</TD></TR></TBODY></TABLE>
=> door is close

xapmcsRF don't reconize all bytes of ds10 ( 41 bits):

first byte :

- if first byte ="29" -> it is the master receiver because bit7=0 and the message lenght is 41 bits

- if first byte ="A9" -> it is the slave receiver because bit7=1 and the message lenght is 41 bits

the others bytes are X10 SECURITY RF format

Thanks for any pointers that you can give!
Dos

**Michael McSharry** · April 25, 2007, 05:08 PM

I did not have any logic for 41 bit DS10A sensor, only the 32 bit variation. I added it with 1.5.7. I will leave the testing to you to confirm proper operation.

**dos** · April 26, 2007, 02:54 PM

xapmscRF: rfxcom & ds10

Hello,
ds10 events appear ok in the xap message, in the "browser" and "IO windows" :
<TABLE bgColor=#c0c0c0><TBODY><TR><TD>19:43:57 | A9, 15, 1A, 85, 7A, 0D
19:43:57 | 80 | 151A=OFF | Security Ignored because location not defined for sensor
19:43:57 | A9, 15
19:43:57 | 1A, 85, 7A, 0D, 80 | Debounce Discard of 151A=OFF
19:43:57 | A9, 15, 1A, 85, 7A
19:43:57 | 0D, 80 | Debounce Discard of 151A=OFF
19:43:57 | 29, 15, 1A, 85
19:43:57 | 7A, 0D, 80, 50, 1A, 2D, 20 | Debounce Discard of 151A=OFF
19:43:57 | A9, 15
19:43:57 | 1A, 85, 7A, 0D, 80 | Debounce Discard of 151A=OFF
</TD></TR></TBODY></TABLE>
=> door is close

<TABLE bgColor=#c0c0c0><TBODY><TR><TD>19:43:59 | A9, 15, 1A, 05, FA
19:43:59 | 0D, 80 | 151A=ON | Security Ignored because location not defined for sensor
19:43:59 | A9, 15, 1A, 05, FA, 0D, 80 | Debounce Discard of 151A=ON
19:43:59 | A9, 15, 1A, 05
19:43:59 | FA, 0D, 80 | Debounce Discard of 151A=ON
19:43:59 | A9, 15, 1A, 05, FA, 0D, 80 | Debounce Discard of 151A=ON
19:43:59 | A9, 15
19:43:59 | 1A, 05, FA, 0D, 80 | Debounce Discard of 151A=ON
</TD></TR></TBODY></TABLE>
=> door is open

Thanks Michael
Dos

**dos** · April 27, 2007, 05:55 AM

xapmscRF: rfxcom/dim-bright

hello,
I have another probleme with x10 rf. when I make a dim or bright I obtain A3 on or A4 on.

I get data flowing in the rfreceiver (RFXCOM software) such as:

<TABLE bgColor=#c0c0c0 border=1><TBODY><TR><TD>command</TD><TD>BYTE 0</TD><TD>BYTE 1</TD><TD>BYTE 2</TD><TD>BYTE 3</TD><TD>BYTE 4</TD></TR><TR><TD>A3-on</TD><TD>20</TD><TD>6O</TD><TD>9F</TD><TD>08</TD><TD>F7</TD></TR><TR><TD>A-bright</TD><TD>20</TD><TD>6O</TD><TD>9F</TD><TD>88</TD><TD>77</TD></TR><TR><TD>A4-on</TD><TD>A0</TD><TD>6O</TD><TD>9F</TD><TD>18</TD><TD>E7</TD></TR><TR><TD>A-dim</TD><TD>A0</TD><TD>6O</TD><TD>9F</TD><TD>98</TD><TD>67</TD></TR></TBODY></TABLE>
I get data flowing in the IO window such as:

<TABLE bgColor=#c0c0c0><TBODY><TR><TD>19:48:44 | 60, 9F, 88, 77 | A3=ON | Ignored because location not defined for sensor
19:48:44 | A0, 60, 9F, 88, 77 | Debounce Discard of A3=ON
19:48:44 | A0, 60, 9F, 88, 77 | Debounce Discard of A3=ON
19:48:45 | A0, 60, 9F, 88, 77 | Debounce Discard of A3=ON

</TD></TR></TBODY></TABLE>
=> A-bright

<TABLE bgColor=#c0c0c0><TBODY><TR><TD>19:48:50 | A0, 60, 9F, 98, 67 | A4=ON | Ignored because location not defined for sensor
19:48:50 | A0, 60, 9F, 98, 67 | Debounce Discard of A4=ON
19:48:50 | A0, 60, 9F, 98, 67 | Debounce Discard of A4=ON
19:48:51 | A0, 60, 9F, 98 19:48:51 | 67 | Debounce Discard of A4=ON>

</TD></TR></TBODY></TABLE>
=> A-dim

xapmcsRF don't reconize bit7 of byte3 :

if bit7 = 1 -> byte 3 is a command (the units numbers are not used) :

<TABLE bgColor=#c0c0c0 border=1><TBODY><TR><TD>command</TD><TD>byte3</TD></TR><TR><TD>dim</TD><TD>0x98</TD></TR><TR><TD>bright</TD><TD>0x88</TD></TR><TR><TD>all lights on</TD><TD>0x90</TD></TR><TR><TD>all units off</TD><TD>0x80</TD></TR></TBODY></TABLE>

if bit7 = 0 -> the units numbers are used.

Thanks
Dos

**Michael McSharry** · April 27, 2007, 06:47 PM

I was checking for the command bits in the reverse bit order of what you describe (e.g. Bright 88 vs 11). I trust you are correct and changed the order in V1.5.9.

**dos** · April 28, 2007, 06:16 AM

Hello,
dim and bright events appear ok in the xap message, in the "browser" and "IO windows" :

<TABLE bgColor=#c0c0c0><TBODY><TR><TD>12:15:32 | 20, 60, 9F
12:15:32 | 98, 67 | A2=DIM | Ignored because location not defined for sensor
12:15:32 | 20, 60, 9F, 98, 67 | Debounce Discard of A2=DIM
12:15:32 | 20, 60, 9F, 98, 67 | Debounce Discard of A2=DIM
12:15:32 | 20, 60
12:15:32 | 9F, 98, 67 | Debounce Discard of A2=DIM
12:15:32 | 20, 60, 9F, 98, 67 | Debounce Discard of A2=DIM
12:15:32 | 20, 60, 9F, 98, 67 | Debounce Discard of A2=DIM
12:15:32 | 20
12:15:32 | 60, 9F, 98, 67 | Debounce Discard of A2=DIM
12:15:32 | 20, 60, 9F, 98
12:15:32 | 67 | Debounce Discard of A2=DIM</TD></TR></TBODY></TABLE>
=> A-dim

<TABLE bgColor=#c0c0c0><TBODY><TR><TD>12:15:40 | 20
12:15:40 | 60, 9F, 88, 77 | A2=BRIGHT | Ignored because location not defined for sensor
12:15:40 | 20, 60, 9F, 88
12:15:40 | 77 | Debounce Discard of A2=BRIGHT
12:15:40 | 20, 60, 9F, 88, 77 | Debounce Discard of A2=BRIGHT
12:15:40 | 20
12:15:40 | 60, 9F, 88, 77 | Debounce Discard of A2=BRIGHT</TD></TR></TBODY></TABLE>

=> A-bright

Thanks Michael
Dos

**dos** · April 28, 2007, 06:22 AM

xamscrf :rfxcom/dim-bright

Hello,
dim and bright events appear ok in the xap message, in the "browser" and "IO windows" :
<TABLE bgColor=#c0c0c0><TBODY><TR><TD>12:15:32 | 20, 60, 9F
12:15:32 | 98, 67 | A2=DIM | Ignored because location not defined for sensor
12:15:32 | 20, 60, 9F, 98, 67 | Debounce Discard of A2=DIM
12:15:32 | 20, 60, 9F, 98, 67 | Debounce Discard of A2=DIM
12:15:32 | 20, 60
12:15:32 | 9F, 98, 67 | Debounce Discard of A2=DIM
12:15:32 | 20, 60, 9F, 98, 67 | Debounce Discard of A2=DIM
12:15:32 | 20, 60, 9F, 98, 67 | Debounce Discard of A2=DIM
12:15:32 | 20
12:15:32 | 60, 9F, 98, 67 | Debounce Discard of A2=DIM
12:15:32 | 20, 60, 9F, 98
12:15:32 | 67 | Debounce Discard of A2=DIM
</TD></TR></TBODY></TABLE>
=> A- dim

<TABLE bgColor=#c0c0c0><TBODY><TR><TD>12:15:40 | 20
12:15:40 | 60, 9F, 88, 77 | A2=BRIGHT | Ignored because location not defined for sensor
12:15:40 | 20, 60, 9F, 88
12:15:40 | 77 | Debounce Discard of A2=BRIGHT
12:15:40 | 20, 60, 9F, 88, 77 | Debounce Discard of A2=BRIGHT
12:15:40 | 20
12:15:40 | 60, 9F, 88, 77 | Debounce Discard of A2=BRIGHT
</TD></TR></TBODY></TABLE>
=> A-bright

Thanks Michael
Dos

**matisere** · October 12, 2007, 02:59 PM

Hello Michael,
I can not distinguish between the ARM and Light ON neither DISARM and Light OFF on remote KR21 also for the PANIC button.
Could you help me?

**Michael McSharry** · October 12, 2007, 04:14 PM

I'm assuming a KR21 is a visonic part. If you provide a snapshot of what is being received from the IO window and what is being sent via xAP vs. what you are expecting then we have a chance. It would also be nice if the discussion was moved from this thread to a new one in the xAP Discussion subforum do the library does not get cluttered.

**Michael McSharry** · October 12, 2007, 06:50 PM

Bert indicated that this is the same as the KR10 which is included in his decode document. It was added to V1.7.9 of xapmcsRF.

Announcement

xapmcsRF - W800 / RFXCOM xAP Node

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment