[Solved] Nodes having trouble reconnecting to gateway
-
@grumpazoid said in Nodes having trouble reconnecting to gateway:
4171 !TSF:MSG:SEND,2-2-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=NACK:1
This is the result from the log parser (from Chrome/Windows10):
Sent Message
Sender: 2
Last Node: 2
Next Node: 0
Destination: 0
Sensor Id: 255
Command: INTERNAL
Message Type:I_PING
Payload Type: P_BYTE
Payload Length: 1
Signing: 0
Failed uplink counter: 0
Status: NACK (OK=success, NACK=no radio ACK received)
Payload: 1The NACK can be caused by the missing capacitor. But you should also see those after it has connected.
@electrik Thanks for this.
I am on Windows 7. I will try another PC. EDIT HAve tried another windows 7 machine No output on IE Firefox Chrome or Opera?
As far as i know the breakout boards I am using have capacitors included on the. So I just apply a good 5V and plug in a radio.@FlyingDomotic Thanks. So would I put that code at the top of the sketch for both node and gateway? Before the loop?
Raspberry Pi 3B - Domoticz + Node Red
Arduino Pro Mini 3.3V - W5100 Ethernet, Nrf24
Arduino Mega, RFLink 433Mhz
Sonoff/ESP8266/Tasmota switches -
@electrik Thanks for this.
I am on Windows 7. I will try another PC. EDIT HAve tried another windows 7 machine No output on IE Firefox Chrome or Opera?
As far as i know the breakout boards I am using have capacitors included on the. So I just apply a good 5V and plug in a radio.@FlyingDomotic Thanks. So would I put that code at the top of the sketch for both node and gateway? Before the loop?
-
@grumpazoid: I had recently the same issue with a 2560 node and a Nano gateway. I fixed it putting a delayMicroseconds(1500) at (very) top of RF24stopListening function.
LOCAL void RF24_stopListening(void) { // The following delay will allow this node to send an ACK to the last received message // Value should be at least equal to ACR (1500 ms for 250 Kb/s transmission with 15 retries delayMicroseconds(1500); //// *** FF_CHANGE *** //// RF24_DEBUG(PSTR("RF24:SPL\n")); // stop listening RF24_ce(LOW); // timing delayMicroseconds(130); RF24_setRFConfiguration(RF24_CONFIGURATION | _BV(RF24_PWR_UP) ); // timing delayMicroseconds(100); }Don't know if your trouble is the same as mine, but hope this helps!
@flyingdomotic Ok So I have modified \Arduino\libraries\MySensors\hal\transport\RF24\driver\RF24.cpp and reuploaded my sketches to the gateway and a couple of nodes.
Unfortunately one of those nodes is still reluctant to connect. You can see the tx LED coming on for a long time while it tries.
There must be something in the underlying code not quite right?
-
@grumpazoid Strange. The log parser works for me in Chrome, IE, FF on Win7 and Safari on ios.
Could you check if the browser console says anything about why it doesn't work? (F12 in chrome and FF)
@mfalkvidd Thanks for that.
F11 showed that the page was failing to resolve cdnjs.cloudflare.com
I run a pihole so just needed to add to my whitelist.Fixed. Thanks.
Now back to the node/gateway communication problem!
-
The parser says that no radio ACK has been received when the node tries to ping the gateway.
I have today built a replacement radio breakout board from scratch. The problem is still the same.
Some nodes connect, some randomly do not.
I have replaced every piece of gateway hardware, so this my be something within the Mysensors code.
Any suggestions please?Raspberry Pi 3B - Domoticz + Node Red
Arduino Pro Mini 3.3V - W5100 Ethernet, Nrf24
Arduino Mega, RFLink 433Mhz
Sonoff/ESP8266/Tasmota switches -
The parser says that no radio ACK has been received when the node tries to ping the gateway.
I have today built a replacement radio breakout board from scratch. The problem is still the same.
Some nodes connect, some randomly do not.
I have replaced every piece of gateway hardware, so this my be something within the Mysensors code.
Any suggestions please? -
@grumpazoid what hardware are you running your gateways and sensors on? Please provide a thorough description.
@yveaux I have a serial gateway built on Arduino Uno connected to Pi. This is now just spare as I have W5100 / arduino nano ethernet gateway. Nodes are mostly 3.3V pro minis. One is 5V nano. All arduinos are clones.
Radios on nodes are NRF24L01+. On gateways I can use NRF24L01+ or amplified version (doesn't make a difference to this behaviour).As an example I switched off the gateway 2 hours ago. 2 nodes are came in straight away, the other 3 have no communication. Chances are the same 2 will connect again if I power cycle the gateway but the nodes that work straight away changes randomly. It seems like the gateway does not want to acknowledge certain nodes.
Behaviour is the same if I revert to stock motion sketch.
Raspberry Pi 3B - Domoticz + Node Red
Arduino Pro Mini 3.3V - W5100 Ethernet, Nrf24
Arduino Mega, RFLink 433Mhz
Sonoff/ESP8266/Tasmota switches -
@yveaux I have a serial gateway built on Arduino Uno connected to Pi. This is now just spare as I have W5100 / arduino nano ethernet gateway. Nodes are mostly 3.3V pro minis. One is 5V nano. All arduinos are clones.
Radios on nodes are NRF24L01+. On gateways I can use NRF24L01+ or amplified version (doesn't make a difference to this behaviour).As an example I switched off the gateway 2 hours ago. 2 nodes are came in straight away, the other 3 have no communication. Chances are the same 2 will connect again if I power cycle the gateway but the nodes that work straight away changes randomly. It seems like the gateway does not want to acknowledge certain nodes.
Behaviour is the same if I revert to stock motion sketch.
-
@grumpazoid are you saying you have two gateways using the same frequency (the serial gw and the ethernet gw) running? If that't the case, the problems have a simple solution - turn off one of the gateways.
@mfalkvidd No I only use one at any time.
I started with serial and then built the ethernet gateway. To eliminate the ethernet gateway hardware I just reverted back to serial to test. -
@grumpazoid: I had recently the same issue with a 2560 node and a Nano gateway. I fixed it putting a delayMicroseconds(1500) at (very) top of RF24stopListening function.
LOCAL void RF24_stopListening(void) { // The following delay will allow this node to send an ACK to the last received message // Value should be at least equal to ACR (1500 ms for 250 Kb/s transmission with 15 retries delayMicroseconds(1500); //// *** FF_CHANGE *** //// RF24_DEBUG(PSTR("RF24:SPL\n")); // stop listening RF24_ce(LOW); // timing delayMicroseconds(130); RF24_setRFConfiguration(RF24_CONFIGURATION | _BV(RF24_PWR_UP) ); // timing delayMicroseconds(100); }Don't know if your trouble is the same as mine, but hope this helps!
@flyingdomotic thank you. I also had some problems with some nodes which worked very nice on 2.1.1. When I worked on some of the nodes and updated to 2.3.1 I noticed, that communication wasn't so great anymore.
On first glance this fix works on my plant sensor node. Hope it stays that way now.Some people are saying with debug on it works and without it, it doesn't maybe the Debug line before the ce(low) does the same thing as your delay.
-
I think I have fixed the issue. I changed to the cap on the ethernet gateway from 47uF to 1uF. I have power cycled the gateway 4 times now and all the nodes came in. Looks like less is more! For whatever reason the breakout boards obviously don't work well for me.
I will keep testing for a few days. -
Finally fixed as detailed here https://forum.mysensors.org/topic/10138/repeater-node-causing-problems-solved/25
