Price

For example, a common soaring flight system includes a Cambridge 302 and a PDA. The Cambridge 302 sends GPS, wind, airspeed and vario data out at 4800 baud. 4800 baud is fast enough for that data, but not fast enough to for sending all that data, and FLARM data - therefore most FLARM units send data at 19200 baud or higher. The K6 Mux can receive the 302 data at 4800 baud and convert it to 19200 baud, combine it with the FLARM data at 19200 baud, and send it to the PDA at 19200 baud (or a higher baud rate if necessary). Also, the K6 Mux is extremely user-configurable. It supports 3 or more "modes" that are used at different times. A 3-position switch can be used to select between a "flight" mode, and 2 "communication" modes. For example in a system with a PowerFLARM and Cambridge 302, the 3-position switch can be configured to select between "flight" mode, "communication with PowerFLARM" mode and "communication with 302" mode. In "flight" mode the K6 Mux combines the GPS, vario, airspeed and wind data from the 302 with FLARM traffic data from the PowerFLARM and sends it to the PDA. The PDA can also exchange MacCready and other data with the 302 in flight. In "communication with PowerFLARM" mode the PDA can send flight declarations to the PowerFLARM and download flight logs from the PowerFLARM. In "communication with 302" mode the PDA can send flight declarations to the 302 and download flight logs from the 302. The PDA doesn't need to receive GPS data from both the 302 and the PowerFLARM, so the K6 Mux can be setup to filter out the PowerFLARM's GPS data.
 

Baud Rate Conversion
The K6 Mux also handles baud rate conversions with ease.  In the example above, the Cambridge 302 communicates with the K6 Mux at 4800 baud.  The PowerFLARM communicates with the K6 Mux at 19200 baud.  And the K6 Mux communicates with the PDA at 19200 baud.

Data Filter
In some applications it is important to filter the data going through the K6 Mux so that only the required data is sent.  For example, in the example above the GPS data from the 302 will be used, so it is important to filter out the GPS data from the PowerFLARM, while still sending the traffic data from the PowerFLARM.  The K6 Mux makes that easy.

Setup
As you can see from the manual (below) setting up the K6 Mux can be a bit tricky, but it only needs to be done once.  The setup is done by connecting the K6 Mux to a PC and using a terminal program such as HyperTerminal.  A PC/power cable is not included with the K6 Mux. I can configure the K6 Mux for you for $20 (highly recommended) - so it will be ready to use when you receive it.  I have a setup cable that powers the K6 Mux with 12V and connects it to the PC's RS-232 port.  If you want to be able to configure your K6 Mux unit, you can make your own cable, or buy a VLb-PC-Pwr cable and a Pwr-12V-500mA power supply.

Example Setup Data
The PDF file below shows all the settings necessary for the example system described above.

K6-Mux-Example-Setup-FLARM-302-iPAQ.pdf

K6 Mux Setup - FLARM and 302.pdf

Online Configuration Tool
K6 Team has created a nice utility for configuring the K6 Mux.  It can be used to select the devices that will be talking through the K6 Mux as well as the baud rates, and which data will be allowed through, and which data will be suppressed.  However, the utility does not setup data forwarding, or the direct communication settings.  Those must be done after the setup file created by the configuration tool is transferred to the K6 Mux.  Below are examples of the basic setup file for the example system described above, and a procedure for manually setting the other required parameters.
K6 Mux Online Configurator: http://mux.k6team.de/
Configuration File: This file was generated by the K6 Mux Online Configurator.  Transfer it to K6 Mux using HyperTerminal and XModem: K6Mux-ConfigFile-1FLARM-2None-3CAI302.cf
Configuration Changes: Procedure for setting the remaining parameters: K6Mux-ConfigChanges-1FLARM-2None-3CAI302.pdf

Specifications

Power/Data Cables
Cable-K6Mux-302-PDA-0p3 - Cable for connecting a Cambridge 302 to the K6 Mux and to a PDA cradle or cable.  Data is sent from the 302 to the K6 Mux and then on to a DB-9f connector for a PDA cradle or cable.  5V power from the 302 is sent around the K6 Mux - directly to the DB-9f connector for the PDA cable or cradle.
Cable-K6Mux-FLARM-0p3 - Cable for connecting a FLARM or PowerFLARM to the K6 Mux.  This cable passes 12V power from the K6 Mux to the FLARM or PowerFLARM.
Cable-K6Mux-GNAV-0p3, Cable for connecting a Cambridge 302 or GPS-NAV to the K6 Mux.  Power is not passed through this cable, data only.
Cable-K6Mux-PS5a-0p3 - Cable for connecting a Goddard PS-5a to the output port of a K6 Mux.
Cable-K6Mux-Pwr-2, Cable for bringing 12V power into the K6 Mux.  The 12V power is used to power the K6 Mux and the PowerFLARM.  It can be connected to any port on the K6 Mux.
VLb-PC-Pwr, PC cable.  Use with Pwr-12V-500mA power supply.  Plugs into the output port on the K6 Mux.

Note: The power/data cable supplied with the Naviter Oudie connects directly to a FLARM, PowerFLARM or the K6 Mux.  It also provides 12V power for the K6 Mux and the FLARM or PowerFLARM.

Example Systems
Several example systems using the K6 Mux are shown here: K6 Mux Example Systems

Downloads

• K6 Mux Manual

Recent Pocket PCs and other user interface devices do not have RS-232 serial ports - making it difficult to connect them with soaring GPS units.  However, most current PDAs (Pocket PCs and Palm devices) and PNDs (Personal Navigation Devices - such as the HP iPAQ 310) do have a built-in BlueTooth radio.  But no soaring GPS offers BlueTooth capability - which is where the K6 Bt comes in.  The K6 Bt is a BlueTooth transceiver which makes it possible for soaring GPS and flight computer units to talk through the K6 Bt over BlueTooth to the PDA or PND.  It is a 2-way communication so data such as MacCready and water ballast settings can be exchanged between the PDA and soaring flight computer.  The BlueTooth connection is even password protected so that it cannot be intercepted or received by another device.

Example Systems
Click on the images below to view larger versions.

In the example shown above, an LX Colibri or EW microRecorder is connected to a K6 Bt.  The K6 Bt enables 2-way communications between the LX Colibri or EW microRecorder and the PDA (HP iPAQ 210/211/214 shown) or PND (HP iPAQ 310/314 shown).  A Cable-K6Bt-Pwr-2 is used to provide 12V power to the K6 Bt.  A Cable-K6Bt-Colibri-0.3 or Cable-K6Bt-EWmicroRec-0.3 power/data cable is used to connect both 12 V power and 2-way data between K6 Bt and the Colibri or EW microRecorder.  Click on the images to view larger versions.  For a breakdown of all the required parts, please see the links below.
EW microRecorder with K6 Bt and iPAQ 310
LX Navigation Colibri with K6 Bt and iPAQ 310

In the example shown above, a K6 Bt receives both data and 5 V power from a Cambridge 302 or GPS-NAV.  The K6 Bt enables 2-way communications between the 302 and the PDA (HP iPAQ 210/211/214 shown) or PND (HP iPAQ 310/314 shown).  A Cable-K6Bt-302-0.3 power/data cable is used to connect the 302 or GPS-NAV to the K6 Bt. Or, if you want the 302 to also power the PDA, you can use the Cable-K6Bt-302-0.3-miniUSB-1 wiring harness. Note: The 302 does not seem to be able to power both the K6 Bt and an iPAQ 310, but it works fine with an iPAQ 210 or similar.  Click on the images to view larger versions.  For a breakdown of all the required parts, please see the links below.
Cambridge 302 with K6 Bt and iPAQ 310
Cambridge 302A with K6 Bt and iPAQ 310

In the example shown above, a K6 Bt receives both data and 5 V power from an LX7007 Pro IGC.  The K6 Bt enables 2-way communications between the LX7007 and the PDA (HP iPAQ 210/211/214 shown).  A Cable-K6Bt-LX7007-0.3 power/data cable is used to connect the LX7007 to the K6 Bt.  A Nimbus cradle with a RAM mounting arm is also shown.  The Nimbus cradle includes a power cable with a USB "A" connector that is shown plugged into a Socket Mobile Power Pack.

Comm Port Baud Rate Switching
Some soaring GPS, flight recorder and flight computer products automatically switch baud rates when doing jobs such as transferring waypoints, task declarations and flight logs.  The K6 Bt has established a freely available protocol which makes baud rate changes possible, as long as the software on the PDA is setup to support the baud rate switching.

Compatibility - PDA or PND
Most current PDAs (such as the iPAQ 110/111/112, or iPAQ 210/211/214) and PNDs (Personal Navigation Devices - like the HP iPAQ 310 series) have BlueTooth radios built in.  Any device with a built-in BlueTooth radio should work fine.

Compatibility - Soaring GPS or Flight Computer or GPS Flight Recorder
Any soaring instrument with a standard RS-232 serial port (every one I can think of) should work fine - as long as the soaring software on the PDA or PND supports the K6 Bt and the desired soaring instrument.

Great for 2-Seat Gliders!
The K6 Bt makes it much easier to install a PDA in the back seat of a 2-seat glider.  The BlueTooth radio signals can reach easily from the nose of the glider to the PDA in the back seat.  Therefore, there is no need to run PDA power/data cables from the nose of the glider to the back seat.  However, a K6 Bt unit is required for every PDA.  It is not possible for more than 1 PDA to talk to a K6 Bt.  It is possible to connect 2 K6 Bt units to a single soaring GPS unit (such as a Cambridge 302, or LX Colibri, or EW microRecorder, etc.).   Another thing to consider is that the PDA's built-in battery may not last through a long glider flight.  See the note Power for the PDA or PND below for suggestions.

Compatibility - Soaring Software
It appears that special communications protocols are used - especially where baud rate switching is required.  Therefore, the K6 Bt will only work with soaring software that is customized to work with the K6 Bt.  SeeYou Mobile has been tested and works well for sending GPS data to the PDA and exchanging MacCready and other data between the PDA and a Cambridge 302.  However, at this time I have not been able to successfully send a task declaration from SeeYou Mobile to a Cambridge 302 or download a flight log from the 302 using SeeYou ConnectMe.  SeeYou says they are certain those functions will be working soon.  I tested using iPAQ hx4700, iPAQ 210 and iPAQ 310 units and a Cambridge 302.  I was not able to establish a connection between the 302 and the PDA or PND when using Glide Navigator II or the Cambridge 300 Utility.  It may be that I just need to more testing.  It is my understanding that the Cambridge 300 utility doesn't work with the K6 Bt because the baud rate is changed for flight log downloads.  The K6 Bt can handle that, but the Cambridge 300 Utility does not support the K6 Bt.  I would think that Glide Navigator II would work with the K6 Bt since there is no baud rate switching, but so far my tests showed that it did not work.

Power for the PDA or PND
Although there is no data cable connection to the PDA or PND, you will probably want to power the device with 5 V power to ensure that it will have enough power to last through a long soaring flight.  Two good options for providing 5V power would be the Goddard PS-5a or the Socket Mobile Power Pack.  Nimbus cradles can be purchased with a DBCAI connector for connection to the Goddard PS-5a or a USB-A connector for connection to the Socket Mobile Power Pack.

Specifications

Power/Data Cables
Cable-K6Bt-Pwr-2
Cable-K6Bt-302-0.3
Cable-K6Bt-302-0.3-miniUSB-1
Cable-K6Bt-Colibri-0.3
Cable-K6Bt-EWmicroRec-0.3
Cable-K6Bt-FLARM-0.3 (also works with Volksloggers)
Cable-K6Bt-LX7000-0.3
Cable-K6Bt-LX8000-0.3
Cable-USBA-mini-USB-Pwr-1

Links
Video showing the establishment of a data connection between an iPAQ 314 and a FLARM unit - using a K6 Bt BlueTooth connection.

Downloads

• K6 Bt Manual

Paul E. Remde

8661 Connelly Place
Savage, Minnesota 55378
USA

Home | Contact | Customer Service | How to Order | Privacy | Technical Support | View Cart

Phone: 1-952-445-9033
FAX: 1-952-445-8954