On 01/25/2011 10:44 AM, Holger Hans Peter Freyther wrote: I can't make it work. The first issue was the /dev/ttyACM0 in the source code (my gps is /dev/ttyUSBX). I modified it in the code, but I think that a cmd line option would be nicer. I don't see any debug/error log lines, but no coordinates appear in my log file. Any hint? My gps receiver works fine with other softwares.

let the GPS warm up, maybe it just needs to start tracking the sats, or add a printf to dump what data is coming from the GPS 2011/1/25 Dario Lombardo <dario.lombardo(a)libero.it>

On 01/25/2011 01:51 PM, MArc Richter wrote: patches welcome, no harm if two people work on this. Personally I would prefer command line parameters as cell log is not using a config file yet.

On 01/25/2011 02:17 PM, Dario Lombardo wrote: For command line options. Each app can have its own set, just add them to the one already present for the cell_log (e.g. to disable rach bursts). If you go for config file parsing, make sure that no config file is required (keep it optional). But then again parameters are preferred by me. z.

On 01/25/2011 02:43 PM, MArc Richter wrote: Attached there is my patch to support cmd line gps in cell_log.

On 01/25/2011 04:34 PM, Holger Hans Peter Freyther wrote: Very good. This is the new patch that should fix both.

Something's going wrong when I try to commit. git commit . git formal-patch git push Last one returns "fatal: The remote end hung up unexpectedly". Am I making something wrong?

On 01/26/2011 01:48 PM, Holger Hans Peter Freyther wrote: Ok. Attached there is the format-patch.

On 01/26/2011 02:34 PM, Holger Hans Peter Freyther wrote: Opps... you're right. Thank you.

On 01/25/2011 16:34, Holger Hans Peter Freyther wrote: Actually it does, even though it may truncate the resulting string in the process: « snprintf() and vsnprintf() will write at most size-1 of the characters printed into the output string (the size'th character then gets the terminating `\0') » HTH, -- khorben

Hi, On 01/26/2011 21:28, Holger Hans Peter Freyther wrote: first, I have to admit that the manual on Linux is very confusing and unclear about snprintf(), which is why I pasted an extract from BSD. Still, if you do: === BEGIN PASTE === $ cat snprintf.c && make snprintf && ./snprintf #include <sys/utsname.h> #include <stdio.h> #include <string.h> int main(void) { struct utsname uts; char buf[16]; int res; if(uname(&uts) == 0) printf("%s %s\n", uts.sysname, uts.release); memset(buf, 0xff, sizeof(buf)); res = snprintf(buf, 4, "%s", "AAAAAAAA"); printf("snprintf() returned %d, buf[3] = 0x%02x\n", res, buf[3]); return 0; } cc snprintf.c -o snprintf Linux 2.6.9-023stab052.4-enterprise snprintf() returned 8, buf[3] = 0x00 === END PASTE === Which would tend to argue in my direction, as this was run on a Debian Lenny host. However, as I was kindly reminded by a friend in the meantime, you are also right. Even though POSIX/SUSv3 itself says: http://pubs.opengroup.org/onlinepubs/009695399/functions/printf.html « The sprintf() function shall place output followed by the null byte, '\0', in consecutive bytes starting at *s; it is the user's responsibility to ensure that enough space is available. The snprintf() function shall be equivalent to sprintf(), with the addition of the n argument which states the size of the buffer referred to by s. If n is zero, nothing shall be written and s may be a null pointer. Otherwise, output bytes beyond the n-1st shall be discarded instead of being written to the array, and a null byte is written at the end of the bytes actually written into the array. » (the last sentence is important here) there are platforms indeed which do not respect this: http://msdn.microsoft.com/en-us/library/2ts7cx93%28v=vs.80%29.aspx So on Windows you are right. Now I guess the question is: is OsmocomBB intended to support non-POSIX platforms natively? HTH, -- khorben

Nice ! But do you want to deploy this patch to the repository to gave everyone this feature ? On Tue, Jan 25, 2011 at 4:30 PM, Dario Lombardo &lt;dario.lombardo(a)libero.it&gt; wrote:

i've had the same issue. Use the attached patch to read the required data from the $GPGGA NMEA sentence. - Martin

if (!strcmp("$GPGLL") { // run the old code } else if(!strcmp("$GPGGA)) { // run your new code } else { return; } would work better... ;-) On Mon, Jan 31, 2011 at 1:34 PM, Dario Lombardo &lt;dario.lombardo(a)libero.it&gt; wrote:

I don't see a huge problem here. Why not just parse whatever message with interesting info we get? if (!strcmp("$GPGLL") { // extract coordinates and update buffer } else if(!strcmp("$GPGGA)) { // extract coordinates and update buffer } else if(!strcmp("$GPRMC)) { // extract coordinates and update buffer } else if(!strcmp("$GPSuperProprietaryMessageWithAwesomePrecisionData")) { // extract coordinates and update buffer } else { // no luck with this message return; } Sebastien On Mon, Jan 31, 2011 at 4:28 PM, &lt;mad(a)auth.se&gt; wrote:

On 01.02.2011 09:43, Dario Lombardo wrote: how about a proper gpsd-integration? I've some spare time in the end of this month to try it. I would parse only one least common NMEA-sentence. As Mad said the "GPRMC"-sentence should be a good candidate for this. All other GPS-input-messages could be read via libgpsd from gpsd (which seems to be able to read even most obscure GPS-binary formats). best regards, Martin

It would also be nice to have a dummy-GPS mode, where you could put the longtitude/latitude as a command line argument for gsmmap. I think most people won't move much debugging with osmocon, so a static position is sufficient. But: there is already an application for GPSd, gpsfake which can fake positions (and can give a static position). If full GPSd-compatibility is made, this would be redundant. http://gpsd.berlios.de/ -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Cell-log-gsmmap-tp2327658p241209… Sent from the baseband-devel mailing list archive at Nabble.com.

I would leave the possibility of using the current GPS code by using a define at compile time, so when compiling for an embeeded platform (like android, armstrong or equivalent) you do not rely on having the gpsd library and daemon available 2011/2/7 Dario Lombardo &lt;dario.lombardo(a)libero.it&gt;

Dario Lombardo wrote: Please fix the code so that it uses the value from the config. //Peter

So let me short summarize this 1. conntect GPS device 2. in the config (osmocom.cfg) change the following lines from ..... ! gps device /dev/ttyACM0 gps baudrate default no gps enable ! ms 1 sim reader ....... to .... ! gps device /dev/ttyACM0 gps baudrate default gps enable ! ms 1 sim reader ..... 3. run Cell_log 4. convert Cell_log with gsmmap to a valid .kml file is this correct ? On Tue, Jan 25, 2011 at 10:44 AM, Holger Hans Peter Freyther < holger(a)freyther.de&gt; wrote: