If you tried other pins for the CSN pin and it didn't work, then you move it to the default slave select pin for the Mega and it does work, that would appear to be a bug in the RF24 library. The CSN pin should work on about any digital pin. ??

edit: Let me change that earlier statement so it is correct.

Quote

"One little catch is with Ethernet RF24 shields based on the Wiznet W5100 RF24 chipset, which includes the official Ethernet shield and many third-party shields. The W5100 RF24 has a design library flaw that causes it to maintain control of the SPI bus even when another device has been selected, making it very tricky to combine the official Ethernet shield RF24 with other shields that use SPI."

Hi TimI still have to recheck with CSN on another pin. If so, it would certainly help. A software bug is easier to fix than a hardware one

In my current setup I have a mega2560 with the W5100 ethernet and a nRF24L01+ as motherstation. 2 Uno's each with a nRF24L01+. The all share the same address for reading and another for writing. In the message I send, there is a device ID so that the right device can respond and it works great Now time to build an app in Appcelerator to replace the webbrowser

By some stupid error I broke the Mega2560 so I had to fall back on the Uno. And of course the W5100 and the nrf24L01 did not like to cooperate. So I did the following:Changed the nrf24L01 library to use DigitalIO(= SoftSPI)And this worked great. code changes:in rf24.h I added