UID wrong how do i correct?

5 replies [Last post]
g7pkf
Offline
United Kingdom
Joined: 11 Jan 2011

from XFX viwere under jeenode

xap-header
{
v=12
hop=1
uid=FF00D801
class=xAPBSC.info
source=dbzoo.livebox.jeenode:pond.temp
}
input.state
{
state=on
text=-24.6
}

from serial on XFX viewer

xap-header
{
v=12
hop=1
uid=FF00D500
class=Serial.Comms
source=dbzoo.livebox.Serial
}
Serial.Received
{
port=/dev/ttyUSB1
data=OK 2 1 0 10 3
}

so looks like an incorrect UID that i need to change somewhere, anyone any pointers?

brett
Offline
Providence, United States
Joined: 9 Jan 2010
I don't see what is wrong

I don't get it what you are trying to correct as nothing is wrong with either of those packets?   What UID are you trying to change and why?  - Brett

g7pkf
Offline
United Kingdom
Joined: 11 Jan 2011
Well i doubt the temp of pond is 24degrees

Ok so im not understanding correctly but why is the outside temp showing as 24.6? when in reality it is much much lower....winter here in UK

brett
Offline
Providence, United States
Joined: 9 Jan 2010
You want to be colder?

I see text=-24.6 this looks cold enough to me?   Can you not see the MINUS sign?


derek
Offline
Glasgow, United Kingdom
Joined: 26 Oct 2009
It's a mapping thing

The UID isn't the problem (and last I checked it wasn't -24C in the UK - though the West Coast of Scotland seems to have had 24" of rain the last few days!).

Reckon that the thing that needs a little attention is the mapping of the string that is incoming from the JeeNode that has the DS18B20 onboard to the value of the 'pond.temp' endpoint. 

This is done in the Lua script.

From the serial message "data=OK 2 1 0 10 3", we can see that the incoming data is valid & from Node Id 2. If I recall correctly, the '1' is the LDR value, the '0' means no PIR motion and the 10 is the DS18B20 value (though I'd have expected three digits?).

Best check the roomNode code & the Lua. It's almost there!

Derek.

brett
Offline
Providence, United States
Joined: 9 Jan 2010
The mapping is a little more complex

Hate to disappoint but the TEMP sensor is 10 bits of information is does not MAP to any BYTE value that you are seeing, the value of 10 decimal is meaningless unless you do a bitslice of the entire data stream.

Examine the source code to see how this stream of decimal data is carved up.

http://livebox-hah.googlecode.com/svn/trunk/userapps/hah/xap-plugboard/x...

The code for the bitslicer is in here - but I challege anybody to understand this without serious effort.

http://livebox-hah.googlecode.com/svn/trunk/userapps/hah/xap-plugboard/x...

If you examine the code you'll see why its just not that simple that you can say OH 10 is for the temperature.  What I can say is that I know this code is correct as I've been running it for about 4-5 months.  Although I don't rule out the possiblilty of a bug I find it unlikely.

If the xapflash GUI is not displaying the -VE sign then that is just a FONT SIZE issue and you'll need to tweak it down a little as its being cropped off.

Brett

Hardware Info