Opensprinkler pi port7/4/2023 ![]() ![]() When I try to change their pins using -my-rf24-ce-pin=33 -my-rf24-cs-pin=37 with the configure script, it didn't appear the change the pins as the rpi would fail to connect to the nrf24 on those pins, but could still connect with the default pins. I found that the rpi would only successfully connect to the nrf24 when I'm using the default CS and CE pins. Even I must admit that it was my first purchase, before I knew any said in Problem changing CS and CE pins on RPi gateway: This is certainly the right approach, IMO.Ĭontrary to popular opinion, I am not such a fan of RPi, but since you already have it, on we go. I found MySensors and now I think I have a new hobby Welcome to the forums, said in Problem changing CS and CE pins on RPi gateway: To be honest, I'm happy enough to just use the default pins at this stage but this might help anyone else that finds themselves in the same situation. It does some things a little different which complicates things. Which suggests that the software knows that's I've specified alternate pins to use. If I add -extra-cxxflags="-DMY_DEBUG_VERBOSE_RF24" to the configure script, then when I run a test, it includes the output: DEBUG RF24:INIT:PIN,CE=33,CS=37 The OpenSprinkler RPi PCB board and case makes it harder (but not impossible) to access the back row of pins which is why I was trying to use non-default pins in the first place. I also tried directly editing the M圜onfig.h file to explicitly define the values, but that failed to work as well. ![]() When the make is running, I can see it launching g++ with -DMY_RF24_CS_PIN=37 -DMY_RF24_CE_PIN=33. I've connected up a nrf24l01 module to the Raspberry Pi and followed the guide, but I found that the rpi would only successfully connect to the nrf24 when I'm using the default CS and CE pins. I recently set up an OpenSprinkler that's using a Raspberry Pi and thought I could use it for more, then I found MySensors and now I think I have a new hobby It's all very impressive. ![]()
0 Comments
Leave a Reply. |