Hard to say. St:fail generally means that you don't get ack from the receiver. This is normally range, power or hardware. There is not a general fix for this but you need to try and learn... i admit its strange I worked for some days. Maybe a radio fried ?
Don't have the radios to close to eachother. Try a.couple of meters.
Sorry I'm out of more solid ideas.
Hey sundberg84, quick question for you.
If you look at my debug logs above it looks like the gateway is infact receiving the message but the node thinks it fails. Con you confirm my interpretation of the following two lines?
send: 42-42-0-0 s=1,c=1,t=0,pt=7,l=5,sg=0,st=fail:20.0
0;255;3;0;9;read: 42-42-0 s=1,c=1,t=0,pt=7,l=5,sg=0:20.0
If that's correct, could that change what the issue might be?
Yes, I saw that - it seems to work one way but the ack (return) does not reach back. So its on the edge.
But this should update the value in your controller.
Thanks. Will update these.
Problem is I need to do fussy search using keywords. And the sellers tries to get as many matches as possible (they add a lot of keywords thats not even describe their product). The ali-database is updated constantly. Gah.
@mfalkvidd said in NRF51-52 PA not support ???:
the return value of send() indicates whether the sending node received an acknowledgement from the next node. If the next node (the gateway unless you have repeaters) received the message and send() still returns false, it usually means that the acknowledgement was lost.
Maybe the PA makes it possible for the sending node to reach the gateway, but the gateway is unable to reach the sending node?
The network is simple, this node is nrf52 with an amplifier and a gateway with the nrf24 radio module with an amplifier. It would be strange if a gateway with an amplifier could not deliver ACK. Two moments, or I did a very bad control of the amplifier on the node nRF52 or in the radio driver itself, something is not working well, and may need some delay settings. If i send messages with an ECHO (soft ack) request, this works fine over very long distances. Hw ack does not work properly.
@Yveaux I also add the delay to not ddos the gateway. When I did the MySensors workshop, 20 people started to connect to the gateway almost at the same time. And they got Funky messages. Since then I do a delay. But it would probably be better to add a random time to the delay. Something like 20ms + random( 0 - 30 ) ms. That way you don't get the ddos effect. Sonoff had the same problems with their solution a couple of years ago, when the servers went down. All Sonoff devices tried to reconnect almost the at the same time. Which caused a ddos xd