Hi, thanks to Paul my emonGLCD have correct time.
But don't send temperature to emonbase. I look at every line of sketch but i don't be able to send temperature.
I use the original sketch without modification for emonGLCD but no temp.
Thanks for help.
Yuki
Re: A new problem with emonGLCD
Which sketch is the "original sketch"?
Does the emonGLCD not send the temperature, or does the emonBase not receive the temperature?
Does the emonGLCD receive anything from your emonTx?
Re: A new problem with emonGLCD
Ok. Sorry.
1) The sketch is SolarPV
2) i don't know but emonBase receive from emonTX
3) emonGLCD receive from emonTX and receive time from emonBase
Thanks.
Re: A new problem with emonGLCD
The part of the sketch that sends the temperature is right at the end, starting at line 258.
Have you got the emonGLCD node defined in emonhub.conf to receive the temperature measurement?
Re: A new problem with emonGLCD
emonGLCD sketch solar PV send temp
emonglcd.temperature = (int) (temp * 100); // set emonglcd payload
rf12_sendNow(0, &emonglcd, sizeof emonglcd); //send temperature data via RFM12B using new rf12_sendNow wrapper -glynhudson
rf12_sendWait(2);
}
emonGLCD sketch solarPV node
//--------------------------------------------------------------------------------------------
// RFM12B Settings
//--------------------------------------------------------------------------------------------
#define MYNODE 20 // Should be unique on network, node ID 30 reserved for base station
#define RF_freq RF12_868MHZ // frequency - match to same frequency as RFM12B module (change to 868Mhz or 915Mhz if appropriate)
#define group 210 // network group, must be same as emonTx and emonBase
emonhub
[[[runtimesettings]]]
pubchannels = ToEmonCMS,
subchannels = ToRFM12,
interval = 300
# datacode = B #(default:h)
# scale = 100 #(default:1)
group = 210 #(default:210)
frequency = 868 #(default:433)
baseid = 20 #(emonPi default:5)
quiet = false #(default:true)
calibration = 230V #(UK/EU: 230V, US: 110V)
sendtimeinterval = 60
# interval = 300 #(default:0)
# nodeoffset = 32 #(default:0)
is right?
Yuki
Re: A new problem with emonGLCD
You need to ask pb66, do you not have a section that might look like:
This node number(20) conflicts with the default Node number for the second emonTH, therefore you must either comment that out, or change this and the node number of your GLCD (to 23?)
Re: A new problem with emonGLCD
Indeed since every node must have a unique nodeid on any JeeLib based network,
As for defining the emonGLCD in the nodes section of emonhub.conf, I don't actually recall this ever coming up about the emonGLCD on the "emon-pi" variant emonHub and it isn't an issue for original emonhub since it does not force the user to fully define every node, so providing the nodes have unique node id's it will just work,
If the emonGLCD is transmitting as node 20 and node 20 is defined as an emonTH in the nodes section the packets will be discarded as they don't fit the definition. The easy way to over come this (if not using an emonTH on node 20) would be as Robert says, to delete or comment out the emonTH node20 and add the emonGLCD node20 as per his example, although (personally) I would be inclined to avoid using spaces in the name to reduce the chance of future surprises, use "int_temp" or "glcdTemp" or something similar,
Paul
[Edited the snip above to incorporate your suggestion - RW]
Re: A new problem with emonGLCD
Sorry for the delay but my computer was dead!!!!
Thanks to Robert and to Paul.
I comment out the emonTH node20 and create a new emonGLCD node20 and it work.
Thanks again guys.
Yuki