st:fail sometimes and sometimes OK

[rvendrame]

@flopp said:

sorry for asking so much
after each gw.send?

Yes

[flopp]

@rvendrame said:

@flopp said:

sorry for asking so much
after each gw.send?

Yes

Thanks

[flopp]

It have now been running for 35 minutes without any error, 100uF on both NRF. Delay(100); after each gw.send. Will try later to remove that and see it the problem was the caps.

Thanks everyone 👊

[flopp]

During I wrote above reply it reported 3 fails!!!
I hope that was just a glitch and will let it run without any changes

[sundberg84]

What do you power the nodes with? Since it seems to work better with caps on, there might be something to your power or wiring you can do to make it better.

[flopp]

@sundberg84 said:

What do you power the nodes with? Since it seems to work better with caps on, there might be something to your power or wiring you can do to make it better.

I wrote it in first post, no hard feelings

sensor, lipo batt
gateway, usb from PC

[sundberg84]

Sorry m8. My thought was that depending how you run power and ground in your ciriut it can disturb the radio. For example i had a 5v arduino with a 5v relay and if i didn run the ground through the arduino but instead direct to ground the radio got to many spikes and i got really much st:fails.

[flopp]

@sundberg84

no worries, I done it my self my times.

Right now I think the problem was a loose cap or bad/small cap. Before I used a 4.7uF, no I have one 100uF on each NRF.

[sundberg84]

Yea, thats kind of interesting... i have 25+ nodes and everyone except the gateway runs on 4.7 only and it works great... but if that works for you im glad!

[Marcell Kovacs]

@rvendrame said:

Once I had similar problems, a 4.7nF cap and gw.wait(100) after each transmit did the trick for me... Hope it helps somehow.

I also got to this solution when experienced the same 'st:fail' issue. The arduino's delay wont help, because it wont receive anything from radio during the delay.

As i got mutch less or no error with ack = false, I thing its linked to receiving some ACK packets. I have no deeper information or debugging possibilities at the moment.