Author Topic: Getting Device Information  (Read 6403 times)

Offline Mike Petrichenko

  • Bluetooth Framework Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 2491
  • Karma: 1000
    • Wireless Communication Library
Re: Getting Device Information
« Reply #15 on: March 25, 2007, 02:38:04 PM »
Good time of the day!

OK. I thinkm I know wher eis the bug...

eto ne tupik, eto po hodu zhopa kakaja-to :)
WCL - Wireless Communication Library
TextBlue - Bluetooth Proximity Marketing Software
WCL Phone Explorer - Free Phone Content Manager

Offline AnupamVarghese

  • Newbie
  • *
  • Posts: 46
  • Karma: 0
Re: Getting Device Information
« Reply #16 on: March 26, 2007, 01:16:45 PM »
Mike,

Greetings!

Things seem to be working well for me.
Just one doubt.

GSMModemClient needs port number, what is the best method to determine which port number to use (for both ir and bt)?
OR.. is creating a new COMPort using COMPortCreatorX a good way to do this?

Regards,
AV

Offline Mike Petrichenko

  • Bluetooth Framework Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 2491
  • Karma: 1000
    • Wireless Communication Library
Re: Getting Device Information
« Reply #17 on: March 26, 2007, 02:14:35 PM »
No GMS modem do not need port number for Bluetooth or IrDA. It need it only for Serial Port. The Port property of the BluetoothTransport is a bluetooth RFCOMM channel number. Ususally you do not need change that.
WCL - Wireless Communication Library
TextBlue - Bluetooth Proximity Marketing Software
WCL Phone Explorer - Free Phone Content Manager

Offline AnupamVarghese

  • Newbie
  • *
  • Posts: 46
  • Karma: 0
Re: Getting Device Information
« Reply #18 on: March 26, 2007, 03:21:00 PM »
Funny, when GSMModem is used without setting port number with bluetooth (works good with IR), I get the following error:
 
  System Error.  Code: 10053.
  An established connection was aborted by the software in your host machine

So, I simply set port number = 1 and then tried. It works!

Why so? Is there a solution?

_________________________
Scenario

Device:
    Nokia 6021, Series 40 dp2.

Driver:
    Microsoft.

Framework:
   5.2 beta

Code:
    bgsm.Transport = atBluetooth
    bgsm.BluetoothTransport.Address = dev.Address
    'bgsm.BluetoothTransport.Port = 1    <--- Please Note: Commented out
    bgsm.BluetoothTransport.Radio = Radios.Radio(0)
    Set Radios = Nothing
    bgsm.Open
________________________

Regards,
AV

Offline Mike Petrichenko

  • Bluetooth Framework Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 2491
  • Karma: 1000
    • Wireless Communication Library
Re: Getting Device Information
« Reply #19 on: March 26, 2007, 03:23:47 PM »
It happens because GSMModem can't detect which RFCOM channel used in nokia. So you can leave it as 1. If it is possible, please post shere your nokia services and its port numbers (as it shows in Discovery demo).

Thank you.
WCL - Wireless Communication Library
TextBlue - Bluetooth Proximity Marketing Software
WCL Phone Explorer - Free Phone Content Manager

Offline AnupamVarghese

  • Newbie
  • *
  • Posts: 46
  • Karma: 0
Re: Getting Device Information
« Reply #20 on: March 26, 2007, 03:35:23 PM »
Sure,

Does this screenshot help?

Offline Mike Petrichenko

  • Bluetooth Framework Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 2491
  • Karma: 1000
    • Wireless Communication Library
Re: Getting Device Information
« Reply #21 on: March 26, 2007, 03:46:14 PM »
Yes. Screenshort is very helpfull. Thank you a lot. I'll check why it not works with default settings.
WCL - Wireless Communication Library
TextBlue - Bluetooth Proximity Marketing Software
WCL Phone Explorer - Free Phone Content Manager

Offline AnupamVarghese

  • Newbie
  • *
  • Posts: 46
  • Karma: 0
Re: Getting Device Information
« Reply #22 on: March 26, 2007, 04:50:01 PM »
Mike,

Please let me know when you find out.
Otherwise, please suggest if 
a. first try with no port set,
b. on error set port to 1 (why 1?) and try
- is a good idea.

Regards,
AV

Offline Mike Petrichenko

  • Bluetooth Framework Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 2491
  • Karma: 1000
    • Wireless Communication Library
Re: Getting Device Information
« Reply #23 on: March 26, 2007, 04:59:07 PM »
In fact. The component should automatically detect services and ports for services. Try check AutoDetect property.

Port 1 used because services DialupNetworking uses port 1.

I think the problem is that device has SerialPort service and DialUp Networking (usually it the same). But seems like on SerialPort it do not accept some features or need some authentication/encryption, but for DialUp - not. Component automatically detects SerailPort and try work with it.
WCL - Wireless Communication Library
TextBlue - Bluetooth Proximity Marketing Software
WCL Phone Explorer - Free Phone Content Manager