pilot-link implements the following protocol stack to
communicate within palm powered devices:
+-----------+
| CMP | DLP |
+-----+-----+
|   PADP    |
+-----------+
|   SLP     |
+-----------+
These protocols are stacked (OSI-stack), e.g.
a DLP packet is packed in a PADP packet and this is packed in 
a SLP packet. SLP contains framing information (marks that 
a packet is starting in the current byte stream). A SLP packet
start every time within the 3 bytes 0xBE 0xEF 0xED.

I have traced the USB byte stream between HotSync and the device,
and normally these magic sequence (0xBE 0xEF 0xED) is in the trace.
But now i have a new M505 connect within "direct" USB. And these
trace doesn't start within these sequence. So the new M505 doesn't
use the SLP protocol, which is correct for the USB communication
because SLP provides framing information which is done by the USB
stack sooner - the protocol is obsolete.

example - first 10 Bytes (from device):
01 FF 00 00 000 16 90 01 00 00 

Anyone have success on a minimal HotSync within M505 and USB ?
begin:vcard 
n:Dietrich;Ralf
tel;fax:+49-30-34902671
tel;work:+49-30-34902670
x-mozilla-html:FALSE
url:http://www.envicon.com
org:envi.con;SE
adr:;;Brandenburgische Str. 69;Berlin;;10713;Germany
version:2.1
email;internet:[EMAIL PROTECTED]
title:Ralf Dietrich
note:http://pinstall.envicon.com
end:vcard

Reply via email to