maximatecc CrossCore XM Quick start guide

CCpilot XM and CrossCore XM - Software guide
Revision: 1.6
Software Guide
Date: Jun 24, 13
Software guide
www.maximatecc.com
CCpilot XM and CrossCore XM

CCpilot XM and CrossCore XM - Software guide
Revision: 1.6
Software Guide
Date: Jun 24, 13
www.maximatecc.com
Contents
Revision history ..................................................................................................................................4
1. Introduction ..................................................................................................................................5
1.1. Conventions and defines......................................................................................................... 5
1.2. Identification .............................................................................................................................. 5
1.3. References.................................................................................................................................. 6
2. Basic operation ............................................................................................................................7
2.1. Login and passwords ................................................................................................................ 7
2.2. Using the touch screen............................................................................................................. 7
2.3. Keyboard .................................................................................................................................... 7
2.4. Calibrating the touch screen.................................................................................................. 8
2.5. Software deployment............................................................................................................... 8
3. Device start-up behaviour ..........................................................................................................9
3.1. BIOS .............................................................................................................................................. 9
3.2. Windows system start-up specifics ......................................................................................... 9
3.3. Linux system start-up specifics................................................................................................. 9
3.4. Status LED indication............................................................................................................... 10
4. Accessing and using the interfaces of XM device ................................................................11
4.1. CF/HDD...................................................................................................................................... 11
4.2. CAN............................................................................................................................................ 11
4.3. Ethernet ..................................................................................................................................... 12
4.4. USB.............................................................................................................................................. 12
4.5. RS232 Serial access ................................................................................................................. 12
4.6. Video in ..................................................................................................................................... 12
4.7. Audio In / Out........................................................................................................................... 12
4.8. Digital Input............................................................................................................................... 13
4.9. Status LED .................................................................................................................................. 13
4.10. Backlight............................................................................................................................ 13
4.11. Ambient light sensor........................................................................................................ 14
4.12. Buzzer ................................................................................................................................. 14
4.13. EEPROM ............................................................................................................................. 14
4.14. Hardware watchdog functionality .............................................................................. 14
4.15. Temperature sensors ....................................................................................................... 14
4.16. GPS ..................................................................................................................................... 14
4.17. GPRS/GSM ........................................................................................................................ 15
4.18. WLAN ................................................................................................................................. 15
4.19. Bluetooth ........................................................................................................................... 15
5. CCsettings...................................................................................................................................16
5.1. Main menu................................................................................................................................ 16
5.2. Version ....................................................................................................................................... 16
5.3. Temperature............................................................................................................................. 16
5.4. Display ....................................................................................................................................... 17
5.5. Power ......................................................................................................................................... 17
5.6. Heater........................................................................................................................................ 17

CCpilot XM and CrossCore XM - Software guide
Revision: 1.6
Software Guide
Date: Jun 24, 13
www.maximatecc.com
5.7. About ......................................................................................................................................... 18
5.8. LED.............................................................................................................................................. 18
5.9. Buzzer ......................................................................................................................................... 18
5.10. CAN.................................................................................................................................... 18
5.11. Digital Input....................................................................................................................... 19
5.12. Touch screen .................................................................................................................... 19
5.13. Light sensor ....................................................................................................................... 20
5.14. On/Off................................................................................................................................ 20
5.15. Advanced......................................................................................................................... 21
5.16. Telematics ......................................................................................................................... 21
6. CCvideo ......................................................................................................................................22
6.1. CCvideo main window .......................................................................................................... 22
6.2. Selection menu ........................................................................................................................ 22
6.3. Input info ................................................................................................................................... 23
6.4. Video cropping........................................................................................................................ 23
7. Software update and recovery ................................................................................................24
7.1. Restore firmware settings ....................................................................................................... 24
7.2. Updating firmware components.......................................................................................... 24
7.3. Updating system components.............................................................................................. 24
7.4. Reinstalling the operating system......................................................................................... 24
8. Linux specifics ............................................................................................................................26
8.1. Linux system content............................................................................................................... 26
8.2. Updating system software ..................................................................................................... 26
8.3. Installing new drivers, applications and system packages ............................................. 27
8.4. IP address configuration ........................................................................................................ 30
8.5. Changing serial port settings................................................................................................. 31
8.6. Remote access ........................................................................................................................ 31
8.7. Serial Number Broadcast configuration ............................................................................. 32
8.8. Splash screen image replacement ..................................................................................... 33
8.9. Desktop background image replacement ....................................................................... 33
8.10. USB memory installer ....................................................................................................... 33
9. Windows system specifics.........................................................................................................34
9.1. Windows system content ....................................................................................................... 34
9.2. File system layout..................................................................................................................... 34
9.3. Installing new drivers, applications and system packages............................................. 34
9.4. Remote access ........................................................................................................................ 34
9.5. Embedded write filter ............................................................................................................. 35
9.6. File based write filter ............................................................................................................... 35
9.7. Hibernate once resume many.............................................................................................. 36
Operating system licensing ...........................................................................................................37
Technical support............................................................................................................................38
Trade Mark, etc. ..............................................................................................................................38

CCpilot XM and CrossCore XM - Software guide
Revision: 1.6
Software Guide
Date: Jun 24, 13
www.maximatecc.com
Revision history
Rev
Date
Comments
P1.0
2011-07-06
-
P1.1
2012-02-17
xx
P1.2
2012-03-30
Update for new windows and Linux system
images.
Licensing and 3rd party SW annotations added.
P1.3
2012-04-04
Small fixes and layout changes
P1.4
2012-11-27
A-I + CrossCore XM
P1.5
2012-12-03
Update after review
P1.6
2013-06-17
Small clarification for WLAN settings in
networking for Linux.
Company name change.

CCpilot XM and CrossCore XM - Software guide
Revision: 1.6
Software Guide
Date: Jun 24, 13
www.maximatecc.com
1. Introduction
This software guide contains information on how to start using the CC Pilot XM and CrossCore XM
products and how to access Service functionality.
XM devices are available with both Windows and Linux operating system. This guide is applicable
for both operating systems. Operating system specific information is pointed out in the text or
addressed in the respective operating system sections. Windows may refer to Windows XP Tablet
PC Edition, Windows Embedded Standard 7 or other versions of Windows. Unless otherwise
stated, the information is applicable to all versions of Windows.
The reader should be familiar with the respective operating system and computer usage to fully
benefit from this material.
1.1. Conventions and defines
CCpilot XM and CrossCore XM are in most cases identical in functionality and usage. The following
definition is used to separate unit specific details. The observe symbol is also used to highlight such
difference.
Defines
Use
CCpilot XM
Information that is specific for CCpilot XM
CrossCore XM
Information that is specific for CrossCore XM
XM device
Information that applies to both CCpilot XM and CrossCore XM
The observe symbol is used to highligt information in this document, such as differences between
product CCpilot and CrossCore product models.
The A symbol is used to highlight information specific for CCpilot XM All-Integrated and CrossCore
XM All-Integrated.
The exclamation symbol is used to highlight important information.
Text formats used in this document.
Format
Use
Italics
Paths, filenames, definitions.
Bold
Command names and important information
1.2.Identification
On the side of the XM device there is a label with version and serial numbers which identify your
unique computer. Take note of them. During service and other contact with the supplier it is
important to be able to provide these numbers.

CCpilot XM and CrossCore XM - Software guide
Revision: 1.6
Software Guide
Date: Jun 24, 13
www.maximatecc.com
1.3. References
For further information on the XM device and the available APIs see the following references.
[1] CCpilot XM and CrossCore XM –Programmers Guide
[2] SocketCAN in Linux kernel,
http://lxr.linux.no/linux+v2.6.31.14/Documentation/networking/can.txt
[3] CCAux API documentation (CC AUX x.x.x.x, available in the CC AUX SDK)
[4] CAN Interface Description (available within the Windows SDK)
[5] CCpilot XM and CrossCore XM –Technical Manual
[6] Embedded Write filer documentation (MSDN), http://msdn.microsoft.com/en-
us/library/bb521449%28v=winembedded.51%29.aspx
[7] File based write filter (FBWF) documentation, (MSDN), http://msdn.microsoft.com/en-
us/library/ee832762.aspx
[8] Hibernate once resume many (HORM) documentation (MSDN),
http://msdn.microsoft.com/en-us/library/bb521614%28v=WinEmbedded.51%29.aspx
[9] CCpilot XM and CrossCore XM –Performing Operating System Recovery
[10]CCpilot XM and CrossCore XM –Performing Firmware Updates

CCpilot XM and CrossCore XM - Software guide
Revision: 1.6
Software Guide
Date: Jun 24, 13
www.maximatecc.com
2. Basic operation
This section provides an overall description on basic usage of XM device.
2.1. Login and passwords
By default auto login is enabled and no passwords are required to start using XM device.
The root/administrators passwords are as follows
Under Linux there is one user per default. The user is ccs and the password is default.
This user has administrator rights by using the sudo approach.
Under Windows there are two users per default. The Windows default administrator user
Administrator with the password CCpilotXM and the user Operator which does not
have any password. The Operator user has administrator rights and automatic login
enabled by default.
Custom users can be added with the tools from respective operating system.
2.1.1. Serial console login (Linux)
By default, the serial port can be used as a login terminal for headless access to the XM device. This
service can however be disabled, if a peripheral connection on serial port is desired. This is
specifically covered in chapter 8.5 Changing serial port settings.
Login service is using the same credentials as mentioned above for serial port terminal access.
2.2. Using the touch screen
Navigate the desktop or any application using the touch screen with a stylus or finger.
Tap the screen to perform the equality of a mouse click.
Double click is performed similar to using an external pointing device. Tap the screen twice
in the same place.
Tap and hold the on the touch screen to perform the equivalent to a right click.
There are two available USB profiles for the touch screen; mouse profile and touch profile.
The profile can be changed in CCsettings or through the CCAux API.
Besides the touch screen, keyboard and mouse connected via USB can also be used.
Touch screen functionality is only available in CCpilot XM product versions.
2.3. Keyboard
There is a virtual keyboard available to input letters and symbols using the touch screen. The
virtual keyboard can be used either via the mouse or the touch screen.
The icon to enable the virtual keyboard looks like this:
in Windows
in Linux

CCpilot XM and CrossCore XM - Software guide
Revision: 1.6
Software Guide
Date: Jun 24, 13
www.maximatecc.com
2.4. Calibrating the touch screen
To calibrate the touch screen, open CCsettings. Select Touch and then Calibrate Now. Then follow
the step by step sequence to calibrate the display.
It is also possible to launch the calibration application explicitly from any custom application by
calling the TouchCalibrator application (naming convention applicable per operating system). This
application also take additional arguments to configure the calibration method, such as number of
calibration points (5, 9 or 13 points) and edge distance settings of the calibration points. The 5
point calibration is the default method. The 13 point calibration can be used if the results of the 5
point calibration are not satisfactory. The available command line options can be seen with the --h
or --help option flags.
Touch screen functionality is only available in CCpilot XM product versions.
2.5. Software deployment
There are several methods to add your own software to the device. The standard methods to
transfer software to XM device are to either copy files using the network connection or to use USB
storage devices. To install the software, follow the instructions for the respective software.
Additionally, software can be deployed with remote access functions, see the operating system
specific parts in this document for more information.

CCpilot XM and CrossCore XM - Software guide
Revision: 1.6
Software Guide
Date: Jun 24, 13
www.maximatecc.com
3. Device start-up behaviour
At power on, the XM device has an internal microcontroller that monitors the power supply and
performs start-up configurations and power settings. It then supplies the main computer board
with power; from there the device execution begins, starting with the BIOS.
3.1. BIOS
The BIOS is XM device specific BIOS, which performs the initial setup of the main processor and its
on-board peripherals. Once finished, the operating system execution takes over.
During BIOS operation different startup options can be accessed, the BIOS can for instance be used
to occasionally boot from USB attached storage media by pressing the key F11. If other non-
standard BIOS settings are desired, access the BIOS Settings menu by pressing the DEL key during
BIOS startup. BIOS settings changes should normally not be needed and can be affecting specific
functions within the system, so any changes must be careful considered before applying.
3.2. Windows system start-up specifics
Once the Windows operating system is started, normal operating system steps are performed. The
Windows operating system is fully available as standard, with installed device drivers for all
hardware peripherals available.
3.3. Linux system start-up specifics
The Linux operating system, an Ubuntu LTS derivate, has two start-up modes, the normal mode
and the recovery mode. In the normal mode the root file system is write protected, meaning that
any run time settings normally done by the user are discarded after a power cycle.
To be able to perform system settings, the Linux system must be restarted into recovery mode. This
is done with the shell command:
# sudo reb oot -resc ue .sh
This recovery mode enables the write back mode of the root file system; in this mode a user can
perform settings that are kept permanent and the system works as the standard Ubuntu system.
The device can also be started into the recovery mode directly, if a keyboard is attached. Keep the
<SHIFT> key pressed while booting the device normally, then choose the recovery system from the
menu that appears.
The recovery system may be more error prone to file system corruption, it is recommended to limit
the use of this mode. Be careful and perform controlled shutdown and restart operations while in
recovery mode, as well as making sure the device has a steady supply power.

CCpilot XM and CrossCore XM - Software guide
Revision: 1.6
Software Guide
Date: Jun 24, 13
www.maximatecc.com
3.4. Status LED indication
This section describes the basic default status LED behavior. The LED is located in different
locations depending on the device type, see Technical Manual for details. Note that the status LED
behavior can be disabled totally and/or overridden by user software through the CCAux API.
3.4.1. Start-up sequence
During startup, the LED indications are as follows:
1. Flashing YELLOW at 1 Hz. Pre-heating is activated and in effect, start-up is delayed while
the device is heated.
2. Flashing YELLOW at 2 Hz. Device start-up phase begins.
3. Operating system is then started, and specific service software begins to execute.
4. Static GREEN. System is operational.
3.4.2. Shutdown sequence
Once shutdown or reboot is initiated:
1. Static YELLOW. Shutting down, rebooting or entering suspended mode.
2. LED OFF. Device is off
3.4.3. Suspend/resume sequence
Once suspend is initiated:
1. Flashing YELLOW at 0.2 Hz. In suspend mode
2. Flashing YELLOW at 2 Hz. Resuming operation
3. Static GREEN. System is operational.
3.4.4. Error indication
There are two different types of error indications available from the status LED:
Flashing RED –An occasional three RED blinks during startup indicates an internal error
that is recoverable, i.e. the system can continue its execution and normal operation. Error
code can be retrieved trough the CCAux API, since the status LED will follow its normal
status indication scheme.
Flashing BLUE –The device becomes non-operational, and seems to be dead, despite
powered on. A number of BLUE LED blinks should be displayed. Record the number of
blinks, as this can be useful in an eventual support contact.
Reason for BLUE LED blinking could be voltage levels out of range, temperature related problems
or internal hardware errors. First steps should be to let device cool off, and verify it has correct
power supply attached, before starting the device again.

CCpilot XM and CrossCore XM - Software guide
Revision: 1.6
Software Guide
Date: Jun 24, 13
www.maximatecc.com
4. Accessing and using the interfaces of XM device
This section covers basic usage and access of the XM device hardware. Most of the hardware is
accessed using the default Windows or Linux interfaces but some XM device specific interfaces,
such as CAN and Digital In, require additional software and/or interfaces to be accessed. See the
CCpilot XM and CrossCore XM –Programmers guide documentation for general information
regarding software development using XM device interfaces.
Depending on product model, all interfaces may not be present on your specific model. There may
also be additional methods to access XM device than the ones described herein, depending on
operating system and additional installed software.
4.1. CF/HDD
XM device uses a compact flash based storage. The storage is identified to the system as an IDE-
device, i.e. a normal hard disk drive.
The Compact Flash module is industrial grade classified and has both static and dynamic wear
levelling to prevent a premature aging and to ensure the longest lifetime, still Compact Flash drives
has a limited number of write cycles. It is recommended that the amounts of writing to storage are
limited within the application. Rather keep information in RAM memory and write larger blocks at
one time instead of frequently writing smaller pieces.
Additional details about CF usage recommendations can be found in CCpilot XM and CrossCore
XM –Programmers guide.
4.1.1. Windows
In the maximatecc Windows images, measures have been taken to reduce the number of write
accesses during normal operation. These measures include disabling of file access timestamps and
disabling of prefetching services. Note that the page file is disabled by default; this is to enhance the
life time of the Compact Flash card and reduce the system reserved storage media space. Further
configuration to reduce flash write cycles can be set up by the customer: See chapter 9 Windows
system specifics, for information about the EWF, FBWF and HORM technologies.
4.1.2. Linux
In Linux, the Compact Flash card is partitioned into one root file system, which is write protected,
and one user file system area, which is write enabled by default. The latter area is the preferred
location for user software installations. See chapter 8.3 Installing new drivers, applications and
system packages.
4.2. CAN
XM device has four CAN interfaces with user configurable baud rate and frame type accessible from
the CCsettings application or from registry and/or standard file system settings.
The CAN interfaces can also be accessed in Windows using the proprietary CAN API, further
described in the CAN Interface Description, or with the Linux operating system standard API
SocketCAN. More information can be found in CCpilot XM and CrossCore XM –Programmers
Guide.

CCpilot XM and CrossCore XM - Software guide
Revision: 1.6
Software Guide
Date: Jun 24, 13
www.maximatecc.com
4.3. Ethernet
Two Ethernet ports are available on XM device, thus enabling simultaneously connection with two
physical network infrastructures. XM device is per default set up to use DHCP for IP address
retrieval. The network connection settings can be changed within the operating system settings.
Be aware that connecting XM device to a network environment can impose a security threat if not
taking the required security measures.
4.4. USB
Via the USB port, a multitude of devices can be connected to XM device. For some devices, drivers
compatible with the operating system must be installed in order for the device to function. Follow
the instruction from the device supplier for the respective operating system.
4.5. RS232 Serial access
Select COM1 in Windows to access the serial port of XM device.
In Linux the serial port is accessed from dev/ttyS0 and when communicating with the targets, the
settings for serial port to use are 115200-8-N-1. By default the serial port is set up as a login
console, but this can be disabled to allow connection of peripheral accessories. This is specifically
covered in chapter 8.5 Changing serial port settings.
The Serial port in XM device follows RS232 signalling levels, but with a limited set of signals. For
more information see the Technical manual.
Note that the serial port should not be used by any software when performing upgrades of internal
microcontroller firmware. The internals of the device needs to have undisturbed access to the serial
port during this operation.
4.6. Video in
The video in signals can be viewed by the CCvideo application, further described in chapter 6
CCvideo. The video in signals can also be accessed and controlled using the CCAux API.
4.7. Audio In / Out
Audio in and audio out is controlled using the normal operating system functionality. The audio
device is identified as Cirrus Logic HD Audio. Note that the audio input is muted per default.
4.7.1. Linux audio settings
Audio input and output settings can be found from menu System › Preferences › Sound.
For any changes to be persistent they need to be made while the system is in rescue mode.
4.7.2. Windows audio settings
The sound settings can be managed using normal operating system procedures accessible via the
control panel.
In Windows XP the Cirrus Logic audio driver supports the below listed combinations of
frequency/resolutions for playback and recording. If other settings are used, the audio may be
distorted or not audible.

CCpilot XM and CrossCore XM - Software guide
Revision: 1.6
Software Guide
Date: Jun 24, 13
www.maximatecc.com
Frequency
Resolution
8Khz
8bit mono
8bit stereo
16bit stereo
12KHz
8bit mono
8bit stereo
16bit mono
16bit stereo
16KHz
8bit mono
8bit stereo
16bit stereo
32KHz
8bit mono
8bit stereo
16bit stereo
44.1KHz
44.1KHz 8bit mono
44.1KHz 8bit stereo
44.1KHz 16bit stereo
48 KHz
48KHz 8bit mono
48KHz 8bit stereo
48KHz 16bit stereo
4.8. Digital Input
The digital input signals are available for software developers using the CCAux API. The digital
input status can be viewed within CCsettings for test purposes.
4.9. Status LED
The status LED in the XM device is used by the computer itself and by the operating system to
indicate different states or to present warnings, as described in 3.4 Status LED indication. The
status LED can also be controlled by the applications running on XM device using the CCAux API.
The blinking frequency and colour of the LED can be controlled. The latest status LED instruction
is always used. The status LED can also be disabled which means that only hardware error codes
and user application behaviour is enabled. Yellow blinking at start-up and static green in
operational mode are turned off.
4.10. Backlight
The XM device has an adjustable backlight intensity level. In addition to the backlight control
buttons on the CCpilot XM front, the backlight functionality can also be controlled from CCsettings
and via software using the CCAux API. The most recent setting is always used. The backlight
buttons are dedicated for backlight adjustment only.
Together with the ambient light sensor it is possible to make a custom, fully automatic, backlight
control. Such an automatic backlight control function is included in CCpilot XM, but it is not
enabled by default. It can be set up in CCsettings or through the CCAux API.
For CrossCore XM, the backlight and ambient light sensor is not available.

CCpilot XM and CrossCore XM - Software guide
Revision: 1.6
Software Guide
Date: Jun 24, 13
www.maximatecc.com
4.11. Ambient light sensor
The ambient light sensor measures light levels in front of CCpilot XM; for example it’s used for
automatic backlight control. The ambient light sensor is accessed through the CCAux API. It can
also be accessed for diagnostic through CCsettings.
4.12. Buzzer
In addition to the audio In/Out signals, CCpilot XM is also equipped with a buzzer that can play
tones in various frequency and intensity levels. The buzzer is accessed through the CCAux API. It
can also be accessed for diagnostic through CCsettings.
For CrossCore XM, the buzzer is not available.
4.13. EEPROM
A user accessible EEPROM is available in the device, if such storage is required. It’s not normally
needed since a device of this type can store persistent settings in ordinary files in the file system
instead. The EEPROM is accessed via the JIDA interface.
4.14. Hardware watchdog functionality
There is a watchdog available making it possible for the hardware to monitor an application so it
does not stall the system. The exact behaviour is up to the application software to handle and
configure. This functionality is available using the JIDA interface.
4.15. Temperature sensors
There are several temperature sensors placed internally in the device. Thus it is possible for an
application to retrieve temperature information from the temperatures sensors through the CCAux
API or the JIDA interface, depending on temperature sensor placement.
4.16. GPS
The internal GPS receiver in XM device All-Integrated follows NMEA-0183 standards. To access
the GPS receiver data, you should open up a serial connection to /dev/ttyUSB1 (Linux) or COM4
(Windows), with 8-N-1-9600 settings. Note that the GPS receiver needs to be power on to be able
to operate. This is done with the CCSettings program or through the CC AUX API.
On Linux, the output of the GPS device can be verified with the following command:
# stty -F /dev /ttyUSB1 ispe ed 9 600 & & ca t </dev/ ttyUSB1
For Windows, similar serial terminal programs can be used for verification.
Once initiated with an initial read operation, the GPS receiver will start to output NMEA-0183
formatted messages on the serial connection, containing GPS information. It is possible to add
extra GPS software that can format this data and provide a more user-friendly approach to it. The
functionality of the GPS receiver together with the open-source implementation GPSD has been
verified. For more information, see http://gpsd.berlios.de/
NMEA also allows the GPS device to be configured, for more details; locate Fastrax iSuite™ NMEA
manual. It is also possible to use CCSettings for initial verification of GPS receiver functionality, see
more in section 5.16.

CCpilot XM and CrossCore XM - Software guide
Revision: 1.6
Software Guide
Date: Jun 24, 13
www.maximatecc.com
4.17. GPRS/GSM
XM device All-Integrated has a GPRS modem for data connections. To access the GPRS/GSM
modem, you should open up a serial connection to /dev/ttyUSB0 (Linux) or COM3 (Windows),
with 8-N-1-57600 settings. Note that the GPRS/GSM modem needs to be power on to be able to
operate. This is done with the CCSettings program or through the CC AUX API.
The GPRS modem supports the standard set of AT commands, so any software that supports the
standard AT command specification using serial communication can be used. For instance, the
current power status is available via the AT command (on Linux):
# chat TIMEO UT 2 '' A T | mi crocom -t 5000 /dev/t tyUSB0
For Windows, similar serial terminal programs can be used for the same type of simple verification.
It is also possible to use CCSettings for initial verification of modem functionality, see more in
section 5.16.
4.18. WLAN
XM device All-Integrated supports WLAN, interoperable with the standard 802.11 b/g networks.
Note that the WLAN module needs to be power on to be able to operate. This is done with the
CCSettings program or through the CC AUX API.
In Linux, the wireless tools that are installed on the device can be used for setting up the actual
network. Such tools include the iwconfig, iwlist, iwspy, iwpriv, wpa_supplicant and
wpa_cli commands. Additionally, the network interfaces file can be used for configuring WLAN
settings.
In Windows, the standard operating system network connections can be used for setting up a
wireless connection using the WLAN module.
4.19. Bluetooth
XM devices with All-Integrated options have HCI Bluetooth support. HCI stands for Host
Controller Interface and provides a uniform interface method for accessing Bluetooth hardware
capabilities. The Bluetooth module complies with the Bluetooth 2.1 standard. Note that the
Bluetooth module needs to be power on to be able to operate. This is done with the CCSettings
program or through the CC AUX API.
In Windows, the Microsoft Bluetooth stack is used for communication with Bluetooth devices. In
Windows 7, Bluetooth device settings have been moved to Devices and Printers from the Control
Panel applet. Please see the Microsoft documentation for specific Bluetooth usage.
In Linux, the official Linux Bluetooth protocol stack Bluez is supported, and can be used for
communication with Bluetooth devices. Please see the Bluez documentation for more specific
Bluetooth usage.

CCpilot XM and CrossCore XM - Software guide
Revision: 1.6
Software Guide
Date: Jun 24, 13
www.maximatecc.com
5. CCsettings
CCsettings is used for viewing and adjusting XM device specific features and information. Through
the CCsettings main window, the different settings pages are reached, each containing different
areas of settings and information.
All functionality and settings accessed using CCsettings is also available through the CCAux API to
enable integration of settings and functionality within any additional user application, or from the
command line with the tool ccsettingsconsole. For details about this, please see the API
documentation or ccsettingsconsole --help.
Start CCsettings from its menu item or optional desktop shortcut. In Windows, CCsettings can also
be started from the Control Panel.
5.1. Main menu
The main screen of CCsettings show the available
settings pages.
Click on the respective icons to enter its settings page.
It is always possible to revert to the main menu by
pressing the Menu button. If a keyboard is in use, the
Escape key can also be used to revert to the main menu.
5.2. Version
The version page displays the XM device internal
software versions, as well as application interface version
and the version of CCsettings itself.
5.3. Temperature
XM device’s internal temperature sensors can be viewed
from the temperature page.

CCpilot XM and CrossCore XM - Software guide
Revision: 1.6
Software Guide
Date: Jun 24, 13
www.maximatecc.com
5.4. Display
Use the display page to alter the XM device backlight
functionality.
Adjust the backlight of the display by dragging the
Backlight level slider.
Enable automatic backlight using the Enable checkbox.
The display brightness is then adjusted using CCpilot
XM’s light sensor. Soft transitions enable smoother
adjustment of the backlight.
The Sensitivity slider adjusts the level and phase of
backlight adjustment depending on the surrounding light.
The Status LED can be automatically dimmed according to the backlight setting if LED dimming is
enabled. Note that this may not work if a custom color is used or if a blink sequence is set up by
user applications.
For CrossCore XM, the Display option is not available in CCSettings.
5.5. Power
The power page is used to enable or disable the built in
power controls in XM device.
Enable power by checking the respective check box.
Using the Power status drop down box it is possible to
adjust the current setup or the default setup during
system start-up.
5.6. Heater
The heater page is used to adjust the starting
temperature of the internal heater.
Adjust the temperature and activate the setting by
pressing the Apply button

CCpilot XM and CrossCore XM - Software guide
Revision: 1.6
Software Guide
Date: Jun 24, 13
www.maximatecc.com
5.7. About
The about page displays device specific information and
status information. Select what type of information to
display using the Selection drop down box.
Select System report drop down to generate a full device
information report, which can be saved to file. This
report can be very useful for service and support
questions.
5.8. LED
The LED page is used to view the possible LED
indication types and to adjust the LED behavior during
startup.
Enable or disable the status LED indication during
startup of XM device using the Enable checkbox.
5.9. Buzzer
The Buzzer page is used to analyze the possible audio
output from the Buzzer.
Adjust the frequency and volume of the built in buzzer
using the sliders.
Test the buzzer sound by pressing the On button. Press
it again to turn off the buzzer.
For CrossCore XM, the Buzzer is not available in
CCSettings.
5.10. CAN
CAN is normally used and configured directly from the
controlling software. But from CCsettings it is possible
to adjust the default Baud rate and CAN Frame type.
The Device drop down box is used to select the CAN
device to adjust.

CCpilot XM and CrossCore XM - Software guide
Revision: 1.6
Software Guide
Date: Jun 24, 13
www.maximatecc.com
5.11. Digital Input
The digital input page displays the status of the digital
input ports on XM device.
5.12. Touch screen
The touch screen page is used to select whether the
touch display shall be identified to the operating system
as a touch screen or as a mouse.
Select Use touch profile to identify the touch screen as a
touch screen, this is the default and preferred setting.
Select Use mouse profile to identify the touch screen as a
mouse, this setting is required for Windows XP-based
installations without the tablet PC component.
If the touch screen if the pointing precision seems low it
is possible to make a calibration. Start the calibration
sequence by selecting Calibrate Now and follow the step
by step sequence. Different calibration methods can be
chosen to perform more precise calibration.
In the Advanced tab, additional touch and calibration
settings can be made. For instance, by entering a time at
Right click time and pressing Apply it is possible to
adjust the time needed until pressing on the touch screen
will result in a right click action. See the CCAux API
documentation for further information on the advanced
settings.
For CrossCore XM, the Touch Screen option is not available in CCSettings.

CCpilot XM and CrossCore XM - Software guide
Revision: 1.6
Software Guide
Date: Jun 24, 13
www.maximatecc.com
5.13. Light sensor
The light sensor page is used for Light sensor evaluation.
This access is for evaluation, no settings are stored when
leaving the light sensor page.
For CrossCore XM, the Light Sensor option is not
available in CCSettings.
5.14. On/Off
The On/Off page is used to adjust the startup and shut
down settings of XM device.
Any altered setting must be activated using the Apply
button.
Short press - ON/OFF button - adjust the unit behavior
when making a quick press and release of the on/off
button.
Long press - ON/OFF button - adjust the unit behavior
when pressing and holding the On/Off button.
ON/OFF signal - adjust the behavior of the On/off signal through the power connector. The time
settings adjust how long the signal must stay low before XM device reacts to the signal.
Unit start-up makes it possible to select if the unit shall respond to start-up from both the on/off
button and/or the on/off signal in the power connector, or if it shall be configured to start up
directly when supply voltage is applied.
Suspend mode is used for activating automatic transition from suspend mode to shut down of the
computer. The time defines the amount of minutes XM device shall remain in suspend mode before
shutting down. Setting the time value to 0disables the shut-down feature; XM device will stay in
suspended mode indefinitely, until started or until power is removed.