It would be nice if you could post a .pdf of the schematic.... not everyone has the tool to see the board from the .sch file.

@Nca78

1.27mm headers 5x2 (.05in) Mouser 855-M50-3500542 made by Harwin

Well, that news to me. I've always use the HCW variant and did NOT noticed the pin change. My error for not looking at the detail... (This was not the case with the RFM69W and HW radios, both shared the same pin-out)

but again, using the HCW allow one to also use the RFM95 radios, and if you keep power below +13, power consumption is about the same... also the new RFM69 radio driver in 2.2b use adaptive power control as an option, this keep power use to a minimum saving power.

I just re-checked the data sheets, RFM95 and RFM69HCW do share the same pin-out.

Yes, The H = High Power version, C = Compact version 16x16mm pkg, vis 16x19mm pkg

My error, RFM69CW and RFM69HCW are available, also note that if you do not use the power over +13dbm, power consumption is about the same between the radios.

https://lowpowerlab.com/forum/rf-range-antennas-rfm69-library/rfm69w-and-rfm69hw-current-consumption/


[0_1496604219131_RFM69CW-V1.1.pdf](/assets/uploads/files/1496604221362-rfm69cw-v1.1.pdf) 

Both the RFM69HC and RFM69HCW are available in the smaller package.... again, this would allow RFM95 to be used.

Thanks...

[0_1496601875842_RFM69HC_DataSheet_v1.1.pdf](/assets/uploads/files/1496601877634-rfm69hc_datasheet_v1.1.pdf) 

Is this board using the RFM69HCW footprint so that one could also use an RFM95??
If not, please consider this change and you might want to consider as an option for DIO-1 connected to an I/O pin on the CPU.. (this would also make it compatible with LoRaWan network)

Thanks

I use the standard Arduino IDE for most things but moving to PlatformIO as it's editor is so much better that the brain dead one in the Arduino IDE

@gohan Pro-mini, is a great part, but sometime you need a lot more! 32 bit is the future for me, less power, less cost, more resources....less hassles...

@lafleur

You should also add this to your test code to see debug messages from the MySensor stack.. Also add to gateway, so that you can see what happening on both ends....

/*  Enable debug prints to serial monitor on port 0 */
#define MY_DEBUG            // used by MySensor
#define MY_DEBUG_VERBOSE_RFM69 

@Nca78

As manufacturing of chips goes to smaller and smaller die size, chip cost go down and preformance goes up..... older processors cost more to build that newer parts!

It all means better performance, less power and more features for less money...

The intel 8080 when it was introduced was $360, power hungry, no ram, no storage, no I/O, needed a lot of support chips.... we have come a long way!!!!