Hi, Hub, I have code for a 16f876 that should work but it does not jet. If you mail me on [email protected] , I will replay you that code. I am as far as this: Initialisation is done, and I can read the registers back. I see used current change for the different modes, and see it change when I change the rate of sending packages, so I assume there is something transmitted. But the receiver does not report the arrival of anything. (and than my old scoop broke down and it cost me 10 days to repair). I am very pleased if you will look over my code and indicate where I might be incorrect. I know that the code should be tuned up to be JALLIB compiant, but... The structure of the program is like that as for the RF12B what is ducumented at my site www.henkzelf.nl (last link on intro-page).
By the way, I am 2 day's out, so do not expect an answer before wednesday. On 16 apr, 10:25, hubidrei <[email protected]> wrote: > Hi, > > I am very interested in your work on the RFM70, since I am currently > trying to get them work for my home automation, but I am far away from > a solution. For the master i use a18f2550 on a dwarf board, with Sprut > USB Bootloader. Slaves are 18f23k20. For now I try to translate the > RFM70.h and RFM70init.c files from the HopeRF RFM70 product site, but > this program uses pointers to arrays, so I have a lot todo until I > have a working lib. > > On 17 Mrz., 04:00, mattschinkel <[email protected]> wrote: > > > > > > > > > > Hello Matt, > > > Let us talk here about SPI, and not in the RF12 discussion. > > > Thanks, I didn't want to change the subject in the other discussion. > > > > I saw your code, and you are right about the mode. > > > The mode is not only about speed, but also about clock polarity. > > > I'll add "speed" to my software SPI lib, and also an spi exchange > > procedure. > > > I'll read yours over, maybe I don't understand what you required. > > > > About my other remark: > > > It would be nice if in the labels of the procedures and functions > > > no “_sw” or “_hw” appears for the ones who are compatible. > > > I know that changing labels in the lib for the hardware driver > > > can cause confusion. But still ... > > > "alias" can solve this problem. When including SPI in your main > > program, you can just do: > > alias spi_master is spi_master_sw > > > This way, your other files/libs can call "spi_master" instead of > > "spi_master_sw" or "spi_master_hw". This makes it easy to change > > between the two. > > > It is important to know that someone may decide to use both > > spi_master_hw and spi_master_sw on the same PIC, although there seems > > to be no reason to do so from our point of view. > > > > By the way: are you interested in a driver for the 24lc256 SPI-RAM? > > > I think we're interested in any new libraries :) > > > > If so: mail [email protected] and you get it. I have no time to check > > > for JALLIB style > > > as I am very busy with a radio-link using aRFM70. The RF12B did not > > > pass for > > > the project with Joep. > > > Knowing style guide will help you write good software in the future as > > well. > > > Matt. -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
