<Oksana>
I got the screen protector (actually, two of them) from Clarivue. Looks fine. I no longer wish to increase the brightness of the display. And, tracker unpaused itself, since I cleaned up a bit of space. apt-get clean, dpkg --forget-old-unavail, and removing the log of operator name widget. Still, I need to find how to switch off the logging. And clean up a bit more.
ReqGame has joined #neo900
freemangordon has joined #neo900
ecloud is now known as ecloud_wfh
ashneo76 has quit [Ping timeout: 245 seconds]
ashneo76 has joined #neo900
mvaenskae has quit [Ping timeout: 252 seconds]
Pali has joined #neo900
ReqGame has quit [Ping timeout: 244 seconds]
<DocScrutinizer05>
Oksana: >>In addition to the widget, there is a control panel that lets you enable/disable cell broadcast display as well as enabling/disabling 2 different log files.<< http://talk.maemo.org/showthread.php?t=80526
<ds2>
DocScrutinizer05: have you finalized on the choice of sensor chips (Accel/Mag/Gyro/Pressure)?
Pali has quit [Remote host closed the connection]
<DocScrutinizer05>
not completely, I still think we should consider the highly integrated Bosch thing I found
<DocScrutinizer05>
I don't see why it would be worse than two separate Bosch chips
<DocScrutinizer05>
given it's similarly sourceable
<DocScrutinizer05>
note that I doubt usefulness of any magnetic compass in our highly magnet infested environment. Known sources of rather strong - though static - magnetic fields are: speakers, earpiece, vibra motor, switch magnets in battery id and display slider
<DocScrutinizer05>
s/ id / lid /
<DocScrutinizer05>
sources of variable magnetic fields are relatively high DC currents floating along long paths: display backlight, modem power et al
<ds2>
static can be calibrated out
<ds2>
the DC loads can be canceled out with careful layout
<DocScrutinizer05>
unless it exceeds the allowed range of the sensor
<ds2>
you mean the saturation sensing range
<DocScrutinizer05>
yes
<ds2>
some mag sensors can handle higher saturation ranges then others
<ds2>
haven't used the BMM stuff much to know off hand
<DocScrutinizer05>
yes, that's where I came from
<ds2>
ah, so you know hte issues :D
<ds2>
then put in a fluxgate :D
<DocScrutinizer05>
>>Magnetic field range typical 1300μT (x-, y-axis); ±2500μT (z-axis) Magnetic field resolution of ~0.3μT<<
<ds2>
seems smaller then the HMC's
<DocScrutinizer05>
fluxgate?
<ds2>
there is one company that makes sensors based on that
<DocScrutinizer05>
what is a fluxgate?
<ds2>
coils you drive with a wave form to see when it saturates
<DocScrutinizer05>
aaah
<ds2>
the saturation point is related to the field strength
<DocScrutinizer05>
nifty
<ds2>
very wide range
<ds2>
the AK* chips are based on something like that IIRC
<DocScrutinizer05>
:nod:
<ds2>
having a known/open design could make this a nice research instrument
<ds2>
hence my interest in the sensors
<DocScrutinizer05>
basically when you have a compensating sensor like that fluxgate, your allowable range is only defined by the power you can feed to the compensation
<DocScrutinizer05>
signal - compensation = 0 (or constant), gives it away already
<DocScrutinizer05>
ideally you would combinate a linear sensor with an active compensation
<ds2>
only problem is you have a finite battery
<DocScrutinizer05>
combine*
<DocScrutinizer05>
yes, exactly
<ds2>
You could sheild the rest of the board with mu-metal ;)
<DocScrutinizer05>
mu or generally metal is a huge headache and PITA in design of small series
<DocScrutinizer05>
again same rules like for cases apply
<DocScrutinizer05>
the component is friggin cheap, the tooling unbearably expensive
<ds2>
not with mumetal...that stuff ain't cheap
<DocScrutinizer05>
so you only can afford it for 7 figure production batches
<ds2>
for the volumes you are looking at, there are protohouse that can do it cheaper with soft-tooling (essentially CNC for sheet metal)
<DocScrutinizer05>
well, maybe 6 or even 5 when you want to go "luxury is our normal operation mode"
<DocScrutinizer05>
CNC for metal? cool shite
<DocScrutinizer05>
any pointers welcome
<DocScrutinizer05>
:-)
<DocScrutinizer05>
actually knowing a source for e.g. slider mech remakes already would make me feel much calmer regarding building of NNN batches
<ds2>
I have literature from a company but it is buried under 5 years worth of trade show literature :(
<DocScrutinizer05>
sourcing of the original N900 spare stuff starts to become mission impossible, in volumes starting 2 figures
<ds2>
the term they use is "soft tooling" for sheetmetals/cases. PC case makers use that for protoing. the same folks also prototype RF cans
<ds2>
indeed
<DocScrutinizer05>
cooooool
<DocScrutinizer05>
I guess a sample will be absolutely fine as definition for those CNC houses?
<DocScrutinizer05>
anyway, any help highly appreciated
<DocScrutinizer05>
we even might add cans then ;-D
<ds2>
I have to dig... lots of stuff from trade shows piled up
<DocScrutinizer05>
maybe you have a somewhat easier time googling that stuff than I would
<ds2>
this was at a PCB show and I was intrigued by the booth with all the cans.
<ds2>
let me try
<DocScrutinizer05>
(PCB show) there's awesome amazing stuff existing. You seen PCB embedded components?
<DocScrutinizer05>
dang weird stuff, you don't bother to solder R, C, L anymore (unless L or C are huge), they come buried into PCB already
<Oksana>
Good morning, and thank you! Question about GPS/Glonass: what does Qualcomm gpsOne Gen8A (inside the cellular modem chip) think about civilian-use restrictions (above 18 kilometers altitude and 515 meters per second speed)? Because for future-proofness (space-flights and the like) having non-restricted GPS receiver would be a good idea.
<ds2>
isn't that a question for the US Gov?
<Oksana>
They still do not know what direction their space-flight program is going to take (asteroid, Moon or Mars) ;-) And for the Moon, they plan to have a mess of radio-beacons (initially, at least), instead of putting some GPS satellites into orbit around the Moon.
<Oksana>
It's not a deal-breaker because: 1. an external (ITAR-free?) GPS can be attached via Bluetooth; 2. space exploration is going at snail pace. But still, it would be nice to know which, if any, restrictions are imposed within existing hardware (aka Qualcomm gpsOne Gen8A)
Pali has quit [Remote host closed the connection]
jonwil has joined #neo900
sparetire_ has joined #neo900
wicket64 has joined #neo900
arcean has quit [Read error: Connection reset by peer]
b1101 has quit [Quit: b1101]
paulk-collins has quit [Quit: Quitte]
<DocScrutinizer05>
Oksana: the restrictons of GPS are *most likely* in firmware of modem module, which is update-able
<DocScrutinizer05>
so it's probably safe to expect Gemalto providing a non-restricted firmware update whenever the restrictions are moot from a legal POV *and* there's a reason beyond funny restrictions' removal to ship a new firmware
<DocScrutinizer05>
galileo might be such reason
<ShadowJK>
the high altitude balloon hobbyists used to have list of 'good' gps modules
<DocScrutinizer05>
though I'm nnot sure galileo is GPS/GLONASS compatible, hw-wise
<DocScrutinizer05>
ShadowJK: do you know if GPS receivers could learn (crippled) galileo?
* DocScrutinizer05
still hasn't managed to fill a blue waste bag with CH4
<DocScrutinizer05>
alas I have no gas in my current flat :-/
<DocScrutinizer05>
dunno if PNG is available in bottles
<DocScrutinizer05>
LPG for sure won'
<DocScrutinizer05>
t fly, literally
<DocScrutinizer05>
I just had a nice talk about webshops with an ex-colleague and friend: Markus S.
<ds2>
hmm? do balloons go that fast?
<DocScrutinizer05>
no, that high
<ds2>
the restriction should be on the combo of height AND speed
<DocScrutinizer05>
I think it's either or
<ds2>
if you don't meet both, then you should be fine
<DocScrutinizer05>
I am sure some GPS modules implement "either of both"
<DocScrutinizer05>
well, the basic limitation is delay and frequency (9/s) of GPS fixes
<ds2>
you could always try to use the SDR stuff for GPS
<DocScrutinizer05>
there some massive "Heissenberg" applies, either you know the speed but you don't know when and where that speed applied, or you get the where and when but don't know the true speed ;-)
<DocScrutinizer05>
SDR for GPS been already POCed
<DocScrutinizer05>
based on RTL-SDR
<ds2>
yes, that was what I was referring to
<ds2>
just donno how reliable is that implementation
<DocScrutinizer05>
but it's again waaaay too slow and thus introduces Heissenberg
<DocScrutinizer05>
"Hi user! based on average of last 30s I think you could be at X,Y,Z with vector V - unless you changed direction or speed during last 30s"
<DocScrutinizer05>
I honestly hope nobody tries to control a IBM with that
<MonkeyofDoom>
international business machine :)
<DocScrutinizer05>
it would prolly miss target by some 10km
<DocScrutinizer05>
honestly average crappy GPS is too slow even for car cruising on highway. The application software has to extrapolate what gets reported by GPS to guesstimate the realtime position
<DocScrutinizer05>
mere GPS fix may be several 100m "late"
JoHnY has quit [Remote host closed the connection]
<DocScrutinizer05>
at least that's what I seem to have whitnessed
<DocScrutinizer05>
I don't think the skew/delay been introduced by the APE app
<DocScrutinizer05>
when I watched e.g. tangogps painting track into map, it took like 5s until the 90° turn actually showed up in track painted
louisdk has quit [Read error: Connection reset by peer]
<DocScrutinizer05>
depending on smartness of app it either extrapolates and then reverts false extrapolations and repaints the new track of last 5s, or it simply shows mad excursions into offroad areas when you do a 90° turn
<DocScrutinizer05>
eventually it snaps to road again, after "driving" for 500m or 1000m some 100m offset parallel to the new road