blog.strobotics.com.

au

http://blog.strobotics.com.au/2008/06/17/rfm12-tutorial-part2/

RFM12 Tutorial Part2

135

Part 2 RFM12 Hardware Interface

In this next part of the RFM12 tutorials Ill be covering the hardware interface, signal descriptions and how you go about hooking it up to the MCU of your choice.

Packages
The RFM12 RF module comes in a couple of different packages, DIP and SMD, Ill mainly be covering the DIP throughout these series, but will touch on the SMD where necessary. There is also a long range version of the RFM12B, this is the RFM12BP and has a reported range of 3000m. The RFM12BP only comes in an extended SMD package, but I wont be covering it here in the tutorials, although all of the commands will be the same. The only difference is the RFM12BP has an on board power amp, which requires 12V to power the PA portion and has associated control pins for Tx/RX control. DIP The DIP package uses a 62 2mm pitch header to connect the various signals to the MCU, The size of this header is a bit of a problem if you want to do prototyping as it doesnt breadboard well, initially I didnt have any 2mmm pitch female headers so I hand soldered on individual wires to the back of each pin, not really good in the long run as the wires kept on breaking off, so I designed a breakout board to bring out all the signals onto a standard 100mil pitch, much easier to breadboard. SM D There are two version of the SMD module, and from what I can gather the only difference is the crystal, one is the standard HCU form factor, while the other is a ceramic oscillator. Antenna: The only real difference when using the SMD over the DIP package is there is no on-board antenna connection, the antenna comes out via one of the pins, so you need to design in an antenna connection if using the SMD version. ARSSI: The SMD package allows access to another useful signal that is not available to the DIP version, this is the ARSSI Analogue Relative Signal Strength Indicator, which is basically the strength of the signal being received by the module, however its not bought out on any of the pins, beats me why? There a digital version of this signal accessible though the software interface, from what I can gather there is a difference from the Digital and Analogue versions of this signal. Anyway what it boils down to if you want to access this analogue signal then you have to manually solder on a wire to access this pad (shown as red circle). UPDATE: the onboard DRSSI is a single bit returned in the status word that indicates if the RSSI is above the set threshold. The ARSSI hack mentioned gives an analogue value that is proportional to the RSSI signal received.

Antenna
The antenna mostly used will probably be a whip antenna, basically a piece of wire cut to the right length, I wont be covering antenna theory here, as I dont know it , but suffice to say the approx lengths involved are as follows (measured from factory supplied antennas): 433Mhz 173mm 915Mhz 87mm UPDATED: 03/07/2009 These antenna lengths are calculated for the respective bands 433 1/4 wave = 164.7mm 433 1/2 wave = 329.4mm 433 full wave = 692.7mm 868 1/4 wave = 82.2mm 868 1/2 wave = 164.3mm 868 full wave = 345.5mm 915 1/4 wave = 77.9mm 915 1/2 wave = 155.9mm 915 full wave = 327.8mm With these lengths Ive had no problem reaching 30m+ indoors through a number of walls and 120m+ outside, Ive not yet trie different types of antennas such as SMA connected rubber duck type but they should work as Ive spoken to tech support at HopeRF and they tell me that the antenna circuit on both modules is balanced to 50 Ohm, this means that most SMA rubber duck antennas in the right frequency range will also work. Make sure that the antenna is matched to the frequency range required to get the best range, i.e. dont use a wifi antenna for 2.4GHZ on a 433Mhz module, it may work for short distances, but definately wont be optimal for long distances, also you may damage your RF module (unconfirmed it this is is the case as these are low power devices), but usually antennas need to be SWR matched to stop reflectance back into the transmitter circuit. There is also some technical documents on Hopes website for PCB based antennas, but Ive not used these at all so your milage may vary with them. As mentioned earlier the SMD has no direct antenna connection so you need to design in a connection, either a solder pad on your board or an SMA connector. The DIP package on the other hand allows you to solder in the antenna right onto the module, usually you will solder in the wire directly, however you need to make sure that you get the right pad, as there are two very small solder pads right next to each other, one is the antenna, one is ground, both are not marked in anyway as to to their function, and the documentation does not show which one is which. You need to solder in the piece of wire to the one not connected to ground, best to check with a multimeter or continuity tester first. It looks as though you can also uses these two pads on the DIP module to connect an external SMA connector with a pigtail to the module as well (both ground and antenna).

PIN Connections
The pin connections for the module is described below, I have indicated whether the connection is required

or is optional when making connections. The basic connections as described will allow data rates of up to approx 12000bps on an 8Mhz PIC using a bit-bashed SPI, polled approach when handling sending and receiving data, higher data rates will require hardware SPI, higher MCU speed and the use of interrupts, these will be discussed in a later tutorial.

UPDATE: Please see this article for more detailed information regarding RFM12B bit rates and the different pin connections. VDD (required) The nominal working voltage is between 2.2v and 3.8v (NOT 5V), make sure that you have bypass filters in place on the supply rails. nINT/VDI (optional) This pin can be configured as either input or output, if configured as an input then its function is an active low interrupt request from the MCU, The MCU pulls this line low if it want to interrupt the RF module. If configured as an output then its the VDI, Valid Data indicator, meaning valid data has been detected by the receiver and outputs a high. Factory Default is VDI SDI (required) SPI Data input, where the MCUs MOSI signal needs to be connected to. SCK(required) SPI clock input from MCU nSEL (required) Chip Select (active low). This signal must be pulled low before any signal is sent via SPI to the RF module, SDO (required) SPI Data out, where the MCU MISO signal needs to be connected to. nIRQ (optional) Interrupt Request output (active low), this is when the RF module wans to signal the MCU an event has occurred. This should be tied high with a pullup resistor. FSK/DATA/nFFS (optional but requires 10K pullup when not used): FSK Transmit data input DATA Received Data output nFFS If pulled high then the FIFO is selected then data is transmited / received via the internal FIFO acessed via the SPI interface. If the FIFO is not being used then this is where the data is directly clocked into or out of the Tranceiver. Use this mode for high datarates. DCLK/CFIL/FFIT (optional): DCLK is the data clock when no FIFO is used (used in conjunction with FSK/DATA/nFFS pin). CFIL is used to connect an external capacitor when using 256K datarates, this is for the analogue filter, normally the internal digital filter is used by default, only lower data rates are achieved with the digital filter. FFIT FIFO interrupt, interrupt signal is generated whenever the FIFO interrupt level is achieved (level is configured via SPI and is covered in the software interface tutorial), normally the interrupt level would be set to 8 if using the FIFO so that an interrupt is generated for every byte received. If using the FSK/DATA to clock in the data then the interrupt level should be set to 1, this way an interrupt is set for every bit sent/received. CLK (optional) Clock output, defaults to 1Mhz, but can be configured in increments up to 10Mhz, or

switched off. This signal can be used to provide a clock signal to the MCU if it has no internal oscillator, i.e. cuts down on an additional crystal required for the MCU. This signal is also used in the calibration of the RF modules and will be explained later. nRES (required) this is reported in the Hope RF documentation as an output but is really an input (active low) and needs to be tied high at all times. If pulled low it will reset the module back to POR default (power on reset) settings. GND (required) Power Ground. ANT (on SMD, required) Where the antenna is connected. Back Part 1 | Next Part 3a

Similar Posts:
You must be logged in to post a comment.