-
Notifications
You must be signed in to change notification settings - Fork 240
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
Phantom device (change BROADCAST ID) #40
Comments
@thomsna if I read the code correctly, address 124 is the broadcast. In your teat, try counting how many acks you get and from what addresses to confirm. |
@aperepel Thanks for clearing that up. 124 is indeed the broadcast address. |
Great, this is not an issue, it looks. I would maybe prefer to have the broadcast on a more 'classic' address like 0 or 255, than in a middle of the range. @gioblu any comment on that? 124 doesn't even look cool in binary :) |
+1 for setting broadcast address to 0, like I2C. |
Hi @aperepel @thomsna to be consistent and not subjected to versioning changes (as the one you are proposing) bugs, always use constants if you can: Could be more clean I agree, we should run extended tests, but if all is ok, I don't see limits in changing |
Two Arduino pro mini ATmega328.
A master set at address 45 and a slave set at 44.
Bus on pin 12.
While sending to device 124 even though it didn't exist on the network, I get ACK values back.
Can someone reproduce this?
Here, I wrote a script to check for a response on all addresses.
Code for master:
Code for slave:
The text was updated successfully, but these errors were encountered: