Cassia User Manual: Release Date: Nov 19, 2021
Cassia User Manual: Release Date: Nov 19, 2021
Contents
1. What is a Cassia Gateway? .............................................................................................. 3
1.1. Cassia X2000 ........................................................................................................................ 3
1.2. Cassia X1000 ........................................................................................................................ 5
1.3. Cassia E1000 ........................................................................................................................ 6
1.4. Cassia S2000 ........................................................................................................................ 7
1.5. Certified Country List............................................................................................................. 8
2. Installation ...................................................................................................................... 10
2.1. X2000 .................................................................................................................................. 10
2.2. X1000 .................................................................................................................................. 15
2.3. E1000 .................................................................................................................................. 17
2.4. S2000 .................................................................................................................................. 19
3. Deployment .................................................................................................................... 22
3.1. X1000 and X2000 ............................................................................................................... 22
3.2. E1000 and S2000 ............................................................................................................... 23
4. Getting Started ............................................................................................................... 25
4.1. Understanding the Cassia Access Controller ....................................................................... 25
4.2. Apply Licenses Key and Developer Key/Secret ................................................................. 26
4.3. Network Requirement ......................................................................................................... 27
4.4. CAPWAP and MQTT Setting .............................................................................................. 28
4.5. Connecting the Gateway to AC........................................................................................... 29
5. Cassia Bluetooth Gateway Configurations .................................................................. 32
5.1. Status Tab ........................................................................................................................... 32
5.2. Basic Tab ............................................................................................................................ 33
5.2.1. Wired Settings ..................................................................................................................... 36
5.2.2. Wi-Fi Settings ...................................................................................................................... 36
5.2.3. USB Cellular Modem........................................................................................................... 39
5.3. Container Tab...................................................................................................................... 42
5.4. Events Tab .......................................................................................................................... 50
5.5. Other Tab ............................................................................................................................ 50
5.6. Service Tab ......................................................................................................................... 60
6. More information on Access Controller ....................................................................... 64
6.1. Deployment Options............................................................................................................ 64
6.2. AC License .......................................................................................................................... 65
6.3. AC Statistics ........................................................................................................................ 65
6.4. Interface & Protocol............................................................................................................. 66
6.5. Bluetooth Roaming .............................................................................................................. 67
6.6. Gateways Auto Configuration ............................................................................................. 68
1 Copyright 2021 Cassia Networks, Inc.
6.7. Gateway Batch Configuration ............................................................................................. 70
6.8. Bluetooth Debug Tool .......................................................................................................... 75
6.9. Enhanced Locationing......................................................................................................... 76
6.10. Email Alert ........................................................................................................................... 77
6.11. Multiple AC Viewer .............................................................................................................. 78
6.12. Backup AC Configuration .................................................................................................... 79
7. Cassia RESTful APIs...................................................................................................... 80
Appendix A: Cassia’s TI Sensor Tag Demo......................................................................... 82
Appendix B: Supported USB Cellular Modems ................................................................... 87
Appendix C: WPA2 Enterprise Security............................................................................... 89
Appendix D: EU WEEE Directive .......................................................................................... 95
Appendix E: Configurable MQTT TLS Certificates for Gateway-AC Communication....... 96
Appendix F: Cassia Gateway LED Indicators.................................................................... 102
Appendix G: China RoHS ................................................................................................... 104
Appendix H: Antenna Radiation Graphs............................................................................ 105
The Cassia Bluetooth Gateway is a long-range enterprise Bluetooth gateway that can be
used for indoor and outdoor environments. It extends the range of Bluetooth connectivity
up to 1 kilometer and enables remote control of up to 40 Bluetooth low energy devices
without requiring any changes to Bluetooth end devices.
The Cassia Bluetooth gateway acts as a protocol gateway, which translates between the
Bluetooth protocol and the Internet Protocol (IP) protocol. This enables your Bluetooth low
energy devices to be remotely accessible and controllable via an Internet application.
From firmware 1.3 onwards, Cassia provides container support for the Cassia Bluetooth
Gateway E1000, X1000, and X2000 where users can run custom applications.
Cassia launched the new X2000 Bluetooth gateway to deliver secure, long-range, multiple
device connectivity for enterprise-grade IoT applications. It is designed to further improve
the performance and reduce the complexity and cost of large-scale Industrial IoT
deployments. The X2000 features Bluetooth Low Energy (BLE) 5.0 support, a ruggedized
IP66 enclosure, integrated TPM chip, more power/Wi-Fi/antenna options, larger memory,
and various enhancements.
The X2000 extends Bluetooth connectivity up to 400 meters for Bluetooth 4.x and 1
kilometer for Bluetooth 5.0 in open space using a patented filtering and smart antenna
array. Furthermore, the range extension does not require replacing existing Bluetooth low
power end devices, nor is it dependent on Bluetooth Mesh. In bi-directional mode, the
X2000 can pair and connect up to 40 end devices. In broadcast/advertising mode, it can
listen to hundreds of end devices.
The X2000 supports the full functionality of Bluetooth Low Energy 5.0, including higher data
rates (2M PHY), advertising extensions, and long range. X2000 also offers flexible Bluetooth
3 Copyright 2021 Cassia Networks, Inc.
configuration and two state-of-the-art Bluetooth modes: pure scan and high speed multiple
connection modes. Pure scan offers the best scan performance in high noise floor and
situations with a large number of Bluetooth devices. High speed multiple connection mode
optimizes the connection performance when receiving data from multiple Bluetooth
devices simultaneously.
The X2000 supports edge computing, which can improve response time, reduce the cost of
data transmission & cloud service, improve reliability, security, and scalability. The X2000
can run large custom applications in its Ubuntu container. The container and APP can use
up to 700 MB memory in the X2000, which is much larger than X1000 & E1000 (128 MB).
The X2000 has a TPM (Trusted Platform Module) chip embedded. It can support secure
boot, trusted boot, secure storage, and other crypto-chip-based security functions. The
TPM can further enhance X2000’s security level.
Cassia’s X2000 can be used as a protocol gateway, which translates between Bluetooth
protocol and IP protocol. The X2000 Internet Protocol (IP) backhaul options include
Ethernet, 2.4GHz/5GHz Wi-Fi, and USB cellular modem. As a result, Bluetooth end devices
are remotely accessible and controllable via an Internet application.
The X2000 has eight LEDs, including BLE, AC, 4G, Wi-Fi, Ethernet, system, and power. They
are very useful during gateway installation and troubleshooting. Please check Appendix F
for more information.
The X2000 supports Power over Ethernet (PoE) and a 12V DC power source. It can easily
attach to a pole or wall with an included mounting kit or can be placed on a flat space with
an optional desktop stand kit.
The X2000 has passed the below environmental tests. It can be used both indoor and
outdoor environments.
For full features and specifications, please see the X2000 datasheet here:
https://www.cassianetworks.com/resources/x2000-bluetooth-edge-gateway/
The Cassia X1000 enterprise Bluetooth gateway has an IP65-rated enclosure and may be
deployed in indoor and outdoor environments. The X1000 can be attached to a pole or wall
(a mounting kit is included) or placed on a surface like a desk or counter space. It receives
power from Power-over-Ethernet (PoE) via the uplink Ethernet port.
The X1000 has a built-in smart antenna array designed specifically for Bluetooth. It also
The X1000 increases the number of devices that can be simultaneously paired and
connected to 22 Bluetooth low energy devices. It can also listen to potentially hundreds of
devices at the same time when operating in broadcast mode.
For full features and specifications, please see the X1000 datasheet here:
https://www.cassianetworks.com/resources/x1000-enterprise-bluetooth-router-en/
The Cassia E1000 is an enterprise Bluetooth gateway with edge computing capabilities
specifically designed for deployments in industrial, hospitals, senior centers, schools, gyms,
and other indoor locations. The Cassia E1000 can be attached to the ceiling or wall (a
mounting kit is included) or may be placed on a desktop or counter space. The E1000 is
powered via a Micro-USB adapter or from a switch using Power over Ethernet via the uplink
Ethernet port.
The E1000 increases the number of devices that can be paired and controlled for up to 40
Bluetooth low energy devices. In broadcast mode, the E1000 can listen to several hundred
Bluetooth low energy end devices. Its patented smart antenna is optimized for horizontal
use. The E1000 supports Ethernet, 2.4Ghz, and 5Ghz Wi-Fi, or USB cellular modem as an IP
uplink. This enables your Bluetooth low energy devices to be remotely accessible and
controllable remotely via an Internet application.
For full features and specifications, please see the E1000 datasheet here:
https://www.cassianetworks.com/resources/e1000-bluetooth-edge-router/
The Cassia S2000 enterprise Bluetooth gateway is designed for deployments in industrial
automation, health monitoring, senior safety, and other enterprise IoT applications. The
Cassia S2000 can be attached to a ceiling or wall with the included mounting kit, or it can be
placed on a desktop or counter space. The S2000 receives power from either a Micro-USB
adapter or a switch using PoE via the uplink Ethernet port.
The S2000 extends Bluetooth’s range up to 1000 feet and expands the number of Bluetooth
low energy devices that can be paired and controlled up to 20 devices. In broadcast mode,
the S2000 can listen to several hundred Bluetooth low energy end devices. The patented
smart antenna of the S2000 is optimized for horizontal use.
The S2000 is used as a protocol gateway, translating between the Bluetooth protocol and
the IP protocol. It supports Ethernet, 2.4Ghz Wi-Fi, and USB cellular modem for IP uplink.
You can easily access and control your Bluetooth low energy devices remotely via an
Internet application or a mobile app.
NOTE: For S2000, if the received advertising packets are more than 200 per second, it is
recommended to use scan filters to reduce S2000’s CPU load.
For full features and specifications, please see the S2000 datasheet here:
https://www.cassianetworks.com/resources/s2000-enterprise-bluetooth-router/
X2000’s Mexico (IFT & NYCE) and Taiwan (NCC & BSMI) certifications will be available in
2021 Q4.
2.1. X2000
Hardware
• Cassia X2000 Gateway
• Power-over-Ethernet (POE) 802.3af/at compliant source, or PoE injector if PoE network
is not available
• CAT5 Ethernet cable with standard RJ45 connector (Patch cord): 1 unit if PoE available,
or 2 units if used with PoE injector
NOTE: Only the Ethernet connector without the outer PVC jacket can fit X2000’s cable
glands.
• 12V DC power source or AC/DC power adapter (if not using PoE). The DC connector
type should be interior diameter 2.5 mm, outside diameter 5.5 mm, center +v, and
outer –v. The output voltage should be 12V. The output power should be equal to or
larger than 12 W.
NOTE: Please don't use PoE and 12V DC at the same time
The screws in the X2000 package are ST4.2×25. The user can use longer ST4.2 screws or
ST5 screws too. If the user uses bigger screws, e.g., ST6, it will be difficult to install
X2000’s mounting bracket.
6. Connect 12V DC power cable and cable gland to X2000 in the same way as step 5
7. For outdoor X2000 installations, please connect the ground cable to ensure X2000’s
safety
Included in Package
3. Install silicon plugs (please skip this step if the ground cable is installed);
2.3. E1000
Hardware
• Cassia E1000 Gateway
• Power-over-Ethernet (PoE) 802.3af/at compliant source, or PoE injector if PoE network
is not available
• CAT5 Ethernet cable with standard RJ45 connector (Patch cord): 1 unit if PoE available,
or 2 units if used with PoE injector
• Micro USB power cable and universal plugs (if not using PoE)
• Computer System (Desktop/Laptop/Smart Phone/Tablet) with Wi-Fi connectivity
• USB cellular modem: required only if set up over a SIM-based Internet connection is
required
Mounting
1. Place the E1000 on a flat, unobstructed surface or mount it using the supplied
mounting kit in a vertical or horizontal orientation;
2. If mounting, first screw the mounting plate onto wall or ceiling;
3. Connect the E1000 to power with the supplied Micro USB cable and power adapter
and to a Wi-Fi Access Point via Ethernet or Wi-Fi (2.4GHz or 5GHz);
2.4. S2000
Hardware
• Cassia S2000 Gateway
• Power-over-Ethernet (PoE) 802.3af/at compliant source, or PoE injector if PoE network
is not available
• CAT5 Ethernet cable with standard RJ45 connector (Patch cord): 1 unit if PoE available,
or 2 units if used with PoE injector
• Micro USB power cable and universal plugs (if not using PoE)
• Computer System (Desktop/Laptop/Smart Phone/Tablet) with Wi-Fi connectivity
• USB cellular modem. This is only required if set up is over a SIM-based Internet
connection
Mounting
1. Place the S2000 on a flat, unobstructed surface or mount it using the supplied
mounting kit in a vertical or horizontal orientation.
2. If mounting, first screw mounting plate into wall or ceiling.
3. Connect the S2000 to power with the supplied Micro USB cable and power adapter
and to a Wi-Fi Access Point via Ethernet or Wi-Fi (2.4GHz only).
NOTE: For your network setting information, please contact your IT administrator.
According to the above formula, the following tilt angles are highly recommended:
• At a height of 10-30 feet (3-10 meters), no tilting is needed
• At a height of 30-60 feet (10-20 meters), 5°-10° tilt is required
• At a height of more than 60 feet (20 meters), please calculate the inclination angle
according to the formula provided above
The optimal placement for the Cassia E1000 and S2000 should be located above ground
at a height of 10 to 15 feet (3-5 meters), in direct line of sight of the BLE device, and
within 180 to 1000 feet (60-300 meters) range of the BLE device. Ceiling installations
should be 6 feet (2 meters) away from nearby walls or columns. Obstacles, like walls, as
well as Wi-Fi interference, will reduce the range of Cassia’s Bluetooth gateways.
• Keep at least 3 feet (1 meter) away from cellular antennas and Wi-Fi access points.
• Installation should be far from microwaves, wireless keyboard/mouse, and other
devices that also use the 2.4 GHz band.
• Avoid installations near air conditioners, heating pipes, water supply pipes,
transformer boxes, an elevator operation room, etc.
The Cassia IoT Access Controller (AC) is a powerful IoT network management solution.
Using the Cassia AC, organizations have access, control, and monitor over IoT
environments. The Cassia AC solution enables the deployment and management of
hundreds of Bluetooth gateways, as well as the monitoring of thousands of
detected/connected devices in an enterprise environment from one centralized interface.
For more details, please see the Cassia IoT Access Controller Server Data Sheets here:
https://www.cassianetworks.com/resources/cassia-iot-access-controller/
The user may use a Cassia-hosted AC or install their own AC server. It is strongly
recommended that new users use a Cassia-hosted AC to expedite the evaluation process.
The evaluation process of a Cassia Bluetooth Gateway with a Cassia-hosted AC is available
for purchase with Cassia Starter Kits. Please contact the Cassia sales team for more
information.
If you want to manage more than three gateways, please apply the License Key which
governs the number of managed gateways. Before using Cassia’s RESTful API through the
AC, you will need a Developer Key and Developer Secret.
Please send the required information below to [email protected] to apply the
License Key, Developer Key, and Developer Secret.
• Customer name
• Number of managed gateways (4 to 9999 gateways)
• Length of subscription (in months)
• Device ID (copy from AC setting page)
Please see the screenshot below for inputting the Developer Key, Developer Secret, and a
server license key via the AC.
Input your developer key, developer secret, and license key via the AC
From v2.1.1, for the gateways that uses MQTT to communicate with AC (default setting),
the following ports are used and required for firewall configuration. TCP ports 80, 443 and
9999 are not required anymore.
Please make sure the following ports are opened outbound on the gateway side firewall.
For the gateways that use CAPWAP to communicate with AC or the gateways using
firmware below v2.1.1, the following ports may be used and required for firewall
configuration.
Please make sure the following ports are opened outbound on the gateway side firewall.
The user can check if a TCP port is opened by using Netcat in chapter 5.5.
Before firmware 2.0.2, Cassia Bluetooth gateway communicates with AC using CAPWAP
protocol. CAPWAP is based on UDP port 5246 and 5247 and always uses DTLS 1.2 to
ensure security (no unsecured CAPWAP).
From firmware 2.0.2, Cassia gateway can also use MQTT to communicate with AC. MQTT
uses TCP port 8883 and always uses TLS 1.2 (no unsecured MQTT). MQTT improves the
robustness of gateway and AC communication. It brings a higher upgrade success rate and
less BLE data drop rate. What is more, sometimes the user’s firewall doesn’t allow UDP
packets to pass. In this case, MQTT will help the packets between the gateway and AC to
pass through the user’s firewall.
TCP based MQTT protocol is more reliable on internet than UDP based CAPWAP protocol.
If the AC and gateways are connected through the internet, and the Cassia RESTful API
through the AC is used to collect Bluetooth device data, it is highly recommended to
disable CAPWAP ports in AC Settings page, which will force all the gateways to connect to
the AC through MQTT. Otherwise, there might be packet loss or an incorrect message
sequence between the gateway and AC. The API calls might return HTTP 502 or 504 errors,
depending on the internet connection quality.
One AC can use MQTT to communicate with some gateways and use CAPWAP to
communicate with the other gateways at the same time. The user can enable or disable
CAPWAP and MQTT ports on AC by setting “CAPWAP port” and “MQTT port” on AC
setting page. The user can disable CAPWAP ports if they don’t want gateways to connect
this AC by CAPWAP.
The user can set the preferred gateway-AC protocol by setting parameter “AC-Gateway
Protocol Priority” on AC or gateway’s console. First, the gateway will use the preferred
protocol to connect AC. If it failed, e.g., port is blocked by the firewall, the gateway will try
the other protocol automatically. After the gateway is online, the user can find the actually
used protocol by checking “AC-Gateway Protocol” on AC or gateway’s console.
NOTE: From version 2.0.3, a newly installed AC will support MQTT only (CAPWAP disabled
28 Copyright 2021 Cassia Networks, Inc.
by default). If the user needs to connect a version 1.4.x gateway (only supports CAPWAP)
to a 2.0.3 AC, please enable the CAPWAP ports in AC settings. For the AC upgraded from a
lower version, both CAPWAP and MQTT will be enabled by default.
NOTE: From firmware 2.0.3, the default “AC-Gateway Protocol Priority” on the gateway is
MQTT. If the gateway was upgraded from lower versions, the default value will be
CAPWAP.
Please follow the below steps to migrate one gateway from CAPWAP to MQTT.
1) Open outbound TCP port 8883 on gateway side firewall.
2) Fill in AC server address in AC console gateway Config tab or gateway console
Basic tab, if it is empty. NOTE: AC server address is mandatory if AC is in the cloud
or MQTT is used for gateway and AC communication.
3) In the AC console gateway Config tab or gateway console Basic tab, please change
“AC-Gateway Protocol Priority” from CAPWAP to MQTT.
4) The gateway will disconnect from AC and try to re-connect by MQTT. If the
gateway can’t connect to AC by MQTT in 15 minutes, it will try CAPWAP instead
automatically.
5) After the gateway is on-line, please check if MQTT is actually used by checking
“AC-Gateway Protocol” on the AC console gateway Details tab or gateway console
Status tab.
6) When all the gateways managed by one AC have been migrated to MQTT, the
user can disable CAPWAP ports on the AC setting page.
You will find your Cassia Bluetooth gateway’s MAC address located at the bottom of the
gateway.
If you are filtering MAC addresses in your security policy, please make sure to input the
active MAC addresses. For example, if you are using Wi-Fi for an uplink connection, your
active MAC will be Label_ MAC+1. See the table below for further details.
For firmware 1.2 or above, a Cassia Bluetooth gateway comes with a Wi-Fi hotspot
function (2.4GHz only). The SSID is cassia-xxxxxx (the “x’s” corresponds to the last 6 digits
of the gateway’s MAC address). The default password of the Wi-Fi hotspot is the same as
the SSID.
For example, if the Cassia Bluetooth gateway MAC address is “CC:1B:E0:E0:96:DC”, the
SSID and its default password will be “cassia-E096DC”. The gateway’s default IP address is
192.168.40.1. The gateway’s console default username is admin.
Please follow the Gateway Installation Guide to connect your laptop to the Wi-Fi hotspot
and to configure the gateway and connect it to the AC. For detailed instructions, please
click here: https://www.cassianetworks.com/support/knowledge-base/.
If you are running a firmware version lower than 1.2, then a setup requires a few
additional steps. For detailed instructions please follow the document link here:
https://www.cassianetworks.com/download/docs/Cassia_Quick_Start_Guide-
v1.2.pdf
If you can’t find the Wi-Fi hotspot (2.4GHz only) or forget the username and password,
and your firmware is 1.2 or above, please press and hold the reset button located at the
bottom of the gateway for 10 to 15 seconds while the gateway is powered on. Once reset,
NOTE: After reset, the gateway configurations in the below table will be set to the factory
default profile settings. The country code, container, and customer APP will not be
impacted.
To configure the gateway, please open the Cassia Bluetooth gateway’s local console by
entering its local IP address or access it from the gateway’s Wi-Fi hotspot. The user can also
configure the gateways by gateway auto configuration feature (chapter 6.6), or configure the
gateways in batch from AC console (chapter 6.7).
The gateway’s local console account will be frozen for 1 minute after 5 failed attempts. The
login password will expire in 180 days if “Change Password Every 180 days” is switched on in
Other tab.
NOTE: The Google Chrome browser is preferred as results may vary with other browsers.
Parameter Description
Model X2000, X1000, E1000 or S2000.
MAC This is the MAC address printed on the bottom of the Cassia Bluetooth
gateway, which is equal to the gateway’s Ethernet interface MAC.
Working Mode AC Managed mode means the Cassia Bluetooth Gateway is connected to
the Cassia IoT Access Controller and managed by the AC.
Standalone mode means the Cassia Bluetooth Gateway is not connected to
the AC and operating locally.
AC-Gateway Protocol CAPWAP or MQTT. It shows the actually used gateway-AC
communication protocol. It may be different from the “AC-Gateway
Protocol Priority” configuration, which is the preferred protocol. If the
gateway connects to AC successfully, it will save the used protocol and try
it first after the connection is lost or gateway reboot.
Uplink Ethernet, Wi-Fi, or USB cellular modem
ETH IP Ethernet IP address of the gateway
WLAN IP WLAN IP address
Cellular IP The IP address of the gateway when using a USB cellular modem
Country/Region Deployment location
Firmware Version The firmware version on the gateway
Up Time The gateway up time in hours since the last reboot
AC Online Time The time of the gateway connected with the AC. If not connected, it shows
offline.
Chip 0 Status of BLE chip 0. It can be idle, active scan, passive scan, or advertise
Chip 1 Status of BLE chip 1. It can be idle, active scan, passive scan, or advertise
CPU Usage Current status of CPU
Memory Usage Current memory usage
Storage Usage Total and current storage usage
The user can configure the most common settings for the gateway, such as Gateway
Mode, Tx Power, AC Server Address, Remote Assistance, Connection Priority, and
Wired/Wi-Fi/Cellular configurations.
The Cassia Bluetooth Gateway supports the following networking uplinks: wired, Wi-Fi,
and USB cellular modem.
NOTE:
1. In general, Wi-Fi and cellular networks are less stable and have more interference
compared to Ethernet connections. To guarantee good uplink performance, we
suggest that the user use Ethernet (wired) for the uplink.
2. Cassia Bluetooth gateway does not operate in networks with VPN (Virtual Private
Network).
Parameter Description
Gateway Name From firmware v2.1.1, the user can setup gateway name from the
gateway’s local webpage. The user can still setup gateway’s name
from AC as before.
This is very useful for the user who doesn’t share AC account to the
engineers that install the Bluetooth gateway. When a new Bluetooth
NOTE: To check if the external BLE antenna is enabled, the user can
check if the received RSSI changed.
Statistics Report Interval Cassia gateway reports statistical information to AC regularly. The
default statistic report interval is 30 seconds. This interval setting can
be increased to 1, 2, or 5 minutes.
NOTE: If the user uses Cassia RESTful API through AC, please do an
OAuth 2.0 authentication with the AC using the developer
credentials granted. It is not necessary to do OAuth on each
gateway. For the user using Cassia RESTful API in the container, it is
not necessary to do OAuth authentication.
Remote Assistance Turn this on will enable Cassia engineers to remotely access the
gateway for troubleshooting purposes. By default, this function is off.
The network uplink traffic between the gateway and the AC includes BLE traffic and
management traffic. There are two ways to reduce the uplink management traffic.
3. The user can change the Statistic Report Interval to 1, 2, or 5 minutes
4. The user can select MQTT as the Data Path on the AC Settings page in v1.4, or
select MQTT as AC-Gateway communication protocol on the gateway web page
in v2.0.
Below are examples of network uplink management traffic with different configurations
(not including BLE traffic).
CAPWAP CAPWAP control MQTT
Firmware & Configuration control + data MQTT data path control + data
(MB per month) (MB per month) (MB per month)
v1.3 (w/o container) 255 (DL 58, UL 197) N/A in v1.3 N/A
v1.3 (w/ container) 390 (DL 58, UL 332) N/A in v1.3 N/A
v1.4 (30s, w/o container) 195 (DL 43, UL 152) 165 (DL 50, UL 115) N/A
v1.4 (30s, w/ container) 215 (DL 43, UL 172) 175 (DL 53, UL 122) N/A
v1.4 (5min, w/o container) 170 (DL 43, UL 127) 117 (DL 45, UL 72) N/A
The network uplink traffic in the production environment depends on the configuration,
BLE device, etc, and should be evaluated on a case-by-case basis. It is recommended to
use scan filter API to reduce BLE uplink traffic. Please refer to SDK Implementation Guide
for details.
In Static IP allocation, please enter your network information, including IP, netmask,
gateway, and DNS.
Cassia’s Bluetooth gateways’ Wi-Fi supports Client or Hotspot mode (2.4GHz only). For
the initial deployment, the gateway operates in Hotspot mode by default. This allows
the user to connect to the gateway via Wi-Fi using a laptop or mobile device for
configuration purposes. The Cassia Bluetooth gateway will advertise an SSID: cassia-
xxxxxx (the “x’s” correspond to the last 6-digit of the gateway’s MAC address). For
additional details, see section 4.3.
To use the Wi-Fi as your uplink, please switch the Operating Mode to the Client mode.
Please complete the rest of the configuration fields. For details on your Wi-Fi settings,
please contact your IT administrator.
From firmware 2.0.3, the user can enable “Verify before saving” before switching to
Client mode. If the gateway can’t connect to Wi-Fi AP within 30 seconds, it will switch
back to Hotspot mode automatically. This function will avoid an un-necessary gateway
reset if the user sets the wrong Wi-Fi configuration.
NOTE:
1. X1000 and S2000 only support 2.4GHz Wi-Fi. E1000 and X2000 support both
2.4GHz and 5GHz Wi-Fi. Wi-Fi hotspot mode only supports 2.4GHz.
2. The country code should be set correctly when using 5G Wi-Fi. Otherwise, 5G
36 Copyright 2021 Cassia Networks, Inc.
Wi-Fi may not work correctly.
3. Once changed Wi-Fi operation mode to the Client, the gateway will stop sharing
the Wi-Fi hotspot and changes the connection to the configured WIFI network.
You can enable the Wi-Fi hotspot by setting Wi-Fi operation mode to Hotspot
from AC or gateway console. You can find the gateway’s local IP address in AC.
The local IT department can also find out the gateway’s local IP address by
accessing the Wi-Fi AP device list or by performing the network scan. In case a
static IP is used, the address is known.
4. Before firmware 2.0.3, if there was an error in Wi-Fi SSID, password, or IP
address configurations, you cannot access the gateway anymore. Please press
the reset button for 10 seconds to reset the gateway.
From firmware 1.4 and above, Cassia’s gateway supports additional Wi-Fi security
modes. The user can choose the Wi-Fi Security Mode, provide the required inputs, and
then connect to the Wi-Fi AP with enterprise-level security.
From firmware 2.0, the user can set two Wi-Fi SSID as uplinks for redundancy. Gateway
will switch to the secondary Wi-Fi SSID automatically if the first SSID can’t be detected
or can’t be connected.
NOTE: If the secondary Wi-Fi SSID is enabled, both Wi-Fi SSID protocols should be DHCP.
Cassia’s gateway supports USB cellular modem as the network uplink. You will have to
purchase a supported USB cellular modem and a SIM card with an active data plan that
works with the USB cellular modem.
Before using any USB cellular modem, please connect it to your laptop/desktop to
ensure the internet can be accessed with the USB cellular modem. After testing the
connection to the internet, please connect the USB cellular modem to the USB port on
the Cassia Bluetooth gateway, select the right modem type and configure the
parameters, if needed.
Cassia’s Bluetooth gateway also supports the use of any USB-powered Wi-Fi modems. In
this case, the gateway can connect to the Wi-Fi modem by Wi-Fi uplink (chapter 5.2.2).
The USB cellular modem with RNDIS Driver Ethernet Type 1 & Type 2 is supported.
• Type 1: An APN needs to be specified. For example, wyleslte.gw7.vzwentp
and 10569.mcs are KORE Wireless APN. NOTE: If you are using a SIM card
from another cellular operator, please contact the cellular operator for the
right APN.
• Type 2: It applies the settings automatically and shows the LAN connection.
e.g., HW E3372s-153 modem.
Below are the USB cellular modems that can be selected by default:
• HW MS2131i-8
• HW E3372s-153
• HW E3372h-153
• HW E8372h-153 (Europe)
• HW E8372h-155 (China)
• HW E8372h-320 (Europe, added in firmware v2.1.1)
• HW E8372h-820 (China, added in firmware v2.1.1)
• Novatel USB730L (for Verizon)
• MultiTech MTD-MVW1 (for Verizon)
• MultiTech MTD-MNA1 (for Verizon, AT&T, and other Cellular operators)
• MultiTech MTCM-LAT3-B03 (for AT&T, T-Mobile, and other Cellular operators)
• MultiTech MTCM-LNA3-B03 (for Verizon and AT&T)
• MultiTech MTCM-LSP3-B03 (for Sprint)
• MultiTech MTCM2-L4G1 (for Vodafone, Telefonica and Orange)
• Zoom 4615 (for Verizon)
• Zoom 4630 (for AT&T, T-Mobile, and other Cellular operators)
• ConnectedIO EM1000T-VZ-CAT1 (for Verizon)
• NXCC UX302NC (for DoCoMo)
• Soracom Onyx Dongle SC-QGLC4-C1
To fit USB730L into the bottom enclosure of the X1000, the USB connector of U730L
should be turned over. Please follow the steps below.
40 Copyright 2021 Cassia Networks, Inc.
Step 1: Remove the two screws of the USB connector Step 2: Remove the cover with the USB logo
Step 3: Turn over the USB connector Step 4: Put the cover and the two screws back
New USB cellular modems can be added by using the Custom option. Below is an
example. For USB cellular modem and SIM card related information, please contact the
carrier.
NOTE: With a USB cellular modem, the Cassia Bluetooth gateway needs to be in a place
where there is good cellular network coverage. From firmware 2.0, the user can check
the cellular signal strength on AC (AC->Gateway->Details->Uplink) or gateway console
(Status tab) as GOOD, MEDIUM, or POOR. If the signal strength is POOR, please try SIM
cards from other cellular operators or try other uplink solutions. Only MultiTech celllar
modems, HW cellular modems and ConnectedIO EM1000T-VZ-CAT1 support the
showing of cellular signal strength.
NOTE: If the user changed the default setting of parameter “Device” for MultiTech
cellular modems, the value of RSSI, IMSI and IMEI may render incorrectly.
Cassia gateway supports USB cellular modem auto recovery function. After setting
“Recover Action” to ON, Cassia gateway will power reset the USB cellular modem
(X2000) or reset the USB interface (other gateways) if it can’t reconnect to the cellular
network in 10 minutes. For an AC managed gateway, if the cellular connection can’t be
recovered in one hour, the gateway will perform a soft reboot automatically. All cellular
modems connected by USB port are able to support this function.
From firmware 1.3 and above, Cassia’s Bluetooth gateway E1000, X1000, and X2000
support custom applications in the container (OS is Ubuntu 16.04.3).
• Before firmware 2.0.3, when HTTPS is enabled on the gateway, the Cassia API URL used
in the container APP should be updated to use port 443. From firmware 2.0.3, port 80
between container and gateway firmware is always enabled, so APP doesn’t need to
be updated regardless of the gateway’s HTTPS settings.
• After upgrading gateway firmware to 2.0.2, if the APP uses BlueZ with Gatttool and
Bluetoothd (e.g., noble or python Bluetooth lib) instead of Cassia Bluetooth stack and
Cassia RESTful API, please change ‘Cassia Bluetooth Stack’ to close (in AC console ->
Gateway -> Config-> Bluetooth Setting, or gateway console -> Other -> Bluetooth
Setting, default is open). Otherwise, Bluetooth operations in the APP may return
failure.
Cassia Bluetooth stack and Cassia RESTful API offer the state of the art Bluetooth
scan and connection performance. It is highly recommended to keep the Cassia
Bluetooth stack open and use Cassia RESTful API to achieve the best performance
• From firmware 2.0.2, an option to enable and disable container local SSH login is added
in the Container tab. The container local SSH login is OFF by default for security reasons.
Please turn it ON, before you want to local SSH login the container. Reset gateway will
change this option into the default value OFF.
• From firmware 2.0.2, the output of the RESTful API to obtain gateway configuration
from AC will be changed (GET http://{your AC domain}/api/cassia/info?mac=
<hubmac>). The container status will be removed from the default API output, to avoid
the oversized UDP packets problem. Container status can be got separately by the
same API with the additional parameter ‘fields=container’. Please refer to SDK WIKI for
details.
• From gateway firmware 2.0.2, DNS name server in Cassia Bluetooth gateway will be
propagated into container /etc/resolv.conf. Besides two default DNS name servers
8.8.8.8 and 114.114.114.114 , the container will use the DNS setting in the Network
section of the gateway webpage Config tab as an additional DNS name server. This
feature solves the problem that the firewall blocks two default DNS servers.
Legacy NOTES
• Please remember to change the container SSH password upon the first login.
• Please implement APP log rotation to avoid flooding container storage. From v1.4.3,
the container can use up to 2.3GB. For the gateways with firmware lower than v1.4.3,
if APP log floods gateway storage, the gateway may be offline and can’t recover by a
reboot. The user has to press the factory reset button to reset the gateway and then
delete the container.
• It is suggested to keep the memory usage in the container below 70%. The other 30%
is for peak hours and abnormal cases. It means the container should use less than
90MB, which includes memory used by custom application and all the tools running in
the container.
• Reset container will delete and re-create the container. The files under /opt will be
kept, and the custom APPs not under /opt will be deleted.
• Factory reset gateway will not impact the container, APP, and container files.
• If you want to upgrade an existing APP, please make sure that the name and/or version
is different.
• Cassia gateway container uses a compact version of Ubuntu. Certain packages may not
be pre-installed and/or available.
• The user has SSH/root access to the Ubuntu container. However, Ubuntu is running as
a container, so its core cannot be modified, and the properties of sysfs, e.g., /proc, is
read-only.
• Please make sure the ports in chapter 4.3 are opened outbound on the gateway side
43 Copyright 2021 Cassia Networks, Inc.
firewall. The user can check if a TCP port is opened by using Netcat on the gateway’s
console
The container and APP share CPU, memory, and storage with the host gateway. Please
check the below table for more information. When there is no APP installed, the container
CPU usage is usually lower than 5%, the container memory usage is usually lower than 1%,
and there is about 1.1 GB storage free (container uses about 1.2 GB)
The first container version is v1.1.1. The latest container version is v2.0.1. Please check
below table for the major difference. The user can keep using v1.1.1 container if they don’t
need the new features in v2.0.1 container. Please verify your APP together with the new
container carefully before rolling out new container to more gateways, since the Ubuntu
version changed and the pre-installed utilities and packages are different.
Please download the container firmware from the link below: Note: this link is Password
Protected.
https://www.cassianetworks.com/support/knowledge-base/router-gateway-firmware/.
Below is the list of utilities and packages pre-loaded in container v1.1.1 and v2.0.1.
python3-dbus No 1.2.16
NPM 3.10.10 No
node-gyp 6.11.5 No
noble 4.4.6 No
Please follow the steps below on the gateway console to install the container. The detailed
installation and deployment guide can be found in Cassia Custom Application Deployment
Instructions in https://www.cassianetworks.com/support/knowledge-base/general-
documents/.
From firmware 1.4.2, the user can install a container from an smartphone locally. Please
save the container firmware on your smartphone in advance and login gateway’s local
console from the Wi-Fi hotspot (2.4GHz only) or the gateway’s private IP.
Select and install container firmware:
The Container tab page displays Operating System, Container Status, Container Version,
Storage Usage, Transmit Rate, Transmit Bytes, Receive Rate, Receive Bytes, CPU Usage, and
Memory Usage of the container.
Parameter Description
Operating System The core of the container, e.g., Ubuntu 16.04.3 in release 1.3
Container Status Working status of the container
Container Version The firmware version of the container
Storage Usage Storage usage and reserved by the container (out of 2.3GB storage)
Transmit Rate Transmit Rate by the container
Transmit Bytes Transmit Bytes by the container
Receive Rate Receive Rate by the container
Receive Bytes Receive Bytes by the container
CPU Usage CPU used by the container (out of 2 CPU cores)
Memory Usage Memory used by the container (out of 128MB RAM for E1000 and
X1000, and out of 700MB RAM for X2000)
The Container tab page also displays the installed APP on the container and the programs in
operation.
The user can update the APP by clicking the button Select File and Install. From firmware
1.4.2, the user can update the APP from the smartphone locally. Please save the APP on
your smartphone in advance and login gateway’s local console from the Wi-Fi hotspot
(2.4GHz only) or the gateway’s private IP.
From firmware 2.0.3, the user can delete the installed APP by clicking the Del button. This
action will delete /root/apps/${app_name}.sh and /root/apps/${app_name}.version, but
will remain all other APP files unchanged (avoid deleting important customer data). Please
delete the other APP files, if necessary, by adding delete script (recommended, available
from firmware v2.1.1), adding codes in autorun.sh of the new APP, or by SSH into the
container.
The user can also follow the below steps to install or delete APP for a batch of gateways.
APP in the container can call local RESTful API like below (Turn on scanning as an example).
$curl –v 10.10.10.254/gap/nodes/?event=1&active=1
From firmware 1.4.1, the user can add their own APP configuration console in Cassia
gateway’s local console and AC’s console.
First, please add meta.json (defines the configuration items) in the APP package. After that,
the user can find their APP configuration console on the gateway local console and AC
console. After the configuration, the gateway will generate file config.json under folder
/root/config/<app_name>/.
The user can also Run, Stop, Reset or Delete the container by clicking the buttons.
The Events tab page displays events of different Level (Info, Major, etc.) and different
Module (Web, Bluetooth, MQTT, WTP, Network, etc.). The user can click the Export button
to export the logs for further analysis.
The Status tab page displays the Portal Password. When logging in for the first time, the
gateway’s console will require the user to change from the default password. The password
should include numbers, letters, and special characters. The password length should be
between 8-20.
The user can update the gateway’s firmware from AC or gateway console by clicking the
Select File and Upgrade button. If the firmware image is encrypted with *.GPG, please
switch on “Verify GPG File Encryption?”. Please turn it off if the firmware image is *.gz file
format.
From firmware 1.4.2 and above, the user can update the gateway’s firmware from an
smartphone locally. Please download the gateway firmware onto your smartphone in
advance and log into the gateway’s local console from the Wi-Fi hotspot (2.4GHz only) or
the gateway’s private IP.
50 Copyright 2021 Cassia Networks, Inc.
The latest firmware download is available here:
https://www.cassianetworks.com/support/knowledge-base/router-gateway-firmware/.
Please note, this download site is password protected for Cassia’s authorized partners.
For example, when using the Bluetooth debugger, please set “Access Control Allow Origin”
and “Allow Origin” to * or the URL of the requesting page http://www.bluetooth.tech
If you want to use HTTPS to access the gateway web or call local RESTful API, please switch
on “Enable HTTPS” and provide the SSL Private Key and SSL Certificate files.
The user can also import a dedicated SSL Private Key and SSL Certificate for secure
communication between gateway and AC. Cassia gateway always uses secured CAPWAP
and MQTT to communicate with AC, no matter if the default or custom certificates are
used.
From firmware 1.4, the user can run network debug tools Ping, Traceroute, TCP dump, and
NetCat on the gateway’s local console. From firmware 2.0.3, the user can run Speed Test
too. Speed Test will not work if the gateway has multiple uplinks, e.g., Ethernet and Wi-Fi
are connected at the same time. These debug tools will help on-site engineers to identify
network issues. NOTE: S2000 only support Ping, Traceroute, NetCat and Deployment tool.
From firmware 2.1.0, the user can run the BLE throughput monitor tool by selecting
“Throughput” in the gateway’s local console. This tool can show how many BLE connections
on each chip and show the BLE throughput of all the connections or part of them. The user
can check the result in chart format (not supported by S2000) or table format. To get the
correct display format, please use this tool on the computer only.
The user can click the Reboot button to perform a restart of the gateway. The user can also
click the Reset button to reset the gateway’s configuration to the default profile settings
and enable a Wi-Fi hotspot (2.4GHz only). The country code, container, and customer APP
will not be impacted. Please check chapter 4.5 for more information.
To minimize cybersecurity risks, please remember to click the Sign Out button after the
gateway configuration.
From firmware 2.0.3, the user can download the gateway debug log from AC too (see below
screenshot). Only one gateway’s debug log can be downloaded from AC at the same time. It
may take 2-5 minutes (time out in 10 min) to download one gateway debug log. Please
don’t touch the AC console and wait until the download is finished, otherwise, the
download may be interrupted.
If the gateway is configured as standalone mode (in the Basic tab), the user can configure
below Bluetooth parameters on the gateway’s local console. If the gateway is configured as
AC managed mode, the user can only set these parameters on the AC server console.
One Bluetooth chip can support scan and connection at the same time. If Default is
selected, the gateway will use a set of pre-defined parameters. If Custom is selected, the
user can define the Cassia gateway’s BLE parameters, e.g., connection interval. The table
below shows the default, maximum and minimum values of each parameter.
Parameter Default (ms) Min (ms) Max (ms)
Scan Interval 15 2.5 10240
Scan Window 10 2.5 10240
LE Page Scan Interval 60 2.5 10240
LE Page Scan Window 30 2.5 10240
Connection Min Interval 7.5 7.5 4000
Connection Max Interval 30 7.5 4000
Latency 0 0 499
Supervisor Timeout 1000 100 32000
Cassia Bluetooth gateway E1000, S2000, and X2000 offers a more flexible Bluetooth
configuration and two state-of-the-art Bluetooth modes: pure scan and high speed multiple
connection modes. The two Bluetooth chips can run in a different mode with a different
configuration, for example, one chip uses pure scan mode, and the other chip uses high
speed multiple connection mode.
From firmware 2.0.3, the user can enable the “avoid 2.4G interference” feature to minimize
the 2.4Ghz interference between Wi-Fi and BLE. To avoid 2.4Ghz interference, we
recommend installing Cassia Bluetooth gateway at least 3 feet (1 meter) away from Wi-Fi
access points. But in some cases, there still may be 2.4Ghz interference even Cassia
Bluetooth gateway and Wi-Fi access points are installed 3-6 meters away from each other.
For example, if there is continuous Wi-Fi download on one specific Wi-Fi 2.4Ghz channel,
Wi-Fi may cause strong interference to BLE. In this case, the user can set the Wi-Fi channels
which have the most interference (channel 1, 6, or 11) in Bluetooth Setting. Then, Cassia
Bluetooth gateway will avoid using these frequencies. Please check your Wi-Fi channel
configuration on the Wi-Fi access point or contact your IT team.
From firmware 1.4 and above, Cassia supports Azure IoT SDK on X1000 and E1000. The
Cassia gateway must be operated in standalone mode and connected to Azure IoT Hub by
MQTT protocol.
NOTE: Azure IoT SDK support is a Beta version in firmware 1.4. Please contact
[email protected] for Azure beta program details.
The user can control the Cassia gateway by calling the “Direct Method” or “Message to
Device” interface. The JSON format is based on local RESTful API. The feedback and data
from Cassia gateway are reported to Azure IoT Hub in JSON format. Also, the user can POST
JSON string from Cassia gateway container to Azure IoT Hub.
The Cassia gateway can send scanned data directly from the gateway to a third-party
server while keeping the control path to the AC. We call this function “bypass” mode.
Since release 1.2, Cassia gateway supports MQTT protocol on the bypass traffic which
means that the Cassia gateway can publish advertisement messages it receives from the
BLE sensors to an MQTT server/broker. Other clients, such as web applications on your
laptop and smartphone device can subscribe to the topics from the MQTT-Broker.
When the gateway is running in AC Managed mode (configured by Gateway Mode in Basic
tab), the user can only configure the gateway’s MQTT in the AC console (see the
configuration in AC->Gateway->Config->Bypass). When the gateway is running in
Standalone mode, the user can configure the MQTT function in the gateway console
Service tab. The user can set up data push and data cache configuration, MQTT
configurations, and scan settings.
To reduce MQTT packets and MQTT overheads, the gateway can cache a maximum of 100
advertisement packets or a maximum of 60 seconds, and send them to the MQTT broker
together.
Parameter Description
Scan Mode Passive or active scan
• The difference between active and passive scan is that active scan requests
a SCAN_RESPONSE packet from the advertiser.
62 Copyright 2021 Cassia Networks, Inc.
• A passive scan generally takes more time since the gateway must listen and
wait for an advertisement versus actively probing to find an advertiser.
However, with the passive scan, devices consume less battery power.
Filter Scan filters for advertisement packets
• Name: supports full name, prefix (for example Cassia*) and suffix (for
example *Cassia) name filters
• MAC: supports full MAC and prefix MAC filters (for example CC:DD:EE*)
• UUID: filter based on UUID in the advertisement packets.
• RSSI: filter out devices whose RSSI value is weaker than this value.
• Value: filter advertisement packets with data xx from offset yy. If offset is
not set, the gateway will filter data xx with any offset.
• Duplicates filter: for a value equal to or larger than 1000 (ms), if the
received advertisement packets are the same, the gateway will only send
one advertisement packet to the MQTT broker before the timer times out.
If the gateway receives a different advertisement packet, it will send the
new advertisement packet to the MQTT broker immediately. Value 1
means only send one packet for one device, which is usually used to detect
how many Bluetooth low energy devices are around the Bluetooth
gateway. Default is 0 (no timer).
NOTE: The keywords used for filtering need to be in the advertisement packets.
The UUID in advertisement packets may be only part of the UUID in Bluetooth
low energy profile.
Time Stamp Add timestamp in the bypass MQTT packets. Default is no
NOTE: Before upgrading AC software, please make sure the host server has a minimum of
2GB free storage.
Application
Server
Internet
Exit
Cassia AC
Core Switch
Access Access
BLE
Gateways
Internet
Exit
Core
Switch
Access Access
Switch Switch
Cassia BLE
Gateways
6.2. AC License
For a privately hosted AC server, please contact the Cassia sales team to apply for your
annual AC server license. One Cassia AC supports a maximum of three gateways when the
AC license is not applied or has expired.
• Length of subscription: monthly (for Starter Kit only) or annually
• Number of managed gateways: 4 to 9999 gateways
6.3. AC Statistics
AC statistics page shows the statistical data of the AC throughput, memory/CPU, gateways,
devices, AC API calls, and traffic amount per day, per week, or month.
From firmware 2.0, the user can select MQTT to replace CAPWAP. MQTT uses TCP
port 8883 and TLS 1.2. MQTT improves the robustness of gateway and AC
communication and can help the IP packets to pass through the user’s firewall, in
case the firewall doesn’t allow UDP packets to pass. One AC can support MQTT and
CAPWAP at the same time. Please check chapter 4.4 for more information.
• The interface between the AC and the application server is using RESTful APIs, on
HTTP (port 80) or HTTPS (port 443). For details on Cassia’s RESTful APIs please see
the next section. For more information about how to generate SSL private key and
certificate, please see section 5.5.
Cassia invented fast and secure Bluetooth roaming technology to solve this problem
without requiring any changes to the Bluetooth protocol and/or end devices.
• Ensures continuous user data connection during roaming handoff
• Ensures seamless and fast Bluetooth roaming without any human intervention
• No changes are required to the Bluetooth protocol and/or end devices
• Highly secure at all times
• Bluetooth roaming can be applied for any mobile Bluetooth IoT applications
First, please input or import the gateway configuration into AC, select when the
configuration should be sent (first time online or each time online), and then save the
configuration. The current configuration can be exported into a file.
The format of the configuration complies with JSON format of Cassia RESTful API “Obtain
Cassia Router’s Configuration”. Please check below link for more information about this
API (https://github.com/CassiaNetworks/CassiaSDKGuide/wiki/RESTful-API#obtain-cassia-
routers-configuration).
After the configuration is saved, it is suggested to check if the configuration is correct
(avoid typo). Please press button “Test Configuration” and select one on-line gateway.
After that, when the new gateway is online, AC will send the configuration to the new
gateways automatically. You can check the configuration result in the event log. If the
configuration failed, you can find “CONF FAIL” on gateway console too.
TIPS: You can select a specific type of gateway through the filter on the top left. If you
want to configure more gateways at once, please select showing 100 gateways per page
in the lower-left corner.
NOTE: The cellular modem configuration needs to be configured on the local console of
the gateway. They can’t be configured in batches from AC.
TIPS
• Only one type of parameter can be configured in batches at a time, for example,
Ethernet parameters and WIFI parameters can’t be configured at the same time.
74 Copyright 2021 Cassia Networks, Inc.
If you want to configure multiple types of parameters, please configure them
separately.
• If the configuration of some gateways fails, you can copy the configuration results
(see the red part in the below figure), and try to configure these gateways again
later.
Similarly, you can also perform batch upgrades, restarts, and resets for the Bluetooth
gateways. You can also perform batch operations for the containers and APPs.
For more information, please check the Cassia AC Bluetooth Debug Tool User Guide here:
https://www.cassianetworks.com/support/knowledge-base/general-documents/.
Please use http://www.bluetooth.tech/debugger/, if you are using AC software lower
than v1.4.
From firmware 2.0, the Cassia Access Controller (AC) provides email alert functionality. AC
will send an email to you in the below conditions.
• AC CPU/RAM/storage usage is higher than 80%: maximum one email every day
• AC license will expire within 30 days or has expired: maximum one email every day
• More than the pre-configured number of gateways is offline within 5 minutes: send an
email immediately
• Any gateway in the specific group goes offline or online: send an email immediately.
The user can tag one gateway with a maximum of three groups.
• Aggregated (all the gateways that use USB cellular modems) cellular data usage in this
calendar month is greater than the pre-configured threshold: maximum one email
every day
From firmware 2.1.1, the multiple AC viewer provides a central place to monitor the AC
online/offline status, AC resource consumption (CPU/Memory/Storage/Cellular),
online/offline gateways, and connected/detected devices for all their ACs.
To add a new AC to the monitoring list, please provide the AC Address, Developer Key &
Secret (in AC setting page) of the AC.
NOTE: The backup encrypted file can’t be imported to the AC on a different server if the
backup encrypted file includes AC license.
The Cassia RESTful APIs were developed to enable third-party developers and device
manufacturers to utilize Cassia’s gateway Bluetooth routing and extended range capabilities
while using their Cloud services to connect and control multiple BLE devices per gateway
simultaneously.
Furthermore, the Cassia RESTful APIs are designed to integrate directly into the
application/server using an HTTP/HTTPS-based communication protocol, which provides
programming language flexibility. Cassia supports C#, Node.js, and Java, but the user can
choose other languages as needed.
The Cassia RESTful APIs are built into the Cassia IoT Access Controller (AC) and Bluetooth
gateways and provide the following functions:
a. Monitor Bluetooth gateways and BLE devices
b. Connect and control BLE devices
c. Support three modes: scanning, connecting, broadcasting/advertising
d. Write/read data to/from the BLE device via the Cloud server
e. Read data as notification/indication events from the BLE device via the Cloud server
f. Bluetooth 4.2 Secure Pairing
g. Room based and triangle-based location tracking
Cassia RESTful API supports both HTTP (port 80) and HTTPS (port 443).
From firmware 2.1.0, a PHY update API is introduced to support Bluetooth Low Energy 5.0
higher data rates (2M PHY) and long range features. PHY update API is used to switch to a
different PHY after a Bluetooth connection is set up. Different PHY (2M, 1M, Coded w/ S2,
Coded w/ S8) can be used in two directions of a connected device or used in two
connections of two devices. The BLE5.0 advertising extensions don’t need a new API.
NOTE: From firmware 2.0, the output of the RESTful API to obtain gateway configuration
from AC will be changed (GET http://{your AC domain}/api/cassia/info?mac= <hubmac>).
The container status will be removed from the default API output, to avoid the oversized
UDP packets problem. Container status can be got separately by the same API with the
additional parameter ‘fields=container’. Please refer to SDK WIKI for details.
NOTE: Room-based and triangle-based location tracking APIs and gateway auto-selection APIs lead to
increased gateway traffic (high 4G cost) and increased CPU consumption. It is recommended to only
enable “BT Positioning” and “Gateway Auto-Selection” on the AC setting page when needed. What is
more, after upgrading AC from version 1.4.3 to version 2.0.2 and above, please double check if the
“Gateway Auto-Selection” in AC setting page is still OFF.
NOTE: From v2.1.0, in return message of scan API through AC, parameter name (‘event
type’) has been changed from ‘evt_type’ to ‘evtType’. This is to keep consistent with local API
in which ‘evtType’ is used. For example,
{"bdaddrs":[{"bdaddr":"E1:D2:F8:F9:82:E0","bdaddrType":"random"}],"adData":"020100000
00000000000000000","name":"(unknown)","rssi":-29,"evtType":0}
For details on Cassia RESTful API guidelines, please check the Github wiki site:
https://github.com/CassiaNetworks/CassiaSDKGuide/wiki.
Cassia’s demonstrations showcase the Cassia Bluetooth gateways and AC in use with off-the-
shelf BLE devices. Please see the full list at http://www.bluetooth.tech. The following section
demonstrates a Cassia Bluetooth gateway and AC in use with a Texas Instruments (TI) Sensor
Tag CC2650STK.
TI Sensor Tag
In your AC server console, you will see the sensor tag is connected under the Device page.
If you power on additional TI sensor tags, they will be connected to the same gateway one-
by-one.
Operating temperature:
-40° to +122° F (-40° to +50° C)
Storage temperature:
-40° to +185° F (-40° to +85° C) LTE CAT M1 only modems. They can only
access the cellular network where LTE
Humidity: CAT M1 is enabled. What is more, the
4G (LTE CAT M1): B4 (AWS 1700 Mhz), B13 78.7 mm x 40.1 mm x 18.8 mm Relative humidity 15% to 93% router upgrade may take more than one
MultiTech MTD-MVW1 (700 Mhz) Up to 300 Kbps downlink and 375 Kbps uplink Verizon Mini SIM (2FF) USA, Canada (not including USB cable) 1.4.3 + noncondensing hour because limited CAT M1 throughput.
4G (LTE CAT M1)
Verizon: B4 (AWS 1700 Mhz), B13 (700 LTE CAT M1 only modems. They can only
Mhz) access the cellular network where LTE
CAT M1 is enabled. What is more, the
AT&T: B2 (1900 Mhz), B4 (AWS 1700 Mhz), Verizon, AT&T and other cellular Same as MultiTech MTD- router upgrade may take more than one
MultiTech MTD-MNA1 B12 (700 Mhz) Same as MultiTech MTD-MVW1 operators Mini SIM (2FF) USA, Canada Same as MultiTech MTD-MVW1 1.4.3 + MVW1 hour because limited CAT M1 throughput
Verizon, AT&T, T-Mobile, and other Same as MultiTech MTCM-LAT3- Same as MultiTech MTCM- If customer wants to put this in the X1000,
MultiTech MTCM-LNA3-B03 Same as MultiTech MTCM-LAT3-B03 Same as MultiTech MTCM-LAT3-B03 cellular operators Micro SIM (3FF) USA, Canada B03 1.4.3 + LAT3-B03 they need ribbon cable antennas.
Same as MultiTech MTCM-LAT3- Same as MultiTech MTCM- If customer wants to put this in the X1000,
MultiTech MTCM-LSP3-B03 Same as MultiTech MTCM-LAT3-B03 Same as MultiTech MTCM-LAT3-B03 Sprint Micro SIM (3FF) USA, Canada B03 2.0.2 + LAT3-B03 they need ribbon cable antennas.
Operating temperature:
-22° to +140° F (-30° to +60° C)
88 Copyright 2021 Cassia Networks, Inc.
Storage temperature:
-40° to +185° F (-40° to +85° C)
May have heat issues encapsulated in the
4G (LTE CAT 1): B4 (AWS 1700 Mhz), B13 80.9 mm x 50.4 mm x 15 mm Humidity: X1000 bottom cap. Better to use outside
Zoom ZoomCell 4615 (700 Mhz) Up to 10 Mbps downlink and 5 Mbps uplink Verizon Micro SIM (3FF) USA (without antenna) 1.4.3 + 5% to 95% of the router.
LTE CAT 1: up to 10 Mbps downlink and 5 Mbps
4G (LTE CAT 1): B2/B4/B5/B12 uplink
May have heat issues encapsulated in the
3G (UMTS): 850 MHz / 1700 MHz / AWS HSPA: up to 7.2 Mbps downlink and 5.76 Mbps AT&T, T-Mobile, and other Cellular X1000 bottom cap. Better to use outside
Zoom ZoomCell 4630 2100 MHz / 1900 MHz uplink operators Micro SIM (3FF) USA Same as Zoom ZoomCell 4615 1.4.3 + Same as Zoom ZoomCell 4615 of the router.
84 mm x 57 mm x 17.79 mm This is too big for the X1000 bottom cap.
without antenna (please put Place it outside of the router.
4G (LTE CAT 1): B2 (1900 MHz), B4 (1700 EM1000T-VZ-CAT1 outside of Operating temperature:
ConnectedIO EM1000T-VZ-CAT1 MHz), B13 (700 MHz) Up to 10 Mbps downlink and 5 Mbps uplink Verizon Mini SIM (2FF) USA X1000 enclosure) 1.4.3 + -22° to +185° F (-30° to +85°C) Power input: 5V DC 0.5A
4G (LTE): 800/1500/1800/2100 MHz
Operating temperature:
3G (UMTS): 800/850/2100 MHz 14° to 122° F (-10° C to 50° C)
88 mm x 30 mm x 12.2 mm (not Humidity:
NXCC UX302NC 2G (GSM): 850/900/1800/1900 MHz DoCoMo Micro SIM (3FF) Japan including USB connector) 2.0.3 + 15% to 90% Can't use Softbank's SIM card
Appendix C: WPA2 Enterprise Security
From firmware 1.4, Cassia Bluetooth gateway supports 802.1x. It means from firmware 1.4
the user can use WPA2 enterprise Wi-Fi AP as the uplink.
NOTE
• In 1.4 GA firmware, a character return is required for CA certificate, Client Certificate,
and Private Key (please check below snapshots). In 1.4.1 GA and 2.0 GA firmware, the
character return is optional.
• In 1.4 GA and 1.4.1 GA firmware, please reboot the gateway after updating the CA
certificate, Client Certificate, or Private Key. In 2.0 GA firmware, we will fix this issue.
• Only the PEM certificate file format is supported.
• For private keys, Cassia has tested des, des3, seed, and aes. Camellia is not supported.
The user needs to set the Wi-Fi operation mode to “Client”, set the “Safe Mode” and “EAP
Type” based on the Wi-Fi AP configuration, and provide required inputs. Then, Cassia
Bluetooth gateway will connect to the Wi-Fi AP with WPA2 enterprise enabled.
The user should provide Identify and Password, besides SSID, IP, and DNS options. Below is
an example.
The user should provide Identify, Password, and CA Certificate, besides SSID, IP, and DNS
options. Below is an example.
The user should provide Identify, Password, CA Certificate, Client Certificate, Private Key, and
Private Key Password, besides SSID, IP, and DNS options. Below is an example.
If a password is not needed, the user should set “Safe Mode” to None. In this case, only SSID
and IP should be configured. Below is an example.
ca.crt example:
-----BEGIN CERTIFICATE-----
MIIDdTCCAl2gAwIBAgIJANeiouNsNcHlMA0GCSqGSIb3DQEBCwUAMFExCzAJBgNV
BAYTAlhYMRUwEwYDVQQHDAxEZWZhdWx0IENpdHkxHDAaBgNVBAoME0RlZmF1bHQg
Q29tcGFueSBMdGQxDTALBgNVBAMMBHRlc3QwHhcNMTgxMDMwMTA0NjQ5WhcNMjgx
MDI3MTA0NjQ5WjBRMQswCQYDVQQGEwJYWDEVMBMGA1UEBwwMRGVmYXVsdCBDaXR5
MRwwGgYDVQQKDBNEZWZhdWx0IENvbXBhbnkgTHRkMQ0wCwYDVQQDDAR0ZXN0MIIB
IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAymWBDuwiacayEuFG1BtvJF3Z
qu0OzyOExNh2cyuNx+rxgcy0CECkvDqXAvOOIpV5+C7SO39j5i3y6lIv6q8HbtQd
J04Fxjb//RJsPDG9GtK+RnC/p81Xi2o3AUJ6K8eLPhwsikt1nQaXCetT03JZKMQm
3cSqu2nyjJWowpHTr7cVTk8S6mZJBiLMPX6YOCTae1cR98JBlWfquRe9e/XJQAOw
/iq/51LAtHmee+x8eaai8/516bHsuVppYYIhqg4YNATeqsGT0BlQNrwjXekPx4KY
X3YmAP9EXBqApKts4ACIGcPLig81vKgd6hChTc6eK2yXW0dTuOMtkwTP+KOGiwID
AQABo1AwTjAdBgNVHQ4EFgQUXHdieYTw3ZOWAGLJDRRF6S0FIpswHwYDVR0jBBgw
FoAUXHdieYTw3ZOWAGLJDRRF6S0FIpswDAYDVR0TBAUwAwEB/zANBgkqhkiG9w0B
AQsFAAOCAQEAs3r/C51AJcpUxPvUT4XSVycMNH79gSYwbLsoBRC0r7YK04enIZ7r
fi6I0Dl3R6Qbp0ergt80QrBmGLI1nCPyqft0pUfCPaZEGrQhCo58r8NSQyCnSm67
mqzBrs3JIlvZixi/0rU1vaq5lFaJq6HaKiN0gJDuJPC1XX5Fern+/cGsBpFCzfG9
c/ouim3PB03M6UG+FBSX9UDpf/pTRfWnRzgmbITH5nMv/tXHKoNCQcCRYqkSgQ6L
kmncU8ajvWVOkJdztrtdsxHatcxlLaD79jd7hpETMjoOdpYuBRz7zs2K5SELw9QU
1g1YyMALL8wZCU2CBNbSCyzBL4DJrMug3g==
-----END CERTIFICATE-----
client.key example:
client.crt example:
-----BEGIN CERTIFICATE-----
MIIDHDCCAgQCCQCMtSyQfdk92zANBgkqhkiG9w0BAQsFADBRMQswCQYDVQQGEwJY
WDEVMBMGA1UEBwwMRGVmYXVsdCBDaXR5MRwwGgYDVQQKDBNEZWZhdWx0IENvbXBh
bnkgTHRkMQ0wCwYDVQQDDAR0ZXN0MB4XDTE4MTEwMTAyMTMyOVoXDTI4MTAyOTAy
MTMyOVowTzELMAkGA1UEBhMCWFgxFTATBgNVBAcMDERlZmF1bHQgQ2l0eTEcMBoG
A1UECgwTRGVmYXVsdCBDb21wYW55IEx0ZDELMAkGA1UEAwwCdHQwggEiMA0GCSqG
SIb3DQEBAQUAA4IBDwAwggEKAoIBAQDDPrVoQCFUXBgA807fkgrkYdF+ozeO3CGI
GJRxa3YsGVZ9TIcRe9L/oOkiOyomQbqRRGFcbULqmPyBAymtZoAkNOGGXP7nrco4
NOQA7dVPC6ueZi+gYWCuMOkKO8D8JVZnMZfctbymYLWNvIN8+TqAGV49+rSPU1wd
56eh26YJ4Wnq5gY1jPG9I233Tyq05Br6hFv79ZIOFSsqwK3rGd2447bh3yMb4ah2
qm+He78hK2XwV6X2M7UyUUTYwIo40hcc4k7edTK/thxqyUK3aCHQEUKK8ruF/BI7
dufVtH0k0srSLNJ3svsRh6VK5Rwi1CezABkknBQjcpWChcJcG8lVAgMBAAEwDQYJ
KoZIhvcNAQELBQADggEBAAfAnL6vIYh/IjlbdUMMSsdvWiAYIiSyWrLyz3ZeGs4u
lUaagR4evVNPTq7ToAbvtaDd0PTPoJkfVxVN65Rc/TtlwnkGh+GmQhk5twjEMUrs
7vDBkdYDOv3ZqHSpeFCDTwn1rO6HpV2h+it7EqhVlpyYow2QA1VMVgNJr7fBWMsY
AJsIepors/nGjBm57cQKMcmU8T6O5mYFGpaVlpM/q+1rm/zl7pmo4ghit1fiVlRi
HS0YB9ZbjVdwMbazf4m07h8x5vE8CzId9bD6ByWebANcOoy8z6fTSLUaifLU11D6
s92moajRMu6Dl5rnPvHFSwsofCjd4b7bZ2AUpGJeqTo=
-----END CERTIFICATE-----
Waste Electrical and Electronic Equipment (WEEE) symbol on the Cassia Bluetooth gateway
and/or accompanying documents means that used electrical and electronic equipment
(WEEE) should not be mixed with general household waste. Disposing of this product
correctly will help save valuable resources and prevent any potential negative effects on
human health and the environment, which could otherwise arise from inappropriate waste
handling.
If you wish to discard electrical and electronic equipment (EEE) in the European Union,
please contact your dealer or supplier for further information. Penalties may be applicable
for incorrect disposal of this waste, in accordance with your national legislation.
1. Overview
To further improve the communication security between Cassia IoT Access Controller (AC)
and Cassia Bluetooth gateway, Cassia supports configurable MQTT TLS certificates for
gateway and AC communication from firmware 2.0.
The user can generate their MQTT certificate and load it in AC and gateway console. If the
loaded certificate doesn’t match or expired, the gateway can’t connect to the AC. The
certificate can be a CA certificate or a self-signed certificate. Cassia gateway always uses the
secured MQTT to communicate with AC, no matter if the default or custom certificate is used.
NOTE
• Only PEM certificate file format is supported
• Don’t support private keys with passphrase protected
• Don’t support certificate revoke
2. AC Configuration
TCP port 8883 is used by MQTT protocol between Cassia AC and Cassia Bluetooth gateway.
The user can use NetCat to check if TCP port 8883 is enabled on AC and reachable from the
gateway. Please login gateway’s local console, select Other page, and run NetCat like below.
TCP port 8883 has been opened on VMware AC. If the user wants to open TCP port 8883 for
Cassia-hosted AC, please contact Cassia support.
NOTE: Please skip this step if the AC is running on the cloud, e.g., Azure or AWS because the
time of the host server is always correct.
If the AC is not running on the cloud, it is recommended to switch on “Set the time
automatically” and set your own NTP time servers on the AC setting page.
The AC time will be used for certificate validation. If the AC time is not configured correctly,
the gateway can’t connect to the AC.
Default means using the default certificate provided by Cassia. The gateway and AC
communication is still protected.
3. Gateway Configuration
Please configure the correct local date in the gateway’s local console Other tab. After
connected to AC, the gateway will get the correct time from AC automatically.
The local date will be used for certificate validation. If the date is not configured correctly,
the gateway can’t connect to the AC.
Please fill in MQTT certificates in the gateway Other tab. Please change Certificate
Configuration to User Config, and then fill in the CA Certificate, Client Certificate, and Client
Private Key.
NOTE
• The AC and gateways should use the same CA certificate.
• Now, we only support bi-directional authentication. It means the gateway will
authenticate AC and AC will authenticate gateway too. So, both CA certificate, client
certificate, and client private key should be provided on the gateway side.
The AC and gateway console will check the integrity & validity of the certificate and private
key. Please check chapter E.1 for the format requirement. If the local date and time are not
configured correctly (see chapter E.2.3 and E.3.1), the validity check will fail too.
If the gateway can’t connect to the AC, please double-check if you load the correct certificate
and private key. The user can set the Certificate Configuration back to Default to exclude any
other issues, e.g., transport issue.
The user can find TLS error logs in the gateway console Log tab.
ca.crt example:
-----BEGIN CERTIFICATE-----
MIIDdzCCAl+gAwIBAgIJALSD+kQkX3FuMA0GCSqGSIb3DQEBCwUAMFIxCzAJBgNV
BAYTAkFVMRMwEQYDVQQIDApTb21lLVN0YXRlMSEwHwYDVQQKDBhJbnRlcm5ldCBX
aWRnaXRzIFB0eSBMdGQxCzAJBgNVBAMMAmRkMB4XDTE5MDUwNTAzMDk0NloXDTIw
MDUwNDAzMDk0NlowUjELMAkGA1UEBhMCQVUxEzARBgNVBAgMClNvbWUtU3RhdGUx
ITAfBgNVBAoMGEludGVybmV0IFdpZGdpdHMgUHR5IEx0ZDELMAkGA1UEAwwCZGQw
ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDP+fPO92U1IHrIBvXHM5kP
wB25McMpRu3CUz9SnbC/LNi8uaSZI0glevlnsU/mckVeKDizWEX6ZrtPfokN8yH2
JmwaG16AAo6jmtmam9VjVWjZeXB7bGxIi9/obl/viD9efrLamNbpldBeZEFB0ia0
p6xcCh+0Vo+268xbWdiHGnwFaFcUMhaQ0hIuHdujWguSzMLYXqATGjhZSvdkSCe+
ieUcc+y4SZTPlH+xD78MwyBxGSxMxSo6ANRjcQNIJedn2eF36dcLbVSzOEEyR2Xs
EQYBVkAyv4mFR2uFOn/j+3LR+uqEI5vAGkKw5pl5D9d9em2Ym/O5IhosOOxTzBnF
AgMBAAGjUDBOMB0GA1UdDgQWBBT5SOcADFP2P/DhdcGZRD7H96BtuTAfBgNVHSME
GDAWgBT5SOcADFP2P/DhdcGZRD7H96BtuTAMBgNVHRMEBTADAQH/MA0GCSqGSIb3
DQEBCwUAA4IBAQAfnXfC/lMOROwv0KL8uyROtY2V1hvTjIoc1D/5zHGY7IOgLCyz
3ZRyvb3VGvVR+MPi8PHkp4X1mud/n8uVRDF+qTYvQnhxS2HF7ABxwC4Fz0JmIYAn
KYcLBgB4sUXHa8kqZiPcW8Y0GnXuT1kiYTGodfN0K6T3pXPy08Inh3IcySqwgjmh
cGppJQC86LugeLFN8lB/EzQSMPpG1fyxHwlyqmsm7LNryYqr5QoS2CUc6qlc3Hc0
pu+Q15kCapJ7TS71V5hOqEtHD7XuWfhYbltAQpexw5M6udECVa3TEUWBmq86Oq6/
n0aFHK5hb2J2NhpuPAKQIUbBn7UXTd3pw1RP
-----END CERTIFICATE-----
client.crt example:
-----BEGIN CERTIFICATE-----
MIIDKzCCAhMCCQDgCfVlo1FF7TANBgkqhkiG9w0BAQsFADBSMQswCQYDVQQGEwJB
VTETMBEGA1UECAwKU29tZS1TdGF0ZTEhMB8GA1UECgwYSW50ZXJuZXQgV2lkZ2l0
cyBQdHkgTHRkMQswCQYDVQQDDAJkZDAeFw0xOTA1MDUwNzM3NDNaFw0yMDA1MDQw
NzM3NDNaMF0xCzAJBgNVBAYTAkFVMRMwEQYDVQQIDApTb21lLVN0YXRlMSEwHwYD
VQQKDBhJbnRlcm5ldCBXaWRnaXRzIFB0eSBMdGQxFjAUBgNVBAMMDTE5Mi4xNjgu
MC4yNDUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC+XCQuhUEndr8c
9D7uZwzhi4OWzq3GeaZXpYyFnsEY/D7o/dlfPMMdE+THw4BRJ/PFROGZ6A23W3p8
KisRIa9z12LRoVa8kH3FVBB2Khw8i5n7xJsaP2bZ2yaEKCf77uR5r8S6xq3SRVhR
Webxwxo3j/bG+uWLWfj5spn6EZvuBXog64lcN6V9FEUUA1cpIEGAtKqQvFdYFPgj
sMLoKN2n2OJ0CZGqa4cbf3bfFPOSFVsG2IZurThIHeR9vovXf2cHU7bPRX/6gfQb
4KS4lD3hkX8SZ8vOKm/qNJj98IxIrNwYJBneP+BsSxBgAbq/89nVLlcT4DWcpDzu
rMyuwbYfAgMBAAEwDQYJKoZIhvcNAQELBQADggEBACc9mAkv9ErVQO7v7JrxweoJ
XnYcq4jlHIo9S7x5flTou2C4GVp1231jVRjzxJs3yQ0o+Xj8WsePHLpITNZRmYOS
SnAR/AhA3tUejHbfJsDKvsjHPBdG83hJ9MhQ1friyHiWVrMxVoPrPpvynG7mKN/i
FSQlxh9bTwHtTWhBJ5X1bqOnJaz69qaumGvSIIey3IklLKJhs4LC5ADn4HHa2Xfs
pRXC69CfPrYg/grTUPAY3uV/tPdTUDwCwxnvchR4bLgP4gUW6PSNvZ4MxRBx+ulx
f9Z4+5j5cnmDhafUdBtE4Vs809VlfK5hgwvIy2gzZjONBLQvFKqN5duwNvr08EM=
-----END CERTIFICATE-----
* HW models E3372s-153, E3372h-153 and E8372h are DHCP cellular modems. MultiTech
models MTCM-LNA3-B03 and MTCM2-L4G1 are PPPoE cellular modems. If you want to know
the type of other USB cellular modems, please contact your Cassia sales/support contact
X1000 LED may keep on blinking if the PoE power supply is not stable. Please try to replace
the PoE injector.
桂花网生产的蓝牙路由器符合 SJ / T 11364-2014
The Bluetooth gateways provided by Cassia Networks; Inc. is in conformity with standard SJ / T
11364-2014
产品中有害物质的名称和含量
Hazardous Substances Table
对销售之日的所售产品,本表显示我公司供应链的电子信息产品可能包含这些物质。 (This
table shows where these substances may be found in the supply chain of our electronic information
products, as of the date of sale of the enclosed product)
此环保使用期限只适用于产品在产品手册中所规定的条件下工作。
The Environment-Friendly Use Period is valid only when the product is operated under the
conditions defined in the product manual.
If you place your gateway as depicted in the image above, the images below show
the Antenna Gain in 3-D.
If you place the E1000 and S2000 on a tabletop (shown above), the radiation pattern
graph results are shown below.