Typical Configurations¶

Setting the Wireless Interface¶

The three wireless interface options are

Wi-Fi (TCP)
Bluetooth (SPP)
BLE

Unspecified Behavior

Only one wireless interface may be selected at a time.
All others must be disabled for correct operation.
All interfaces are disabled by default.

Details are explained in this section.

TCP¶

Wi-Fi (TCP) is the only interface that can connect to multiple peers at the same time.
As a result, the configuration for this mode differs from the others.

We firstly show the simple case a CANlink® wireless 4000 connected to another CANlink® wireless 4000 in 'Bridge Mode'.

NAMING

We use the 'Bridge Mode' to describe one CLW4000 connected as a wireless CAN bridge from one CAN bus to another.

This is distinguished from 'MultiPoint Mode' where a device is connected to more than one other wireless peer (so multiple CAN buses are connected together).

But we also use the term 'Gateway Mode' in this document to describe using a CANlink® wireless 4000 as wireless access to the CAN bus from another device (such as PC, or mobile phone).

From the perspective of the device there is no difference between 'Bridge' and 'Gateway' Modes both are a point-to-point single-peer connection

Bridge Mode¶

This is the typical use-case of the device - connecting two CAN buses together wirelessly.

We describe a typical (WPA2 authenticated) configuration of a Server and Client device to connect over Wi-Fi.
More information is available in the .eds file that was distributed with the firmware.

(Change highlighted text to suit)

Step	Wi-Fi Server	Wi-Fi Client
Restore all default parameters	Set `0x1011:0x01` to `0x64616F6`	Set `0x1011:0x01` to `0x64616F6`
WiFi Operating Mode	Set `0x3000:0x01` to `2` Access Point mode	Set `0x3000:0x01` to `1` Infrastructure mode
WiFi SSID	Set `0x3000:0x02` to "CLW4000_Server"	Set `0x3000:0x02` to "CLW4000_Server"
WiFi Authentication (as appropriate)	Set `0x3000:0x04` to `7` WPA/WPA2 Mixed	Set `0x3000:0x04` to `7` WPA/WPA2 Mixed
WiFi Password	Set `0x3000:0x05` to "CLW4000_Pass"	Set `0x3000:0x05` to "CLW4000_Pass"
WiFi DHCP Mode	Set `0x30000x09` to `2` Server (MiniAP only)	Set `0x3000:0x09` to `1` DHCP Client (Infrastructure only)
WiFi Region (as appropriate)	Set `0x30000x25` to `2` EU (Default)	Set `0x30000x25` to `2` EU (Default)
Access Point Channel	Set `0x3000:0x0F` to one of - 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11 (2.4GHz) - 36, 40, 44, 48 (5GHz)	🚫
Enable WiFi 2.4GHz Band	🚫	If Server channel is ≤ 11 - set `0x3000:0x10` to `1` - set `0x3000:0x11` to `0`
Enable WiFi 5GHz Band	🚫	If Server channel is ≥ 36 - set `0x3000:0x10` to `0` - set `0x3000:0x11` to `1`
Bluetooth Enable	Set `0x3008:0x03` to `0` Disable	Set `0x3008:0x03` to `0` Disable
BLE Enable	Set `0x3008:0x09` to `0` Disable	Set `0x3008:0x09` to `0` Disable
WiFi Enable	Set `0x3008:0x02` to `1` Enable	Set `0x3008:0x02` to `1` Enable
Connection Direction	Set `0x3010:0x15` to `2` Server enabled	Set `0x3010:0x15` to `3` Client enabled
Connect Type 1	Set `0x3010:0x16` to `1` TCP Socket	Set `0x3010:0x16` to `1` TCP Socket
WiFi IP Address	Set `0x3000:0x0A` to "192.168.0.34"	🚫
Address of Socket Server	🚫	Set `0x3010:0x17` to content of object `0x30000x0A` in Server device (above)
Node ID CAN 1	Set `0x4050:0x03` to 34	Set `0x4050:0x03` to 44
Node ID CAN 2	Set `0x4050:0x03` to 35	Set `0x4050:0x03` to 45

MultiPoint Mode¶

This is a configuration in which more than two physically separate CAN buses are connected logically together via a Wi-Fi network.
See MultiPoint connections for information.

MultiPoint means that any CAN data:

from the physical CAN bus of the Server is sent to each wirelessly connected peer, and
from the CAN bus of any peer is sent to the Server.

It can be seen that data from the bus of one peer is not shared with other pairs.

No special configuration is required over and above that to establish a Bridge between two devices, as long as that device can connect.
In other words, when another CANlink® wireless 4000 device is added to the network, the Server will automatically send incoming CAN data to all peers. No additional configuration must be done to the Server.

Tip

When we talk about 'CAN bus' in a general sense, we refer to either of the two buses the CANlink® wireless 4000 supports.
Logically, they are treated in the same way, and very little distinction are made between them (apart from Node ID).

Therefore, when we discuss sending CAN data wirelessly, data from both buses will be sent wirelessly, and put onto the correct bus when received by the peer device.

Configuration

To establish more than one Client connection to a Wi-Fi Server, some configuration is required.

Typically, the first Client is connected with the following settings:

Object	Server	1st Client
Access Point Mode `0x3000:0x01 [Operating Mode]`	`0x02 [Mini Access Point]`	`0x01 [Infrastructure]`
WiFi SSID `0x3000:0x02`	as appropriate	as appropriate
Authentication `0x3000:0x04 [Authentication Type]`	`0x07 [WPA/WPA2 Mixed]`	`0x07 [WPA/WPA2 Mixed]`
Password `0x3000:0x05 [WiFi Authentication Key]` (See Password Requirements)	as appropriate	as appropriate
Static IP Address `0x3000:0x0A [WiFi IP Address]`	as appropriate	🚫
DHCP `0x3000:0x09 [DHCP Mode]`	`0x02 [Server]`	`0x01 [DHCP Client (WLAN infrastructure only)]`
RF channel `0x3000:0x0F [WLAN - Access Point Channel]`	as appropriate	🚫
RF band. One of: - `0x3000:0x10 [Enable 2.4GHz WiFi Band / Infrastructure only]` - `0x3000:0x11 [Enable 5GHz WiFi Band / Infrastructure only]`	🚫	as appropriate
IP Address `0x3000:0x0A [IP Address]`	as appropriate	🚫
Disable BT `0x3008:0x03 [Bluetooth Enable]`	`0x00`	`0x00`
Disable BLE `0x3008:0x02 [BLE Enable]`	`0x00`	`0x00`
Enable WiFi `0x3008:0x02 [WiFi Enable]`	`0x01`	`0x01`
Server address `0x3010:0x17 [EEP URL Address/WLAN Client only 1]`	🚫	Value of `0x3000:0x0A [IP Address]` in Server device
Enable WiFi server `0x3010:0x15 [EEP Connection Direction Configuration/Server or Client 1]`	`0x02 [Server enabled]`	`0x03 [Client enabled]`
Connection type `0x3010:0x16 [EEP Connect Type 1]`	`0x01 [TCP Socket]`	`0x01 [TCP Socket]`
Socket Listen Port `0x3010:0x18 [Socket Listen Port/WiFi only 1]`	(`30000` by default)	Value of `0x3010:0x18 [Socket Listen Port/WiFi only 1]` in Server device

There are different objects per Client connection. These have been highlighted in green.
By default each of the seven possible Client connections has a different default port:

Connection	Object	Default Port
Client 1	`0x3010:0x18 [Socket Listen Port/WiFi only 1]`	30 000
Client 2	`0x3011:0x18 [Socket Listen Port/WiFi only 2]`	30 001
Client 3	`0x3012:0x18 [Socket Listen Port/WiFi only 3]`	30 002
Client 4	`0x3013:0x18 [Socket Listen Port/WiFi only 4]`	30 003
Client 5	`0x3014:0x18 [Socket Listen Port/WiFi only 5]`	30 004
Client 6	`0x3015:0x18 [Socket Listen Port/WiFi only 6]`	30 005
Client 7	`0x3016:0x18 [Socket Listen Port/WiFi only 7]`	30 006

As we can see, the first Client connects by default to port 30000, which is the default port that the Server will open and listen on.
All Port numbers can be set to the same value. This is how this tutorial will continue.

The Server device must be configured for each Client connection.
Again, as can be seen, the settings for each Client are in a different object, from 0x3010 for Client one, through 0x3016 for Client seven.

Server Objects (`0x3011` group)	Server Value
Enable WiFi server `0x3011:0x15 [EEP Connection Direction Configuration/Server or Client 2]`	`0x02 [Server enabled]`
Connection type `0x3011:0x16 [EEP Connect Type 2]`	`0x01 [TCP Socket]`
Socket Listen Port `0x3011:0x18 [Socket Listen Port/WiFi only 1]`	`30000`

The second Client connection is configured exactly as in the prior table with the settings for the first Client.
After this Client device has been configured, three CANlink® wireless 4000 would be connected together:

For an additional Client connection, the values in the 0x3012 group. (And so forth):

Server Objects (`0x3012` group)	Value
Enable WiFi server `0x3012:0x15 [EEP Connection Direction Configuration/Server or Client 2]`	`0x02 [Server enabled]`
Connection type `0x3012:0x16 [EEP Connect Type 2]`	`0x01 [TCP Socket]`
Socket Listen Port `0x3012:0x18 [Socket Listen Port/WiFi only 1]`	`30000`

MultiTalk¶

This is a configuration in which more than two separate CAN buses are connected logically together, and all data is shared between all connected nodes. See MultiTalk connections for information.

The difference over MultiPoint is that incoming wireless data is also propagated to all other peers.
Since only one device (the Server) has more than one peer - only this device needs configuration.

When Wi-Fi connections have already been established, only one setting is required to enable MultiPoint.

Step	Wi-Fi Server	Wi-Fi Client(s)
Enable MultiTalk `0x3008:0x04 [MultiTalk Enable]`	Set to `0x01`	🚫 No configuration needed

Bluetooth¶

See the Bluetooth section for details about configuring a Bluetooth Server and Client.

Bluetooth Low Energy (BLE)¶

See BLE for details about configuring a BLE Server and Client.