Speed up Lazarus??

[BigChimp]

So try if that port is listening. Run netstat on the Pi to find out if some daemon is listening on port 2947, and if so, if it is on localhost/127.0.0.1 only or on 0.0.0.0 (=any interface).

If it is listening on any interface, check any firewalls (inbound on the pi and outbound on your desktop) to see if they are blocking things.

[BLL]

Hi, Thanks for the info. I have run netstat and there is no entry for 2947. I haven't installed a firewall on the Pi. SSH works fine.

I have the Windows firewall set to show any blockings.

Not sure where to go next!

[BigChimp]

Well, who/what told you the gps would send data on port 2947? It obviously isn't sending data and maybe you should enable it. Isn't there some documentation you can read?

Also, getting some general knowledge/reading up on Linux and networking may be a good idea. Getting people to spoon feed you what to do without knowing what you're doing is not a good way to efficiently go forward...

[BLL]

The gps is enabled, working and the gpsd daemon provides the data on port 2947. Data from this port is available in my program on the raspi and also displays via the cgps program, so it must be something else!

[BigChimp]

Please paste the output of

Code: [Select]

netstat -an | grep 2947
to see what's going on...

[BLL]

Hi, some of it is me being green and not knowing what to do! Here is the output:

pi@raspberrypi ~ $ netstat -an | grep 2947
tcp        0      0 127.0.0.1:2947          0.0.0.0:*               LISTEN
unix  2      [ ACC ]     STREAM     LISTENING     2947     /var/run/gpsd.sock

[BigChimp]

This

Code: [Select]

tcp        0      0 127.0.0.1:2947
means the daemon/program is listening on 127.0.0.1, i.e. localhost/locally only and not on any network interfaces.

That explains why you can't get the gps info from another machine.

[BLL]

Oh b*****! So that's it. Thanks for your help.