Created attachment 38395 [details] Support to TCP source I patched Gypsy to test without GPS unit in PC. I tested with GPSFeed+. (http://gpsfeed.sourceforge.net/). GPSFeed+ is a GPS Simulator. It supports to COM/TCP/HTTP output and replay from NMEA log. I tested patched gypsy to using below way. 1. Run GPSFeed+ then start to GPS with TCP output setting $ tclsh gpsfeed+.tcl (then, set the tcp port and start to GPS) 2. Run gypsy example with GPSFeed+'s output tcp address instead of device path $ ./simple-gps-gypsy tcp://127.0.0.1:2222 (port number is 2222) I decided to use tcp:// scheme to avoid conflict with blutooth address. As you know, BT address is also start with number. And my patch contains that if device path has a dot, replace to underscore to avoid conflict with D-Bus object path.
#28667 is an alternative way of replaying a NMEA log for simulating, I'd appreciate it if you could have a look at that and give us your feedback. I'm cautious of feature creep because once we add networking support other requests will follow. I think that a way of replaying a NMEA log through a pipe should be sufficient for simulating.
Thank you for your fast reply. :-) I agree that using pipe is a best way to replay or simulating NMEA log. But I think that supporting TCP source is also very useful feature for specific situation or platform that cannot use pipe like Windows. And Many GPS simulator support TCP output. And Supporting TCP source could be used by special purpose like IDE. Imagine that MeeGo Simulator for Window or MeeGo SDK for Windows. For this, Native Development tool like Android's DDMS can send location data into Gypsy in the emulator like qemu.
Are there any news about an simulate feature for software develop on gypsy?
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.