ESP8266 gateway and sensor node not talking - noobie

[pwatt01]

Hello all,

I just had all of my parts arrive and are builing my contoller and first sensor (DHT11 on MEGA clone). After flashing both (using the development build), they both seem to be working according to the serial monitor, but i cannot seem to make them talk to each other!

Can anyone help me out? I am using the examples on both the gateway and node.

Here is the output from the gateway after pressing reset:

0‚~?–4“Ò¶£ÿOAaû0;0;3;0;9;Starting...
scandone
f 0, ....scandone
.add 0
aid 4
pm open phy_2,type:2 0 0
cnt 

connected with <ssid>, channel 1
ip:192.168.1.200,mask:255.255.255.0,gw:192.168.1.254
.IP: 192.168.1.200
0;0;3;0;9;gateway started, id=0, parent=0, distance=0

this is from the sensor node:

Starting...
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:
read: 255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
find parent
send: 255-255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
read: 255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
read: 255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
read: 255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
find parent
send: 255-255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
read: 255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
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
T:21.00
find parent
send: 255-255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
read: 255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
H:36.00
find parent
send: 255-255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:

and here is the log from domotitz

2015-10-29 07:11:37.529 Domoticz V2.3347 (c)2012-2015 GizMoCuz
2015-10-29 07:11:37.529 Build Hash: b835f24, Date: 2015-10-15 03:16:03
2015-10-29 07:11:37.554 Sunrise: 05:48:00 SunSet:19:10:00
2015-10-29 07:11:37.554 EventSystem: reset all events...
2015-10-29 07:11:37.561 Active notification subsystems: (0/10)
2015-10-29 07:11:37.657 Webserver started on port: 8080
2015-10-29 07:11:37.662 Started shared server on: ::
2015-10-29 07:11:37.720 Incoming connection from: 127.0.0.1
2015-10-29 07:11:39.666 EventSystem: reset all events...
2015-10-29 07:11:39.667 EventSystem: reset all device statuses...
2015-10-29 07:11:39.667 EventSystem: Started
2015-10-29 07:11:41.672 MySensors: connected to: 192.168.1.200:5003
2015-10-29 07:11:41.672 MySensors: Gateway Ready...
2015-10-29 07:11:42.366 Login successfull : user 'admin'

[pwatt01]

OK.. i think after looking a bit more they are talking.. however there are a few issues and they are not understanding each other or somehitng. I remember reading before that there is a way to flash the device back to stock/wipe the EEPROM. DOes anyone know the link to that?

[hek]

What does the gateway log say when you restart the sensor?

[pwatt01]

Nothing. Or no change at least. The shots above are still the only messages that I am getting, apart from the ESP8266 rebooting by itself occasionaly, and the sensor node tends to repeat itself as new readings come in

[Mersing]

Hello,

I've setup a ESP8266 Gateway with RF24 Radio.
I've got a RF24 Node with DS18B20.
I'ved used Esp8266Gateway.ino / DallasTemperatureSensor.ino out of the box.
Everything is working fine. Node and GW are communicating.

I'm now trying to run this setup with RF69. I'm facing the same issue as described in the initial post.

Pin mapping
RF69 <-> ESP8266
DIO0 <-> GPIO4
SCK <-> GPIO14
MOSI <-> GPIO13
MISO <-> GPIO12
CS <-> GPIO15

From RFM69.h
define RF69_SPI_CS               SS

#elif defined(ARDUINO_ARCH_ESP8266)
  // TODO !! Untested code! Entering unknown territory...
  #define RF69_IRQ_PIN          4
  #define RF69_IRQ_NUM          0
#endif

By default, from RFM69.h, RF69_IRQ_PIN is 2.
However to properly boot GPIO15 must be LOW and GPIO2 must be HIGH.
Connecting IRQ to GPIO2, RF69 pull its IRQ to LOW, making GPIO2 LOW and ESP8266 not booting.
Then I'll use GPIO4.

I'm using the same config file for GW and Node (e.g same NWETWORKID, ENCRYPTKEY, FREQUENCY).

On the Node Side : DallasTemperatureSensor.ino

#define isRFM69HW true // Enable High Power
MyTransportRFM69 transport( RFM69_FREQUENCY, RFM69_NETWORKID, RF69_SPI_CS, RF69_IRQ_PIN, isRFM69HW, RF69_IRQ_NUM );
MySensor gw( transport );
gw.begin( NULL, 8 );

On the GW Side : Esp8266Gateway.ino

#define isRFM69HW true
MyTransportRFM69 transport(RFM69_FREQUENCY, RFM69_NETWORKID, RF69_SPI_CS, RF69_IRQ_PIN, isRFM69HW, RF69_IRQ_NUM);

OUTPUT

GW Side

ESP8266 MySensors Gateway
Connecting to WRT54G
.......Connected!
IP: 192.168.1.25
0;0;3;0;9;gateway started, id=0, parent=0, distance=0

Node

send: 8-8-0-0 s=255,c=0,t=17,pt=0,l=3,sg=0,st=fail:1.5
send: 8-8-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,st=fail:0
sensor started, id=8, parent=0, distance=1
send: 8-8-0-0 s=255,c=3,t=11,pt=0,l=18,sg=0,st=fail:Temperature Sensor
send: 8-8-0-0 s=255,c=3,t=12,pt=0,l=3,sg=0,st=fail:1.1
send: 8-8-0-0 s=0,c=0,t=6,pt=0,l=0,sg=0,st=fail:
send: 8-8-0-0 s=0,c=1,t=0,pt=7,l=5,sg=0,st=fail:21.5
find parent
send: 8-8-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
send: 8-8-0-0 s=0,c=1,t=0,pt=7,l=5,sg=0,st=fail:21.5
send: 8-8-0-0 s=0,c=1,t=0,pt=7,l=5,sg=0,st=fail:21.5

No more log output from the Gateway.

Any clue ?

[Mersing]

Hello,

I received addition log on the GW:

ESP8266 MySensors Gateway
Connecting to WRT54G
.......Connected!
IP: 192.168.1.25
0;0;3;0;9;gateway started, id=0, parent=0, distance=0
0;0;3;0;9;Inclusion started by button.
0;0;3;0;5;1
0;0;3;0;9;Inclusion started by button.
0;0;3;0;9;Inclusion started by button.
0;0;3;0;9;Inclusion started by button.
0;0;3;0;9;Inclusion started by button.
0;0;3;0;9;Inclusion started by button.
0;0;3;0;9;Inclusion started by button.
0;0;3;0;9;Inclusion started by button.
0;0;3;0;9;Inclusion started by button.
0;0;3;0;9;Inclusion started by button.
0;0;3;0;5;0

"Inclusion started by button." are coming randomly (not triggered by node reboot ).

[hek]

Guys, would be great if you used the development branch instead.
Really need more testers of that code... also and any fixes for ESP8266/RF69 would be done in the dev-branch.

[Mersing]

Hello,

I'm now testing with 1.6, on GW and Node.

I'm trying to get familiar with the 1.6 changes.
On the node how can I setup the NODE ID ? ( it seems that gw.begin( NULL, 5) can't be used anymore).
On the Node side, I'm using DallasTemperatureSensor.ino.
Should I add presentation() call from Setup () ?

void setup()   { 
  // Startup up the OneWire library
  sensors.begin();
  // requestTemperatures() will not block current thread
  sensors.setWaitForConversion(false);
  presentation();
}

I've setup the communication with RF24, as a first test.
From the GW

0;0;3;0;9;read: 5-5-0 s=255,c=0,t=17,pt=0,l=10,sg=0:1.6.0-beta
0;0;3;0;9;read: 5-5-0 s=255,c=3,t=6,pt=1,l=1,sg=0:0
0;0;3;0;9;read: 5-5-0 s=255,c=3,t=11,pt=0,l=18,sg=0:Temperature Senso
0;0;3;0;9;read: 5-5-0 s=255,c=3,t=12,pt=0,l=3,sg=0:1.1
0;0;3;0;9;read: 5-5-0 s=255,c=3,t=11,pt=0,l=18,sg=0:Temperature Senso
0;0;3;0;9;read: 5-5-0 s=255,c=3,t=12,pt=0,l=3,sg=0:1.1
0;0;3;0;9;read: 5-5-0 s=0,c=0,t=6,pt=0,l=0,sg=0:
0;0;3;0;9;read: 5-5-0 s=0,c=1,t=0,pt=7,l=5,sg=0:23.6
0;0;3;0;9;read: 5-5-0 s=0,c=1,t=0,pt=7,l=5,sg=0:23.7

Everything is working fine. (Seems the Node ID is coming from previous 1.5 upload, I've setup it to 5)

I've then replaced the radio by RF69 ones.
Below the changes in GatewayESP8266.ino

#define MY_RADIO_RFM69
#define MY_RF69_IRQ_PIN 4

Node ouput

Starting...
send: 5-5-0-0 s=255,c=0,t=17,pt=0,l=10,sg=0,st=fail:1.6.0-beta
send: 5-5-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,st=fail:0
send: 5-5-0-0 s=255,c=3,t=11,pt=0,l=18,sg=0,st=fail:Temperature Sensor
send: 5-5-0-0 s=255,c=3,t=12,pt=0,l=3,sg=0,st=fail:1.1
sensor started, id=5, parent=0, distance=1
send: 5-5-0-0 s=255,c=3,t=11,pt=0,l=18,sg=0,st=fail:Temperature Sensor
send: 5-5-0-0 s=255,c=3,t=12,pt=0,l=3,sg=0,st=fail:1.1
find parent
send: 5-5-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
send: 5-5-0-0 s=0,c=0,t=6,pt=0,l=0,sg=0,st=fail:
send: 5-5-0-0 s=0,c=1,t=0,pt=7,l=5,sg=0,st=fail:22.5
send: 5-5-0-0 s=0,c=1,t=0,pt=7,l=5,sg=0,st=fail:22.6

GW Output

0;0;3;0;9;Starting...
scandone
f 0, ....scandone
.add 0
aid 7
pm open phy_2,type:2 0 0
cnt 

connected with WRT54G, channel 6
dhcp client start...
.ip:192.168.1.25,mask:255.255.255.0,gw:192.168.1.1
.IP: 192.168.1.25
0;0;3;0;9;gateway started, id=0, parent=0, distance=0

ESP8266 MySensors Gateway
Connecting to WRT54G
sl
f -240, ....scandone
usl
sul 7 0
reconnect
rm 0
pm close 7 0 0/3399505
f 0, ....scandone
.add 0
aid 7
pm open phy_2,type:2 0 0
cnt 

connected with WRT54G, channel 6
dhcp client start...
..ip:192.168.1.25,mask:255.255.255.0,gw:192.168.1.1
.Connected!
IP: 192.168.1.25

Nothing more on the GW side.

Any idea ? Where (lib) can I start troubleshooting ?

Regards.

[hek]

Set static id with:

#define MY_NODE_ID xx

My guess is something goes wrong here:
https://github.com/mysensors/Arduino/blob/development/libraries/MySensors/drivers/RFM69/RFM69.cpp#L47

[Mersing]

Hello,
I had a look at RFM69.cpp, bool RFM69::initialize function.
It a bit far away from my current skill to debug.
I've tried to display registers to check if they have been properly initialized.

  Serial.println( "bool RFM69::initialize" );
  Serial.println( "Read Registers" );
  Serial.print( "RegOpMode Read 0x01 : " );
  Serial.println( readReg( 0x01) );
  Serial.print( "RegDataModul Read 0x02 : " );
  Serial.println( readReg( 0x02) );
  Serial.print( "RegVersion Read 0x10 : " );
  Serial.println( readReg( 0x10) );
  Serial.print( "RegRssiValue Read 0x24) : " );
  Serial.println( readReg( 0x24) );
  Serial.println( "" );

Output is

0;0;3;0;9;Starting...
bool RFM69::initialize
Read Registers
RegOpMode Read 0x01 : 4
RegDataModul Read 0x02 : 0
RegVersion Read 0x10 : 36
RegRssiValue Read 0x24) : 56

scandone
f 0, ....scandone
.add 0
aid 7
pm open phy_2,type:2 0 0
cnt 

Seems the registers are OK. However I can't go a step further.

I'm please to help for testing any new enhancement.

Regards,
Mersing.

[hek]

Hmm... I should really order a few RFM69 radios myself.

I only have a couple of Moteions. Doesn't help much if I would help out debugging ESP8266 with RFM69.

[Mersing]

You could maybe hack / re-use the radio from the Motino

[hek]

Na... just have to wait for the china slow boat. Should be here before christmas

[Fabien]

I have same bug : http://forum.mysensors.org/topic/2538/esp8266-and-rfm69w-loop-reboot

[hek]

Are you getting the same error in dev branch?

[Fabien]

With the last git developpement it works. except when a node start presentation, gateway reboot. And sometimes it reboots randomless.
node is a sensebender with MySensors 1.6 and gateway with 1.6 too.
Important : You have to define MY_RF69_IRQ_NUM = MY_RF26_IRQ_PIN on ESP8266

#define MY_RADIO_RFM69
#define MY_RFM69_FREQUENCY   RF69_868MHZ
#define MY_RF69_IRQ_PIN 15
#define MY_RF69_SPI_CS 2
#define MY_RF69_IRQ_NUM 15

Result is

connected with PandoraBox_1BB657, channel 1
dhcp client start...
.ip:192.168.2.165,mask:255.255.255.0,gw:192.168.2.1
.IP: 192.168.2.165
0;0;3;0;9;Init complete, id=0, parent=0, distance=0
chg_B:-120

Soft WDT reset

ctx: cont 
sp: 3ffef9a0 end: 3ffefc60 offset: 01b0

>>>stack>>>
3ffefb50:  00000001 3ffefd00 3ffeff68 00000001  
3ffefb60:  00000024 3ffefd00 3ffeff68 402022f2  
3ffefb70:  3ffe8496 00000000 3ffefd00 40202378  
3ffefb80:  3ffe8496 00000000 3ffefd00 40202563  
3ffefb90:  3ffefd1e 00000001 3ffefd00 40202a43  
3ffefba0:  3fffdc20 00000000 3ffeec28 3ffefcd8  
3ffefbb0:  3fffdc20 3ffefd1d 3ffefd00 40202e0c  
3ffefbc0:  40209c8d 00000000 3ffeec28 40203ed1  
3ffefbd0:  00000000 00000002 3ffefe58 402039d0  
3ffefbe0:  00000000 3ffefd00 3ffeff68 40202338  
3ffefbf0:  40101500 402059d6 3ffeff50 3ffefc20  
3ffefc00:  3ffefc10 00000004 3ffefcf9 40202358  
3ffefc10:  3fffdc20 00000000 00000000 3ffeec30  
3ffefc20:  3fffdc20 00000000 3ffeec28 3ffeec30  
3ffefc30:  3fffdc20 00000000 3ffeec28 40203aee  
3ffefc40:  00000000 00000000 3ffeec28 402041a0  
3ffefc50:  00000000 00000000 3ffeec40 40100114  
<<<stack<<<
�!�L�<1���0;0;3;0;9;Starting gateway (RRNGE-, 1.6.0-beta)
0;0;3;0;9;Radio init successful.
scandone
state: 0 -> 2 (b0)
.state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 3
pm open phy_2,type:2 0 0
cnt 
chg_B:-60

connected with PandoraBox_1BB657, channel 1
dhcp client start...
.ip:192.168.2.165,mask:255.255.255.0,gw:192.168.2.1
.IP: 192.168.2.165
0;0;3;0;9;Init complete, id=0, parent=0, distance=0
chg_B:-120
0;0;3;0;9;read: 1-1-0 s=1,c=1,t=0,pt=7,l=5,sg=0:24.6
0;0;3;0;9;read: 1-1-0 s=2,c=1,t=1,pt=2,l=2,sg=0:51
0;0;3;0;9;read: 1-1-0 s=1,c=1,t=0,pt=7,l=5,sg=0:24.4

And something strange, I only recieve Humidity one time. (sensebender defaut sketch with FORCE_TRANSMIT_INTERVAL 0 )

[Fabien]

@hek you are right it works fine with

#define TIME_OUT 500

in https://github.com/mysensors/Arduino/blob/development/libraries/MySensors/drivers/RFM69/RFM69.cpp#L47

0�~?�4�!�{�OAa�0;0;3;0;9;Starting gateway (RRNGE-, 1.6.0-beta)
0;0;3;0;9;Radio init successful.
scandone
state: 0 -> 2 (b0)
.state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 3
pm open phy_2,type:2 0 0
cnt 
chg_B:-60

connected with PandoraBox_1BB657, channel 1
dhcp client start...
.ip:192.168.2.165,mask:255.255.255.0,gw:192.168.2.1
.IP: 192.168.2.165
0;0;3;0;9;Init complete, id=0, parent=0, distance=0
chg_B:-120
0;0;3;0;9;read: 1-1-0 s=1,c=1,t=0,pt=7,l=5,sg=0:24.8
0;0;3;0;9;read: 1-1-0 s=2,c=1,t=1,pt=2,l=2,sg=0:54
0;0;3;0;9;read: 1-1-0 s=255,c=0,t=17,pt=0,l=10,sg=0:1.6.0-beta
0;0;3;0;9;read: 1-1-0 s=255,c=4,t=0,pt=6,l=10,sg=0:FFFFFFFFFFFFFFFF0300
0;0;3;0;9;read: 1-1-0 s=255,c=3,t=11,pt=0,l=17,sg=0:Sensebender Micro
0;0;3;0;9;read: 1-1-0 s=255,c=3,t=12,pt=0,l=3,sg=0:1.4
0;0;3;0;9;read: 1-1-0 s=2,c=0,t=7,pt=0,l=0,sg=0:
0;0;3;0;9;read: 1-1-0 s=2,c=1,t=1,pt=2,l=2,sg=0:54
0;0;3;0;9;read: 1-1-0 s=1,c=1,t=0,pt=7,l=5,sg=0:24.7
0;0;3;0;9;read: 1-1-0 s=2,c=1,t=1,pt=2,l=2,sg=0:50
0;0;3;0;9;read: 1-1-0 s=1,c=1,t=0,pt=7,l=5,sg=0:24.7
0;0;3;0;9;read: 1-1-0 s=2,c=1,t=1,pt=2,l=2,sg=0:51
0;0;3;0;9;Client 0 connected
0;0;3;0;9;read: 1-1-0 s=1,c=1,t=0,pt=7,l=5,sg=0:24.5
0;0;3;0;9;read: 1-1-0 s=2,c=1,t=1,pt=2,l=2,sg=0:50

I don't try with other timeout values.

[hek]

Ok, great. We need to increase timeout then.

[Fabien]

@hek Yes and perhaps a feature to set MY_RF69_IRQ_NUM = MY_RF26_IRQ_PIN when using ESP8266. Do You want to test other timeout values ? Is it critical ?

[hek]

@Fabien said:

MY_RF26_IRQ_PIN

I cannot find this defined anywhere...

[Fabien]

sorry MY_RF69_IRQ_PIN ...

[Fabien]

Work with 51ms timeout with my config. I set 60ms to be "secure"

[Yveaux]

@hek said:

Ok, great. We need to increase timeout then.

Better add a yield() call in those blocking wait loops.
When quiclkly looking over the code of the RF69 driver, the RFM69::initialize call could in theory block for 1.5 sec...
That's a watchdog reset waiting to happen!

[hek]

Yep,

https://github.com/mysensors/Arduino/pull/287

[Yveaux]

@hek

[Mersing]

This is working great !

Tx for this !

[chrille]

I am seeing something similar with RFM69 (specifically RFM69CW) and ESP8266. I have build an ESP8266 gateway based on the GatewayESP8266 sketch and this is what I changed

#define MY_RADIO_RFM69
#define MY_GATEWAY_ESP8266
#define MY_RFM69_FREQUENCY   RF69_868MHZ
#define MY_RF69_IRQ_PIN 4
#define MY_RF69_SPI_CS 15
#define MY_RF69_IRQ_NUM 4

I build a sensor node with the DallasTemperatureSensor sketch on an Arduino Mini Pro and defined

#define MY_RADIO_RFM69
#define MY_RFM69_FREQUENCY   RF69_868MHZ

When I start up the gateway I see

0;255;3;0;9;Starting gateway (RRNGE-, 2.0.0-beta)
0;255;3;0;9;Radio init successful.
....scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 8
cnt

connected with AP, channel 1
ip:62.x.x.x,mask:255.255.255.128,gw:62.x.x.x
.IP: 62.x.x.x
0;255;3;0;9;Init complete, id=0, parent=0, distance=0

So far so good - I assume all the radio wiring is OK, since the radio init is successful

On the sensor node I see

Starting sensor (RRNNA-, 2.0.0-beta)
Radio init successful.
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:
Init complete, id=255, parent=255, distance=255

As soon as the sensor node is started the ESP8266 crashes with a WDT reset

Soft WDT reset

ctx: cont
sp: 3ffef370 end: 3ffef630 offset: 01b0

>>>stack>>>
3ffef520:  00000001 3ffef6d4 3ffef964 00000000
3ffef530:  00000024 3ffef6d4 3ffef964 40202436
3ffef540:  3ffe8432 00000000 3ffef6d4 402024bc
3ffef550:  3ffe8432 00000000 3ffef6d4 402026a7
3ffef560:  3ffef6f2 00000001 3ffef6d4 40202b87
3ffef570:  3fffdae0 00000000 3ffee600 3ffef6ac
3ffef580:  3fffdae0 3ffef6f1 3ffef6d4 40202cf4
3ffef590:  3fff1210 00000000 3ffee600 402042b4
3ffef5a0:  00000000 00000002 3ffef82c 40203d20
3ffef5b0:  00000000 3ffef6d4 3ffef964 4020247c
3ffef5c0:  401057ff 00000400 00000103 3ffef5f0
3ffef5d0:  3ffef5e0 00000004 3ffef6cd 4020249c
3ffef5e0:  3ffe8920 00000000 00000000 3ffee608
3ffef5f0:  3fffdae0 00000000 3ffee600 3ffee608
3ffef600:  3fffdae0 00000000 3ffee600 40203e6c
3ffef610:  feefeffe feefeffe 3ffee600 402045b4
3ffef620:  feefeffe feefeffe 3ffee610 40100114
<<<stack<<<

The libraries are 2.0 beta as from a few days ago. I consider the power to the ESP8266 to be OK, since I use the same for en NRF24 based gateway and also for several other ESP modules.

From the thread I understand that known issues should be fixed in the current beta. Any ideas on how to move on?

[Yveaux]

@chrille Try adding the following line to your setup() function:

ESP.wdtDisable();

It should disable the (software) watchdog on ESP. See if it continues, or if it will now just hang.

[chrille]

@Yveaux Just tried that. The change removed the watchdog message and the stack trace, but the module still reboots

[chrille]

...I also tried to change TIME_OUT in rfm69.cpp to 500 as suggested by Fabien. Doesn't make any difference

[Yveaux]

@chrille said:

the module still reboots

Probably the hardware watchdog kicks in then...

[chrille]

@Yveaux I did some further tests and it may be related to the inclusion mode feature. At least disabling this makes things more stable - but I still haven't got the radio side working reliable. When this is working I will go back to the gateway and see if I can find out what triggers the crash

[chrille]

@Yveaux I think I have narrowed down the issue now to this code in RFM69.cpp

void RFM69::sendACK(const void* buffer, byte bufferSize) {
debug(PSTR("RFM69: void sendACK\n"));
  byte sender = SENDERID;
  debug(PSTR("RFM69: sendACK - entering while()\n"));
  while (!canSend()) receiveDone();
  sendFrame(sender, buffer, bufferSize, false, true);
}

(The debug lines are added by me)

Most of the time the WDT kicks in, after logging "entering while()" - occasionally it will reach sendFrame() and log a "read: " line but then the WDT kicks in when it gets to the while() loop again.
sendAck is called from sendFrame, that disables interrupts, by calling select()

With a bunch of additional debug turned on, this is what I get on the console

0;255;3;0;9;Init complete, id=0, parent=0, distance=0
chg_B:-60
chg_B:-120
0;255;3;0;9;RFM69: interruptHandler
0;255;3;0;9;RFM69: IRQ handler - select chip
0;255;3;0;9;RFM69: IRQ handler - release chip
0;255;3;0;9;RFM69: IRQ handler - read RSSI
0;255;3;0;9;RFM69: receiveDone() - payload
0;255;3;0;9;RFM69: void sendACK
chg_B:-60
0;255;3;0;9;RFM69: sendACK - entering while()
0;255;3;0;9;RFM69: sendFrame()
0;255;3;0;9;RFM69: interruptHandler
0;255;3;0;9;RFM69: IRQ handler - read RSSI
0;255;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0,sg=0:
0;255;3;0;9;RFM69: interruptHandler
0;255;3;0;9;RFM69: IRQ handler - select chip
0;255;3;0;9;RFM69: IRQ handler - release chip
0;255;3;0;9;RFM69: IRQ handler - read RSSI
0;255;3;0;9;RFM69: receiveDone() - payload
0;255;3;0;9;RFM69: void sendACK
0;255;3;0;9;RFM69: sendACK - entering while()

Soft WDT reset

ctx: cont
sp: 3ffefa70 end: 3ffefd30 offset: 01b0

>>>stack>>>
3ffefc20:  00000001 3ffefdd4 3ffeffdc 000000ff
3ffefc30:  00000024 3ffefdd4 3ffeffdc 402022da
3ffefc40:  3ffe8496 00000000 3ffefdd4 40202360
3ffefc50:  00000000 00000000 3ffefdd4 4020254b
3ffefc60:  3ffefdf2 00000000 3ffefdd4 402037f9
3ffefc70:  3fffdc20 00000000 3ffefdd4 3ffefdac
3ffefc80:  3fffdc20 3ffefdf1 3ffefdd4 4020385c
3ffefc90:  00000003 00000000 3ffeecf8 40204035
3ffefca0:  00000003 00000000 00000000 00000000
3ffefcb0:  3ffefd58 3ffefdd4 3ffeffdc 3ffeed00
3ffefcc0:  3ffefe00 00000000 3ffefe98 40203aec
3ffefcd0:  00000003 00000000 000000ff 00000000
3ffefce0:  000000ff 00000002 00000000 00000000
3ffefcf0:  3fffdc20 00000000 3ffeecf8 3ffeed00
3ffefd00:  3fffdc20 00000000 3ffeecf8 40203c06
3ffefd10:  00000000 00000000 3ffeecf8 4020432c
3ffefd20:  00000000 00000000 3ffeed10 40100114
<<<stack<<<

Any ideas on how to fix this, would be greatly appreciated!

[Yveaux]

@chrille I'm not familiar with rfm implementation, but you could try adding a call to yield() inside the while loop.

[chrille]

@Yveaux Thank you very much. This seems to have fixed the issue now!

[Yveaux]

@chrille Could you create a pull-request (or a bug report) for this fix in MySensors' github repo ?

[chrille]

@Yveaux I already did! https://github.com/mysensors/Arduino/pull/396