Sentrius IG60-BL654 + BT610 Starter Kit

NMCLI should be utilized to configure network interfaces. 

It is possible to bring up an AP on the IG60/SOM60 with network manager. If the connection is marked as "autoconnect" it will come up even after reboot. Property: connection.autoconnect: yes

However in so called APSTA mode (simultaneous station / AP operation) each connection (station and AP) need to have their own interface.

The standard interface is wlan0. For the AP it is necessary to define a secon interface, for example ap0:

iw phy0 interface add ap0 type __ap

This setting however is not persistent, hence it needs to be definded upon every reboot of the IG60/SOM60.

This could be achieved by adding above line to a script in /etc/profile.d. For example:

cat /etc/profile.d/add_ap0.sh

iw phy0 interface add ap0 type __ap

With this script being present the interface ap0 will be avaiable after each reboot.

AWM, if active, sets the regulatory domain and country of the 60 radio to the current location with the help of beacons it recieves from surrounding access points.

While it is mandatory to be FCC compliant, the routine to determine the location must run every 30min. This is a draw-back for softAPs created on the 60-radio as connections will be interupted every 30min. Some clients may take this less grazefully than others.

Running the AWM routine regularily is not mandatory for the other regulatory domains the 60-series is certified for, though. For those it is enough that the loaction is determined upon the first run of the routine and it as not to be repeated after that. That is what AWM-lite does.

So, for radios only deployed in regulatory domains ISED, ETSI, MIC, KC AWM-lite can be used, which also enables the seamless use of the 60-radio as softAP in conjunction with AWM(-lite).

It is also good practice to consult "app_note_60_summit_awm" which is located in the documents archive of a 60-radio software release.

The LTE modem inside a LTE equipped IG60 running Laird Linux can be enable with the following command:

echo 0 > /sys/devices/platform/gpio/lte_on/value

A succesfull action will be indicated by two USB interfaces appearing:

# ip addr show

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

    inet 127.0.0.1/8 scope host lo

       valid_lft forever preferred_lft forever

    inet6 ::1/128 scope host

       valid_lft forever preferred_lft forever

2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000

    link/ether fa:87:d7:c4:c1:e3 brd ff:ff:ff:ff:ff:ff

3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000

    link/ether 36:42:a6:34:a7:4e brd ff:ff:ff:ff:ff:ff

4: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000

    link/ether c0:ee:40:44:e1:b4 brd ff:ff:ff:ff:ff:ff

5: usb0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000

    link/ether fa:96:11:12:13:14 brd ff:ff:ff:ff:ff:ff

6: usb1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000

    link/ether fa:96:11:12:13:16 brd ff:ff:ff:ff:ff:ff

Only usb0 is used by the LTE modem. usb1 can be ignored.

While for the Linux enthusiat it is surely not impossible to build and image for the SOM60 or IG60 that supports on device build capabilities with the given tools, it is neither intended by Laird, nor is it supported.

Reason for this are the limited resources (memory and processing power) an embedded module such as SOM60 and an embedded gateway like the IG60 can offer for on device building capabilities.

The preferred method would be to include any packages desired on the SOM60 or IG60 into the Buildroot SDK.

To add files to a Laird Linux build, enable "BR2_ROOTFS_OVERLAY" in your config and provide it with an absolute path to the directory you would like to overlay.  Files in this directory will be inserted relative to "/".  For example, if you would like to add files to "/etc" and the path to the overlay directory is "/buildroot/overlay", create a directory "/buildroot/overlay/etc/<files>".

Adaptive World Mode should not be used when hosting an AP.  The channel hopping algorithm can cause disconnect issues in some cases.  The best option is to set the regulatory domain in firmware manually, but at the minimum the "adaptive_ww" service should be disabled.  

Laird has added custom packages to Laird Linux.  These can be found in "menuconfig", under the "Laird Connectivity" / "Packages" section.  

To enable a Wi-Fi bridge, select the package "BR2_PACKAGE_LRD_WIFI_BRIDGE" and then set the destination interface. For example, set the destination interface to "Ethernet" if you would like to bridge the Wi-Fi to a wired connection.  

There's a Zephyr RTOS Discord channel.  This is a great place to ask questions and have them answered by the engineers who wrote the software.  There's even a channel for HL7800!

Project Zephyr Discord

The repo tool is often available to be installed using a package manager. In the case you're facing challenges with this method, or would like to directly add the repo files to your path, the following commands can be used:

sudo wget https://storage.googleapis.com/git-repo-downloads/repo -O /usr/local/bin/repo
sudo chmod a+rx /usr/local/bin/repo


When you run the "repo init" command for the first time you will be asked to configure your name and email. You can also set these values with the following commands:

git config --global user.email "you@example.com"
git config --global user.name "Your Name"
git config --global color.ui true


Use Network Manager to set an IP address as static in Laird Linux.  In the example below the IP address of ETH0 will be set to 192.168.2.150.

nmcli con add type ethernet con-name "static-ip" ifname eth0 ipv4.method manual ipv4.addresses 192.168.2.150/24
nmcli connection show
nmcli dev status

When an available LTE connection is configured along with WLAN profiles and/or one or more WLAN profiles, the Sentrius IG60 uses the following behaviour to establish network connections:

• If a WLAN like Wi-fi connection is established and available, it will be used when establishing a connection
• The LTE connection will be used for connections when a WLAN connection isn't available

After following all steps to register and commission your IG60-BL654-LTE trough Wi-fi then successively deploying BT510/610 into your Bluegrass account, go back to your IG60 Sentrius phone application to remove Wi-fi and enable LTE. After a couple of minutes the LTE connection should take over on sending BT510 data into your Bluegrass platform.

Please make sure to use a proper activated IoT SIM Card compatible with LTE Cat1 network.

Once a device has been provisioned into AWS Bluegrass platform, it should upgrade by itself. If the IG60 isn't being upgraded, it means that something is going wrong at a connection level.

Yes. There is a python script on the IG60-BL654 LL developer SD card image called
btpa_firmware_loader.py

This can be used to upload a new firmware to the BL654 inside IG60-BL654 LL.

IP stands for Ingress Protection. Its a standard we use to check the sealability of a product once it is installed.

It is composed as IP## , where first digit is for dust/solid objects and the 2nd digit, is for liquids.
Here is the meaning for each numerical code:

Laird Connectivity is committed to the long-term supply of all its standard embedded wireless modules and packaged products. Laird Connectivity’s products are specifically designed to meet the needs of the industrial and medical markets, which typically require 7 – 10 years product lifecycle. Although Laird Connectivity can’t guarantee that a component used in our products will not be obsoleted and cannot be reasonably substituted, Laird Connectivity can assure customers we will continue to sell our product when we have customer demand and can obtain the necessary components to build our products.

View our full policy here.