Initiate new KaKu device using RFXCom command tool
Moderator: RDNZL
Initiate new KaKu device using RFXCom command tool
Dear Forum
Using a RFXCom LAN transceiver I want to initiate a new KaKu AC1000 device.
I've used Domotiga, tools, RFXCom commander, transmitter in the AC/HE UK tab. The address is set for D1, AC Code 0000 (what is this used for?).
The KaKu unit is flashing (in program mode) and I click ON in RFXCOm commnaer, but no result (the KaKu unit keeps flashing.
Domotiga debug shows after clicking ON:
2011/12/21 16:34:55 [RFXComTX] 215000001000
2011/12/21 16:34:56 [RFXComTX] ACK=>33
I can send X10 commands to existing X10 devices, they work fine, thus ruling out LAN issues to RFXCom.
Am I on the right track here or overlooking something causing this initialisation of a new KaKu not to work?
Thanks!
OWK
Using a RFXCom LAN transceiver I want to initiate a new KaKu AC1000 device.
I've used Domotiga, tools, RFXCom commander, transmitter in the AC/HE UK tab. The address is set for D1, AC Code 0000 (what is this used for?).
The KaKu unit is flashing (in program mode) and I click ON in RFXCOm commnaer, but no result (the KaKu unit keeps flashing.
Domotiga debug shows after clicking ON:
2011/12/21 16:34:55 [RFXComTX] 215000001000
2011/12/21 16:34:56 [RFXComTX] ACK=>33
I can send X10 commands to existing X10 devices, they work fine, thus ruling out LAN issues to RFXCom.
Am I on the right track here or overlooking something causing this initialisation of a new KaKu not to work?
Thanks!
OWK
Domotiga
Cubietruck, Ubuntu server 1.0.2
RFXcom LAN, home brew ground plane antenna
KaKu
Cubietruck, Ubuntu server 1.0.2
RFXcom LAN, home brew ground plane antenna
KaKu
- b_weijenberg
- Forum Moderator
- Posts: 1746
- Joined: Sun May 14, 2006 4:32 pm
- Location: Netherlands
Re: Initiate new KaKu device using RFXCom command tool
For KAKU you must not enable the HE EU checkbox.
Try this: reset the KAKU unit to erase all programmed remotes.
Try this: reset the KAKU unit to erase all programmed remotes.
Re: Initiate new KaKu device using RFXCom command tool
Thanks for the reply Bert,
Can you be more specific where the HE EU check box is located in Domotiga
I will reset the device, but it was brand new from the box.
Olaf
Can you be more specific where the HE EU check box is located in Domotiga
I will reset the device, but it was brand new from the box.
Olaf
Domotiga
Cubietruck, Ubuntu server 1.0.2
RFXcom LAN, home brew ground plane antenna
KaKu
Cubietruck, Ubuntu server 1.0.2
RFXcom LAN, home brew ground plane antenna
KaKu
- b_weijenberg
- Forum Moderator
- Posts: 1746
- Joined: Sun May 14, 2006 4:32 pm
- Location: Netherlands
Re: Initiate new KaKu device using RFXCom command tool
the checkbox is in the RFXmitter program, not in DomotiGa (I suppose)
Reset anyway.
Reset anyway.
Re: Initiate new KaKu device using RFXCom command tool
Did the reset, no result
I have LAN transceiver, should I use RFXMitter software and not RFTransmitter as I did?
With RFTransmitter: in the AC tab there is no HE EU checkbox,
In RFXMitter there is a HE EU checkbox, but I run into the same problem: how to set the correct address (D1 for example) into the 4 combo boxes available that have values up to FF.
I have LAN transceiver, should I use RFXMitter software and not RFTransmitter as I did?
With RFTransmitter: in the AC tab there is no HE EU checkbox,
In RFXMitter there is a HE EU checkbox, but I run into the same problem: how to set the correct address (D1 for example) into the 4 combo boxes available that have values up to FF.
Domotiga
Cubietruck, Ubuntu server 1.0.2
RFXcom LAN, home brew ground plane antenna
KaKu
Cubietruck, Ubuntu server 1.0.2
RFXcom LAN, home brew ground plane antenna
KaKu
- RDNZL
- Forum Moderator
- Posts: 1008
- Joined: Sun Sep 24, 2006 1:45 pm
- Location: Dordrecht, The Netherlands
- Contact:
Re: Initiate new KaKu device using RFXCom command tool
Wait a little bit, i have almost changed ac/heeu addressing so it uses the same values as rfxcom software.
So no x10 alike adresses anymore.
This format is also used by rfxcom xpl interface.
Also coding of packet is done correctly now.
So no x10 alike adresses anymore.
This format is also used by rfxcom xpl interface.
Also coding of packet is done correctly now.
Regards, Ron.
Re: Initiate new KaKu device using RFXCom command tool
Thanks for the quick response guys!
I'll wait for the new release.
Regards
Olaf
I'll wait for the new release.
Regards
Olaf
Domotiga
Cubietruck, Ubuntu server 1.0.2
RFXcom LAN, home brew ground plane antenna
KaKu
Cubietruck, Ubuntu server 1.0.2
RFXcom LAN, home brew ground plane antenna
KaKu
- RDNZL
- Forum Moderator
- Posts: 1008
- Joined: Sun Sep 24, 2006 1:45 pm
- Location: Dordrecht, The Netherlands
- Contact:
Re: Initiate new KaKu device using RFXCom command tool
Can you try version 0.1.202?
See example address for new address format.
There is now also an HEEU checkbox in RFXCom Commander.
See example address for new address format.
There is now also an HEEU checkbox in RFXCom Commander.
Regards, Ron.
Re: Initiate new KaKu device using RFXCom command tool
Great job again Ron, got it working
I initialised the KaKu device uing the RFXCom commander in Domotiga.
In the example address in device set-up the unit part is 2 digits. Maybe it is an idea to make in the RFXCom Commander the unit address 2 digit too (so: 01 and not 1). It got me confused
Thanks again for your great work!
Regards
Olaf
I initialised the KaKu device uing the RFXCom commander in Domotiga.
In the example address in device set-up the unit part is 2 digits. Maybe it is an idea to make in the RFXCom Commander the unit address 2 digit too (so: 01 and not 1). It got me confused

Thanks again for your great work!
Regards
Olaf
Domotiga
Cubietruck, Ubuntu server 1.0.2
RFXcom LAN, home brew ground plane antenna
KaKu
Cubietruck, Ubuntu server 1.0.2
RFXcom LAN, home brew ground plane antenna
KaKu
- RDNZL
- Forum Moderator
- Posts: 1008
- Joined: Sun Sep 24, 2006 1:45 pm
- Location: Dordrecht, The Netherlands
- Contact:
Re: Initiate new KaKu device using RFXCom command tool
Maybe thats a bug will check it. I think it should be just 1 not 01 everywhere.
Regards, Ron.