Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch enables the use of the RFM69W modules directly connected to the Raspberry Pi headers (no arduino gateway needed)
Note that we use software chip-select because we need to query the 1st byte to determine how many bytes to read without de-asserting chip-select, and the hardware chip-select does not support this. I have code to do this reusing the CS0 pin, but it required less change to use a separate pin, so I've started with that.
the configure command I used is:
./configure --my-gateway=mqtt --my-controller-ip-address=127.0.0.1 --my-mqtt-publish-topic-prefix=mysensors-out --my-mqtt-subscribe-topic-prefix=mysensors-in --my-mqtt-client-id=mygateway1 --my-transport=rfm69 --my-is-rfm69hw --my-rfm69-frequency=433 --my-rf69-irq-pin=10 --my-rf69-spi-cs=22 --my-rf69-spi-clock-div=250
This puts the IRQ pin on header-pin 10 and the chip-select on header pin 22 and uses a 1MHz clock (May be 1.6MHz on RPi3 depending on bus frequency)