There is a status register that will tell you a lot. Be
careful reading the data sheet. There is one, on my copy -
hard to see, footnote about a register which you have to
clear by writing ones to it. This is counter intuitive but I
know from much personal experience that writing zeros will
leave the register set to one.

Another word of caution. If you intend to use all the pipes,
beware, my Chinese product did not have all of the pipes
functioning.

I have some information posted here which may be useful:
http://libstock.mikroe.com/projects/view/992/nrf24l01-with-p
ic16f877a-and-no-libraries

http://forum.mikroe.com/viewtopic.php?f=3D88&t=3D59923

Allen

> -----Original Message-----
> From: piclist-bounces@mit.edu [mailto:piclist-
> bounces@mit.edu] On Behalf Of Anthony Toft
> Sent: Sunday, July 10, 2016 6:34 PM
> To: piclist@mit.edu
> Subject: [PIC] NRF24L01 with PC24FV32KA302 not working
>=20
> Ok folks, it's time to access the hive mind.
>=20
>=20
>=20
> I have a personal project that uses multiple PICS's and is
> going to use the
> NRF24L01 for its internal communication. The "master node"
> uses a PIC24 and
> handles communication from an ESP board and formulates a
> packet to send to
> the slave nodes. I have the network socket working well
> enough to trigger
> the breakpoints I'd expect, as well as outputting debug
data.
> The issue is
> with sending the data through the NRF pipe.
>=20
>=20
>=20
> I have a state machine that is driven by the SPI interrupt
that
> sends the
> various initialization commands that I have found
scattered
> all over the
> internet to the nrf chip. The state machine itself seems
to
> work, as far as
> it progresses though the various states to the READY
state. I
> have no clue
> as to whether the NRF is getting the commands. I then
> provide the state
> machine a packet to send, and it does not appear to do
> anything. At the
> moment I am working without a configured receiver and I
> would have expected
> the NRF to have asserted the maximum retry interrupt at
the
> very least, but
> this does not seem to happen.
>=20
>=20
>=20
> I don't know how to even start debugging this and any
clues
> would be most
> useful. I have been poking at it on and off for many
months,
> and am even
> currently thinking of swapping this idea out for a set of
ESP
> devices and
> talking directly to each slave node, although that would
> require some
> serious redesign work.
>=20
>=20
>=20
> Again, any ideas/thoughts on how to even start would be
> super helpful
>=20
>=20
>=20
> Thanks
>=20
>=20
>=20
> Anthony
>=20
>=20
>=20
> --
> http://www.piclist.com/techref/piclist PIC/SX FAQ & list
> archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist

--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.