Timeline for Transmit and receive data with nrf24l01
Current License: CC BY-SA 3.0
23 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jul 26, 2017 at 4:49 | history | edited | SkyFrotza | CC BY-SA 3.0 |
added 133 characters in body
|
Jul 26, 2017 at 4:42 | history | edited | SkyFrotza | CC BY-SA 3.0 |
added 551 characters in body
|
Jul 25, 2017 at 9:39 | vote | accept | SkyFrotza | ||
Jul 25, 2017 at 8:56 | comment | added | SkyFrotza | Let us continue this discussion in chat. | |
Jul 25, 2017 at 8:47 | comment | added | nickagian | Well, the fact that you read 0 from the STATUS register seems again odd. In my opinion you have a problem with the SPI communications. I'd advise you to start from the basics. Write a code where you just wait for your power-up time and then you read the CONFIG register. Don't over-complicate things. You don't need to write any register: The SPI communication should work even if the chip is in power down mode. Then debug your SPI code until you get 0x08 as a read value from this minimal code. As you seem to have an oscilloscope, I'd strongly advise you to use it during the process. | |
Jul 25, 2017 at 8:44 | history | edited | SkyFrotza | CC BY-SA 3.0 |
deleted 3 characters in body
|
Jul 25, 2017 at 8:28 | comment | added | SkyFrotza | @nickagian maybe you can read my update 2. I have added new code to read NRF24L01 STATUS register. I make pin CE in HIGH, and then Make my PWR_UP register HIGH too. After that, I update my STATUS register. I read again, but i always get x00 at statusNRF var and x07 at temp var. | |
Jul 25, 2017 at 8:24 | history | edited | SkyFrotza | CC BY-SA 3.0 |
added 762 characters in body
|
Jul 25, 2017 at 7:58 | comment | added | nickagian | As I said I'd use the CONFIG register right after boot and it should return 0x08. The 0x17 value for the FIFO_STATUS seems a bit odd. | |
Jul 25, 2017 at 7:57 | history | edited | SkyFrotza | CC BY-SA 3.0 |
added 2304 characters in body
|
Jul 25, 2017 at 7:56 | answer | added | nickagian | timeline score: 1 | |
Jul 25, 2017 at 7:34 | comment | added | SkyFrotza | @ChrisStratton I have finished to edit my question. If you still don't understand with my question, please reply this post immediately. Thank you. | |
Jul 25, 2017 at 7:32 | comment | added | SkyFrotza | @nickagian I have tested with read FIFO_STATUS (0x17, read at datasheet) register from nrf24l01 and it reply hex code 0x17. I think it's work. Perhaps, need some advice. | |
Jul 25, 2017 at 7:25 | comment | added | nickagian | How are you sure that your SPI communication works? Have you tried reading the configuration register after boot? It should give you a value of 0x08. And for a user to be notified about a direct mention to him, you should use the @ in front of the username in your comment. | |
Jul 25, 2017 at 7:08 | history | edited | SkyFrotza |
edited tags
|
|
Jul 25, 2017 at 6:08 | comment | added | SkyFrotza | to mr. Chriss Stratton, I have finished to edit my question. If you still don't understand with my question, please reply this post immediately. Thank you. | |
Jul 25, 2017 at 6:04 | history | edited | SkyFrotza | CC BY-SA 3.0 |
added 121 characters in body
|
Jul 25, 2017 at 5:59 | history | edited | SkyFrotza | CC BY-SA 3.0 |
added 121 characters in body
|
Jul 25, 2017 at 5:45 | history | edited | SkyFrotza | CC BY-SA 3.0 |
added 121 characters in body
|
Jul 25, 2017 at 5:32 | history | edited | SkyFrotza | CC BY-SA 3.0 |
added 10 characters in body
|
Jul 25, 2017 at 5:26 | comment | added | SkyFrotza | Thank you. I just forget to write my NRF24l01 pin that i used. | |
Jul 25, 2017 at 5:19 | comment | added | Chris Stratton | Your hardware configuration doesn't show the CE pin, but you're using a flow that seems to assume it is used and asserted appropriately. Start by verifying that you can read the receiver's status register. Then explain what is going on with the CE, and post your code and the actual connections. | |
Jul 25, 2017 at 5:07 | history | asked | SkyFrotza | CC BY-SA 3.0 |