Sentrius IG60-BL654 and IG60-BL654-LTE Wireless IoT Gateway

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.

We do have a dedicated Github page page that exposes Python examples code which undertake common operations between a BT510 and a BL654 loaded with smartBASIC AT Commands Interface.

It especially includes :

• Sensor configuration
• Analysing advertisements
• Reading and decoding BT510 event logs
• ... and many more!

These codes can be easily leveraged for any real world applications that would include BT510 mated with the IG60-BL654 or any other custom gateways.

You can find more information on the following page : https://github.com/LairdCP/BT510-Python

DTM functionality is integrated into our SmartBASIC firmware preloaded on the BL654 in the IG60 Laird Linux. Activation of DTM is done by AT+DTM command as described in this application note. Instead of using our UwTerminalX program you can use e.g., microcom to connect to the BL654 and communicate (microcom -s 115200 -p /dev/sttyS2, exit microcom with ctrl-x). After that DTM commands can be exercised which in fact are binary commands sent at 19200 baud instead of 115200 used for SmartBASIC interactive mode. However, most commands are composed of non-ascii bytes and hence it is not possible to enter these into microcom or other terminal programs. The below sequence shows how to send the exit-DTM-mode command from the Linux console as an example:

Set the serial port parameters to 19200/8N1:

stty -F /dev/ttyS2 19200 cs8 -parenb -cstopb

Echo a two-byte command (0x3f, 0xfe bytes) into the serial port device:

echo -ne "\x3f\xfe" > /dev/ttyS2

The -n switch will suppress the newline at string end and -e will allow for escape’ing of hex numbers. That way it will send the required bytes 0x3f and 0xff directly and raw into the serial port device.

Other DTM commands could be sent in the same way by replacing \x3f... with different hex numbers.

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…

There is a python script on the IG60-BLE654 LL developers SD card image called

btpa_utility.py

This can be used to upload, rename and delete sB apps to and from the IG60-BL654.

It can also be used to list the directory content and sending AT commands to the BL654.

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.

With access to the IG60 Laird Linux console you can start the terminal program "microcom" to issue AT commands to the integrated BL654 BLE module.
The BLE modulel istens on /dev/ttyS2.

# microcom /dev/ttyS2

To exit microcom use ctrl-x.
 

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

 

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.

There exist pre-defined GPIOs in the IG60 to control the BL654 module, which can be found under /sys/devices/platform/gpio:

• bt_nautorun: If set to 0 (low) autorun is active and and $autorun$ application will start after power up/reset and if set to 1 (high) autorun will be disabled.
• card_nreset: Setting to 0 (low) asserts BL654 reset and 1 (high) releases reset.

To exit an $autorun$ application nAUTORUN needs to be set high followed by a module reset.

echo 1 > /sys/devices/platform/gpio/bt_nautorun/value (disables autorun)
echo 0 > /sys/devices/platform/gpio/card_nreset/value (assert reset)
echo 1 > /sys/devices/platform/gpio/card_nreset/value (release reset)
echo 0 > /sys/devices/platform/gpio/bt_nautorun/value (re-enable autorun)

You should now be able to connect to the BL654 through e.g. microcom with access to the smartBASIC interactive mode:

microcom -s 115200 /dev/ttyS2

You can now use e.g. AT&F* to clear the flash file system before loading a new smartBASIC app to the module with the above Python script. (Note: CTRL-x will exit microcom).

Note: You can always check the current state of the above GPIOs with

cat /sys/devices/platform/gpio/.../value

See also the IG60-BL654 online documentation.

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.