Search:

not really, in rx mode its PayloadReady in tx mode its PacketSent





that's 1% of the job done


cannot see any point to creating these vars , they will never be used

there is a big difference between comments that impart some information and visual white noise that masks the very few bits of data that are crucially different
and worthy of notation

yes the tx data is valid on sck's falling edge



no , its because a device with a cs low type input will assert its outputs when cs is low, they should not be asserted until every thing is in...

a few comments

for correct spi tx to rfm69 CKE must be asserted. SMP setting is irrelevant for rfm69 rx , I set SMP to suit other devices on my spi bus


...

sdo is pic output and would be the mosi line [master out slave In] connect to the module input pin, should be marked mosi
sdi is pic input and is the miso line [master in...

on that subject why even use a crystal




wrong , did you even look at the schematic I provided ?

there are 5 connections needed

read a register on the module . write a new value to that register read the register again and confirm the new value


looking at your picture there are two wires missing on each module , that's...

imho the example schematic from hoperf data sheet has miso/mosi names transposed on the module so be wary.

mosi is master out slave in and pic is the master

not really you need to understand what the rmf69 module wants , not what the pic mssp module is capable of .

refer to the rfm69hw data sheet , they do provide a pic connection example .

I have...

after a bit of experimenting I have come up with a fairly simple demo for rfm69hw with no bells and whistles for pbp
it can support two nodes has a fixed length payload of 16 bytes the remote end is...

i can only advise on rfm69 modules here
the modules come fixed to operate in one only of these bands you need one thats legal in your country
315MHz Module
433MHz Module
868MHz Module
915MHz...

exactly , all registers return to their default por values when the chip is reset , the chip has no non volatile registers.
every register that you assign a non por value to needs that value...

I found this useful , saves a lot of typing


ps use word or wordpad to view

No problem , but I don't particularly want to support it [ there is a slight bug in the reset fifo sequence too ,should be $ca81 from memory I think]
you realise of course that rfm69's are quite...

here's a pgm I did some years back to let my pic projects talk to the Arduino things its based on and compatible with the Arduino

rfm12b lowpowerlab library. I would not develop anything new...

rfm69 and rfm12 modules don't work that way , they retain no settings when powered off so they to be fully configured every power up .
they communicate via spi bus to the host and are most suited...