Re: [tGarden-dev] fixing wearables etc this week

[nik g. <ni...@xd...>]

> questions:
> 
> (0) what data rates were we able to get from the ipaq's in ars and 
> rotterdam? 

we didnt use teh ipaq setup in linz, as i remember from rdamm it was
"resonable" (sorry fr the lack of detail)

>  how about txooom? 

we measured delay times (which seem to have a more drastic effewct on
coupling of the space to the player than sampling freq,)
anywhere from 3,4ms to thirty seven seconds!!!

> our gvu lab rates seem slow  -- only 
> a few vectors / sec from the one single! ipaq.   what factors control 
> or limit the frequency of data from the accelerometer to 802.11b? 
> (wasn't that a rate fixed at the pic, or does that depend on 
> available  802.11b speeds/bandwidth?

we had some very unusual fluctuation s  in netwrok behaviour in torino.
generally it worjked better at night, perhaps excessive radiation during the
day? badly configured cell network? if  you are gettin gonly a few samples
per second, it might be a sensor or pic problemm since stocks version waits
quite a while (tens of milliseconds) between sensor channels if no data is
sent from the sensor. make sure both sensors are plugged into the pic, and
that they are both working sensors.
 
> our little 802.11b network runs only the ipaqs and a mac airport on a 
> pc.   there's a second mac airport card but that's built into the oz 
> mac in order for it to get around some draconian sysad restrictions 
> on our wireless usage.

have a look at some of teh wireless monitoring thruput/frame dropping rates
 
> (1) why do (at least 2 of) the ipaq's not stay on when detached from 
> the ac charger?   in one case, switching to a different "phong" ac 
> adapter/charger fixed that, but here at gatech gvu lab this no longer 
> seems / doesn't seem to work.

we had a similar probelm with the ipaq * power, maybe some flaw in the
batteriues? maybe we are just being to harsh  on the poor office
accesories?!
 
> (2) one ipaq has a "broken" serial port.
> is that under warranty?  how should one go about diagnozing and 
> having it fixed? (compaq factory, i presume -- but does anyone know 
> exactly?)

id say waranty, phone compaq * find ou the terms
 
> (3) now at least 2 of the pic's seem broken.  what next?
> need diagnosis + fix.

we have decided to build better (more accurate, sensitive, robust) units, 
 
> i have this week, may 6-11 to dedicate to these problems, so am 
> standing by, ready to entertain all reasonable suggestions.

hope some of this helps

nk