Driver for RFXmitter by RFXCOM released

[Solosid]

Originally Posted by Tieske8

thx for the feedback, does this mean you're up and running now?

Hi Tieske,

No girder is not controlling the HomeEasy stuff

Time Date Source Details Payloads
12:19:31:066 7/26/2010 RFXmitter Driver version 0.2. Initialization command failed: Data received (12 bytes): 22 03 DB 31 80 00 22 03 DB 31 80 00.Codes returned (20 00): INCOMPLETERESPONSETIMEOUT


not sure what it means?

I know 03DB3180 is the code for the light when using RFxmitter program

I dont know how to enter this in the girder plugin box

I have tried various combinations but still no sucess...

Cheers

Mark

[Solosid]

Hi All,

i have disabled the G5 plugin so i could try and grab some codes though the programs supplied with the RFXCom unit

if i send a text to the SMS unit the code comes out as

228D1E6E1800 light on
228D1E6E0800 light off

if I use the HE300w remote the code comes out as

2203DB319000 light on
2203DB318000 light off

I presuming the 228 and 220 part would be the sending unit identifier

then the next 6 digits is the address code for the unit

and then the 00... not sure what thats for

Questions,

Why does it have 2 different address codes?

Does it matter which one I try and use?



Copied from RFXmitter log

Init cmd to transmitter => F037F037
2203DB319000
2203DB319000
48EA00B9000000001486 (light on with remote)


2203DB318000 (light off with remote)

228D1E6E1800
228D1E6E1800
228D1E6E1800
228D1E6E1800
228D1E6E1800
228D1E6E1800228D1E6E1800
228D1E6E1800
228D1E6E1800
228D1E6E1800228D1E6E1800
228D1E6E1800
228D1E6E1800
228D1E6E1800
228D1E6E1800
228D1E6E1800228D1E6E1800
228D1E6E1800228D1E6E1800
228D1E6E1800
228D1E6E1800
228D1E6E1800
228D1E6E1800 (light on with text)


228D1E6E0800228D1E6E0800228D1E6E0800228D1E6E0800
228D1E6E0800
228D1E6E0800228D1E6E0800228D1E6E0800228D1E6E0800
228D1E6E0800
228D1E6E0800
228D1E6E0800
228D1E6E0800228D1E6E0800
228D1E6E0800228D1E6E0800228D1E6E0800
228D1E6E0800
228D1E6E0800
228D1E6E0800228D1E6E0800228D1E6E0800228D1E6E0800
228D1E6E0800228D1E6E0800
228D1E6E0800
228D1E6E0800228D1E6E0800228D1E6E0800 (light off with text)




cheers

Mark

[Tieske8]

Originally Posted by Solosid

I presuming the 228 and 220 part would be the sending unit identifier

then the next 6 digits is the address code for the unit

and then the 00... not sure what thats for

Questions,

Why does it have 2 different address codes?

Does it matter which one I try and use?

You can't presume that.

Have you checked the comment by Bert;

Originally Posted by b_weijenberg

Mark,

For sure, you have COM11 assigned which is the receiver COM port. Data displayed is from the OWL CM113.
You have to configure COM12 for the RFXmitter in Girder.

Bert

Because, as Bert states, the byte sequence in your logs (which RFXmitter tries to interpret as a response on the initialisation commands) look like an OWL command. Thats an inbound signal, hence the byte code is probably coming in from the RECEIVER and not from the RFXMITTER. The only thing the RFXMITTER sends back is an acknowledgement code. So it seems RFXmitter driver is talking to the RECEIVER.

Questions:
1) in settings, plugins header, plugins tab; is 'Generic Serial' enabled?
2) in settings, plugins header, serial tab; which COM ports have a device discription shown?
3) in COM port redirector; what COM port does the receiver connect to?
4) in COM port redirector; what COM port does the RFXmitter connect to?

we'll get there

[Solosid]

Originally Posted by Tieske8

Y
Questions:
1) in settings, plugins header, plugins tab; is 'Generic Serial' enabled?

yes

2) in settings, plugins header, serial tab; which COM ports have a device discription shown?

was 11 now 12

3) in COM port redirector; what COM port does the receiver connect to?

not sure how to tell the difference

4) in COM port redirector; what COM port does the RFXmitter connect to?

see above

we'll get there

I know we will

[Tieske8]

Originally Posted by Solosid

2) in settings, plugins header, serial tab; which COM ports have a device discription shown?

was 11 now 12

Whats the result of changing this? any changes to what you see in the log? (make sure to reset the lua scripting engine in Girder, just-in-case, after changing parameters)

By the way; when you succesfully used the RFXmitter program, what COM port did you connect to? Girder should be configured to use the same port.

Originally Posted by Solosid

3) in COM port redirector; what COM port does the receiver connect to?

not sure how to tell the difference

@bert; isn't this configured through the network ports being used? a different network port for each virtual COM port? can you email me the DeviceInstaller? so I can have a look at its configuration options?

[Solosid]

Hi,

Im still getting this in the Girder log

Time Date Source Details Payloads
23:09:11:463 7/28/2010 RFXmitter Driver version 0.2. Initialization command failed: Codes returned (40 00): NORESPONSETIMEOUT


Cheers
Mark

[Tieske8]

Mark,

I've been thinking this over and it gets harder and harder to pinpoint a cause of this error.

From what I saw in the screenshot you posted (and removed again), you have the RFXmitter program connected to COM12. And it was working, eg. you were able to turn lights on/off.

One thing not yet covered is other Girder devices. So can you run some tests;
1) remove the RFXMitter from Girder (in the serial tab, remove it) and close Girder
2) start RFXmitter and make sure you can switch a light on/off
3) close rfxmitter (so it releases COM12), start Girder but don't do anything. Now start RFXmitter again and see if you can again switch a light on/off on COM12. With Girder in the background, just to make sure that some other Girder component doesn't grab COM12.
Its important to run the sequence exactly in the order described.

[Solosid]

Hi Tieske,

PM sent for reason for removal!

I am having an amazing amount of difficlty understanding this RF stuff

with IR you copy the code and emulate it with whatever divice you have.

1. Is RF not like that?

2. What am I missing?, it cant be this difficult surely.


Mark

[b_weijenberg]

Mark,

The order is normally that you configure a HE unit in the software with a (random selected) device code. You push the learn button on the HE device and you send an ON command. This HE unit will be paired to the device configured in the software.

Bert

[Solosid]

Hi Bert,

That doesn't seem to work....

this is the exact sequence I do

1. open RFXmitter
2. connect to Com12 for port 10002
3. mode select, dont use handshake with receiver


this is the code it logs

Init cmd to transmitter => F037F037
ACK=> 37

4. go to the AC page
5. enter any config (not sure what to do with the last two digits, chose 80)
6. press learn on the 'test socket'
7.press 'on' in the RFXmitter program

is that the right sequence...because nothing happens...

also does the girder plugin 'emulate' a rf signal by using the 'bits'?

cheers

Mark