It was very hard to even know what is really going on with it, I finally gave up. I played around with DietPi once a little bit (if that is what I am thinking of), what a mess with all their custom stuff going on. You could also help the project out tremendously by lodging an issue over at the GitHub, which is probably more likely to get addressed (sooner or later) than posting here in forums, where possibly it could get said in Problem changing CS and CE pins on RPi gateway:Īs you are just beginning to figure out (perhaps) this is only one aspect of the problems with RPi. Furthermore as mentioned, I eschew RPi (for lots of reasons). If I add -extra-cxxflags="-DMY_DEBUG_VERBOSE_RF24" to the configure script, then when I run a test, it includes the output:Īs to particulars of this issue, hopefully one of devs familiar with that part of code (build scripts for RPi?) stops by. When the make is running, I can see it launching g++ with -DMY_RF24_CS_PIN=37 -DMY_RF24_CE_PIN=33. 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. 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. The OSPi v3.0 kit includes the enclosure (with a clear acrylic window), assembled and tested OSPi circuit board and terminal blocks. To get started, you will also need the following, which are NOT included in. Small flathead screwdriver, Phillips head screwdriver, and needle nose electronics plier OpenSprinkler Pi (OSPi) v1.4+ User Manual (Updated May 31, 2015) Contents. Tapered machine screws to attach back to front of OpenSprinkler housing (screw head must fit into OSPi slot)Ĩx 8 inch solid wire (same gauge as Rainbird wire) Rainbird irrigation system with 7 zones and 24V AC sprinkler valves (OSPi can handle more zones with additional parts) Micro USB to USB cable 3ft from Amazon $5.49 Orbit Water Conservation Sprinkler System Rain/Freeze Sensor, Amazon $30.11 SanDisk Ultra 16GB Ultra Micro SDHC UHS-I/Class 10 Card with Adapter (SDSQUNC-016G-GN6MA) from Amazon $6.60 OpenSprinkler OS3.0 AC-powered (including 24VAC power adapter, US) $166.00 A case and power supply for the Raspberry are not needed. The parts below seem to work best for me. In another Raspberry Pi project, I measured, tested and experimented with various kits and components.
0 Comments
Leave a Reply. |