east_galway_wan@yahoo.ie (eurorunner) wrote in message news:<f313d646.0406010233.52d8756e@posting.google. com>...
> I have purchased a 3310 data cable, connected it correctly to the
> phone and the serial port of the pc. Downloaded oxygen phone manager
> -> but oxygen is not detecting the phone. I have selected the various
> cable types (DAU-9P/FBUS; DLR 3/DLR-3P) that are available in the
> oxygen option settings but it still doesnt pick up the 3310.
>
>
> As i understand it there are different data cable types? If so, how
> do i know what type the data cable i have is ...as there are no
> markings on it. Only thing it has is a switch with options of 'M' or
> 'F' - which should i select??
>
> I think i came across something about needing to have the correct
> drivers for a specific data cable? can this be the case???
>
>
> Would be grateful if you can share the knowledge.
Thank you for your request!
The cable, you are using, isn't DLR-3p. The cable should be of F-Bus
type, so you could establish connection between the phone and PC.
Please, check the following cable's parameters and settings:
Do you have any switches on your cable? If yes, you should switch the
cable to F(F-Bus) mode.
The cable's PIN contacts should be of the same length and none of
these should stuck in cable's contact platform. Is it true? If not,
then the cable is defective.
Have you removed isolating foam around the cable's PIN contacts? You
should remove this, as the foam may block cable contacts.
Please, check, whether you have placed the battery to corresponding
battery holders (slots) in the cable's contact platform.
Is the phone turned on, while trying to establish connection? The
phone should be turned on, so the signal could reach the phone.
---
Are you running any other phone management programs simultaneously
with Oxygen Phone Manager II? If yes, please, close such programs, as
they may occupy all of the phone's connectivity capabilites.
Unfortunately not all PC mainboards may support F-Bus (full duplex,
115200 bit/s) mode under MS Windows NT 4.0/2000/XP/2003 Server. In
this case, changing IRQ (Interrupt Request) number, assigned for
serial COM port used may help.
IMPORTANT NOTE: Please, do not (!) perform this operation, if you are
not hardware professional to avoid possible system malfunction! If you
are not sure, how to do it, please, contact your system administrator
and/or hardware service company. In other case, you are using
instructions below on your own risk only:
==========
How to change IRQ (Interrupt Request) number under MS Windows NT
4.0/2000/XP/2003 Server:
You can change IRQ (Interrupt Request) number in 'Start' -> 'Control
panel' -> 'System' -> 'Hardware' -> 'Device Manager' -> 'Ports COM &
LPT' -> right-click on corresponding COM port number -> select
'Properties' option from the POP-up menu -> select 'Resources'
bookmark -> uncheck 'Automatic tunning (set-up)' option (name depends
on COM port's drivers)
Here you can select another IRQ (Interrupt Request) from already
predefined confingurations or specify another IRQ directly by
selecting 'IRQ' ('Interrup Request') resource and pressing 'Change'
button (may not function with some PC motherboards).
REM.: Some PC motherboards may allow to change IRQ number from BIOS
only (log in during startup session).
Just change your IRQ (Interrupt Request) number to another free one in
your system, or swap IRQ's between Sound chipset/card or mouse and
corresponding serial COM port.
==========
We strongly do not recommend to use technological cable connectivity,
as incorrect or non-professional cable use may seriously damage your
phone.
With best regards! Maxim Vyalkov
Oxygen Software technical support department
http://www.oxygensoftware.co.uk
Tel.:+70957139582
Linear Mode
