-
-
Notifications
You must be signed in to change notification settings - Fork 894
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RPI3 GW poor RSSI on RFM69HW #1077
Comments
Could you compare the two versions when using the same output power? That would help us determine if the problem is caused by a difference in output power or a difference in code. |
The output power is set automatically by ATC, I'm just reading it from node side. |
ok. Thanks. |
I'll post some rfm69 logs as soon as I can |
Here are the logs with latest dev on GW and stable on node as it doesn't make much of a difference. |
Looks like there is noise/constant activity on the channel:
CSMA threshold is set to -95dBm (by default), i.e. RSSI above this value are considered as channel activity - you could try setting the threshold lower, e.g. to -85dBm and see if communication/retries improve:
|
mysgw: Starting gateway... that improved a little, but the node is still using 100% tx power |
here is node log 0 MCO:BGN:INIT NODE,CP=RPONA---,VER=2.3.0-alpha |
Node log with ATC FIX 0 MCO:BGN:INIT NODE,CP=RPONA---,VER=2.3.0-alpha |
Did you install the fix on both, node & GW? |
What fix ? |
please tell me where is this fix and how i can use it... ? |
Only on node. |
Ok but how use it this fix and whre i found it... |
It's for development purposes only, I'm testing with tekka to find out what is the problem |
Is there any update on this issue? I'm seeing the same problem using Rpi GW on 2.3.2. Poor TX RSSI (from node perspective) makes ATC unusable. @SimoneBnc Could you please share the fix you mentioned earlier? |
For me is still problem. Untill not fix i use MySensors 2.2.0 and it works ok. |
Same here, I'm still in 2.2 |
No looks good. Share new version with bug and share next versio also with bug... |
I confirm 2.2.0 works OK. Both RSSI on Rpi and ATC. |
Hi, was this issue ever solved? Running MySensor version 2.3.2-beta on a AVR 328p / RFM69CW node and a PI3 / RFMCW MQTT gateway I'm experiencing similar issues where the RSSI of messages received by the gateway remain very low (< -85dB) irrespective of the TX level of the node. Distance is only a few meters (< 5). |
Hi, I'm not sure I haven't checked it with 2.3.X. For production at my
house I'm still using 2.2.0 which works flawlessly for me in that matter.
Right now I'm busy working to get hoperf RFM73 working with mysensors (It's
a chinese 'clone' of the Nordic NRF24 but with some changes to it, anyway I
found it more convenient to use, especially that it's much smaller module
in size compared to Nordic nrf24...), which should work but it's currently
not.
--
Pozdrawiam,
Piotr Raczyński
wt., 16 kwi 2019 o 11:04 turboproc <notifications@github.com> napisał(a):
… Hi, was this issue ever solved? Running MySensor version 2.3.2-beta on a
AVR 328p / RFM69CW node and a PI3 / RFMCW MQTT gateway I'm experiencing
similar issues where the RSSI of messages received by the gateway remain
very low (< -85dB) irrespective of the TX level of the node. Distance is
only a few meters (< 5).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1077 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACXfx6w7IOsKQMRN1lPAF0GlqdD9g12vks5vhZIlgaJpZM4SbXJw>
.
|
OK, let me check how this works with version 2.2.0. If that works flawlessly at my place as well it's time to find the relevant difference between version 2.2.0 and 2.3.X. |
O dont know why developer not fing this bugs and not fix it for a long time. |
It is still beta for a reason I'd say 😀 |
Ok but official release 2.3.1 also has this bug. |
OK, did some trial and error and learned that release 2.2.0 works almost perfect, at least regarding this topic. So sticking for now on this release until I understand what can be gained with anything newer. |
I had same connection problems like you guys... With MySensors version 2.3.2, the GW and Nodes work okay for about have a day... the RSSI values ranging from -80 to -90, round about. Then I also switched to version 2.2.0. The RSSI values now read about -60. I hope this time the Nodes and GW operate reliably for much longer... |
I found the proximate cause for the low Rx RSSI value when radio RFM69 is connected over SPI to Raspberry Pi. To test this, I used the radio's AutoMode, to switch from Rx to StandBy with the rising edge of PayloadReady If you want to test this, you need to add In the I do not know what is the root cause of this delay, as I wrote here before finding this topic and investigating even more, it happened that my GW worked perfectly once, without any hardware or software modification. So if a fluke made it work, there has to be a root cause. |
@alexelite nice debugging! I checked this topic after my controller SW updates to see if this one got resolved. It seems that almost, do you mind submitting a pull request? |
fix mysensors#1077 Use radio auto standby mode to get correct RSSI value. Details mysensors#1077 (comment)
fix mysensors#1077 Use radio auto standby mode to get correct RSSI value. Details https://git.io/JXHrE
@piotrraczynski, did you get a chance to test the fix? For me it works very good. It is the most stable GW after testing multiple alternatives like serial, esp8266-mqtt, esp32-mqtt. |
Hi @alexelite, sorry not yet, let me check your fix locally, it seems that CI failed in your PR, but the results are gone? I asked tot rerun the checks itself. BTW. what did you use for getting RSSI chart like here? |
@piotrraczynski, CI failed because the length of one of the lines in the commit message was over the max stated in the rules. About the graphs, I modified the gateway software so for every message received it also publishes an RSSI value, over MQTT. |
Hi all, I've been having the same RSSI issue on my RPI gateway. I used the RFM69_new.cpp file you refer above in my gateway, but the RPI presented an error when I ran "make". Have you solved this problem using another file? Am I doing something wrong? Thank you for any advice. |
@oumuamua119, I did not change a thing in make. Can you post what error you got? The changes I made were very basic as I remember. It was more than 2 years ago when I submitted the pull request and maybe other things changed in mysensors. I use the same version as I did then. |
Hi @alexelite. Thanks for the response! I repeated the steps I made before and realized I downloaded the wrong file (I did wget on the permalink...). Basic mistake... I downloaded the right file and it is working perfectly. Thanks! |
I have tried compiling the development version on my RPI3 with a RFM69HW radio same as the node (pro mini 3.3v) but I am getting -90dbm RSSI on node with 100% tx power and a bunch of NACKs, while just compiling the stable version on the RPI3 makes the node reporting a -70dbm RSSI with 0% tx power. I also tried both stable and development version on node but the result is the same so it is something wrong on the GW side.
GW is compiled as follow: ./configure --my-transport=rfm69 --my-rfm69-frequency=433 --my-is-rfm69hw --my-gateway=ethernet --my-port=5003, I only added #define MY_RFM69_NETWORKID (27) to the mysgw.cpp
The text was updated successfully, but these errors were encountered: