[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Nokia 3410 support / development help
From: |
Bertrik Sikken |
Subject: |
Re: Nokia 3410 support / development help |
Date: |
Sun, 01 Dec 2002 17:37:40 +0100 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020826 |
Bertrik Sikken wrote:
<discussion about getting smsc from a Nokia 3410>
Interestingly, in the log from the windows software each of the
transfers involved in getting the smsc has two extra bytes with
something that looks like a sequence number (0x142->0x144->0x146)
Sorry, I see now this is actually part of the fbus 2 protocol.
Perhaps we can tackle the unexpected message (that I receive after
a request for the smsc info) by adding a no-operation case to
the incoming SMS handler. As I understand the packet:
0x1E 0x0c 0x00 0x02 : FBUS packet from phone to PC, command 0x02
0x00 0x06 : length of following data
0x61 0x0f 0x00: FBUS response header?
(this is not specified in nokia.txt or nk6110.txt ????)
0xC9 : data
0x01 : frames-to-go (last frame)
0x44 : sequence number
0x1E 0x8A : checksum
So do you think is it a good idea to add something like
case 0xC9:
break;
to function IncomingSMS1 in nk6100.c ?
(I'll try it anyway...)
Regards,
Bertrik
- Re: Nokia 3410 support / development help,
Bertrik Sikken <=