0% found this document useful (0 votes)
636 views39 pages

Avnet SmartEdge IIoT Gateway User Guide - 20191217

Uploaded by

sef370
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
636 views39 pages

Avnet SmartEdge IIoT Gateway User Guide - 20191217

Uploaded by

sef370
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 39

SmartEdge Industrial IoT Gateway

User Guide

Version 1.1, 12/2019


SmartEdge Industrial IoT Gateway
User Guide

i. REVISION HISTORY
V1.0 Initial Release 20190820
V1.1 Update formatting, links, content 20191217

http://www.element14.com/gateway Page 2
SmartEdge Industrial IoT Gateway
User Guide

ii. TABLE OF CONTENTS

I. REVISION HISTORY 2

1. INTRODUCTION / OVERVIEW 7

1.1. IMPORTANT SAFETY INFORMATION 7

1.2. INTERNAL SYSTEM VIEW 7

1.3. PACKING LIST 8

2. HARDWARE DESCRIPTION 9

2.1. BLOCK DIAGRAM 9

2.2. SPECIFICATIONS 9
RASPBERRY PI 3 CORE 9
STORAGE MEDIUM 9
INPUT POWER 9
ENVIRONMENTAL 10
DIMENSIONING & MOUNTING 10
FRONT PANEL LEDS 10
HARDWARE WATCHDOG TIMER (WDT) 10
TRUSTED PLATFORM MODULE (TPM) & SECURE BOOT 10
REAL-TIME CLOCK (RTC) WITH BATTERY BACKUP 10

2.3. EXTERNAL CONNECTIONS 11


DC-INPUT 11
DUAL ETHERNET PORTS 11
DUAL USB PORTS 11
DISPLAY CONNECTOR 11
ISOLATED RS-485 / RS-422 / RS232 11
ISOLATED CANBUS 12
ISOLATED DIGITAL I/O 12

2.4. INTERNAL EXPANSION 13


USB HEADER 13
MINI-PCIE SLOT (J34) 13
HAT EXPANSION SLOT 14

3. USAGE 16

http://www.element14.com/gateway Page 3
SmartEdge Industrial IoT Gateway
User Guide

3.1. POWER INPUT 16

3.2. INTERFACES 16
USB 2.0 16
ETHERNET 16
RESET BUTTON 16
HDMI 16
ONBOARD DIGITAL I/O 16
ONBOARD RS232/485 17
CANBUS 17
INTERNAL MPCIE SLOT 17
INTERNAL RASPBERRY PI HAT EXPANSION SLOT 17

3.3. FUNCTION SELECTION JUMPERS 18


RS232/485 JUMPER 19
CANBUS JUMPER 19
WATCHDOG JUMPER 19

3.4. IOTCONNECT CLOUD ENROLLMENT 20


ENROLLMENT STEPS 20

3.5. IMAGE UPDATE 23


REQUIREMENTS 23
EMMC MOUNTING STEPS 23
WRITING A NEW IMAGE OR SAVING EXISTING 24

3.6. SYSTEM CUSTOMIZATION 24


HARDWARE CUSTOMIZATION 24
SOFTWARE CUSTOMIZATION 24

4. SOFTWARE CONFIGURATION 26

4.1. AVNET IMAGE 26


LOCAL ACCESS & CONFIGURATION 26
INCLUDED SOFTWARE 26

4.2. SECURE BOOT 27

4.3. MISCELLANEOUS 27
TRUSTED PLATFORM MODULE 27
DESKTOP GUI 27
OTHER SOFTWARE 28
REAL-TIME CLOCK (RTC) 28
RESET BUTTON 28

http://www.element14.com/gateway Page 4
SmartEdge Industrial IoT Gateway
User Guide

4.4. DIFFERENCES FROM STANDARD RASPBERRY PI 28


CUSTOM BOARD TYPE 28
eMMC UPDATE PROCEDURE 28
ON BOARD PERIPHERALS 29

5. IOTCONNECT DETAILS 30

5.1. USAGE 30
VIEW SENSORS 30
OTA UPDATES 30

5.2. CONFIGURING THE IOTCONNECT SDK 30


DEFAULT WIFI ACCESS POINT CREDENTIALS 30
MODIFY LOCAL CONFIGURATION 30
EXAMPLE 31

5.3. SYSTEM OPERATIONS 31


CONFIGURATION MODE 31
NORMAL MODE 31
TOP LED STATUS INDICATORS 31

5.4. WHAT’S NEXT 31

5.5. PROVISIONING MULTIPLE DEVICES 31


STEPS REQUIRED 32

6. REFERENCES 33

6.1. COMPLIANCE 33
REGULATORY COMPLIANCE AND MARKINGS 33
SIMPLIFIED EU DECLARATION OF CONFORMITY 33
SUPPLIER'S DECLARATION OF CONFORMITY 33
FCC COMPLIANCE STATEMENT 33
APPLICABLE EUROPEAN UNION DIRECTIVES 33

6.2. SCHEMATIC REFERENCES 35


CANBUS 35
RS232/RS485 35
PCIe & SIM SOCKET 36
DIGITAL I/O 36

6.3. REST API DOCUMENTATION 37


GET DEVICE ID 37
GET NETWORK STATUS 37

http://www.element14.com/gateway Page 5
SmartEdge Industrial IoT Gateway
User Guide

GET WIFI ACCESS POINT LISTING 37


SET WIFI CLIENT SSID & PSK 37
GET WIFI CLIENT CONNECTION STATUS 38
SET NEW IOTCONNECT CREDENTIALS 38
START IOTCONNECT SDK AND DISABLE REST API & WIFI AP 38
READ IOTCONNECT SDK CONFIGURATION 38
WRITE IOTCONNECT SDK CONFIGURATION 38
WRITE CELLULAR APN CONFIGURATION 38

6.4. ERRATA 39

6.5. TRADEMARKS & NOTICES 39


TRADEMARKS 39
NOTICES 39

http://www.element14.com/gateway Page 6
SmartEdge Industrial IoT Gateway
User Guide

1. INTRODUCTION / OVERVIEW
The Avnet SmartEdge Industrial IoT Gateway connects your sensors and other devices to the cloud. This allows you to
view status and control connected devices on a customizable web portal from any internet connected location.

1.1. IMPORTANT SAFETY INFORMATION


WARNING! DO NOT INSTALL DCIN PLUG INTO CANBUS PORT! THIS WILL DESTROY THE CANBUS DRIVER AND
TERMINATION RESISTOR!

A safety leaflet is included in the package and available at our product landing page. Please read it prior to powering on
your Gateway.

1.2. INTERNAL SYSTEM VIEW

http://www.element14.com/gateway Page 7
SmartEdge Industrial IoT Gateway
User Guide

1.3. PACKING LIST


 Avnet SmartEdge IIoT Gateway System

 Parts Kit:
 Extension ring: install to increase height of enclosure for Raspberry Pi HATs
 DIN rail mount with screws: install with flat head screws
 Flat head screws (2): use to attach DIN rail mount
 Wall mount screws (2): install into wood or metal, placed 97mm apart vertically
 Standoffs (4): install on top of existing standoffs when using extension ring
 3 Position terminal block, black (1): use for DC-IN connection
 3 Position terminal block, green (1): use for CANbus connection
 5 Position terminal block, green (3): use for Digital I/O and RS485 connection
 Pan head screws (2): use to secure a HAT onto the Gateway
 Quick Start Guide
 Safety Leaflet

http://www.element14.com/gateway Page 8
SmartEdge Industrial IoT Gateway
User Guide

2. HARDWARE DESCRIPTION
2.1. BLOCK DIAGRAM
GPIO GPIO RS232/ CAN
FCTRY
A B 485 Bus
RESET

MCU

GPIO
XTAL Serial CAN XTAL
RTC 14.7456M Controller Controller 16.00M

chip J8 GPIO 40pin TPM


J11
J15 DUAL
microUSB USB
WiFi 802.11 b/g/n
Bluetooth 4.2
2.4GHz band J17
USB Hub/ DUAL
Broadcom USB USB
Ethernet
BCM2837 Switch
XTAL
37.4M
J10
XTAL
10/100
19.2M
ENET

J12 USB Hub/ J18


1GB USB 2x4 Ethernet 10/100
eMMC
LPDDR2 ENET

Power
Regulation
mPCIe Expansion
uSIM
(USB only)

12VDC to
DVI/HDMI
24VDC
Input

2.2. SPECIFICATIONS

RASPBERRY PI 3 CORE
 64-Bit, Quad-core ARM A53 (Broadcom BCM2837) SoC
 Direct connection to enclosure heat sink for heat dissipation
 Maximum clock speed limited to 900MHz for enhanced thermal range
 1GB LPDDR2 SDRAM
 WiFi/BT, 2.4GHZ, 802.11bgn, BT 4.2

STORAGE MEDIUM
 8GB (minimum) eMMC onboard

INPUT POWER
 Voltage: 12-24VDC Input
 Power: 12W minimum, 18W recommended. Additional power may be needed for installed USB devices or expansion
cards (mPCIe or HATs). Be sure to verify the power supply high temperature derating for your operating
temperature range.

http://www.element14.com/gateway Page 9
SmartEdge Industrial IoT Gateway
User Guide

ENVIRONMENTAL
 Ambient Operating Temperature Range: -20°C to 70°C*, non-condensing humidity
 Storage Temperature Range: -40°C to 85°C, non-condensing humidity

*Note: depending on processor workload, CPU throttling may occur above 50C ambient

DIMENSIONING & MOUNTING


 Dimensions: 125mm W x 127mm D x 43mm H (55mm H with included expansion ring)
 Weight: 0.4kg
 Mounting: Desktop, Wall (sheet metal screws included), or DIN Rail (w/ included DIN rail bracket for 35mm "top hat")

FRONT PANEL LEDS


 Power / Activity LED
 Green indicates valid power
 Red flashing indicates disk activity by default, but configurable
 User LED
 Controlled from user code

HARDWARE WATCHDOG TIMER (WDT)


 Selectable timeout (1-255 seconds)

TRUSTED PLATFORM MODULE (TPM) & SECURE BOOT


 SLB9670 TCG 2.0 Trusted Platform Module
 Secure Boot Option when used with Avnet's Image

REAL-TIME CLOCK (RTC) WITH BATTERY BACKUP


 PCF8563 real-time clock
 BR1225 backup battery

http://www.element14.com/gateway Page 10
SmartEdge Industrial IoT Gateway
User Guide

2.3. EXTERNAL CONNECTIONS

DC-INPUT
 12VDC - 24VDC +/- 10%
 Recommended Wire: 18-24AWG Solid or 18-22AWG Stranded
 Install Protective Earth Wire

DC-IN Terminal Block Connections

Symbol Signal Name

Protective Earth GND

- 0V (GND)

+ 12-24VDC

DUAL ETHERNET PORTS


 10/100 Base-T
 Link / Activity LEDs

DUAL USB PORTS


 USB 2.0 High-Speed
 5V @ 1.2A Output, shared among all USB ports

DISPLAY CONNECTOR
 HDMI / DVI Compatible

ISOLATED RS-485 / RS-422 / RS232


 SC16IS740 UART (16C550 compatible)
 Jumper selection (see section 3.3)
 Term: Enable RS485 termination [installed by default, 120ohm termination]
 Shdn: Port Shutdown [not installed by default, port enabled]
 Slew: Slow Slew Rate [not installed by default, fast slew rate]
 Full: Full duplex (4-wire) [not installed by default, RS485 half duplex]
 RS232: Use RS232 signaling [not installed by default, RS485 mode]

RS-485/RS-422/RS-232 Terminal Block Connections

2-Wire RS485 4-Wire RS485


Signal RS-232
(half) (full) RS-422
- (n/c) RD (A) - CTS

+ (n/c) RD (B) + RXD

G GND GND GND

A DATA (A) - TD (A) - TXD

B DATA (B) + TD (B) + RTS

http://www.element14.com/gateway Page 11
SmartEdge Industrial IoT Gateway
User Guide

ISOLATED CANBUS
WARNING! DO NOT INSTALL DCIN PLUG INTO CANBUS PORT! THIS WILL DESTROY THE CANBUS DRIVER AND
TERMINATION RESISTOR!

 MCP2515 CAN Controller


 Recommended Cable: Shielded Twisted Pair, 120ohm impedance (Belden 3105A)
 Route multiple device connections as daisy chain, with termination only at endpoints
 Jumper selection for: CAN termination (see section 3.3)

CAN Terminal Block Connections

Signal CANbus signal

G GND

L CANL

H CANH

ISOLATED DIGITAL I/O


 Dual individually isolated blocks A & B, with each block having two (2) inputs and two (2) outputs
 Digital Outputs:
 Outputs are open drain
 High Level: up to 60V can be applied to Digital Output
 Low Level: 1.5V max @ 500mA
 Digital Inputs:
 Inputs have internal pull-down of 6.8kOhm.
 High Level: minimum of 5V @ 1mA at the input terminal, 60V @ 10mA max
 Low Level: maximum of 1V at the input terminal

Digital I/O Terminal Block Connections

Label Digital I/O Signal

Ox Output x

Ix Input x

G Ground

Oy Output y

Iy Input y

http://www.element14.com/gateway Page 12
SmartEdge Industrial IoT Gateway
User Guide

2.4. INTERNAL EXPANSION

USB HEADER
 2x4 header with two USB ports for optional internal USB devices
 Specially designed HATs can use USB

USB Header (J12)

Pin Signal Name Signal Name Pin

1 Vbus Vbus 2

3 USB1- USB2- 4

5 USB1+ USB2+ 6

7 GND GND 8

MINI-PCIE SLOT (J34)


 Full size mPCIe slot for USB devices only (PCIe bus is not connected)
 Supports USB, SIM, and WWAN LED for optional cellular modem
 MicroSIM socket for modem is located on the bottom side of the PCBA (remove the four corner standoffs and the
middle screw to lift out the PCBA)
 The included enclosure extension ring has two knockouts for SMA bulkhead antenna cables. The knockouts may
need to be removed using a drill/router bit.

Mini-PCIe Slot

http://www.element14.com/gateway Page 13
SmartEdge Industrial IoT Gateway
User Guide

HAT EXPANSION SLOT


 Support for standard Raspberry Pi HAT boards
 Both HAT and mPCIe card can be installed (check for any interference)
 Standard device-tree overlays can be used
 Enclosure expansion ring can increase the enclosure height
 Orient the expansion ring with the tab facing the PCB near the coin battery
 Install the four standoffs in the parts kit to the four locations shown in below picture
 HATs have access to full 40pin HAT I/O and alternate functions*

*NOTE: I2C1 Bus (GPIO2/GPIO3) is shared with onboard devices. I2C addresses: 0x33, 0x43, 0x44, 0x51 are reserved.

HAT Expansion card location

Install
additional
standoffs to
use expansion
ring (4 places)

http://www.element14.com/gateway Page 14
SmartEdge Industrial IoT Gateway
User Guide

Raspberry Pi HAT Expansion Connector (J8)

Pin Signal Name Signal Name Pin

1 3.3Vout 5Vout 2

3 I2C1_SDA (GPIO2) 5Vout 4

5 I2C1_SCL (GPIO3) GND 6

7 GPIO4 GPIO14 8

9 GND GPIO15 10

11 GPIO17 GPIO18 12

13 GPIO27 GND 14

15 GPIO22 GPIO23 16

17 3.3Vout GPIO24 18

19 GPIO10 GND 20

21 GPIO9 GPIO25 22

23 GPIO11 GPIO8 24

25 GND GPIO7 26

27 ID_SD (GPIO0) ID_SC (GPIO1) 28

29 GPIO5 GND 30

31 GPIO6 GPIO12 32

33 GPIO13 GND 34

35 GPIO19 GPIO16 36

37 GPIO26 GPIO20 38

39 GND GPIO21 40

http://www.element14.com/gateway Page 15
SmartEdge Industrial IoT Gateway
User Guide

3. USAGE
For basic operation, the Avnet SmartEdge IIoT Gateway requires a power connection along with internet access. A
mobile App can be used to connect the Gateway to the IoTConnect cloud solution, and create a new user account to
access it.

3.1. POWER INPUT


 An external power supply is required (not provided)
 Output rating: 12VDC to 24VDC (+/- 10%), 18W minimum, 24W recommended, LPS (Limited Power Source)
 Use 16-22AWG power supply wiring, stripped back 4-5mm, twisted & optionally tinned
 Find the black, 3 position terminal plug in the included parts kit
 Insert the prepared wires into the terminal plug, observing proper location
 An Earth GND wire is recommended

Signal DC Input
Earth GND
- 0V (GND)
+ 12-24VDC

CAUTION: Verify terminal block wiring is correct, tight, and with no bare wiring exposed

3.2. INTERFACES

USB 2.0
Two USB 2.0 High-Speed ports are available to accept devices and can provide 0.5A per port.

ETHERNET
Two 10/100 Ethernet peripherals are available. By default, both are configured the same and can accept connection to
the customers network. Some advanced topologies could be configured by the customer (bridged, router, etc).

RESET BUTTON
A pin hole reset button (labeled RST) is located next to the HDMI port. A paperclip can be used to activate it.

 Short press (less than 5 seconds) initiates a reboot


 Long press (between 5 and 30 seconds) re-enters Configuration state for IoTConnect Cloud Enrollment (section 3.4)
 Very long press (greater than 30 seconds) performs a Factory Reset

HDMI
An HDMI monitor can be used for console display. It should be connected at boot to enable the proper output.

ONBOARD DIGITAL I/O


The digital inputs and outputs are available as /sys/class/gpio/gpio200 thru gpio207. GPIO200/202/204/206 are
inputs and GPIO201/203/205/207 are outputs. See the schematic in the appendix for detailed connections. GPIOs
must be exported in your application to use them. If they are used in the SDK (IoTConnectSDK.conf) then they are
exported automatically.

http://www.element14.com/gateway Page 16
SmartEdge Industrial IoT Gateway
User Guide

ONBOARD RS232/485
You can use the onboard RS232/485 interface as a serial console, Modbus RTU interface, or other serial usages.

The RS-232/RS-485 port is configured by default for 2-wire RS-485 operation with termination enabled. On board
jumpers can reconfigure the port for full duplex or RS-232 signaling. See section 3.3 for jumper configuration and
connections.

The port is /dev/ttySC0. Refer to the schematics in the appendix for detailed connections.

CANBUS
The internal CANbus is available but not fully enabled by default in the image. It can be enabled by removing the
comments dealing with the can0 section in /etc/network/interfaces. Be sure to set the proper bitrate for your bus.
Utilities cansend and candump are included and the can0 device can be used by the network stacks.

A CAN termination jumper is enabled by default. Refer to section 3.3 for more information and refer to the schematics
in the Appendix.

INTERNAL MPCIE SLOT


This full size mPCIe slot is plug-n-play with USB based cards. PCIe cards are not supported. As with any USB device,
additional drivers may need to be installed.

INTERNAL RASPBERRY PI HAT EXPANSION SLOT


A standard Raspberry Pi HAT expansion slot of available, and can support most off-the-shelf HAT cards. The I2C1 bus is
enabled for onboard devices, so the HAT card(s) must not conflict with that usage.

http://www.element14.com/gateway Page 17
SmartEdge Industrial IoT Gateway
User Guide

3.3. FUNCTION SELECTION JUMPERS


The RS232/485, CANBUS, and WATCHDOG have internal jumpers to set bus signaling, termination, function, etc. The
lid must be removed to access these jumpers.

Jumper locations

RS232/485
settings

CANbus
Watchdog
termination
enable

Detail of J22 jumpers

http://www.element14.com/gateway Page 18
SmartEdge Industrial IoT Gateway
User Guide

RS232/485 JUMPER
 Term [default installed]: Install to enable RS422/485 bus termination (bus should be terminated on both ends only)
 Shdn: Install to shutdown the transceiver (disable)
 Slew: Install to use slow slew rate. This reduces EMI emissions but limits maximum bandwidth
 Full: Install to enable RS422/485 full duplex (4-wire)
 RS232: Install to use RS232 signaling instead of RS422/485 (Full & Term jumpers should be removed)

CANBUS JUMPER
 Term [default installed]: Install to enable CANbus termination (bus should be terminated on both ends only)

WATCHDOG JUMPER
 WDT: If this jumper is installed, the hardware watchdog timer is enabled at power-on. It must be disabled or toggled
before power-on timeout (approximately 4 minutes) else the system will reset.

http://www.element14.com/gateway Page 19
SmartEdge Industrial IoT Gateway
User Guide

3.4. IOTCONNECT CLOUD ENROLLMENT


A 30-day trial of IoTConnect cloud service is provided. Perform the following steps to enroll your Gateway.

After mobile app sign-up is complete, you can login to the IoTConnect Web Portal: https://avnet.iotconnect.io using
the same credentials as the mobile app.

For more information, see the IOTCONNECT DETAILS section of this document (Section 5).

ENROLLMENT STEPS
Follow this installation process to connect your Avnet SmartEdge IIoT Gateway to the cloud.

1. Connect your SmartEdge Gateway to your Ethernet network, if available, by using one of the two Ethernet Ports. If
using wireless, this will be set up in a later step using the mobile App.
2. Insert the correctly wired power supply plug to start the unit. IMPORTANT! Make sure to install into the 12-24VDC
power input shown above and not the CAN port!
3. Other hardware connections can optionally be made at this time. See section 0 for more information
4. Download the Avnet IoTConnect mobile application to register your SmartEdge Gateway with the IoT Connect
cloud. Refer to the web portal below for App Store links.

Web Portal: https://element14.com/gateway

5. Launch the App and enter your Login email 6. Sign Up for a new account by entering your
and password, or press Sign Up details

http://www.element14.com/gateway Page 20
SmartEdge Industrial IoT Gateway
User Guide

7. To add a device, tap lower right symbol , 8. Connect your mobile's WiFi to the
then tap "Add Device" + "IotGateway_xxxxxxxx". WiFi Password is
"IoTConnect" (case sensitive)

9. Optionally, connect your SmartEdge 10. After a minute, your device should appear in
Gateway to your local WiFi network the Device List

http://www.element14.com/gateway Page 21
SmartEdge Industrial IoT Gateway
User Guide

11. Tap your device to see the device details 12. Tap the sensor to view sensor readings

http://www.element14.com/gateway Page 22
SmartEdge Industrial IoT Gateway
User Guide

3.5. IMAGE UPDATE


The onboard eMMC storage device can be mounted as a drive on another PC. This will allow re-imaging the Gateway.

REQUIREMENTS
 Linux or Windows PC
 USB Type A plug to microUSB plug data cable (charger cables without data signals will not work)
 Special build of rpiboot utility

Location of eMMC update connection & jumper

eMMC Update
jumper and
connector location

EMMC MOUNTING STEPS


 With Gateway power removed, open lid on Gateway by removing the four (4) screws
 Ensure jumper is installed on J16 header
 Connect USB cable between the microUSB port on the Gateway and Type A port on the PC
 On Linux PC (recommended), install a special version of rpiboot to enable mass storage mode on the Gateway:
 sudo apt install git libusb-1.0-0-dev
 git clone https://github.com/Avnet/smartedge-iiot-gateway-custom.git
 cd smartedge-iiot-gateway-custom/rpiboot
 make
 sudo ./rpiboot_secure.sh
 On Windows PC, install a special version of rpiboot to enable mass storage mode on the Gateway:
 Download Windows installer here: https://github.com/Avnet/smartedge-iiot-gateway-
custom/raw/master/rpiboot/win32/rpiboot_setup.exe
 Run the rpiboot_setup.exe, note that you may have to click through a few Windows warnings.
 The installer adds USB drivers for the Gateway, along with the rpiboot.exe executable.
 Once installation is complete, run the rpiboot.exe
 After all above is complete, connect power to the Gateway, then rpiboot output should show:

Waiting for BCM2835/6/7


Sending bootcode.bin
Successful read 4 bytes
Waiting for BCM2835/6/7
Second stage boot server

http://www.element14.com/gateway Page 23
SmartEdge Industrial IoT Gateway
User Guide

File read: start.elf


Second stage boot server done
 The eMMC should now show up as a drive on the PC

WRITING A NEW IMAGE OR SAVING EXISTING


Once the eMMC is mounted as a drive, individual files can be accessed or the entire drive contents can be copied or
replaced. While it is possible to use Linux "dd" command to read/write a new image, a safer and more user friendly
tool is recommended (example, balenaEtcher). By default, this tool verifies the image was written correctly, which is
very useful to identify possible cable/port issues.

 Download image
 Standard Avnet SmartEdge IIoT Gateway images are available through the http://www.element14.com/gateway
landing page. Click on the Software Image link under Resources.
 Standard Raspberry Pi images won't work without some additional files in the /boot partition (refer to section 4.4)
 Write the image to the Gateway using an image writing tool. Important: if not using balenaEtcher, you must unzip
the image prior to writing.

3.6. SYSTEM CUSTOMIZATION


The SmartEdge IIoT Gateway system can be extended with additional hardware or software as needed for your
application.

HARDWARE CUSTOMIZATION
The standard Pi HAT expansion connector opens up a wide variety of ready-made hardware solutions. Custom HATs
can be developed specifically for your application. In many cases, drivers are already available and the HAT can be
plug-n-play. Other HATs may require adding a dtoverlay in the /boot/config.txt file. Mechanically, you can use the
included expansion ring, and customize it for the installed HAT(s). The 3D files can be provided to create your own
expansion ring.

There's a USB header internally that can be used. If designing a custom HAT, a small extension of the HAT board outline
can include this USB header to add USB devices on the HAT.

A mPCIe slot is available to add cards that use the USB bus. This is mostly for cellular modems, but other cards are
possible. Custom cards can be designed if only 3.3V power and USB interface are used.

SOFTWARE CUSTOMIZATION
Because the Gateway is based on the popular Raspberry Pi computer, there are several O/S and Linux distributions
available. Due to differences between the SmartEdge Gateway and Raspberry Pi, standard Pi images these cannot run
without modification. In most cases, the changes are small and straightforward. See section 4.4 for details.

The kernel source is available to customize as needed from our github site (see section 4.1).

There are a large number of software packages available that can be installed using the Ubuntu "apt" mechanism.

There is a battery backed RTC on the gateway. For systems that do not have internet connectivity (I.e. closed system)
then this can be set then enabled with a few standard Linux commands to keep the date/time even if the power fails.
Normally this system is on the internet and the correct time information is provided using network time keeping
protocols.

http://www.element14.com/gateway Page 24
SmartEdge Industrial IoT Gateway
User Guide

There is a PCIe connector on board and accepts most PCIe USB devices and is primarily used for cellular modem
connections. Note: If you decide to use a cellular modem there will be customization needed control data calls.
Standard Linux tools that are available can be used for dialer customizations.

The gateway has the NodeRed project baseline installed on the system. By default the service is not started. Additional
NodeRed modules will be provided for the device, as they are currently being developed by Avnet. For more
information on NodeRed and how to use it, refer to the following link: https://nodered.org/docs/getting-
started/raspberrypi

The ssh terminal service is disabled by default. You can use the raspi-config tool to enable it. The setting is under the
interface options section. Also add an empty file called “ssh” to the /boot directory, then reboot.

The raspi-gpio tool can be used to see the default GPIO configuration for the gateway. If custom hardware is used on
the HAT connector you should use the device tree overlay to setup and HAT connection GPIO. Then use the raspi-gpio
tool to ensure the GPIO’s are configured correctly.

http://www.element14.com/gateway Page 25
SmartEdge Industrial IoT Gateway
User Guide

4. SOFTWARE CONFIGURATION

4.1. AVNET IMAGE


The unit comes pre-loaded with a special version of Raspbian. Due to differences in the Avnet SmartEdge IIoT Gateway
compared with a standard Raspberry Pi, standard Raspbian images won't boot without modification. See section 4.4
for details.

LOCAL ACCESS & CONFIGURATION


Connect a USB keyboard and HDMI monitor to the Gateway, and power-on. NOTE: If connecting an HDMI monitor after
power-on, the resolution may not be correct or the output may not be enabled.

Default login: avnet Password: avnet

From this point, you have Linux shell access. You can install additional software components (using apt), control
startup devices (using systemctl), modify the IoTConnect configuration, view logging (files in /var/log), etc.

INCLUDED SOFTWARE
 Linux based on Raspbian, with Avnet SmartEdge IIoT Gateway platform specific support added
 Linux kernel source github: https://github.com/Avnet/smartedge-iiot-gateway
 Avnet image releases: http://avnet.me/smartedge-iiot-gateway-releases
 Custom U-Boot with support for TPM 2.0 trusted boot
 U-Boot source github: https://github.com/Avnet/smartedge-iiot-gateway-uboot
 IoTConnect cloud solution provided (30-day trial included)
 Custom files github: https://github.com/Avnet/smartedge-iiot-gateway-custom

http://www.element14.com/gateway Page 26
SmartEdge Industrial IoT Gateway
User Guide

4.2. SECURE BOOT


 The Gateway has an optional one-time "switch" to enable a secure boot feature
 Once enabled, the processor will ensure only Avnet signed boot files are executed by the processor. Other files will
cause the boot process to halt without explanation (unit will appear dead!)
 Important! After enabling secure boot, only Avnet signed images can be used on the Gateway. All other images will
not boot!
 Please contact [email protected] for additional information on the secure boot feature.

4.3. MISCELLANEOUS
High compatibility with standard Raspbian utilities such as “raspi-config, and raspi-gpio”, etc, make it easy to transition
from a standard Raspberry Pi to the Avnet SmartEdge IIoT Gateway.

TRUSTED PLATFORM MODULE


 Various TPM 2.0 compliant utilities can be found in /usr/local/bin.
 U-Boot starts first instead of the kernel, and launches kernel after filling out TPM 2.0 PCR 0 value. If secure boot is
enabled, this provides a core root of trust for measurement (CRTM) implementation.
 TPM 2.0 PCR 0 element contains the value of the kernel (/boot/zImage) that is calculated from u-boot.

DESKTOP GUI
 To conserve space, the desktop GUI is not installed on the standard image
 To install, perform the following steps with a network connection:

# Ensure Avnet /boot files don't change with upgrade


sudo apt-mark hold raspberrypi-bootloader
sudo apt-mark hold raspberrypi-kernel
sudo apt-mark hold raspberrypi-sys-mods

# Get latest updates


sudo apt update
sudo apt upgrade
sudo apt dist-upgrade

# Install the desktop GUI


sudo apt install --no-install-recommends xserver-xorg xinit
sudo apt install raspberrypi-ui-mods

# Install web browser (optional)


sudo apt install chromium-browser

# Remove downloaded apt packages from above steps (no longer needed)
sudo apt clean

# Change boot setting to enable desktop boot


sudo raspi-config # Use menus to enable desktop boot

http://www.element14.com/gateway Page 27
SmartEdge Industrial IoT Gateway
User Guide

OTHER SOFTWARE
 For a list of preinstall packages, run "dpkg –l" for current Debian installed packages
 For Python 2.7/3.x installed packages run 'pip list" and "pip3 list".
 Custom utilities are provided for system control and are found in /opt/avnet-iot/ or /usr/bin/
 NodeRed base line installation, not started. Review online NodeRed documentation for Raspberry Pi.
 Minicom and Tio are included as terminal programs.

REAL-TIME CLOCK (RTC)


The onboard real-time clock can restore the system clock on boot-up if a network connection is not available. When a
network connection is available, the system clock and real-time clock are periodically synchronized to a NTP time
server.

RESET BUTTON
The gateway includes a small hole next to the HDMI connector for reset:
 Short press and release performs reboot
 Hold reset for ~10 seconds then release to re-enter Configuration mode. This enables WiFi AP mode and the REST
API to allow configuration with the mobile App. The top LED will blink green-off-red-off to indicate this mode.
 Hold reset for ~45 seconds then release to perform a Factory Reset. This will place the unit back into the out-of-
box configuration state.

4.4. DIFFERENCES FROM STANDARD RASPBERRY PI


It is important to understand these differences if trying to build your own kernel for the Gateway.

CUSTOM BOARD TYPE


The addition of eMMC required creation of a new Pi board type called "custom". The Avnet SmartEdge IIoT Gateway
uses this type. In response, the Raspberry Pi boot firmware searches for "/boot/bcm2710-rpi-custom.dtb" and
"/boot/dt-blob.bin" files, and if not present or correct, the system may not boot. Source for these two files are
located here: https://github.com/Avnet/smartedge-iiot-gateway/tree/master/arch/arm/boot/dts

You should check for other possible changes to our device tree source files based on your target kernel. Our kernel is
based on Linux 4.14.79. Review the history of bcm2710-rpi-3-b.dts file to see if changes may be required to the
bcm2710-rpi-custom.dts file. Then your kernel needs rebuilt (make sure the bcm2710-rpi-custom.dts and dt-blob.dts
files are added to the build process).

WARNING: Because of the above differences, performing any standard Raspberry Pi update that modifies the kernel or
boot files will likely prevent the system from booting. This includes writing a standard Raspbian image to the Gateway
or performing "apt-get upgrade". If this happens, you will have to follow the image update instructions located
elsewhere in this guide (Section 3.5) to fix the /boot files or re-image the system. To prevent Raspbian updates from
automatically updating your kernel and firmware files (and bricking your Gateway), execute the following commands:

sudo apt-mark hold raspberrypi-bootloader


sudo apt-mark hold raspberrypi-kernel
sudo apt-mark hold raspberrypi-sys-mods

eMMC UPDATE PROCEDURE


Since the Avnet SmartEdge IIoT Gateway contains an eMMC, a special procedure is required to rewrite it. See section
3.5 for details on updating the onboard eMMC.

http://www.element14.com/gateway Page 28
SmartEdge Industrial IoT Gateway
User Guide

ON BOARD PERIPHERALS
The Avnet SmartEdge IIoT Gateway has several onboard peripherals that a standard Pi does not. Many of these
peripherals connect to the SPI2 bus on the higher GPIOs, freeing up the GPIOs on the HAT for usage.

Some of these peripherals use a customized driver:


 GPIO expansion: gpio_fxl6408
 UART: sc16is7xx
 CAN: mcp251x
 Cellular: option, usb_wwan, qcserial, qmi_wwan

These driver changes are available from our github repo for the kernel (see section 4.1)

http://www.element14.com/gateway Page 29
SmartEdge Industrial IoT Gateway
User Guide

5. IOTCONNECT DETAILS
5.1. USAGE
After first enrolling your Gateway using the mobile App (see section 3.4), you can view and control your device(s)
through the web portal (avnet.iotconnect.io). Once logged in to the web portal, you are presented with a "Dashboard".
IoTConnect documentation is available under the Resource tab. Below are some of the capabilities. Note that some
features require admin level access.

VIEW SENSORS
Once logged in, your device(s) can be found on Device tab on the left side. Clicking on the device tab will show a list of
the devices that are configured for the logged in user.

More advanced options like OTA updates and Command Setup require Administrator rights. For many users, the device
may need to transition from the 30-day trial period to your own paid account before Administrator rights are available.

OTA UPDATES
An update package can be delivered to the Gateway(s) from the IoTConnect Cloud. The update package is a specially
formatted tarball, consisting of a script that gets executed on the Gateway.

To create an update:
 Using a Linux PC, create a directory named "updates"
 Create a file in that directory called install.sh with instructions to perform the update
 Include any other supporting files in that directory
 Compress the "updates" directory contents into a .tar.gz file
 Rename the .tar.gz file to .txt
 Setup the web portal for the OTA firmware update and point the file for OTA to your .txt file
 Test the update thoroughly before sending to production systems
 Issue the OTA update to your device(s)

5.2. CONFIGURING THE IOTCONNECT SDK


As an initial step, you should configure your Gateway using the mobile App "Avnet IoTConnect" for iOS and Android.
See section 3.4 for configuration steps. One sensor, CpuTemperature, is enabled by default and reported to the cloud.

DEFAULT WIFI ACCESS POINT CREDENTIALS


 WiFi AP SSID: IotGateway_xxxxxxxx”
 WiFi AP Passkey: IoTConnect

MODIFY LOCAL CONFIGURATION


 Connect a HDMI monitor and USB keyboard to the Gateway, then power on. Login with the default credentials--
user login: avnet, Password: avnet
 The IoTConnect SDK is located at "/opt/avnet-iot/IoTConnect/sample" or
"/usr/bin/IoTConnectSDK_Py2.7/Testing/sample"
 You can modify the IoTConnectSDK.conf and user_functions.py files in the SDK for your sensors
 Verify or add your IoTConnect mobile App created username and password to the IoTConnectSDK.conf file
 The IoTConnect.conf file contains sections for CloudSDKConfiguration, CloudSystemControl, and
CloudSDKDefaultObject<xxx> entries

http://www.element14.com/gateway Page 30
SmartEdge Industrial IoT Gateway
User Guide

 For the CloudSDKDefault options, you should add the section names [CloudSDKDefaultObject<xxx>] sequentially
numbered and update the DefaultObjectCount in the CloudSystemControl section accordingly

EXAMPLE
You can add/modify the python code in user_functions.py. The user_callbackMessage(msg) receives COMMANDS from
the cloud and user_Initialize() is called when the SDK starts to contain any custom initialization code. Both of these
functions must be present.

 For a simple test, add a section to the IoTConnectSDK.conf file:

[CloudSDKDefaultObject2]
# Predefined objects can go here. NUMBER/STRING/OBJECT
Value=NUMBER
Name=TestUserFunction
UsePythonInterface=ThisIsMyFunction
 Then uncomment the function ThisIsMyFunction() in user_functions.py
 Restart the SDK (either reboot, or sudo systemctl restart iotconnectservice)
 The new information you just added should show up on the cloud

5.3. SYSTEM OPERATIONS

CONFIGURATION MODE
On initial boot, the system comes up in configuration mode. A REST API runs, and the Gateway's WiFi is configured for
Access Point mode. From a mobile device or other WiFi connected PC, you can connect directly to the Gateway's WiFi
(SSID = "IotGateway <sn/cpuid>"). You can determine your Gateway's S/N from the HDMI monitor output.

If you have trouble with the mobile App configuration, and no longer have the WiFi AP as an option, you may have to re-
enter configuration mode on the Gateway. To do this, press and hold the factory reset button for 10 seconds. This will
restart and re-enable the WiFi AP mode.

NORMAL MODE
Once configured the Gateway enters normal mode. The WiFi AP and REST API are disabled, IoTConnect API is running.

TOP LED STATUS INDICATORS


 Configuration Mode: green-off-red-off
 Normal Mode with cloud connection: green-off-green-off
 Shutdown/Reboot/Halt: red fast blink

5.4. WHAT’S NEXT


The IoTConnect SDK can be customized for your application. Additional sensors and controls can be added for the
cloud connection. See the custom github (Sec 4.1) for information.

5.5. PROVISIONING MULTIPLE DEVICES


Multiple gateways can be provisioned without the Mobile Application. It is best to use the Ethernet connection to the
Gateway for this. See section 6.3 for the supported REST API.

http://www.element14.com/gateway Page 31
SmartEdge Industrial IoT Gateway
User Guide

STEPS REQUIRED
 Find the IP addresses for the connected Gateway(s)
 Read /DeviceID to get the device's serial number. You can use this to select the files needed for that device. If you
are unsure just issue the REST command to all IP addresses and if it responds then proceed with that Device ID.
 Get the /WiFiIWList of in range WiFi access points. Then put /WiFiClientSSID_PSK to set the new
wpa_supplicant.conf file.
 Issue the /IOTGetIOTConnectSDK command to get the current SDK configuration file. Modify the SDK configuration
file, then use the /IOTSetIOTConnectSDK to replace it.
 Issue the /CloudAttach command to setup the WiFi connection, if configured. It will also start the SDK.

http://www.element14.com/gateway Page 32
SmartEdge Industrial IoT Gateway
User Guide

6. REFERENCES
6.1. COMPLIANCE

REGULATORY COMPLIANCE AND MARKINGS


 FCC Class B Compliance (USA)
 IC Class B Compliance (Canada)
 CE Class B Compliance (Europe)
 RCM (Australia / New Zealand)
 WPC (India)
 SRRC (China)

SIMPLIFIED EU DECLARATION OF CONFORMITY


Hereby, Avnet Inc., declares that SmartEdge IIoT Gateway is in compliance with Directive 2014/53/EU.
The full text of the EU declaration of conformity is available at the following internet address:
element14.com/gateway

Frequency Range RF Output Power


2402MHz - 2480MHz 0.0051 Watts
2412MHz - 2462MHz 0.2449 Watts

SUPPLIER'S DECLARATION OF CONFORMITY


47 CFR § 2.1077 Compliance Information

Unique Identifier
Trade Name: SmartEdge IIoT Gateway
Model No.: AVTSE-RPI-IIOTG

Responsible Party – U.S. Contact Information


Avnet, Inc.
2211 South 47th Street; Phoenix, AZ USA 85034
Phone: 480-643-2000

FCC COMPLIANCE STATEMENT


This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This
device may not cause harmful interference, and (2) this device must accept any interference received, including
interference that may cause undesired operation.

APPLICABLE EUROPEAN UNION DIRECTIVES


Radio Equipment Directive (RED) - 2014/53/EU

Article 3.1 (a) protection of health and safety


 EN 62479:2010: Assessment of the compliance of low power electronic and electrical equipment with the basic
restrictions related to human exposure to electromagnetic fields (10 MHz to 300 GHz)
 EN 62311:2008: Assessment of electronic and electrical equipment related to human exposure restrictions for
electromagnetic fields (0 Hz - 300 GHz)
 EN 60950-1:2006+A11:2009+A1:2010+A12:2011+A2:2013: Information technology equipment. Safety. General
requirements

http://www.element14.com/gateway Page 33
SmartEdge Industrial IoT Gateway
User Guide

Article 3.1 (b) electromagnetic compatibility


 EN 301 489-1 V2.1.1: electromagnetic compatibility (EMC) standard for radio equipment and services; Part 1:
Common technical requirements
 EN 301 489-17 V3.1.1: electromagnetic compatibility (EMC) standard for radio equipment and services; Part 17:
Specific conditions for broadband data transmission systems
 Test methods for emissions:
 EN 55032:2015 Class B: Conducted emissions at mains terminals (150 kHz - 30 MHz)
 EN 55032:2015 Class B: Conducted emissions at telecommunications port (150 kHz - 30 MHz)
 EN 55032:2015 Class B: Radiated emissions (30 MHz - 1 GHz)
 EN 55032:2015 Class B: Radiated emissions (above 1 GHz)
 EN 61000-3-2:2014 Class A: Harmonic current emission
 EN 61000-3-3:2013 Clause 5: Voltage fluctuations and flicker
 Test methods for immunity:
 EN 61000-4-2:2009 4kV Contact 8kV Air: Electrostatic discharge
 EN 61000-4-4:2012 1kV 5/50ns Tr/Td 5kHz repetition frequency: Electrical fast transients/burst at power
port
 EN 61000-4-4:2012 0.5kV 5/5ns Tr/Td 5kHz repetition frequency: Electrical fast transients/burst at signal
port
 EN 61000-4-5:2014+A1:2017 1.2/50µs Tr/Td 1kV line-to-line 2kV line-to-ground: Surge at power port
 EN 61000-4-6:2014 3Vrms (emf) 80% 1kHz AM: Conducted immunity at power port (150 kHz - 80 MHz)
 EN 61000-4-6:2014 3Vrms (emf) 80% 1kHz AM: Conducted immunity at signal port (150 kHz - 80 MHz)
 EN 61000-4-11:2014+A1:2017: Voltage dips and interruptions
 EN 61000-4-3:2006+A1:2008+A2:2010 3V/m 80% 1kHz AM: Radiated Immunity (80 MHz - 6 GHz)

Article 3.2 efficient use of radio spectrum


 EN 300 328 V2.1.1: Wideband transmission systems; Data transmission equipment operating in the 2,4 GHz ISM
band and using wide band modulation techniques

Restriction of the use of certain Hazardous Substances directive (RoHS) - 2011/65/EU and 2015/863/EU

This product meets the requirements of Directive 2011/65/EU and 2015/863/EU for the restriction of the use of
certain hazardous substances in electrical and electronic equipment.

Applied standard:
 EN IEC 63000:2018: Technical document for the assessment of electrical and electronic products with respect
to the restriction of hazardous substances.

Recycling and disposal of Waste Electrical and Electronic Equipment (WEEE) - 2012/19/EU

Correct disposal of the product


 This marking indicates that this product should not be disposed with other household wastes throughout the
EU.
 To prevent possible harm to the environment or human health from uncontrolled waste disposal, recycle it
responsibly to promote the sustainable reuse of material resources.
 To return your used device, please use the return and collection systems or contact the retailer where the
product was purchased. They can take this product for environmentally safe recycling.

http://www.element14.com/gateway Page 34
SmartEdge Industrial IoT Gateway
User Guide

6.2. SCHEMATIC REFERENCES

CANBUS

RS232/RS485

http://www.element14.com/gateway Page 35
SmartEdge Industrial IoT Gateway
User Guide

PCIe & SIM SOCKET

DIGITAL I/O

http://www.element14.com/gateway Page 36
6.3. REST API DOCUMENTATION
When the Gateway is in configuration mode, it exposes a network API used by the mobile App to set up the Gateway.
Instead of the mobile App, this API can be used to configure multiple Gateways directly.

If connected over WiFi AP, the default <ipaddress> is 192.168.2.1

If connected over Ethernet, the <ipaddress> is set by your network DHCP server

All commands assume header: "Content-Type: application/json"

GET DEVICE ID
GET http://<ipaddress>:8080/DeviceId

Possible Response:
{
"DeviceID": "<deviceid>"
}

GET NETWORK STATUS


GET http://<ipaddress>:8080/NetworkStatus

Possible Response:
{
"IsConnected": {true,false}
}

GET WIFI ACCESS POINT LISTING


GET http://<ipaddress>:8080/WiFiAccessPointList

Possible Response:
{
"AccessPointList": [
{
"SSID": "value",
"SignalStrength": "value"
},
]
}

SET WIFI CLIENT SSID & PSK


PUT '{"<myssid>":"<mypsk>"}'
http://<ipaddress>:8080/WiFiClientSSID_PSK

Possible Response:
{
"Response": {1,0}
}
SmartEdge Industrial IoT Gateway
User Guide

GET WIFI CLIENT CONNECTION STATUS


GET http://<ipaddress>:8080/WiFiClientConnectionStatus

Possible Response:
{
"WiFi client IP": "<wifi_ipaddress, netmask, etc>"}
}

SET NEW IOTCONNECT CREDENTIALS


PUT
'{"cpid":"<myCpid123dddd4567>","username":"<[email protected]>","password":"<myp@$
$>"}'
http://<ipaddress>:8080/IOTNewCPID
Possible Response:
{
"Response": {1,-1}
}

START IOTCONNECT SDK AND DISABLE REST API & WIFI AP


PUT '{""}'
http://<ipaddress>:8080/CloudAttach
Possible Response:
{
"Response": {1,0}
}

READ IOTCONNECT SDK CONFIGURATION


GET http://<ipaddress>:8080/IOTGetIOTConnectSDKConf
Possible Response:
{
"IOTGetIOTConnectSDKConf": "<contents of file>"
}

WRITE IOTCONNECT SDK CONFIGURATION


PUT '<contents of file>'
http://<ipaddress>:8080/IOTSetIOTConnectConf
Possible Response:
{
"IOTConnectSDKConf": {1,0}
}

WRITE CELLULAR APN CONFIGURATION


PUT '<contents of file>'
http://<ipaddress>:8080/IOTSetAPNConf
Possible Response:
{
"IOTSetAPNConf": {1,0}
}

http://www.element14.com/gateway Page 38
SmartEdge Industrial IoT Gateway
User Guide

6.4. ERRATA
Please see the github repositories (section 4.1) for updates, bug list, etc.

6.5. TRADEMARKS & NOTICES

TRADEMARKS
Raspberry Pi is a trademark of the Raspberry Pi Foundation.

NOTICES
The provided software and firmware are subject to the following disclaimer.

DISCLAIMER. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

http://www.element14.com/gateway Page 39

You might also like