Cannot get RFM69HW connection between ESP8266GW and Pro Mini Sensor
-
Quick update: Setting
#define MY_RFM69_IRQ_NUM 5(D1=GPIO5, the ESP has interrupts on (almost) all GPIO pins and the interrupt number equals the pin number) - that is, skipping the digitalPinToInterrupt() function - seems to work. That should pretty much localize the problem. -
Ok, I have finally identified the issue.
I did some more testing with the switched roles, ESP8266 as (light) sensor, Pro Mini as serial gateway, hardcoded MY_NODE_ID. According to the logs, the ESP sends the parent quest, the Pro Mini answers, but never gets an ACK. The ESP does not report any answer. Ergo, the interrupt doesn't work.
So I scoped it, electrically, everything was fine. I tried D2 instead of D1, no change. Then I remembered that the default in the code was GPIO2, which is D4. This is a really stupid choice, because if you connect it like that, the ESP will not boot. GPIO2 needs to be pulled up during boot, and DIO0 from the RFM69 pulls it down. What works though is to first boot, then connect the cable.
Lo and behold - everything suddenly worked. So either I am the idiot and#define MY_RFM69_IRQ_PIN D1is not how you set the interrupt, or whoever thought that it was clever to default the interrupt to a pin that prevents booting also decided to ignore the configured value ...I'll dig into the code to find out, but of course wouldn't mind if anybody who knows the code better would be faster :)
Will file an issue or pull request if I find something. -
@elcaron said in Cannot get RFM69HW connection between ESP8266GW and Pro Mini Sensor:
MY_RFM69_IRQ_PIN
So both MUST be defined? I thought NUM was prety much an override, since it can be programmatically derived from the pin. Undfortunaely, it does not seem to be documented.
-
Ok, I see ...
#define DEFAULT_RFM69_IRQ_NUM digitalPinToInterrupt(DEFAULT_RFM69_IRQ_PIN)So it indeed has to be set separately. I don' really see why this isn't set to
#define DEFAULT_RFM69_IRQ_NUM digitalPinToInterrupt(MY_RFM69_IRQ_PIN)MyConfig.h is included before, so tha should work.
-
I don't know why the code is written the way it is. When I verified the rfm69 wiring and wrote the instructions, I decided to not use the default IRQ pin, since it would interfere with boot (as you also have identified). That's why I added the define instructions to set both MY_RF69_IRQ_PIN and MY_RF69_IRQ_NUM.
I am not familiar with the rfm69 driver code, but I think what you suggest should work. You are very welcome to create a pull request. If someone has any objections, they can always make their case during the code review.
-
@mfalkvidd said in Cannot get RFM69HW connection between ESP8266GW and Pro Mini Sensor:
When I verified the rfm69 wiring and wrote the instructions, I decided to not use the default IRQ pin
Maybe note this in the instructions? This cost me 1 year (in which I did not touch the stuff after i didn't work immediately) and a weekend of checking wireing and so on (because with a missing IRQ on the gateway, it looks like nothing is working, while the issue is quite easy to find on a node).
Ok, PR is filed, I also fixed it for the RFM95, which had the same issue.
-
@mfalkvidd said in Cannot get RFM69HW connection between ESP8266GW and Pro Mini Sensor:
When I verified the rfm69 wiring and wrote the instructions, I decided to not use the default IRQ pin
Maybe note this in the instructions? This cost me 1 year (in which I did not touch the stuff after i didn't work immediately) and a weekend of checking wireing and so on (because with a missing IRQ on the gateway, it looks like nothing is working, while the issue is quite easy to find on a node).
Ok, PR is filed, I also fixed it for the RFM95, which had the same issue.
-
@elcaron could you describe the type of note you think you would have noticed?
Great work on the PR.
@mfalkvidd Maybe a "* Different from code default and examples"?
You do not really expect that you have to change defaults when you get a wiring guide from the official site associated with the code, especially when running an example that is explicitly for the platform (the ESP8266 gateway sketch).In hindsight, this was probably stupid, but I didn't even look at the defines below the table, because I thought I was running a working example specifically for the ESP8266 and only needed to find the right pins.
-
@mfalkvidd Maybe a "* Different from code default and examples"?
You do not really expect that you have to change defaults when you get a wiring guide from the official site associated with the code, especially when running an example that is explicitly for the platform (the ESP8266 gateway sketch).In hindsight, this was probably stupid, but I didn't even look at the defines below the table, because I thought I was running a working example specifically for the ESP8266 and only needed to find the right pins.
-
-
As a * that resolves to above mentioned note directly in the table:
D1* | DIO0 | Gray
...
Below: * Different from code default and examplesAs I said, one doesn't necessarily expect that defaults have to changed an ESP-specific example sketch.
-
Adding references to github:
https://github.com/mysensors/MySensors/issues/1075
https://github.com/mysensors/MySensors/pull/1076 -
Ok, my setup is running now (including personalization, encryption, and soft signing) and stuff is published to mqtt.
Thanks everyone for the help! I really like this community.Now I need to resolve the issue with the OpenHAB binding but that's no topic for here.
