Release 292-294

8 replies [Last post]
brett
Offline
Providence, United States
Joined: 9 Jan 2010

Few changes.

  • 291 - All xap processes now log to /var/log
  • 292 - Added ch.total endpoint to xap-currentcost  = ch.1+ch.2+ch.3
  • 293 - move ch.total endpoint to UID 05
  • 294 - Fixed a googlecal issue where-by it would output debug messages even if not in debug mode. Combined with a fixin 291 this had the potential to now crash your HAH
brett
Offline
Providence, United States
Joined: 9 Jan 2010
Release 295

A lurking bug that has been with us for quite some time in currentcost when I added ch.total it revealed a problem elsewhere in the code as far back as the 280 release and probably even earlier.  Thanks Aivo for your debug output.

I tracked it down.  It was introduced between 252 and 253 at r84 when I rewrote it for xaplib2 back in Sep 2010.

Pentala
Offline
Joined: 22 Oct 2011
Current Cost - Not working since upgrade to 295/3.4

Hi,

I upgraded this evening (/etc/init.d/upgrade) to 295 - however since the upgrade I'm not seeing any xap messages from Currentcost other than the heartbeat messages...? 

 

 

xap-hbeat
{
v=12
hop=1
uid=FF00DC00
class=xap-hbeat.alive
source=dbzoo.livebox.CurrentCost
interval=60
port=3643
pid=176
}

I've checked the USB connection - Microcom, and I am receiving XML messages on the configured port -

<msg><src>CC128-v1.29</src><dsb>00008</dsb><time>18:33:26</time><tmpr>21.0</tmpr><sensor>0</sensor><id>00077</id><type>1</type><ch1><watts>00906</watts></ch1></msg>
<msg><src>CC128-v1.29</src><dsb>00008</dsb><time>18:33:32</time><tmpr>20.8</tmpr><sensor>0</sensor><id>00077</id><type>1</type><ch1><watts>00903</watts></ch1></msg>
<msg><src>CC128-v1.29</src><dsb>00008</dsb><time>18:33:38</time><tmpr>20.8</tmpr><sensor>0</sensor><id>00077</id><type>1</type><ch1><watts>00904</watts></ch1></msg>
<msg><src>CC128-v1.29</src><dsb>00008</dsb><time>18:33:44</time><tmpr>20.9</tmpr><sensor>0</sensor><id>00077</id><type>1</type><ch1><watts>00891</watts></ch1></msg>

I've also tried configuring a second channel but still no XAP messages...?

[currentcost]
enable=1
usbserial=/dev/ttyUSB0
model=CC128
type1=A
desc1=Watts-Ch1
unit1=Watts
hysteresis1=10
Also done a full power cycle of the Livebox and the CurrentCost...still no joy :-(
Andy

 

 

g7pkf
Offline
United Kingdom
Joined: 11 Jan 2011
ditto

Current cost no work :(

derek
Offline
Glasgow, United Kingdom
Joined: 26 Oct 2009
Hard to test

Do recall that Brett has been making the recent CC code changes 'blind' (as he no longer has a CC unit). Once I'm back at base, I can stand up a test unit for him to access over our bridged network. I'm sure that it won't take long to get this sorted.

Derek.

brett
Offline
Providence, United States
Joined: 9 Jan 2010
Don't know why

Unfortunate the program is breaking in a part of the code I never touched when adding the cc.total endpoint which means the bug has been dormant and has only just surfaced now.  I'm going to have to debug this using Derek kit in his basement as I don't have a currentcost anymore.   If you roll back to the last beta the CC works although it has the same bug I just fixed!?  I will be at least 3-4 hours or more before I get a chance to look a this.

# /etc_ro_fs/update-dev hah-beta.dbzoo.com

Corrected a typo on the above command.

g7pkf
Offline
United Kingdom
Joined: 11 Jan 2011
No worries

Not life or death.

 

command above does not seem to work?

Pentala
Offline
Joined: 22 Oct 2011
I've downgraded as per the

I've downgraded as per the post above and the CurrentCost stats are back :-)

 

# cd /etc_ro_fs/
# ./update-dev hah-beta.dbzoo.com

Build: 283.2/3.4

 

Please let me know if you need any logs etc to help identify the problem.

Andy

brett
Offline
Providence, United States
Joined: 9 Jan 2010
Release 296

This will fix the CC woahs.  The funny thing is I didn't add any code except some debugging and now it works.  Perhaps what happened is that the change I made for 295 never got compiled in so when I released the bug was still there.

Anyway I've been told by Aivo that this works so here we go!

Brett

Hardware Info