GPS position under Windows 7 lazarus / 34-Windows ---------------------------------------------------------------------- PAF · 2014-02-26 15:10 I am running FPC 2.6.0 under Windows 7 and want to access position and speed from a gps sensor connected to a USB port. I would prefer to do this with the use of the ilocation api (getreport and so forth). However ilocation does not seem to be available in any FPC unit. Thanks in advance for any advice on how to manage this! Per Anders ---------------------------------------------------------------------- PAF · 2014-03-03 13:47 I had no replies to this question, but several person have shown interest, so here is how I solved it. I now use synaser (+ synautil and synafpc; all available on http://sourceforge.net/p/synalist/code/HEAD/tree/trunk/). This makes it easy to send and receive information on COM ports (including USB). If anyone is interested in sample code so let me know. Per Anders ---------------------------------------------------------------------- rc.1990 · 2014-03-03 15:44 Could you post the sample code and explain from which device (mobile phone, tablet, etc) into USB have you obtained the GPS position? ---------------------------------------------------------------------- Jurassic Pork · 2014-03-03 16:03 hello, in my lazarus serial component Tlazserial here   there is an example project to read and  simulate NMEA frames from GPS. Friendly, J.P ---------------------------------------------------------------------- georgebou · 2014-03-03 17:09 Nice. when i have time i will test it ---------------------------------------------------------------------- PAF · 2014-03-03 20:17 I have a separate gps sensor which (like other components of nautical navigation) sends sentences according to the NMEA protocol. A program to test the synaser connection follows. Per Anders ---------------------------------------------------------------------- avra · 2014-03-04 02:19 Quote from: Jurassic Pork on March 03, 2014, 05:03:21 pmin my lazarus serial component Tlazserial here   there is an example project to read and  simulate NMEA frames from GPS. Tlazserial is very nice but GPL license limits it's usage too much for me... ---------------------------------------------------------------------- Jurassic Pork · 2014-03-04 05:19 hello Avra, LazSerial is LGPL not GPL  : QuoteLazSerial v0.1 Serial Port Component for Lazarus (windows and linux). by Jurassic Pork  03/2013 This library is Free software; you can rediStribute it and/or modify it   under the terms of the GNU Library General Public License as published by   the Free Software Foundation; either version 2 of the License, or (at your   option) any later version. Friendly, J.P ---------------------------------------------------------------------- taazz · 2014-03-04 05:23 doesn't change much for a component gpl or lgpl is the same thing of course if it was a dll then things would be different. ---------------------------------------------------------------------- BigChimp · 2014-03-04 08:04 Agreed with taazz. The LGPL with linking exception as used by Free Pascal & Lazarus components could be a good choice if you want to be able to use a module like LazSerial in any project (even closed source). Other licenses of course also fit, like BSD, MIT, public domain, but modified LGPL has the advantage that it matches the licenses of the LCL etc, probably cutting down on complexity and confusion... ---------------------------------------------------------------------- avra · 2014-03-04 08:17 Quote from: Jurassic Pork on March 04, 2014, 06:19:23 amLazSerial is LGPL not GPLLast time I checked, TComPort component used in LazSerial was GPL, and GPL is viral when used as source or linked to. The way I understand licenses, even if your work is LGPL, using GPL TComPort indirectly through LGPL TLazSerial would make impossible to have my commercial work closed source. That was the end of the game for me.  http://sourceforge.net/projects/cportlaz I would be really happy to be proved wrong on this one ---------------------------------------------------------------------- BigChimp · 2014-03-04 09:50 Quote from: avra on March 04, 2014, 09:17:33 amTComPort component used in LazSerial was GPL, and GPL is viral when used as source or linked to. The way I understand licenses, even if your work is LGPL, using GPL TComPort indirectly through LGPL TLazSerial would make impossible to have my commercial work closed source. You're right about using GPL code as source, then it is indeed viral and your whole code is considered GPL, whatever license terms you pasted on them yourself. Same for static linking. Opinions about dynamic linking differ, to put it mildly. ---------------------------------------------------------------------- Jurassic Pork · 2014-03-04 21:22 hello, Avra said : QuoteLast time I checked, TComPort component used in LazSerial was GPL, Lazserial doesn't use TComport component, only the file lazserialsetup.pas uses some functions from  this version of TComport which has a public domain licence  . Friendly J.P ---------------------------------------------------------------------- marcov · 2014-03-04 22:21 Quote from: avra on March 04, 2014, 09:17:33 amQuote from: Jurassic Pork on March 04, 2014, 06:19:23 amLazSerial is LGPL not GPLLast time I checked, TComPort component used in LazSerial was GPL, and GPL is viral when used as source or linked to. Next time, check better, it is PD: http://sourceforge.net/projects/comport/ ---------------------------------------------------------------------- avra · 2014-03-05 13:48 Quote from: avra on March 04, 2014, 09:17:33 amI would be really happy to be proved wrong on this one   And I really am. ;-) Silly me, it seams that I have checked wrong ComPort component. Thanks everyone!