I have just bought a navigational GPS unit which serves for use in-car and whilst walking. It has a label on the back which says: Win CE .NET 4.2 Core.
I also have a Thinkpad which came with Windows XP. This GPS unit is recognised by XP using active sync but I'd prefer to use RAKI (synce-kde) running under Linux.
After plugging the unit into a USB port I get this in the logs:
kernel: usb 1-7.1: new full speed USB device using ehci_hcd and address 33 kernel: usb 1-7.1: device descriptor read/64, error -32 kernel: usb 1-7.1: device descriptor read/64, error -32 kernel: usb 1-7.1: new full speed USB device using ehci_hcd and address 34 kernel: usb 1-7.1: configuration #1 chosen from 1 choice
There is nothing else in the logs relating to that connection and RAKI does nothing - it apparently does not recognise it and I don't know what the error means.
Any help would be welcome.
On Sun, Apr 08, 2007 at 05:21:58PM +0100, Barry Samuels wrote:
I have just bought a navigational GPS unit which serves for use in-car and whilst walking. It has a label on the back which says: Win CE .NET 4.2 Core.
I also have a Thinkpad which came with Windows XP. This GPS unit is recognised by XP using active sync but I'd prefer to use RAKI (synce-kde) running under Linux.
After plugging the unit into a USB port I get this in the logs:
kernel: usb 1-7.1: new full speed USB device using ehci_hcd and address 33 kernel: usb 1-7.1: device descriptor read/64, error -32 kernel: usb 1-7.1: device descriptor read/64, error -32 kernel: usb 1-7.1: new full speed USB device using ehci_hcd and address 34 kernel: usb 1-7.1: configuration #1 chosen from 1 choice
There is nothing else in the logs relating to that connection and RAKI does nothing - it apparently does not recognise it and I don't know what the error means.
It's been a while since I did any work on synce, but do you have the ipaq driver compiled for your kernel and if so does it get loaded ok when you plug the GPS device in? You need a PPP connection to come up to the device which RAKI will then talk over IIRC. synce-serial-start, if installed, might well help bring this up.
J.
On 08/04/07 17:35:10, Jonathan McDowell wrote:
It's been a while since I did any work on synce, but do you have the ipaq driver compiled for your kernel and if so does it get loaded ok when you plug the GPS device in? You need a PPP connection to come up to the device which RAKI will then talk over IIRC. synce-serial-start, if installed, might well help bring this up.
I'm sure I don't have an ipaq driver in the kernel. Is it something I need even though this GPS is not an ipaq?
On Sun, Apr 08, 2007 at 06:37:34PM +0100, Barry Samuels wrote:
On 08/04/07 17:35:10, Jonathan McDowell wrote:
It's been a while since I did any work on synce, but do you have the ipaq driver compiled for your kernel and if so does it get loaded ok when you plug the GPS device in? You need a PPP connection to come up to the device which RAKI will then talk over IIRC. synce-serial-start, if installed, might well help bring this up.
I'm sure I don't have an ipaq driver in the kernel. Is it something I need even though this GPS is not an ipaq?
You don't give a lot of details about model numbers or what drivers you think you have installed and need, so I'm guessing a bit based on knowledge of connecting up WinCE devices that's a few years old.
The ipaq driver provides what looks like a serial device to the kernel. It operates with a range of WinCE devices, originally the iPaq (hence the name), but also things such as smartphones running WinCE. You then run PPP over this serial device, while the WinCE device also does PPP, providing a network connection. Over this IP layer runs the SynCE software which looks like an ActiveSync instance to the device. RAKI is part of the SynCE layer, but you need the device driver and PPP layers to be operational to have any hope of it working.
Does that help you figure out which steps you've missed perhaps? Of course your GPS require something else entirely in which case ignore all of the above. ;)
J.
Jonathan
Thanks very much for the help you have given - it has helped a great deal. I have now managed to get the thing to connect.
On 08/04/07 20:28:45, Jonathan McDowell wrote:
You don't give a lot of details about model numbers or what drivers you think you have installed and need, so I'm guessing a bit based on knowledge of connecting up WinCE devices that's a few years old.
I didn't give any details because I though that most people wouldn't have heard of it. It's a Road Angel Navigator 7000. I didn't realise that I would need any more drivers as it used USB but you are right the ipaq module does the trick.
The ipaq driver provides what looks like a serial device to the kernel. It operates with a range of WinCE devices, originally the iPaq (hence the name), but also things such as smartphones running WinCE. You then run PPP over this serial device, while the WinCE device also does PPP, providing a network connection. Over this IP layer runs the SynCE software which looks like an ActiveSync instance to the device. RAKI is part of the SynCE layer, but you need the device driver and PPP layers to be operational to have any hope of it working.
I didn't realise that either as there is nothing in the RAKI help which indicates that other software/settings may be necessary.
I've now also installed the synce-serial package and I apparently need to run synce-serial-start before the unit will connect. I also had to run synce-serial-config initially to create the approprite ppp settings. None of this is explained or mentioned in the synce-kde help.
I still have a few problems inasmuchas I cannot connect unless I stop the firewall (Firestarter) first so there are settings there to tweak. The other strange thing is that when I stop the wince connection there are still 3 related network connections showing in Firestarter's active connections box and they won't go away. How do I stop those?
-
Barry Samuels -
Barry Samuels -
Jonathan McDowell