@mfalkvidd thanks! I'll try with RFM69_RETRIES=1 and handle retris from sketch. The reason I'd like to see what is my retry count is that I'd like to see how the nodes perform in a longer period of time. for short time I see that the power is fluctuating so I wanted to see how many retries on average do I have for a given target_rssi (-70 is the default). I was wondering how much lower can I get to still have reliable link quality.
@mfalkvidd, AFAIK B+ version of Raspberry Pi can provide up to 500mA on 3.3V rail (they replaced linear 3.3V regulator to a switching one), see https://pinout.xyz/pinout/pin1_3v3_power
Anyway I tried external 3v3 anyway a minute ago. Unfortunately my results are the same...
@mfalkvidd thanks! I'll try with RFM69_RETRIES=1 and handle retris from sketch. The reason I'd like to see what is my retry count is that I'd like to see how the nodes perform in a longer period of time. for short time I see that the power is fluctuating so I wanted to see how many retries on average do I have for a given target_rssi (-70 is the default). I was wondering how much lower can I get to still have reliable link quality.
Hi
Is there a way to pull send retries statistics and present in my controller of choice (openhab in my case)?
I have several battery nodes (rfm69) with ATC enabled. I'm trying to fine tune target RSSI for ATC to optimize battery life. Is there a way to get to either total or average number of retries ?
Was there any follow up to this issue?
I can confirm that ATC does not work using Rpi gateway. Well, it kind of works when you set very low MY_RFM69_ATC_TARGET_RSSI_DBM. I tried -100dBm and then the node is finally decreasing TX power to -2dbm. Anyway, when using Rpi as a gateway I can see (from node perspective) very low (-90) TX RSSI, whereas the same parameter is -26 when using arduino serial gateway (with the same close distance between node and the gateway).
Since the TX RSSI is very low, then the ATC works only when you set your target to lower than that, like mine -100 setting for test purposes.
@gohan I tried 2.2 and it gives far better results! Thanks. Is there an issue filed already in the database? Have anyone tried to bissect it or already know what is the root cause?
Tnanks, however
@alexsh1 tried 1. already, works the same and I have MY_IS_RFM69HW from the very beginning
@mfalkvidd I've used --my-is-rfm69hw for configure.
My last chance is to attach another RFM69 directly to the goldpins since I use custom PCB now with LCD and other stuff. Maybe I messed something in the design.
@mfalkvidd, AFAIK B+ version of Raspberry Pi can provide up to 500mA on 3.3V rail (they replaced linear 3.3V regulator to a switching one), see https://pinout.xyz/pinout/pin1_3v3_power
Anyway I tried external 3v3 anyway a minute ago. Unfortunately my results are the same...
Hi,
I've built Ethernet gateway on RPi with RFM69HCW. When node connects to the gateway I experience very poor range 1-2m tops. RSSI value read on the node gives me -99~-109 values. I use 3v3 rail from RPI and have 220uF capacitor between RFM vcc and gnd.
However when I use the very same node with arduino flashed with serial gateway, I get -29~-37 RSSI with the same distance.
I tried to replace RFM connected to the RPI but results are the same (very poor range and RSSI values).
Did anyone experience poor range with RPI as gateway with RFM69?