Problem with freezing CurrentCost Device and livebox RF usage
9 October, 2011 - 08:52
Hi!
Since there is a problem with AVR (RF) freezing only solveable with permanent rebooting the livebox running on the old bascom code,
I flashed the new code from brett an now I am on Build 287/3.4.
Since I am on the new AVR firmware, I have the following problem about every 12 hours (e.g. over night):
The CurrenCost device doesn't show any actual Watts on it's display any more, instead only "--------- W".
The livebox again does not execute RF-changes (via twitter, googlecal or direct) any more.
Just powering off an on the CurrentCost device again and/or cut the serial connection to the livebox doesn't work.
The only way to solve the problem is to reboot/toogle power off an on again on the livebox!
It seens to me as if the CurrentCost device cannot receive Watts-Info from its external device any more, even after cutting off from livebox and rebooting, so maybe the livebox RF disturbes the communication between them? Aditionally I have to say, that I have the external antenna from the shop connected to the livebox.
After livebox rebooting, everything is fine again!
Thanks for your help!
9 October, 2011 - 12:31
#2
RF and Currentcost
Couple of points.
If your current cost device is not receiving data this is not related to any HAH function. The xap-current cost daemon is a receiver of data only no control signal is sent back up the cable to the current cost display. You'll need to better position your head end to be near your clamp transmitter. Restarting the HAH and/or the xap-currentcost daemon if it has any affect at all can only be coincidence.
The RF unit. When moving from 2.x firmware to the 3.x firmware as the code is different the timing on the RF signal need to be adjusted. If you let us know what devices are you controlling we can make sure you are using the right RF HEX sequence. A failure receive is *not* the same as a failure to transmit (ie lockup). However the two are *very* hard to distinguish from each other. To date the v3.4 firmware has not experienced any lock up.
Brett
13 October, 2011 - 20:32
#4
RF timing codes for v3.x
These look like LIDL RF codes - which Gary posted some updates for. Mind you I'm not sure how he derived these if it was by trial and error or by using scope to figure out the exact timings and then looking at the output of the RF unit and aligning the pulse streams.
http://www.homeautomationhub.com/content/modified-lidl-urf-codes-new-ard...
Can you tell us what RF units you are controlling? Derek's the man to put up some new RF codes.
Brett
13 October, 2011 - 21:05
#5
Trial and error!
As Brett rightly guessed these codes were derived from trial and error. However, I have a current cost unit sat on top of my livebox and rf and current cost work fine with these codes. Very stable. (I dont use external ant though) One other thought. Do you use a USB hub and other USB devices? Garry
RF can be hard to setup. Having two antenna very close to each other will result in a local drop in signal. I keep my CurrentCost receiver as far away from the HAH RF ariel as I can.
However, this doesn't explain why a reboot of the HAH sorts things out. I'm running 287/3.4 and don't see this problem.
It would be interersting to know if a forced restart of xap-Currentcost solves this issue. This would be much cleaner than a full reboot. Do try this & let us know if it helps.
On the topic of reboot, you've done a great job on the Lua scripts - the more example scripts that can be published, the easier it is for other users.
Derek.