RFXCom Rx Not receiving.

[danward79]

Hi Guy's

Just trying out the RFXCom Component, set it up for my comport etc, but I do not seem to be getting, any events it says it is connected ok, but I get this in the lua console.


Initialized RFXCOM instance
TreeScript (golua): ...der5\luascript\Classes/DUI/ConfigSerialInstances.lua:289: attempt to index a boolean value
stack traceback:
...der5\luascript\Classes/DUI/ConfigSerialInstances.lua:289: in function `?'
...romixis\Girder5\luascript\Classes/DUI/ConfigEdit.lua:210: in function `OnEvent'
...der5\luascript\Classes/DUI/ConfigSerialInstances.lua:245: in function `OnEvent'
...romixis\Girder5\luascript\Classes/DUI/ConfigBase.lua:53: in function <...romixis\Girder5\luascript\Classes/DUI/ConfigBase.lua:49>

[Promixis]

Dan,

you may need to delete all prior rfxcom stuff you had - all of the old rfxcom lua files. also all old w800 files need to go.

plus - don't you have the w800 receiver, not a rfxcom receiver?

[danward79]

Hi Mike,

No I changed to an RFXCom a long while ago.

As for the files I did delete everything, I did an uninstall before I installed.

[Promixis]

Is the component enabled?

[danward79]

Is the component enabled?

Of course! :rolleyes::p

[danward79]

Any other ideas?

[danward79]

The w800 plugin seems to working fine, if that helps.

[Ron]

Did you delete the config files in the userdata directory?

[danward79]

Did you delete the config files in the userdata directory?

Did a full uninstall. Just tried deleting all rfxcom cfg's made no difference.

[Ron]

So..

. You deleted all config files in the user directory?
C:\Documents and Settings\ron\Application Data\Promixis\Girder\5\Config

. Enabled the RFXCOM component
. Went to RF Devices - Receivers
. The dropdown is empty.
. Hit add
. Enter some name and select com port.
. Hit OK.

That seems to work on my end,.. keep an eye on the lua console and report when this goes wrong.

[danward79]

That is exactly what I have been doing.

Did you seen the console output, I posted in my first post.

Does the rfxcom receiver need to be in a certain mode for the plugin?

[Ron]

I did see you console output but I was wondering when it popped up as it is not giving any errors on my end.

[danward79]

Ok, I just did a total uninstall, deleted all configs again and then reinstalled started g5, and tried to load rfxcom receiver plugin. It would not let me set a com port when I added an instance.

This is the console output.


LOG: Component Manager : 5 - Error reading component configuration file: ComponentManager.cfg Error: File doesn't exist
LOG: Device Manager : 4 - Unable to read config file DeviceManager.cfg File doesn't exist
Loading RFXCOMReceiver.lua
Loaded RFXCOMReceiver.lua
Welcome to Promixis Girder 5.0.0 build 517
...mixis\Girder5\luascript\components\SunriseSunse t.lua:509: attempt to index global `GeographicalLocation' (a nil value)
stack traceback:
...mixis\Girder5\luascript\components\SunriseSunse t.lua:509: in function `GetLocalSunrise'
...mixis\Girder5\luascript\components\SunriseSunse t.lua:244: in function `SetupTodaysEvents'
...mixis\Girder5\luascript\components\SunriseSunse t.lua:208: in function `SetupSchedules'
...mixis\Girder5\luascript\components\SunriseSunse t.lua:161: in function `Enable'
...iles\Promixis\Girder5\luascript\ComponentManage r.lua:305: in function `EnableComponent'
...iles\Promixis\Girder5\luascript\ComponentManage r.lua:271: in function `ProcessComponentRequires'
...iles\Promixis\Girder5\luascript\ComponentManage r.lua:293: in function `EnableComponent'
...iles\Promixis\Girder5\luascript\ComponentManage r.lua:543: in function `StartEnabledComponents'
...iles\Promixis\Girder5\luascript\ComponentManage r.lua:219: in function <...iles\Promixis\Girder5\luascript\ComponentManage r.lua:218>
[C]: ?
...iles\Promixis\Girder5\luascript\ComponentManage r.lua:218: in function <...iles\Promixis\Girder5\luascript\ComponentManage r.lua:217>
Initialized RFXCOM instance
TreeScript (golua): ...\luascript\Components/Classes/InstancesContainer.lua:159: ...romixis\Girder5\luascript\Classes/Transport/Core.lua:558: bad argument #1 to `Open' (number expected, got string)
stack traceback:
[C]: in function `Open'
...romixis\Girder5\luascript\Classes/Transport/Core.lua:558: in function `Connect'
...romixis\Girder5\luascript\Classes/Transport/Base.lua:101: in function `Initialize'
...romixis\Girder5\luascript\Classes/Transport/Base.lua:77: in function `New'
...\luascript\Components/Classes/InstancesContainer.lua:194: in function `StartInstance'
...\luascript\Components/Classes/InstancesContainer.lua:158: in function <...\luascript\Components/Classes/InstancesContainer.lua:158>
[C]: in function `xpcall'
...\luascript\Components/Classes/InstancesContainer.lua:158: in function `AddInstanceSetting'
...\Girder5\/plugins/treescript/RFXCOM Receivers UI.lua:273: in function `?'
...romixis\Girder5\luascript\Classes/DUI/ConfigEdit.lua:210: in function `OnEvent'
...\Girder5\/plugins/treescript/RFXCOM Receivers UI.lua:239: in function `OnEvent'
...romixis\Girder5\luascript\Classes/DUI/ConfigBase.lua:53: in function <...romixis\Girder5\luascript\Classes/DUI/ConfigBase.lua:49>
stack traceback:
[C]: in function `assert'
...\luascript\Components/Classes/InstancesContainer.lua:159: in function `AddInstanceSetting'
...\Girder5\/plugins/treescript/RFXCOM Receivers UI.lua:273: in function `?'
...romixis\Girder5\luascript\Classes/DUI/ConfigEdit.lua:210: in function `OnEvent'
...\Girder5\/plugins/treescript/RFXCOM Receivers UI.lua:239: in function `OnEvent'
...romixis\Girder5\luascript\Classes/DUI/ConfigBase.lua:53: in function <...romixis\Girder5\luascript\Classes/DUI/ConfigBase.lua:49>
Initialized RFXCOM instance
TreeScript (golua): ...\luascript\Components/Classes/InstancesContainer.lua:159: ...romixis\Girder5\luascript\Classes/Transport/Core.lua:558: bad argument #1 to `Open' (number expected, got string)
stack traceback:
[C]: in function `Open'
...romixis\Girder5\luascript\Classes/Transport/Core.lua:558: in function `Connect'
...romixis\Girder5\luascript\Classes/Transport/Base.lua:101: in function `Initialize'
...romixis\Girder5\luascript\Classes/Transport/Base.lua:77: in function `New'
...\luascript\Components/Classes/InstancesContainer.lua:194: in function `StartInstance'
...\luascript\Components/Classes/InstancesContainer.lua:158: in function <...\luascript\Components/Classes/InstancesContainer.lua:158>
[C]: in function `xpcall'
...\luascript\Components/Classes/InstancesContainer.lua:158: in function `AddInstanceSetting'
...\Girder5\/plugins/treescript/RFXCOM Receivers UI.lua:273: in function `?'
...romixis\Girder5\luascript\Classes/DUI/ConfigEdit.lua:210: in function `OnEvent'
...\Girder5\/plugins/treescript/RFXCOM Receivers UI.lua:239: in function `OnEvent'
...romixis\Girder5\luascript\Classes/DUI/ConfigBase.lua:53: in function <...romixis\Girder5\luascript\Classes/DUI/ConfigBase.lua:49>
stack traceback:
[C]: in function `assert'
...\luascript\Components/Classes/InstancesContainer.lua:159: in function `AddInstanceSetting'
...\Girder5\/plugins/treescript/RFXCOM Receivers UI.lua:273: in function `?'
...romixis\Girder5\luascript\Classes/DUI/ConfigEdit.lua:210: in function `OnEvent'
...\Girder5\/plugins/treescript/RFXCOM Receivers UI.lua:239: in function `OnEvent'
...romixis\Girder5\luascript\Classes/DUI/ConfigBase.lua:53: in function <...romixis\Girder5\luascript\Classes/DUI/ConfigBase.lua:49>
Initialized RFXCOM instance
TreeScript (golua): ...\luascript\Components/Classes/InstancesContainer.lua:159: ...romixis\Girder5\luascript\Classes/Transport/Core.lua:558: bad argument #1 to `Open' (number expected, got string)
stack traceback:
[C]: in function `Open'
...romixis\Girder5\luascript\Classes/Transport/Core.lua:558: in function `Connect'
...romixis\Girder5\luascript\Classes/Transport/Base.lua:101: in function `Initialize'
...romixis\Girder5\luascript\Classes/Transport/Base.lua:77: in function `New'
...\luascript\Components/Classes/InstancesContainer.lua:194: in function `StartInstance'
...\luascript\Components/Classes/InstancesContainer.lua:158: in function <...\luascript\Components/Classes/InstancesContainer.lua:158>
[C]: in function `xpcall'
...\luascript\Components/Classes/InstancesContainer.lua:158: in function `AddInstanceSetting'
...\Girder5\/plugins/treescript/RFXCOM Receivers UI.lua:273: in function `?'
...romixis\Girder5\luascript\Classes/DUI/ConfigEdit.lua:210: in function `OnEvent'
...\Girder5\/plugins/treescript/RFXCOM Receivers UI.lua:239: in function `OnEvent'
...romixis\Girder5\luascript\Classes/DUI/ConfigBase.lua:53: in function <...romixis\Girder5\luascript\Classes/DUI/ConfigBase.lua:49>
stack traceback:
[C]: in function `assert'
...\luascript\Components/Classes/InstancesContainer.lua:159: in function `AddInstanceSetting'
...\Girder5\/plugins/treescript/RFXCOM Receivers UI.lua:273: in function `?'
...romixis\Girder5\luascript\Classes/DUI/ConfigEdit.lua:210: in function `OnEvent'
...\Girder5\/plugins/treescript/RFXCOM Receivers UI.lua:239: in function `OnEvent'
...romixis\Girder5\luascript\Classes/DUI/ConfigBase.lua:53: in function <...romixis\Girder5\luascript\Classes/DUI/ConfigBase.lua:49>
I then exited and loaded girder again, this is the console output, before I did a thing.



Loading RFXCOMReceiver.lua
Loaded RFXCOMReceiver.lua
Welcome to Promixis Girder 5.0.0 build 517
...mixis\Girder5\luascript\components\SunriseSunse t.lua:509: attempt to index global `GeographicalLocation' (a nil value)
stack traceback:
...mixis\Girder5\luascript\components\SunriseSunse t.lua:509: in function `GetLocalSunrise'
...mixis\Girder5\luascript\components\SunriseSunse t.lua:244: in function `SetupTodaysEvents'
...mixis\Girder5\luascript\components\SunriseSunse t.lua:208: in function `SetupSchedules'
...mixis\Girder5\luascript\components\SunriseSunse t.lua:161: in function `Enable'
...iles\Promixis\Girder5\luascript\ComponentManage r.lua:305: in function `EnableComponent'
...iles\Promixis\Girder5\luascript\ComponentManage r.lua:271: in function `ProcessComponentRequires'
...iles\Promixis\Girder5\luascript\ComponentManage r.lua:293: in function `EnableComponent'
...iles\Promixis\Girder5\luascript\ComponentManage r.lua:543: in function `StartEnabledComponents'
...iles\Promixis\Girder5\luascript\ComponentManage r.lua:219: in function <...iles\Promixis\Girder5\luascript\ComponentManage r.lua:218>
[C]: ?
...iles\Promixis\Girder5\luascript\ComponentManage r.lua:218: in function <...iles\Promixis\Girder5\luascript\ComponentManage r.lua:217>
I then went into component manager, had to re enable the rfx component as it did not remember it, and tried to set a com port which is not listed, non are.

[danward79]

Loading RFXCOMReceiver.lua
Loaded RFXCOMReceiver.lua
Welcome to Promixis Girder 5.0.0 build 517
...mixis\Girder5\luascript\components\SunriseSunse t.lua:509: attempt to index global `GeographicalLocation' (a nil value)
stack traceback:
...mixis\Girder5\luascript\components\SunriseSunse t.lua:509: in function `GetLocalSunrise'
...mixis\Girder5\luascript\components\SunriseSunse t.lua:244: in function `SetupTodaysEvents'
...mixis\Girder5\luascript\components\SunriseSunse t.lua:208: in function `SetupSchedules'
...mixis\Girder5\luascript\components\SunriseSunse t.lua:161: in function `Enable'
...iles\Promixis\Girder5\luascript\ComponentManage r.lua:305: in function `EnableComponent'
...iles\Promixis\Girder5\luascript\ComponentManage r.lua:271: in function `ProcessComponentRequires'
...iles\Promixis\Girder5\luascript\ComponentManage r.lua:293: in function `EnableComponent'
...iles\Promixis\Girder5\luascript\ComponentManage r.lua:543: in function `StartEnabledComponents'
...iles\Promixis\Girder5\luascript\ComponentManage r.lua:219: in function <...iles\Promixis\Girder5\luascript\ComponentManage r.lua:218>
[C]: ?
...iles\Promixis\Girder5\luascript\ComponentManage r.lua:218: in function <...iles\Promixis\Girder5\luascript\ComponentManage r.lua:217>
This is different to before I did the uninstall, as it remembered the component was enable and the serial port and showed it as opened ok.

[Ron]

We'll have to wait for Mike.

[Promixis]

Dan, this appears to be related to order of components loading... we have not seen it happen here :(

This *should* fix the problem. Goes in the component dir.

[danward79]

Thanks Mike that got rid of the errors but I still get no rfxcom rx events. There is nothing in the colsole or the log.

Does the rfxcom antenna have to be in a particular mode?

[Promixis]

Thanks Mike that got rid of the errors but I still get no rfxcom rx events. There is nothing in the colsole or the log.

Does the rfxcom antenna have to be in a particular mode?

The rest of the code is Rob's. Did you try the RFXCOM test software to make sure its working?

[danward79]

I used the w800rf32 to chk, that....

[Promixis]

no - try their software to make the receiver is working?

[Rob H]

Which components have you enabled? You need the RFXCOM Receiver and the RFXCOM Transmitters component to process RFXCOM one-wire devices.

[danward79]

I have X10 tx's, RFXCom Tx's and RFXCom Rx installed.

Sensor wise I have RFXCom Type 1 & 6 sensors, plus some visionic and x10 pir's

[danward79]

Rob, Does the plugin require the receiver in a specific mode?

[b_weijenberg]

Dan,

I don't know which mode is used but Variable Length mode would be the best choice. If right after the COM port initialization the command 0xF02C is send to the receiver the receiver will be set to variable length mode and the receiver responds with 0x2C as an indication that the receiver is connected and operational.

Bert

[Rob H]

I'm currently using mode F041 - which it sends to the RFXCOM on startup. Which , as I read the documentation, should set Visonic mode with X10 enabled.

I can try F02C if you think it would be better Bert.

[b_weijenberg]

F041 is possible but all Visonic data is transmitted to Girder without translation.
If you use F02C then all Visonic sensor and keyfob data is translated to the X10 equivalent command. This makes it much easier because the X10 security decoding software can be used for Visonic too.

[Promixis]

F041 is possible but all Visonic data is transmitted to Girder without translation.
If you use F02C then all Visonic sensor and keyfob data is translated to the X10 equivalent command. This makes it much easier because the X10 security decoding software can be used for Visonic too.

Bert, we have developed seperate components to deal with the various types of RFtransmitters. ie x10, rfxcom, and (coming) visonic. In this case, would it not be best to variable length mode? Does the 2C mode limit the visonic sensors to just x10 type addressing and data?

[Promixis]

F041 is possible but all Visonic data is transmitted to Girder without translation.
If you use F02C then all Visonic sensor and keyfob data is translated to the X10 equivalent command. This makes it much easier because the X10 security decoding software can be used for Visonic too.

Also, the 315 sensor is working here. Didn't receive an antenna with it - just a short yellow wire. Is this the antenna?

[danward79]

Any ideas on my problem Rob?

[b_weijenberg]

You should have received a groundplane antenna too. I will ask Ronald to send you one. For the time being you can use the yellow wire antenna.

In variable length mode almost all Visonic data is available. In chapter 10 is explained how the translation is done.
You can of course use F041 but this needs additional coding. You will also receive a lot of RF packets in F041 mode (about 18) while in F02C you only will receive 1 packet. There is no need to receive more then one packet on the COM interface. The reason that 18 Visonic RF packets (normally 5 for X10) are transmitted is that the signal can be disturbed by other RF signals.
All duplicate packets are ignored for 5 seconds in F02C mode.

In F029 (32 bit mode) the Visonic packets are repeated 3 times. The reason is that some programs did a check on multiple packets and they need at least 3 packets (MisterHouse)

Bert

[b_weijenberg]

Dan, did you receive my email?

Bert

[Promixis]

Any ideas on my problem Rob?

Dan goto luscript/classes/rfxcom.lua. at line 187 (below HandleData) add print (event)

[b_weijenberg]

Mike,

I checked for the antenna. The Visonic receivers don't have the groundplane in the package. At least for the 433 and the 868 receivers the wire antenna is OK and I expect that you will have also good results using the wire antenna on the 315 receiver.
The receiving distance must be equal to the Visonic panel. A normal situation is that the keyfob has a transmit range of about 8 meters and the sensors > 50 meters free sight.

Bert

[danward79]

Actually ignore this message!

[danward79]

Dan, did you receive my email?

Bert

No, I did add you to my msn buddies thou.

[danward79]

it is failing in RFXCom receiver.lua


RXXX Data: 20 60 9F 98 67 `Ÿ˜g Code: RXCHAR
RXXX Data: 20 60 9F 98 67 `Ÿ˜g Code: RXCHAR
RXXX Data: 20 60 9F 98 67 `Ÿ˜g Code: RXCHAR
RXXX Data: 20 60 9F 98 67 `Ÿ˜g Code: RXCHAR
RXXX Data: 20 60 9F 98 67 `Ÿ˜g Code: RXCHAR
RXXX Data: 20 60 9F 98 67 `Ÿ˜g Code: RXCHAR
RXXX Data: 20 60 9F 98 67 `Ÿ˜g Code: RXCHAR
RXXX Data: 20 60 9F 98 67 `Ÿ˜g Code: RXCHAR
RXXX Data: 20 60 9F 98 67 `Ÿ˜g Code: RXCHAR
RXXX Data: 20 60 9F 98 67 `Ÿ˜g Code: RXCHAR
RXXX Data: 20 60 9F 98 67 `Ÿ˜g Code: RXCHAR
RXXX Data: 20 60 9F 98 67 `Ÿ˜g Code: RXCHAR
RXXX Data: 20 60 9F 98 67 `Ÿ˜g Code: RXCHAR
RXXX Data: 20 60 9F 98 67 `Ÿ˜g Code: RXCHAR


this is the function


OnReceiveData = function(self, event)
print("RXXX", event)
local data = event:GetData()
if data and string.len(data) > 0 then
self:CancelTimeout()
--print(math.formatbytes(data))
if self.AwaitingACK then
if string.len(data) == 1 and string.byte(data) == math.hextodecimal('41') then
self.AwaitingACK = false


end
return
end
--[[
else
-- at this point pass the data up to whoever is listening
local success, data = false, data
local attempt = 1
repeat
success, data = self:PartitionData(data, attempt)
if not success then
--print('Trying '..math.formatbytes(data))
else
--print('Success')
end
attempt = attempt + 1
until success or (string.len(data) == 0)
if self.Bytecount > 0 then
self:ArmTimeout()
end
end
--]] print("x")
self:Event (self.Events.Receive,data)
end
end,

Catch you later I am off to a party!

[Rob H]

Hmmm.... looks like it's not getting the acknowledgement of the initialisation back.

[danward79]

Here the output after girder starts up, is the first line the acknowledge?


Loading RFXCOMReceiver.lua
Loaded RFXCOMReceiver.lua
Welcome to Promixis Girder 5.0.0 build 517
Initialized RFXCOM instance
RXXX Data: 01 FD .ý Code: RXCHAR
RXXX Data: 20 E0 1F 10 EF à..ï Code: RXCHAR
RXXX Data: 20 E0 1F 10 EF à..ï Code: RXCHAR
RXXX Data: 20 E0 1F 10 EF à..ï Code: RXCHAR
RXXX Data: 20 E0 1F 10 EF à..ï Code: RXCHAR

[b_weijenberg]

Rob,

If Dan's X10 receiver has a software version lower than 9 it will not respond on the 0xF041 initialization command.
The support for a Visonic and an X10 receiver in one USB interface is implemented in X10 receiver version 9 and up.
See the firmware revision history at the end of this page: http://www.rfxcom.com/descr_433_X10_Oregon.htm

Bert

[Rob H]

Ah, that's probably it then.

Does that mean that Dan won't be able to use both X10 and Visonic without upgrading the firmware? Or do I just need to use F02C to initialise?

[b_weijenberg]

F02C will operate on any RFXCOM receiver so that is a possibility. In this mode the Visonic sensors will operate like X10 sensors.
However, the first 2 address bytes of the X10 security sensor have a format:
Byte 1 is device address
Byte 2 lower nibble is complement of Byte 1, upper nibble is Byte 1
This format is not used for translated Visonic sensors! The first 2 bytes of a converted Visonic to X10 packet contains a real 16 bits address.
So if you do a check on the first 2 bytes of the X10 security packet to check the validity of the packet this must be changed then.


Dan can contact me for an upgrade of the X10 receiver.
An upgrade is only possible if the receiver contains a PIC16F688 microcontroller. Dutch people can send me the receiver and add a SASE and the upgrade will be free. People from other countries can send me the receiver and the cost will be 5 euro for handling & shipping.
The latest version of the X10 receiver can also receive Oregon Scientific sensors and Domia Lite remotes.

Bert

[danward79]

It receives Visonic and X10 Ok, I think you need to set it to work Variable Length mode (i.e F02C)

[danward79]

If I initialise my receiver to Visonic & Variable mod, then do a get software version I get this.

Init cmd to receiver => F041
01FF ACK
Version request to receiver => F020
4900FE Version 49 00

[b_weijenberg]

The version indication is not valid because the F041 command disturbed the communication.
This is because your receiver doesn't support the F041 command.

Send a variable length command and then the software version request.

[danward79]

The version indication is not valid because the F041 command disturbed the communication.
This is because your receiver doesn't support the F041 command.

Send a variable length command and then the software version request.

Ok this is what I got


Init cmd to receiver => F02C
04F9 ACK
Version request to receiver => F020
0D00F8 Version 0D 00

[b_weijenberg]

Dan, still not OK. You need to see something like this:

Init cmd to receiver => F02C
2C ACK
Version request to receiver => F020
4D13 Version Master=13

[danward79]

I don't seem to be getting a constant result.

Init cmd to receiver => F02C
20FE ACK
Version request to receiver => F020
0804 Version 08 04
Version request to receiver => F020
4D02 Version Master=02
Init cmd to receiver => F02C
20FE ACK
Version request to receiver => F020
4D02 Version Master=02
Init cmd to receiver => F02C
20FE ACK
Version request to receiver => F020
4D02 Version Master=02
Version request to receiver => F020
0808 Version 08 08
Version request to receiver => F020
0500FE Version 05 00
Version request to receiver => F020
4D02 Version Master=02
Version request to receiver => F020
0804 Version 08 04
Version request to receiver => F020
4D02 Version Master=02
Version request to receiver => F020
0804 Version 08 04
Version request to receiver => F020
4D02 Version Master=02
Version request to receiver => F020
4D02 Version Master=02
Version request to receiver => F020
0508FF Version 05 08
Version request to receiver => F020
0804 Version 08 04
Version request to receiver => F020
0808 Version 08 08
Version request to receiver => F020
0500FE Version 05 00
Version request to receiver => F020
4D02 Version Master=02
Version request to receiver => F020
4902FE Version 49 02
Version request to receiver => F020
4902FF Version 49 02
Version request to receiver => F020
0808 Version 08 08
Version request to receiver => F020
0804 Version 08 04
Version request to receiver => F020
0508FF Version 05 08
Version request to receiver => F020
0500FE Version 05 00
Version request to receiver => F020
0804 Version 08 04
Version request to receiver => F020
4D02 Version Master=02
Version request to receiver => F020
0808FF Version 08 08
Version request to receiver => F020
4D02 Version Master=02
Version request to receiver => F020
4D08 Version Master=08

[b_weijenberg]

This must be a receiver with version 1 or 2! Those versions don't support the software version command. At that time I didn't know that so many versions at high speed would follow.
It is not possible to upgrade the very old receivers because they use another type of microcontroller (PIC16F676) with less memory.

Bert

[danward79]

Ok, We have got the antenna problem sorted now, turns out mine had two masters in it. So I have removed one until I get another in the post.

So. The x10 master now responds to 041 Initialisation. So I am in bussiness. But it seems not to be working relaibly.

For example events are not always being generated. Even thou data is received. Here is the console output for a sensor not being processed.


ProcessReceive 20 20 D0 1A 05 Ð..
ProcessReceive 20 20 D0 1A 05 Ð..
ProcessReceive 20 20 D0 1A 05 Ð..
ProcessReceive 20 21 D1 32 CD !Ñ2Í
ProcessReceive 20 21 D1 32 CD !Ñ2Í
ProcessReceive 20 21 D1 32 CD !Ñ2Í


It also looks like it is the same with x10 data too.


ProcessReceive 20 E0 1F 30 CF à.0Ï
ProcessReceive 20 E0 1F 30 CF à.0Ï
ProcessReceive 20 E0 1F 30 CF à.0Ï
ProcessReceive 20 E0 1F 30 CF à.0Ï


All of these work perfectly with the w800 component, just not the rfxcom component

[danward79]

It also seems that the temperature is in Degree's F regardless of the unit settings.

[Promixis]

It also seems that the temperature is in Degree's F regardless of the unit settings.

Did you script reset?

[danward79]

Did you script reset?

Yes, G5 has been set to Imperial for awhile.

[Promixis]

Yes, G5 has been set to Imperial for awhile.

Dan are you using metric or imperial?

If you look at the rfxcomtransmitters component, see the processdata method -> some prints in there may help find where the problem is. It should automatically handle the unit change...

[danward79]

Hi Mike,

It seems dispite my UnitSystem.cfg storing my setting from the settings menu of Metric.

print(gir.GetUnitSystems()) always returns imperial!...

Hence.


local ConvertSensorValue = {
['Type 1 Temperature (DS18B20)'] = function (v)
v = v * .125
if v > 200 then
v = - (256 - v)
end
return gir.ConvertUnits ('Metric',gir.GetUnitSystem (),'Temperature',v)
end,
['Type 2 Temperature (DS2438)'] = function (v)
v = v * .125
if v > 200 then
v = - (256 - v)
end
return gir.ConvertUnits ('Metric',gir.GetUnitSystem (),'Temperature',v)
end,
['Type 3 Temperature (DS2438)'] = function (v)
v = v * .125
if v > 200 then
v = - (256 - v)
end
return gir.ConvertUnits ('Metric',gir.GetUnitSystem (),'Temperature',v)
end,
['Humidity (HIH4000)'] = function (v,sv) return math.round (((((v*0.01)/ sv) - 0.16) / 0.0062),0) end,
['Barometer (MPXA4115)'] = function (v,sv) return gir.ConvertUnits ('Metric',gir.GetUnitSystem (),'BarometricPressure',((((v*0.01)/sv) + 0.095) / 0.0009)) end,
['Analog (DS2438)'] = function (v) return v end,
['Supply Voltage'] = function () return (v * .010) end,
['Power Monitor'] = function (v,sv) return v end,
['Unknown'] = function (v) return v end,
}

Always returns imperial. I can't see where the config file is chked at start up, so can't go any further at the moment any clues?

[Promixis]

try this fix...

[Promixis]

Dan,

as an FYI, the gir.UnitXXX functions are all no longer used. see the Global UnitSystem and the lua component UnitSystem for using units....

[danward79]

Thanks, that works

[Promixis]

Thanks, that works

phew... sorry -> for got to migrate that code :)

[danward79]

Mike,

I got my new boards now everything seems to be working.

I have also got a barometer, which is cool, but it has highlighted a couple of issues.

1. The output to the event needs rounding. My last reading was "1018.9265536723"

2. The supply voltage used for the sensor calculation.

Let me explain. I have a barometer plugged into one rfxcom transmitter.

The barometer has, it's own Supply Voltage, Temp and Pressure.
The Main transmitter also has Supply Voltage, Temp and Humidity.

So it is important that only the supply voltage from the barometer is used for the temp and pressure calc from the barometers sensors. As it is also the same for the main transmitters sensors.

The problem is that the supply voltage can be different as measured by both sensors even thou they are on the same supply.

Is this accounted for in the current set up of the pulgin?

[Promixis]

The code does use the supply voltage - check line 286 of the component. do not have a barometer sensor to test against.

[Rob H]

From my reading of it, it only uses the supply voltage of a DS2438 not the barometer. I could be wrong though.

[Promixis]

that is my take as well.. the code as is should work

[danward79]

The problems could occure if the supply voltage is different between the acessory and the main transmitter, as mine is.

This is likely for almost all cases, when you consider that there is a posibilty of 7 sensors, at 5m each. Not counting component tolerances.

[Promixis]

The problems could occure if the supply voltage is different between the acessory and the main transmitter, as mine is.

This is likely for almost all cases, when you consider that there is a posibilty of 7 sensors, at 5m each. Not counting component tolerances.

you will need to modify the code block that looks for the supply voltage.

what is the relationship of the barometer sensor relative to the supply voltage (ID)?

[b_weijenberg]

Mike,

For the calculation of the HR and hPa you need to have the value from the humidity or barometric sensor and the supply voltage on this sensor. The A/D voltage is the output voltage of those sensors.

Formula to calculate RH: RH = ((A/D voltage / supply voltage) - 0.16) / 0.0062

Formula to calculate hPa: hPa = ((A/D voltage / supply voltage) + 0.095) / 0.0009

The 1-Wire connection is a bus and all sensors have the same supply voltage so it is not necessary to have more supply sensors in the configuration, only 1 is enough.
But.... if sensors are connected using a cable that gives a loss in the supply voltage it would be better to have each sensor configured with the associated supply voltage. It is of course not advised to use such a configuration because the humidity and baro sensors work already on 4.7 volts while 5 volt is preferred.


Bert

[Promixis]

Bert, or anyone....

How does one decode the visonic code secure transmissions. I have a keyfob and we are getting output like...


VCS F8 EC 9F 64 E0 4F 0D 00 40 øìŸdàO..@
VCS 51 D9 3E C9 C0 9E 1A 00 80 QÙ>ÉÀž..€
VCS B9 E8 07 99 01 3C 34 01 00 ¹è.™.<4..
VCS B9 E8 07 99 01 3C 34 01 00 ¹è.™.<4..
VCS F6 CD 37 9E 01 3C 34 01 00 öÍ7ž.<4..
VCS FB 66 9B CF 00 9E 1A 00 80 ûf›Ï.ž..€
VCS 7B 66 9B CF 00 9E 1A 00 80 {f›Ï.ž..€
VCS FB 66 9B CF 00 9E 1A 00 80 ûf›Ï.ž..€
VCS FF 6C D3 79 E0 13 C3 40 00 ÿlÓyà.Ã@.
VCS FB 66 9B CF 00 9E 1A 00 80 ûf›Ï.ž..€
VCS FD B3 4D E7 80 4F 0D 00 40 ý³Mç€O..@
VCS FB 66 9B CF 00 9E 1A 00 80 ûf›Ï.ž..€
VCS F6 CD 37 9E 01 3C 34 01 00 öÍ7ž.<4..
VCS FD B3 4D E7 80 4F 0D 00 40 ý³Mç€O..@
VCS CF C9 2C F7 C0 9E 1A 00 80 ÏÉ,÷Àž..€

[b_weijenberg]

please use variable mode.
Check the keyfob with the RFreceiver program to check if data is correct received. In variable mode the Visonic keyfob command is translated to KR21 X10 security format and the decoding is available in the RFreceiver source.

Bert