News Forum Phone database

> New Topic
> Reply
< Esato Forum Index > Sony Ericsson / Sony > Technical > Mitsumi usb bt & t68 & xntdconnect wont connect Bookmark topic

Hi!

I am currently strugling with the above combination.

What I am able to do is: Connect to the phone over BT with hyperterminal and give AT-commands, connect to the phone using ??flaw?? mobile agent.
It look's like any program that uses COM port "correctly" works...

Why is it so that when I try to use that sw. made by Ericsson I'll just get message phone not found... At the bottom of this post is short cut-n-paste from mobile phone monitor's debugger.

Phone is T68 upgraded to sw. R2E006, USB-BT is Mitsumi WIF-0402C (www.mitsumi.de), OS is W2k Pro. + SP2.

Anyone had similiar problems ??? Resolved???? Please help...

Debug out start------

(+317.704 s) 0x0658 CPortPoll (2) :Port \.ANUBCOM has status DISCONNECTED
(+317.704 s) 0x0658 CPortPoll (2) :PollComport \.ANUBCOM for arrive
(+317.704 s) 0x0658 CCOMMPortResourceCollection (2) :Lock \.ANUBCOM
(+317.704 s) 0x0658 CPortPoll (2) :PollForArrival of \.ANUBCOM
(+317.704 s) 0x0658 CPortPoll (2) :Poll \.ANUBCOM for arrival
(+317.704 s) 0x0658 CAB (2) :Entering _CAB_CreateFile
(+317.704 s) 0x0658 CAB (2) :_CAB_CreateFile - Reserved port, current port is INVALID_HANDLE_VALUE
(+317.705 s) 0x0658 CAB (0) :_CAB_CreateFile - Could not open port, INVALID_HANDLE_VALUE
(+317.705 s) 0x0658 CAB (2) :PollComport - CreateFile(\.ANUBCOM) API failure (0x2)
(+317.705 s) 0x0658 CPortPoll (2) :Poll PORT_STATUS_UNKNOWN
(+317.705 s) 0x0658 CPortPoll (2) :PollForArrival of \.ANUBCOM finished
(+317.705 s) 0x0658 CCOMMPortResourceCollection (2) :Unlock \.ANUBCOM
(+317.705 s) 0x0658 CPortPoll (2) :m_vPortPollInfo.Unlock()
(+318.265 s) 0x0644 MSIrSock (1) :getCurrentIrSocketDevices Getsockopt error: 10050 PROBABLY DISABLED
(+318.705 s) 0x0658 CPortPoll (2) :m_PhoneVisualiser.IsPolling(TRUE)
(+318.705 s) 0x0658 CPortPoll (2) :m_vPortPollInfo.Lock()
(+318.705 s) 0x0658 CPortPoll (2) :Port COM3 has status DISCONNECTED
(+318.705 s) 0x0658 CPortPoll (2) :PollComport COM3 for arrive
(+318.705 s) 0x0658 CCOMMPortResourceCollection (2) :Lock COM3
(+318.705 s) 0x0658 CPortPoll (2) :PollForArrival of COM3
(+318.706 s) 0x0658 CPortPoll (2) :Poll COM3 for arrival
(+318.706 s) 0x0658 CAB (2) :Entering _CAB_CreateFile
(+318.706 s) 0x0658 CAB (2) :_CAB_CreateFile - Open reserved port, but no change in mode
(+321.810 s) 0x0658 CAB (1) :_AsynchQueryPort - No modem status in 3000 ms.
(+321.810 s) 0x0658 CAB (2) :Entering _CAB_CloseHandle
(+321.810 s) 0x0658 CAB (2) :open port not really closed
(+321.810 s) 0x0658 CPortPoll (2) :Poll PORT_STATUS_UNCHANGED
(+321.810 s) 0x0658 CPortPoll (2) :PollForArrival of COM3 finished




[ This Message was edited by: make10 on 2002-08-12 07:36 ]
--
Posted: 2002-08-12 08:35:00
Edit : Quote


check the virtual com port config in MPM settings
--
Posted: 2002-08-12 08:40:00
Edit : Quote


already checked, only COM3 is enabled, it is also reserved(won't affect if it's not reserved).

Is there anyway to configure the timeout value and/or force MPM to monitor only COMx (currently it still check's that which port to monitor)... Crawled through registry but found nothing......
--
Posted: 2002-08-12 09:00:00
Edit : Quote


the bluetooth adapters usually uses virtual com ports. is com 3 a virtual com port in your sytem?

if not, check your serial port settings in your bt configuration program
--
Posted: 2002-08-12 14:42:00
Edit : Quote


Yes it is, as I already said I can connect to the phone over bt but MPM won't detect my phone...

Btw. in the commercial version of XNTD sw. there is possibility to set com-port and it's speed or select IR.... Too bad that, atleast trial version won't support T68...
--
Posted: 2002-08-13 07:47:00
Edit : Quote

---

New Topic   Reply

Forum Index