Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strange behaviour #3

Open
fcaeiro opened this issue Jan 28, 2012 · 5 comments
Open

Strange behaviour #3

fcaeiro opened this issue Jan 28, 2012 · 5 comments

Comments

@fcaeiro
Copy link

fcaeiro commented Jan 28, 2012

Hi there maniacbug
i had made a mistake changing your library that i download 20/12/11 and today i downloaded the current one...
With the new version, my sensors start to act strange....

I did some testing using your sensor net example and ...

One arduino in nodeadress 0 (base) and other that i manually change the address i found that only the address 1 and 3 have success to send to base...

2,4,5 fails what happen ? how can troubleshoot more this i'm not getting why is not working ?

Regards.

this is my base:


RF24Network/examples/sensornet/
VERSION: Unknown
ADDRESS: 0
setup_address node=00 mask=00 parent=00 pipe=00
119: NET Pipe 5 on node 00 has address f0f0f0f0c3
173: NET Pipe 4 on node 00 has address f0f0f0f0a5
226: NET Pipe 3 on node 00 has address f0f0f0f096
278: NET Pipe 2 on node 00 has address f0f0f0f069
331: NET Pipe 1 on node 00 has address f0f0f0f05a
385: NET Pipe 0 on node 00 has address f0f0f0f03c
STATUS = 0x0e RX_DR=0 TX_DS=0 MAX_RT=0 RX_P_NO=7 TX_FULL=0
RX_ADDR_P0-1 = 0xf0f0f0f03c 0xf0f0f0f05a
RX_ADDR_P2-5 = 0x69 0x96 0xa5 0xc3
TX_ADDR = 0xf0f0f0f096
RX_PW_P0-6 = 0x20 0x20 0x20 0x20 0x20 0x20
EN_AA = 0x3f
EN_RXADDR = 0x0b
RF_CH = 0x5c
RF_SETUP = 0x27
CONFIG = 0x0f
DYNPD/FEATURE = 0x00 0x00
Data Rate = 250KBPS
Model = nRF24L01+
CRC Length = 16 bits
PA Power = PA_HIGH


This is my sender:

VERSION: Unknown
ADDRESS: 2
setup_address node=02 mask=07 parent=00 pipe=02
119: NET Pipe 5 on node 02 has address f0f0f0d2c3
173: NET Pipe 4 on node 02 has address f0f0f0d2a5
226: NET Pipe 3 on node 02 has address f0f0f0d296
278: NET Pipe 2 on node 02 has address f0f0f0d269
331: NET Pipe 1 on node 02 has address f0f0f0d25a
385: NET Pipe 0 on node 02 has address f0f0f0d23c
STATUS = 0x0e RX_DR=0 TX_DS=0 MAX_RT=0 RX_P_NO=7 TX_FULL=0
RX_ADDR_P0-1

sending: Hello, world!
935: NET Sending id 0001 from 02 to 00 type
984: NET message 6548
1007: MAC Sending to 00 via 00 on pipe 2
1051: NET Pipe 2 on node 00 has address f0f0f0f069
1330: MAC Sent on f0f0f069 failed
1364: APP Send failed


if i keep all other things === and only change the adress of the sender to 1 or 3 i have sucess sending


sending: Hello, world!
935: NET Sending id 0001 from 03 to 00 type
984: NET message 6548
1007: MAC Sending to 00 via 00 on pipe 3
1051: NET Pipe 3 on node 00 has address f0f0f0f096
1107: MAC Sent on f0f0f096 ok

1138: APP Send ok

@fcaeiro
Copy link
Author

fcaeiro commented Jan 28, 2012

Confirmed i found my old download from 20-12 replaced in my arduino libraries and now all address from 1 to 5 are working..
Some kind of bug in this new version...

@maniacbug
Copy link
Owner

Thanks for reporting. Very strange. I did make a bunch of changes recently, so I will have to try this out.

@basilfx
Copy link

basilfx commented Feb 21, 2012

I might have a similar issue. When using the Meshping example and hardcoded node addresses, only the following setup works (all nodes communicate):

1st node: address 0
2nd node: address 01
3th node: address 011

but not:

1st node: address 0
2nd node: address 01
3th node: address 021 or 012 (which should work http://arduino.cc/forum/index.php/topic,84135.msg631713.html#msg631713 - read the notice about the diagram)

or

1st node: address 0
2nd node: address 01
3th node: address 02

Somehow I think that when it involves pipe 2-6, it does not work anymore. However, in all situations above, the 1st node is able to communicate with the 2nd node.

I have tried to slow down the speed and decreased the transmit power because for testing, all nodes are very close to each other. However, it did not help. I reset the nodes after programming.

@maniacbug
Copy link
Owner

@basilfx found it, and submitted a patch at maniacbug/RF24#5 . This totally makes sense. Will merge it as soon as I can.

@maniacbug
Copy link
Owner

The fix has been applied to RF24, maniacbug/RF24@2c97186 . I suspect this would fix this issue, but have not yet tested it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants