<br><br><div class="gmail_quote">2009/9/12 Michael 'Mickey' Lauer <span dir="ltr"><<a href="mailto:mickey@vanille-media.de">mickey@vanille-media.de</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Saturday 12 September 2009 09:56:08 Ivo van den Maagdenberg wrote:<br>
> Anyone able to show how to read out the accelerometers through d-bus? I<br>
> tried looking it up on <a href="http://wiki.openmoko.org/wiki/Dbus_device_API" target="_blank">http://wiki.openmoko.org/wiki/Dbus_device_API</a> but<br>
> did not find references to the accelerometers.<br>
<br>
</div>What's your usecase? Since very recently, we provide<br>
<a href="http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.Device.Orientation.html;hb=HEAD" target="_blank">http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.Device.Orientation.html;hb=HEAD</a><br>
<br>
</blockquote></div>The use case is as follows: take the openmoko and make it a cycleway shock measuring platform, utilizing the accelerometers. So, direct reads from the are going to be needed. The gps unit is of course of interest to make the measurements location-based.<br>
<br>I am not yet up to speed with the fso stack. Is it possible to explain why the fso direction to read out data from the accelerometers was abandoned? I could understand the argument that constantly reading out the accelerometers would hog the cpu and probably would also drain the battery very easily too. Switching the readout on and off through by fso interface command and reading them out would be a natural thing to have, but as said, I have not implemented a single line of code in the fso domain :)<br>
<br>