Archived Forum

Both emonHub and emonCMS rely on a valid timestamp and it looks like the time on your Pi has reset to 1970. This is most probably caused by a lack of internet connection when first booted up, unfortunately the Pi has no real time clock and the read-only mods made on the read-only SD image increase the Pi's dependency on a working internet connection at boot time.

Sometimes this resolves itself sometime after another reboot but it is probably best to perform the update manually. If you can connect it to a working internet connection you can restart the daemon that corrects the time using

sudo service ntp restart

OR if you cannot get a working internet connection set the time manually to the current UTC (edit to current time) using

sudo date -s "Wed Oct  8 10:33:21 UTC 2014"

Either way back-up the current time to file using

sudo fake-hwclock save

This should get the time corrected, but if you reboot and there is no internet connection at boot time it will probably reoccur, so if you are using this without a permanent internet connection you should consider the changes being discussed on the Read-only time issues thread. Step 1 is the more important step for this issue.

Once the system time is correct everything else should work Ok.

Paul

Thanks for that

now i am seeing a timestamp on my inputs, however im not getting any reports from my CT inputs...

here is an output from my logs, i have increased the log level :

pi@raspberrypi:~$ tail /var/log/emonhub/emonhub.log
2014-10-09 13:11:35,983 DEBUG 8 Append to 'emonCMS' buffer => time: 1412860295.92, data: [10, 0, 0, 0, 0, 25433, 0], ref: 8
2014-10-09 13:11:36,089 INFO Sending: http://localhost/emoncms/input/bulk.json?apikey=E-M-O-N-C-M-S-A-P-I-K-E-Y&data=[[1412860295.92,10,0,0,0,0,25433,0]]&sentat=1412860296
2014-10-09 13:11:37,251 DEBUG Receipt acknowledged with 'ok' from http://localhost/emoncms
2014-10-09 13:11:46,763 DEBUG 9 NEW FRAME : 1412860306.76  10 0 0 0 0 0 0 0 0 103 99 0 0
2014-10-09 13:11:46,768 DEBUG 9 Timestamp : 1412860306.76
2014-10-09 13:11:46,771 DEBUG 9      Node : 10
2014-10-09 13:11:46,773 DEBUG 9    Values : [0, 0, 0, 0, 25447, 0]
2014-10-09 13:11:46,803 DEBUG 9 Append to 'emonCMS' buffer => time: 1412860306.76, data: [10, 0, 0, 0, 0, 25447, 0], ref: 9
2014-10-09 13:11:46,906 INFO Sending: http://localhost/emoncms/input/bulk.json?apikey=E-M-O-N-C-M-S-A-P-I-K-E-Y&data=[[1412860306.76,10,0,0,0,0,25447,0]]&sentat=1412860306
2014-10-09 13:11:47,385 DEBUG Receipt acknowledged with 'ok' from http://localhost/emoncms

the mains power voltage seems to work fine, just the CT come back with no readings.

please advise

thanks

Do you have a programmer? If so, you could connect that and check that the serial port has the power values (I'm guessing you have the default sketch and the first four values are the powers). You'd also see whether it thought the CTs were connected. Obvious question, are the plugs fully home? The sockets can be very stiff and if you can see any metal of the barrel, they're not. Are they shop CTs, or did they come from elsewhere. If from elsewhere, are the plugs wired correctly?

HI

dont have a programmer, i bought the fully assebled emonTXv3, im sure they tested it before dispatch. and they are connected properly it goes all the way into the socket. and yes the 4 x CT,emonTX v3, rf module for pi, are from the shop, bought everything from openenergymonitor shop. im using AC-AC adapter.

i have tested 2 ports(CT1 and CT3) and they are giving me the same results of 0

is the power cable running through the CT suppose to be fitted tightly between the clamp ?

not sure what else to try, have not found anyone with similar scenarios.

regards

How have you fitted the CT to the cable, and to which cable? It must be a single core cable. If it is a 2-core or 3-core cable containing both line and neutral, you will of course not read any current at all. It makes no detectable difference whether the cable passes exactly through the middle of the CT, or to one side, or at an angle, but the two halves of the core must be securely clipped together.

It should look like this:

I didn't answer your duplicate post on the other thread (different discussion) and it looks like Robert has it covered here :-)

As you've worked out the problem has to be with the circuits being tested or the ct connections as the voltage (and the zero power values) can be seen which tells us the payload is being transmitted and received Ok.

Incredibly, I couldn't find a picture of a CT on a cable anywhere on this site. I've added one to the post above.