[garyhgaryh]

Originally Posted by HighVoltage

This is interesting, in the Bluetooth log...

28 0.00000475 Pde_reader v3_1 IOCTL_SERIAL_SET_HANDFLOW BtPort2 SUCCESS Shake:1 Replace:40 XonLimit:8192 XoffLimit:2048
....
42 0.00000950 Pde_reader v3_1 IOCTL_SERIAL_SET_HANDFLOW BtPort2 SUCCESS Shake:0 Replace:80000000 XonLimit:8192 XoffLimit:2048

For reference:
XonLim: Specifies the minimum number of bytes allowed in the input buffer before the XON character is sent.
XoffLim: Specifies the maximum number of bytes allowed in the input buffer before the XOFF character is sent. The maximum number of bytes allowed is calculated by subtracting this value from the size, in bytes, of the input buffer.

Curious why these are being set if software flow control is disabled. Is it what is being used between the bluetooth stacks?

Side note:
I believe if fTXContinueOnXoff is true the flag shown up in Replace will be set.

typedef struct _SERIAL_HANDFLOW {
   ULONG ControlHandShake;
   ULONG FlowReplace;
   LONG XonLimit;
   LONG XoffLimit;
   } SERIAL_HANDFLOW,*PSERIAL_HANDFLOW;

#define SERIAL_DTR_MASK           ((ULONG)0x03)
#define SERIAL_DTR_CONTROL        ((ULONG)0x01)
#define SERIAL_DTR_HANDSHAKE      ((ULONG)0x02)
#define SERIAL_CTS_HANDSHAKE      ((ULONG)0x08)
#define SERIAL_DSR_HANDSHAKE      ((ULONG)0x10)
#define SERIAL_DCD_HANDSHAKE      ((ULONG)0x20)
#define SERIAL_OUT_HANDSHAKEMASK  ((ULONG)0x38)
#define SERIAL_DSR_SENSITIVITY    ((ULONG)0x40)
#define SERIAL_ERROR_ABORT        ((ULONG)0x80000000)
#define SERIAL_CONTROL_INVALID    ((ULONG)0x7fffff84)

#define SERIAL_AUTO_TRANSMIT      ((ULONG)0x01)
#define SERIAL_AUTO_RECEIVE       ((ULONG)0x02)
#define SERIAL_ERROR_CHAR         ((ULONG)0x04)
#define SERIAL_NULL_STRIPPING     ((ULONG)0x08)
#define SERIAL_BREAK_CHAR         ((ULONG)0x10)
#define SERIAL_RTS_MASK           ((ULONG)0xc0)
#define SERIAL_RTS_CONTROL        ((ULONG)0x40)
#define SERIAL_RTS_HANDSHAKE      ((ULONG)0x80)
#define SERIAL_TRANSMIT_TOGGLE    ((ULONG)0xc0)
 #define SERIAL_XOFF_CONTINUE      ((ULONG)0x80000000)
#define SERIAL_FLOW_INVALID       ((ULONG)0x7fffff20)

I noticed this as well and I couldn't figure out how this was set.

When cable connected they are set to 0 (XonLimit:0 XoffLimit:0).

[garyhgaryh]

Originally Posted by HighVoltage

Something else to try in all of this is to monitor the serial comm between the GBS301 and the procede while the app is trying to establish communications. This can be helpful to determine if/how much of the data is making its way across and also at what rate(s). Just use a pair of diodes to tap onto the RX and TX (anodes), tie the cathodes together and run that to the RX of another serial port.

With the null modem connection, the Rx line is always negative. I see no data going through. It will usually flash the leds when data is going through, but the LED is solid green (negative voltage).

Gary

[HighVoltage]

Originally Posted by garyhgaryh

With the null modem connection, the Rx line is always negative. I see no data going through. It will usually flash the leds when data is going through, but the LED is solid green (negative voltage).

Gary

Ok if I follow this correctly from your photos, the TX from the Bluetooth becomes RX on the breakout box after the null modem. TX on the Bluetooth should correspond to data from the App. As I recall from you log the app starts by sending only a single byte. At 9600 baud (9600 bits/sec in this scenario), thats 10/9600 for one byte (10 bits = 1 start, 8 data, 1 stop). That means the led will get a pulse for roughly 1 ms. Might be a bit difficult to see if at all. Faster baud rates will only make it harder to see.

And if the 2nd column is some local timestamp:

0.00006258 Pde_reader v3_1 IRP_MJ_WRITE BtPort2 SUCCESS Length 1: .
46 0.00008381 Pde_reader v3_1 IRP_MJ_WRITE BtPort2 SUCCESS Length 1: .
47 0.00008381 Pde_reader v3_1 IRP_MJ_WRITE BtPort2 SUCCESS Length 1: .
48 0.00035982 Pde_reader v3_1 IRP_MJ_WRITE BtPort2 SUCCESS Length 1: .
49 0.00008688 Pde_reader v3_1 IRP_MJ_WRITE BtPort2 SUCCESS Length 1: .
50 0.00008632 Pde_reader v3_1 IRP_MJ_WRITE BtPort2 SUCCESS Length 1: .
51 0.00008549 Pde_reader v3_1 IRP_MJ_WRITE BtPort2 SUCCESS Length 1: .
52 0.00008800 Pde_reader v3_1 IRP_MJ_WRITE BtPort2 SUCCESS Length 1: .
53 0.00008521 Pde_reader v3_1 IRP_MJ_WRITE BtPort2 SUCCESS Length 1: .
54 0.00008716 Pde_reader v3_1 IRP_MJ_WRITE BtPort2 SUCCESS Length 1: .

The duration between transmissions just makes it even harder..

[HighVoltage]

I just noticed something. Is that 2nd column a time delta in seconds? If so, 83 microseconds (usec) is not a whole lot of time to wait for a response.

EDIT: Ah, this was 57600 bps than it makes a little more sense but still seems a bit quick IMHO.

[garyhgaryh]

Originally Posted by HighVoltage

I just noticed something. Is that 2nd column a time delta in seconds? If so, 83 microseconds (usec) is not a whole lot of time to wait for a response.

EDIT: Ah, this was 57600 bps than it makes a little more sense but still seems a bit quick IMHO.

Yeah, it's difficult to see. You see it flickering slightly at the base, but looks solid otherwise. You have to look closely at the base and compare it to the other LEDs on the breakout box to know it's flickering.. very difficult indeed to see.. but you can see the flickering.

[zenmaster]

A number of adapters can take an AT command of ATS3=1 to specify low-latency mode. Have you tried that (while offline)? If there is a timing issue, that might help. Also, I wonder what the portmon log would show from another bluetooth master? BTW, what are you using on the PC end?

[garyhgaryh]

Originally Posted by zenmaster

A number of adapters can take an AT command of ATS3=1 to specify low-latency mode. Have you tried that (while offline)? If there is a timing issue, that might help. Also, I wonder what the portmon log would show from another bluetooth master? BTW, what are you using on the PC end?

On the iogear adapter, typing AT during the first 6 secs will get you into the device's menu. After 6 secs, typing an at command does nothing.

I thought about trying out another BT master. I even though of buying another iogear 301 to use as a master (and using the other one as the slave connected to the procede), but then I might end up with two of them I can't use. So I'm looking for another serial bluebooth device to use as a slave to replace the iogear 301.

On the PC end, I'm using an Airlink ABT-U200 bluetooth adapter. This adapter supports BT v2.0 + EDR with up to 3Mbps data rate. I'm uses the WIDCOMM bluetooth software 5.1.0.2100.

[garyhgaryh]

Originally Posted by HighVoltage

43 0.00000196 Pde_reader v3_1 IOCTL_SERIAL_GET_TIMEOUTS BtPort2 SUCCESS
44 0.00000168 Pde_reader v3_1 IOCTL_SERIAL_SET_TIMEOUTS BtPort2 SUCCESS RI:-1 RM:0 RC:0 WM:0 WC:-1172264056

For some reason it is returning a very large long value (not negative). It is probably using an unsigned value that is getting (mis)interpreted as a signed (2s comp) value by Portman using %d instead of %u in the console (printf) output. In this instance I believe it is sending 0xBA20AB88 , which is +3122703240 but using %d would be shown as 0x..FBA20AB88 or -1172264056. Whoever wrote Portman probably never expected such a large value, and frankly, why would they? It is huge.

I just updated the WIDCOMM bluetooth software from version 5.1.0.2100 to 5.1.0.4200. Seems like that fixed the weird WC value. I think you're right about the WC value being misinterpreted.

I was hoping updating the bluetooth software would magically fix my communication issue with the procede. No such luck.

Gary

[garyhgaryh]

Attached is the trace of the bluetooth stack when I try to connect to the procede via BT. See any clues or anything that stands out?
Gary

04:07:21.671 BTKRNLPortOpenCOM: Device Found
04:07:21.671 BTKRNL_SDP_FindRfcommScn
04:07:21.671 SDP - Originate started
04:07:21.671 L2CA_ConnectReq() PSM: 0x0001
04:07:21.671 L2CA_ConnectReq() BDA: 00-02-5b-00-0b-18
04:07:21.671 LCB 0 Priority:0 XmitWindow:9 Congestion Start:10 End:8 Discard:12
04:07:21.671 BTM_InqDbRead: bd addr [00025b000b18]
04:07:21.671 SetBusyLevel action:3 level:10
04:07:21.671 --
04:07:21.671 SENT Command to HCI. Name: HCI_Create_Connection (Hex Code: 0x0405 Param Len: 13)
04:07:21.671 Parameters
04:07:21.671 BD_ADDR of remote device : 00-02-5b-00-0b-18
04:07:21.671 Packet Types Supported : 0x0018 ( DM1 DH1 )
04:07:21.671 Page Scan Repetition Mode : 1 (0x01)
04:07:21.671 Page Scan Mode(BT1.1) / Reserved(BT1.2) : 0 (0x00)
04:07:21.671 Clock Offset : 64885 (0xfd75)
04:07:21.671 Allow Role Switch : 1 (0x01)
04:07:21.671 --
04:07:21.671 L2CAP - L2CA_conn_req() returned CID: 0x0075
04:07:21.671 --
04:07:21.671 RCVD Event from HCI. Name: HCI_Command_Status (Hex Code: 0x0f Param Len: 4)
04:07:21.671 Parameters
04:07:21.671 Status : Success (0x00)
04:07:21.671 Num HCI Cmd Packets : 1 (0x01)
04:07:21.671 Cmd Code : 0x0405 (HCI_Create_Connection)
04:07:21.671 --
04:07:22.015 --
04:07:22.015 RCVD Event from HCI. Name: HCI_Connection_Complete (Hex Code: 0x03 Param Len: 11)
04:07:22.015 Parameters
04:07:22.015 Status : Success (0x00)
04:07:22.015 Connection Handle : 12 (0x000c)
04:07:22.015 BD_ADDR of remote : 00-02-5b-00-0b-18
04:07:22.015 Link Type : 1 (0x01)
04:07:22.015 Encryption Mode : 0 (0x00)
04:07:22.015 --
04:07:22.015 SetBusyLevel action:4 level:0
04:07:22.015 Security Manager: btm_sec_connected handle:12 status:0 enc_mode:0
04:07:22.015 btm_acl_created: RemBdAddr: 00025b000b18
04:07:22.015 --
04:07:22.015 SENT Command to HCI. Name: HCI_Read_Clock_Offset (Hex Code: 0x041f Param Len: 2)
04:07:22.015 Parameters
04:07:22.015 Connection Handle : 12 (0x000c)
04:07:22.015 --
04:07:22.015 SetPacketType Mask -> 0xcc18
04:07:22.015 SetBusyLevel action:1 level:1
04:07:22.015 btm_sec_execute_procedure: Required:0x80 Flags:0x90 State:0
04:07:22.015 Security Manager: Start get name
04:07:22.015 Duplicate btm_acl_created: RemBdAddr: 00025b000b18
04:07:22.015 L2CAP - LCID: 0x0075 st: CLOSED evt: LOWER_LAYER_CONNECT_CFM
04:07:22.015 Security Manager: l2cap_access_req PSM:1 Handle:12 State:3 Flags:0x90 Required:0x80 Service ID:1
04:07:22.015 btm_sec_execute_procedure: Required:0x80 Flags:0x90 State:3
04:07:22.015 --
04:07:22.015 RCVD Event from HCI. Name: HCI_Command_Status (Hex Code: 0x0f Param Len: 4)
04:07:22.015 Parameters
04:07:22.015 Status : Success (0x00)
04:07:22.015 Num HCI Cmd Packets : 1 (0x01)
04:07:22.015 Cmd Code : 0x041f (HCI_Read_Clock_Offset)
04:07:22.015 --
04:07:22.015 --
04:07:22.015 SENT Command to HCI. Name: HCI_Read_Remote_Version_Information (Hex Code: 0x041d Param Len: 2)
04:07:22.015 Parameters
04:07:22.015 Connection Handle : 12 (0x000c)
04:07:22.015 --
04:07:22.031 --
04:07:22.031 RCVD Event from HCI. Name: HCI_Max_Slots_Changed (Hex Code: 0x1b Param Len: 3)
04:07:22.031 Parameters
04:07:22.031 Connection Handle : 12 (0x000c)
04:07:22.031 LMP Max Slots : 5 (0x05)
04:07:22.031 --
04:07:22.031 --
04:07:22.031 RCVD Event from HCI. Name: HCI_Command_Status (Hex Code: 0x0f Param Len: 4)
04:07:22.031 Parameters
04:07:22.031 Status : Success (0x00)
04:07:22.031 Num HCI Cmd Packets : 1 (0x01)
04:07:22.031 Cmd Code : 0x041d (HCI_Read_Remote_Version_Information)
04:07:22.031 --
04:07:22.031 --
04:07:22.031 SENT Command to HCI. Name: HCI_Change_Connection_Packet_Type (Hex Code: 0x040f Param Len: 4)
04:07:22.031 Parameters
04:07:22.031 Connection Handle : 12 (0x000c)
04:07:22.031 Packet Type : 0xcc18 ( DM1 DH1 DM3 DH3 DM5 DH5 )
04:07:22.031 --
04:07:22.031 --
04:07:22.031 RCVD Event from HCI. Name: HCI_Read_Remote_Version_Information_Complete (Hex Code: 0x0c Param Len: 8)
04:07:22.031 Parameters
04:07:22.031 Status : Success (0x00)
04:07:22.031 Connection Handle : 12 (0x000c)
04:07:22.031 LMP Version : 1 (0x01)
04:07:22.031 Manufacturer Name : 10 (0x000a) [(null)]
04:07:22.031 LMP Subversion : 657 (0x0291)
04:07:22.031 --
04:07:22.031 --
04:07:22.031 RCVD Event from HCI. Name: HCI_Command_Status (Hex Code: 0x0f Param Len: 4)
04:07:22.031 Parameters
04:07:22.031 Status : Success (0x00)
04:07:22.031 Num HCI Cmd Packets : 1 (0x01)
04:07:22.031 Cmd Code : 0x040f (HCI_Change_Connection_Packet_Type)
04:07:22.031 --
04:07:22.031 --
04:07:22.031 SENT Command to HCI. Name: HCI_Write_Link_Supervision_Timeout (Hex Code: 0x0c37 Param Len: 4)
04:07:22.031 Parameters
04:07:22.031 Connection Handle : 12 (0x000c)
04:07:22.031 Timeout (625us units) : 11200 (0x2bc0)
04:07:22.031 --
04:07:22.031 --
04:07:22.031 RCVD Event from HCI. Name: HCI_Connection_Packet_Type_Changed (Hex Code: 0x1d Param Len: 5)
04:07:22.031 Parameters
04:07:22.031 Status : Success (0x00)
04:07:22.031 Connection Handle : 12 (0x000c)
04:07:22.031 Packet Type : 0xcc18 ( DM1 DH1 DM3 DH3 DM5 DH5 )
04:07:22.031 --
04:07:22.031 --
04:07:22.031 RCVD Event from HCI. Name: HCI_Command_Complete (Hex Code: 0x0e Param Len: 6)
04:07:22.031 Parameters
04:07:22.031 Num HCI Cmd Packets : 1 (0x01)
04:07:22.031 Cmd Code : 0x0c37 (HCI_Write_Link_Supervision_Timeout)
04:07:22.031 Status : Success (0x00)
04:07:22.031 Connection Handle : 12 (0x000c)
04:07:22.031 --
04:07:22.031 --
04:07:22.031 SENT Command to HCI. Name: HCI_Write_Link_Policy_Settings (Hex Code: 0x080d Param Len: 4)
04:07:22.031 Parameters
04:07:22.031 Connection Handle : 12 (0x000c)
04:07:22.031 Link Policy Settings : 0x0007
04:07:22.031 : Enable Master Slave Switch
04:07:22.031 : Enable Hold Mode
04:07:22.031 : Enable Sniff Mode
04:07:22.031 --
04:07:22.031 --
04:07:22.031 RCVD Event from HCI. Name: HCI_Command_Complete (Hex Code: 0x0e Param Len: 6)
04:07:22.031 Parameters
04:07:22.046 Num HCI Cmd Packets : 1 (0x01)
04:07:22.046 Cmd Code : 0x080d (HCI_Write_Link_Policy_Settings)
04:07:22.046 Status : Success (0x00)
04:07:22.046 Connection Handle : 12 (0x000c)
04:07:22.046 --
04:07:22.046 --
04:07:22.046 SENT Command to HCI. Name: HCI_Remote_Name_Request (Hex Code: 0x0419 Param Len: 10)
04:07:22.046 Parameters
04:07:22.046 BD_ADDR of remote : 00-02-5b-00-0b-18
04:07:22.046 Page Scan Repetition Mode : 1 (0x01)
04:07:22.046 Page Scan Mode(BT1.1) / Reserved(BT1.2) : 0 (0x00)
04:07:22.046 Clock Offset : 0 (0x0000)
04:07:22.046 --
04:07:22.046 --
04:07:22.046 RCVD Event from HCI. Name: HCI_Command_Status (Hex Code: 0x0f Param Len: 4)
04:07:22.046 Parameters
04:07:22.046 Status : Success (0x00)
04:07:22.046 Num HCI Cmd Packets : 1 (0x01)
04:07:22.046 Cmd Code : 0x0419 (HCI_Remote_Name_Request)
04:07:22.046 --
04:07:22.078 --
04:07:22.078 RCVD Event from HCI. Name: HCI_Read_Clock_Offset_Complete (Hex Code: 0x1c Param Len: 5)
04:07:22.078 Parameters
04:07:22.078 Status : Success (0x00)
04:07:22.078 Connection Handle : 12 (0x000c)
04:07:22.078 Clock Offset : 32118 (0x7d76)
04:07:22.078 --
04:07:22.078 BTM_InqDbRead: bd addr [00025b000b18]
04:07:22.140 --
04:07:22.140 RCVD Event from HCI. Name: HCI_Remote_Name_Request_Complete (Hex Code: 0x07 Param Len: 255)
04:07:22.140 Parameters
04:07:22.140 Status : Success (0x00)
04:07:22.140 BD_ADDR of remote : 00-02-5b-00-0b-18
04:07:22.140 Remote Name : IOGEAR GBS301 0B18 (len: 19)
04:07:22.140 --
04:07:22.140 Security Manager: rmt_name_complete status:0 State:3
04:07:22.140 btm_sec_execute_procedure: Required:0x80 Flags:0x98 State:0
04:07:22.140 Security Manager: access granted
04:07:22.140 L2CAP - LCID: 0x0075 st: ORIG_W4_SEC_COMP evt: SECURITY_COMPLETE
04:07:22.140 L2CAP SENT Command. Name: L2C Connection Request (0x02) ID 0x01, len 4
04:07:22.140 PSM : 0x1
04:07:22.140 Source CID : 0x75
04:07:22.140 --
04:07:22.171 L2CAP RECV Command. Name: L2C Connection Response (0x03) ID: 0x01, Len: 8
04:07:22.171 Destination CID : 0x62
04:07:22.171 Source CID : 0x75
04:07:22.171 Result : 0x1
04:07:22.171 Status : 0x2
04:07:22.171 --
04:07:22.171 L2CAP - LCID: 0x0075 st: W4_L2CAP_CON_RSP evt: PEER_CONNECT_RSP_PND
04:07:22.187 L2CAP RECV Command. Name: L2C Connection Response (0x03) ID: 0x01, Len: 8
04:07:22.187 Destination CID : 0x62
04:07:22.187 Source CID : 0x75
04:07:22.187 Result : 0x0
04:07:22.187 Status : 0x0
04:07:22.187 --
04:07:22.187 L2CAP - LCID: 0x0075 st: W4_L2CAP_CON_RSP evt: PEER_CONNECT_RSP
04:07:22.187 L2CAP - Calling Connect_Cfm_Cb(), CID: 0x0075, Success
04:07:22.187 L2CA_ConfigReq() CID: 0x0075
04:07:22.187 L2CAP - LCID: 0x0075 st: CONFIG evt: UPPER_LAYER_CONFIG_REQ
04:07:22.187 L2CAP SENT Command. Name: L2C Configuration Request (0x04) ID 0x02, len 12
04:07:22.187 Destination CID : 98 (0x0062)
04:07:22.187 Flags (last request) : 0x0000
04:07:22.187 Option type 1 : 4c 06
04:07:22.187 Option type 2 : ff ff
04:07:22.187 --
04:07:22.187 SDP - got conn cnf, sent cfg req, CID: 0x75
04:07:22.218 L2CAP RECV Command. Name: L2C Configuration Response (0x05) ID: 0x02, Len: 6
04:07:22.218 Source CID : 117 (0x0075)
04:07:22.218 Flags (last response) : 0x0000
04:07:22.218 Result : 0 (0x0000)
04:07:22.218 --
04:07:22.234 L2CAP - LCID: 0x0075 st: CONFIG evt: PEER_CONFIG_RSP
04:07:22.234 L2CAP - Calling Config_Rsp_Cb(), CID: 0x0075
04:07:22.234 SDP - Rcvd cfg cfm, CID: 0x75 Result: 0
04:07:22.234 L2CAP RECV Command. Name: L2C Configuration Request (0x04) ID: 0x01, Len: 8
04:07:22.234 Destination CID : 117 (0x0075)
04:07:22.234 Flags (last request) : 0x0000
04:07:22.234 Option type 1 : 30 00
04:07:22.234 --
04:07:22.234 L2CAP - LCID: 0x0075 st: CONFIG evt: PEER_CONFIG_REQ
04:07:22.234 L2CAP - Calling Config_Req_Cb(), CID: 0x0075
04:07:22.234 L2CA_ConfigRsp() CID: 0x0075 Result: 0
04:07:22.234 L2CAP - LCID: 0x0075 st: CONFIG evt: UPPER_LAYER_CONFIG_RSP
04:07:22.234 L2CAP SENT Command. Name: L2C Configuration Response (0x05) ID 0x01, len 6
04:07:22.234 Source CID : 98 (0x0062)
04:07:22.234 Flags (last response) : 0x0000
04:07:22.234 Result : 0 (0x0000)
04:07:22.234 --
04:07:22.234 SDP - Rcvd cfg ind, sent cfg cfm, CID: 0x75
04:07:22.234 --
04:07:22.234 Sent SDP message. PDU Id: SERVICE_SEARCH_ATTR_REQ (Hex: 0x06) Trans: 0 Param Len: 19
04:07:22.234 Descriptor : Data_Ele_Seq (0x06)
04:07:22.234 Length Code : 5 (In next byte)
04:07:22.234 Length : 3
04:07:22.234 Service Search Pattern:
04:07:22.234 Sequence entry : 1.1
04:07:22.234 Descriptor : UUID (0x03)
04:07:22.234 Length Code : 1 (2 bytes)
04:07:22.234 UUID value : 4353 (0x1101) SERVCLASS_SERIAL_PORT
04:07:22.234 Max Attribute Byte Count : 1596 (0x063c)
04:07:22.234 Requested Attribute ID List:
04:07:22.234 Descriptor : Data_Ele_Seq (0x06)
04:07:22.234 Length Code : 5 (In next byte)
04:07:22.234 Length : 9
04:07:22.234 Sequence entry : 1.1
04:07:22.234 Descriptor : Uint (0x01)
04:07:22.234 Length Code : 1 (2 bytes)
04:07:22.234 UINT value : 1 (0x0001) SERVICE_CLASS_ID_LIST
04:07:22.234 Sequence entry : 1.2
04:07:22.234 Descriptor : Uint (0x01)
04:07:22.234 Length Code : 1 (2 bytes)
04:07:22.234 UINT value : 4 (0x0004)
04:07:22.234 Sequence entry : 1.3
04:07:22.234 Descriptor : Uint (0x01)
04:07:22.234 Length Code : 1 (2 bytes)
04:07:22.234 UINT value : 256 (0x0100) SERVICE_NAME
04:07:22.234 Continuation State Len : 0 (0x00)
04:07:22.234 --
04:07:22.234 L2CA_DataWrite() CID: 0x0075 Len: 24
04:07:22.234 L2CAP - LCID: 0x0075 st: OPEN evt: UPPER_LAYER_DATA_WRITE
04:07:22.234 --
04:07:22.234 SENT ACL Data to HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 28 Data: 0x18 0x00 0x62 ...
04:07:22.234 Data:
04:07:22.234 0000: 18 00 62 00 06 00 00 00 13 35 03 19 11 01 06 3c ..b......5.....<
04:07:22.234 0010: 35 09 09 00 01 09 00 04 09 01 00 00 5...........
04:07:22.234 --
04:07:22.265 --
04:07:22.265 RCVD ACL Data from HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 52 Data: 0x30 0x00 0x75 ...
04:07:22.265 Data:
04:07:22.265 0000: 30 00 75 00 07 00 00 00 2b 00 26 36 00 2a 36 00 0.u.....+.&6.*6.
04:07:22.265 0010: 27 09 00 01 35 03 19 11 01 09 00 04 35 0c 35 03 '...5.......5.5.
04:07:22.265 0020: 19 01 00 35 05 19 00 03 08 01 09 01 00 25 09 53 ...5.........%.S
04:07:22.265 0030: 50 02 00 07 P...
04:07:22.265 --
04:07:22.265 L2CAP - LCID: 0x0075 st: OPEN evt: PEER_DATA
04:07:22.265 --
04:07:22.265 Rcvd SDP message. PDU Id: SERVICE_SEARCH_ATTR_RSP (Hex: 0x07) Trans: 0 Param Len: 43
04:07:22.265 Attribute Lists Byte Count : 38 (0x0026)
04:07:22.265 List Data ... : 36 00 2a 36 00 27 09 00 01 35 03 19 11 01 09 00
04:07:22.265 Continuation State Len : 2 (0x02)
04:07:22.265 Cont. State Data : 00 07
04:07:22.265 --
04:07:22.265 --
04:07:22.265 Sent SDP message. PDU Id: SERVICE_SEARCH_ATTR_REQ (Hex: 0x06) Trans: 1 Param Len: 21
04:07:22.265 Descriptor : Data_Ele_Seq (0x06)
04:07:22.265 Length Code : 5 (In next byte)
04:07:22.265 Length : 3
04:07:22.265 Service Search Pattern:
04:07:22.265 Sequence entry : 1.1
04:07:22.265 Descriptor : UUID (0x03)
04:07:22.265 Length Code : 1 (2 bytes)
04:07:22.265 UUID value : 4353 (0x1101) SERVCLASS_SERIAL_PORT
04:07:22.265 Max Attribute Byte Count : 1596 (0x063c)
04:07:22.265 Requested Attribute ID List:
04:07:22.265 Descriptor : Data_Ele_Seq (0x06)
04:07:22.265 Length Code : 5 (In next byte)
04:07:22.265 Length : 9
04:07:22.265 Sequence entry : 1.1
04:07:22.265 Descriptor : Uint (0x01)
04:07:22.265 Length Code : 1 (2 bytes)
04:07:22.265 UINT value : 1 (0x0001) SERVICE_CLASS_ID_LIST
04:07:22.265 Sequence entry : 1.2
04:07:22.265 Descriptor : Uint (0x01)
04:07:22.265 Length Code : 1 (2 bytes)
04:07:22.265 UINT value : 4 (0x0004)
04:07:22.265 Sequence entry : 1.3
04:07:22.265 Descriptor : Uint (0x01)
04:07:22.265 Length Code : 1 (2 bytes)
04:07:22.265 UINT value : 256 (0x0100) SERVICE_NAME
04:07:22.265 Continuation State Len : 2 (0x02)
04:07:22.265 Cont. State Data : 00 07
04:07:22.265 --
04:07:22.265 L2CA_DataWrite() CID: 0x0075 Len: 26
04:07:22.265 L2CAP - LCID: 0x0075 st: OPEN evt: UPPER_LAYER_DATA_WRITE
04:07:22.265 --
04:07:22.265 SENT ACL Data to HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 30 Data: 0x1a 0x00 0x62 ...
04:07:22.265 Data:
04:07:22.265 0000: 1a 00 62 00 06 00 01 00 15 35 03 19 11 01 06 3c ..b......5.....<
04:07:22.265 0010: 35 09 09 00 01 09 00 04 09 01 00 02 00 07 5.............
04:07:22.265 --
04:07:22.296 --
04:07:22.296 RCVD ACL Data from HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 19 Data: 0x0f 0x00 0x75 ...
04:07:22.296 Data:
04:07:22.296 0000: 0f 00 75 00 07 00 01 00 0a 00 07 50 20 73 6c 61 ..u........P sla
04:07:22.296 0010: 76 65 00 ve.
04:07:22.296 --
04:07:22.296 L2CAP - LCID: 0x0075 st: OPEN evt: PEER_DATA
04:07:22.296 --
04:07:22.296 Rcvd SDP message. PDU Id: SERVICE_SEARCH_ATTR_RSP (Hex: 0x07) Trans: 1 Param Len: 10
04:07:22.296 Attribute Lists Byte Count : 7 (0x0007)
04:07:22.296 List Data ... : 50 20 73 6c 61 76 65
04:07:22.296 Continuation State Len : 0 (0x00)
04:07:22.296 --
04:07:22.296 --
04:07:22.296 Full Attribute List:
04:07:22.296 Descriptor : Data_Ele_Seq (0x06)
04:07:22.296 Length Code : 6 (In next word)
04:07:22.296 Length : 42
04:07:22.296 Sequence entry : 1.1
04:07:22.296 Descriptor : Data_Ele_Seq (0x06)
04:07:22.296 Length Code : 6 (In next word)
04:07:22.296 Length : 39
04:07:22.296 Sequence entry : 2.1
04:07:22.296 Descriptor : Uint (0x01)
04:07:22.296 Length Code : 1 (2 bytes)
04:07:22.296 UINT value : 1 (0x0001) SERVICE_CLASS_ID_LIST
04:07:22.296 Sequence entry : 2.2
04:07:22.296 Descriptor : Data_Ele_Seq (0x06)
04:07:22.296 Length Code : 5 (In next byte)
04:07:22.296 Length : 3
04:07:22.296 Sequence entry : 3.1
04:07:22.296 Descriptor : UUID (0x03)
04:07:22.296 Length Code : 1 (2 bytes)
04:07:22.296 UUID value : 4353 (0x1101) SERVCLASS_SERIAL_PORT
04:07:22.296 Sequence entry : 2.3
04:07:22.296 Descriptor : Uint (0x01)
04:07:22.296 Length Code : 1 (2 bytes)
04:07:22.296 UINT value : 4 (0x0004) PROTOCOL_DESC_LIST
04:07:22.296 Sequence entry : 2.4
04:07:22.296 Descriptor : Data_Ele_Seq (0x06)
04:07:22.296 Length Code : 5 (In next byte)
04:07:22.296 Length : 12
04:07:22.296 Sequence entry : 3.1
04:07:22.296 Descriptor : Data_Ele_Seq (0x06)
04:07:22.296 Length Code : 5 (In next byte)
04:07:22.296 Length : 3
04:07:22.296 Sequence entry : 4.1
04:07:22.296 Descriptor : UUID (0x03)
04:07:22.296 Length Code : 1 (2 bytes)
04:07:22.296 UUID value : 256 (0x0100) PROTOCOL_L2CAP
04:07:22.296 Sequence entry : 3.2
04:07:22.296 Descriptor : Data_Ele_Seq (0x06)
04:07:22.296 Length Code : 5 (In next byte)
04:07:22.296 Length : 5
04:07:22.296 Sequence entry : 4.1
04:07:22.296 Descriptor : UUID (0x03)
04:07:22.296 Length Code : 1 (2 bytes)
04:07:22.296 UUID value : 3 (0x0003) PROTOCOL_RFCOMM
04:07:22.296 Sequence entry : 4.2
04:07:22.296 Descriptor : Uint (0x01)
04:07:22.296 Length Code : 0 (1 byte)
04:07:22.296 UINT value : 1 (0x01)
04:07:22.296 Sequence entry : 2.5
04:07:22.296 Descriptor : Uint (0x01)
04:07:22.296 Length Code : 1 (2 bytes)
04:07:22.296 UINT value : 256 (0x0100) SERVICE_NAME
04:07:22.296 Sequence entry : 2.6
04:07:22.296 Descriptor : Text_Str (0x04)
04:07:22.296 Length Code : 5 (In next byte)
04:07:22.296 Length : 9
04:07:22.296 Text_String value : SPP slave (len: 9)
04:07:22.296 --
04:07:22.296 SDP - disconnect CID: 0x75
04:07:22.296 L2CA_DisconnectReq() CID: 0x0075
04:07:22.296 L2CAP - LCID: 0x0075 st: OPEN evt: UPPER_LAYER_DISCONNECT_REQ
04:07:22.296 L2CAP SENT Command. Name: L2C Disconnection Request (0x06) ID 0x03, len 4
04:07:22.296 Destination CID : 0x62
04:07:22.296 Source CID : 0x75
04:07:22.296 --
04:07:22.312 L2CAP RECV Command. Name: L2C Disconnection Response (0x07) ID: 0x03, Len: 4
04:07:22.312 Destination CID : 0x62
04:07:22.312 Source CID : 0x75
04:07:22.312 --
04:07:22.312 L2CAP - LCID: 0x0075 st: W4_L2CAP_DISC_RSP evt: PEER_DISCONNECT_RSP
04:07:22.312 L2CAP - Calling DisconnectCfm_Cb(), CID: 0x0075
04:07:22.312 SDP - Rcvd L2CAP disc cfm, CID: 0x75
04:07:22.312 BTM_SetSecurityLevel: Orig:1 Name:SPP slave ID:1 Level:0x0 PSM:0x3 MX_ProtoChan:0x30001
04:07:22.312 RFCOMM_CreateConnection() called SCN: 1 is_server:0 mtu:0
04:07:22.312 RFCOMM_CreateConnection() BDA: 00-02-5b-00-0b-18
04:07:22.312 RFCOMM_CreateConnection dlci:2 signal state:0xb
04:07:22.312 port_open_continue
04:07:22.312 rfc_timer_start - timeout:60
04:07:22.312 port_select_mtu selected 1007 based on connection speed
04:07:22.312 rfc_mx_sm_state_idle - evt:6
04:07:22.312 L2CA_ConnectReq() PSM: 0x0003
04:07:22.312 L2CA_ConnectReq() BDA: 00-02-5b-00-0b-18
04:07:22.312 L2CAP - LCID: 0x0076 st: CLOSED evt: UPPER_LAYER_CONNECT_REQ
04:07:22.312 Security Manager: l2cap_access_req PSM:3 postponed for multiplexer
04:07:22.312 L2CAP - LCID: 0x0076 st: CLOSED evt: SECURITY_COMPLETE
04:07:22.312 L2CAP SENT Command. Name: L2C Connection Request (0x02) ID 0x04, len 4
04:07:22.312 PSM : 0x3
04:07:22.312 Source CID : 0x76
04:07:22.312 --
04:07:22.312 L2CAP - L2CA_conn_req() returned CID: 0x0076
04:07:22.328 L2CAP RECV Command. Name: L2C Connection Response (0x03) ID: 0x04, Len: 8
04:07:22.328 Destination CID : 0x63
04:07:22.328 Source CID : 0x76
04:07:22.328 Result : 0x1
04:07:22.328 Status : 0x2
04:07:22.328 --
04:07:22.328 L2CAP - LCID: 0x0076 st: W4_L2CAP_CON_RSP evt: PEER_CONNECT_RSP_PND
04:07:22.359 L2CAP RECV Command. Name: L2C Connection Response (0x03) ID: 0x04, Len: 8
04:07:22.359 Destination CID : 0x63
04:07:22.359 Source CID : 0x76
04:07:22.359 Result : 0x0
04:07:22.359 Status : 0x0
04:07:22.359 --
04:07:22.359 L2CAP - LCID: 0x0076 st: W4_L2CAP_CON_RSP evt: PEER_CONNECT_RSP
04:07:22.359 L2CAP - Calling Connect_Cfm_Cb(), CID: 0x0076, Success
04:07:22.359 rfc_mx_sm_state_wait_conn_cnf - evt:9
04:07:22.359 rfc_mx_send_config_req
04:07:22.359 L2CA_ConfigReq() CID: 0x0076
04:07:22.359 L2CAP - LCID: 0x0076 st: CONFIG evt: UPPER_LAYER_CONFIG_REQ
04:07:22.359 L2CAP SENT Command. Name: L2C Configuration Request (0x04) ID 0x05, len 8
04:07:22.359 Destination CID : 99 (0x0063)
04:07:22.359 Flags (last request) : 0x0000
04:07:22.359 Option type 1 : 9b 06
04:07:22.359 --
04:07:22.406 L2CAP RECV Command. Name: L2C Configuration Response (0x05) ID: 0x05, Len: 6
04:07:22.406 Source CID : 118 (0x0076)
04:07:22.406 Flags (last response) : 0x0000
04:07:22.406 Result : 0 (0x0000)
04:07:22.406 --
04:07:22.406 L2CAP - LCID: 0x0076 st: CONFIG evt: PEER_CONFIG_RSP
04:07:22.406 L2CAP - Calling Config_Rsp_Cb(), CID: 0x0076
04:07:22.406 rfc_mx_sm_state_configure - evt:11
04:07:22.406 rfc_mx_conf_cnf p_cfg:80550140 res:0
04:07:22.406 L2CAP RECV Command. Name: L2C Configuration Request (0x04) ID: 0x02, Len: 8
04:07:22.406 Destination CID : 118 (0x0076)
04:07:22.406 Flags (last request) : 0x0000
04:07:22.406 Option type 1 : 9b 06
04:07:22.406 --
04:07:22.406 L2CAP - LCID: 0x0076 st: CONFIG evt: PEER_CONFIG_REQ
04:07:22.406 L2CAP - Calling Config_Req_Cb(), CID: 0x0076
04:07:22.406 rfc_mx_sm_state_configure - evt:12
04:07:22.406 rfc_mx_conf_ind p_cfg:bacd3ce4
04:07:22.406 L2CA_ConfigRsp() CID: 0x0076 Result: 0
04:07:22.406 L2CAP - LCID: 0x0076 st: CONFIG evt: UPPER_LAYER_CONFIG_RSP
04:07:22.406 L2CAP SENT Command. Name: L2C Configuration Response (0x05) ID 0x02, len 6
04:07:22.406 Source CID : 99 (0x0063)
04:07:22.406 Flags (last response) : 0x0000
04:07:22.406 Result : 0 (0x0000)
04:07:22.406 --
04:07:22.406 L2CA_DataWrite() CID: 0x0076 Len: 4
04:07:22.406 L2CAP - LCID: 0x0076 st: OPEN evt: UPPER_LAYER_DATA_WRITE
04:07:22.406 --
04:07:22.406 SENT ACL Data to HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 8 Data: 0x04 0x00 0x63 ...
04:07:22.406 Data:
04:07:22.406 0000: 04 00 63 00 03 3f 01 1c ..c..?..
04:07:22.406 --
04:07:22.437 --
04:07:22.437 RCVD ACL Data from HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 8 Data: 0x04 0x00 0x76 ...
04:07:22.437 Data:
04:07:22.437 0000: 04 00 76 00 03 73 01 d7 ..v..s..
04:07:22.437 --
04:07:22.437 L2CAP - LCID: 0x0076 st: OPEN evt: PEER_DATA
04:07:22.437 rfc_mx_sm_sabme_wait_ua - evt:1
04:07:22.437 rfc_timer_stop
04:07:22.437 PORT_StartCnf result:0
04:07:22.437 L2CA_DataWrite() CID: 0x0076 Len: 14
04:07:22.437 L2CAP - LCID: 0x0076 st: OPEN evt: UPPER_LAYER_DATA_WRITE
04:07:22.437 --
04:07:22.437 SENT ACL Data to HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 18 Data: 0x0e 0x00 0x63 ...
04:07:22.437 Data:
04:07:22.437 0000: 0e 00 63 00 03 ef 15 83 11 02 f0 00 00 ef 03 00 ..c.............
04:07:22.437 0010: 00 70 .p
04:07:22.437 --
04:07:22.437 rfc_port_timer_start - timeout:60
04:07:22.468 --
04:07:22.468 RCVD ACL Data from HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 18 Data: 0x0e 0x00 0x76 ...
04:07:22.468 Data:
04:07:22.468 0000: 0e 00 76 00 01 ef 15 81 11 02 e0 00 00 40 01 00 ..v..........@..
04:07:22.468 0010: 00 aa ..
04:07:22.468 --
04:07:22.468 L2CAP - LCID: 0x0076 st: OPEN evt: PEER_DATA
04:07:22.468 rfc_port_timer_stop
04:07:22.468 PORT_ParNegCnf dlci:2 mtu:320 cl: 224 k: 0
04:07:22.468 Security Manager: mx_access_req proto_id:3 chan_id:1 State:0 Flags:0x98 Required:0x83 Service ID:1
04:07:22.468 btm_sec_execute_procedure: Required:0x83 Flags:0x98 State:0
04:07:22.468 Security Manager: access granted
04:07:22.468 L2CA_DataWrite() CID: 0x0076 Len: 4
04:07:22.468 L2CAP - LCID: 0x0076 st: OPEN evt: UPPER_LAYER_DATA_WRITE
04:07:22.468 --
04:07:22.468 SENT ACL Data to HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 8 Data: 0x04 0x00 0x63 ...
04:07:22.468 Data:
04:07:22.468 0000: 04 00 63 00 0b 3f 01 59 ..c..?.Y
04:07:22.468 --
04:07:22.468 rfc_port_timer_start - timeout:60
04:07:22.515 --
04:07:22.515 RCVD ACL Data from HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 8 Data: 0x04 0x00 0x76 ...
04:07:22.515 Data:
04:07:22.515 0000: 04 00 76 00 0b 73 01 92 ..v..s..
04:07:22.515 --
04:07:22.515 L2CAP - LCID: 0x0076 st: OPEN evt: PEER_DATA
04:07:22.515 rfc_port_timer_stop
04:07:22.515 PORT_DlcEstablishCnf dlci:2 mtu:1685 result:0
04:07:22.515 rfc_timer_stop
04:07:22.515 BTKRNLRfcVportMgmtCallback port:9 handle:17 status:0x0000
04:07:22.515 PORT_CheckConnection() handle:17
04:07:22.515 L2CA_DataWrite() CID: 0x0076 Len: 8
04:07:22.515 L2CAP - LCID: 0x0076 st: OPEN evt: UPPER_LAYER_DATA_WRITE
04:07:22.515 --
04:07:22.515 SENT ACL Data to HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 12 Data: 0x08 0x00 0x63 ...
04:07:22.515 Data:
04:07:22.515 0000: 08 00 63 00 03 ef 09 e3 05 0b 8d 70 ..c........p
04:07:22.515 --
04:07:22.515 rfc_port_timer_start - timeout:60
04:07:22.515 BTKRNL_SDP_FindRfcommScn unblocked
04:07:22.515 BTKRNLSetVcomEventCallback: Event callback addr BAC34176
04:07:22.515 BTKRNLSetVcomEventCallback: Data callback addr BAC34380
04:07:22.515 PORT_SetEventCallback() handle:17
04:07:22.515 PORT_SetDataCallback() handle:17 cb 0xb9dee60c
04:07:22.515 PORT_SetEventMask() handle:17 mask:0x3ffff
04:07:22.515 PORT_GetModemStatus() rc:0 handle:17 signal:0
04:07:22.515 --
04:07:22.515 RCVD ACL Data from HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 12 Data: 0x08 0x00 0x76 ...
04:07:22.515 Data:
04:07:22.515 0000: 08 00 76 00 01 ef 09 e3 05 0b 0d aa ..v.........
04:07:22.515 --
04:07:22.515 L2CAP - LCID: 0x0076 st: OPEN evt: PEER_DATA
04:07:22.515 L2CA_DataWrite() CID: 0x0076 Len: 8
04:07:22.515 L2CAP - LCID: 0x0076 st: OPEN evt: UPPER_LAYER_DATA_WRITE
04:07:22.515 --
04:07:22.515 SENT ACL Data to HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 12 Data: 0x08 0x00 0x63 ...
04:07:22.515 Data:
04:07:22.515 0000: 08 00 63 00 03 ef 09 e1 05 0b 0d 70 ..c........p
04:07:22.515 --
04:07:22.515 PORT_ControlInd
04:07:22.515 BTPortEvtCallback handle 17 port 9 event 0xe18
04:07:22.515 PORT_GetModemStatus() rc:0 handle:17 signal:3
04:07:22.515 PORT_ControlInd DTR_DSR : 1, RTS_CTS : 1, RI : 0, DCD : 0 Break : 0
04:07:22.515 PORT_GetState() handle:17
04:07:22.515 PORT_SetState() handle:17
04:07:22.515 PORT_SetState() handle:17 FC_TYPE:0x0
04:07:22.515 PORT_Control() handle:17 signal:0x3
04:07:22.515 PORT_Control() handle:17 signal:0x1
04:07:22.515 PORT_SetState() handle:17
04:07:22.515 PORT_SetState() handle:17 FC_TYPE:0x0
04:07:22.515 PORT_Control() handle:17 signal:0x3
04:07:22.515 PORT_GetState() handle:17
04:07:22.515 PORT_SetState() handle:17
04:07:22.515 PORT_SetState() handle:17 FC_TYPE:0x0
04:07:22.515 L2CA_DataWrite() CID: 0x0076 Len: 14
04:07:22.515 L2CAP - LCID: 0x0076 st: OPEN evt: UPPER_LAYER_DATA_WRITE
04:07:22.515 --
04:07:22.515 SENT ACL Data to HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 18 Data: 0x0e 0x00 0x63 ...
04:07:22.515 Data:
04:07:22.515 0000: 0e 00 63 00 03 ef 15 93 11 0b 06 03 00 11 13 7f ..c.............
04:07:22.515 0010: 3f 70 ?p
04:07:22.515 --
04:07:22.515 rfc_port_timer_start - timeout:60
04:07:22.515 PORT_Control() handle:17 signal:0x3
04:07:22.515 PORT_Control() handle:17 signal:0x1
04:07:22.515 PORT_SetState() handle:17
04:07:22.515 PORT_SetState() handle:17 FC_TYPE:0x0
04:07:22.515 PORT_Control() handle:17 signal:0x3
04:07:22.515 PORT_GetState() handle:17
04:07:22.515 PORT_SetState() handle:17
04:07:22.515 PORT_SetState() handle:17 FC_TYPE:0x0
04:07:22.515 PORT_Control() handle:17 signal:0x4
04:07:22.515 L2CA_DataWrite() CID: 0x0076 Len: 8
04:07:22.515 L2CAP - LCID: 0x0076 st: OPEN evt: UPPER_LAYER_DATA_WRITE
04:07:22.515 --
04:07:22.515 SENT ACL Data to HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 12 Data: 0x08 0x00 0x63 ...
04:07:22.515 Data:
04:07:22.515 0000: 08 00 63 00 03 ef 09 e3 05 0b 85 70 ..c........p
04:07:22.515 --
04:07:22.515 rfc_port_timer_start - timeout:60
04:07:22.515 PORT_Control DTR_DSR : 1, RTS_CTS : 0, RI : 0, DCD : 1 Break : 0
04:07:22.515 PORT_Control() handle:17 signal:0x2
04:07:22.515 L2CA_DataWrite() CID: 0x0076 Len: 8
04:07:22.515 L2CAP - LCID: 0x0076 st: OPEN evt: UPPER_LAYER_DATA_WRITE
04:07:22.515 --
04:07:22.515 SENT ACL Data to HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 12 Data: 0x08 0x00 0x63 ...
04:07:22.515 Data:
04:07:22.515 0000: 08 00 63 00 03 ef 09 e3 05 0b 81 70 ..c........p
04:07:22.515 --
04:07:22.515 rfc_port_timer_start - timeout:60
04:07:22.515 PORT_Control DTR_DSR : 0, RTS_CTS : 0, RI : 0, DCD : 1 Break : 0
04:07:22.515 PORT_SetState() handle:17
04:07:22.515 PORT_SetState() handle:17 FC_TYPE:0x0
04:07:22.515 PORT_Control() handle:17 signal:0x3
04:07:22.515 L2CA_DataWrite() CID: 0x0076 Len: 8
04:07:22.515 L2CAP - LCID: 0x0076 st: OPEN evt: UPPER_LAYER_DATA_WRITE
04:07:22.515 --
04:07:22.515 SENT ACL Data to HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 12 Data: 0x08 0x00 0x63 ...
04:07:22.515 Data:
04:07:22.515 0000: 08 00 63 00 03 ef 09 e3 05 0b 89 70 ..c........p
04:07:22.515 --
04:07:22.515 rfc_port_timer_start - timeout:60
04:07:22.515 PORT_Control DTR_DSR : 0, RTS_CTS : 1, RI : 0, DCD : 1 Break : 0
04:07:22.546 --
04:07:22.546 RCVD ACL Data from HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 12 Data: 0x08 0x00 0x76 ...
04:07:22.546 Data:
04:07:22.546 0000: 08 00 76 00 01 ef 09 e1 05 0b 8d aa ..v.........
04:07:22.546 --
04:07:22.546 L2CAP - LCID: 0x0076 st: OPEN evt: PEER_DATA
04:07:22.546 rfc_port_timer_stop
04:07:22.546 PORT_ControlCnf
04:07:22.546 L2CA_DataWrite() CID: 0x0076 Len: 5
04:07:22.546 L2CAP - LCID: 0x0076 st: OPEN evt: UPPER_LAYER_DATA_WRITE
04:07:22.546 --
04:07:22.546 SENT ACL Data to HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 9 Data: 0x05 0x00 0x63 ...
04:07:22.546 Data:
04:07:22.546 0000: 05 00 63 00 0b ff 01 19 86 ..c......
04:07:22.546 --
04:07:22.546 BTPortEvtCallback handle 17 port 9 event 0x200
04:07:22.546 --
04:07:22.546 RCVD ACL Data from HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 9 Data: 0x05 0x00 0x76 ...
04:07:22.546 Data:
04:07:22.546 0000: 05 00 76 00 09 ff 01 05 5c ..v.....\
04:07:22.546 --
04:07:22.546 L2CAP - LCID: 0x0076 st: OPEN evt: PEER_DATA
04:07:22.546 rfc_inc_credit:5
04:07:22.546 PORT_FlowInd fc:1
04:07:22.609 --
04:07:22.609 RCVD ACL Data from HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 12 Data: 0x08 0x00 0x76 ...
04:07:22.609 Data:
04:07:22.609 0000: 08 00 76 00 01 ef 09 e1 05 0b 85 aa ..v.........
04:07:22.609 --
04:07:22.609 L2CAP - LCID: 0x0076 st: OPEN evt: PEER_DATA
04:07:22.625 PORT_WriteData() max_len:1
04:07:22.625 PORT_WriteData 1 bytes
04:07:22.625 PORT_Write : Data is being sent
04:07:22.625 L2CA_DataWrite() CID: 0x0076 Len: 5
04:07:22.625 L2CAP - LCID: 0x0076 st: OPEN evt: UPPER_LAYER_DATA_WRITE
04:07:22.625 --
04:07:22.625 SENT ACL Data to HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 9 Data: 0x05 0x00 0x63 ...
04:07:22.625 Data:
04:07:22.625 0000: 05 00 63 00 0b ef 03 ff 9a ..c......
04:07:22.625 --
04:07:22.625 BTPortEvtCallback handle 17 port 9 event 0x4004
04:07:22.625 PORT_WriteData() exit written:1
04:07:22.703 --
04:07:22.703 RCVD ACL Data from HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 12 Data: 0x08 0x00 0x76 ...
04:07:22.703 Data:
04:07:22.703 0000: 08 00 76 00 01 ef 09 e1 05 0b 81 aa ..v.........
04:07:22.703 --
04:07:22.703 L2CAP - LCID: 0x0076 st: OPEN evt: PEER_DATA
04:07:22.734 PORT_WriteData() max_len:1
04:07:22.734 PORT_WriteData 1 bytes
04:07:22.734 PORT_Write : Data is being sent
04:07:22.734 L2CA_DataWrite() CID: 0x0076 Len: 5
04:07:22.734 L2CAP - LCID: 0x0076 st: OPEN evt: UPPER_LAYER_DATA_WRITE
04:07:22.734 --
04:07:22.734 SENT ACL Data to HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 9 Data: 0x05 0x00 0x63 ...
04:07:22.734 Data:
04:07:22.734 0000: 05 00 63 00 0b ef 03 ff 9a ..c......
04:07:22.734 --
04:07:22.734 BTPortEvtCallback handle 17 port 9 event 0x4004
04:07:22.734 PORT_WriteData() exit written:1
04:07:22.750 --
04:07:22.750 RCVD ACL Data from HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 18 Data: 0x0e 0x00 0x76 ...
04:07:22.750 Data:
04:07:22.750 0000: 0e 00 76 00 01 ef 15 91 11 0b 06 03 00 11 13 7f ..v.............
04:07:22.750 0010: 3f aa ?.
04:07:22.750 --
04:07:22.750 L2CAP - LCID: 0x0076 st: OPEN evt: PEER_DATA
04:07:22.750 rfc_port_timer_stop
04:07:22.750 PORT_PortNegCnf
04:07:22.750 PORT_PortNegCnf Control Already sent
04:07:22.750 --
04:07:22.750 RCVD ACL Data from HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 12 Data: 0x08 0x00 0x76 ...
04:07:22.750 Data:
04:07:22.750 0000: 08 00 76 00 01 ef 09 e1 05 0b 89 aa ..v.........
04:07:22.750 --
04:07:22.750 L2CAP - LCID: 0x0076 st: OPEN evt: PEER_DATA
04:07:22.843 PORT_WriteData() max_len:1
04:07:22.843 PORT_WriteData 1 bytes
04:07:22.843 PORT_Write : Data is being sent
04:07:22.843 L2CA_DataWrite() CID: 0x0076 Len: 5
04:07:22.843 L2CAP - LCID: 0x0076 st: OPEN evt: UPPER_LAYER_DATA_WRITE
04:07:22.843 --
04:07:22.843 SENT ACL Data to HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 9 Data: 0x05 0x00 0x63 ...
04:07:22.843 Data:
04:07:22.843 0000: 05 00 63 00 0b ef 03 ff 9a ..c......
04:07:22.843 --
04:07:22.843 BTPortEvtCallback handle 17 port 9 event 0x4004
04:07:22.843 PORT_WriteData() exit written:1
04:07:22.906 --
04:07:22.906 RCVD ACL Data from HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 9 Data: 0x05 0x00 0x76 ...
04:07:22.906 Data:
04:07:22.906 0000: 05 00 76 00 09 ff 01 03 5c ..v.....\
04:07:22.906 --
04:07:22.906 L2CAP - LCID: 0x0076 st: OPEN evt: PEER_DATA
04:07:22.906 rfc_inc_credit:5
04:07:22.953 PORT_WriteData() max_len:1
04:07:22.953 PORT_WriteData 1 bytes
04:07:22.953 PORT_Write : Data is being sent
04:07:22.953 L2CA_DataWrite() CID: 0x0076 Len: 5
04:07:22.953 L2CAP - LCID: 0x0076 st: OPEN evt: UPPER_LAYER_DATA_WRITE
04:07:22.953 --
04:07:22.953 SENT ACL Data to HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 9 Data: 0x05 0x00 0x63 ...
04:07:22.953 Data:
04:07:22.953 0000: 05 00 63 00 0b ef 03 ff 9a ..c......
04:07:22.953 --
04:07:22.953 BTPortEvtCallback handle 17 port 9 event 0x4004
04:07:22.953 PORT_WriteData() exit written:1
04:07:23.062 PORT_WriteData() max_len:1
04:07:23.062 PORT_WriteData 1 bytes
04:07:23.062 PORT_Write : Data is being sent
04:07:23.062 L2CA_DataWrite() CID: 0x0076 Len: 5
04:07:23.062 L2CAP - LCID: 0x0076 st: OPEN evt: UPPER_LAYER_DATA_WRITE
04:07:23.062 --
04:07:23.062 SENT ACL Data to HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 9 Data: 0x05 0x00 0x63 ...
04:07:23.062 Data:
04:07:23.062 0000: 05 00 63 00 0b ef 03 ff 9a ..c......
04:07:23.062 --
04:07:23.062 BTPortEvtCallback handle 17 port 9 event 0x4004
04:07:23.062 PORT_WriteData() exit written:1
04:07:23.171 PORT_WriteData() max_len:1
04:07:23.171 PORT_WriteData 1 bytes
04:07:23.171 PORT_Write : Data is being sent
04:07:23.171 L2CA_DataWrite() CID: 0x0076 Len: 5
04:07:23.171 L2CAP - LCID: 0x0076 st: OPEN evt: UPPER_LAYER_DATA_WRITE
04:07:23.171 --
04:07:23.171 SENT ACL Data to HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 9 Data: 0x05 0x00 0x63 ...
04:07:23.171 Data:
04:07:23.171 0000: 05 00 63 00 0b ef 03 ff 9a ..c......
04:07:23.171 --
04:07:23.171 BTPortEvtCallback handle 17 port 9 event 0x4004
04:07:23.171 PORT_WriteData() exit written:1
04:07:23.218 --
04:07:23.218 RCVD ACL Data from HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 9 Data: 0x05 0x00 0x76 ...
04:07:23.218 Data:
04:07:23.218 0000: 05 00 76 00 09 ff 01 03 5c ..v.....\
04:07:23.218 --
04:07:23.218 L2CAP - LCID: 0x0076 st: OPEN evt: PEER_DATA
04:07:23.218 rfc_inc_credit:5
04:07:23.281 PORT_WriteData() max_len:1
04:07:23.281 PORT_WriteData 1 bytes
04:07:23.281 PORT_Write : Data is being sent
04:07:23.281 L2CA_DataWrite() CID: 0x0076 Len: 5
04:07:23.281 L2CAP - LCID: 0x0076 st: OPEN evt: UPPER_LAYER_DATA_WRITE
04:07:23.281 --
04:07:23.281 SENT ACL Data to HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 9 Data: 0x05 0x00 0x63 ...
04:07:23.281 Data:
04:07:23.281 0000: 05 00 63 00 0b ef 03 ff 9a ..c......
04:07:23.281 --
04:07:23.281 BTPortEvtCallback handle 17 port 9 event 0x4004
04:07:23.281 PORT_WriteData() exit written:1
04:07:23.390 PORT_WriteData() max_len:1
04:07:23.390 PORT_WriteData 1 bytes
04:07:23.390 PORT_Write : Data is being sent
04:07:23.390 L2CA_DataWrite() CID: 0x0076 Len: 5
04:07:23.390 L2CAP - LCID: 0x0076 st: OPEN evt: UPPER_LAYER_DATA_WRITE
04:07:23.390 --
04:07:23.390 SENT ACL Data to HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 9 Data: 0x05 0x00 0x63 ...
04:07:23.390 Data:
04:07:23.390 0000: 05 00 63 00 0b ef 03 ff 9a ..c......
04:07:23.390 --
04:07:23.390 BTPortEvtCallback handle 17 port 9 event 0x4004
04:07:23.390 PORT_WriteData() exit written:1
04:07:23.500 PORT_WriteData() max_len:1
04:07:23.500 PORT_WriteData 1 bytes
04:07:23.500 PORT_Write : Data is being sent
04:07:23.500 L2CA_DataWrite() CID: 0x0076 Len: 5
04:07:23.500 L2CAP - LCID: 0x0076 st: OPEN evt: UPPER_LAYER_DATA_WRITE
04:07:23.500 --
04:07:23.500 SENT ACL Data to HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 9 Data: 0x05 0x00 0x63 ...
04:07:23.500 Data:
04:07:23.500 0000: 05 00 63 00 0b ef 03 ff 9a ..c......
04:07:23.500 --
04:07:23.500 BTPortEvtCallback handle 17 port 9 event 0x4004
04:07:23.500 PORT_WriteData() exit written:1
04:07:23.531 --
04:07:23.531 RCVD ACL Data from HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 9 Data: 0x05 0x00 0x76 ...
04:07:23.531 Data:
04:07:23.531 0000: 05 00 76 00 09 ff 01 03 5c ..v.....\
04:07:23.531 --
04:07:23.531 L2CAP - LCID: 0x0076 st: OPEN evt: PEER_DATA
04:07:23.531 rfc_inc_credit:5
04:07:23.609 PORT_WriteData() max_len:1
04:07:23.609 PORT_WriteData 1 bytes
04:07:23.609 PORT_Write : Data is being sent
04:07:23.609 L2CA_DataWrite() CID: 0x0076 Len: 5
04:07:23.609 L2CAP - LCID: 0x0076 st: OPEN evt: UPPER_LAYER_DATA_WRITE
04:07:23.609 --
04:07:23.609 SENT ACL Data to HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 9 Data: 0x05 0x00 0x63 ...
04:07:23.609 Data:
04:07:23.609 0000: 05 00 63 00 0b ef 03 ff 9a ..c......
04:07:23.609 --
04:07:23.609 BTPortEvtCallback handle 17 port 9 event 0x4004
04:07:23.609 PORT_WriteData() exit written:1
04:07:23.718 PORT_WriteData() max_len:1
04:07:23.718 PORT_WriteData 1 bytes
04:07:23.718 PORT_Write : Data is being sent
04:07:23.718 L2CA_DataWrite() CID: 0x0076 Len: 5
04:07:23.718 L2CAP - LCID: 0x0076 st: OPEN evt: UPPER_LAYER_DATA_WRITE
04:07:23.718 --
04:07:23.718 SENT ACL Data to HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 9 Data: 0x05 0x00 0x63 ...
04:07:23.718 Data:
04:07:23.718 0000: 05 00 63 00 0b ef 03 ff 9a ..c......

((continue next post ))

[garyhgaryh]

(( continue from prev page ))
04:07:23.718 --
04:07:23.718 BTPortEvtCallback handle 17 port 9 event 0x4004
04:07:23.718 PORT_WriteData() exit written:1
04:07:23.718 CBtSerialApp::~CBtSerialApp
04:07:23.718 PORT_Control() handle:17 signal:0x2
04:07:23.718 PORT_Control() handle:17 signal:0x4
04:07:23.718 L2CA_DataWrite() CID: 0x0076 Len: 8
04:07:23.718 L2CAP - LCID: 0x0076 st: OPEN evt: UPPER_LAYER_DATA_WRITE
04:07:23.718 --
04:07:23.718 SENT ACL Data to HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 12 Data: 0x08 0x00 0x63 ...
04:07:23.718 Data:
04:07:23.718 0000: 08 00 63 00 03 ef 09 e3 05 0b 81 70 ..c........p
04:07:23.718 --
04:07:23.718 rfc_port_timer_start - timeout:60
04:07:23.718 PORT_Control DTR_DSR : 0, RTS_CTS : 0, RI : 0, DCD : 1 Break : 0
04:07:23.718 BTKRNLSetVcomEventCallback: Event callback addr 00000000
04:07:23.718 BTKRNLSetVcomEventCallback: Data callback addr 00000000
04:07:23.718 PORT_SetEventCallback() handle:17
04:07:23.718 PORT_SetDataCallback() handle:17 cb 0xb9dee60c
04:07:23.718 PORT_CheckConnection() handle:17
04:07:23.718 RFCOMM_RemoveConnection() handle:17
04:07:23.718 BTPortEvtCallback handle 17 port 9 event 0x8098
04:07:23.718 rfc_port_timer_start - timeout:3
04:07:23.718 L2CA_DataWrite() CID: 0x0076 Len: 4
04:07:23.718 L2CAP - LCID: 0x0076 st: OPEN evt: UPPER_LAYER_DATA_WRITE
04:07:23.718 --
04:07:23.718 SENT ACL Data to HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 8 Data: 0x04 0x00 0x63 ...
04:07:23.718 Data:
04:07:23.718 0000: 04 00 63 00 0b 53 01 b8 ..c..S..
04:07:23.718 --
04:07:23.765 --
04:07:23.765 RCVD ACL Data from HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 12 Data: 0x08 0x00 0x76 ...
04:07:23.765 Data:
04:07:23.765 0000: 08 00 76 00 01 ef 09 e1 05 0b 81 aa ..v.........
04:07:23.765 --
04:07:23.765 L2CAP - LCID: 0x0076 st: OPEN evt: PEER_DATA
04:07:23.781 --
04:07:23.781 RCVD ACL Data from HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 8 Data: 0x04 0x00 0x76 ...
04:07:23.781 Data:
04:07:23.781 0000: 04 00 76 00 0b 73 01 92 ..v..s..
04:07:23.781 --
04:07:23.781 L2CAP - LCID: 0x0076 st: OPEN evt: PEER_DATA
04:07:23.781 rfc_port_closed
04:07:23.781 rfc_port_timer_stop
04:07:23.781 rfc_mx_sm_state_connected - evt:8
04:07:23.781 rfc_timer_start - timeout:3
04:07:23.781 L2CA_DataWrite() CID: 0x0076 Len: 4
04:07:23.781 L2CAP - LCID: 0x0076 st: OPEN evt: UPPER_LAYER_DATA_WRITE
04:07:23.781 --
04:07:23.781 SENT ACL Data to HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 8 Data: 0x04 0x00 0x63 ...
04:07:23.781 Data:
04:07:23.781 0000: 04 00 63 00 03 53 01 fd ..c..S..
04:07:23.781 --
04:07:23.781 rfc_port_timer_stop
04:07:23.781 port_rfc_closed in CLOSING state
04:07:23.781 rfc_port_closed DONE
04:07:23.781 rfc_mx_sm_state_disc_wait_ua - evt:8
04:07:23.781 rfc_port_timer_stop
04:07:23.812 --
04:07:23.812 RCVD ACL Data from HCI. Handle: 0x00c Boundary: 2 Brdcst: 0 Len: 8 Data: 0x04 0x00 0x76 ...
04:07:23.812 Data:
04:07:23.812 0000: 04 00 76 00 03 73 01 d7 ..v..s..
04:07:23.812 --
04:07:23.812 L2CAP - LCID: 0x0076 st: OPEN evt: PEER_DATA
04:07:23.812 rfc_mx_sm_state_disc_wait_ua - evt:1
04:07:23.812 L2CA_DisconnectReq() CID: 0x0076
04:07:23.812 L2CAP - LCID: 0x0076 st: OPEN evt: UPPER_LAYER_DISCONNECT_REQ
04:07:23.812 L2CAP SENT Command. Name: L2C Disconnection Request (0x06) ID 0x06, len 4
04:07:23.812 Destination CID : 0x63
04:07:23.812 Source CID : 0x76
04:07:23.812 --
04:07:23.812 rfc_timer_stop
04:07:23.859 L2CAP RECV Command. Name: L2C Disconnection Response (0x07) ID: 0x06, Len: 4
04:07:23.859 Destination CID : 0x63
04:07:23.859 Source CID : 0x76
04:07:23.859 --
04:07:23.859 L2CAP - LCID: 0x0076 st: W4_L2CAP_DISC_RSP evt: PEER_DISCONNECT_RSP
04:07:24.250 CBtComIf:elayedDeviceRemove: found event for bda=180b005b0200
04:07:25.296 --
04:07:25.296 SENT Command to HCI. Name: HCI_Disconnect (Hex Code: 0x0406 Param Len: 3)
04:07:25.296 Parameters
04:07:25.296 Connection Handle : 12 (0x000c)
04:07:25.296 Reason : 19 (0x13)
04:07:25.296 --
04:07:25.296 --
04:07:25.296 RCVD Event from HCI. Name: HCI_Command_Status (Hex Code: 0x0f Param Len: 4)
04:07:25.296 Parameters
04:07:25.296 Status : Success (0x00)
04:07:25.296 Num HCI Cmd Packets : 1 (0x01)
04:07:25.296 Cmd Code : 0x0406 (HCI_Disconnect)
04:07:25.296 --
04:07:25.468 --
04:07:25.468 RCVD Event from HCI. Name: HCI_Disconnection_Complete (Hex Code: 0x05 Param Len: 4)
04:07:25.468 Parameters
04:07:25.468 Status : Success (0x00)
04:07:25.468 Connection Handle : 12 (0x000c)
04:07:25.468 Reason : 22 (0x16)
04:07:25.468 Connection Terminated by Local Host
04:07:25.468 --
04:07:25.468 btm_sco_acl_removed -> bda 00:02:5b:00:0b:18

It looks like the HCI_Disconnect was caused by the other end terminating the connection. I assume other end would be the procede not the iogear adapter.

[zenmaster]

Originally Posted by garyhgaryh

I just updated the WIDCOMM bluetooth software from version 5.1.0.2100 to 5.1.0.4200. Seems like that fixed the weird WC value. I think you're right about the WC value being misinterpreted.

I was hoping updating the bluetooth software would magically fix my communication issue with the procede. No such luck.

This suggests that the SPP-implementation in the Widcomm stack itself is at least partially responsible for the divergence in behavior between a real COM port and a virtual COM port. At this point, it could be the case that all the communication problems are caused by the particular stack.

According to this, the Zoom 4310B USB dongle w/ Toshiba stack has successfully been used in a robot project with the GBS301. That project had a no-flow-control link as well.

[garyhgaryh]

Originally Posted by zenmaster

This suggests that the SPP-implementation in the Widcomm stack itself is at least partially responsible for the divergence in behavior between a real COM port and a virtual COM port. At this point, it could be the case that all the communication problems are caused by the particular stack.

According to this, the Zoom 4310B USB dongle w/ Toshiba stack has successfully been used in a robot project with the GBS301. That project had a no-flow-control link as well.

Thanks .. that was one of the first articles I saw when I got the iogear adapter. With the info on that page, I still can't get the procede to "talk" through the adapter. It could very well be an issue with the SPP-implementation, but I can't say for sure.

Gary

[e.n335]

In case you guys really like to do this project I would recommend the use of 2 Parani adapters. There is a complete description on the forum how to do it, munters has it on his car and he likes it.

I did it in my early PROcede times. The PROcede does not support hardware handshake.

Cheers,
- Eugen

[HighVoltage]

Originally Posted by e.n335

In case you guys really like to do this project I would recommend the use of 2 Parani adapters. There is a complete description on the forum how to do it, munters has it on his car and he likes it.

I did it in my early PROcede times. The PROcede does not support hardware handshake.

Cheers,
- Eugen

I think the whole point is to keep it cheap by sticking with one Bluetooth device.

[e.n335]

Originally Posted by HighVoltage

I think the whole point is to keep it cheap by sticking with one Bluetooth device.

I think the whole point is to keep the SW guessing it's a native RS-232 device. Along with security and stability in the wireless environment.

[HighVoltage]

Actually no it isnt. Thats an issue related to this approach but not the point of the thread. Munter's already contributed the dual Paranis solution on Reply #22. I suggested wifi.

At this stage everyone involved is aware of that alternative solution but is going forward on this approach to try to keep the cost down.

[zenmaster]

Originally Posted by garyhgaryh

Thanks .. that was one of the first articles I saw when I got the iogear adapter. With the info on that page, I still can't get the procede to "talk" through the adapter. It could very well be an issue with the SPP-implementation, but I can't say for sure.

May be worth finding a couple of alternative masters for testing (Zoom was only $18 or something). I'll go in for half of the cost. If Widcomm/Broadcom doesn't work, the remaining stacks seem to be the Toshiba and BlueSoleil. (Mindtree's EtherMind is for embedded use and Microsoft apparently uses sockets instead of virtual COM ports.)

Also, for the Widcomm/Broadcom, take a look under HKLM\SOFTWARE\Widcomm\BtConfig\SerialTransport\. Apparently, flow control defaults can be set there.

[garyhgaryh]

Originally Posted by HighVoltage

I think the whole point is to keep it cheap by sticking with one Bluetooth device.

Yes, that was the reason I'm on this project. Lately, I thought about buying a 2nd iogear gbs301 as a master...

[garyhgaryh]

Originally Posted by zenmaster

May be worth finding a couple of alternative masters for testing (Zoom was only $18 or something). I'll go in for half of the cost. If Widcomm/Broadcom doesn't work, the remaining stacks seem to be the Toshiba and BlueSoleil. (Mindtree's EtherMind is for embedded use and Microsoft apparently uses sockets instead of virtual COM ports.)

Also, for the Widcomm/Broadcom, take a look under HKLM\SOFTWARE\Widcomm\BtConfig\SerialTransport\. Apparently, flow control defaults can be set there.

I bought another master. It's a Micro Innovations mini bluetooth adapter. I only bought it because it's small. I'll give that a try later.

We should not need two serial bluetooth adapter. We only (at least in theory) need it for the slave device which connects to the procede. The master could be another serial bluetooth device configured as a master, or a bluetooth dongle for a PC/PDA/etc, or a built in bluetooth on a laptop or desktop or whatever.

Scalbert: you said you would play with the iogear 301 this past weekend. Any luck?

Gary

[scalbert]

Originally Posted by garyhgaryh

Scalbert: you said you would play with the iogear 301 this past weekend. Any luck?

Nope, after reading your adventures I saw there wasn't a real need. You pretty much confirmed what I saw.

[zenmaster]

Originally Posted by garyhgaryh

I bought another master. It's a Micro Innovations mini bluetooth adapter. I only bought it because it's small. I'll give that a try later.

We should not need two serial bluetooth adapter. We only (at least in theory) need it for the slave device which connects to the procede. The master could be another serial bluetooth device configured as a master, or a bluetooth dongle for a PC/PDA/etc, or a built in bluetooth on a laptop or desktop or whatever.

The idea would be to try all 3 stacks on the PC end - to rule out a stack problem. The stacks tend to be tied to the chipset.

And if GBS301 can't be made to work, there are several RS232 circuit-board kits available (BT 1.1 and 1.2) for around $50.

[garyhgaryh]

Originally Posted by scalbert

Nope, after reading your adventures I saw there wasn't a real need. You pretty much confirmed what I saw.

I've wasted enough time on this. I'm going to try a few more things (see below) and if it doesn't work, I'm going with either a wifi serial or wired option (free as I already have the hw - the rs serial/usb cable).

I'm not saying that it's impossible to get iogear gbs301 to work with the procede. I'm just _almost_ out of options and definately out of patience and ideas. I invested alot of time and some money and I'm no closer than I was a week ago, although I made some progress, the end result is the same - no workie.

Originally Posted by zenmaster

The idea would be to try all 3 stacks on the PC end - to rule out a stack problem. The stacks tend to be tied to the chipset.

And if GBS301 can't be made to work, there are several RS232 circuit-board kits available (BT 1.1 and 1.2) for around $50.

I just installed the generic microsoft bluetooth drivers for the micro innovations mini bluetooth adapter (which is being used as the master). One thing I like about this adapter is that there is no special software to load. It uses the included bluebooth drivers included in XP.

http://www.provantage.com/micro-inno...t~7MCR902C.htm

What's interesting is once all the drivers loaded, the OS said it's ready to use, but I couldn't find any devices (not my cell phone nor the iogear). Then I realize I can't find bluetooth devices with WIDCOMM software/configurator. If I look in the device manager, I noticed subtle differences in the bluetooth device icons (one is called bluetooth devices and the other bluetooth radios). I had to find, in the control panel, the software used to configure the generic bluetooth device. To discover and use a slave device, there is a difference process to set these devices up. After setting up the iogear, I now have an SPP on com11 (incoming) and com12 (outgoing). Not sure what incoming and outgoing means, but I believe incoming is when the device INITIATES communication and outgoing means the COMPUTER initiates the connection. I will be using the later, however, I need to remap to a com port less than 10. Not sure how to do that with this software (yet).

I don't expect this new device to solve my bluetooth issues. If it does, I'll be a happy man.. gotta go...

Gary

PS. It looks like I can use device properties to remap the port!