Gateway and Sensors are not connecting
-
Hi,
i found this project about a year ago and bought some sensors etc.
This week I got some time and motivation, so I started playing around.
So I loaded the "SerialGateway" Example from the mysensors library on my arduino UNO and the "DimmableLight" Example on a fake Nano (first on a fake Mega, but the Mega threw the error message "failed init radio" or something like that).My Problem:
I think they see each other, but the sensor node isn't registered by the gateway.
I use MYSController for testing. The Debug tab shows the following:05.10.2015 19:21:59 STARTUP Initialize message logging 05.10.2015 19:21:59 STARTUP MYSController 0.1.2.282 05.10.2015 19:21:59 STARTUP FPC 2.6.4 / Lazarus 1.4.2 05.10.2015 19:21:59 STARTUP still under development :) tekka 2015 05.10.2015 19:21:59 STARTUP Load INI file... 05.10.2015 19:21:59 STARTUP INI version 0.1.2.282 05.10.2015 19:21:59 INFO *** Logging START *** 05.10.2015 19:21:59 VERSION MYSController 0.1.2.282 05.10.2015 19:21:59 STARTUP INI file loaded 05.10.2015 19:21:59 STARTUP Loading FW repository... 05.10.2015 19:21:59 REPO FW "Blink" loaded. t=10, v=1, blocks=72, crc=0xD098 05.10.2015 19:21:59 REPO FW "TimeReporter" loaded. t=20, v=1, blocks=840, crc=0x4AC5 05.10.2015 19:21:59 REPO FW "Sensebender Micro" loaded. t=100, v=1, blocks=1344, crc=0x3482 05.10.2015 19:21:59 REPO FW "Sensebender Blink" loaded. t=110, v=1, blocks=768, crc=0x1314 05.10.2015 19:21:59 REPO FW repository loaded. Items=4 05.10.2015 19:21:59 STARTUP Initialize message types 05.10.2015 19:21:59 NODE New node discovered, node id=0 05.10.2015 19:21:59 NODE New node discovered, node id=255 05.10.2015 19:22:08 UPDATE 4295098650 05.10.2015 19:22:16 INFO Flushing FIFO 05.10.2015 19:22:16 INFO Connected to COM3 05.10.2015 19:22:18 CHILD New child discovered, node id=0, child id=0 05.10.2015 19:22:18 RX 0;0;3;0;9;gateway started, id=0, parent=0, distance=0 05.10.2015 19:22:18 RX 0;0;3;0;14;Gateway startup complete. # HERE IS THE SENSOR NODE POWERED ON 05.10.2015 19:22:29 RX 0;0;3;0;9;read: 255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0: 05.10.2015 19:22:30 RX 0;0;3;0;9;send: 0-0-255-255 s=255,c=3,t=8,pt=1,l=1,sg=0,st=bc:0 05.10.2015 19:22:31 RX 0;0;3;0;9;read: 255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0: 05.10.2015 19:22:32 RX 0;0;3;0;9;send: 0-0-255-255 s=255,c=3,t=8,pt=1,l=1,sg=0,st=bc:0 05.10.2015 19:22:33 RX 0;0;3;0;9;read: 255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0: 05.10.2015 19:22:34 RX 0;0;3;0;9;send: 0-0-255-255 s=255,c=3,t=8,pt=1,l=1,sg=0,st=bc:0 05.10.2015 19:22:35 RX 0;0;3;0;9;read: 255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0: 05.10.2015 19:22:36 RX 0;0;3;0;9;send: 0-0-255-255 s=255,c=3,t=8,pt=1,l=1,sg=0,st=bc:0 05.10.2015 19:22:37 RX 0;0;3;0;9;read: 255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0: 05.10.2015 19:22:38 RX 0;0;3;0;9;send: 0-0-255-255 s=255,c=3,t=8,pt=1,l=1,sg=0,st=bc:0
And the sensor node Serial output prints the following:
find parent send: 255-255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc: sensor started, id=255, parent=255, distance=255 find parent send: 255-255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc: find parent send: 255-255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc: find parent send: 255-255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc: Light state: OFF find parent send: 255-255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc: Node ready to receive messages...
I also tried this with the SerialGateway and Dimmer example from the mysensors website, but same failure.
I downloaded the library a few days ago so it should be everything the current version. Arduino IDE Version is: 1.6.5
I already tried different radios (also one with external antenna), all chips are marked with the + version, but RF24 library GettingStarted example doesn't show the +. I haven't added capacitors to the radios, but I think this problem is software sided because it looks to me like they find each other.Any help appreciated
Greetings from Germany,
JohannesPS: this project looks very cool and would be great if I get it to work.
-
Gateway answers the FIND_PARENT request from node... But node does not seem to get the response.
Could very well be a powering issue. Caps usually resolves this type of behaviour.
-
Ok thank you very much!
You were right. Today my Caps came and now it's working perfect!