This is good to know, thank you. I changed the code accordingly.
Yikes, I must be getting confused between radio libraries. Correct, it doesn't exist. I don't have it in my library, but there is a radio.readAllRegsCompact(); you could implement (I'll put it on my long term to do list to maybe get to one day...).
For Boron troubleshooting, does it work if Boron is the transmitter and Photon the receiver? Can you disable the Boron cellular/mesh radios while testing?
PS: PM me if someone wants to donate 3rd gen devices and a set of RFM69 radios I can use to physically set up a test system to work through compatibility.
Trying this - no errors, output looks good in serial, but the Photon doesn't receive anything.
C:\Users\Ben>particle serial monitor
Opening serial monitor for com port: "COM4"
Serial monitor opened successfully:
.Sending Hello Photon 19
OK, sent without retrying
.Sending Hello Photon 20
OK, sent without retrying
.Sending Hello Photon 21
OK, sent without retrying
I'll keep trying. I really appreciate all of this - especially since you said you've since moved on to another rf module. I'm rechecking every wire and reflashing again.
@benbarnard that's interesting and frustrating. And the Photon just shows "........"? The receiving Photon is definitely the one with the RX sketch on? The same Photon that before received fine from the transmitting Photon?
Do you have 2 Borons to test Boron to Boron? Just trying to isolate the problem. If Photon to Photon works, and IF Boron to Boron works, then there's something to solve between the two hardware profiles. Maybe they have different clock speeds and the scaling or something doesn't work appropriately.
I donāt have another Boron - but I did put in an order for two Xenons this morning. I can use them (once they show up) to test this - at least then itāll be 3rd Gen to 3rd Gen. That said, Iām going to keep playing with this for a while in the hope that Iāve simply overlooked something. Thank you again!
Hi, Thank you @bloukingfisher for the library and the examples codes for tx and rx!
Just trying to use the RFM69-PARTICLE library with Workbench and between 2 Argons running OS 2.0.0.
the Receiver appears to behave correctly but does not receive anything.
The transmitting Argon shows this (I added reading the temperature just to see if comms with the RFM69HCW was working - result appears high?)
RFM69 TX Startup setup
Radio Temp C 165
Sending on 433 MHz
Sending Hello Argon5 0
I notice that there is no SPI.beginTransaction(SPISettings); and SPI.endTransaction(); so effectively the SPI bus is defaulted? Was there a reason for this?
RFM69_CS D6
RFM69_INT D2
RFM69_RST A5
in case these are overridden?
I found the problem in RFM69_Particle.cpp in the initialize method.
//pinMode(_slaveSelectPin, OUTPUT);
SPI.begin(_slaveSelectPin);
The SPI.begin() that was there before was overwriting the pinMode to be the default chip select!
I'm not sure whether this is safe to use. A5 is the MOSI pin for SPI so it should probably not be used as RST pin on the RFM69.
The default SS pin for SPI is A2 and calling SPI.begin() would not do anything other than setting A2 as OUTPUT pin. But after that any SPI.xxx() call wouldn't touch A2 again. It's the user code that needs to control the correct CS pin.
Agreed if it was the Photon I was using!
I wired the RFM69HCW feather according to the github solution that @rickkas7 put together for the RF96 I thought to allow the Argon to be used with the ethernet featherwing.
I see - I was going by Photon as itās mentioned in the topic title 