DOG REPELLENT

I got these yesterday and a few hours later I had two Uno's talking to each other. I tried a few libraries and found that the "RF24" library from maniacbug.github.io/RF24/This library seemed better than the MIRF library in the quick look that I took at each. My project will use 5 of these to communicate with one central/master unit. Communication will be directional.I have not yet tested the range on these. I hope to use them about 50 ft from each other (unobstructed). If I experience range issues I'll come back and post an update here. If you're thinking about going wireless and don't require 802.11b/g/n then give this a shot. It is cheap and works well!Update: 9/10/13I've had a chance to connect 3 of these and have them send/receive data and it worked reliably. I moved the units all over the house to see if I noted a change and I got the data with out missing a beat. I didn't test if there was a change in data rate but I didn't notice any issues.Update: 10/2/13I took a pair of these outside, connected to Arduino's. They were mounted in plastic project boxes and I tested the range. Unobstructed range was 50 feet. After that the signal dropped off and I got no reply. In the house I tested on different floors of the house and went from the basement to the 2nd floor and they were able to communicate with out an issue.

[Third Review]I've updated the defective driver library for the MCP2210 with the latest version from Microchip and now..., EUREKA!! It works really fast!!![Second Review]I've created my own protocol stack (Three Layers - PTX size/Two Layers PRX size) over the nRF24L01 to allow chunked/bidirectional link between my laptop and a pcDuino V2. It works!On the PTX side I constantly send packets (user/NOOP commands) to the PRX. Packets have a protocol header that allow the PRX to assemble back multi-packet transmissions. Completed packets are decoded and executed and the raw result (byte data) is placed in a response queue.The PRX writes response packets in the TX pipes sent back in the ACK phase, then decoded and executed the same way on the PTX side.The process works but after a while the whole process slows down (PTX side which uses the MCP2210). If I stop the program and start over, it starts to work fast showing the same behavior after a while.No memory leaks allowed since PTX side is a C# program and the GC handles allocation/deallocation by itself (steady memory + cpu behavior seen in the task manager). The PRX side has been built in C/C++ running in Ubuntu and compiled with g++ using smart pointers and the STL library.It seems like the MCP2210 USB library is the guilty of this misbehavior! PRX side always works fast which uses the raw SPI bus to communicate the nRF24L01.[First Review]I love this product since now I can establish a wireless bidirectional link between my laptop and the MCUs! The documentation is pretty clear and understandable to make your own driver! It does require some time to digest!It supports STAR configurations, maximum six transmitters/one receiver. Bidirectional link is also available by packing data back to the transmitter in the ACK packet using Auto Acknowledgement and pipe address. Protocol can be dynamic or static in packet size. Enhanced Shock Burst guarantees express packet delivery without MCU intervention or notification in case of MAX_RT IRQ.

For me using the ICSP headers has been daunting, These have amazing reviews online and have great range once you get them working, But DONT WASTE YOUR TIME WITHOUT FEMALE HEADER JUMPERS! I spent hours and hours using makeshift jumpers that looked like they were creating a good connection, only to find out that even though I had a good idea, It wasn't, a good....idea.....OK So, With the CORRECT female jumpers, There are several Libraries for these, with lots of forum support, They have awesome range and can be used for an AMAZING amount of projects, Like: RC cars/trucks, QuadCopters, RC transmitters, WiFi, Connecting Arduino/Rasberry Pi. Networking. Iv heard rumours of Bluetooth connectivity with these guys. Swarming Drones have been made with a collection of these.If you can think it, I am pretty sure you can do it with these.SO save yourself a headache and get some jumpers and HAVE FUN!

I built several temperature, humidity and light sensors following the plans on MySensors.org, so I needed some nRF24L01+ transceivers. I bought a bunch from another vender on that big online flea market that starts with an eB. They worked on some of the units, but wouldn't work on others. I wasted literally days of troubleshooting before deciding to try a different source for the transceivers.I bought two of these Addicore branded units, and they worked in ALL cases. I've since bought several more, and they too work every time.The first ones I bought were considerably less expensive, but when you factor in all the days of wasted time and frustration, these turn out to be Drastically more cost effective.By the way, if you need wireless sensors, and like to build, the MySensors project is a good way to go.

These are a super-cheap way of getting your Arduinos talking to each other wirelessly. That said, a few caveats:- I had some problems using these with a RedBoard (knock-off Uno). Adding a decoupling capacitor (i.e. soldering a 100uF cap across the power and ground leads) fixed the issue.- The chips require a 3v power supply. Some other nRF24 chips come with a 5v to 3v regulator, but they're also more expensive. That said, the data inputs are 5v compatible, so you can use the 3v output of the Arduino for the Vcc input and hook the data pins up to the Arduino directly.- I'm still having some problems with dropped packets when I try to transmit without a delay. This makes it difficult to realize anything close to the 2Mbps bandwidth. I can send at most about 200 packets per second, and at 32 bytes per packet this gives about 50Kbps.