Comments (5)
Actually.. none of the examples presented in the Arduino IDE from this library will compile:
Trying out GettingStarted, GettingStarted_CallResponse and a couple of others returns
"error: 'rf24_min' was not declared in this scope..
from rf24.
Thanks for mentioning this. Should have tested the change that caused this on Arduino, but it seemed so straightforward, and I didn't catch the error.
from rf24.
Excellent. Now we get to the 2nd error in the old examples:
led_remote.pde: In function 'void loop()':
led_remote:236: error: void value not ignored as it ought to be
read() now returns void and as far as I can tell, available() is now supposed to be used to test if we're done... I'm not profficient enough to rewrite the examples though..
Another thing.. I'd really like for the pin-connections to be clarified a bit more in the examples.. I am scratching my head as what RF24 radio(9,10) meant.. I did figure out that it probably meant which MISO/MOSI-pin on my device the radio was attached to, but there is no mention of where and how CE and CSN are configured (but apparently their pins are predefined to be 7 and 9 (in this library?)).
I could open another bug.. and I could also (when I finally get the communication to work) rewrite the descriptions of the newer examples to be more beginner-friendly.,
Cheers
/rené
from rf24.
Technically, users can choose any pins for the radio CE and CS pins. I chose 7 and 8 as the default, since pins 9 and 10 conflict with my audio libraries.
I don't understand your confusion, because the example literally says
// Hardware configuration: Set up nRF24L01 radio on SPI bus plus pins 7 & 8
RF24 radio(7,8);
I would argue that it is not the job of a low-level radio driver to teach users about SPI functionality. In any case, Google has pages and pages of information on using NRF24L01 modules, and there is tons of documentation about SPI, not to mention http://tmrh20.github.io/RF24/index.html
I am aware there are problems with some of the examples, but examples and documentation are last on my list of priorities. I thought it more pertinent to spend the hundreds of hours involved into fixing and testing the actual radio driver, and network library, instead of making things pretty.
I'm not sure why so many people are freaking out about the LED sketch right now, but no amount of emails or harrassment is going to make me change it right now, I'm busy.
BTW, the LED sketch was left in for historical purposes for users to reference. If anything I would just remove it entirely because I'm getting really sick of it. Feel free to contribute.
Pin assignments are not a software bug. If anything, feel free to update the documentation and/or examples if you feel it needs clarification.
from rf24.
facepalm.. on my part. of course those two numbers are the CE and CS-pins
and not SPI..
I came off sounding way less greatful than I really am. I do understand
that there are several generations of code and examples in this (great!)
library.. whenever I dive into a new library I always go to the examples
for ideas how the library works and when the examples don't work.. well..
frustration ensues..
I am guessing that these nRF24-modules recently came into a awareness of a
'new' generation of arduino and pi-users, which might be why you are
feeling 'bombed' suddenly.
Give me a few days and I'll see if I can't rewrite the LED-sketch.. it's a
great real-world example of how to use this (did I mention 'great'?)
library and submit it to you.
Best Regards
/rené
On 28 November 2014 at 07:59, TMRh20 [email protected] wrote:
Technically, users can choose any pins for the radio CE and CS pins. I
chose 7 and 8 as the default, since pins 9 and 10 conflict with my audio
libraries.I don't understand your confusion, because the example literally says
// Hardware configuration: Set up nRF24L01 radio on SPI bus plus pins 7 & 8
RF24 radio(7,8);I would argue that it is not the job of a low-level radio driver to teach
users about SPI functionality. In any case, Google has pages and pages of
information on using NRF24L01 modules, and there is tons of documentation
about SPI, not to mention http://tmrh20.github.io/RF24/index.htmlI am aware there are problems with some of the examples, but examples and
documentation are last on my list of priorities. I thought it more
pertinent to spend the hundreds of hours involved into fixing and testing
the actual radio driver, and network library, instead of making things
pretty.I'm not sure why so many people are freaking out about the LED sketch
right now, but no amount of emails or harrassment is going to make me
change it right now, I'm busy.BTW, the LED sketch was left in for historical purposes for users to
reference. If anything I would just remove it entirely because I'm getting
really sick of it. Feel free to contribute.Pin assignments are not a software bug. If anything, feel free to update
the documentation and/or examples if you feel it needs clarification.—
Reply to this email directly or view it on GitHub
#43 (comment).
from rf24.
Related Issues (20)
- 'make' errors, and RF24 on RPi, aarch64-linux-gnu HOT 18
- [Question] NRF24 Transmitter get "stuck" when powered from wall power outlet HOT 2
- RPi5 uses different gpio pin numbers (per Linux kernel update) HOT 48
- Radio.printDetails(); does nothing for MKR1010 but Radio.sprintfPrettyDetails(buffer); works fine???? HOT 4
- Pipe is sometimes returned at "255". HOT 15
- Is there a known ESP32 Deep Sleep issue with radio.powerDown()? [Question] HOT 19
- Can RF24 library be used with WiFi? HOT 2
- Can RF24 library be used with WiFi? HOT 4
- [Question] setChannel & setDataRate not read correctly by printPrettyDetails ? HOT 4
- ESP32 Core Panic on radio 0; No panic on Radio number 1, same wiring. How to troubleshoot?[Question] HOT 22
- Use Linux kernel's character device API to implement IRQ capability HOT 113
- [Question] R24.h, testRPD(void) "Strong signal > 64dBm" : "Weak signal < 64dBm" HOT 5
- [Question] Issue using the ManualAcknowledgements.ino HOT 11
- Multiple senders one receiver HOT 1
- reorganize examples HOT 5
- revise MRAA driver's GPIO
- Phasing out most Linux drivers HOT 1
- [Question] Address names used in examples problematic? HOT 8
- Library blocks 11 pin HOT 1
- Unable to use SPI1 on the raspberry pi pico HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rf24.