Kanardia BLU User manual

BLU & Kanja — Manual
© Kanardia d.o.o.
August 2021
Revision 1.5

BLU & Kanja — Manual
Contact Information
Publisher and producer:
Kanardia d.o.o.
Lopata 24a
SI-3000
Slovenia
Tel: [phone]
Email: [e-mail]
A lot of useful and recent information can be also found on the Internet. See
http://www.kanardia.eu for more details.
Copyright
This document is published under the Creative Commons, Attribution-Share-
Alike 3.0 Unported licence. Full license is available on http://creativecommons.
org/licenses/by-sa/3.0/legalcode web page and a bit more human read-
able summary is given on
http://creativecommons.org/licenses/by-sa/3.0/. In short, the license
gives you right to copy, reproduce and modify this document if:
 you cite Kanardia d.o.o. as the author of the original work,
 you distribute the resulting work only under the same or similar license
to this one.
Credits
This document was written using TeX Live (L
A
T
E
X) based document creation
system using Kile running on Linux operating system. Most of the figures were
drawn using Open Office Draw, Inkscape and QCad applications. Photos and
scanned material was processed using Gimp. All document sources are freely
available on request under the licence mentioned above and can be obtained
by email. Please send requests to [e-mail].
Revision History
The following table shows the revision history of this document.
2 © Kanardia 2020

BLU & Kanja — Manual CONTENTS
Rev. Date Description
1.3 February 2020 Revised with LaTeX
1.4 July 2020 Instrument Screen Layout Changes updated
1.5 August 2021 Kanja App updated
Contents
1 Introduction 6
1.1 System Requirements . . . . . . . . . . . . . . . . . . . . . . . 6
1.2 KanjaMeaning........................... 6
2 Software Installation 7
3 Hardware Installation 8
4 Kanja App 8
4.1 AccessGrants............................ 8
4.2 TheStartPage ........................... 9
4.3 Pairing and First Connection . . . . . . . . . . . . . . . . . . . 9
4.4 Connection ............................. 10
4.5 DevicesPage ............................ 11
5 Standard Options 12
5.1 Info ................................. 12
5.2 Update ............................... 13
5.2.1 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . 14
5.3 Console ............................... 14
5.4 ICan................................. 15
5.5 Reset................................. 16
3 © Kanardia 2020

BLU & Kanja — Manual CONTENTS
6 Special Commands 16
6.1 EngineTotalTime ......................... 16
6.2 FlightTotalTime ......................... 17
6.3 FuelLevel.............................. 17
6.4 UpdateData ............................ 17
6.5 UpdateApp............................. 17
6.6 About ................................ 17
7 Daqu Options 18
7.1 Channels .............................. 18
7.1.1 Fuel Pressure Example . . . . . . . . . . . . . . . . . . . 19
7.1.2 Fuel Level Example . . . . . . . . . . . . . . . . . . . . 21
7.2 Offset ................................ 21
7.3 ResetChannels........................... 22
7.4 Tank................................. 23
7.4.1 EditShape ......................... 23
7.4.2 Empty/Full......................... 25
7.4.3 Verification With ICan . . . . . . . . . . . . . . . . . . . 26
7.4.4 Example........................... 26
8 Indu & Digi Options 29
8.1 ScreenCustom ........................... 30
8.2 ScreenOEM ............................ 31
8.3 Logo................................. 31
8.4 Channels .............................. 32
8.4.1 Standalone Indu RPM . . . . . . . . . . . . . . . . . . . 32
8.5 RPMLogger ............................ 33
8.6 Flags................................. 34
8.7 Response .............................. 34
8.8 Offset ................................ 36
8.8.1 Static Pressure . . . . . . . . . . . . . . . . . . . . . . . 36
8.8.2 Dynamic Pressure . . . . . . . . . . . . . . . . . . . . . 36
8.9 Password .............................. 37
4 © Kanardia 2020

BLU & Kanja — Manual CONTENTS
9 Limited Conditions 37
9.1 Warranty .............................. 38
9.2 TSOInformation.......................... 40
5 © Kanardia 2020

BLU & Kanja — Manual 1. Introduction
1 Introduction
First of all we would like to thank you for choosing Kanardia.
Kanardia BLU is a CAN-to-Bluetooth interface device which in combination
with Kanja Android application provides ability to upgrade and configure
most CAN based Kanardia products. It is also well suited for various diag-
nostic.
When your system consist mostly from Indu devices, Horis or similar, it is
essential component for the software update.
This manual covers BLU device in combination with its Kanja Android app.
 BLU is the interface device which plugs into Kanardia CAN bus network.
It listens to the CAN bus traffic and transmits the traffic to the Kanja
app via Bluetooth connection.
 Kanja is an Android app, used to manipulate Kanardia CAN bus de-
vices. Most of this manual is devoted to Kanja.
1.1 System Requirements
To run Kanja application and control Kanardia devices with BLU interface
you will need an Android tablet or telephone with:
 Android version 7 or higher,
 WiFi/3G/4G data connection,
 Bluetooth v2.1 or later.
1.2 Kanja Meaning
In our language (Slovene) Kanja shown in Figure 1 is a name for a predator
bird very common in Europe. See wiki https://en.wikipedia.org/wiki/
Common_buzzard for more details.
6 © Kanardia 2020

BLU & Kanja — Manual 2. Software Installation
Figure 1: Kanja (Common Buzzard) in flight. The photo is credit of Andreas
Trepte, http://avi-fauna.info/.
2 Software Installation
Kanja can be installed from Play Store. Example is shown on Figure 2:
1. Open the Play Store app on your Android device.
2. Enter Kanja Kanardia into the search field.
3. Locate the Kanja app and install it in a standard way.
Figure 2: Installation from Play Store detail.
7 © Kanardia 2020

BLU & Kanja — Manual 3. Hardware Installation
3 Hardware Installation
BLU dongle has to be connected to Kanardia CAN network. Normally the
easiest way to do it is to connect it in a place where RJ45 CAN bus terminator
plug is connected. Shortly after the power is applied to Kanardia devices
(CAN network) the BLU will indicate initialization routine by blinking red
and blue LEDs. Once the initialization is complete the blue LED will blink
in a rate of one blink per second.
Figure 3: Blu inserted into an Indu device into one of the CAN ports.
You have to assure that at least one CAN bus terminator is present on the
CAN bus! If not terminator is present, the CAN bus will not be working
properly.
4 Kanja App
4.1 Access Grants
On the very first run, the system will ask you to allow Kanja some access.
In reality Kanja only needs access to files, where the latest firmware, user
layouts and configurations are stored. However, the system will ask you for
more permissions. Please allow access to them otherwise you will not be able
to pair it with BLU. It is beyond our knowledge why all these permissions are
needed.
8 © Kanardia 2020

BLU & Kanja — Manual 4.2 The Start Page
4.2 The Start Page
When Kanja starts, a page similar to Figure 4 appears. Figure 4 shows
individual elements on the page.
1
O Kanja app version is shown on top and last data download date & time
is shown below.
2
O Opens a new page with a list of all Kanardia devices detected on the
CAN bus. You have to connect Kanja and BLU first.
3
O The connection button. Click it to establish connection between Kanja
and BLU. BLU must be paired first. The hexadecimal number on the
button shows the address of the bluetooth device it will connect to.
4
O A click on the Scan button opens a list of detected Bluetooth devices.
Normaly you have to do this only once – to pair your BLU with Android.
5
O Status bar is briefly shown on the app start. Once the latest data has
been downloaded, Done is displayed and shortly after the line disappears.
6
O Kanja global menu allows access to certain special commands.
7
O Manual BLU address entry. This is seldom used. You may use it in
cases where selection from the Scan process fails.
4.3 Pairing and First Connection
Kanja app and BLU must be paired before first connection to the CAN net-
work. Usually this is done only once. Android will remember the last BLU
address and will try to reuse it in the future.
1. Plug the BLU device into a free CAN slot on Kanardia CAN network.
See section 3.
2. Make sure the Kanardia CAN network is powered on and make sure
that at least one CAN bus terminator is present.
3. Make sure that the BLU initializes properly (blue LED blinking in a
rate of one blink per second).
4. Make sure that the Bluetooth module and its visibility to others is
enabled on the Android device.
9 © Kanardia 2020

BLU & Kanja — Manual 4.4 Connection
1
2
3
4
5
6
7
Figure 4: Typical page shown on Kanja start
5. Start the Kanja app on Android device. The page similar to one shown
on Figure 5a shall appear.
6. Click the Scan button to start scanning for Bluetooth devices and wait
a few seconds.
7. Bluetooth addresses starts appearing on the list, see Figure 5b. You may
see significant number of addresses. Unfortunately, many Androids have
problem in detecting names of the devices, so only their addresses may
be shown. You got you BLU address listed on the Warranty papers. If
Kanardia BLU does not appear on the list, compare the addresses with
the address on the Warranty paper. Select the matching address.
8. Press the Connect button. Confirm Bluetooth pairing request when the
dialog appears, Figure 5c. It will not appear if BLU was already paired
with this Android. Finally, page changes to a list of Kanardia devices
detected on the CAN network.
4.4 Connection
If Kanja and BLU were already paired (see section 4.3), then simply:
10 © Kanardia 2020

BLU & Kanja — Manual 4.5 Devices Page
(a) Before first connection. (b) Bluetooth devices list. (c) Pairing request.
Figure 5: First connection process. Number of detected Bluetooth devices can
be significant. Pairing request number is random.
1. Plug BLU into a free CAN slot and make sure you have at least one
terminator in the network.
2. Make sure the CAN network is on. BLU shall be blinking.
3. Press the Connect button to establish connection between Kanja and
BLU.
You may keep BLU plugged in permanently, if this suits you.
4.5 Devices Page
Once connection is established, Kanja shall switch to the device page. This
page lists all devices found on the CAN bus. Device name, serial number and
hardware number are shown together with their name. Figure 6 shows an
example.
Please note that certain instruments may consists of several devices. Horis,
for example, consist of the Horis core device and an AD-AHRS-GPS module
called Airu.
The following actions are possible:
11 © Kanardia 2020

BLU & Kanja — Manual 5. Standard Options
1
2
3
Figure 6: An example of devices detected on the CAN bus network.
1
O Blue arrow closes this page and switches back to the previous one. Al-
ways use this command to get previous page. Do not use Android back.
2
O Select a device from the list to open more options for this device.
3
O Access to special functions, which are not necessarily device specific.
5 Standard Options
Once a device is selected a list of options appears in a new page. Many of
these options are standard for all devices, Figure 7. They will be covered in
this section.
Figure 7: Standard options for all devices on the CAN network.
5.1 Info
The Info command, opens yet a new page, where some general device infor-
mation is shown. Use blue back button, to switch to previous page. Figure 8
12 © Kanardia 2020

BLU & Kanja — Manual 5.2 Update
illustrates and example.
Figure 8: Device general information page.
Unit shows the device name.
Hardware shows the device hardware version. This shall never change.
Software shows the software version as major.minor release. This changes
with each update.
SVN is special software build number (subversion number), which exactly
identifies software situation at the time software was created. This
number increases in steps with every update.
Serial number of the device.
Date of the device creation.
5.2 Update
This command is used to transfer latest firmware (software) into a CAN de-
vice. Most devices can be updated this way, but not all. Nesis, Aetos and
Emsis are exceptions – they must be updated using USB memory stick or
micro SD card.
On every start, Kanja connects to our server and automatically downloads
the latest firmware along with some other configuration files. The date and
time of the last data is shown on the start page, see Figure 4, mark (1) below.
The downloaded files are then kept on your Android device.
Selecting the Update option starts an update process. A confirmation win-
dow appears to prevent accidental updates. After the decision is confirmed,
firmware programming starts.
13 © Kanardia 2020

BLU & Kanja — Manual 5.3 Console
(a) Confirmation window. (b) Update progress.
Figure 9: Device update process.
Kanja updates only one device – the selected one. If you have several devices,
you have to repeat the process for all of them.
Note that certain device may have a different Unit name, but they share same
firmware. For example all Indu devices and Digi share the same firmware.
Hence, you may see generic firmware name instead the device name during
the programming. In the example from Figure 9, Digi was updated but Indu
text appeared in the progress page.
5.2.1 Troubleshooting
If for any reason the firmware update procedure fails the application will
automatically try to repeat the update.
In case the application could not successfully update the device (device not
working properly) shortly disconnect the power from Kanardia CAN net-
work/device and connect it back. Once you will reconnect Kanja with Kanar-
dia BLU the application will automatically start processing the problematic
unit.
5.3 Console
The Console option may come handy during some troubleshooting and de-
bugging. It shall be seldom used.
This command redirects the system output of the device over the CAN bus
network and allows you to see various text messages that devices sends. In
most cases you will not be able to understand them, but they can be useful to
us and help us to understand certain problems. Figure 10 shows an example.
14 © Kanardia 2020

BLU & Kanja — Manual 5.4 ICan
Figure 10: A console page example. Device specific information and diagnostic
messages appear on the page.
5.4 ICan
The ICan is also a debugging and troubleshooting tool. It opens a new page
which shows all flight and engine messages sent by this device on the CAN
bus. Service messages are not shown. Each message consists of its id and
value. Values are received and shown in real-time, Figure 11a. Furthermore,
when a parameter is selected, a new page with the real time chart is opened,
Figure 11b.
(a) ICan main page. (b) ICan chart page.
Figure 11: An Example of Airu (AD-AHRS-GPS) device messages.
15 © Kanardia 2020

BLU & Kanja — Manual 5.5 Reset
5.5 Reset
The Reset options sends the reset command to the device. Device shall restart
as it was turned off and back on. Not all devices accept this command. This
command shall be seldom used.
6 Special Commands
When a global menu symbol is selected (denoted as 6 O on Figure 4), a page
with special commands appears. Figure 12 shows an example.
Figure 12: A page with special commands.
6.1 Engine Total Time
The Engine Total Time command opens a dialog where the engine time can
be changed. See Figure 13 for instance.
1. Write the desired engine time value (in decimal hours) into the field.
2. Click OK button to update the engine total time.
3. Click on left arrow button to leave special commands page.
When a new time was set, Kanja sends special message over CAN bus to all
connected devices to accept the new time. Most devices ignore this message,
but devices which have logging capability accept it. Please wait about 10
seconds after the command was sent before you turn the CAN bus network
off.
16 © Kanardia 2020

BLU & Kanja — Manual 6.2 Flight Total Time
Figure 13: Setting a new engine total time.
6.2 Flight Total Time
Same principles as for the engine total time (see section 6.1) are also used for
the flight total time.
6.3 Fuel Level
This is very special function limited to Digi. When software based tank
(without fuel level sensors) is used with Digi, there is no way to enter the
initial fuel level value as Digi has no input capability. However, when Blu is
connected, then the fuel level can be adjusted using this feature. The fuel
level is typically set before flight, but it can be set during the flight as well.
It takes about six seconds for the system to remember the change.
6.4 Update Data
This command is obsolete. It can be used to download all firmware and
special data from the server. Note that this is done automatically, when
Kanja is started.
6.5 Update App
This command is obsolete. It opens a window, which tells you to check Play
Store for the latest version.
6.6 About
The command opens a window with some publishing data and credits.
17 © Kanardia 2020

BLU & Kanja — Manual 7. Daqu Options
Figure 14: The about and credits window.
7 Daqu Options
When selecting Daqu from list of connected devices, the extra options are
available as on shown on Figure 15. They are explained in next subsections.
Figure 15: Daqu specific options are marked with a red frame.
7.1 Channels
This option is used to configure Daqu and miniDaqu channels. An engine or
aircraft sensor is connected to one of Daqu channels. Once a sensor is wired
to a Daqu channel the channel must be properly set to support the sensor.
For each sensor/channel pair, we must define the function of the sensor, the
sensor make/type/model and some other information.
A proper channel configuration is a complex topic and it depends on a sensor
type and a sensor function. These details are explained in the Daqu and
miniDaqu manual.
18 © Kanardia 2020

BLU & Kanja — Manual 7.1 Channels
When Channels option is selected, Kanja lists names of all detected channels
together with their current function and sensor name. An example is shown
on Figure 16.
Figure 16: Illustration Daqu channels screen. Some channels are not used and
some channels are not visible.
Details on a channel configuration will be shown on two examples: a fuel
pressure sensor and fuel level sensor.
7.1.1 Fuel Pressure Example
Select a channel to which a fuel pressure sensor is connected. It is usually
connected to channel D02 on Daqu or to channel F01 on miniDaqu. For
this example we assume a Kavlico 15 PSI pressure sensors. This is an active
sensor with 0.5-4.5V signal output range, where 0.5 V represents 0 and 4.5 V
represents sensor range value. The sensor range value is 15 PSI, which equals
to 1.034 bar. Such sensor is typically used on Rotax engines with carburetors.
Note: Pressure in Kanja must be always given in bars.
Please note that your case may be significantly different. You may use a
different channel, sensor may work on a different principle and it may have a
different range.
From the list of channels select channel D02. A new window appears where
channel specific settings are specified.
19 © Kanardia 2020

BLU & Kanja — Manual 7.1 Channels
Figure 17: An example of fuel pressure sensor configuration.
1. The Function lists all possible functions for given channel. For this
example, search for the Fuel pressure and select it.
2. The Sensor lists all possible sensors that can be connected to this chan-
nel. Our fuel pressure sensor has a 0.5 to 4.5 V output range. Thus, we
search for the Active 0.5-4.5 V item.
3. The Filter tells how quickly Daqu responds to a sensor change. A
small filter results in fast respond and a large filter in slower respond.
We do not need a very fast response on fuel pressure change, hence a
2000 ms, which equals to 2 secs is selected. Note that Daqu manual
show recommended filter values in seconds, but Kanja requires them in
milliseconds.
4. The Report tells how frequently Daqu transmits sensor readings on the
CAN bus. A value of 2 Hz seems reasonable. This means that Daqu
will transmit fuel pressure reading two times per second. Daqu manual
specifies this value in seconds. Two times per seconds means every 500
ms or 0.5 sec.
5. Range: Finally, sensor working range must be defined. Here we tell that
sensor at its max value of 4.5V equals to 1.034 bar. Remember, for
pressure sensors, this value must be always given in bars.
Once all data is entered, you shall get something similar to Figure 17.
Once all parameters are entered, press the Back arrow on top left screen corner
to get back to the list of channels. Please note that the new channel settings
were sent to Daqu, but they were not stored permanently yet. If you want
to make this permanent, you have to press Back again to close the Channels
page and go back to Daqu options. Now the change is permanent.
20 © Kanardia 2020