I modified MyConfig.h file and RFM69 driver to allow you build gateway (ethernet or MQTT) with W5100 ethernet and RFM69 radio modules using SoftSPI bus. You can find it at: https://github.com/gieemek/RFM69_softSPI-for-MySensors-2.1.1
Hi @berkseo. Thanks for the suggestion, but could you describe in more detail? As for my TODO list, there is already a task to add 485 interface to the gateway. My latest device "xRoom" have this interface.
ps/ Where have you gone?
I have been working on "xRoom" shield. A small announce:
Do you remember the discussion about multinode? So, it will be available soon))
Hi,
for everyone who reads all of this, forget about the last few posts.
I don't know why it works even when the Interrups are masked out on the radio, but it works now.
The error I had occured because of the config of the OrangePi-Gateway.
I removed:
--extra-cxxflags="-DMY_RF24_DATARATE=\(RF24_250KBPS\) -DMY_RF24_BASE_RADIO_ID=\(0x00,0xFC,0xE1,0xA8,0xA8\) -DMY_DEBUG_VERBOSE_RF24"
and wrote:
--extra-cxxflags="-DMY_RF24_DATARATE=\(RF24_250KBPS\) -DMY_DEBUG_VERBOSE_RF24"
Now I think I have an working OrangePi-Gateway without signing but with interrupt enabled.
If there are new problems I will come back here.
The next step for me is to activate signing again and bring the node into homeassistant.
@kimot I am not handling that situation. I'm taking for granted ssr will do his job. Maybe there's some ssr safety topic I'm unaware? Suggestions for a v3.0 are welcome.
About the temperature measuring... I use two sensors. The one in the board protects electronics from temperatures beyond design (60°C). It's near the ssr because the ssr's derating curve is the most limiting condition.
The control sensor is placed in the bottom of the heater. It connects to the board through a 3 pin header connector.
Not yet !
In fact, the interrupt must be short enough and fast enough to be sure to not miss the RFM69 interrupts.
The code for 8 dimmers will not be really more complicated : in fact, each time we got a zero cross, we must set a timer to zero, and then wait the good amount of milliseconds to turn on the needed outputs.
So, yes, we'll have an interrupts each 10ms (each time the wave crosses the zero, to be precise !), but I think all we have to do in the interrupt handler is set the timer to zero (or to micros() ...) and then on the main loop, wait the good amount of time for each output before setting them ON.
Seems simple on paper, perhaps it will not work on the chip....
In facts, my main concern is : will the RFM interrupt be short enough to not disturb the zero crossing interrupt ?
Although, not yet tested the RFM : do we NEED the interrupt pin ? Can't we poll frequently the RFM?