Driver for RFXmitter by RFXCOM released

[Tieske8]

Hi All,

Today I released the new driver I wrote for the RFXmitter by RFXCOM. Any questions or bugs can be dropped here. Its still very rough, I only own some X10 and HomeEasy stuff, hence thats the only part that got some decent testing.

Current version is 0.3

WHAT'S INCLUDED


================

• initialization, with or without handshake
• device version reporting
• support for COM port connections only (see link below, check the redirector driver availability for your platform!!)
• support for the following protocols
  
• Flamingo
• HomeEasy HE105 heater
• ATI Remote Wonder II (remote control emulation)
• ATI Remote Wonder Plus (remote control emulation)
• Medion (remote control emulation)
• PCremote (remote control emulation)
• Robocam/Ninja
• ARC protocol (wheel based devices by, amongst others; KlikAanKlikUit, NEXA, Proove, Domia Lite, ByeByeStandBy, ELRO AB600, Intertechno, Duwi)
• Waveman
• Harrison curtains
• X10 Lighting (On, Off, All On, All Off, Dim, Bright)
• HomeEasy (UK and EU) with automatic code (and compatible formats; KlikAanKlikUit, NEXA, etc.)

[ATWindsor]

Very nice, does it also work with the NEXA auto-learn products?

[b_weijenberg]

Yes, it wil also work for NEXA and Chacon auto-learn modules.

[ATWindsor]

Yes, it wil also work for NEXA and Chacon auto-learn modules.

Thanks a lot for the feedback, will be ordering the LAN-version today

[ATWindsor]

Hello, I have gotten the LAN-version in the mail today, but I am struggling a bit, I followed the instructions in the read-me file, so the plugin is installed. I have the Lan version of the rfxcom, with a reciever and transmitter. I know the IP of the device, and I have in girder settings chosen COMport 5 for the rfxcom-device. However, I am a bit stuck now.

First of all, do i need the Lantronix Comportdirector to run? It does not support my OS (wich is vista 64 bit). Hopefully, the answer is no. In girder, what do i do now? If i have a switch that the rfxcom-device can communicate with, how do i get the signal into girder, and trigger an event when the switch is pressed? In the action-window, i can create a send event action, but there are no available choices in the pulldown-menu. Sorry if theese are very stupid questions, but i am totally new to to the device, and I am not very advanced in using girder5 either.

[b_weijenberg]

Girder needs a COM port redirector as the plugins do not have a TCP/IP interface.

[Tieske8]

First of all, do i need the Lantronix Comportdirector to run? It does not support my OS (wich is vista 64 bit). Hopefully, the answer is no.

unfortunately the answer is yes, the Girder driver is a COM-port based device

In the action-window, i can create a send event action, but there are no available choices in the pulldown-menu.

Can you check the variable window (you can make it visible through the view menu). First click the refresh button and then check for a table called "RFXmitter", within that table there should be a "Protocols" table. Are these available?
If not then probably the driver was not loaded.
The driver actually consists of 2 parts; the serial driver (which builds the "Protocols" table), and a treescript action (which uses the "Protocols" table)

Sorry if theese are very stupid questions, but i am totally new to to the device, and I am not very advanced in using girder5 either.

No problem, glad someone is using the device and can help pinpoint the bugs.

The other possibility is a rewrite of the driver to use a transport device rather than a plain serial device. That should permit direct access to the TCP/IP connection or a serial connection.

I have been investigating that option, but there are three issues;
1) I only have a USB version myself, so have no test capability
2) documentation is pretty tough. I went through some examples provided, but there seems to be no clear overview of the object model used.
3) time.... to code it using the transport model

If I find some spare time in the coming weeks, I'll have another look at it.

[Tieske8]

Relased an updated version today. Version 0.2 contains the following fixes;

• Fixed HomeEasy EU, UK-preset & EU-preset, bug
• Fixed group commands HomeEasy EU & UK
• Added experimental protocol for testing (only for specifically prepared devices!)
• Improved verbose information on status and versions
• Fixed bug SendRFXCommand function

The latest version can be downloaded here (please note: download location changed!)

[Solosid]

Hi Tieske,

I have printed out the RFXmitter driver.lua

And if you look at line 66 it seems some code
Has been commented out?

-- ReceiveTerminator = serial.hexobyte ("33"),


Haven't had chance to look on the pc yet... Bedtime reading...


Cheers

Mark

[Tieske8]

Hi Tieske,

I have printed out the RFXmitter driver.lua

And if you look at line 66 it seems some code
Has been commented out?

-- ReceiveTerminator = serial.hexobyte ("33"),


Haven't had chance to look on the pc yet... Bedtime reading...


Cheers

Mark

Its in the initialization part, the full 2 code lines are;

    -- ReceiveTerminator = serial.hextobyte ("33"),    -- Use the handshake signals XRTS-XCTS (receiver connected)
    ReceiveTerminator = serial.hextobyte ("37"),    -- Don't use the handshake signals XRTS-XCTS (no receiver connected)

All it does is setting the default NOT using a handshake (2nd line), if you would switch the comment to the other line, all you do is changing the default.