[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
re: [coldsync-hackers] Palm Sync protocol
- To: Sérgio Girão Filho <sergio at polibrasnet dot com.br>
- Subject: re: [coldsync-hackers] Palm Sync protocol
- From: "John Roets" <jjr at sunflower dot com>
- Date: Mon, 29 Jul 2002 11:19:07 -0500
- Cc: <coldsync-hackers at lusars dot net>
- In-Reply-To: <000e01c235be$8c801da0$0601a8c0@server01>; from sergio@polibrasnet.com.br on Sat, 27 Jul 2002 19:40:03 -0300
- Reply-To: coldsync-hackers at lusars dot net
- Sender: owner-coldsync-hackers at lusars dot net
Howdy Sergio.
Yes, I have had great progress.
To start, I simply changed two lines w/in PConnection_serial.c...
Find the lines (line 642-644[version 2.2.5]) which look like:
/* Set initial rate. 9600 bps required for handshaking */
cfsetispeed(&term, B9600);
cfsetospeed(&term, B9600);
These were meant to set the initial rate for handshaking (with a serial palm cradle).
change these to:
cfsetispeed(&term, B115200);
cfsetospeed(&term, B115200);
These now are set fine to connect to the modem.
Problem is, now you cannot sync with a cradle when you (might) need to.
I therefore went to work and implemented a 'modem;' flag for the listen block (and the command line) to switch between the 9600 and the 115200 settings. It works, and that's what I'm using now. I was going to submit it, but then after discussion with others on the list, I/we? came to the conclusion that a listen block setting for initial-rate would make more sense, and be more generic for other possible future uses. I started working on this, but was bogged down heavily by two clients' work, and haven't the chance yet to resume.
Someone else on the list spoke recently about integrating this and a few other features, and I'm not certain where it led (sorry, I can't remember who that was, and I'm working via webmail as my normal connection is currently down).
As for mgetty, part of my original setup was mgetty>>>ColdSync, but in debugging and finding the initial-rate problem, I eliminated mgetty from the chain, to focus in on the unknown (at that time) error. Currently, ColdSync is listening to the serial port of the modem all alone, and working perfectly ~99% of the time (We've had ~1-2 problems with clients with bad lines in over 4 months with at least 7 clients syncing 1-3 times daily). It shouldn't be a problem though to use mgetty (as I intend to soon myself) via its login setup config, as it only connects, launches ColdSync, and then lets ColdSync handle its own work.
Hope this helps.
If anyone would like to discuss the further work discussed above, or integration of the code I've already developed, please tell me. I'd like to get this code/feature into the project. The solution itself is pretty simple, I'm just a little slow working with the flex/lex stuff.
Thank you.
ColdSync rules. Truly.
> =?iso-8859-1?Q?S=E9rgio_Gir=E3o_Filho?= <sergio@polibrasnet.com.br> wrote:
>
> Hi folks,
does anyone know where I can find information about the protocol used to sync PalmOS based devices, it´s simple because I don't find software that can sync throw direct modem setup so I deciding to develop one!
Please I need urgent help.
Sergio Girão
--
This message was sent through the coldsync-hackers mailing list. To remove
yourself from this mailing list, send a message to majordomo@thedotin.net
with the words "unsubscribe coldsync-hackers" in the message body. For more
information on Coldsync, send mail to coldsync-hackers-owner@thedotin.net.