|T O P I C R E V I E W
||Posted - 09/13/2004 : 04:16:50
I have tried the new 1.20 version and found that if I use bluetooth port COM6 it takes much longer time for on_Read to make a event rather when I use standard port COM1.
In COM1 mode it takes 200ms for my application to recieve a event but in COM6 it takes 1000ms.
This makes the animation in my application very slow.
Is there any way to optimize this, or is the bluetooth stack slower than standard serial port.?
I use the SerialTools on Microsoft Smartphone 2003.
|3 L A T E S T R E P L I E S (Newest First)
||Posted - 09/15/2004 : 04:21:16
I was not sure if the slowing part was the phone or the "Bluetooth to RS232" dongle.
So I wrote a test application that sends a char over ther serial port and measure the time it takes to get a echo response.
When I use a serial cable between PC and my Qtek 8080 (HTC) I got 10 ms in response time. Thats OK.
So changed to bluetooth connection.
The response time was now 1002 ms!!
I removed the "Bluetooth to RS232" dongle and connected a TECOM "Bluetooth to USB" dongle at the PC side. The TECOM use WIDCOMM 1.4210 bluetooth stack.
The responce this time was 1003 ms.
The Qtek 8080 (HTC Voyager) has microsoft bluetooth stack inside.
A conclusion of this is that the microsoft bluetooth stack has some kind of timeout that is set to 1000 ms.
It takes some time to pack/unpack data on the Bluetooth link, but it should not take 1000 ms to do this.
Wonder if there is some way to change this timeout??
||Posted - 09/13/2004 : 06:09:24
The cellular phone is a Qtek 8080, I think that it is Microsofts own BT stack, I don't know the version of it.
The ROM version of the phone is 188.8.131.52
No, it is always 1000 ms.
||Posted - 09/13/2004 : 04:20:40
It is not unlikely it has something to do with the BT stack.
What brand does your device have?
Can you see the version number and brand of the BT stack?
Is the 1000ms only a first response delay, or is it the same even after the first data has been coming in?