@sundberg84 , sorry, I meant I did not burn the bootloader and was not aware of that.

Did you mean "reset capacitator", not resistor?

And on that note, am I right that reset to iscp should go to DTS contact?

thanks for help.

@sundberg84 said in In Wall AC/DC Pcb (with Relay) for MySensors (SMD):

header?

No, I did not. I used to work with arduinos, so this is the first time I bought and try mega328p. could you advise where to find a resource with step-by-step instructions on that?

hi, I get constantly messages Arduino: 1.8.5 (Linux), Board: "Arduino Pro or Pro Mini, ATmega328P (5V, 16 MHz)"
avrdude: stk500_getsync() attempt 7 of 10: not in sync: resp=0xde
avrdude: stk500_getsync() attempt 8 of 10: not in sync: resp=0x4c
avrdude: stk500_getsync() attempt 9 of 10: not in sync: resp=0x9d
avrdude: stk500_getsync() attempt 10 of 10: not in sync: resp=0xaa

is this hardware problem? I select Arduino Pro Mini board setting with AVRISP mkII programmer. are these ok?

@annujbhatia , did you manage to connect it right? I have the same challenge as I have 9 zones.

https://www.arduino.cc/en/Tutorial/ShiftOut should be the guidance I suppose

@mfalkvidd ,

I guess I am talking about software ACK's (though not sure).

But, as @itbeyond advised, I downgraded to 2.2.0, recompiled and problems dissapeared. Log is clean, NACK's no more.

@yveaux said in nrf24 : transmission of data works fine, but constant NACK's produced:

e

I kind of do not quite understand why it can be that transmission is reliable in my case within 25-30 metres distance (node and GW communicate reliably), but NACK's appear when distance is over 5-6 metres?

@mfalkvidd ,

I have no repeaters. I tried to experiment to answer your questions. I went to the ~15 meters distance where GW shows peristent NACK's.

I understand the normal scenario is, that node send a message, GW receives the message, GW send ACK to node, node receives ACK from gateway. it should be the end of transaction?

GATEWAY LOG ENTRIES:

0;255;3;0;9;477668 TSF:MSG:READ,250-250-0,s=0,c=1,t=48,pt=3,l=2,sg=0:225
0;255;3;0;9;477674 TSF:MSG:ACK REQ
0;255;3;0;9;477713 !TSF:MSG:SEND,0-0-250-250,s=0,c=1,t=48,pt=3,l=2,sg=0,ft=0,st=NACK:225
250;0;1;0;48;225
0;255;3;0;9;478752 TSF:MSG:READ,250-250-0,s=0,c=1,t=48,pt=3,l=2,sg=0:226
0;255;3;0;9;478758 TSF:MSG:ACK REQ
0;255;3;0;9;478797 !TSF:MSG:SEND,0-0-250-250,s=0,c=1,t=48,pt=3,l=2,sg=0,ft=0,st=NACK:226
250;0;1;0;48;226
Channel:76 PaLevel:MAX DataRate:250KBPS
0;255;3;0;9;480967 TSF:MSG:READ,250-250-0,s=0,c=1,t=48,pt=3,l=2,sg=0:228
0;255;3;0;9;480973 TSF:MSG:ACK REQ
0;255;3;0;9;481013 !TSF:MSG:SEND,0-0-250-250,s=0,c=1,t=48,pt=3,l=2,sg=0,ft=0,st=NACK:228
250;0;1;0;48;228

This is what a node shows for the same transmissions:

LOG FROM NODE
124526 TSF:MSG:SEND,250-250-0-0,s=0,c=1,t=48,pt=3,l=2,sg=0,ft=0,st=OK:225
124533 TSF:MSG:READ,0-0-250,s=0,c=1,t=48,pt=3,l=2,sg=0:225
124538 TSF:MSG:ACK
125067 TSF:MSG:SEND,250-250-0-0,s=0,c=1,t=48,pt=3,l=2,sg=0,ft=0,st=OK:226
125074 TSF:MSG:READ,0-0-250,s=0,c=1,t=48,pt=3,l=2,sg=0:226
125079 TSF:MSG:ACK
125625 !TSF:MSG:SEND,250-250-0-0,s=0,c=1,t=48,pt=3,l=2,sg=0,ft=0,st=NACK:227
126171 TSF:MSG:SEND,250-250-0-0,s=0,c=1,t=48,pt=3,l=2,sg=0,ft=1,st=OK:228
126179 TSF:MSG:READ,0-0-250,s=0,c=1,t=48,pt=3,l=2,sg=0:228
126184 TSF:MSG:ACK

message "226" - a node sent message, GW received it, GW sent ACK and node received ACK. Why GW entry shows NACK? What I am missing?

When we look at node entry "227", a node sent a message, GW did not receive it (there is no entry in GW log), so node did not receive the ACK from GW. this all makes sense.

Hi all,

I use arduinoUno as serial gateway, nrf24 for radios.

I find this strange, that overall reliable data transmission distance is probably ~30 meters, through the walls. so mysensors reliably send data to GW and actuators receive commands.

But I can not use ACK required feature, as in the logs I see systematically NACK's. for troubleshooting I used nrf24doctor sketches ( https://forum.mysensors.org/topic/9178/nrf24doctor )

So what I find is:

When I am at ~7m range, I nrf24doctor node shows no faults and gateway produces all nice log entries like this:

250;0;1;0;48;17
0;255;3;0;9;227401 TSF:MSG:READ,250-250-0,s=0,c=1,t=48,pt=3,l=2,sg=0:18
0;255;3;0;9;227408 TSF:MSG:ACK REQ
0;255;3;0;9;227418 TSF:MSG:SEND,0-0-250-250,s=0,c=1,t=48,pt=3,l=2,sg=0,ft=0,st=OK:18

But when distance increases by one-two meters, mesages are received, but the log on the GW consistently shows NACK's:
250;0;1;0;48;322
0;255;3;0;9;558810 TSF:MSG:READ,250-250-0,s=0,c=1,t=48,pt=3,l=2,sg=0:323
0;255;3;0;9;558817 TSF:MSG:ACK REQ
0;255;3;0;9;558856 !TSF:MSG:SEND,0-0-250-250,s=0,c=1,t=48,pt=3,l=2,sg=0,ft=0,st=NACK:323

The same pattern stays when we increase distance further, - messages are received (within ~25-30 meters distance I find 1-2% of faults, but 99% messages go through).

So do I understand this right, that my node manages to deliver to gateway the message with payload, but fails to deliver the ACK? What could be explanation behind?

@Technovation , thanks for diagnostics tool. Could you help to interpret the results what I get?

When I am at ~7m range, I nrf24doctor node shows no faults and gateway produces all nice log:

250;0;1;0;48;17
0;255;3;0;9;227401 TSF:MSG:READ,250-250-0,s=0,c=1,t=48,pt=3,l=2,sg=0:18
0;255;3;0;9;227408 TSF:MSG:ACK REQ
0;255;3;0;9;227418 TSF:MSG:SEND,0-0-250-250,s=0,c=1,t=48,pt=3,l=2,sg=0,ft=0,st=OK:18

When distance increases, nrf24doctor node shows 1-2 percent of faults, but the log on the gateway consistently shows NACK's:

250;0;1;0;48;322
0;255;3;0;9;558810 TSF:MSG:READ,250-250-0,s=0,c=1,t=48,pt=3,l=2,sg=0:323
0;255;3;0;9;558817 TSF:MSG:ACK REQ
0;255;3;0;9;558856 !TSF:MSG:SEND,0-0-250-250,s=0,c=1,t=48,pt=3,l=2,sg=0,ft=0,st=NACK:323

So do I read it right way, that my node manages to deliver to gateway the message with payload, but fails to deliver the ACK?

How that works? How do I understand results like this?

thanks,

Where to find a sketch with temperature read?