Announcement

**Michael McSharry** · March 22, 2006, 11:57 PM

Node status screenshot

Attached Files

**Michael McSharry** · April 2, 2006, 01:36 AM

Updates made to provide setup options that provide the following features:
1. Allow signal inversion so that something like a dusk sensor can be treated as a dawn sensor
2. Allow xapBSC and/or xap-x10 for any message reporting
3. Allow xap-x10.request to be delivered similar to retransmit to any X10 address
4. Allow software to generate the OFF timing in lieu of the hardware OFF sent by device. This allows automatic debouncing

**jasv** · April 2, 2006, 12:20 PM

Very cool

I am not ready to use this but I will be in a couple of weeks. Thanks for this addition to xap.

**Michael McSharry** · April 2, 2006, 01:06 PM

I just noticed that the PC Remote protocol was published in another thread today. Looks pretty easy so I'll add it. I had done the temp/humidity sensors already, but only coded per spec since I do not have any of these with which to test.

**Michael McSharry** · April 2, 2006, 03:31 PM

I reposted with the X10 PC Remote recognition added. I did notice that the same RF code is used for "PC" and "4". I selected to interpret it as "4" . I also made the debounce interval for the PC Remote 50% of the other sensors to enhance the Vol+ and other similiar continuous buttons.

**martynw** · August 31, 2006, 01:24 PM

xapmcsRF with visonic receiver

Hello,

I've just installed a visonic powermax alarm system with pirs, contacts, smoke detectors, etc and have setup an RFXCOM Visonic interface (868 mhz version).

I'm attempting to get it playing nicely together with xapmcsRF but don't seem to be getting anywhere!

The rfxcom unit is installed and working, if I fire up the "visonic receiver" application from their software cd I get data flowing in the viewer such as:

Code:

 
31/08/2006 19:21:07= 24107D661C60			 PowerCode Addr:107D66 No Tamper,Close,Battery-OK ,Alive,Restore reported	,Primary contact 
31/08/2006 19:22:13= 242C7D661C90			 PowerCode Addr:2C7D66 No Tamper,Close,Battery-OK ,Alive,Restore reported	,Primary contact 
31/08/2006 19:22:13= 242C7D661C90			 PowerCode Addr:2C7D66 No Tamper,Close,Battery-OK ,Alive,Restore reported	,Primary contact 
31/08/2006 19:22:13= 242C7D661C90			 PowerCode Addr:2C7D66 No Tamper,Close,Battery-OK ,Alive,Restore reported	,Primary contact 
31/08/2006 19:22:14= 242C7D661C90			 PowerCode Addr:2C7D66 No Tamper,Close,Battery-OK ,Alive,Restore reported	,Primary contact 
31/08/2006 19:22:14= 242C7D661C90			 PowerCode Addr:2C7D66 No Tamper,Close,Battery-OK ,Alive,Restore reported	,Primary contact 
31/08/2006 19:22:14= 242C7D661C90			 PowerCode Addr:2C7D66 No Tamper,Close,Battery-OK ,Alive,Restore reported	,Primary contact 
31/08/2006 19:22:25= 24F5ABC61440			 PowerCode Addr:F5ABC6 No Tamper,Close,Battery-OK ,Alive,Restore not reported,Primary contact 
31/08/2006 19:22:25= 24F5ABC61440			 PowerCode Addr:F5ABC6 No Tamper,Close,Battery-OK ,Alive,Restore not reported,Primary contact 
31/08/2006 19:22:26= 24F5ABC61440			 PowerCode Addr:F5ABC6 No Tamper,Close,Battery-OK ,Alive,Restore not reported,Primary contact 
31/08/2006 19:22:26= 24F5ABC61440			 PowerCode Addr:F5ABC6 No Tamper,Close,Battery-OK ,Alive,Restore not reported,Primary contact 
31/08/2006 19:22:26= 24F5ABC61440			 PowerCode Addr:F5ABC6 No Tamper,Close,Battery-OK ,Alive,Restore not reported,Primary contact 
31/08/2006 19:22:26= 24F5ABC61440			 PowerCode Addr:F5ABC6 No Tamper,Close,Battery-OK ,Alive,Restore not reported,Primary contact 
31/08/2006 19:22:46= 24C627C61400			 PowerCode Addr:C627C6 No Tamper,Close,Battery-OK ,Alive,Restore not reported,Primary contact 
31/08/2006 19:22:46= 24C627C61400			 PowerCode Addr:C627C6 No Tamper,Close,Battery-OK ,Alive,Restore not reported,Primary contact 
31/08/2006 19:22:46= 24C627C61400			 PowerCode Addr:C627C6 No Tamper,Close,Battery-OK ,Alive,Restore not reported,Primary contact 
31/08/2006 19:22:46= 24C627C61400			 PowerCode Addr:C627C6 No Tamper,Close,Battery-OK ,Alive,Restore not reported,Primary contact 
31/08/2006 19:22:46= 24C627C61400			 PowerCode Addr:C627C6 No Tamper,Close,Battery-OK ,Alive,Restore not reported,Primary contact

If I fire up xapmcsrf then I don't seem to get much at all. I get a few event.log xap messages (pertinent bits below):

Code:

 xap-header 
 
{
 
v=12
 
hop=1
 
uid=FF005200
 
class=Homeseer.Event
 
source=mcs.W800.AHSHA
 
}
 
Event.Log
 
{
 
time=31/08/2006 19:24:34
 
type=xapmcsW800
 
data=W800 Comm Port 7 Opened
 
}
 
xap-header
{
 
v=12
 
hop=1
 
uid=FF005200
 
class=Homeseer.Event
 
source=mcs.W800.AHSHA
 
}
 
Event.Log
 
{
 
time=31/08/2006 19:24:35
 
type=xapmcsW800
 
data=Receiver confirmed 32 bit mode configuration
 
}

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

Code:

19:25:50 | 4C, BD, 8C
19:25:50 | 73
19:26:09 | 3D | Discarding 4C
19:26:09 | 19, 8C, 73

Firing up a web browser and viewing the status page doesn't seem to show anything either.

Am I doing something wrong (or stupid

)? Or is xapmcsrf not compatible with the visonic receiver?

Thanks for any pointers that you can give!

Martyn

**Michael McSharry** · August 31, 2006, 03:19 PM

I'm not familiar with what Bert did different for the Visonic interface. Just now I saw the protocol docs on his web site. When I look at the X10-equivalent command set and protocol in section 8 of his document I do not see a correlation with the 48 bit data stream in your visonic receiver. As an example...

24 10 7D 66 1C 60

Where I expect the 3rd & 4th bytes to be complements of each other.

I also see that xapmcsRF is configured for 32 bit operation. Independent of that, however, is that the IO window shows the raw data stream from the RFCOM receiver is not seeing much. I would expect the equivalent activity level between the two receivers.

If Bert could chime in a identify the nature of the Visonic interface or make any other observations then we will make progress much faster.

**b_weijenberg** · August 31, 2006, 05:00 PM

Martyn,

In the screen dump the receiver is operating in Visonic mode and the received data is the real untranslated RF data.

Using the "visonic receiver" program, init the receiver in 32 bit mode (NOT 32 bit X10 mode).

BTW: At the download page of www.rfxcom.com there is a new version of the RFreceiver program that works now with all type of receivers, also the visonic.

Michael,
the RFXCOM receiver is set into 32 bit mode (W800 compatible) by sending 2 characters hex F0 - hex 29. The receiver responds then with hex 29. If your program can start with sending the hex F029 and waits for the response hex 29 the program can detect that the receiver is connected and operational. The same is true for a W800.

Bert

**martynw** · August 31, 2006, 05:16 PM

Hello Michael, Bert

Thanks for the quick responses!

With the new RF receiver software init to "32 bit mode" I get:

Code:

 
Init cmd to receiver => F029
29 ACK 
32E90CF3 Visonic motion sensor Alert 
107D847B Visonic door sensor	Normal

With xapmcsrf I get:

Code:

23:18:14 | F5, AB, 0C, F3
23:18:31 | EC, B9, 0C, F3 | Discarding F5
23:18:36 | FE, DD, 0C, F3 | Discarding 00 | Discarding 00 | Discarding 00

Hope this helps!

Martyn

**Michael McSharry** · August 31, 2006, 05:18 PM

The setup of the 32 bit mode was done and did show in the xAP message posted. What I do not understand is why very little data was received by the RFXCOM. The visonics protocol document describes some X10 compatibility translations. If this is being used in non-X10 mode then how should the data be interpreted?

**b_weijenberg** · September 1, 2006, 04:28 AM

In 32 bit mode the received data has the same format as the X10 security.
However:
1- All duplicate RF messages (~20 in Visonic RF) are suppressed and only one packet is send to the RS232 port to lower the load of the PC. The Visonic packets are checked in the receiver on validity using the parity control bits and only valid RF packets are translated to X10 format and 1 packet is send to the RS232 port.
2- In the X10 definition the 2nd byte is a half complement of the 1st byte. But the RFXCOM Visonic receiver transmits in the first 2 bytes a real 16 bits address. This is to eliminate the possibility to have duplicate sensor addresses. If only 8 bits of the Visonic sensor address where used then there is a big chance to get duplicated addresses. The sensor address is fixed and can't be changed in the sensor (even after a battery change stays the address the same).

I guess the 3 messages are valid packets from 3 different sensors giving an Alert signal:
23:18:14 | F5, AB, 0C, F3 sensor addr F5AB Alert 0C
23:18:31 | EC, B9, 0C, F3 sensor addr ECB9 Alert 0C
23:18:36 | FE, DD, 0C, F3 sensor addr FEDD Alert 0C

Bert

**Michael McSharry** · September 1, 2006, 02:33 PM

I added the X10 mode of the Visonic to V1.3.3.

Each Device will show up as three entities with the device codes of
xxxxS0,xxxxS1, and xxxxKF that correspond to the sensor bit 7 off,on and the keyfob.

The sensor Alert/Normal will be ON/OFF state respectively and may be event or info depending upon the prior state. The BatteryLow and Tamper will always be an event. All keyfob actions will be events.

Some sample messages...

Code:

xap-header
{
    v=12
    hop=1
    uid=FF005202
    class=xapbsc.info
    source=mcs.W800.MCS5:S1.W800________F5ABS1.S1.State
}
input.state.1
{
    state=Off
}

Code:

xap-header
{
    v=12
    hop=1
    uid=FF005202
    class=xapbsc.event
    source=mcs.W800.MCS5:S1.W800________F5ABS1.S1.BatteryLow
}
input.state.1
{
    state=ON
}

**martynw** · September 1, 2006, 02:46 PM

That's fantastic Michael, thanks very much!

I'll have a play over the weekend and report back.

Martyn

**martynw** · September 1, 2006, 04:40 PM

Originally posted by Michael McSharry

Each Device will show up as three entities with the device codes of
xxxxS0,xxxxS1, and xxxxKF that correspond to the sensor bit 7 off,on and the keyfob.

Hi Michael,

I'm a little confused at the above, can you expand please?

I'm looking at a PIR device that gives the following device codes:

FEDDKF
FEDDS0
FEDDS1

What do they represent?

Thanks,

Martyn

Announcement

xapmcsRF - W800 / RFXCOM xAP Node

xapmcsRF - W800 / RFXCOM xAP Node

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment