KPilot with Visor over USB?

[zoniguana]

Has anybody managed to get this working? I seem to be about halfway there... The connection happens, but no transmission does; no data gets backed up and that means no synching happens...

If I start up KPilot first and hit either hotsynch or fastsynch, it asks me to hit the hotsynch button. If I hit the hotsynch button first, KPilot Daemon starts up (in theory) and pretends it is synching the data. It is smart enough to ask the Visor who I am and realize there is a ddiscrepancy. It asks me about my name and, when I tell it to accept the Visor's version, it goes no further than to spin and contemplate its navel...

The Visor is my brain away from home... Can anybody point me in the right direction?

P.S. Mandrake Linux 8.2 running KDE...

[T2F]

http://www.linuxlookup.com/html/guides/visor-jpilot.html
Handspring-Visor with Linux mini-HOWTO

I'm using RedHat 7.3 and JPilot, but just tried KPilot and it worked. Be sure that you are using the right USB ports, the mini-HOWTO instructs you to create symbolic links to /dev/ttyUSB1 for /dev/pilot and /dev/palm. If you put the Visor into the cradle, press the Hotsync button and then run dmsg, you will be able to tell which ports your Visor is using. Mine is:
snip/
usbserial.c: Handspring Visor converter now disconnected from ttyUSB2
hub.c: USB new device connect on bus1/1/5, assigned device number 8
usbserial.c: Handspring Visor converter detected
visor.c: Handspring Visor: Number of ports: 2
visor.c: Handspring Visor: port 1, is for Generic use and is bound to ttyUSB1
visor.c: Handspring Visor: port 2, is for HotSync use and is bound to ttyUSB2
usbserial.c: Handspring Visor converter now attached to ttyUSB1 (or usb/tts/1 for devfs)
usbserial.c: Handspring Visor converter now attached to ttyUSB2 (or usb/tts/2 for devfs)
/snip
As you can see, my Visor comes up on ttyUSB2 (for HotSync), it didn't work well when I had the symbolic link set to ttyUSB1!
I remember that I upgraded JPilot, I'm not sure about pilot-link, but I did install JPilot-syncmal so as to use Avantgo, and it works really well.

[zoniguana]

I have no ttyusb; I have /dev/usb/tty, with no devices listed in there. I already have some sort of a link to /dev/pilot (any way I can find out what's on there - what the link is for?). As I understand it, I cannot set up a symbolic link to /dev/usb/tty; only to a file within there, n'est-ce pas?

So, I'm back to square one. Installed J-Pilot, and it says it is syncing with all the goodies, but the blasted visor comes back and says somethin' **** the bed. When I go into JPilot to look for data and see wht died, it shows no data that is on the Visor. Any way to specify where the data should go? In the individual conduits, I can export the data, but I don't see where I can configure them to send, say, calendar data to KOrganizer. Thoughts?

Thanks!!

[T2F]

It sounds as if your Visor isn't talking to any program. Can you determine which port your Visor is using? To determine where your /dev/pilot is linked, open a console, and cd to /dev. Then type 'ls -l'. Then find the line for "pilot" and it will have the link on it. If that link isn't the same as the second link that the Visor is actually using, it won't talk.

Bill

[zoniguana]

How do I know what port JPilot or KPilot is looking on? I'd prefer to use KPilot, if I can, since that one has more obvious conduit settings (to me), and tosses information where I want it to end up, anyway.

I think there is some level of communication, as KPilot is able to compare the username KPilot has with what is on the Visor (one had justin williams, the other had Justin Williams, and KPilot wanted to know which to use...), but the data is not making it in. Will try looking to see where the link it and see what I can dig up! Thanks!

[X_console]

Moving this to Technical Support.

[T2F]

How do I know what port JPilot or KPilot is looking on?

I don't remember the setup for KPilot, but JPilot has a Configure window. If the Port there is blank, it defaults to '/dev/pilot', and thus to whatever port it links to. I prefer to make my own link of '/dev/visor' and manually insert it, so I know what is going on.
Regards,
Bill

[zoniguana]

Merde alors....

Got J-Pilot working, so, I can snag information off the palm, but I cannot, at this point, get the information over into KOrganizer, which I have been using to date. I think, maybe, I'll just switch to using JPilot as my organizer center and the hell with K-Pilot... LOL

[T2F]

Glad you got it working. I had so little luck with KPilot at first that I just gave up on it too. I am fairly pleased with JPilot, and am using it exclusively.
Regards,
Bill

[zoniguana]

Now if I can just figure out how to prevent it from timing out when using syncMAL or moving large files, I'll be a really happy camper... Doesn't take much for some of us! LOL