Forgot your password?
No account? Register one!
August 3, 2008
Product WRL-09582 |
about a year ago
No. They are different. I tried the RMF12 with a PIC micro and gave up. I switched to a MRF49XA and it works beautifully. I think it had to do with the 16 bit fifo.
Anyway, I still haven’t seen anyone use a pic micro with the RFM12 without doing “bit-banging” of the commands and data.
Hey all, I finally gave up on the RFM12 and went to a MicroChip MRF49XA. Now my Balance Bot is up and running with Remote control!
Product WRL-09582 |
about 2 years ago
And in the end it turns out, the stopper is that I could not slow down the PIC SPI enough to match the RFM12 requirements. This is perhaps another reason all the PIC examples use bit-banging. My application cannot afford the bandwidth this requires and TMR2 is not available.
I finally gave up on the RFM12 part and have switched to a MicroChip MRF49XA. It works like a charm. My Balance Bot is now working with a very inexpensive 2-way Remote Control. This little tranceiver has a lot of potential and I’m just getting started!
roychook, I sure hope you got your answer by now. But if not, here’s my 2 cents…, All the examples I’ve seen using the Arduino processor use the SPI like you are wanting. Just write, and read the data. It gets clocked automatically.
But all the examples I’ve seen using a PIC micro manually clock the data one bit at a time. (Called “bit-banging). This is pretty usless. I’m trying to find out more, and I hope I’m wrong about the PIC not doing 16-bit SPI.
Sorry if this is a repeat. I’m stuck with using the PICf877 to SPI to the RFM12B. I’ve seen several examples of this using a “bit-banging” method. I wonder if anyone has done this by using the PIC SPI as intended with interrupt. My concern is the PIC is for 8-bit bytes, and the RFM12b has a 16-bit FIFO. I’m thinking there might be an extra clock between the bytes to cause an overflow. I’m going to have to put a lot of work into this just to finally find out it would never work.
No public wish lists :(