1 |
Stroller <stroller@××××××××××××××××××.uk> [14-10-12 09:28]: |
2 |
> |
3 |
> On Sat, 11 October 2014, at 3:10 pm, meino.cramer@×××.de wrote: |
4 |
> > ... |
5 |
> > Two things need still to be investigated: How can I store GPSdata onto the |
6 |
> > flash in a way, that no additional data is stored if no movement is |
7 |
> > there. |
8 |
> |
9 |
> This should be pretty easy, but if you want help with it, you're going to need to give us some insight into how you're storing or accessing the GPS data at present. |
10 |
> |
11 |
> Having said that, I'm not convinced that this is necessary. I have a logfile here with 91,000 lines of text in it, and it's 9.9mb and bzips down to 369kb. 91,000 is close to 10 entries every minute for a week, and I'd guess that you'd find CSV formatted GPS data written as text to have about the same length and compressibility as a typical /var/log/messages entry. |
12 |
> |
13 |
> > And I have to prevent, that a sector/block/organisation unit |
14 |
> > of the flash is written more than once to prevent ware out of the |
15 |
> > flash. |
16 |
> |
17 |
> Wear-levelling should be handled by the flash memory controller, and you shouldn't need to worry about it. |
18 |
> |
19 |
> Stroller. |
20 |
> |
21 |
> |
22 |
> |
23 |
|
24 |
Hi Stroller, |
25 |
|
26 |
thank you for your input :) !! |
27 |
|
28 |
I am still a pure newbie to gps. This morning I discovered, that there |
29 |
a LOT of kinds of output of the different GPS devices...the output of |
30 |
mine looks /so standard/, that I thought it would be /THAT STANDARD/. |
31 |
;) |
32 |
|
33 |
Ok ... the device I use is an Ultimate GPS by Adafruit Industries. |
34 |
The device is a GlobalTop-FGPMMOPA6C module with a MediaTek MT3339 |
35 |
chipset. |
36 |
|
37 |
The output are NMEA sentences (pure ASCII as it seems). The module is |
38 |
wired to UART01 on my embedded computer, so gpsd can read the data |
39 |
from /dev/ttyO1. |
40 |
Via gpsd it is possible to create json output from that (instead of |
41 |
NMEA). |
42 |
|
43 |
The module creates from 1 to 10 position reports per second. I want |
44 |
to make this speed depended (read: I have to write some code for it, |
45 |
if I dont find some...). If one choose 1 report/second it will send |
46 |
5 position report and then 1 status report (current time for example). |
47 |
|
48 |
Since civil GPS modules have the feature to obfuscate the exact |
49 |
position up to some degree (otherwise I would build a weapon instead |
50 |
of tinkering with an embedded system...at least according to some |
51 |
external laws ;) I see problems in deciding, whether I am really |
52 |
moving or my position is moving due to """less accuracy of the |
53 |
chipset""". |
54 |
|
55 |
Currently the GPS antenna is clamped to my desktop lamp and I am |
56 |
nearly up to 100% sure that it is not moving at all...but gpsmon gives |
57 |
me a natural speed of 0.5km/h which is definitely too much for |
58 |
a warmth induced Brownian molecular motion... ;) |
59 |
|
60 |
"Wear levelling should be handled by the flash memory controller..." |
61 |
|
62 |
This "should" makes me a little nervous, Stroller... ;) |
63 |
Linux includes a filesystem called F2FS, which takes care |
64 |
of the wear levelling problem (as far as I know). This F2FS originates |
65 |
from SAMSUNG, one of the greater manufacturer of Flash memories of all |
66 |
kind. Why the effort, if the memory controller take care of it? |
67 |
Stroller, I DONT EXPLICETLY OR IMPLICITELY EXPRESS A "I DONT BELIEVE |
68 |
YOU" HERE...! |
69 |
It is just the difference between what manufacturer states ("...should be |
70 |
handled...") and what mechanisms create more benefits for them. |
71 |
|
72 |
Best regards, |
73 |
mcc |