CCilot XA and CCpilot XS
Product revision: 0.12
Software guide
2018-03-19
www.crosscontrol.com
14
4.18.1.
Association and authentication
Unsecured networks (and simple WEP authentication) can be connected simply using
iwconfig
and “one liner” command. But WPA enabled access points require the use of the
wpa_supplicant
-daemon, which uses its own configuration file. A default template of such
configuration file is available at the device as /
etc/wpa_supplicant.tmpl
. In addition to containing
all of the configuration options of the
wpa_supplicant
, the file documents them all in great
detail.
In most cases, the file can be stripped down to as simple as below example, which defines an access
point with name
XA_WPA
, using
WPA/WPA2
encryption and passphrase “
connectme
”.
network={
ssid="XA_WPA"
psk="connectme"
key_mgmt=WPA-PSK
}
Example on how to start
wpa_supplicant
and initiate
dhcp
on it:
# wpa_supplicant –Dwext –B –ieth1 –c /usr/local/etc/name_of_config
# dhclient –pf /var/run/dhclient.eth1.pid eth1
4.19.
Bluetooth
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 powered on to be able to operate. This is done with the CCSettings program or through
the CC AUX API.
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.
Additionally, the device needs to load the Bluetooth drivers for Bluetooth to become operational.
This is done within a script, which also enables the power to the Bluetooth circuit, if the API
method isn’t desired. The script command to use for initializing Bluetooth is:
# /etc/init.d/bluetooth start
Of course, the analogue way for stopping Bluetooth is also usable.
