💬 Sensebender Micro mk2
-
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
-
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) -
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) -
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.
-
RFM69CW and RFM69HCW are not pin compatible.. One downside with hoperf, that they can't stick with a standard footprint layout..
-
@tbowmo from what I understand, they are pin compatible.
C and "non-C" are not pin compatible, but H and "non-H" are.
Older discussion on a similar topic: https://forum.mysensors.org/post/60304
-
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.
Seems that you are right about the power consumption.. According to the datasheets, they use the same in receive mode, and when transmitting 13dBm.. So in theory it shouldn't do any harm on battery life..
Well I'll see if I can incorporate it in the second prototype..
-
Check the datasheets, RFM69HCW has 16 pins, while RFM69CW only has 14 pins.
At least when I looked at the datasheets a couple of hours ago
@tbowmo said in 💬 Sensebender Micro mk2:
Check the datasheets, RFM69HCW has 16 pins, while RFM69CW only has 14 pins.
At least when I looked at the datasheets a couple of hours ago
Yes you are right. Sorry for the confusion.
-
Could we do what Moteino has done and drop support for HW/W radios and opt for HCW/CW/RFM95/96/RFM12 using double sets of pads?
https://lowpowerlab.com/shop/product/99
Would be great if the community could settle on just one radio or a common way of doing things. -
Currently I have the first prototype pcbs without components, so need to make an order at mouser/digikey. This has been on my task list for the last couple of months though, as wife / kids have a lot of other projects for me during the summer time :)
-
Currently I have the first prototype pcbs without components, so need to make an order at mouser/digikey. This has been on my task list for the last couple of months though, as wife / kids have a lot of other projects for me during the summer time :)
-
MySensors is already ported to samd21 so I expect things to be minor in order to get it up and running on samd20.
I will probably change footprint for the rfm69 module to use one that is compatible with rfm95 as well. And some other minor changes as well
-
A small update on this project, which I admit is taking longer than it should be (A lot of other projects has higher priority according to the wife)
I finally got the first prototype assembled saturday evening, I can upload firmware (via jtag/swd), and I have a semi hacked arduino core, that can build. But when programming the samd20e with this core, and a simple sketch toggling an output pin, nothing happens.
It seems that arduino halts in its initialization routine, waiting for some hardware to become ready after a reset, however I have not identified which part of the hardware yet.
-
A small update on this project, which I admit is taking longer than it should be (A lot of other projects has higher priority according to the wife)
I finally got the first prototype assembled saturday evening, I can upload firmware (via jtag/swd), and I have a semi hacked arduino core, that can build. But when programming the samd20e with this core, and a simple sketch toggling an output pin, nothing happens.
It seems that arduino halts in its initialization routine, waiting for some hardware to become ready after a reset, however I have not identified which part of the hardware yet.
-
Sorry, I got caught up in a couple of other projects, so still haven't got the first prototype up and run nok :(
