OpenBeacon - Recent changes [en]

User:Julianmarble

Milosch — Wed, 08 Sep 2010 08:05:52 GMT

blocked [[Julianmarble (Talk | contribs)]] with an expiry time of infinite (account creation disabled, e-mail blocked) Spamming links to external sites

OpenPCD Passive RFID Project

Milosch — Wed, 08 Sep 2010 07:59:56 GMT

Reverted edits by Alysia (talk) to last revision by Milosch

← Older revision		Revision as of 07:59, 8 September 2010
Line 50:		Line 50:
	* two-wire I2C interface on 1x4 header		* two-wire I2C interface on 1x4 header
	* SAM-BA reset control on 1x4 header		* SAM-BA reset control on 1x4 header
-	* [http://www.onlinechatden.com free online chat rooms]
	* 4 analog inputs on a 1x5 header		* 4 analog inputs on a 1x5 header
	* bootloader reset via push-button		* bootloader reset via push-button

OpenPCD Passive RFID Project

Alysia — Wed, 08 Sep 2010 06:35:56 GMT

OpenPCD 1 release:

← Older revision		Revision as of 06:35, 8 September 2010
Line 50:		Line 50:
	* two-wire I2C interface on 1x4 header		* two-wire I2C interface on 1x4 header
	* SAM-BA reset control on 1x4 header		* SAM-BA reset control on 1x4 header
		+	* [http://www.onlinechatden.com free online chat rooms]
	* 4 analog inputs on a 1x5 header		* 4 analog inputs on a 1x5 header
	* bootloader reset via push-button		* bootloader reset via push-button

User:Alysia

Alysia — Wed, 08 Sep 2010 06:24:50 GMT

New user account

OpenPCD Passive RFID Project

Milosch — Tue, 07 Sep 2010 20:05:13 GMT

History:

← Older revision		Revision as of 20:05, 7 September 2010
(2 intermediate revisions not shown)
Line 45:		Line 45:
	== OpenPCD 1 release ==		== OpenPCD 1 release ==
	[[File:FirstOpenPCD.jpg\|right\|thumb\|400px\|First OpenPCD 1 hardware release]]		[[File:FirstOpenPCD.jpg\|right\|thumb\|400px\|First OpenPCD 1 hardware release]]
-	The OpenPCD hardware design is based on the CL RC632 Multiple Protocol Contactless Reader IC from Philips, which supports ISO 14443 A&B, ISO 15693, Mifare and ICODE protocols. This reader IC is connected via SPI to an ARM Microcontroller. We chose the AT91SAM7S128 with a 32-bit RISC processor architecture, 128 kbytes Flash and 32 kbytes SRAM. The Microcontroller is accessible via USB-B-MINI plug and optionally via a 20-pin JTAG header. The design provides several interesting interfaces for monitoring and studying the RFID signal:	+	The [[Hardware\|OpenPCD hardware design]] is based on the CL RC632 Multiple Protocol Contactless Reader IC from Philips, which supports ISO 14443 A&B, ISO 15693, Mifare and ICODE protocols. This reader IC is connected via SPI to an ARM Microcontroller. We chose the AT91SAM7S128 with a 32-bit RISC processor architecture, 128 kbytes Flash and 32 kbytes SRAM. The Microcontroller is accessible via USB-B-MINI plug and optionally via a 20-pin JTAG header. The design provides several interesting interfaces for monitoring and studying the RFID signal:

	* serial RS232/TTL interface on 1x5 header		* serial RS232/TTL interface on 1x5 header
Line 59:		Line 59:
	= License =		= License =

-	The hardware design has been released under a CC attribution share-alike license, the reader firmware and drivers (librfid glue code, plus some extras) have been released under GNU/GPL. You can find both at our download page. Your participation is welcomed in our OpenPCD Subversion repository and our Wiki.	+	The [[Hardware\|hardware design]] has been released under a [http://creativecommons.org/licenses/by-sa/2.5/ CC attribution share-alike license], the reader firmware and drivers (librfid glue code, plus some extras) have been released under GNU/GPL. You can find both at our download page. Your participation is welcomed in our OpenPCD Subversion repository and our Wiki.

-	Design and SDK are available under non-open license types upon request.	+	Design and SDK are available under non-open license types upon request alternatively to the OpenSource licenses provided here.

	= History =		= History =
Line 67:		Line 67:
	The projects prehistory started in May 2005 with Harald and Milosch working in the lab of the CCC-Berlin on different ways to passive receive and demodulate RFID signals. The RFID tag responds to the RFID reader by using the transmitted 13,56MHz carrier signal as a power supply and modulates the carrier with a 847.5kHz subcarrier by load modulation according to its contained informations. With further knowledge of how to downmix the incoming signal to make filtering with common filter possible before amplify the signal, a hardware (rfiddump.org) was designed to simulate the RFID transponder. Brita got involved with the HF PCB layout for the RFID Mini Sniffer and trials with different antennas.		The projects prehistory started in May 2005 with Harald and Milosch working in the lab of the CCC-Berlin on different ways to passive receive and demodulate RFID signals. The RFID tag responds to the RFID reader by using the transmitted 13,56MHz carrier signal as a power supply and modulates the carrier with a 847.5kHz subcarrier by load modulation according to its contained informations. With further knowledge of how to downmix the incoming signal to make filtering with common filter possible before amplify the signal, a hardware (rfiddump.org) was designed to simulate the RFID transponder. Brita got involved with the HF PCB layout for the RFID Mini Sniffer and trials with different antennas.

-	In a one hour presentation at the 22C3 (Chaos Communication Congress December 2005 in Berlin) Harald and Milosch first public announced the project. Harald covered the technical background about the RFID technology, the ICAO MRTD specification, and his efforts to develop a free software protocol stack. Milosch described the current progress in developing hardware and software defined radio based passive sniffing of the RFID radio interface.	+	In a one hour [http://events.ccc.de/congress/2006/Fahrplan/events/1736.en.html presentation at the 22C3] (Chaos Communication Congress December 2005 in Berlin) Harald and Milosch first public announced the project. Harald covered the technical background about the RFID technology, the ICAO MRTD specification, and his efforts to develop a free software protocol stack. Milosch described the current progress in developing hardware and software defined radio based passive sniffing of the RFID radio interface.

-	Meanwhile Harald launched the project OpenMRTD, which provides a free (GPL) toolset for reading and verifying various RFID protocols from MRTDs (Machine Readable Travel Documents). As part of this project the Free Software RFID library 'librfid' implements the RFID reader side protocol stack of ISO 14443 A, ISO 14443 B, ISO 15693, Mifare Ultralight and Mifare Classic. In order to use these free tools, users still have to rely on commercial and closed hardware readers with their limitations and faults.	+	Meanwhile Harald launched the project [http://openmrtd.org/ OpenMRTD], which provides a free (GPL) toolset for reading and verifying various RFID protocols from MRTDs (Machine Readable Travel Documents). As part of this project the Free Software RFID library 'librfid' implements the RFID reader side protocol stack of [[ISO14443\|ISO 14443 A]], [[ISO14443\|ISO 14443 B]], [[ISO15693\|ISO 15693]], Mifare Ultralight and Mifare Classic. In order to use these free tools, users still have to rely on commercial and closed hardware readers with their limitations and faults.

	To fill this gap in the free toolchain for verifying RFID protocols, this project tries to develop a free hardware design of an RFID reader with free firmware (which either works with librfid on the host PC, or runs librfid in the reader). The first prototype of the OpenPCD free RFID reader is still under testing but already offers the basic functionality of reading different RFID cards/transponder and transmitting freely modulated signals.		To fill this gap in the free toolchain for verifying RFID protocols, this project tries to develop a free hardware design of an RFID reader with free firmware (which either works with librfid on the host PC, or runs librfid in the reader). The first prototype of the OpenPCD free RFID reader is still under testing but already offers the basic functionality of reading different RFID cards/transponder and transmitting freely modulated signals.

Hardware

Milosch — Tue, 07 Sep 2010 19:53:25 GMT

← Older revision		Revision as of 19:53, 7 September 2010
Line 1:		Line 1:
	[[Category:OpenPCD]]		[[Category:OpenPCD]]
		+
		+	[[File:OpenPCD-PCB.jpg\|thumb\|right\|500px\|OpenPCD 1 revision v0.4 PCB - above image is also available in [[Media:OpenPCD-PCB.jpg\|high resolution]]]]
		+
		+	__TOC__
		+
	== Description of OpenPCD Hardware ==		== Description of OpenPCD Hardware ==

File:OpenPCD-PCB.jpg

Milosch — Tue, 07 Sep 2010 19:44:36 GMT

uploaded "[[File:OpenPCD-PCB.jpg]]" OpenPCD 1 circuit board

Hardware

Milosch — Tue, 07 Sep 2010 19:08:16 GMT

← Older revision		Revision as of 19:08, 7 September 2010
(One intermediate revision not shown)
Line 4:		Line 4:
	=== Overview ===		=== Overview ===

-	~~The~~ [[OpenPCD]] Hardware is based on a Philips [[RC632\|CL RC632 RFID Reader ASIC]] and an [[AT91SAM7\|Atmel AT91SAM7S256]] [[ARM7TDMI]] Microcontroller.	+	* Schematics & Layout files can be found in the [[OpenPCD Downloads]] section.
-		+	* the [[OpenPCD]] Hardware is based on a Philips [[RC632\|CL RC632 RFID Reader ASIC]] and an [[AT91SAM7\|Atmel AT91SAM7S256]] [[ARM7TDMI]] Microcontroller.
-	~~The~~ [[SAM7]] is connected to the host PC via [[USB]].	+	* the [[SAM7]] is connected to the host PC via [[USB]].
-		+	* the [[RC632]] is controlled via [[SPI]].
-	~~The~~ [[RC632]] is controlled via [[SPI]].	+
-		+
-	~~=== Schematics ===~~	+
-		+
-	~~see http://www.openpcd.org/releases.0.html~~	+
-		+
-	~~=== PCB Layout ===~~	+
-		+
-	~~see http://www.openpcd.org/releases.0.html~~	+
-		+

	=== Hardware Revisions ===		=== Hardware Revisions ===

OpenPCD Passive RFID Project

Milosch — Tue, 07 Sep 2010 19:03:27 GMT

OpenPCD first release:

← Older revision		Revision as of 19:03, 7 September 2010
(2 intermediate revisions not shown)
Line 8:		Line 8:

	== Introduction ==		== Introduction ==
-		+	[[File:OpenPCD2s.JPG\|thumb\|400px\|right\|Upcoming OpenPCD 2 - a 13.56MHz RFID Writer/Reader/Emulator with NFC protocol support]]
	OpenPCD is a free hardware design for Proximity Coupling Devices (PCD) based on 13,56MHz communication. This device is able to screen informations from Proximity Integrated Circuit Cards (PICC) conforming to vendor-independent standards such as ISO 14443, ISO 15693 as well as proprietary protocols such as Mifare Classic. Contactless cards like these are for example used in the new electronic passports.		OpenPCD is a free hardware design for Proximity Coupling Devices (PCD) based on 13,56MHz communication. This device is able to screen informations from Proximity Integrated Circuit Cards (PICC) conforming to vendor-independent standards such as ISO 14443, ISO 15693 as well as proprietary protocols such as Mifare Classic. Contactless cards like these are for example used in the new electronic passports.

	The intention of the OpenPCD project is to offer the users full hardware control of the RFID signal and to provide different output signals for screening the communication. With already existing Free Software from the OpenMRTD project for implementing the PCD side protocol stack of various RFID protocols, this project will happily extend the free toolchain around RFID verification.		The intention of the OpenPCD project is to offer the users full hardware control of the RFID signal and to provide different output signals for screening the communication. With already existing Free Software from the OpenMRTD project for implementing the PCD side protocol stack of various RFID protocols, this project will happily extend the free toolchain around RFID verification.

-	=== Further reading ===	+	=== Further reading on OpenPCD 1 ===
	* Design		* Design
	** [[Hardware#Overview\|Overview]]		** [[Hardware#Overview\|Overview]]
Line 43:		Line 43:
	* [[:Category:OpenPCD\|Everything About OpenPCD]]		* [[:Category:OpenPCD\|Everything About OpenPCD]]

-	== OpenPCD ~~first~~ release ==	+	== OpenPCD 1 release ==
-	[[File:FirstOpenPCD.jpg\|right\|~~frameless~~\|400px\|First OpenPCD hardware release]]	+	[[File:FirstOpenPCD.jpg\|right\|thumb\|400px\|First OpenPCD 1 hardware release]]
	The OpenPCD hardware design is based on the CL RC632 Multiple Protocol Contactless Reader IC from Philips, which supports ISO 14443 A&B, ISO 15693, Mifare and ICODE protocols. This reader IC is connected via SPI to an ARM Microcontroller. We chose the AT91SAM7S128 with a 32-bit RISC processor architecture, 128 kbytes Flash and 32 kbytes SRAM. The Microcontroller is accessible via USB-B-MINI plug and optionally via a 20-pin JTAG header. The design provides several interesting interfaces for monitoring and studying the RFID signal:		The OpenPCD hardware design is based on the CL RC632 Multiple Protocol Contactless Reader IC from Philips, which supports ISO 14443 A&B, ISO 15693, Mifare and ICODE protocols. This reader IC is connected via SPI to an ARM Microcontroller. We chose the AT91SAM7S128 with a 32-bit RISC processor architecture, 128 kbytes Flash and 32 kbytes SRAM. The Microcontroller is accessible via USB-B-MINI plug and optionally via a 20-pin JTAG header. The design provides several interesting interfaces for monitoring and studying the RFID signal:

Line 75:		Line 75:
	= Team =		= Team =

-	[[File:OpenPCD_Team.jpg\|right\|~~frameless~~\|400px\|~~Left~~ to ~~Right~~: Milosch Meriac, Brita Meriac, Harald Welte]]	+	[[File:OpenPCD_Team.jpg\|right\|thumb\|400px\|From left to right: Milosch Meriac, Brita Meriac, Harald Welte]]
	Harald Welte is a long-term supporter and active member of the Free Software community. His expertise in Linux Kernel development and networking security made him Chairman of the netfilter coreteam. He's one of the principal authors of the Linux 2.4+Kernel Packetfilter, securing virtually every linux installation. As manager of hmw-consulting in Berlin Harald Welte is offering professional consulting, development and training in the fields of networking security, Linux kernel development and embedded Linux.		Harald Welte is a long-term supporter and active member of the Free Software community. His expertise in Linux Kernel development and networking security made him Chairman of the netfilter coreteam. He's one of the principal authors of the Linux 2.4+Kernel Packetfilter, securing virtually every linux installation. As manager of hmw-consulting in Berlin Harald Welte is offering professional consulting, development and training in the fields of networking security, Linux kernel development and embedded Linux.

NRF24L01

Milosch — Tue, 07 Sep 2010 18:53:44 GMT

← Older revision		Revision as of 18:53, 7 September 2010
Line 1:		Line 1:
	[[Category:OpenBeacon]]		[[Category:OpenBeacon]]
-
	== Overview ==		== Overview ==
-		+	[[File:NRF24L01P.jpg\|300px\|right\|thumb\|nRF14L01+ 2.4GHz frontend from Nordic Semiconductors on the [[OpenBeacon Tag]]]]
	The nRF24L01 is a low-power and low-cost 2.4GHz transceiver ASIC produced by Nordic Semiconductors which is used in our open hardware design for our active RFID tag - http./www.openbeacon.org. We currently use it for realtime tracking of people at congresses.		The nRF24L01 is a low-power and low-cost 2.4GHz transceiver ASIC produced by Nordic Semiconductors which is used in our open hardware design for our active RFID tag - http./www.openbeacon.org. We currently use it for realtime tracking of people at congresses.

Line 19:		Line 18:
	* SPI interface to the CPU		* SPI interface to the CPU

-	== ~~Links~~ ==	+	== Default initialization for [[OpenBeacon Tag]] ==
		+
		+	=== config.h ===
		+	<syntaxhighlight lang="c">
		+	#define CONFIG_DEFAULT_CHANNEL 81
		+	</syntaxhighlight>
		+
		+	===nRF_CMD.h ===
		+	<syntaxhighlight lang="c">
		+	// LNA, RF output -18dBm, 2Mbps
		+	#define NRF_RFOPTIONS 0x09
		+
		+	#define NRF_MAC_SIZE 5
		+	</syntaxhighlight>
		+
		+	===nRF_CMD.c ===
		+	<syntaxhighlight lang="c">
		+	#define NRF_CONFIG_BYTE (NRF_CONFIG_EN_CRC)
		+
		+	// first byte payload size+1, second byte register, 3..n-th byte payload
		+	const unsigned char g_MacroInitialization[] = {
		+	0x01, OP_NOP,
		+	0x02, CONFIG \| WRITE_REG, 0x00, // stop nRF
		+	0x02, EN_AA \| WRITE_REG, 0x00, // disable ShockBurst(tm)
		+	0x02, EN_RXADDR \| WRITE_REG, 0x01, // enable RX pipe address 0
		+	0x02, SETUP_AW \| WRITE_REG, NRF_MAC_SIZE - 2, // setup MAC address width to NRF_MAC_SIZE
		+	0x02, RF_CH \| WRITE_REG, CONFIG_DEFAULT_CHANNEL, // set channel to 2480MHz
		+	0x02, RF_SETUP \| WRITE_REG, NRF_RFOPTIONS, // update RF options
		+	0x02, STATUS \| WRITE_REG, 0x78, // reset status register
		+	0x06, RX_ADDR_P0 \| WRITE_REG, 'O', 'C', 'A', 'E', 'B', // set RX_ADDR_P0 to "BEACO"
		+	0x06, TX_ADDR \| WRITE_REG, 0x01, 0x02, 0x03, 0x02, 0x01, // set TX_ADDR
		+	0x02, RX_PW_P0 \| WRITE_REG, 16, // set payload width of pipe 0 to sizeof(TRfBroadcast)
		+	0x00 // termination
		+	};
		+	</syntaxhighlight>

-	=== ~~Official Product Homepage~~ ===	+	== Further reading ==
-	~~http://www.nordicsemi.no/index.cfm?obj=product&act=display&pro=89~~	+

-	=== Data Sheet ~~===~~	+	* Official Product Homepage: http://www.nordicsemi.no/index.cfm?obj=product&act=display&pro=89
-	http://www.nordicsemi.no/files/Product/data_sheet/nRF24L01_Product_Specification_v2_0.pdf	+	* Data Sheet: http://www.nordicsemi.no/files/Product/data_sheet/nRF24L01_Product_Specification_v2_0.pdf

OpenBeacon Tag

Milosch — Tue, 07 Sep 2010 18:37:17 GMT

Programming Work Flow:

← Older revision		Revision as of 18:37, 7 September 2010
(One intermediate revision not shown)
Line 5:		Line 5:
	* OpenBeacon Tag related firmware source may be found on Subversion server ([http://openbeacon.svn.sourceforge.net/viewvc/openbeacon/trunk/firmware/pic16/tag/ pic16tag Firmware]):		* OpenBeacon Tag related firmware source may be found on Subversion server ([http://openbeacon.svn.sourceforge.net/viewvc/openbeacon/trunk/firmware/pic16/tag/ pic16tag Firmware]):
	svn co svn co https://openbeacon.svn.sourceforge.net/svnroot/openbeacon/trunk/firmware/pic16/tag/ openbeacon		svn co svn co https://openbeacon.svn.sourceforge.net/svnroot/openbeacon/trunk/firmware/pic16/tag/ openbeacon
-	* refer to [[Linux Installation Process of Microchip development environment\|our compiler setup instuctions]]	+	* '''refer to [[Linux Installation Process of Microchip development environment\|our compiler setup instuctions]]'''

	=== Understanding the tag source code ===		=== Understanding the tag source code ===
	[[File:Sputnik-25C3.jpg\|200px\|thumb\|right\|Spurnik tag as used on the 25C3 CCC congress]]		[[File:Sputnik-25C3.jpg\|200px\|thumb\|right\|Spurnik tag as used on the 25C3 CCC congress]]
		+	[[File:PIC16F684.jpg\|200px\|thumb\|right\|PIC16F684 Microcontroller from Microchip on the [[OpenBeacon Tag]] running the code shown]]
		+
	That's the main loop from ''main.c'' in the tag firmware. The line where the actual packet macro is transmitted to the [[nRF24L01]] chip is highlighted. Basically first the packet is assembled, then the CRC calculated and the data encrypted (shuffle_tx_byteorder is used to adjust byte order to achieve platform independence). As final step RFCMD_Execute() triggers the transmitting process. Interesting feature ot this code is that the packet macro is prepended by a macro that adjust the transmit power on every transmission (''g_MacroBeacon.rf_setup'').		That's the main loop from ''main.c'' in the tag firmware. The line where the actual packet macro is transmitted to the [[nRF24L01]] chip is highlighted. Basically first the packet is assembled, then the CRC calculated and the data encrypted (shuffle_tx_byteorder is used to adjust byte order to achieve platform independence). As final step RFCMD_Execute() triggers the transmitting process. Interesting feature ot this code is that the packet macro is prepended by a macro that adjust the transmit power on every transmission (''g_MacroBeacon.rf_setup'').

Linux Installation Process of Microchip development environment

Milosch — Tue, 07 Sep 2010 18:32:55 GMT

Compiler Installation:

← Older revision		Revision as of 18:32, 7 September 2010
Line 12:		Line 12:

	== Compiler Installation ==		== Compiler Installation ==
-		+	[[File:PIC16F684.jpg\|200px\|thumb\|right\|PIC16F684 Microcontroller from Microchip on the [[OpenBeacon Tag]]]]
	Download the ''HI-TECH C for the PIC10/12/16 MCU Family'' compiler at [http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en542849 http://www.microchip.com]. Registration at Microchip seems to be mandatory for that.		Download the ''HI-TECH C for the PIC10/12/16 MCU Family'' compiler at [http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en542849 http://www.microchip.com]. Registration at Microchip seems to be mandatory for that.

File:PIC16F684.jpg

Milosch — Tue, 07 Sep 2010 18:31:04 GMT

uploaded "[[File:PIC16F684.jpg]]" PIC16F684 Microcontroller from Microchip

Linux Installation Process of Microchip development environment

Milosch — Tue, 07 Sep 2010 18:03:28 GMT

← Older revision		Revision as of 18:03, 7 September 2010
(One intermediate revision not shown)
Line 1:		Line 1:
	[[Category:OpenBeacon]]		[[Category:OpenBeacon]]

-	~~= Linux Installation Process of Microchip development environment =~~	+	[[File:Sputnik-25C3.jpg\|200px\|thumb\|right\|Spurnik tag as used on the 25C3 CCC congress]]

	__TOC__		__TOC__
Line 57:		Line 57:
	== Programmer installation ==		== Programmer installation ==
	[[File:PICkit2.jpg\|200px\|right\|thumb\|PICkit2 USB programmer with six pin 2.54mm header attached]]		[[File:PICkit2.jpg\|200px\|right\|thumb\|PICkit2 USB programmer with six pin 2.54mm header attached]]
		+	[[File:Header6x2 54mm.jpg\|200px\|right\|thumb\|Cut your own six pin 2.54 header and insert into PICkit2 programmer to re-flash tags]]
	At [http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en023805 PICkit 2 Development Programmer/Debugger] please scroll down to ''Linux & Mac OS X Software (Unsupported)'' and download ''PK2CMD V1.20 Linux Kernel 2.6 Executable Binary''.		At [http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en023805 PICkit 2 Development Programmer/Debugger] please scroll down to ''Linux & Mac OS X Software (Unsupported)'' and download ''PK2CMD V1.20 Linux Kernel 2.6 Executable Binary''.

File:Header6x2 54mm.jpg

Milosch — Tue, 07 Sep 2010 17:54:59 GMT

uploaded "[[File:Header6x2 54mm.jpg]]"

Linux Installation Process of Microchip development environment

Milosch — Tue, 07 Sep 2010 17:51:10 GMT

Programmer installation:

← Older revision		Revision as of 17:51, 7 September 2010
Line 56:		Line 56:

	== Programmer installation ==		== Programmer installation ==
-		+	[[File:PICkit2.jpg\|200px\|right\|thumb\|PICkit2 USB programmer with six pin 2.54mm header attached]]
	At [http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en023805 PICkit 2 Development Programmer/Debugger] please scroll down to ''Linux & Mac OS X Software (Unsupported)'' and download ''PK2CMD V1.20 Linux Kernel 2.6 Executable Binary''.		At [http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en023805 PICkit 2 Development Programmer/Debugger] please scroll down to ''Linux & Mac OS X Software (Unsupported)'' and download ''PK2CMD V1.20 Linux Kernel 2.6 Executable Binary''.

File:PICkit2.jpg

Milosch — Tue, 07 Sep 2010 17:48:29 GMT

uploaded "[[File:PICkit2.jpg]]"

OpenBeacon Tag

Milosch — Tue, 07 Sep 2010 17:25:49 GMT

← Older revision		Revision as of 17:25, 7 September 2010
(One intermediate revision not shown)
Line 7:		Line 7:
	* refer to [[Linux Installation Process of Microchip development environment\|our compiler setup instuctions]]		* refer to [[Linux Installation Process of Microchip development environment\|our compiler setup instuctions]]

		+	=== Understanding the tag source code ===
	[[File:Sputnik-25C3.jpg\|200px\|thumb\|right\|Spurnik tag as used on the 25C3 CCC congress]]		[[File:Sputnik-25C3.jpg\|200px\|thumb\|right\|Spurnik tag as used on the 25C3 CCC congress]]
		+	That's the main loop from ''main.c'' in the tag firmware. The line where the actual packet macro is transmitted to the [[nRF24L01]] chip is highlighted. Basically first the packet is assembled, then the CRC calculated and the data encrypted (shuffle_tx_byteorder is used to adjust byte order to achieve platform independence). As final step RFCMD_Execute() triggers the transmitting process. Interesting feature ot this code is that the packet macro is prepended by a macro that adjust the transmit power on every transmission (''g_MacroBeacon.rf_setup'').
		+
		+	<syntaxhighlight lang="c" highlight=38>
		+	while (1)
		+	{
		+	g_MacroBeacon.rf_setup = NRF_RFOPTIONS \| ((i & 3) << 1);
		+	g_MacroBeacon.env.pkt.hdr.size = sizeof (TBeaconTracker);
		+	g_MacroBeacon.env.pkt.hdr.proto = RFBPROTO_BEACONTRACKER;
		+	g_MacroBeacon.env.pkt.flags = CONFIG_PIN_SENSOR ? 0 : RFBFLAGS_SENSOR;
		+	g_MacroBeacon.env.pkt.strength = i;
		+	g_MacroBeacon.env.pkt.seq = htonl (seq);
		+	g_MacroBeacon.env.pkt.oid = htonl (oid);
		+	g_MacroBeacon.env.pkt.reserved = 0;
		+	crc = crc16 (g_MacroBeacon.env.datab,
		+	sizeof (g_MacroBeacon.env.pkt) -
		+	sizeof (g_MacroBeacon.env.pkt.crc));
		+	g_MacroBeacon.env.pkt.crc = htons (crc);
		+
		+	// update code_block so on next power up
		+	// the seq will be higher or equal
		+	crc = seq >> 16;
		+	if (crc == 0xFFFF)
		+	break;
		+	if (crc == code_block)
		+	store_incremented_codeblock ();
		+
		+	// encrypt my data
		+	shuffle_tx_byteorder ();
		+	xxtea_encode ();
		+	shuffle_tx_byteorder ();
		+
		+	// reset touch sensor pin
		+	TRISA = CONFIG_CPU_TRISA & ~0x02;
		+	CONFIG_PIN_SENSOR = 0;
		+	sleep_jiffies (JIFFIES_PER_MS (10) +
		+	(rand () % JIFFIES_PER_MS (180)));
		+	CONFIG_PIN_SENSOR = 1;
		+	TRISA = CONFIG_CPU_TRISA;
		+
		+	// send it away
		+	nRFCMD_Macro ((unsigned char *) &g_MacroBeacon);
		+	status = (i & 0xF) == 0;
		+
		+	if (status)
		+	CONFIG_PIN_LED = 1;
		+	nRFCMD_Execute ();
		+	if (status)
		+	CONFIG_PIN_LED = 0;
		+
		+	if (++i >= 4)
		+	{
		+	i = 0;
		+	seq++;
		+	}
		+	}
		+	</syntaxhighlight>
		+
	[[File:OpenBeaconRoundTag.jpg\|200px\|thumb\|right\|round OpenBeacon tag]]		[[File:OpenBeaconRoundTag.jpg\|200px\|thumb\|right\|round OpenBeacon tag]]

OpenBeacon USB

Milosch — Tue, 07 Sep 2010 16:57:58 GMT

Accessing OpenBeacon USB:

← Older revision		Revision as of 16:57, 7 September 2010
(One intermediate revision not shown)
Line 26:		Line 26:

	== Accessing OpenBeacon USB ==		== Accessing OpenBeacon USB ==
		+	[[File:OpenBeaconUSBPowered.jpg\|350px\|thumb\|right\|OpenBeacon USB stand alone meshing system by using an AC USB charger]]

	Under Linux we personally prefer the "cu" command line tool from uucp-Package to access		Under Linux we personally prefer the "cu" command line tool from uucp-Package to access

OpenBeacon Blinkenlights

Milosch — Tue, 07 Sep 2010 15:38:34 GMT

OpenBeacon Blinkenlights project:

← Older revision		Revision as of 15:38, 7 September 2010
(2 intermediate revisions not shown)
Line 2:		Line 2:
	[[Category:OpenBeaconHardware]]		[[Category:OpenBeaconHardware]]
	[[Category:BitmanufakturProject]]		[[Category:BitmanufakturProject]]
		+
		+	[[File:Blinkenlight.jpg\|right\|thumb\|350px\|960 OpenBeacon 2.4GHz real time controlled Halogen dimmers in action]]

	=== OpenBeacon Blinkenlights project ===		=== OpenBeacon Blinkenlights project ===
Line 15:		Line 17:
	Schematics and PCB layout files for the dimmers are released under a Creative Commons license.		Schematics and PCB layout files for the dimmers are released under a Creative Commons license.

-	Some impressions are [http://flickr.com/search/show/?q=blinkenlights+toronto available at flickr.com] ~~and [http://examplesof~~.~~com/art/illustration-art/basil_wolverton_wall_portrait.jpg Examples of Illustration Art].~~	+	Some impressions are [http://flickr.com/search/show/?q=blinkenlights+toronto available at flickr.com].
-		+
-	~~{{#ev:youtube\|jTZosieGhIQ}}~~	+

-	{{#ev:youtube\|q_LxikyXpFU}}	+	{{#ev:youtube\|jTZosieGhIQ}}{{#ev:youtube\|q_LxikyXpFU}}

	=== Credits ===		=== Credits ===

	Hardware and software design for OpenBeacon based solutions is done by [http://www.bitmanufaktur.de Milosch Meriac] and [http://www.bitmanufaktur.de Brita Meriac]. Blinkenlights specific adaptions were done by [http://www.caiaq.de Daniel Mack].		Hardware and software design for OpenBeacon based solutions is done by [http://www.bitmanufaktur.de Milosch Meriac] and [http://www.bitmanufaktur.de Brita Meriac]. Blinkenlights specific adaptions were done by [http://www.caiaq.de Daniel Mack].

OpenBeacon Tag

Milosch — Tue, 07 Sep 2010 15:33:40 GMT

← Older revision		Revision as of 15:33, 7 September 2010
(2 intermediate revisions not shown)
Line 1:		Line 1:
	[[Category:OpenBeacon]]		[[Category:OpenBeacon]]
	[[Category:OpenBeaconHardware]]		[[Category:OpenBeaconHardware]]
-
-	~~== Hardware ==~~
-	* The [[OpenBeacon Tag]] consists of
-	** [[nRF24L01]] 2.4GHz transceiver (1/2MBps)
-	** [http://ww1.microchip.com/downloads/en/DeviceDoc/41202F-print.pdf PIC16F684] PIC14 microcontroller

	== Programming Work Flow ==		== Programming Work Flow ==
Line 11:		Line 6:
	svn co svn co https://openbeacon.svn.sourceforge.net/svnroot/openbeacon/trunk/firmware/pic16/tag/ openbeacon		svn co svn co https://openbeacon.svn.sourceforge.net/svnroot/openbeacon/trunk/firmware/pic16/tag/ openbeacon
	* refer to [[Linux Installation Process of Microchip development environment\|our compiler setup instuctions]]		* refer to [[Linux Installation Process of Microchip development environment\|our compiler setup instuctions]]
		+
		+	[[File:Sputnik-25C3.jpg\|200px\|thumb\|right\|Spurnik tag as used on the 25C3 CCC congress]]
		+	[[File:OpenBeaconRoundTag.jpg\|200px\|thumb\|right\|round OpenBeacon tag]]
		+
		+	== Hardware ==
		+	* The [[OpenBeacon Tag]] consists of
		+	** [[nRF24L01]] 2.4GHz transceiver (1/2MBps)
		+	** [http://ww1.microchip.com/downloads/en/DeviceDoc/41202F-print.pdf PIC16F684] PIC14 microcontroller

	* download area for schematics and layout:		* download area for schematics and layout:

OpenBeacon USB

Milosch — Tue, 07 Sep 2010 15:26:36 GMT

← Older revision		Revision as of 15:26, 7 September 2010
(3 intermediate revisions not shown)
Line 1:		Line 1:
		+	[[File:OpenBeaconUSB.jpg\|right\|thumb\|350px\|OpenBeacon USB Stick]]
		+
		+	__TOC__
		+
	[[Category:OpenBeacon]]		[[Category:OpenBeacon]]
	[[Category:OpenBeaconHardware]]		[[Category:OpenBeaconHardware]]

	== Introduction ==		== Introduction ==
-		+	For mobile OpenBeacon applications the OpenBeacon USB stick can be used. The device contains a freely programmable 32 bit ARM controller. It can be reprogrammed without special tools over USB. We released the firmware under GPL license.
-	~~We've just released the latest~~ OpenBeacon ~~hardware -~~ the OpenBeacon USB stick. The device contains a freely programmable 32 bit ARM controller. It can be reprogrammed without special tools over USB. We released the firmware under GPL license.	+

	== Firmware Versions ==		== Firmware Versions ==

OpenBeacon Base Station 1

Milosch — Tue, 07 Sep 2010 15:21:23 GMT

Hardware:

← Older revision		Revision as of 15:21, 7 September 2010
(One intermediate revision not shown)
Line 4:		Line 4:
	== Hardware ==		== Hardware ==

-	[[~~Image~~:~~OpenBeacon-PoE~~.~~JPG~~\|right\|\|~~200px~~\|aluminum cased reader]]	+	[[File:OpenBeaconPoE1.jpg\|right\|\|150px\|aluminum cased reader]]

	This base station is a Power-over-Ethernet (according to IEEE802.3af) enabled design using a closed source Ubicom Ethernet-enabled Microcontroller.		This base station is a Power-over-Ethernet (according to IEEE802.3af) enabled design using a closed source Ubicom Ethernet-enabled Microcontroller.

File:OpenBeaconPoE1.jpg

Milosch — Tue, 07 Sep 2010 15:19:32 GMT

uploaded a new version of "[[File:OpenBeaconPoE1.jpg]]" Test 1

File:OpenBeaconPoE1.jpg

Milosch — Tue, 07 Sep 2010 15:12:57 GMT

uploaded "[[File:OpenBeaconPoE1.jpg]]" First version of OpenBeacon PoE reader

File:OpenBeacon-PoE.JPG

Milosch — Tue, 07 Sep 2010 14:59:34 GMT

uploaded a new version of "[[File:OpenBeacon-PoE.JPG]]"

File:OpenBeacon-PoE.JPG

Milosch — Tue, 07 Sep 2010 14:58:41 GMT

uploaded "[[File:OpenBeacon-PoE.JPG]]" EasyReader PoE I - old version.

OpenBeacon Active RFID Project

Milosch — Tue, 07 Sep 2010 14:56:35 GMT

Getting Started with OpenBeacon:

← Older revision		Revision as of 14:56, 7 September 2010
(One intermediate revision not shown)
Line 8:		Line 8:

	== OpenBeacon based Applications or Systems ==		== OpenBeacon based Applications or Systems ==
		+	[[File:Blinkenlight.jpg\|200px\|right\|thumb\|OpenBeacon @ Blinkenlights Stereoscope in Toronto]]
	<categorytree mode=pages hideroot=on>OpenBeaconHardware</CategoryTree>		<categorytree mode=pages hideroot=on>OpenBeaconHardware</CategoryTree>

	== Getting Started with OpenBeacon ==		== Getting Started with OpenBeacon ==
		+	[[File:PoEII-s.jpg\|200px\|right\|thumb\|OpenBeacon Ethernet EasyReader PoE II]]
	* List of currently supported [[:Category:OpenBeaconHardware\|hardware platforms]]		* List of currently supported [[:Category:OpenBeaconHardware\|hardware platforms]]
	* [[Microchip_Processor\|Setting up the OpenBeacon tag development environment]]		* [[Microchip_Processor\|Setting up the OpenBeacon tag development environment]]
Line 18:		Line 20:

	== OpenBeacon Hardware Development==		== OpenBeacon Hardware Development==
-	[[~~Image~~:Sputnik-25C3.jpg\|~~150px~~\|right\|thumb\|25C3 OpenBeacon Tag]]	+	[[File:Sputnik-25C3.jpg\|200px\|right\|thumb\|25C3 OpenBeacon Tag]]
	* [[OpenBeacon System\|Overview]]		* [[OpenBeacon System\|Overview]]
	* [[OpenBeacon Tag\|Tag]]		* [[OpenBeacon Tag\|Tag]]

File:Blinkenlight.jpg

Milosch — Tue, 07 Sep 2010 14:53:26 GMT

uploaded "[[File:Blinkenlight.jpg]]" Blinkenlights Stereoscope Toronto at Nuit Blanche