Hard to grab time and value sent from controller

[sundberg84]

Hi.

No i recieve the time, check if its a new day and then sleep the node.
This is done every sleep cycle (20min),. (Im aware about the failure margin here).

I do not sleep the sensor until i got the new time so that should not be a problem.

[sundberg84]

Looking at MysController i get this when i get into the bad loop:

2015-10-16 16:27:20	INFO	Reply time request
2015-10-16 16:27:20	TX	7;255;3;0;1;1445012841
2015-10-16 16:27:20	RX	7;255;3;0;1;
2015-10-16 16:27:24	INFO	Reply time request
2015-10-16 16:27:24	TX	7;255;3;0;1;1445012844
2015-10-16 16:27:24	RX	7;255;3;0;1;
2015-10-16 16:27:28	INFO	Reply time request
2015-10-16 16:27:28	TX	7;255;3;0;1;1445012848
2015-10-16 16:27:28	RX	7;255;3;0;1;
2015-10-16 16:27:28	RX	5;0;1;0;4;1020
2015-10-16 16:27:31	INFO	Reply time request
2015-10-16 16:27:31	TX	7;255;3;0;1;1445012852
2015-10-16 16:27:31	RX	7;255;3;0;1;
2015-10-16 16:27:35	INFO	Reply time request
2015-10-16 16:27:35	TX	7;255;3;0;1;1445012855
2015-10-16 16:27:35	RX	7;255;3;0;1;
2015-10-16 16:27:38	INFO	Reply time request
2015-10-16 16:27:38	TX	7;255;3;0;1;1445012859
2015-10-16 16:27:38	RX	7;255;3;0;1;

@hek
Its like its working one way (Sensor -> Repteter -> Controller) but not the other way around. Is it not using the repeater and thats why the request with time is not getting back?

[sundberg84]

Or its a bad NRF batch i got... AGAIN :(
Notised its a new batch im on... have to try some other nrf in that patch. Works one way though...

[hek]

Also make sure you're running the latest in master branch on gw/repeater. There was a bug there earlier affecting outgoing messages through repeaters.

[sundberg84]

I run 1.4 gw and updated repeaters after bug was reporter (bad routing causing à loop). Its à bit job to update gw to 1.5. Do you think it can make any difference @hek ?

[hek]

I doubt it would change anything. It's the intermittent failure behaviour that is weird.

[sundberg84]

I have ordered new nrf radios. Let's hope the makey the difference.

[sundberg84]

New radio, pro mini and still the same problems :(
I cant get it.

Looking at the gw leds the recieve led blinks when the node sends out the request. 1 second later the controller and gw responds accoring to MYSController and i see the transmit and error led blink.

i have the node right beside the gw now and no repeaters.
Any clues, anyone???

[hek]

And how does the node log look like?

Did you upgrade to 1.5?

[sundberg84]

No i did not upgrade the gw since i had so much problems with the connections...

Nod serial as before:
(From startup)

send: 7-7-0-0 s=255,c=0,t=17,pt=0,l=3,sg=0,st=ok:1.5
send: 7-7-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,st=ok:0
sensor started, id=7, parent=0, distance=1
send: 7-7-0-0 s=255,c=3,t=11,pt=0,l=10,sg=0,st=ok:Rain Gauge
send: 7-7-0-0 s=255,c=3,t=12,pt=0,l=3,sg=0,st=ok:1.7
send: 7-7-0-0 s=1,c=0,t=10,pt=0,l=0,sg=0,st=ok:
Startup completed
send: 7-7-0-0 s=1,c=2,t=24,pt=0,l=0,sg=0,st=ok:
Request pulsecount
send: 7-7-0-0 s=1,c=2,t=24,pt=0,l=0,sg=0,st=ok:
Request pulsecount
send: 7-7-0-0 s=1,c=2,t=24,pt=0,l=0,sg=0,st=ok:
Request pulsecount
read: 0-0-7 s=1,c=2,t=24,pt=0,l=2,sg=0:52
Received last pulse count from gw: 52
send: 7-7-0-0 s=255,c=3,t=1,pt=0,l=0,sg=0,st=ok:
Getting Time
send: 7-7-0-0 s=255,c=3,t=1,pt=0,l=0,sg=0,st=ok:
Getting Time
read: 0-0-7 s=255,c=3,t=1,pt=0,l=10,sg=0:1446829805
Time received: 17

[hek]

DI you have a similar serial log for the gateway? Think you should try to upgrade to be aligned with 1.5. Don't remember what problems you had earlier...