Colibri to SeeYou

Are you using a USB convertor? What version of windows? Quite often
windows sees the data stream from a serial port as a mouse, your
Colibri has control of your PC! Ah! The joys of 'Plug and Pray'.
The way around this involves dropping into control panel and disabling
the 'phantom' mouse in the device list and differs per versions of
windows.

Ian

I am not using a converter. should I be? I'm running windows xp pro on
a dell 600m

devin

wrote:
I am not using a converter. should I be? I'm running windows xp pro on
a dell 600m

devin


There seems to be a collision between the mouse and the serial port
where seeyou tries to access colibri. Please check IRQ setting for mouse
and for your serial port. Do you hear the beeps from colibri? Do you get
the same result if you use LXe?

/Janos

I'm also running xp from a dell d600, with SeeYou 2.x (last version before
3.0).
On an earlier 2.y version I had the Colibri sometimes connecting flawlessly,
sometimes not at all and SeeYou hanging up.
Now it seems to connect more often than it does not, but it takes a very
long time to do so.

So far, I could retrieve every single flight I wanted to for the last two
years, but I never knew why...

--
Bert Willing

ASW20 "TW"


a écrit dans le message de news:
...
I am not using a converter. should I be? I'm running windows xp pro on
a dell 600m

devin

The colibri only beeps at power up. how do I check the IRQ and serial
port setting? lxe would not download thats why I'm using CU


devin

lxe won't download or won't set up on your computer?

will not set up


devin

Devin,

Post the error statement or send it to me off line. If it is the
autoexec file missing error in the installation program you need to
make a copy of the autoexec.nt file and paste it into a different
folder. I had similar problems with WinXP.

Search for your autoexec.nt file and compare where it is to the error
statement. If it is not in the folder the install program is looking
for, copy it and paste a copy in the correct folder.

Mine installed fine after that.

Tim

When a Colibri is connected to a PC and the PC is communicating with
the flight data transfer of the Colibri ( ie when LXe or CU 'connection
wizard' is running ) the Colibri will beep at about 1Hz. This
'heartbeat' tells the user that the mode is working. This beep becomes
intermittent as data is downloaded from the device. When connected
'normally' ie in transmit only NMEA mode as in the glider, the Colibri
does not make any sounds unless a TP or zone is entered.

If your Colibri is connected to your PC and is not making any noise and
your PC's mouse is 'locked up' or doing wierd things ( like wandering
about of its own will ) then the PC has identified and is using the
data stream from the Colibi as a mouse. Depending on your particular
setup on your PC and what programs you are running or have installed
etc this can either be simple to fix ie: by disabling the 'phantom'
mouse driver, or a right pain in the behind.

The Interrupt request used for this will not help much BTW, I suspect
that tinkering with the Windows registry to make the Device Manager
load the serial port driver before the mouse driver might be the right
way to fix the problem once and for all but this is beyond most average
PC users. I wont discuss it here because playing with the registry can
be *fatal* to your PC.

The best solution would be to get a savy PC bloke to sort out your
driver setups. Personally I run ConnectMe on the cockpit iPaq, download
the flights to the iPaq at the end of the day and then transfer the
data using activesync when I'm at the PC. The Colibri doesn't get
removed from the aircraft.

Ian

wrote:
The colibri only beeps at power up. how do I check the IRQ and serial
port setting? lxe would not download thats why I'm using CU


devin


It means there is no serial communication (heartbeats) between colibri
and you application (now it's seeyou). My roommate is working on the
task declaration from Palm to Colibri so I got headache for the
continuous beep sounds
Here is how I can see IRQ on my W2K (other win versions more or less
similar):

Start - Settings - Control Panel - Mouse - Hardware - Properties -
Resources

or

Start - Settings - Control Panel - System - Hardware - Device
manager - Mice and other... - Properties - Resources

under troubleshooting you can set different IRQ (what could collide
something else

Serial port:

Start - Settings - Control Panel - System - Hardware - Device
manager - Ports - select the port where your logger connected -
Properties - Resources

Good luck!

/jancsika