-
Notifications
You must be signed in to change notification settings - Fork 31
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 test-details output #26
Comments
Seems like now you're just picking up some sort of periodic "ticking" signal instead of actual SPI signals. This always confuses me too, but I'm pretty sure all the pins node-nrf/pi-pins deals with are the GPIO numbers, not the actual header pin numbers. So when it says "CE GPIO: 24" but you have it connected to GPIO8, that is likely part of your problem. Also your CSN should probably be connected to (physical header) pin 24 which appears on some RasPi pinouts as "SP10 CE0 N". Please do not confuse this with the transceiver's CE, which is not the SPI select. You need to use one of the two dedicated SPI chip select pins for CSN, and use a GPIO port for CE. Once this is sorted, should get something that looks a lot more like the outputs logged on other tickets or similar to the Arduino library's printDetails call, e.g.
|
Here are the connections I've usually been starting with, btw: https://gist.github.com/natevw/5789019 |
Hey thanks for the connections! I was following this tutorial where CE and CSN were mixed up somehow. I now have Pi and Arduino talking to each other via RF24 but no luck with node-nrf. With node-nrf the Pi never reacts to the Aruino and vice versa. I'm not sure what I'm doing wrong ... do you have any sugestions or do you have a sample? (I did Node says this:
Doese FEATURE=0x7 matter? And the Arduino:
|
Still can't get it to work... I connected
And it works with RF24 with this config:
The correct node-nrf config is |
That's looking much better now! Pretty sure the ce=24/irq=25 version is what you need as well. Now perhaps the only thing, since you've been using the C++ library, maybe you just need to "unbreak" the kernel SPI stack as described here? #1 (comment) |
Yes, 24/25 were correct. I already did the modprobe thing. After doing this
on the Arduino (RF24) I can actually receive on the Pi and it responds (no errors). What I don't understand is that when I send from the Pi and receive on the Arduino I still get nothing. The Arduino receives the response when it pings so why doesn't it work the other way? |
Still the same issue but I enabled your debug switch. I'm using your test.js sample with this (instead of the CountStream):
And get:
Shouldn't I see W_TX_PAYLOAD? Also is |
|
I've uploded it here. I'd appreciate if you can take a look. I tested it with a new module, new cables, even disabled the irq pin ( Could it be the
It works with RF24 without problems. |
switched to a different solution, thanks. |
I've connected an NRF24L01 to an Raspberry Pi B+ (triple checked):
But
sudo node test-details.js /dev/spidev0.0 24 0
gives me this strange output:What's the expected output?
The text was updated successfully, but these errors were encountered: