Support to ATtiny1634

[ramanc51]

Hi thanks to this libray, i modified your libray to support ATtiny1634 controller with ATttinyCore, now able to read & write RFM registers , getting RFM69 chip version, RSSI... ect correctly, but not able to receive payload, reading REG_IRQFLAGS2 always return zero, this mean payload not received, also IRQ not triggeered, i tested this receiver with another working sender(ESP8266+RMF69HCW) with same NETWORK ID and diiffernt NODE ID but no luck, cloud you pls suggest me any idea to resolve this?

ATtiny1634-JeeLibRX.zip

ATtiny1634-JeeLibTX.zip

[brandock]

Trystan may have more to say about this, but I have worked with this quite a bit and would say that, if it were me, I would move to the RFM69_LPL library instead of working with the older, interrupt-based JeeLib style of library. I pasted a link and to a description of the background on these two libraries, as well as an excerpt, below.

Reasons to use the RFM69_LPL library:

1. Frees up an MCU pin from having to be connected to IRQ/DIO0
2. Frees up the MCU to poll the transceiver rather than using an interrupt-based approach
3. You can look at my additions to RFM69_LPL to work the ATtiny84 MCU and incorporate the necessary additions for ATtiny1634: Update RFM69_LPL.cpp to support ATtiny84 and AVR128DB28 RFM69_LPL#2
4. The LPL format is really the go-forward format for OpenEnergyMonitor for many reasons

If you need to use the JeeLib Classic format, and need to receive packets in this format using ATtiny1634, I would suggest you start from the JeeLib library itself: https://github.com/openenergymonitor/jeelib. For these reasons:

1. This RFM69_JeeLib library you posted the issue to is specifically designed for AVR-DB MCUs used in emonTx4, emonTx5, and emonPi2
2. This RFM69_JeeLib library is only designed to enable transmitting, not receiving JeeLib Classic packets. It doesn't currently implement any of the interrupt-based IRQ/DIO0 receiving technique used by JeeLib Classic. There are some thorny hurdles to polling-based receiving in the JeeLib Classic format, where the header bytes happen before the length bytes in the packets.
3. The JeeLib library itself will show you the pattern for working with the ATtiny MCUs because it works with the ATtiny84. You can read some of the things I learned about this here: https://forum.arduino.cc/t/attiny84-jeelib-rfm69cw-attinycore-rf12-sendwait-hangs/1118466 and here: Update RF12.cpp jeelabs/jeelib#109

Background on libraries and formats
We have used the RFM69CW radio now for quite a few years but the release of the emonTx4 brings with it an important change in the software implementation used for the radio. Up until this point we had been using the JeeLib ‘Classic’ packet format. This was built around compatibility with an earlier generation radio module called RFM12. The benefit of backwards compatibility however meant that some of the new features implemented on the RFM69 module could not be used. These included the FIFO data buffers which reduce the requirement to interrupt the main microcontroller (useful for energy monitoring) and hardware encryption.

Jean Claude Wippler who originally developed the JeeLib library did develop a version of the library that made use of the new RFM69 features. He called the resulting packet format the ‘Native’ packet format. There’s a useful post on the differences here. More recently Robert Wall adapted this JeeLib native library for use with the emonPi, to make continuous sampling possible.

The LowPowerLabs packet format and library is a separately developed project by Felix Rusu of LowPowerLabs. In terms of packet format and implementation it is in many ways similar to the JeeLib Native packet format library - in that it uses the native RFM69 module features. The radio settings such as bit rate are subtly different (55,555 bits/s vs 49,230 bits/s). The header section of the radio packet payload is also slightly differently enabling 1023 possible nodes, 256 possible networks and a control byte used for requesting acknowledgments.

The emonTx4 uses the LowPowerLabs radio format by default.
The release of the emonTx4 was originally going to include the switch from the JeeLib Classic format to the JeeLib Native format, but in the end we’ve decided to make the switch to the LowPowerLabs library instead.

This significant change was made primarily in order to make use of the packet acknowledgment and retry feature implemented in the LowPowerLabs library, which in testing was critical to bring packet loss down to the magic 0% level (with nodes within good signal range).

The second important benefit of this change is to have a radio format that is compatible with the wider actively developed LowPowerLabs RFM69 ecosystem

[TrystanLea]

Agreed @brandock please use JeeLib library directly for ATtiny1634 and other cores. This library is just a very minimal fork/implementation that we are using for our AVR-DB based hardware. This repository is not intended for active further development and extending to other cores. Cheers.