!TSM:FPAR:FAIL node and gateway communication problems?

[gohan]

i got the new NRF24 modules and it looks they are working. it looks like they are clones but at least I am not getting errors on startup like the others. For reference on the chip the code is 1609AH

PS I did some tests on range with RF24_PA_MAX but I can get maximum 6-7 meters on same floor with 2 walls. Not as much as I would have expected.

[xelnaha]

@agtig said:

https://forum.mysensors.org/topic/5671/loosing-my-mind-sensor-not-talking-to-esp-gw-latest-2-2-0-beta/2

I have been pulling my hairs out too; whatever I did no joy. I also have the ones with the blob and i'm happy I got back here. Static node, no joy whatsoever. I am looking for the IC nodes now, just need to find a reputable seller as I thought I was buying the IC ones, but eventually was sent the blob cloned ones.

luckily i complained and said what I was sent was fake and got my money back.

[tboha]

Maybe you should give

#define MY_RF24_PA_LEVEL RF24_PA_MIN

a try.
Being short of NRF modules, I ordered 10 pcs from my trusted EBAY-Seller for about 6.5€. What a disappointing experience - none of the modules did its work. All failed with

!TSM:FPAR:NO REPLY

10 defective modules in a row? Not likely. Clones? "Second source"? Fake? - maybe. So back to the roots, digging out maniacbug's library, uploading test sketches (pingpair_ack) - and ... no communication.
Regarding debug output the only difference between working and dysfunctional modules was PA_LEVEL (PA_LOW vs. PA_MAX). So switching to PA_MIN resulted in almost flawless communication arround 5-7m (inhouse with much armoured concrete, not noticeably different from "working" NRF modules).
Reducing PA_LEVEL is advised frequently in this forum, but I never thought of reducing to PA_MIN.
Interesting observation: increasing PA_LEVEL from PA_MIN to PA_LOW resulted in way much higher Round-Trip-Times (6000µs vs 650µs) and some failures (indicating bad transmissions), increasing to PA_LEVEL to PA_HIGH broke communication completely.

So recompiling Mysensors sketches with RF24_PA_MIN did the trick, the probably "fake" modules are doing their job.

[gohan]

I barely make it to the next room whatever power level I choose: I don't know if it is related to the voltage regulator with AMS1117 chip but I get a good communication until a certain point but as soon as I get behind a second wall, the gateway stops receiving even with 250k transfer rate. On my next order I'll get a couple of NRF24 chips with PA and antenna and see if it gets (hopefully) any better, if not I'll probably make the dipole antenna mod on the chips as I'd like to use them for longer range. If any of that will not work the only left solution is to use the Network libraries for the NRF24.

[Tigroenot]

I experience a very strange behavior of couple of sensors. They don't find parent if no repeater nodes are present. As soon as I power on a repeater node they work fine. Why don't they get gateway as parent node? I tried to manually assign parent but no luck. I also tried to change their parent id through the myscontroller. They don't obey :)
What did I miss?

[gohan]

I never configured a parent Id...

[Reza]

hi all friends. i have same problem . i test all state of software and hard ware.
for software:
use static ID
use static parent
change channel for gateway and nodes
use all state of pa_level (min - low - high - max) for nodes and gateway.
for hardware:
use 3 type of radio with/without antena (2chip and 1chip)
use 4.7 - 100 - 470 uF capacitor
use radio adapter and reglator module (5 to 3.3)
use power supply 2A - 10A

but not useful. . .

[gohan]

Pls write what is your hw setup and how you connected everything, because there could be either a sw issue (like old libraries) or some errors in wiring. Also post logs of gateway and node

[Reza]

@gohan
i have a raspberry pi gateway and domoticz controller. and some fixed nodes in some rooms. wiring , sketch (softeware and hardware) is similar to simple sketch in site.
just i added some feature similar to static node id , repeater feature and etc. the important issue is : i used this sketchs and devices (before update library and update sketch of nodes and gateway) without any problem . also use a node in 15 meter distance with gateway and there was 3 thick wall !and worked well, but after update the communication is very weak also for 5 meter with a 10cm wall i have very error similar to : FPAR FAIL - NACK - NO REPLAY - PDT . . . . i sure this is related to new version of library because i test all way for this problem

[gohan]

@Reza
I believe there is a specific discussion about the new library version, maybe you could ask there since the previous version was running fine. To get thing back to work you could restore the library you used before and recompile everything again.

[Reza]

@gohan
Previous Library didn't had "static parent feature"
this feature add in new lib. and i think after add this issue , start problem.
now for near distance between nodes and gateway dont have problem . but for more than 5 meter there is problems.
i think this problem ( most of lastest topics is related to this errors and problems) is related to library.
perhaps @hek know more about this. so if he confirm , i open a new topic and report my exprience....

[gohan]

I'm not using that Static Parent, I left as default so it goes to AUTO in the MyConfig.h but at the moment I'm not using any repeater yet