Tony, let's deal with the easiest and move toward the progressively more complicated.
Regarding your 64bit machine....Yeah, it is a shame. While it could work; it might work....I'm just not the one to troubleshoot it. You will have to tackle that by yourself or find someone brave enough to poke up their head.
TOR is "The Onion Router". It's a clever little bit of wizardry that takes your data packets and wraps other layers around it...like an onion. When you connect to the TOR network by enabling it your data is sent to its ultimate destination, from one node to the next in the network, in which each node knows its predecessor and successor, but no others. Traffic flowing through the network is unwrapped by a symmetric key at each node, which reveals the next downstream node.
What does this all mean?
It preserves anonymity to a great degree. Routers and servers do not know the ultimate source, or destination, of the data request. The TOR network just gets the data and passes it along...from you; back to you.
TOR is included in Navigatrix to provide greater access to information if the need is required and not specifically to provide anonymity.
Let me explain with a real life example.
In Panama, there is a wifi network called "InternetParaTodos". It is a good service provided by the government of Panama to make internet access eventually to everyone in the country. But to make this limited resource available to more people they block high bandwidth sites like Youtube, other video streaming sites, so a small handful of people don't suck all the bandwidth leaving everyone with frustratingly slow internet access. They also block websites deemed socially inappropriate.
Unfortunately, and for whatever conspiratorial reason you want, they also block web sites to many open source sites that are low bandwidth (sourceforge, github, etc.).
It does not provide a cloak of invisibility, but using TOR a person can pass through blocks and access the data s/he wants/needs.
On my "work" machine I upgrade OpenCPN to 3.0.2 to test it just after it came out. For me there is no real added functionality. There have been a few bug fixes, like the "Object Query" window will now close with "OK". And there have been a few stylistic changes which are an improvement, but still take time to become accoustomed. However, the irritation is the default Chart Text font is too large and bold. To each his own.... But, nothing I have done so far keeps my preference from one session to the next. This may have been fixed in subsequent releases.
Now, with regards to your GPS and your AIS, it depends how you plan on receiving the data. You stated the GPS was a Garmin Hockey Puck. If you pump in the AISdata through the sound card it would be un-effected. It comes in via /tmp/aisfifo.
however,for the GPS in OpenCPN the important selection is Network LIBGPS. Baud Rate is handled by gpsd. You could set the rate to 115200 (standard maximum) on any application...if that option were available.
But it looks like your GPS is not getting picked up by gpsd.
For fun let's try a little experiment....(the longer version shouldn't be necessary.)
Open up a terminal
<ctrl><alt><t>
Unplug your GPS if it's already plugged in and then plug it back in. If it's not plugged in; plug it in.
Into the open terminal enter (cut 'n' paste for ease.):
sudo dmesg | tailThe vertical line is called a 'pipe' and is located on the backslash key above the <enter> key (US 105 keyboards).
This provides the tail end of a potentially very long log of everything that has happened to the hardware on your computer since it has been fired up.
By having a freshly plugged in GPS, that command will show what happens when you plug it in. If you missed it, or it was so much fun, you can do it again and again.
It will look something like this:
Code:
Moe@Baboo:~ $ dmesg | tail
[12509.624561] usb 2-2: reset full speed USB device using uhci_hcd and address 6
[12509.771114] usb 2-2: cp210x converter now attached to ttyUSB0
[12525.656138] usb 2-2: USB disconnect, address 6
[12525.656697] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[12525.656772] cp210x 2-2:1.0: device disconnected
[12540.064602] usb 2-2: new full speed USB device using uhci_hcd and address 7
[12540.231390] usb 2-2: configuration #1 chosen from 1 choice
[12540.237448] cp210x 2-2:1.0: cp210x converter detected
[12540.348106] usb 2-2: reset full speed USB device using uhci_hcd and address 7
[12540.499403] usb 2-2: cp210x converter now attached to ttyUSB0
Moe@Baboo:~ $
The numbers in the [brackets] on the left side indicate how long the computer has been running. The important info for us what and where the recently plugged in GPS is connected.
As you see, my off-brand GPS (cp210x) is now attached to ttyUSB0. Isn't that exciting.
Now you are going to turn off the gpsd by entering into the terminal:
sudo /etc/init.d/gpsd stopNext we will fire up the gpsd and specifically tell it to look for your GPS because you know where it is.
Enter:
sudo gpsd -b -N -D 4 /dev/ttyUSB0The last bit "/dev/ttyUSB0" being the "/dev/location_of_you_GPS" that you now know because you ran dmesg | tail.
This starts the gpsd. "-b" just reads the GPS without writing to it; "-n" runs gpsd without being asked; "-N" runs gpsd in the foreground; and "-D 4" makes gpsd chatter about everything, and I mean everything. (Remember to use "-b" just to be 'on the safe side' otherwise the GPS could be latched in inappropriate configurations for less sophisticated software like in Windows. This is the reason for the "write errors" in the output below. If you don't plan on using the GPS with Windows, it's not an issue.)
...just let it set there for a few minutes. The gps' internal almanac might need to updated. Go get a drink. On a cold-cold start of some gps-es it can take up to 29 minutes to update the current almanac and return data...so I'm told. I've never had anything (that worked) take that long.
Eventually, we hope, it will look something like this:
Code:
Moe@Baboo:~ $ gpsd -b -n -N -D 4 /dev/ttyUSB0
gpsd: launching (Version 2.95)
gpsd: listening on port gpsd
gpsd: NTPD shmat(262152,0,0) succeeded, segment 2
gpsd: NTPD shmat(294921,0,0) succeeded, segment 3
gpsd: successfully connected to the DBUS system bus
gpsd: running with effective group ID 1000
gpsd: running with effective user ID 1000
gpsd: opening read-only GPS data source type 3 and at '/dev/ttyUSB0'
gpsd: speed 115200, 8N1
gpsd: attempting USB device enumeration.
gpsd: 1d6b:0002 (bus 1, device 1)
gpsd: 1d6b:0001 (bus 2, device 1)
gpsd: 1d6b:0001 (bus 3, device 1)
gpsd: 1d6b:0001 (bus 4, device 1)
gpsd: 1d6b:0001 (bus 5, device 1)
gpsd: 064e:a102 (bus 1, device 2)
gpsd: 093a:2510 (bus 2, device 5)
gpsd: 10c4:ea60 (bus 2, device 9)
gpsd: vendor/product match with 091e:0003 not found
gpsd: Probing TSIP
gpsd: speed 9600, 8O1
gpsd: speed 115200, 8N1
gpsd: no probe matched...
gpsd: gpsd_activate(): opened GPS (fd 6)
gpsd: speed 4800, 8N1
gpsd: switch_driver(SiRF binary) called...
gpsd: selecting SiRF binary driver...
gpsd: NTPD ntpd_link_activate: 1
gpsd: /dev/ttyUSB0 identified as type SiRF binary (2.011532 sec @ 4800bps)
gpsd: SiRF: baudrate: 4800
gpsd: PPS Create Thread gpsd_ppsmonitor
gpsd: SiRF: unset MID 30...
gpsd: SiRF: Writing error.
gpsd: SiRF: Requesting periodic ecef reports...
gpsd: SiRF: Writing error.
gpsd: SiRF: Requesting periodic tracker reports...
gpsd: SiRF: Writing error.
gpsd: SiRF: Setting DGPS control to use SBAS...
gpsd: SiRF: Writing error.
gpsd: SiRF: Setting SBAS to auto/integrity mode...
gpsd: SiRF: Writing error.
gpsd: SiRF: unset MID 29...
gpsd: SiRF: Writing error.
gpsd: SiRF: Probing for firmware version...
gpsd: SiRF: Writing error.
gpsd: SiRF: Requesting navigation parameters...
gpsd: SiRF: Writing error.
gpsd: SiRF: MND 0x02: Navtype = 0x84, Status = 2, mode = 3
gpsd: SiRF: NTPD SEEN_GPS_2
gpsd: SiRF: NTPD valid time MID 0x02, seen=0x00, time;1344735688.00, leap:15
gpsd: SiRF: MND 0x02: time=1344735688.00 lat=-18.86 lon=-159.80 alt=10.33 track=0.00 speed=0.00 mode=3 status=2 hdop=0.60 used=10 mask={TIME|LATLON|ALTITUDE|SPEED|TRACK|CLIMB|STATUS|MODE|DOP|USED}
...and on, and on, and on.
While it is running open up the GPS Satellite program to see if data spews forth...or OpenCPN.
To stop the blur of data and kill gpsd hit
<ctrl><c>
Ok, by now you might be saying, "Sure, Moe, this is a lot of fun...but does it have a purpose?"
Since you can't see me shrug my shoulders I'll tell you that we would hope to find out:
1)How and where your GPS is recognized on your machine.
2)Differentiate a possible problem with gpsd and a possible, what is called a, "hotplug" issue.
3)See how gpsd responds to your gps when they are specifically connected.
3)Find out what's inside your Garmin hockey puck
..and the third-third thing is how to make it work.
If by some miracle it does work. Reboot, or enter in the terminal:
sudo /etc/init.d/gpsd startto restart the gpsd...or just reboot and it will do it for you.
OR, now that you have done all that...and you gps still doesn't show where your sitting; Cut 'n' paste the output from:
sudo dmesg |tail
and 40 lines, or so of
sudo gpsd -b -n -N -D 4 /dev/whatever_but_should_be_ttyUSB0_or_1_or_ttyUSBsomething.
to a new post and we can take a look-see.