Openmoko - User contributions [en]

Main Page/de

2010-10-26T11:03:46Z

Thomasgruebler:

{{Languages|Main Page}}
__NOTOC__
__NOEDITSECTION__ [[Image:Freerunner02.gif|thumb|150px|right|Neo FreeRunners]]

<div style="padding: 2.5ex; text-align: center; font: bold x-large sans">Openmoko™ - Open. Mobile. Free.</div>

Openmoko™ ist ein Projekt, das als Ziel die Bereitstellung eines Mobiltelefons mit einem Open Source Softwarestack hat. OpenMoko Verkauft derzeit das [[Neo FreeRunner/de|Neo FreeRunner]] Telefon an fortgeschrittene Anwender und startet den Verkauf an die breite Öffentlichkeit sobald die Software weiterentwickelt ist.

Der OpenMoko-Stack, der einen vollständigen X-Server enthält, erlaubt es den Benutzern und Entwicklern die mobile Hardware Plattform in ein einzigartiges Produkt umzuwandeln. Unsere Lizenz gibt den Entwicklern und Anwendern die Freiheit kosmetische Aufbesserungen oder radikale Veränderungen durchzuführen - wechsel die Tapeten oder baue das ganze Haus neu! Sie gibt Ihnen die Freiheit, zum Beispiel das Telefon in ein medizinisches oder Point-of-Sale Gerät umzuwandeln oder die Freiheit einfach Ihre Lieblingsoftware zu installieren. Darüberhinaus ist nicht nur die Software frei, sondern wir haben auch die CAD-Dateien des Gerätes veröffentlicht und unter die Creative Commons Lizenz gestellt. Auf der Linux World 2008 werden wir auch die Schaltpläne dazu veröffentlichen.

<div style="clear:both"> </div>

<table class="wikitable" cellspacing="4" cellpadding="6" width="100%" style="color:white">
<tr style="background:#ff6600; text-align:center; font-weight:bold">
<td width="50%">Neuigkeiten und Veranstaltungen</td>
<td width="50%">Neu auf Openmoko?</td>
</tr>
<tr valign="top" style="background:#333333">
<td>
{{News}}
<br>
Ältere News: [[News_Archive|News Archiv]]
</td>
<td>
===<font color=white>Über Openmoko</font>===
* [[Introduction/de|Einführung]]
* [[Why Openmoko|Was ist Openmoko]]
* [[Neo FreeRunner/de|Neo FreeRunner Telefon]]
* [[Supported Hardware|Unterstützte Hardware]]
* [[FAQ/de|FAQ]]

===<font color=white>Openmoko besorgen</font>===
* [[Getting Openmoko|Openmoko besorgen]]
* [http://www.openmoko.com Openmoko Inc.]

</td>
</tr>
<tr style="background:#ff6600; text-align:center; font-weight:bold">
<td width="50%">Für Benutzer</td>
<td width="50%">Für Entwickler</td>
</tr>
<tr valign="top" style="background:#333333">
<td>
===<font color=white>Anfang</font>===
* [[Getting Started with your Neo FreeRunner/de | Neo FreeRunner Anfänger Referenz]]
* [[Applications|Anwendungen]]

===<font color=white>Distributionen</font>===
* [[Distributions|Features Vergleichstabelle]]
* [[Om 2008.8|Om 2008.8 (ASU)]] - [[Om 2007.2|Om 2007.2 (old stable)]]
* [[OpenmokoFramework|FSO]] - [[FDOM - a Fat and Dirty OM based distribution|FDOM]] - [[Qtopia / Qt Extended on FreeRunner|Qt Extended]] - [[Debian]] - [[Gentoo]] - [[Android]] - [[Stable Hybrid Release]] - [[Hackable:1]]

===<font color=white>Openmoko Community</font>===
* [[Mailing List Duplicates| Mailinglisten]]
* [[Discussion_Forums| Diskussionsforen]]
* [[Community Repository]]
* [[Development resources | Entwicklungsressourcen]]
</td>
<td>
===<font color=white>Anwendungsentwicklung</font>===
* [[Openmoko developer guide|Openmoko Leitfaden für Entwickler]]
* [[Toolchain]]

* [[Python|Einführung in Python]]
* [http://projects.openmoko.org/ Projekte in unserem GForge]
* [[OpenmokoFramework|Openmoko dbus-basierendes Service-Level Framework]]

===<font color=white>Integration und Distributionen</font>===
* [[OpenEmbedded|OpenEmbedded Distribution Eintwicklungsumgebung]]
* [[MokoMakefile|Openmoko bauen mit Hilfe von MokoMakefile ]]
* [[Opkg|Opkg Paketmanager]]

===<font color=white>Emulation</font>===
* [[Openmoko under QEMU|Openmoko unter QEMU]]
</td>
</tr>
</table>

Artikel sortieren nach [[:Category:Categories|Kategorien]].

Pisi/de

2010-10-23T08:03:33Z

Thomasgruebler: New page: {{Languages|Pisi}} PISI contact synchronization PISI calendar synchronization Pisi ist ein Programm zur Syncro...

{{Languages|Pisi}}

[[Image:SHR-PISI.png|200px|thumb|PISI contact synchronization]]
[[Image:SHR-PISI-dates.png|200px|thumb|PISI calendar synchronization]]

Pisi ist ein Programm zur Syncronisation von PIM-Daten (Kontakte, Kalender).

Unterstützte Kontakte:
* SIM via DBUS (z.B. SHR)
* QTopia Adressbuch (e.g. OM 2008.12)
* LDAP (nur lesen)
* VCF Dateien (lokal / webdav)
* Google Kontakte
* OPIMD

Unterstützte Kalender:
* Google Kalender
* ICalendar Dateien (lokal / webdav)

Zur Installation von Pisi führe folgenden Befehl durch:

<pre>
opkg install pisi
</pre>

Zudem benötigst du eine Konfigurationsdatei .pisi/conf zur synchronisation. Hier ein Beispiel für Google Kalender und Google Kontakte:

[googleCalendar]
description=My Google Calendar
module=calendar_google
user=user@gmail.com
password=secret
calendarid=user@gmail.com

[pimlicodates]
description= Pimlico Dates
module=calendar_ics
path=/home/root/.evolution/calendar/local/system/calendar.ics
postprocess=killall e-calendar-factory

[googlecontacts]
description=Google Contacts Account
module=contacts_google
user=user@gmail.com
password=secret

[remoteIcs]
description= Remote ICS on Webdav
module=calendar_remoteics
url=http://webdav.davserver.net/private/pim/
file=remotecalendar.ics
username=<LOGIN>
password=<PASSWORD>

[shrsim]
description=SHR SIM Card Contacts
module=contacts_dbussim
max_simentries = 250
simentry_name_maxlength=18

<onlyinclude>
{{ApplicationBox|
Name=[[Pisi]]|
Description=PIM synchronization |
Homepage=http://freshmeat.net/projects/pisiom|
Screenshot=No-screenshot.png|
TestedOn=SHR|
PackageName=
}}
</onlyinclude>

[[Category:Office Applications]]
[[Category:PIM]]

Biking

2010-02-03T17:43:35Z

Thomasgruebler: /* Bike Mounts */

The collection of information useful for biking with a Neo.

== Bike Mounts ==
[[Image:Openmoko_mtb_01.jpg|thumb]]
* André Gaul [http://andre.web-yard.de/blog/2008/08/03/neo-freerunner-rocks-hard-rides-free/ documented a complete mounting kit]
* It's just a prototype :) but with some foam around the handlebar and careful positioning to avoid bumps, a [http://www.xmission.com/~bmidgley/neobike.jpg basic attachment] like this might work and makes it easy to "pinch" the screen when you need to finger tap something. [http://blogs.thehumanjourney.net/finds/entry/20080306 Something similar].
* [http://www.rabenfrost.net/openmoko/bikemount/ Images of an interesting bike mount]
* Another mount: [http://comiles.eu/~natanael/wordpress/2008/09/10/fahrradhalterung-fur-den-freerunner/ Description/Parts list (in German)] and [http://comiles.eu/~natanael/wordpress/2008/09/10/bilder-vom-fahrrad-freerunner/ Pictures]
* And [http://blog.printf.net/articles/2008/08/11/an-openmoko-bike-ride another one] "which I don't recommend very highly; I've had the phone come off it (without major damage, which is good) twice now while riding over rough road."
* Thomas' one (also on the picture right): [http://thomasgruebler.dyndns.org/wordpress/?p=306 fully useable for driving downhill :D]
* Nytowl's mount [[Image:bike_mount_small.JPG|thumb]] [http://handheldshell.com/built/bike_mount.php below right] Never had the phone come out of the mount before.

== Power Supply ==
If you want to keep the GPS running and have the screen always on or staying on with a long timeout, you'll need a way to supplement power.

=== Charging via hub ===
Connecting a hub ([http://nabendynamo.de/ Nabendynamo]) like the [http://www.peterwhitecycles.com/schmidt.asp SON] to a self-made or prebuilt charger can supply your device while biking.

The FreeRunner has three different [[Forcing_fast_charge_mode|charging modes]]: 100mA, 500mA and 1A. 100mA seems to be too low, as it is said, that the FreeRunner draws 100mA current even when it is switched off. A hub dynamo provides 500mA. If you want to use your lights while charging you need to connect the lights in series to the charger. At least the SON will increase the voltage and still delivers the same current. But you need a bypass circuit in case of less current draw of the charger when the battery is full.

Using an USB connection with that ID resistor for 1A mode provides the advantages that the charging mode is automatically correct.
This might be important if you stop frequently and so cause some kind of power "disconnect" and you do not want
to select the charge mode all the time. 1A mode does not harm the hub dynamo but if the dynamo can provide the 500mA also
at higher voltages, you can gain more charge current than in 500mA mode if you have a switching regulator.
For example if the dynamo would provide 10V 500mA and you would have a 100% efficient regulator,
you would have 5V 1A.

==== Commercial Chargers ====
* [[Zzing]]
* [http://www.jawetec.de/index.php?content=bikecharger&framing=radsport JaWeTec Bike Charger]
* There is a prototype of a hub featuring built-in USB-out which will hopefully be ready for mass market soon.
* The [http://www.ikonglobal.com/ ''Pedal & Power''] rim dynamo supplies 12 V and may be useful with an appropriate 12 V to USB adaptor, like [http://www.maplin.co.uk/Module.aspx?ModuleNo=228257&doy=9m3&C=SO&U=strat15 Maplin's A23JH]

==== self-made chargers ====
* [http://www.heise.de/kiosk/archiv/ct/07/23/190 Article (German) in c't 23/2007, page 190]
* maybe 6V [http://www.forumslader.de/6V-Version-des-Rad-Forum-Ladegeraets.125.0.html Forumslader] (You need at least one diode in series to be within the maximum ratings of the power managment IC and the FET switches in FreeRunner.)
Will fry FR nevertheless, as FR might stop to take up any current and then the 6V still creep thru the diode.(jOERG)
* [http://www.iki.fi/~msmakela/electronics/dynamo5v/ Makela]

Linear regulator above might be replaced by [http://www.dimensionengineering.com/DE-SW050.htm DE-SW050].

=== Alternatives ===
If you decide to try solar, it's recommended to get a flexible panel and attach it to your backpack or something like that. One nice advantage here is it might also charge even when you're not moving. It's unlikely anything below 7 watts will keep things running. (5v * 1A = 5W).

It might work with an dynamo outside the hub like the one on the [http://www.reelight.com reelight], but it looks like their coil produces only 3vAC so it makes sense to use a custom coil.

An extra battery like [http://www.dealextreme.com/details.dx/sku.3060 Rechargeable USB Emergency Power Backup Pack 2400mAh $14.43] can also be useful for extending battery life-time.

== Software for biking ==

* [[TangoGPS]] + [http://blogs.thehumanjourney.net/finds/entry/20080826 OSM Cycle data]
* [[BikeAtor]] + [http://www.opkg.org/package_175.html Bikeator opkg.org webpage]
* {{opkg.org|178|bicirutas}} - Looks for mtb routes in www.bicirutas.net
* [[Navit]]
* [http://wiki.openstreetmap.org/index.php/Rana Rana] (uses [[Installing Pyroute|Pyroute]])
* [http://www.neo1973-germany.de/wiki/pylgrim pylgrim] bitmap map viewer. Dead.
* [[The_Bicycle_Motion_Information_Displayer]]
* [http://wiki.openstreetmap.org/index.php/Mumpot Mumpot]

=== See also ===
* [[GPS applications]]

== Heart Rate Monitor ==

According to [http://www.mail-archive.com/community@lists.openmoko.org/msg11248.html mailing list discussions] some heart rate monitors use [http://thisisant.com/index.php?section=5 ANT]. Due to the modern chip cases building a reliable homemade receiver seems to be difficult.

=== HRM Links ===
* [http://www.mikrocontroller.net/articles/Pulsuhrempf%C3%A4nger_mit_AVR_Butterfly German Microcontroller Wiki], Circuit diagram and DSP Simulation.

== Other Hardware ==
* [http://www.obico.de oBiCo] - An open bicycle linux computer - seems to be alive, but nothing there yet.

= External links =
*[http://www.opencyclemap.org/ OpenCycleMap.org - the OpenStreetMap Cycle Map]
*[http://www.gravitystorm.co.uk/shine/archives/category/openstreetmap/ OpenStreetMap Blog]

[[Category:Add-on data]]

Biking

2009-09-26T10:22:47Z

Thomasgruebler:

The collection of information useful for biking with a Neo.

== Bike Mounts ==
[[Image:Openmoko_mtb_01.jpg|thumb]]
* André Gaul [http://andre.web-yard.de/blog/2008/08/03/neo-freerunner-rocks-hard-rides-free/ documented a complete mounting kit]
* It's just a prototype :) but with some foam around the handlebar and careful positioning to avoid bumps, a [http://www.xmission.com/~bmidgley/neobike.jpg basic attachment] like this might work and makes it easy to "pinch" the screen when you need to finger tap something. [http://blogs.thehumanjourney.net/finds/entry/20080306 Something similar].
* [http://www.rabenfrost.net/openmoko/bikemount/ Images of an interesting bike mount]
* Another mount: [http://comiles.eu/~natanael/wordpress/2008/09/10/fahrradhalterung-fur-den-freerunner/ Description/Parts list (in German)] and [http://comiles.eu/~natanael/wordpress/2008/09/10/bilder-vom-fahrrad-freerunner/ Pictures]
* And [http://blog.printf.net/articles/2008/08/11/an-openmoko-bike-ride another one] "which I don't recommend very highly; I've had the phone come off it (without major damage, which is good) twice now while riding over rough road."
* Thomas' one (also on the picture right): [http://crct-robots.eu/wordpress/?p=306 fully useable for driving downhill :D]

== Power Supply ==
If you want to keep the GPS running and have the screen always on or staying on with a long timeout, you'll need a way to supplement power.

=== Charging via hub ===
Connecting a hub ([http://nabendynamo.de/ Nabendynamo]) like the [http://www.peterwhitecycles.com/schmidt.asp SON] to a self-made or prebuilt charger can supply your device while biking.

The FreeRunner has three different [[Forcing_fast_charge_mode|charging modes]]: 100mA, 500mA and 1A. 100mA seems to be too low, as it is said, that the FreeRunner draws 100mA current even when it is switched off. A hub dynamo provides 500mA. If you want to use your lights while charging you need to connect the lights in series to the charger. At least the SON will increase the voltage and still delivers the same current. But you need a bypass circuit in case of less current draw of the charger when the battery is full.

Using an USB connection with that ID resistor for 1A mode provides the advantages that the charging mode is automatically correct.
This might be important if you stop frequently and so cause some kind of power "disconnect" and you do not want
to select the charge mode all the time. 1A mode does not harm the hub dynamo but if the dynamo can provide the 500mA also
at higher voltages, you can gain more charge current than in 500mA mode if you have a switching regulator.
For example if the dynamo would provide 10V 500mA and you would have a 100% efficient regulator,
you would have 5V 1A.

==== Commercial Chargers ====
* [[Zzing]]
* [http://www.jawetec.de/index.php?content=bikecharger&framing=radsport JaWeTec Bike Charger]
* There is a prototype of a hub featuring built-in USB-out which will hopefully be ready for mass market soon.
* The [http://www.ikonglobal.com/ ''Pedal & Power''] rim dynamo supplies 12 V and may be useful with an appropriate 12 V to USB adaptor, like [http://www.maplin.co.uk/Module.aspx?ModuleNo=228257&doy=9m3&C=SO&U=strat15 Maplin's A23JH]

==== self-made chargers ====
* [http://www.heise.de/kiosk/archiv/ct/07/23/190 Article (German) in c't 23/2007, page 190]
* maybe 6V [http://www.forumslader.de/6V-Version-des-Rad-Forum-Ladegeraets.125.0.html Forumslader] (You need at least one diode in series to be within the maximum ratings of the power managment IC and the FET switches in FreeRunner.)
Will fry FR nevertheless, as FR might stop to take up any current and then the 6V still creep thru the diode.(jOERG)
* [http://www.iki.fi/~msmakela/electronics/dynamo5v/ Makela]

Linear regulator above might be replaced by [http://www.dimensionengineering.com/DE-SW050.htm DE-SW050].

=== Alternatives ===
If you decide to try solar, it's recommended to get a flexible panel and attach it to your backpack or something like that. One nice advantage here is it might also charge even when you're not moving. It's unlikely anything below 7 watts will keep things running. (5v * 1A = 5W).

It might work with an dynamo outside the hub like the one on the [http://www.reelight.com reelight], but it looks like their coil produces only 3vAC so it makes sense to use a custom coil.

An extra battery like [http://www.dealextreme.com/details.dx/sku.3060 Rechargeable USB Emergency Power Backup Pack 2400mAh $14.43] can also be useful for extending battery life-time.

== Software for biking ==

* [[TangoGPS]] + [http://blogs.thehumanjourney.net/finds/entry/20080826 OSM Cycle data]
* [[BikeAtor]] + [http://www.opkg.org/package_175.html Bikeator opkg.org webpage]
* {{opkg.org|178|bicirutas}} - Looks for mtb routes in www.bicirutas.net
* [[Navit]]
* [http://wiki.openstreetmap.org/index.php/Rana Rana] (uses [[Installing Pyroute|Pyroute]])
* [http://www.neo1973-germany.de/wiki/pylgrim pylgrim] bitmap map viewer. Dead.
* [[The_Bicycle_Motion_Information_Displayer]]
* [http://wiki.openstreetmap.org/index.php/Mumpot Mumpot]

=== See also ===
* [[GPS applications]]

== Heart Rate Monitor ==

According to [http://www.mail-archive.com/community@lists.openmoko.org/msg11248.html mailing list discussions] some heart rate monitors use [http://thisisant.com/index.php?section=5 ANT]. Due to the modern chip cases building a reliable homemade receiver seems to be difficult.

=== HRM Links ===
* [http://www.mikrocontroller.net/articles/Pulsuhrempf%C3%A4nger_mit_AVR_Butterfly German Microcontroller Wiki], Circuit diagram and DSP Simulation.

== Other Hardware ==
* [http://www.obico.de oBiCo] - An open bicycle linux computer - seems to be alive, but nothing there yet.

= External links =
*[http://www.opencyclemap.org/ OpenCycleMap.org - the OpenStreetMap Cycle Map]
*[http://www.gravitystorm.co.uk/shine/archives/category/openstreetmap/ OpenStreetMap Blog]

[[Category:Add-on data]]

File:Openmoko mtb 01.jpg

2009-09-26T10:19:50Z

Thomasgruebler: Openmoko Freerunner mounted on a Mountainbike.

Openmoko Freerunner mounted on a Mountainbike.

Biking

2009-09-25T19:32:11Z

Thomasgruebler: /* Bike Mounts */

The collection of information useful for biking with a Neo.

== Bike Mounts ==

* André Gaul [http://andre.web-yard.de/blog/2008/08/03/neo-freerunner-rocks-hard-rides-free/ documented a complete mounting kit]
* It's just a prototype :) but with some foam around the handlebar and careful positioning to avoid bumps, a [http://www.xmission.com/~bmidgley/neobike.jpg basic attachment] like this might work and makes it easy to "pinch" the screen when you need to finger tap something. [http://blogs.thehumanjourney.net/finds/entry/20080306 Something similar].
* [http://www.rabenfrost.net/openmoko/bikemount/ Images of an interesting bike mount]
* Another mount: [http://comiles.eu/~natanael/wordpress/2008/09/10/fahrradhalterung-fur-den-freerunner/ Description/Parts list (in German)] and [http://comiles.eu/~natanael/wordpress/2008/09/10/bilder-vom-fahrrad-freerunner/ Pictures]
* And [http://blog.printf.net/articles/2008/08/11/an-openmoko-bike-ride another one] "which I don't recommend very highly; I've had the phone come off it (without major damage, which is good) twice now while riding over rough road."
* Thomas' one: [http://crct-robots.eu/wordpress/?p=306 fully useable for driving downhill :D]

== Power Supply ==
If you want to keep the GPS running and have the screen always on or staying on with a long timeout, you'll need a way to supplement power.

=== Charging via hub ===
Connecting a hub ([http://nabendynamo.de/ Nabendynamo]) like the [http://www.peterwhitecycles.com/schmidt.asp SON] to a self-made or prebuilt charger can supply your device while biking.

The FreeRunner has three different [[Forcing_fast_charge_mode|charging modes]]: 100mA, 500mA and 1A. 100mA seems to be too low, as it is said, that the FreeRunner draws 100mA current even when it is switched off. A hub dynamo provides 500mA. If you want to use your lights while charging you need to connect the lights in series to the charger. At least the SON will increase the voltage and still delivers the same current. But you need a bypass circuit in case of less current draw of the charger when the battery is full.

Using an USB connection with that ID resistor for 1A mode provides the advantages that the charging mode is automatically correct.
This might be important if you stop frequently and so cause some kind of power "disconnect" and you do not want
to select the charge mode all the time. 1A mode does not harm the hub dynamo but if the dynamo can provide the 500mA also
at higher voltages, you can gain more charge current than in 500mA mode if you have a switching regulator.
For example if the dynamo would provide 10V 500mA and you would have a 100% efficient regulator,
you would have 5V 1A.

==== Commercial Chargers ====
* [[Zzing]]
* [http://www.jawetec.de/index.php?content=bikecharger&framing=radsport JaWeTec Bike Charger]
* There is a prototype of a hub featuring built-in USB-out which will hopefully be ready for mass market soon.
* The [http://www.ikonglobal.com/ ''Pedal & Power''] rim dynamo supplies 12 V and may be useful with an appropriate 12 V to USB adaptor, like [http://www.maplin.co.uk/Module.aspx?ModuleNo=228257&doy=9m3&C=SO&U=strat15 Maplin's A23JH]

==== self-made chargers ====
* [http://www.heise.de/kiosk/archiv/ct/07/23/190 Article (German) in c't 23/2007, page 190]
* maybe 6V [http://www.forumslader.de/6V-Version-des-Rad-Forum-Ladegeraets.125.0.html Forumslader] (You need at least one diode in series to be within the maximum ratings of the power managment IC and the FET switches in FreeRunner.)
Will fry FR nevertheless, as FR might stop to take up any current and then the 6V still creep thru the diode.(jOERG)
* [http://www.iki.fi/~msmakela/electronics/dynamo5v/ Makela]

Linear regulator above might be replaced by [http://www.dimensionengineering.com/DE-SW050.htm DE-SW050].

=== Alternatives ===
If you decide to try solar, it's recommended to get a flexible panel and attach it to your backpack or something like that. One nice advantage here is it might also charge even when you're not moving. It's unlikely anything below 7 watts will keep things running. (5v * 1A = 5W).

It might work with an dynamo outside the hub like the one on the [http://www.reelight.com reelight], but it looks like their coil produces only 3vAC so it makes sense to use a custom coil.

An extra battery like [http://www.dealextreme.com/details.dx/sku.3060 Rechargeable USB Emergency Power Backup Pack 2400mAh $14.43] can also be useful for extending battery life-time.

== Software for biking ==

* [[TangoGPS]] + [http://blogs.thehumanjourney.net/finds/entry/20080826 OSM Cycle data]
* [[BikeAtor]] + [http://www.opkg.org/package_175.html Bikeator opkg.org webpage]
* {{opkg.org|178|bicirutas}} - Looks for mtb routes in www.bicirutas.net
* [[Navit]]
* [http://wiki.openstreetmap.org/index.php/Rana Rana] (uses [[Installing Pyroute|Pyroute]])
* [http://www.neo1973-germany.de/wiki/pylgrim pylgrim] bitmap map viewer. Dead.
* [[The_Bicycle_Motion_Information_Displayer]]
* [http://wiki.openstreetmap.org/index.php/Mumpot Mumpot]

=== See also ===
* [[GPS applications]]

== Heart Rate Monitor ==

According to [http://www.mail-archive.com/community@lists.openmoko.org/msg11248.html mailing list discussions] some heart rate monitors use [http://thisisant.com/index.php?section=5 ANT]. Due to the modern chip cases building a reliable homemade receiver seems to be difficult.

=== HRM Links ===
* [http://www.mikrocontroller.net/articles/Pulsuhrempf%C3%A4nger_mit_AVR_Butterfly German Microcontroller Wiki], Circuit diagram and DSP Simulation.

== Other Hardware ==
* [http://www.obico.de oBiCo] - An open bicycle linux computer - seems to be alive, but nothing there yet.

= External links =
*[http://www.opencyclemap.org/ OpenCycleMap.org - the OpenStreetMap Cycle Map]
*[http://www.gravitystorm.co.uk/shine/archives/category/openstreetmap/ OpenStreetMap Blog]

[[Category:Add-on data]]

Biking

2009-09-25T19:26:24Z

Thomasgruebler: /* Bike Mounts */

The collection of information useful for biking with a Neo.

== Bike Mounts ==

* André Gaul [http://andre.web-yard.de/blog/2008/08/03/neo-freerunner-rocks-hard-rides-free/ documented a complete mounting kit]
* It's just a prototype :) but with some foam around the handlebar and careful positioning to avoid bumps, a [http://www.xmission.com/~bmidgley/neobike.jpg basic attachment] like this might work and makes it easy to "pinch" the screen when you need to finger tap something. [http://blogs.thehumanjourney.net/finds/entry/20080306 Something similar].
* [http://www.rabenfrost.net/openmoko/bikemount/ Images of an interesting bike mount]
* Another mount: [http://comiles.eu/~natanael/wordpress/2008/09/10/fahrradhalterung-fur-den-freerunner/ Description/Parts list (in German)] and [http://comiles.eu/~natanael/wordpress/2008/09/10/bilder-vom-fahrrad-freerunner/ Pictures]
* And [http://blog.printf.net/articles/2008/08/11/an-openmoko-bike-ride another one] "which I don't recommend very highly; I've had the phone come off it (without major damage, which is good) twice now while riding over rough road."
* Thomas' one: [http://crct-robots.eu/wordpress/?p=306 fully for downhill driving useable :D]

== Power Supply ==
If you want to keep the GPS running and have the screen always on or staying on with a long timeout, you'll need a way to supplement power.

=== Charging via hub ===
Connecting a hub ([http://nabendynamo.de/ Nabendynamo]) like the [http://www.peterwhitecycles.com/schmidt.asp SON] to a self-made or prebuilt charger can supply your device while biking.

The FreeRunner has three different [[Forcing_fast_charge_mode|charging modes]]: 100mA, 500mA and 1A. 100mA seems to be too low, as it is said, that the FreeRunner draws 100mA current even when it is switched off. A hub dynamo provides 500mA. If you want to use your lights while charging you need to connect the lights in series to the charger. At least the SON will increase the voltage and still delivers the same current. But you need a bypass circuit in case of less current draw of the charger when the battery is full.

Using an USB connection with that ID resistor for 1A mode provides the advantages that the charging mode is automatically correct.
This might be important if you stop frequently and so cause some kind of power "disconnect" and you do not want
to select the charge mode all the time. 1A mode does not harm the hub dynamo but if the dynamo can provide the 500mA also
at higher voltages, you can gain more charge current than in 500mA mode if you have a switching regulator.
For example if the dynamo would provide 10V 500mA and you would have a 100% efficient regulator,
you would have 5V 1A.

==== Commercial Chargers ====
* [[Zzing]]
* [http://www.jawetec.de/index.php?content=bikecharger&framing=radsport JaWeTec Bike Charger]
* There is a prototype of a hub featuring built-in USB-out which will hopefully be ready for mass market soon.
* The [http://www.ikonglobal.com/ ''Pedal & Power''] rim dynamo supplies 12 V and may be useful with an appropriate 12 V to USB adaptor, like [http://www.maplin.co.uk/Module.aspx?ModuleNo=228257&doy=9m3&C=SO&U=strat15 Maplin's A23JH]

==== self-made chargers ====
* [http://www.heise.de/kiosk/archiv/ct/07/23/190 Article (German) in c't 23/2007, page 190]
* maybe 6V [http://www.forumslader.de/6V-Version-des-Rad-Forum-Ladegeraets.125.0.html Forumslader] (You need at least one diode in series to be within the maximum ratings of the power managment IC and the FET switches in FreeRunner.)
Will fry FR nevertheless, as FR might stop to take up any current and then the 6V still creep thru the diode.(jOERG)
* [http://www.iki.fi/~msmakela/electronics/dynamo5v/ Makela]

Linear regulator above might be replaced by [http://www.dimensionengineering.com/DE-SW050.htm DE-SW050].

=== Alternatives ===
If you decide to try solar, it's recommended to get a flexible panel and attach it to your backpack or something like that. One nice advantage here is it might also charge even when you're not moving. It's unlikely anything below 7 watts will keep things running. (5v * 1A = 5W).

It might work with an dynamo outside the hub like the one on the [http://www.reelight.com reelight], but it looks like their coil produces only 3vAC so it makes sense to use a custom coil.

An extra battery like [http://www.dealextreme.com/details.dx/sku.3060 Rechargeable USB Emergency Power Backup Pack 2400mAh $14.43] can also be useful for extending battery life-time.

== Software for biking ==

* [[TangoGPS]] + [http://blogs.thehumanjourney.net/finds/entry/20080826 OSM Cycle data]
* [[BikeAtor]] + [http://www.opkg.org/package_175.html Bikeator opkg.org webpage]
* {{opkg.org|178|bicirutas}} - Looks for mtb routes in www.bicirutas.net
* [[Navit]]
* [http://wiki.openstreetmap.org/index.php/Rana Rana] (uses [[Installing Pyroute|Pyroute]])
* [http://www.neo1973-germany.de/wiki/pylgrim pylgrim] bitmap map viewer. Dead.
* [[The_Bicycle_Motion_Information_Displayer]]
* [http://wiki.openstreetmap.org/index.php/Mumpot Mumpot]

=== See also ===
* [[GPS applications]]

== Heart Rate Monitor ==

According to [http://www.mail-archive.com/community@lists.openmoko.org/msg11248.html mailing list discussions] some heart rate monitors use [http://thisisant.com/index.php?section=5 ANT]. Due to the modern chip cases building a reliable homemade receiver seems to be difficult.

=== HRM Links ===
* [http://www.mikrocontroller.net/articles/Pulsuhrempf%C3%A4nger_mit_AVR_Butterfly German Microcontroller Wiki], Circuit diagram and DSP Simulation.

== Other Hardware ==
* [http://www.obico.de oBiCo] - An open bicycle linux computer - seems to be alive, but nothing there yet.

= External links =
*[http://www.opencyclemap.org/ OpenCycleMap.org - the OpenStreetMap Cycle Map]
*[http://www.gravitystorm.co.uk/shine/archives/category/openstreetmap/ OpenStreetMap Blog]

[[Category:Add-on data]]

Main Page/de

2009-01-10T11:29:43Z

Thomasgruebler:

{{Languages|Main Page}}
__NOTOC__
__NOEDITSECTION__ [[Image:Freerunner02.gif|thumb|150px|right|Neo FreeRunners]]

<div style="padding: 2.5ex; text-align: center; font: bold x-large sans">Openmoko™ - Open. Mobile. Free.</div>

Openmoko™ ist ein Projekt, das als Ziel die Bereitstellung eines Mobiltelefons mit einem Open Source Softwarestack hat. OpenMoko Verkauft derzeit das [[Neo FreeRunner/de|Neo FreeRunner]] Telefon an fortgeschrittene Anwender und startet den Verkauf an die breite Öffentlichkeit sobald die Software weiterentwickelt ist.

Der OpenMoko-Stack, der einen vollständigen X-Server enthält, erlaubt es den Benutzern und Entwicklern die mobile Hardware Plattform in ein einzigartiges Produkt umzuwandeln. Unsere Lizenz gibt den Entwicklern und Anwendern die Freiheit kosmetische Aufbesserungen oder radikale Veränderungen durchzuführen - wechsel die Tapeten oder baue das ganze Haus neu! Sie gibt Ihnen die Freiheit, zum Beispiel das Telefon in ein medizinisches oder Point-of-Sale Gerät umzuwandeln oder die Freiheit einfach Ihre Lieblingsoftware zu installieren. Darüberhinaus ist nicht nur die Software frei, sondern wir haben auch die CAD-Dateien des Gerätes veröffentlicht und unter die Creative Commons Lizenz gestellt. Auf der Linux World 2008 werden wir auch die Schaltpläne dazu veröffentlichen.

<div style="clear:both"> </div>

<table class="wikitable" cellspacing="4" cellpadding="6" width="100%" style="color:white">
<tr style="background:#ff6600; text-align:center; font-weight:bold">
<td width="50%">Neuigkeiten und Veranstaltungen</td>
<td width="50%">Neu auf Openmoko?</td>
</tr>
<tr valign="top" style="background:#333333">
<td>
* 03/1: [http://lists.openmoko.org/nabble.html#nabble-td2103754|a2103754 Neujahrs-Interview] von Sean Moss-Pultz, Openmoko CEO.
* 29/12: [http://wiki.openmoko.org/wiki/Community_Updates/December_29th%2C_2008 Community Updates/29. Dezenber 2008]
* 19/12: [http://lists.openmoko.org/pipermail/announce/2008-December/000028.html Ankündigung] des [http://wiki.openmoko.org/wiki/Om_2008.12_Update Om 2008.12 Update]
* 11/12: Openmoko Hack session at [http://fsfs.in/ fsfs.in] [http://playingwithsid.blogspot.com/2008/12/fsfsin-2008-day-35-openmoko-hack.html (Arky's photoblog)]
* 10/12: [http://wiki.openmoko.org/wiki/Improving_user_experience#optimization_team_case_closed Optimierungsteam & weiteres]
* 06/12: [http://www.cafepress.com/openmoko_inc Offizieller Openmoko Shop eröffnet]
* 02/12: [http://www.koolu.com/ Koolu.com] veröffentlicht [http://git.koolu.org/ Android source] fürs Freerunner! [http://koolu.com/Press-Release/ (Press Release)]
<br />
* [[Weekly Engineering News|Openmoko Weekly Engineering News]]
* [[News Archive|(news archive)]]
</td>
<td>
===<font color=white>Über Openmoko</font>===
* [[Introduction/de|Einführung]]
* [[Why Openmoko|Was ist Openmoko]]
* [[Neo FreeRunner/de|Neo FreeRunner Telefon]]
* [[Supported Hardware|Unterstützte Hardware]]
* [[FAQ/de|FAQ]]

===<font color=white>Openmoko besorgen</font>===
* [[Getting Openmoko|Openmoko besorgen]]
* [http://www.openmoko.com Openmoko Inc.]

</td>
</tr>
<tr style="background:#ff6600; text-align:center; font-weight:bold">
<td width="50%">Für Benutzer</td>
<td width="50%">Für Entwickler</td>
</tr>
<tr valign="top" style="background:#333333">
<td>
===<font color=white>Anfang</font>===
* [[Getting Started with your Neo FreeRunner/de | Neo FreeRunner Anfänger Referenz]]
* [[Applications|Anwendungen]]

===<font color=white>Distributionen</font>===
* [[Distributions|Features Vergleichstabelle]]
* [[Om 2008.8|Om 2008.8 (ASU)]] - [[Om 2007.2|Om 2007.2 (old stable)]]
* [[OpenmokoFramework|FSO]] - [[FDOM - a Fat and Dirty OM based distribution|FDOM]] - [[Qtopia / Qt Extended on FreeRunner|Qt Extended]] - [[Debian]] - [[Gentoo]] - [[Android]] - [[Stable Hybrid Release]] - [[Hackable:1]]

===<font color=white>Openmoko Community</font>===
* [[Mailing List Duplicates| Mailinglisten]]
* [[Discussion_Forums| Diskussionsforen]]
* [[Community Repository]]
* [[Development resources | Entwicklungsressourcen]]
</td>
<td>
===<font color=white>Anwendungsentwicklung</font>===
* [[Openmoko developer guide|Openmoko Leitfaden für Entwickler]]
* [[Toolchain]]

* [[Python|Einführung in Python]]
* [http://projects.openmoko.org/ Projekte in unserem GForge]
* [[OpenmokoFramework|Openmoko dbus-basierendes Service-Level Framework]]

===<font color=white>Integration und Distributionen</font>===
* [[OpenEmbedded|OpenEmbedded Distribution Eintwicklungsumgebung]]
* [[MokoMakefile|Openmoko bauen mit Hilfe von MokoMakefile ]]
* [[Opkg|Opkg Paketmanager]]

===<font color=white>Emulation</font>===
* [[Openmoko under QEMU|Openmoko unter QEMU]]
</td>
</tr>
</table>

Artikel sortieren nach [[:Category:Categories|Kategorien]].

Talk:Accelerometer data retrieval

2009-01-06T18:12:11Z

Thomasgruebler: /* The /sys interface */ new section

I think it could be useful to have a set of raw outputs from the accelerometer as an indication of the (quality of) data we get from reading the raw output.
Would it be an idea to create a few pages where people can post results from performing easy tasks with the accelerometer. I'm thinking:

* A page with the raw data when it is dropped 5 cm onto a soft surface
* A page with the raw data when it is dropped 50 cm onto a soft surface
* A page with the raw data when it is swinging as a pendulum from -90 degrees to +90 degrees. 10cm line
* Same as above 1m line
* Any other "standardized" test..

== The /sys interface ==

Hello
I editied the The /sys interface because it didn't work on my freerunner as it was there.
--[[User:Thomasgruebler|Thomasgruebler]] 18:12, 6 January 2009 (UTC)

Accelerometer data retrieval

2009-01-06T18:10:36Z

Thomasgruebler: /* The /sys interface */

==Scope==

This document describes a way to access the data provided by the
accelerometers. Furthermore the format of the acquired datastream is explained
in detail. This document does not cover the physical basics of acceleration or
the mathematical details on this subject.

==Axis orientation==

To understand the values provided by the accelerometers it is crucial to
understand how the sensors are oriented. In the following I will refer to the
sensors as first and second sensor. The way to access the data sources of
these two will be described later on in this document.

The Z axis is pointing from the display downwards to to the back of the
openmoko. This applies to both of the sensors.

===Orientation of the first sensor===

To explain the axis orientation I have created some images for easier
understanding.

[[Image:Accelerometer_orientation1.png|Axis orientation of the first accelerometer]]

===Orientation of the second sensor===

In contrast to the first sensor the second one is turned 45 degrees around the
Z axis. See the attached image to get a clue about its orientation.

[[Image:Accelerometer_orientation2.png|Axis orientation of the second accelerometer]]

==Data acquisition==

The information from both of the accelerometers is exported through two
different input event based file mappings. These device nodes can be found at
''/dev/input/event2'' and ''/dev/input/event3''.

The sensor I am refering to as the first one is ''event2''. Therefore the second
one is accessible through the ''event3'' device.

These device nodes can be opened by the default filesystems calls for reading
files. The data can be read from the stream as soon as the sensor measures it. Note that since the data is exported as normal files you can easily e.g. use netcat to stream the accelerometer data over bluetooth to your laptop to a control a game running on your laptop.

==Data structure==

To be able to use the measured data it is important to understand the format
in which the data is provided.
The structure of the given data is based on the kernel input event message
system which exports the following data structure:

<pre>
struct input_event {
struct timeval time;
__u16 type;
__u16 code;
__s32 value;
};
</pre>

The data is written to the stream message by message. Therefore the minimal
used blocksize is 128 bit (16 byte).

Lets have a look at an example readout of the accelerometer data, divided into
the used sections.

<pre>
|----- time ------| |type| |code| |-value-|
8c66 4819 721c 0006 0002 0002 03a8 0000
8c66 4819 7222 0006 0000 0000 0000 0000
8c66 4819 99e6 0006 0002 0000 0048 0000
8c66 4819 9a36 0006 0002 0001 0024 0000
8c66 4819 9a50 0006 0002 0002 0396 0000
8c66 4819 9a57 0006 0000 0000 0000 0000
</pre>

I think the time structure does not need further explaination. A lot more
interesting is the type, code and value part of every message. Lets take a
closer look at these parts.

===Event types===

The types categorize the incoming messages. All possible types can be found in
the kernel sources or include files in ''INCLUDEDIR/linux/input.h''
During the tests with the accelerometers I observed the fact that only two
different message types are used.

;0x00:
:According to ''linux/input.h'' this event is called ''EV_SYN''. It signals the wish to ''syncronize''. Normally this event is used in combination with code 0x00 to mark the send data complete and therefore applyable.

;0x02:
:This event is called ''EV_REL'' and signals ''relative movement''. It is used to transmit the acceleration the sensors encounter.

The definition should not be taken too seriously in this context, because the
data values provided by the accelerometer always represent the absolute
acceleration measured at the given time.

===Event codes===

Both types of event may supply different codes. These codes can be understood
as some kind of further specification about the specified data values

====Syncronization event codes====

The syncronization event may use quite a lot of codes, as ''linux/input.h''
shows. However the only used one seems to be the 0x00 code.

;0x00:
:This code is refered to as SYN_REPORT. It means that the last dataset was completely transmitted. Therefore the before transmitted set of data values can be considered complete. This means if this message is recieved you may process the given data further.

====Relative movement event codes====

The amount of possible codes for this event type is quite big. The only used
ones are the following ones.

;0x00:
:REL_X - Acceleration in x direction

;0x01:
:REL_Y - Acceleration in y direction

;0x02:
:REL_Z - Acceleration in z direction

The X, Y and Z axis are to be understand as defined in the chapter about [[#Axis_orientation|Axis orientation]].

===A typical message block===

A typical message block consists of 3 messages containing the acceleration
data for every of the three axis followed by a syncronization message to
signal the end of the block.

The following example is such a message block with detailed explanation of its
different messages and data sections.

<pre>
8c66 4819 99e6 0006 0002 0000 0048 0000
|------Time-------| EV_REL REL_X |-Value-|
(Measured acceleration in x axis direction of 72)

8c66 4819 9a36 0006 0002 0001 0024 0000
|------Time-------| EV_REL REL_Y |-Value-|
(Measured acceleration in y axis direction of 36)

8c66 4819 9a50 0006 0002 0002 0396 0000
|------Time-------| EV_REL REL_Z |-Value-|
(Measured acceleration in z axis direction of 918)

8c66 4819 9a57 0006 0000 0000 0000 0000
|------Time-------| EV_SYN SYN_REPORT |-Value-|
(The transmitted data block is complete you may process the given data)
</pre>

==Test application==

A simple test application written in ruby:
<pre>
#!/usr/bin/env ruby
x = 0
y = 0
z = 0
File.open("/dev/input/event3") do |f|
while true
event = f.read(16).unpack("llSSl")
time = event[0] + event[1] / 1000000.0
type = event[2]
code = event[3]
value = event[4]
if type == 2
x = value if code == 0
y = value if code == 1
z = value if code == 2
end
if type == 0 && code == 0
sum = Math::sqrt(x*x + y*y + z*z).to_i
printf("%5d %5d %5d %5d\n", x, y, z, sum)
end
end
end

</pre>

Equivalent version in python:

<pre>
#!/usr/bin/python
import struct
from math import sqrt

x = 0
y = 0
z = 0
secondsensorfile = "/dev/input/event3"
#int, int, short, short, int
fmt = 'iihhi'
#open file in binary mode
in_file = open(secondsensorfile,"rb")
event = in_file.read(16)
while event:
(time1,time2, type, code, value) = \
struct.unpack(fmt,event)
time = time1 + time2 / 1000000.0

if type == 2:
if code == 0:
x = value
if code == 1:
y = value
if code == 2:
z = value
if type == 0 and code == 0:
sum = int(sqrt(x*x + y*y + z*z))
print x, y, z, sum
event = in_file.read(16)
in_file.close()

</pre>

Equivalent in Perl

<pre>
#!/usr/bin/perl

$x = 0;
$y = 0;
$z = 0;

$secondsensorfile = "/dev/input/event3";
#open file in binary mode
open FILE, $secondsensorfile;
binmode FILE;

while (read FILE, $buf,16) {
($t1,$t2,$type,$code,$value)=unpack "iissi",$buf;
if ($type==2) {
if ($code==0) {$x=$value};
if ($code==1) {$y=$value};
if ($code==2) {$z=$value};
}
if (($type==0) && (code==0)) {
printf "%f %05d %05d %05d\n",$t1+$t2/1000000,$x,$y,$z;
}
}

</pre>

Read the data in C (FIXME: We're not printing times here).

<pre>
#include <stdio.h>
#include <time.h>
#include <sys/times.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <unistd.h>
#include <stdint.h>
#include <assert.h>

struct input_event {
struct timeval time;
uint16_t type;
uint16_t code;
int32_t value;
};

int read_all(int fd, char *buf, int count)
{
int n_read = 0;
while (n_read != count) {
int result = read(fd, buf + n_read, count - n_read);
if (result < 0)
return result;
else if (result == 0)
return n_read;
n_read += result;
}
return n_read;
}

int main(int argc, char *argv[])
{
int fd;
struct input_event ev;

assert(16 == sizeof(struct input_event));

if (argc != 2) {
fprintf(stderr, "missing /dev/input/XXX\n");
return 1;
}

while (1) {
if ((fd = open(argv[1], O_RDONLY)) == -1) {
perror("open");
return 1;
}
int ret = read_all(fd, (char *) &ev, sizeof(struct input_event));
if (ret != sizeof(struct input_event)) {
fprintf(stderr, "ret == %d\n", ret);
perror("read");
return 1;
}
close(fd);
printf("type:%u code:%u value:%d\n", ev.type, ev.code, ev.value);
usleep(500000); /* 2 reads per second, you might want to read more */
}

return 0;
}
</pre>

== The /sys interface ==

To get the sampling rate of the first accelerometer ''lis302dl.1'' :

# cat /sys/devices/platform/lis302dl.1/sample_rate
100

To set the sampling rate :

# echo 400 > /sys/devices/platform/lis302dl.1/sample_rate
# cat /sys/devices/platform/lis302dl.1/sample_rate
400

The other one is ''lis302dl.2''. See [[GTA02 sysfs#Accelerometers]] for the other options.

==See also==
* [[Accelerometer_Fundamentals]]
* [[Gestures]], [http://code.google.com/p/accelges/source/browse/trunk/accelneo/src/accelneo.c code sample]

==External Links==
* [http://projects.openmoko.org/projects/gestures/ Openmoko Motion Gestures]
* [http://en.wikipedia.org/wiki/Accelerometer Wikipedia - Accelerometer]
* [http://dev.borza.ro/demo/Motion-based%20Gesture%20Recognition%20with%20an%20Accelerometer/Paper.pdf Motion-based Gesture Recognition with an Accelerometer - Paper]
* [http://www.youtube.com/watch?v=s5QMW8k5nis YouTube video: Playing with Accelerometers]
* [http://westhoffswelt.de/blog/my_first_openmoko_application.html Magic Eightball Application using the Accelerometers]

[[Category:Accelerometer]]
[[Category:Application Developer]]

Accelerometer data retrieval

2009-01-06T18:03:47Z

Thomasgruebler: /* The /sys interface */

==Scope==

This document describes a way to access the data provided by the
accelerometers. Furthermore the format of the acquired datastream is explained
in detail. This document does not cover the physical basics of acceleration or
the mathematical details on this subject.

==Axis orientation==

To understand the values provided by the accelerometers it is crucial to
understand how the sensors are oriented. In the following I will refer to the
sensors as first and second sensor. The way to access the data sources of
these two will be described later on in this document.

The Z axis is pointing from the display downwards to to the back of the
openmoko. This applies to both of the sensors.

===Orientation of the first sensor===

To explain the axis orientation I have created some images for easier
understanding.

[[Image:Accelerometer_orientation1.png|Axis orientation of the first accelerometer]]

===Orientation of the second sensor===

In contrast to the first sensor the second one is turned 45 degrees around the
Z axis. See the attached image to get a clue about its orientation.

[[Image:Accelerometer_orientation2.png|Axis orientation of the second accelerometer]]

==Data acquisition==

The information from both of the accelerometers is exported through two
different input event based file mappings. These device nodes can be found at
''/dev/input/event2'' and ''/dev/input/event3''.

The sensor I am refering to as the first one is ''event2''. Therefore the second
one is accessible through the ''event3'' device.

These device nodes can be opened by the default filesystems calls for reading
files. The data can be read from the stream as soon as the sensor measures it. Note that since the data is exported as normal files you can easily e.g. use netcat to stream the accelerometer data over bluetooth to your laptop to a control a game running on your laptop.

==Data structure==

To be able to use the measured data it is important to understand the format
in which the data is provided.
The structure of the given data is based on the kernel input event message
system which exports the following data structure:

<pre>
struct input_event {
struct timeval time;
__u16 type;
__u16 code;
__s32 value;
};
</pre>

The data is written to the stream message by message. Therefore the minimal
used blocksize is 128 bit (16 byte).

Lets have a look at an example readout of the accelerometer data, divided into
the used sections.

<pre>
|----- time ------| |type| |code| |-value-|
8c66 4819 721c 0006 0002 0002 03a8 0000
8c66 4819 7222 0006 0000 0000 0000 0000
8c66 4819 99e6 0006 0002 0000 0048 0000
8c66 4819 9a36 0006 0002 0001 0024 0000
8c66 4819 9a50 0006 0002 0002 0396 0000
8c66 4819 9a57 0006 0000 0000 0000 0000
</pre>

I think the time structure does not need further explaination. A lot more
interesting is the type, code and value part of every message. Lets take a
closer look at these parts.

===Event types===

The types categorize the incoming messages. All possible types can be found in
the kernel sources or include files in ''INCLUDEDIR/linux/input.h''
During the tests with the accelerometers I observed the fact that only two
different message types are used.

;0x00:
:According to ''linux/input.h'' this event is called ''EV_SYN''. It signals the wish to ''syncronize''. Normally this event is used in combination with code 0x00 to mark the send data complete and therefore applyable.

;0x02:
:This event is called ''EV_REL'' and signals ''relative movement''. It is used to transmit the acceleration the sensors encounter.

The definition should not be taken too seriously in this context, because the
data values provided by the accelerometer always represent the absolute
acceleration measured at the given time.

===Event codes===

Both types of event may supply different codes. These codes can be understood
as some kind of further specification about the specified data values

====Syncronization event codes====

The syncronization event may use quite a lot of codes, as ''linux/input.h''
shows. However the only used one seems to be the 0x00 code.

;0x00:
:This code is refered to as SYN_REPORT. It means that the last dataset was completely transmitted. Therefore the before transmitted set of data values can be considered complete. This means if this message is recieved you may process the given data further.

====Relative movement event codes====

The amount of possible codes for this event type is quite big. The only used
ones are the following ones.

;0x00:
:REL_X - Acceleration in x direction

;0x01:
:REL_Y - Acceleration in y direction

;0x02:
:REL_Z - Acceleration in z direction

The X, Y and Z axis are to be understand as defined in the chapter about [[#Axis_orientation|Axis orientation]].

===A typical message block===

A typical message block consists of 3 messages containing the acceleration
data for every of the three axis followed by a syncronization message to
signal the end of the block.

The following example is such a message block with detailed explanation of its
different messages and data sections.

<pre>
8c66 4819 99e6 0006 0002 0000 0048 0000
|------Time-------| EV_REL REL_X |-Value-|
(Measured acceleration in x axis direction of 72)

8c66 4819 9a36 0006 0002 0001 0024 0000
|------Time-------| EV_REL REL_Y |-Value-|
(Measured acceleration in y axis direction of 36)

8c66 4819 9a50 0006 0002 0002 0396 0000
|------Time-------| EV_REL REL_Z |-Value-|
(Measured acceleration in z axis direction of 918)

8c66 4819 9a57 0006 0000 0000 0000 0000
|------Time-------| EV_SYN SYN_REPORT |-Value-|
(The transmitted data block is complete you may process the given data)
</pre>

==Test application==

A simple test application written in ruby:
<pre>
#!/usr/bin/env ruby
x = 0
y = 0
z = 0
File.open("/dev/input/event3") do |f|
while true
event = f.read(16).unpack("llSSl")
time = event[0] + event[1] / 1000000.0
type = event[2]
code = event[3]
value = event[4]
if type == 2
x = value if code == 0
y = value if code == 1
z = value if code == 2
end
if type == 0 && code == 0
sum = Math::sqrt(x*x + y*y + z*z).to_i
printf("%5d %5d %5d %5d\n", x, y, z, sum)
end
end
end

</pre>

Equivalent version in python:

<pre>
#!/usr/bin/python
import struct
from math import sqrt

x = 0
y = 0
z = 0
secondsensorfile = "/dev/input/event3"
#int, int, short, short, int
fmt = 'iihhi'
#open file in binary mode
in_file = open(secondsensorfile,"rb")
event = in_file.read(16)
while event:
(time1,time2, type, code, value) = \
struct.unpack(fmt,event)
time = time1 + time2 / 1000000.0

if type == 2:
if code == 0:
x = value
if code == 1:
y = value
if code == 2:
z = value
if type == 0 and code == 0:
sum = int(sqrt(x*x + y*y + z*z))
print x, y, z, sum
event = in_file.read(16)
in_file.close()

</pre>

Equivalent in Perl

<pre>
#!/usr/bin/perl

$x = 0;
$y = 0;
$z = 0;

$secondsensorfile = "/dev/input/event3";
#open file in binary mode
open FILE, $secondsensorfile;
binmode FILE;

while (read FILE, $buf,16) {
($t1,$t2,$type,$code,$value)=unpack "iissi",$buf;
if ($type==2) {
if ($code==0) {$x=$value};
if ($code==1) {$y=$value};
if ($code==2) {$z=$value};
}
if (($type==0) && (code==0)) {
printf "%f %05d %05d %05d\n",$t1+$t2/1000000,$x,$y,$z;
}
}

</pre>

Read the data in C (FIXME: We're not printing times here).

<pre>
#include <stdio.h>
#include <time.h>
#include <sys/times.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <unistd.h>
#include <stdint.h>
#include <assert.h>

struct input_event {
struct timeval time;
uint16_t type;
uint16_t code;
int32_t value;
};

int read_all(int fd, char *buf, int count)
{
int n_read = 0;
while (n_read != count) {
int result = read(fd, buf + n_read, count - n_read);
if (result < 0)
return result;
else if (result == 0)
return n_read;
n_read += result;
}
return n_read;
}

int main(int argc, char *argv[])
{
int fd;
struct input_event ev;

assert(16 == sizeof(struct input_event));

if (argc != 2) {
fprintf(stderr, "missing /dev/input/XXX\n");
return 1;
}

while (1) {
if ((fd = open(argv[1], O_RDONLY)) == -1) {
perror("open");
return 1;
}
int ret = read_all(fd, (char *) &ev, sizeof(struct input_event));
if (ret != sizeof(struct input_event)) {
fprintf(stderr, "ret == %d\n", ret);
perror("read");
return 1;
}
close(fd);
printf("type:%u code:%u value:%d\n", ev.type, ev.code, ev.value);
usleep(500000); /* 2 reads per second, you might want to read more */
}

return 0;
}
</pre>

== The /sys interface ==

To get the sampling rate of the first accelerometer ''spi0.0'' :

# cat /sys/devices/platform/lis302dl.1/sample_rate
100

To set the sampling rate :

# echo 400 > /sys/devices/platform/lis302dl.1/sample_rate
# cat /sys/devices/platform/lis302dl.1/sample_rate
400

The other one is ''spi0.1''. See [[GTA02 sysfs#Accelerometers]] for the other options.

==See also==
* [[Accelerometer_Fundamentals]]
* [[Gestures]], [http://code.google.com/p/accelges/source/browse/trunk/accelneo/src/accelneo.c code sample]

==External Links==
* [http://projects.openmoko.org/projects/gestures/ Openmoko Motion Gestures]
* [http://en.wikipedia.org/wiki/Accelerometer Wikipedia - Accelerometer]
* [http://dev.borza.ro/demo/Motion-based%20Gesture%20Recognition%20with%20an%20Accelerometer/Paper.pdf Motion-based Gesture Recognition with an Accelerometer - Paper]
* [http://www.youtube.com/watch?v=s5QMW8k5nis YouTube video: Playing with Accelerometers]
* [http://westhoffswelt.de/blog/my_first_openmoko_application.html Magic Eightball Application using the Accelerometers]

[[Category:Accelerometer]]
[[Category:Application Developer]]

User:Thomasgruebler

2009-01-03T10:14:25Z

Thomasgruebler:

My homepages:<br>
http://www.gruebler.at<br>
http://www.crct-robots.eu

User:Thomasgruebler

2009-01-03T10:14:04Z

Thomasgruebler: New page: My homepages: www.gruebler.at www.crct-robots.eu

My homepages:
www.gruebler.at
www.crct-robots.eu

Talk:Wishlist/Sensorbox

2009-01-03T10:12:49Z

Thomasgruebler: /* AVR/PIC */

= Processor discussion =
----
** Please use the ARM processor (32bit address space) - it has no [http://en.wikipedia.org/wiki/Bank_switching Bank switching]; ARM has a big linear directly addressable memory. Can get flashed by this open source tool: [http://tech.groups.yahoo.com/group/lpc21isp/ lpc21isp], [http://groups.yahoo.com/group/lpc21isp/files/ yahoo download (after user registration)].
*** Look e.g. on the cheap [http://www.standardics.nxp.com/products/lpc2000/lpc214x/ LPC214x] quote: "...The LPC214x series is the only ARM7® microcontroller family with full USB 2.0 compliance and USB.org certification..." (LPC2144-LPC2148 has 14 ADC multiplexed channels - two internal ADCs). Chip price: [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=568-1763-ND digikey.com: LPC2144 US$ 8.4], [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=568-1765-ND LPC2148 US$ 11.2]. The [http://en.wikipedia.org/wiki/ARM_architecture ARM architecture] is "old" (from 1983), wildly known, used, efficient(high mips/watt) and uses low power (different kind of deep sleep).
***Test/development/production boards:
****USB powered through USB-flash port, only mentions 2 ADC-ports: [http://www.embeddedartists.com/products/education/edu_2148.php embeddedartists.com: LPC2148 Education Board] (two USB ports - one for programming via a ftdi-chip(USB<->serial) - and one directly connected to LPC2148)
****[http://www.mikrocontroller.net/articles/ARM_MP3/AAC_Player ARM MP3/AAC Player] Quote: "...This is my MP3/AAC player project. The difference to most other players is that decoding is not done on a specialized IC (like VS1001), but directly on the microcontroller. It can play MP3 (all bit rates) and AAC (up to ~256 kbps) from SD card in real time. The project is work in progress..."
****[http://microcontrollershop.com/product_info.php?cPath=315&products_id=2252 LPC2148-based Line-tracing Race Car Robot Kit]
****[http://www.scienceprog.com/arm7-lpc2148-mini-board/ ARM7 LPC2148 mini board], [http://www.scienceprog.com/arm7-base-development-board-for-lpc2148/ ARM7-Base development board for LPC2148]
****ARM1136JF-S-based: [http://www.buglabs.net/ buglabs.net], [http://www.buglabs.net/applications Some applications], [http://bugcommunity.com/wiki/index.php/BUG_Wiki bugcommunity wiki]
****[http://www.gumstix.com/products.html Gumstix]
****AT91SAM7S256 (ARM) based: [http://en.wikipedia.org/wiki/Lego_Mindstorms_NXT Lego Mindstorms NXT], [http://www.teamhassenplug.org/NXT/NXTSoftware.html NXT Programming Software]
****[http://www.visionsystems.de/produkte/6801.html Alekto; DIN RAIL mountable]
****Atmel AT91SAM7X256 based (also ARM): [http://www.makingthings.com/documentation/tutorial/controller-board-overview Controller Board Overview], [http://www.makingthings.com/ makingthings.com], [http://sourceforge.net/projects/makingthings/ sourceforge.net: makingthings]
***Open source support:
****[http://sourceforge.net/projects/lpcusb LPC214x USB stack]
***Links:
****[http://www.nxp.com/pip/LPC2141_42_44_46_48_3.html NXP: LPC2141/42/44/46/48 - Single-chip 16-bit/32-bit microcontrollers]
****[http://rod.info/ARM7Micro ARM7 NXP (formerly a division of Philips) LPC Microcontroller]
****[http://www.embedded.com/design/opensource/200000632?_requestid=1792 Building Bare-Metal ARM Systems with GNU: Part 1 - Getting Started]
****[http://www.siwawi.arubi.uni-kl.de/avr_projects/arm_projects/index.html ARM-Projects]
****[http://www.computer-solutions.co.uk/info/Embedded_tutorials/usb_tutorial.htm Embedded USB - a brief tutorial]
****[http://bas.woodpecker.gotdns.org/ALDS.php ALDS]

--[[User:Glenn|Glenn]] 14:25, 2 November 2008 (UTC)

== [[User:Hns]] ==
This is what has been thought of: a simple processor that still suppports A/D converters and USB. A good candidate appears to be [http://ww1.microchip.com/downloads/en/DeviceDoc/41124c.pdf PIC16C765] Cost is approx. 5 USD.

Using an ARM processor just to convert some samples per second into USB appears to be overkill to me on first though. But the PIC is just one of the options to considered. A drawback appears that the ADC resolution is just 8 bit. This is quite coarse for some sensors. 12 bit would be better...

So what we need:
* single chip
* supports USB and approx. 8 ADC channels without many external components
* low power
* readily available development tools

----

[http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en010172 PIC16C765] is a bad development platform, because it can only be programmed once (OTP). It is also not possible to update to newer enhanced firmware versions for the same reason.

There is also:
*[http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=PIC18F2550-I/SP-ND pic18f2550 US$ 8.2]
*[http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=PIC18F4550-I/P-ND pic18f4550 US$ 8.5]
But for almost the same or a little more, you get much more with ARM.

More:
*PIC16C745: [http://www.iay.org.uk/blog/2003/07/my_very_first_u.html July 25, 2003 My Very First USB Peripheral] Quote: "...For example, I wanted to change the number of buttons and add a couple of LEDs. To do this, you need to build new HID report descriptors and there you run into problems with incomprehensible standards documentation and inconsistent operating systems implementations...One last item that fits in under "firmware" better than anywhere else is the issue of vendor IDs. Like PCI and other "plug and pray" bus systems, your device presents a vendor ID and a product ID so that the host operating system can locate appropriate drivers. Unlike those other systems, there is no "experimental" vendor ID or apparently any way to get a legitimate vendor ID other than paying the USB Implementers Forum a minimum of $1500 every couple of years...If you want a host application of your own talking to a collection of custom peripherals you've designed, though, things are much harder..."
*[http://www.embedds.com/pic18f4550-usb-prototyping-board/ PIC18F4550 USB prototyping board]
*[http://www.embedds.com/pic18f2550-development-board-with-usb-port/ PIC18F2550 development board with USB port]
**[http://www.holger-klabunde.de/usb/18f2550.htm PIC18F2550 Experimentierboard] Quote: "...Es gibt bei Microchip mehrere Code-Beispiele wie man Programme für den PIC schreibt. Als HID (Human Interface Device), über eine spezielle DLL von Microchip oder als CDC-Device (Communication Device Class). Letzteres habe ich hier benutzt. CDC arbeitet [=works] über einen virtuellen COM-Port. Man schreibt seine Programme so als würde man eine serielle Schnittstelle [=interface] ansprechen. Für CDC ist kein spezieller Treiber[=driver] erforderlich..."
*[http://www.semifluid.com/?p=24 PIC18F2550 USB HID Oscilloscope] Quote: "...Using HID means that this oscilloscope does not require drivers (only the oscilloscope software)..."

--[[User:Glenn|Glenn]] 14:23, 2 November 2008 (UTC)

----

Universal (PIC, ARM) USB driver information:
*[http://wiki.sikken.nl/index.php?title=LPCUSB#USB_virtual_COM_port USB virtual COM port]
--[[User:Glenn|Glenn]] 15:45, 2 November 2008 (UTC)

Hello,

I have found this:

http://www.ianstedman.co.uk/Projects/PIC_USB_Interface/pic_usb_interface.html

Greetings

Rene

:Hi Rene - That is fine solution using a ftdi usb<->seriel chip. I use it myself. --[[User:Glenn|Glenn]] 17:41, 3 November 2008 (UTC)

== AVR/PIC ==

I recommend an AVR or PIC.
Since they have no USB Interface, they are both very cheap and are easy to use.
For programming an AVR all needed tools are in the most distros repositorys (gcc-avr, binutils-avr, avrlibc, avrdude).
As USB interface, i recommend using an FTDI USB/Serial changer. They work very fine also with 1MBit Baud.

Every AVR has an integrated I²C, SPI and UART (Serial) Interface. You can connect 8 analog sensors, you have some Hardware Interrupts, Timers, PWM-Outputs,...

http://www.roboternetz.de/wissen/index.php/AVR <br>
http://www.roboternetz.de/wissen/index.php/USB#USB_Interface-Bausteine_.28ICs.29

I'm currently working on an interface to control my robot with the freerunner. I'm using a simple gtk interface that sends some commands over a usb/serial cable to an Atmel ATMega32.

--[[User:Thomasgruebler|Thomasgruebler]] 10:12, 3 January 2009 (UTC)

Talk:Wishlist/Sensorbox

2009-01-03T10:10:41Z

Thomasgruebler: /* AVR/PIC */ new section

= Processor discussion =
----
** Please use the ARM processor (32bit address space) - it has no [http://en.wikipedia.org/wiki/Bank_switching Bank switching]; ARM has a big linear directly addressable memory. Can get flashed by this open source tool: [http://tech.groups.yahoo.com/group/lpc21isp/ lpc21isp], [http://groups.yahoo.com/group/lpc21isp/files/ yahoo download (after user registration)].
*** Look e.g. on the cheap [http://www.standardics.nxp.com/products/lpc2000/lpc214x/ LPC214x] quote: "...The LPC214x series is the only ARM7® microcontroller family with full USB 2.0 compliance and USB.org certification..." (LPC2144-LPC2148 has 14 ADC multiplexed channels - two internal ADCs). Chip price: [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=568-1763-ND digikey.com: LPC2144 US$ 8.4], [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=568-1765-ND LPC2148 US$ 11.2]. The [http://en.wikipedia.org/wiki/ARM_architecture ARM architecture] is "old" (from 1983), wildly known, used, efficient(high mips/watt) and uses low power (different kind of deep sleep).
***Test/development/production boards:
****USB powered through USB-flash port, only mentions 2 ADC-ports: [http://www.embeddedartists.com/products/education/edu_2148.php embeddedartists.com: LPC2148 Education Board] (two USB ports - one for programming via a ftdi-chip(USB<->serial) - and one directly connected to LPC2148)
****[http://www.mikrocontroller.net/articles/ARM_MP3/AAC_Player ARM MP3/AAC Player] Quote: "...This is my MP3/AAC player project. The difference to most other players is that decoding is not done on a specialized IC (like VS1001), but directly on the microcontroller. It can play MP3 (all bit rates) and AAC (up to ~256 kbps) from SD card in real time. The project is work in progress..."
****[http://microcontrollershop.com/product_info.php?cPath=315&products_id=2252 LPC2148-based Line-tracing Race Car Robot Kit]
****[http://www.scienceprog.com/arm7-lpc2148-mini-board/ ARM7 LPC2148 mini board], [http://www.scienceprog.com/arm7-base-development-board-for-lpc2148/ ARM7-Base development board for LPC2148]
****ARM1136JF-S-based: [http://www.buglabs.net/ buglabs.net], [http://www.buglabs.net/applications Some applications], [http://bugcommunity.com/wiki/index.php/BUG_Wiki bugcommunity wiki]
****[http://www.gumstix.com/products.html Gumstix]
****AT91SAM7S256 (ARM) based: [http://en.wikipedia.org/wiki/Lego_Mindstorms_NXT Lego Mindstorms NXT], [http://www.teamhassenplug.org/NXT/NXTSoftware.html NXT Programming Software]
****[http://www.visionsystems.de/produkte/6801.html Alekto; DIN RAIL mountable]
****Atmel AT91SAM7X256 based (also ARM): [http://www.makingthings.com/documentation/tutorial/controller-board-overview Controller Board Overview], [http://www.makingthings.com/ makingthings.com], [http://sourceforge.net/projects/makingthings/ sourceforge.net: makingthings]
***Open source support:
****[http://sourceforge.net/projects/lpcusb LPC214x USB stack]
***Links:
****[http://www.nxp.com/pip/LPC2141_42_44_46_48_3.html NXP: LPC2141/42/44/46/48 - Single-chip 16-bit/32-bit microcontrollers]
****[http://rod.info/ARM7Micro ARM7 NXP (formerly a division of Philips) LPC Microcontroller]
****[http://www.embedded.com/design/opensource/200000632?_requestid=1792 Building Bare-Metal ARM Systems with GNU: Part 1 - Getting Started]
****[http://www.siwawi.arubi.uni-kl.de/avr_projects/arm_projects/index.html ARM-Projects]
****[http://www.computer-solutions.co.uk/info/Embedded_tutorials/usb_tutorial.htm Embedded USB - a brief tutorial]
****[http://bas.woodpecker.gotdns.org/ALDS.php ALDS]

--[[User:Glenn|Glenn]] 14:25, 2 November 2008 (UTC)

== [[User:Hns]] ==
This is what has been thought of: a simple processor that still suppports A/D converters and USB. A good candidate appears to be [http://ww1.microchip.com/downloads/en/DeviceDoc/41124c.pdf PIC16C765] Cost is approx. 5 USD.

Using an ARM processor just to convert some samples per second into USB appears to be overkill to me on first though. But the PIC is just one of the options to considered. A drawback appears that the ADC resolution is just 8 bit. This is quite coarse for some sensors. 12 bit would be better...

So what we need:
* single chip
* supports USB and approx. 8 ADC channels without many external components
* low power
* readily available development tools

----

[http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en010172 PIC16C765] is a bad development platform, because it can only be programmed once (OTP). It is also not possible to update to newer enhanced firmware versions for the same reason.

There is also:
*[http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=PIC18F2550-I/SP-ND pic18f2550 US$ 8.2]
*[http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=PIC18F4550-I/P-ND pic18f4550 US$ 8.5]
But for almost the same or a little more, you get much more with ARM.

More:
*PIC16C745: [http://www.iay.org.uk/blog/2003/07/my_very_first_u.html July 25, 2003 My Very First USB Peripheral] Quote: "...For example, I wanted to change the number of buttons and add a couple of LEDs. To do this, you need to build new HID report descriptors and there you run into problems with incomprehensible standards documentation and inconsistent operating systems implementations...One last item that fits in under "firmware" better than anywhere else is the issue of vendor IDs. Like PCI and other "plug and pray" bus systems, your device presents a vendor ID and a product ID so that the host operating system can locate appropriate drivers. Unlike those other systems, there is no "experimental" vendor ID or apparently any way to get a legitimate vendor ID other than paying the USB Implementers Forum a minimum of $1500 every couple of years...If you want a host application of your own talking to a collection of custom peripherals you've designed, though, things are much harder..."
*[http://www.embedds.com/pic18f4550-usb-prototyping-board/ PIC18F4550 USB prototyping board]
*[http://www.embedds.com/pic18f2550-development-board-with-usb-port/ PIC18F2550 development board with USB port]
**[http://www.holger-klabunde.de/usb/18f2550.htm PIC18F2550 Experimentierboard] Quote: "...Es gibt bei Microchip mehrere Code-Beispiele wie man Programme für den PIC schreibt. Als HID (Human Interface Device), über eine spezielle DLL von Microchip oder als CDC-Device (Communication Device Class). Letzteres habe ich hier benutzt. CDC arbeitet [=works] über einen virtuellen COM-Port. Man schreibt seine Programme so als würde man eine serielle Schnittstelle [=interface] ansprechen. Für CDC ist kein spezieller Treiber[=driver] erforderlich..."
*[http://www.semifluid.com/?p=24 PIC18F2550 USB HID Oscilloscope] Quote: "...Using HID means that this oscilloscope does not require drivers (only the oscilloscope software)..."

--[[User:Glenn|Glenn]] 14:23, 2 November 2008 (UTC)

----

Universal (PIC, ARM) USB driver information:
*[http://wiki.sikken.nl/index.php?title=LPCUSB#USB_virtual_COM_port USB virtual COM port]
--[[User:Glenn|Glenn]] 15:45, 2 November 2008 (UTC)

Hello,

I have found this:

http://www.ianstedman.co.uk/Projects/PIC_USB_Interface/pic_usb_interface.html

Greetings

Rene

:Hi Rene - That is fine solution using a ftdi usb<->seriel chip. I use it myself. --[[User:Glenn|Glenn]] 17:41, 3 November 2008 (UTC)

== AVR/PIC ==

I recommend an AVR or PIC.
Since they have no USB Interface, they are both very cheap and are easy to use.
For programming an AVR all needed tools are in the most distros repositorys (gcc-avr, binutils-avr, avrlibc, avrdude).
As USB interface, i recommend using an FTDI USB/Serial changer. They work very fine also with 1MBit Baud.

Every AVR has an integrated I²C, SPI and UART (Serial) Interface. You can connect 8 analog sensors, you have some Hardware Interrupts, Timers, PWM-Outputs,...

http://www.roboternetz.de/wissen/index.php/AVR
http://www.roboternetz.de/wissen/index.php/USB#USB_Interface-Bausteine_.28ICs.29

Hardware:Neo1973:Alternate Cases:Camera

2009-01-03T09:36:26Z

Thomasgruebler:

Alternate case for the Neo1973, with <strike>rear-mounted</strike> camera module.

==Concept==
A flexible phone is desired that meets most users needs. Camera module should be easily installed or removed (and left in the car) for people that are unable to take cameras into work.

=== cs mount camera ===
* allows use of any standard cs mount (or other lenses with adapters) for superior optical focus & zoom
* cs mount is used because it can be converted to use c mount lenses with a 5mm extension tube
* surface of focal plane array is 12.52mm below top of surface (requiring less room than c mount or many other standard lenses)
* module faces can be exchanged to allow operation in either camera or video-conferencing mode
* lens can easily be unscrewed, converting the image sensor into a useless memory, and replaced with a c/cs mount cap. -- This could disable camera & allow people to bring the phone into work (or you could just remove the entire module)

A strong LED could be used as a close range flash. An ambient light sensor could automatically control this function. This could also be used as a torch.

==Rendered images==
=== cs mount camera (also works with c mount lenses) ===
[http://www.likeasecret.com/Neo1973/Neo1973-Exp_CamCS.mov Neo1973 cs-mount Camera Expansion Module Quicktime rendering]<br />
[[Image:Neo1973-ExpCamCS.png]]

==3D model==
=== cs mount camera ===
[http://www.likeasecret.com/Neo1973/Neo1973-Exp.aoi Neo1973 Art of Illusion 3D Model] - Not fully accurate, just an artistic concept.

==Materials==
* 1 Camera with about 3MP or more for making pictures
* 1 Camera for video conferences.
=== cs mount camera ===
* Aluminum top front of case cover could allow 1" x 32tpi lens mount hole (3.8mm threaded down from surface) made directly into cover.

==Processes==
Stereolithography

==Components==
Camera module with protection<br>
At least 3 Mpx, autofocus!

==Interest==
Leave your nickname here if you are interested in having one made. This is not an order form, but is intended to gauge interest before effort is expended designing the case.<br>

#[[User:changzer|changzer]] maybe it could look nicer than that, but anyway, a camera would be so sweet on this phone
#[[User:cyber_kostyan|cyber_kostyan]]
#[[User:Bootlessjam|Bootlessjam]]
#[[User:Diatessaron|Diatessaron]]
#[[User:Thomas Mathiesen|Thomas Mathiesen]]
#[[User:Gizmhail|Gizmhail]]
#[[User:Fisticuffs|Fisticuffs]]
#[[User:Daniel|Daniel]]
#[[User:Deedend|Deedend]]
#[[User:Aztlek|Aztlek]]
#[[User:Mikesd|Mikesd]] -- Needs to swivel or at very least have a self portrait mirror. FLASH and VIDEO mandatory.
#[[User:Filippo|Filippo]]
#[[User:Beady|beady]]
#[[User:Wvrn|wvrn]] -- A camera is the only thing I am waiting on to buy this phone
#[[User:yvanxxx|yvanxxx]]
#[[User:amarov|amarov]]
#[[User:cedel|cedel]]
#[[User:gwylim|gwylim]]
#[[User:Massa|Humberto Massa]]
#[[User:hhf423|hhf423]]
#[[User:Fursund|Fursund]]
#[[User:Bubbi|Bubbi]]
#[[User:Drizzt|Drizzt]]
#[[User:Pajamabama|Pajamabama]]
#[[User:vozka|vozka]]
#[[User:dlejeune|dlejeune]]
#[[User:AnyWare|AnyWare]]
#[[User:kresp0|kresp0]]
#[[User:sin|sin]]
#[[User:DjAlxor|DjAlxor]]
#[[User:Kf|Kf]]
#[[User:Kylegordon|Kylegordon]]
#[[User:Oatty|Oatty]]
#[[User:nericastillogioleo|nericastillogioleo]]
#[[User:Fradeve11|Fradeve11]]
#[[User:solid|solid]] -- A camera is the only thing I am waiting on to buy this phone. [UPDATE]I posted this comment several months ago. My first generation razr is gimping along. The exterior screen is completely busted and the lcd looks like a purple blob. I am holding off on buying a new phone until I can get a smart phone that replaces all the personal gadgets I have to carry. I need a phone that is a personal music player,a camera and a phone. Having a phone that is deficient in any of the above functions makes it less than smart. I am running out of time. My phone is in worst shape every day. Please just tell us there is a camera in the works, Otherwise I will be buying a non-linux smart phone.
#[[User:Globbi|Globbi]]
#[[User:Madoon|Madoon]]
#[[User:Thomasgruebler|Thomasgruebler]] -- 3MP would be cool
#[[User:Blastur|Blastur]]
#[[User:Tommiku|Tommiku]] -- A camera is the only thing I am waiting on to buy this phone
#[[User:ShakataGaNai|ShakataGaNai]] — it would be nice option to have
#[[User:Bugmenout|Bugmenot]] -- The finishing touch to make it the perfect phone :)
#[[User:rydell|rydell]] -- Definitely the only missing feature! (And a near-critical one)
#[[User:PrtSoftware|PrtSoftware]]
#[[User:bob127|bob127]] -- 3MP would be really nice, I'm also a developer for a phone-related company, I could recommend this phone if it has a camera.
#[[User:Z|Z]] -- Our company would like to develop applications for this phone, the only thing that's stopping us is the lack of a camera
#[[User:dyous87|dyous87]] --A camera would make this the perfect phone for me and I would surely buy it.
#[[User:Massi|Massi]] -- 3MP would be cool
#[[User:jcdemay|jcdemay]] -- a missing feature, don't care if it's not a great one, just need one ;)
#[[User:pokazene_maslo|pokazene_maslo]] -- with flashlight
#[[User:Jackcday|Jackcday]] -- I think it needs a camera, would be great if it could have a very high MPX camera with good software so you could use it as a proper camera.
#[[User:flexd|flexd]] -- This would be excellent for a idea of mine, camera + gps + wifi/gprs/3g/edge fun! :)
#[[User:Duker|Duker]] Would be awesome, especially if the camera (lens component) were removable for those pf us who can't have cameras at work (or court)
#[[User:PipBoy2000|PipBoy2000]]
#[[User:Merire|Merire]] I really want this phone, but I'm not gonna buy one if I can't get a cam.
#[[User:Totoro|totoro]]
#[[User:bacardi55|bacardi55]]
#[[User:jplaville|jplaville]]
#[[User:v0n0|v0n0]]
#[[User:massoo|massoo]] -- A Camera integrated is really cool which will enable to have unified personal gizmo.
#[[User:conbart|conbart]]
#[[User:calavicci|calavicci]] Like others, a camera is all I need to buy the phone.
#[[User:methril|methril]] It's an usefull extra feature.
#[[User:yorick|yorick]] The lack of a camera is a very big disadvantage of this phone (compared to a HTC P3600 for example)
#[[User:Yota_VGA|Yota_VGA]] Absolutely needed!
#[[User:Treviño|Treviño]] A phone doesn't need a camera, but it could be useful to grab fun moments!
#[[User:Daverix|Daverix]] My mobile is the only thing a use to take pictures!
#[[User:snizfast|snizfast]] Would also like a flash unless its good at night
#[[User:oisinmulvihill|Oisin Mulvihill]] I second the 3MP camera and gps so you could geo-tag where the pictures are which is very handy when you want to get back to an interesting place you've come across.
#[[User:dborba|dborba]] 3MP would be ideal.
#[[User:gumpish|gumpish]] -- A camera is the only thing I am waiting on to buy this phone. Every day I pray for the sanity of the development team and that they will realize that any phone that costs over $100USD and doesn't have a camera is worse than useless!
#[[User:Martix|Martix]]
#[[User:Mibo|Michal Bořek]]
#[[User:Setr|Setr]]
#[[User:bytesmythe|Byte Smyðe]] -- Waiting for a camera before I buy one...
#[[User:Yogiz|Yogiz]] -- I'll but GTA02 even without the camera but a good 2mpx+ camera would in my opinion add a lot. I'd like to use it for example to photograph A4 documents in high contrast and feed the pictures to tesseract OCR. It would also be good for use in tandem with gps to add pictures to openstreetmap. Of course sometimes you just need to take a quick picture.
[[Category:Neo1973_alternate_cases]]
#[[User:Axel|Axel]]
#[[User:Weberpk|Weber Perdigão Macedo]]*I am interested. I have experience with embedded computer vision programming, and I can help on it. Feel free to contact me.
#[[User:Pedrosilva| Pedro Silva]] Camera is a must, 3MP or more. Maybe two cameras, most 3G mobile phones have one high resolution camera for photos/video and another VGA camera for video call.
#[[User:lorek123| Lorek]]The camera is the only thing that is missing in this phone.
#[[User:Dewey| Dewey]]This is a great idea! If designed properly, this could be a higher quality camera than most integrated phone cameras. If you leave it in the car, then you will have a camera that you can use in case of an accident. Being detachable, it would be perfect for when camera phones are not allowed when visiting companies on business.
# [[User:Theocrite|Theocrite]] Sounds good. It might be really easier to have pictures associated with contacts on the phone (without using a computer every time). Also it's a good thing to have a camera with you when you didn't expect to have something that needs a camera. I'm worried about the place it might take though. On the picture shown above it seems big. Even if it's removable, it might be something harder to carry.
#[[User:Ulcha|Ulcha]]
#[[User:Tehsagemaster|Tehsagemaster]] Waiting for the camera then I'll be buying one. 2MP is old in my opinion, up to 3MP min or prefer 5MP. Detachable be nice, but not required. Add focus lenses be nice to, but atleast a decent zoom and a bright led flash. Something to cover the lense if possible
#[[user:vandykee|vandykee]] Is anyone taking the lead on this? Are there any resources around for something like this that we can put together? Have much to add to this discussion. will be back often.
#[[User:jordan|jordan]] would buy a bunch of these in a heartbeat if they had cameras. very interested in this device (or the freerunner) for wearable computing device research, but need a camera, or at least good webcam support.
#[[User:remd|remd]] Same as Solid. I just trashed my w960 phone, and I would buy an openmoko phone right now if it had a camera. So Im sticking to my old w800 for now, and wait a little, but I'll have to get a new phone soon. The main things I use my phone for is calling, music listening(mp3+radio), wifi and email/web browsing, calendar, and the camera. And I use the "on flight" mode often, I can browse my mails locally, look at my pictures, see or edit pdf, xls, doc files and mainly listen to music on the plane.
#[[User:nebulo|nebulo]] If Openmoko FreeRunner would include a camera with at least 2MP I would buy one instantly and throw away my SE P1i. I love the idea behind Openmoko and except for the missing camera and 3G (which is not a critical issue) the OM FreeRunner seems to be my dream-mobilephone.
#[[User:Mira| Mira]]The camera is the only thing that is missing in this phone.
#[[User:north5| north5]]As soon as this phone has a camera I will buy it ...
#[[User:GoJian| GoJian]]Camera is really important for a phone actually--i use it so often.
#[[User:petitdragon|petitdragon]]The only reason why I did not buy an openmoko phone is that it has no camera ...
#[[User:Polk1986|Polk1986]] I am thinking about buying an OpenMoko, and would love to have a barcode scanning application like the G1 or iPhone. Unfortunately, there isn't a phone right now. I would be willing to help with mechanical design, but am unsure I have the appropriate coding ability to interface the camera with the rest of the phone.
#[[User:smoe|Steffen]] Cannot sell the phone to myself (or to family) without the camera, just don't skip any of its other features becaues of a camera being added, which are also important. If the camera is plugable, then consider to make that plug future-proof, i.e. allow for higher resolutions and various adapters over time. Please discuss to have a second camera attached or attachable. This will help with 3D vision and an improved coding of a depth of field into the image.
#[[User:joe|Joe]] Like so many have said before - I would buy this phone if it had a camera. The possibilities are endless, and you are going to have a lot of consumers for whom a camera is a must-have on a phone.

Main Page/de

2009-01-03T09:23:33Z

Thomasgruebler:

{{Languages|Main Page}}
__NOTOC__
__NOEDITSECTION__ [[Image:Freerunner02.gif|thumb|150px|right|Neo FreeRunners]]

<div style="padding: 2.5ex; text-align: center; font: bold x-large sans">Openmoko™ - Open. Mobile. Free.</div>

Openmoko™ ist ein Projekt, das als Ziel die Bereitstellung eines Mobiltelefons mit einem Open Source Softwarestack hat. OpenMoko Verkauft derzeit das [[Neo FreeRunner/de|Neo FreeRunner]] Telefon an fortgeschrittene Anwender und startet den Verkauf an die breite Öffentlichkeit sobald die Software weiterentwickelt ist.

Der OpenMoko-Stack, der einen vollständigen X-Server enthält, erlaubt es den Benutzern und Entwicklern die mobile Hardware Plattform in ein einzigartiges Produkt umzuwandeln. Unsere Lizenz gibt den Entwicklern und Anwendern die Freiheit kosmetische Aufbesserungen oder radikale Veränderungen durchzuführen - wechsel die Tapeten oder baue das ganze Haus neu! Sie gibt Ihnen die Freiheit, zum Beispiel das Telefon in ein medizinisches oder Point-of-Sale Gerät umzuwandeln oder die Freiheit einfach Ihre Lieblingsoftware zu installieren. Darüberhinaus ist nicht nur die Software frei, sondern wir haben auch die CAD-Dateien des Gerätes veröffentlicht und unter die Creative Commons Lizenz gestellt. Auf der Linux World 2008 werden wir auch die Schaltpläne dazu veröffentlichen.

<div style="clear:both"> </div>

<table class="wikitable" cellspacing="4" cellpadding="6" width="100%" style="color:white">
<tr style="background:#ff6600; text-align:center; font-weight:bold">
<td width="50%">Neuigkeiten und Veranstaltungen</td>
<td width="50%">Neu auf Openmoko?</td>
</tr>
<tr valign="top" style="background:#333333">
<td>
* 23/10: [http://onlinedev.blogspot.com/2008/10/is-openmoko-working-on-there-back-to.html Back to Basics info]
* 23/10: Weiteren Releases von [[FDOM]] bei Intresse siehe [http://lists.openmoko.org/pipermail/community/2008-October/034219.html Community list]
* 19/10: [[Community_Updates/October_19th%2C_2008|Community update]]
* 15/10: [[Weekly Engineering News|Openmoko Weekly Engineering News]] 41.
* 6/10: [[Community_Updates/October_3rd%2C_2008|Community update]]
* 2/10: Nokia veröffentlicht [http://qtextended.org/ Qt Extended 4.4.1] ([http://qtextended.org/modules/mydownloads/visit.php?lid=86 image], [http://qtextended.org/modules/mydownloads/visit.php?lid=85 SDK])
* 27/9: neues [[FDOM]] veröffentlicht
* 19/9: Erscheinungsdatum von [[Om_2008.9_Update|Om 2008.9]]
* 17/9: [[17th September, 2008 - Activity since launch|Community update]] - Aktivitäten seit dem Start
<br />
* [[Weekly Engineering News|Openmoko Weekly Engineering News]]
* [[News Archive|(news archive)]]
</td>
<td>
===<font color=white>Über Openmoko</font>===
* [[Introduction/de|Einführung]]
* [[Why Openmoko|Was ist Openmoko]]
* [[Neo FreeRunner/de|Neo FreeRunner Telefon]]
* [[Supported Hardware|Unterstützte Hardware]]
* [[FAQ/de|FAQ]]

===<font color=white>Openmoko besorgen</font>===
* [[Getting Openmoko|Openmoko besorgen]]
* [http://www.openmoko.com Openmoko Inc.]

</td>
</tr>
<tr style="background:#ff6600; text-align:center; font-weight:bold">
<td width="50%">Für Benutzer</td>
<td width="50%">Für Entwickler</td>
</tr>
<tr valign="top" style="background:#333333">
<td>
===<font color=white>Anfang</font>===
* [[Getting Started with your Neo FreeRunner/de | Neo FreeRunner Anfänger Referenz]]
* [[Applications|Anwendungen]]

===<font color=white>Distributionen</font>===
* [[Distributions|Features Vergleichstabelle]]
* [[Om 2008.8|Om 2008.8 (ASU)]] - [[Om 2007.2|Om 2007.2 (old stable)]]
* [[OpenmokoFramework|FSO]] - [[FDOM - a Fat and Dirty OM based distribution|FDOM]] - [[Qtopia / Qt Extended on FreeRunner|Qt Extended]] - [[Debian]] - [[Gentoo]] - [[Android]] - [[Stable Hybrid Release]]

===<font color=white>Openmoko Community</font>===
* [[Mailing List Duplicates| Mailinglisten]]
* [[Discussion_Forums| Diskussionsforen]]
* [[Community Repository]]
* [[Development resources | Entwicklungsressourcen]]
</td>
<td>
===<font color=white>Anwendungsentwicklung</font>===
* [[Openmoko developer guide|Openmoko Leitfaden für Entwickler]]
* [[Toolchain]]

* [[Python|Einführung in Python]]
* [http://projects.openmoko.org/ Projekte in unserem GForge]
* [[OpenmokoFramework|Openmoko dbus-basierendes Service-Level Framework]]

===<font color=white>Integration und Distributionen</font>===
* [[OpenEmbedded|OpenEmbedded Distribution Eintwicklungsumgebung]]
* [[MokoMakefile|Openmoko bauen mit Hilfe von MokoMakefile ]]
* [[Opkg|Opkg Paketmanager]]

===<font color=white>Emulation</font>===
* [[Openmoko under QEMU|Openmoko unter QEMU]]
</td>
</tr>
</table>

Artikel sortieren nach [[:Category:Categories|Kategorien]].

Ipkg

2008-12-30T16:22:47Z

Thomasgruebler:

'''NB:''' Current (2008-04-04+) builds of Openmoko now come with the syntax compatible [[Opkg]] tool, not ipkg.

{{Todo|Integrate useful content into [[Opkg]] as a usage section.}}

The practical way to install software on Openmoko is with the [http://handhelds.org/moin/moin.cgi/Ipkg Ipkg package manager], possibly via the graphical Application Manager. Naturally, you need to have obtained an Openmoko system by other means initially.

In the shell, "opkg update" will update the list of available packages, "opkg upgrade" will download and install all packages that have a newer version available and "opkg install new-app" will download and install "new-app".

Have a look at [[Users Repositories]] to get addresses of alternative software repositories, e.g. ScaredyCat's ipkg repository.

== History ==

Ipkg re-implements for embedded systems the functionality of Debian tools dpkg, apt, and apt-get. For example, it uses much less disk space for the package metadata.

== Installing Packages to the Memory Card ==

You can use ipkg to install packages to a folder on the memory card. To do this you'll need the following:

=== Ext2 Formatted Memory Card ===

By default, the memory card comes formated with VFAT (Windows Format). You need to re-format the card with EXT2. You will not be able to view the files on the card using a windows system after this.

To check if your card is using vfat or ext, run the 'mount' command, and look for: /dev/mmcblk0p1 on /media/card.

On the NEO, run the following:
''' This will erase everything on your memory card '''
<pre>
umount /media/card
fdisk /dev/mmcblk0
t
83
w
mke2fs /dev/mmcblk0p1
mount /media/card
</pre>

=== Entry in opkg.conf File ===

In your /etc/opkg.conf file, after "dest root /" add a new line:
<pre>dest card /media/card/opkg</pre>

Create /media/card/opkg folder
<pre>mkdir /media/card/opkg</pre>

=== Installing Packages on the Card ===

When installing a package, use the -d option to have the package installed into the "card" destination:
<pre>opkg install -d card python-core</pre>

This will put all files (binaries and libraries) on the card, under the folder specified in the ipkg.conf file.

=== Linking/Using Packages on the Card ===

Your system will not be able to see the packages that you just added to your card. There are two ways to remedy this.
The better solution is to use ipkg-link from the 'ipkg-utils' package, but 'better' is always subjective - YMMV.

==== 1: Ipkg Utils and ipkg-link ====

Ipkg-utils is a package that provides some additional functionality for ipkg. A very useful tool is ipkg-link, which creates symbolic links for packages installed in non-root locations (such as a card) back to the root file system.

To make this working with Opkg, you've simply to do:
<pre>ln -s /etc/opkg.conf /etc/ipkg.conf
ln -s /media/card/opkg/usr/lib/opkg /media/card/opkg/usr/lib/ipkg</pre>

To get ipkg-utils, run:
<pre>ipkg install ipkg-utils</pre>

To create symbolic links to your root system for a specific package, run: ipkg-link add <package>. For example, for python-core use:
<pre>ipkg-link add python-core</pre>

To create symbolic links for all packages installed in a location, run:
<pre>ipkg-link mount /media/card/ipkg</pre>

The ''ipkg-link remove'' and ''ipkg-link unmount'' commands remove the symlinks for a package or all packages.

There is a list of the options for the ipkg command under "How do I use it?" [http://handhelds.org/moin/moin.cgi/Ipkg here.]

==== 2: Adding the card PATH and LIB directories to your path ====
Another way to add bin and lib files to your system is by modifying your environment variables in /etc/profile as follows:

On the line that defines the PATH variable, add:
<pre>PATH=$PATH:/usr/local/sbin:/usr/sbin:/sbin:/media/card/ipkg/usr/bin</pre>

Then, before the 'export' line add:
<pre>LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/media/card/ipkg/usr/lib</pre>

Then modify the 'export' line and add LD_LIBRARY_PATH to the end.

This will let the system see the binary and library files, but it will not see other resources, such as images, configuration files, desktop files, etc. For this reason, ipkg-link is preferred.

Talk:FDOM - a Fat and Dirty OM based distribution

2008-12-25T20:27:15Z

Thomasgruebler: /* Screen Lock */ new section

"tangogps -> configured to use Google Maps" => This is not permitted by Google Maps. Please remove it.

---

Does the warning still apply to the 0925 release? I know this was the case for the 0913 one.
[[User:Monkeypanic|Monkeypanic]] 01:15, 26 September 2008 (UTC)

---

Is this true that /usr/share/applications/*.desktop files can't use xpm icons?
In scummvm.ipk there are only xpm-icon.

---

== Screen Lock ==

Maybe we could use [http://wiki.openmoko.org/wiki/Zedlock Z-Lock] in the next version? There is also an [http://www.opkg.org/package_66.html ipkg] avaiable.
The current screen lock through the Aux-key looks a bit boring.

Hardware:Neo1973:Alternate Cases:Camera

2007-10-10T17:27:33Z

Thomasgruebler: /* Materials */

Alternate case for the Neo1973, with rear-mounted camera module.

==Concept==

==Rendered images==

==3D model==

==Materials==
* 1 Camera with about 2MP or more for making pictures
* 1 Camera for video conferences. [http://www.google.com/url?sa=t&ct=res&cd=1&url=http%3A%2F%2Fmxhaard.free.fr%2Fspca50x%2FDoc%2FOmnivision%2Fov7610ds.pdf&ei=oAUNR4-KAaTGnAPU0L3kAQ&usg=AFQjCNG8HhZ84EDaXoXX2SsB1ju336NHjQ&sig2=wW--zV187dbJHDtQTrV8WQ OV7610 or OV7110] has an highspeed I²C Interface and would be good for easy connecting to the ARM processor.

==Processes==
Stereolithography

==Components==
Camera module with protection<br>
At least 2 Mpx.

==Interest==
Leave your nickname here if you are interested in having one made. This is not an order form, but is intended to gauge interest before effort is expended designing the case.<br>

#[[User:Bootlessjam|Bootlessjam]]
#[[User:Diatessaron|Diatessaron]]
#[[User:Thomas Mathiesen|Thomas Mathiesen]]
#[[User:Gizmhail|Gizmhail]]
#[[User:Fisticuffs|Fisticuffs]]
#[[User:Daniel|Daniel]]
#[[User:Deedend|Deedend]]
#[[User:Aztlek|Aztlek]]
#[[User:Mikesd|Mikesd]]
#[[User:Filippo|Filippo]]
#[[User:Beady|beady]]
#[[User:Wvrn|wvrn]]
#[[User:yvanxxx|yvanxxx]]
#[[User:amarov|amarov]]
#[[User:cedel|cedel]]
#[[User:gwylim|gwylim]]
#[[User:Massa|Humberto Massa]]
#[[User:hhf423|hhf423]]
#[[User:Fursund|Fursund]]
#[[User:Bubbi|Bubbi]]
#[[User:Drizzt|Drizzt]]
#[[User:Pajamabama|Pajamabama]]
#[[User:vozka|vozka]]
#[[User:dlejeune|dlejeune]]
#[[User:AnyWare|AnyWare]]
#[[User:kresp0|kresp0]]
#[[User:sin|sin]]
#[[User:DjAlxor|DjAlxor]]
#[[User:Kf|Kf]]
#[[User:Kylegordon|Kylegordon]]
#[[User:Oatty|Oatty]]
#[[User:nericastillogioleo|nericastillogioleo]]
#[[User:Fradeve11|Fradeve11]]
#[[User:solid|solid]] -- A camera is the only thing I am waiting on to buy this phone
#[[User:Globbi|Globbi]]
#[[User:Madoon|Madoon]]
#[[User:Thomasgruebler|Thomasgruebler]] -- 3MP would be cool
[[Category:Neo1973_alternate_cases]]

Hardware:Neo1973:Alternate Cases:Camera

2007-10-10T17:22:52Z

Thomasgruebler: /* Materials */

Alternate case for the Neo1973, with rear-mounted camera module.

==Concept==

==Rendered images==

==3D model==

==Materials==
* 1 Camera with about 2MP or more for making pictures
* 1 Camera for video conferences. OV7610 or OV7110 has an highspeed I²C Interface and would be good for easy connecting to the ARM processor.

==Processes==
Stereolithography

==Components==
Camera module with protection<br>
At least 2 Mpx.

==Interest==
Leave your nickname here if you are interested in having one made. This is not an order form, but is intended to gauge interest before effort is expended designing the case.<br>

#[[User:Bootlessjam|Bootlessjam]]
#[[User:Diatessaron|Diatessaron]]
#[[User:Thomas Mathiesen|Thomas Mathiesen]]
#[[User:Gizmhail|Gizmhail]]
#[[User:Fisticuffs|Fisticuffs]]
#[[User:Daniel|Daniel]]
#[[User:Deedend|Deedend]]
#[[User:Aztlek|Aztlek]]
#[[User:Mikesd|Mikesd]]
#[[User:Filippo|Filippo]]
#[[User:Beady|beady]]
#[[User:Wvrn|wvrn]]
#[[User:yvanxxx|yvanxxx]]
#[[User:amarov|amarov]]
#[[User:cedel|cedel]]
#[[User:gwylim|gwylim]]
#[[User:Massa|Humberto Massa]]
#[[User:hhf423|hhf423]]
#[[User:Fursund|Fursund]]
#[[User:Bubbi|Bubbi]]
#[[User:Drizzt|Drizzt]]
#[[User:Pajamabama|Pajamabama]]
#[[User:vozka|vozka]]
#[[User:dlejeune|dlejeune]]
#[[User:AnyWare|AnyWare]]
#[[User:kresp0|kresp0]]
#[[User:sin|sin]]
#[[User:DjAlxor|DjAlxor]]
#[[User:Kf|Kf]]
#[[User:Kylegordon|Kylegordon]]
#[[User:Oatty|Oatty]]
#[[User:nericastillogioleo|nericastillogioleo]]
#[[User:Fradeve11|Fradeve11]]
#[[User:solid|solid]] -- A camera is the only thing I am waiting on to buy this phone
#[[User:Globbi|Globbi]]
#[[User:Madoon|Madoon]]
#[[User:Thomasgruebler|Thomasgruebler]] -- 3MP would be cool
[[Category:Neo1973_alternate_cases]]

Hardware:Neo1973:Alternate Cases:Torch

2007-09-29T19:44:37Z