Comments: RFM69HCW Hookup Guide

Pages

Comments 5 comments

  • “Be sure that you’re powering your Arduino with a “Beefy 3” FTDI board, a wall-wart, or a Lipo battery.”

    Please forgive my ignorance, does this mean you can use: a “Beefy 3” FTDI board or a wall-wart, or a Lipo battery, Or does it mean a “Beefy 3” FTDI board with, a wall-wart, or a Lipo battery?

    Thank you

    • Sorry for the confusion (and Oxford comma); you can power your project with any of those options. The main takeaway was that a normal (not Beefy) FTDI board can’t provide enough power to run the RFM69, so use something else (or in addition to that).

  • Not really experienced with Arduino and even less so with github. I installed the most recent version of the Arduino IDE last night. I can’t say I have if problem with the hardware, because I can’t get the code to compile. I downloaded, the library .zip file then used the Arduino IDE, Libraries >Manage >add .zip file to install it. I then loaded the Examples > node file into the Arduino IDE. It wouldn’t compile. I getting library file errors on the spi flash .lib file. I then used the “copy code ” button to copy the code directly from the tutorial and got the same errors. I pretty sure it’s something I’m buggering up but cant find it. I’ll post the actual error comments later today, since I’m not at that machine now. Thanks for the sanity check.

  • Could this be used to make a wireless USB connection, by plugging one of the arduino/RFM69HCW packages to a computer, and the other to a phone or printer? And then sending the data out the USB as you normally would (ie. just hitting print).

    • If your USB application uses a COM (serial) port, then yes, this can be done. The example code we use in this Hookup Guide is very close to what you’d need (when you type characters in one end, they come out the other). You’ll just have to come up with a way to pass carriage returns (which we’re using as a signal to send a packet but not actually transmitting), and delete the code that prints out extra diagnostic information.


If you've found a bug or have other constructive feedback for our tutorial authors, please send us your feedback!