So Ciseco were nice enough to send me a Slice of Radio to try out on one of my Raspberry Pi’s. Show as shown above sat nicely on one of the original model B boards.
So what is a ‘slice of radio’, well quite simply it’s an SRF RF module on a carrier PCB that makes use of the serial port on the RaspberryPi GPIO connector.
Rather than try and figure out setting the Slice of Radio up for myself, I decided to follow the instructions provided by Ciseco, here, everything went without a hitch, it really did just work as described, full credit to the Ciseco team on this one.
Within ~10 minutes, I was talking to the SRF board, using minicom, and the extensive AT command set that Ciseco have provided to talk to the SRF, and associated RF boards in their range.
We’ll be following this up, with some practical examples of using the Slice of Radio, including how to build a SRF to Wifi bridge for optimal placement of the SRF master node.
Not really too much to say here. There has been much talk on the forums about using arduino and similar systems to provide additional IO capabilities for the RaspberryPi.
So I decided to take things a little further and discover whats needed to use the RaspberryPi itself as a development platform using the Arduino IDE.
Following the simple steps below, it is possible to install, and run the arduino IDE, and then re program your USB connected arduino. (more…)
OWFS the 1-Wire filesystem allows the use of i2c connected bus masters.
RaspberryPi conveniently provide i2c connectivity. However non of the images supplied provide i2c drivers. Fortunately at this point the community with its diverse range of members step in, within a few days an i2c driver is available. A few more days pass, more development takes place and the driver is now a loadable kernel module.
You can view the details of the driver development on this forum thread.
Along with OWFS working on RaspberryPi all the pieces are in place to begin testing of i2c 1-wire bus masters.
So following the delivery of our first raspberry pi from RS, unboxed, and using the debian “squeeze” image it was time to see what works out of the box.
Here’s the obligatory output from /proc/cpuinfo
pi@raspberrypi:~$ cat /proc/cpuinfo
Processor : ARMv6-compatible processor rev 7 (v6l)
BogoMIPS : 697.95
Features : swp half thumb fastmult vfp edsp java tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xb76
CPU revision : 7
Hardware : BCM2708
Revision : 0002
Serial : 000000009a5d9c22
How about adding an FTDI serial adaptor
Bus 001 Device 005: ID 04f2:0402 Chicony Electronics Co., Ltd Genius LuxeMate i200 Keyboard
Bus 001 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
So, how about 1-wire support.
You can’t have failed to notice the buzz around the upcoming RaspberryPi.
Both it’s price £25 for Model B (with ethernet connectivity) and size make it ideally suited to home automation, of particular interest is the expansion header that makes several GPIO connections available.
Included on this header is an i2c connection, making it an ideal candidate as a 1-wire to ethernet convertor for OWFS.
I’ve begun work on two 1-wire breakout boards, both making use of the i2c to 1-wire master chips that are available, providing a single and eight channels using the DS2482-100 and DS2482-800 chip.
Board Features are as follows
- RJ45 1-wire connection using the 1WRJ45 wiring standard.
- GPIO Header for connection to RaspberryPi
- 8 way GPIO Breakout header
- 2 SPI breakout headers , one for each SPI enable line
- Screw terminal for 5V power supply connection
- i2c Level conversion from 3.3v to 5v
- 3 pin DS18B20 connection (8 way board only)
- 6 way 1-wire expansion header (8 way board only)
Screen shots of initial PCB layout below, PCB’s are 5cm x 5cm in size.