Our program supports the cable connection for serial cables, such as original DAU-9p cable, F-Bus cables family, original and generic DLR-3, DLR-3p, Vertu and Samsung cables. Press 'Add' button to add an appropriate serial port. To change the com port just click once on it with left mouse button and choose the COM port from pop-up menu:
Then you should set your cable's type:
Physical COM port connection example:
Virtual COM port connection example:
If you are working with several phones, using Serial port connection, you should add these COM ports also with 'Add' button. 'Remove' button removes current COM port setting and 'Remove all' removes all custom COM-ports. Our software doesn't support M-Bus connection.
DKU-5 connection or CA-42 works only under Windows 2000, Windows XP, Windows XP64, Windows 2003 Server or Windows Vista/Loghorn. To establish DKU-5 connection, just, check 'DKU-5/CA-42' option. Some early versions of DKU-5 drivers may require direct COM-port setting. In this case uncheck 'DKU-5/CA-42' option, add DKU-5's virtual COM port created by DKU-5 drivers and set its type as 'DLR-3/DLR-3p'. Please, don't check 'DKU-5/CA-42' option and direct COM port setting simultaneously. DKU-5 and CA-42 cables may not work with the following models: Nokia 3220, 5140, 5140i, 6020, 6021, 6101, 6103, 6220, 6820, 6822, 7260, 7360.You can use F-Bus cables based on ProLific PL-2303 chipset for these phones.
To set DKU-2 or CA-53 connection just check 'DKU-2/CA-53' option. We support DKU-2/CA-53 connection for all DKU-2/CA-53 capable phones from supported ones , except Nokia 3300. You can connect Nokia 3300 only via F-Bus cable, which connects under the phone's battery. DKU-2 cable in this model isn't connected with the phone section itself and serves for MMC card and MP3 tones management only.
You can establish the Bluetooth connection via Bluetooth Serial Port Profile ( SPP ) assigned for outgoing connections for client applications by your bluetooth stack. Currently tested Bluetooth Stacks are:
| • | Native Microsoft bluetooth stack. |
| • | Widcomm stack from Broadcomm corporation. |
| • | BlueSoleil from IVT corporation. |
| • | BlueFritz! stack from AVM corporation. |
| • | Toshiba generic bluetooth stack. |
| • | BlueManager stack from Extended Systems and Windigo corporation ( works only with 3.1c version). |
Our program doesn't support Fujitsu-Siemens PlugFree bluetooth drivers.
You should pair ( 'bond' , 'trust') your phone with PC before setting Bluetooth connection parameters. Our program doesn't recognize unpaired devices. Also you should enable Bluetooth Serial Port Profile for your phone and make sure, that virtual COM port is assigned for this profile.
In case of Widcomm Bluetooth stack you should connect your phone by 'Nokia PC Suite' service in 'My bluetooth places' folder ( not Nokia PC Suite iself- just the service, create by Bluetooth drivers for phone management software). If you disconnect the phone with PC, one needs to reconnect 'Nokia PC Suite' service manually before running Oxygen Phone Manager for Nokia phones again. Please, don't use 'COM1' service. Same pays to 'Toshiba' and 'AVM Bluefritz!' bluetooth stack: you should connect your phone via COM port marked with 'Nokia PC Suite' sign from the drivers interface. In case of Microsoft Drivers there is no need to connect the phone manually from the driver's interface: just open 'Control panel' -> 'Bluetooth devices' -> 'COM ports' and set your COM port marked with 'Nokia PC Suite' sign in 'Tools' -> 'Options' -> 'Connection and common' as described for cable connection. In case of BlueSoleil bluetooth stack you should connect your phone with 'Bluetooth serial port A' service (this stack doesn't display specific Bluetooth serial port sign). If you are using BlueManager stack from Extended Systems and Windigo, you should choose 'Nokia PC Suite' mode in its setup. Extended Systems drivers use only one COM port in Serial Port Profile both for incoming and outgoing connections. In our program the bluetooth connection setting looks as follows:
If you are using Infra-Red connection just check option Search on IrDA devices. In this case program will try to detect phones connecting via IrDA. There is not need to create a virtual COM port for IRDA connection. Our software works via IRDA stack directly. Our software doesn't support obsolete 'Direct IR' protocol ( implemented in Nokia 6110, 6130, 6150 and 6190 phones). You can connect these phones only via original DAU-9p or generic F-Bus cable:
See also: