Sentrius IG60-SERIAL and IG60-SERIAL-LTE Wireless IoT Gateways

NMCLI should be utilized to configure network interfaces. 

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.  

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

Yes, but it requires integrating Canvas Device Manager and EdgeIQ. This currently is only supported for high volume customers. Please contact your local Laird sales representative if need be.

Unfortunately, the two IG60 version cannot be converted or swapped, so the Laird Linux image won't run on the AWS gateway and vice versa.

You need to boot into Linux and after Login log in issue the command

fw_setenv ethaddr <desired MAC address> 

for example:

fw_setenv ethaddr AABBCCDDEEFF

and reboot

You can read out the address previously set with:

fw_printenv ethaddr

Yes, there is one pin (4) on the power supply connector that can either be configured as an input or output.

The same pin can be connected to the AD converter of the IG60s host processor by software.

Consult Lairds application note "Configuring external I/O pin of the IG60 Laird Linux variant as input or output" to configure pin4 and this tutorial to use the AD converter on the host processor:

https://lairdcp.github.io/guides/60-som-dvk-docs/1.0/ad-converter-tutor…

Once you have created the soft AP on your Linux system and have successfully connected clients to the soft AP you can issue the command

# iw wlan0 station dump

to get a list of connected clients.

Note: the interface name (here: wlan0) might be different in your system.

You can use the Network Manager command line interface to create an open hotspot using this command:

nmcli con add con-name open_hotspot ifname wlan0 type wifi ssid yourSSID mode ap wifi.band bg wifi.channel 6 ipv4.method shared

 

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:

On the LairdLinux versions of the IG60 (455-00006, 455-00076, 455-00084 or 455-00088) you can access the console port by either attaching a USB to Serial adapter to the IG60 USB port and a null modem cable to your computer or by attaching a USB to serial cable to the IG60 USB port and a null modem adapter to your computer.

Also on the IG60-Serial (455-00006) or the IG60-Serial+LTE (455-00084), you can connect a null modem cable to the serial port on the IG60 and your computer.  

Note: You are not able to access the console on a GreenGrass version of the IG60 (455-00008, 455-00081, 455-00085 or 455-00089).

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.