Node dont connect to RaspBerry gateway
-
Hi.
Need som help here to. I have a Rpi gateway up and running without own sensors. output in Debug mode looks like this.
pi@RPI:~/MySensors $ sudo mysgw -d
mysgw: Starting gateway...
mysgw: Protocol version - 2.2.0-beta
mysgw: MCO:BGN:INIT GW,CP=RNNG--Q,VER=2.2.0-beta
mysgw: TSF:LRT:OK
mysgw: TSM:INIT
mysgw: TSF:WUR:MS=0
mysgw: TSM:INIT:TSP OK
mysgw: TSM:INIT:GW MODE
mysgw: TSM:READY:ID=0,PAR=0,DIS=0
mysgw: MCO:REG:NOT NEEDED
mysgw: Listening for connections on 0.0.0.0:5003
mysgw: MCO:BGN:STP
mysgw: MCO:BGN:INIT OK,TSP=1
mysgw: New connection from 10.1.15.182
mysgw: Client 0 connected
mysgw: TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
mysgw: TSF:MSG:BC
mysgw: TSF:MSG:FPAR REQ,ID=255
mysgw: TSF:PNG:SEND,TO=0
mysgw: TSF:CKU:OK
mysgw: TSF:MSG:GWL OK
mysgw: TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
mysgw: TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
mysgw: TSF:MSG:BC
mysgw: TSF:MSG:FPAR REQ,ID=255
mysgw: TSF:CKU:OK,FCTRL
mysgw: TSF:MSG:GWL OK
mysgw: TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
mysgw: TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
mysgw: TSF:MSG:BC
mysgw: TSF:MSG:FPAR REQ,ID=255
mysgw: TSF:CKU:OK,FCTRL
mysgw: TSF:MSG:GWL OK
mysgw: TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0No problem connecting with MYScontroller.
But I cant get my nodes to connect. I do know they work sins they connected to my Arduino GW with no problem. Need som help here to figure out whats wrong
Thx
/HΓ₯kan
-
https://www.mysensors.org/build/debug
I'd start from here. Also why are you using beta version instead of the stable one?
-
Node says it cant find parent. And Rpi says everything is ok. Its like it dosent awnser the Node for som reason.
Is it possible to connect radio module in the wrong way and startup will still initiate OK?
-
Have you tried with stable 2.1.1?
-
@gohan hmm why did I get 2.0.0 Beta
doing
git clone https://github.com/mysensors/MySensors.gitBut still gets Beta version...Sorry n00b to Linux and Rpi is there a better way to get the updateed version?
-
It downloaded the development branch instead of the stable one. @hek is it normal?
-
Yes, development is the default branch (and the only one accepting PRs etc).
If you want to switch to master after cloning the repo, do:
git checkout master
-
Could be worth adding that command to the guide
-
@gohan
What guide?
The rpi guide checks out master: https://www.mysensors.org/build/raspberryThe contribution guide is focused on creating pull requests, so it naturally uses the default (development).
-
Ah my bad, I didn't see the - - branch master at the end of the line as I'm on mobile
-
Try assigning a node ID. Sometimes controllers will provide an ID but the gateway will not. Currently it is using the ID of 255. I think the line of code to add to the sketch is
#define node_ID #
Where the # at the end is the number of your node. Any value between 1 and 254 should work.
-
@gohan hehe N00b misstake thougt --branch Master was referens that the rest downloaded master...have just started to try out git
-
OK got version 2.1.1 on place on Rpi deffined Node Id but still no luck connecting to Rpi GW
GW Log
mysgw: Starting gateway...
mysgw: Protocol version - 2.1.1
mysgw: MCO:BGN:INIT GW,CP=RNNG--Q,VER=2.1.1
mysgw: TSF:LRT:OK
mysgw: TSM:INIT
mysgw: TSF:WUR:MS=0
mysgw: TSM:INIT:TSP OK
mysgw: TSM:INIT:GW MODE
mysgw: TSM:READY:ID=0,PAR=0,DIS=0
mysgw: MCO:REG:NOT NEEDED
mysgw: Listening for connections on 0.0.0.0:5003
mysgw: MCO:BGN:STP
mysgw: MCO:BGN:INIT OK,TSP=1
mysgw: TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
mysgw: TSF:MSG:BC
mysgw: TSF:MSG:FPAR REQ,ID=255
mysgw: TSF:PNG:SEND,TO=0
mysgw: TSF:CKU:OK
mysgw: TSF:MSG:GWL OK
mysgw: TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
mysgw: TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
mysgw: TSF:MSG:BC
mysgw: TSF:MSG:FPAR REQ,ID=255
mysgw: TSF:CKU:OK,FCTRL
mysgw: TSF:MSG:GWL OKNode Log:
0 MCO:BGN:INIT NODE,CP=RNNNA--,VER=2.1.1
3 TSM:INIT
4 TSF:WUR:MS=0
11 TSM:INIT:TSP OK
13 TSM:FPAR
15 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
2022 !TSM:FPAR:NO REPLY
2024 TSM:FPAR
2026 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
4034 !TSM:FPAR:NO REPLY
4036 TSM:FPAR
4038 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
6046 !TSM:FPAR:NO REPLY
6048 TSM:FPAR
6050 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
8058 !TSM:FPAR:FAIL
8059 TSM:FAIL:CNT=1
8061 TSM:FAIL:PDTGoing to replace radio and try again.
-
Double check node ID, I don't see it in node log
-
@gohan Changed radio on Rpi
and node log looks like this now, Forgot MY_ before node0 MCO:BGN:INIT NODE,CP=RNNNA--,VER=2.1.1
3 TSM:INIT
4 TSF:WUR:MS=0
11 TSM:INIT:TSP OK
13 TSM:INIT:STATID=2
18 TSF:SID:OK,ID=2
19 TSM:FPAR
55 TSF:MSG:SEND,2-2-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
2063 !TSM:FPAR:NO REPLY
2065 TSM:FPAR
2101 TSF:MSG:SEND,2-2-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
4108 !TSM:FPAR:NO REPLY
4110 TSM:FPAR
4146 TSF:MSG:SEND,2-2-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
6153 !TSM:FPAR:NO REPLY
6155 TSM:FPAR
6191 TSF:MSG:SEND,2-2-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
8198 !TSM:FPAR:FAIL
8199 TSM:FAIL:CNT=1
8201 TSM:FAIL:PDT
-
@keldandorin Looks like I get som data to GW now but it dosent connect. Node has ID 3
mysgw: TSF:MSG:BC
mysgw: TSF:MSG:FPAR REQ,ID=3
mysgw: TSF:CKU:OK,FCTRL
mysgw: TSF:MSG:GWL OK
mysgw: !TSF:MSG:SEND,0-0-3-3,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
mysgw: TSF:MSG:READ,3-3-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
mysgw: TSF:MSG:BC
mysgw: TSF:MSG:FPAR REQ,ID=3
mysgw: TSF:CKU:OK,FCTRL
mysgw: TSF:MSG:GWL OK
-
Do you have cap on the radio?
-
@gohan yes
-
@keldandorin If I pars log from GW it says
Sent Message
Sender: 0
Last Node: 0
Next Node: 3
Destination: 3
Sensor Id: 255
Command: INTERNAL
Message Type:I_FIND_PARENT_RESPONSE
Payload Type: P_BYTE
Payload Length: 1
Signing: 0
Failed uplink counter: 0
Status: NACK (OK=success, NACK=no radio ACK received)
Payload: 0Just like its acctualy responding to Node !
But the node dosent like the awnser
-
Hi guys, realy need som help here. Got my Rpi gateway up and running and logfile looks ok, see below.
have a working Node running with DTH22. (know its working sins its conenct to my Arduino GW)
Tryed to onfigured Node Id on node. Connecting to my RpiGW with MYScontroller and can see the gateway but no nodes connect.
Log on PRI looks like this
mysgw: Starting gateway...
mysgw: Protocol version - 2.1.1
mysgw: MCO:BGN:INIT GW,CP=RNNG--Q,VER=2.1.1
mysgw: TSF:LRT:OK
mysgw: TSM:INIT
mysgw: TSF:WUR:MS=0
mysgw: TSM:INIT:TSP OK
mysgw: TSM:INIT:GW MODE
mysgw: TSM:READY:ID=0,PAR=0,DIS=0
mysgw: MCO:REG:NOT NEEDED
mysgw: Listening for connections on 0.0.0.0:5003
mysgw: MCO:BGN:STP
mysgw: MCO:BGN:INIT OK,TSP=1
mysgw: TSF:MSG:READ,3-3-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
mysgw: TSF:MSG:BC
mysgw: TSF:MSG:FPAR REQ,ID=3
mysgw: TSF:CKU:OK,FCTRL
mysgw: TSF:MSG:GWL OK
mysgw: !TSF:MSG:SEND,0-0-3-3,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0Log on Node like this
0 MCO:BGN:INIT NODE,CP=RNNNA--,VER=2.1.1
3 TSM:INIT
4 TSF:WUR:MS=0
11 TSM:INIT:TSP OK
13 TSM:INIT:STATID=3
14 TSF:SID:OK,ID=3
16 TSM:FPAR
52 TSF:MSG:SEND,3-3-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
2059 !TSM:FPAR:NO REPLY
2061 TSM:FPAR
2097 TSF:MSG:SEND,3-3-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
4104 !TSM:FPAR:NO REPLY
4106 TSM:FPAR
4142 TSF:MSG:SEND,3-3-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
6149 !TSM:FPAR:NO REPLY
6151 TSM:FPAR
6187 TSF:MSG:SEND,3-3-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
8194 !TSM:FPAR:FAIL
8195 TSM:FAIL:CNT=1
8197 TSM:FAIL:PDTFrom my basic understanding it looks like the GW dont responding in the correct way or the node dont like the awnser. Anyone with more experince out there that can give me some ideas how to fix this.
Thx
/HΓ₯kan
-
The gateway is replying but node is not receiving. Where are you getting power for your nrf24 radio on the rpi? Are you using a capacitor ? size?
-
@gohan taking power from 3v3 pin number 1 an using capasitor that is 10uF
-
Other users reported a similar problem and they solved by using something like this (that's the one I have on my rpi) or any other similar voltage regulator + capacitor
-
@gohan had it running now for a cuple of hours and sudenly it registerd. No luck efter reboot though. Guess I have to order one of them Voltage regulators/capacitors....realy wish I hade one now in my Man Cave
-
I ordered them by mistake some time ago, but they turned out to be very useful
-
@gohan had it running again for some time and at message1890739 It got connected again and seems to be able to send message to GW. But as you say its the GW sending part that dosent seems to work.
1890739 TSM:FPAR:OK
1890740 TSM:ID
1890742 TSM:ID:OK
1890744 TSM:UPL
1890749 TSF:MSG:SEND,3-3-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=OK:1
1892756 TSM:UPL
1892761 TSF:MSG:SEND,3-3-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=OK:1
1892768 TSF:MSG:READ,0-0-3,s=255,c=3,t=25,pt=1,l=1,sg=0:1
1892773 TSF:MSG:PONG RECV,HP=1
1892776 TSM:UPL:OK
-
@gohan You think one of this could solv it to.
http://www.ebay.com/itm/10pcs-LM350-LM350T-3A-Adjustable-Voltage-Regulator-TO-220-NS-/270934993534?hash=item3f14fbea7em1teKyPPDfS02DlKXI_oD1gUsing 5v as output insted and regulat it down to 3.3 v and capasitator on that.
Got them in local store
-
I suggested those modules because you can quickly swap the radio module, but that may work too. Pls post back your results