Synapse SNAPconnect E12 User manual

USER GUIDE
SNAPconnect E12
SNAP Enabled Gateway
©2008-2017 Synapse Wireless, All Rights Reserved. All Synapse products are
patent pending. Synapse , the Synapse logo, SNAP, and Portal are all registered trademarks
of Synapse Wireless, Inc.
Doc# 116-081614-030-B001
6723 Odyssey Drive // Huntsville, AL 35806 // [phone] // Synapse-Wireless.com

Disclaimers
Information contained in this manual is provided in connection with Synapse Wireless products and services and is intended solely to assist its customers.
Synapse reserves the right to make changes at any time and without notice. Synapse assumes no liability whatsoever for the contents of this manual or the
redistribution as permitted by the foregoing limited license. The terms and conditions governing the sale or use of Synapse products is expressly contained in the
terms and conditions for the sale of those respective products.
Synapse retains the right to make changes to any product specification at any time without notice or liability to prior users, contributors, or recipients of
redistributed versions of this manual. Errata should be checked on any product referenced.
Synapse and the Synapse logo are registered trademarks of Synapse Wireless. All other trademarks are the property of their owners.
For further information on any Synapse product or service, contact us at:
Synapse Wireless, Inc.
6723 Odyssey Drive
Huntsville, Alabama 35806
256-852-7888
877-982-7888
256-924-7398 (fax)
www.synapse-wireless.com
License governing any code samples presented in this Manual
Redistribution of code and use in source and binary forms, with or without modification, are permitted provided that it retains the copyright notice, operates only
on SNAP®networks, and the paragraphs below in the documentation and/or other materials are provided with the distribution:
Copyright 2008-2016, Synapse Wireless Inc., All rights Reserved.
Neither the name of Synapse nor the names of contributors may be used to endorse or promote products derived from this software without specific prior written
permission.
This software is provided “AS IS,” without a warranty of any kind. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING
ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED. SYNAPSE AND
ITS LICENSORS SHALL NOT BE LIABLE FOR ANY DAMAGES SUFFERED BY LICENSEE AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THIS SOFTWARE
OR ITS DERIVATIVES. IN NO EVENT WILL SYNAPSE OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR DIRECT, INDIRECT,
SPECIAL, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF
THE USE OF OR INABILITY TO USE THIS SOFTWARE, EVEN IF SYNAPSE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Table of Contents
Overview 1
The Device 2
Getting Started 3
Powering the E12 3
Establishing a Serial Connection 3
Mounting the E12 8
E12 Software Specifics 9
Passwords and root Access 9
E12-Specific Software Packages 9
E12 Physical Interfaces 11
E12 LEDs 11
The SNAPModule-Controlled LED 11
The E12 Button 12
Working With the Gateway's SNAPModule 13
Waking the SNAPModule 13
Resetting the SNAPModule 14
Restoring Functionality to an Unresponsive SNAPModule 14
Upgrading the SNAP Module Firmware 15
Accessing the MicroSD Slot 17
Common Linux Operations 18
Editing Linux Files 18
Making Your Software Run at Startup 18
Running a Script to Completion 18
Starting a Service 19
Setting Your E12’s Clock 20
Resetting a Lost User Password 20
Mounting an External Drive 21
Extending the E12 with USB Accessories 22
USB Power 22
Connecting to an Additional SNAP Device 22
Using usb_modeswitch 23
Factory Restore / Re-Flashing Your E12 24
Restoring from a MicroSD Card 24
Specifications and Installation 25
Specifications 25
E12 Dimensions 26

Troubleshooting Common Problems 27
The Ethernet port does not work or eth0 does not appear in ifconfig 27
SNAPconnect is not working 27
I cannot SSH into my E12 27
Regulatory Information and Certifications 28

Overview
IoT solutions demand reliable and flexible wireless connectivity at scale. SNAPconnect gateways are the interface
between your SNAP mesh networks and the rest of the world. Whether performing data aggregation to quickly
make real-time decisions, merging multiple IoT data streams, or connecting to on-site servers or the cloud,
SNAPconnect gateways provide the connectivity your network needs
915MHz and 2.4GHz Flexibility
IoTapplications exist in many environments. That's why the SNAPconnect E12 Gateway is available in 915MHz and
2.4GHz versions. Both versions are powered by SNAP: the Things Platform, so you can switch between frequencies
without having to redesign your application. It's even possible to have SNAPnetworks of both frequencies in the
same environment, sending information to the same cloud repository.
Powered by Ubuntu - Easy to Customize
The SNAPconnect E12 Gateway is an embedded Ubuntu Linux computer with the flexibility to add custom or 3rd
party software as needed for local databases, IoT platform clients, or other elements. It bridges SNAP edge
networks over Ethernet or optional USB connectivity devices such as cell modems, Bluetooth, or Wi-Fi adapters.
Start Quickly with Included Tools
The E12 is ready-made to host SNAP Thing Services – a suite of software tools that unite IoT devices and
applications via REST and MQTT for tasks such as data collection, device updates, and network management.
Custom programs can be created with the help of SNAPconnect software libraries making communications with IoT
devices in edge networks easy, even in challenging environments.
Protect your Deployment
SNAPconnect gateways emphasize security using AES-128 to encrypt edge network traffic, and standard Linux
security tools to secure the backhaul network. SNAP Thing Services utilizes tools like TLS and HTTPS to secure
outbound interfaces.
1

2SNAPconnect E12 User Guide — 116-081614-030-B001
The Device
The images below show an E12 gateway with all features marked:
All E12s include a SNAP-powered module, and will come with an antenna for the module's connection labeled with
the Synapse S on the E12's case.

Getting Started
Adding an E12 gateway to your SNAP network is easy, but as with adding any computer to any network, if you don’t
follow the right steps, you’ll end up in the wrong place. These directions provide the steps for connecting to your E12
from either a Windows PC or a Linux PC, which we will refer to as your host PC. These instructions assume that you
have some familiarity with your host operating system. See your OS help files if you need assistance installing
software or navigating applications.
To get started with the E12, you'll first need to apply power.
Powering the E12
The E12 is powered through the power terminal
blocks.
Use only UL 60950-1 2nd Edition AM1+AM2
certified LPS power supplies, rated for relative
environmental conditions suitable to your use
location with an output of 7-36VDC, 1500mA Max.
NOTE: Some power supply vendors mark the positive “+” lead with a white stripe.
NOTE: The E12 cannot be powered over the USB SERIAL port.
NOTE: If the E12 is installed into an end product, wiring should be done in accordance with the relevant product
safety standard of the end product.
Establishing a Serial Connection
Next you'll need to establish a USBserial connection.
To establish a serial connection to the E12 and update the software:
1. Ensure that you have terminal emulation software installed on your host PC. Popular software for this purpose
includes Tera Term, PuTTY, minicom, screen, or any of many others.
2. Use a standard USB to micro-USB cable to connect the micro-USB port on your E12 to an open USB port on
your host PC .
3. Apply power to the E12.
3

4SNAPconnect E12 User Guide — 116-081614-030-B001
NOTE: During the upcoming step 4, if you find that your host PC cannot connect to the E12 over the USB
connection, you may need to install the FTDIUSBto UART VCP drivers, available from http://www.ftdichip.com

4. Find the serial port that your host PC has assigned to the E12 (over that USB connection)
To find the serial port on a Windows PC:
a. Check under “Ports” in the Device Manager.
b. Look for USBSerial Port (COMxx) where the xx will indicate the serial port assigned (e.g., COM3, or
COM88).
c. Connect using your preferred terminal application. Example screenshots of connecting via PuTTY and
TeraTerm are provided below:
To find the serial port on a Linux PC:
a. Before plugging in the E12’s USB cable, check for ttyUSB connections in the /dev directory.
5

6SNAPconnect E12 User Guide — 116-081614-030-B001
b. Plug in the E12 and look for a new ttyUSBx, where x indicates the USB connection assigned (e.g., ttyUSB0).
If you had any other USB-serial devices plugged in, you may see more than just /dev/ttyUSB0, which is
why you should check for the presence of these devices first.
c. You can use any of a number of serial terminal programs to connect to your serial port. Linux versions of
PuTTy and TeraTerm exist and work the same way shown in the Windows examples above (other than
the name of the port to which you are connecting. additionally, utilities such as cu or screen are available
as well:
Using cu:
To connect: sudo cu –l /dev/ttyUSB0 –s 115200
To disconnect, at the command line type ~. (tilde, period) and then press Enter.
Using screen:
To connect: sudo screen /dev/ttyUSB0 115200
To disconnect, press Ctrl-A, and then \(backslash).
5. Using your terminal emulator, connect to the E12 using the following serial port settings:
l115200 baud
l8 bits
lNo parity
l1 stop bit
lNo flow control
6. Use your terminal emulation window to log in to the E12 gateway.
Username: snap
Password: synapse
NOTE: You must change your password the first time you log in. This prevents you from installing an E12
gateway with the default password set, which is pretty much the definition of a bad security idea. Ubuntu
enforces some restrictions on what constitutes a valid password, and these instructions are further defined
in the Ubuntu documentation available at https://help.ubuntu.com/.
7. Connect your E12 to the internet.
The easiest way to do this is to make a wired connection to a host (i.e., router) that supports DHCP. (Most do,
by default.) If you wish to configure your device for a static IP address, you may do so via the serial connection
before making your internet connection.
8. Update the Python Development Libraries
Before starting work with the E12, you'll want to make sure you have the latest versions of the software
installed on the unit. The E12 makes use of Python Development Libraries that are sometimes updated to add

new functionality and correct bugs. You can update the version installed on your unit by running the
command:
sudo apt-get install python-dev
NOTE: Remember that Ubuntu Linux does not, by default, enable root as a user. The sudo command
temporarily escalates your privileges to su (super user), so the E12 will prompt you for your password.
NOTE: If you get a "Requirement already satisfied" message from one of the updates, don't be alarmed. It
just means you already have the latest version.
9. Set the Clock
First, you should specify the timezone in which your device will reside. An easy way to do this is to use tzdata,
which allows you to select the general region, and then select the specific zone for your location. You can run it
with the command:
Sudo dpkg-reconfigure tzdata
Next, and only if the E12’s date is not set (i.e. it is not connected to a network so it does not set the date from an
NTP server, and the hardware clock has never been set), set the date manually.
The following example sets the date to April 20, 2016, at 12:30:59 p.m.
sudo date --set “2016-04-30 12:30:59”
Sat Apr 30 12:30:59 CDT 2016
You can set the hardware clock from the system clock using the hwclock command.
sudo hwclock -wu
10. Update SNAPconnect
The SNAPconnect software enables the connection from your E12 device to the rest of your SNAP-powered
network.
To update SNAPconnect, type the command:
sudo –H pip install --upgrade snapconnect –i https://update.
synapse-wireless.com/pypi/
11. Update PyCrypto
The PyCrypto project is required for using AES128 encryption on your radio network.
To update PyCrypto type the command:
sudo -H pip install --upgrade pycrypto
That's it! Your E12 is now ready to work with your SNAP-powered network. Your Python program, using the
SNAPconnect library or the SNAPtoolbelt utilities, interfaces with the gateway's SNAP module directly, and the rest
of your nodes through that. You can also have full internet access via the wired Ethernet connection.
Now it’s up to you to do awesome things with your SNAP-powered network.
You can find examples of other people’s efforts on the Synapse Wireless repository at GitHub:
https://github.com/synapse-wireless.
7

8SNAPconnect E12 User Guide — 116-081614-030-B001
The site includes sample projects for things like sending data collected by SNAP-powered nodes to cloud services,
or an E12-hosted web server. Download the code there, or fork it for your own projects. Better yet, contribute to the
code base for other users.
Mounting the E12
The E12 has mounting holes on the outside flanges of the unit, any of which can be used for mounting the E12 to a
solid surface.

E12 Software Specifics
The E12 uses Canonical’s Ubuntu 14.04, running a custom Linux kernel based on the Beaglebone Black kernal.
There are many resources out there for learning about Ubuntu online, and the topic possibilities far exceed the
scope of this manual. However there are a few details that warrant discussion.
Passwords and root Access
The default configuration for Ubuntu Linux is to have the root user disabled. This is a security precaution, as it means
a hacker who comes across a connection to your device does not automatically know the login name of a user with
full administrative rights to your device.
Instead, Ubuntu works with the sudo paradigm; when you need to perform a function that requires administrative
access, you preface your command with sudo and are prompted for your password (as a reminder that what you
are doing could potentially affect the device’s ability to function).
The default snap user on the E12 has sudo access, and can perform all device administrative tasks. You can create
user accounts on the device and grant them sudo access as well. For added security, you can create sudo-enabled
user accounts and then delete the snap user account to further reduce a potential hacker’s knowledge of how to
access the gateway.
If you would rather work with the root account anyway, you can enable it by assigning a password:
sudo passwd root
Similarly, you can change the snap password with the same command:
sudo passwd snap
NOTE: No account can connect via SSH without a password, though connecting over a serial terminal session is
possible for accounts with no password.
E12-Specific Software Packages
The E12 comes with several support packages installed, and additional ones are available via apt and pip.
NOTE: Before installing new packages, be sure to run sudo apt-get update to sync your E12 with the
package servers and obtain the newest version. This action may take a few minutes, depending on your internet
connection speed.
You can pull the latest updates for your gateway by calling:
sudo apt-get update
sudo apt-get install gateway-updates-latest
9

10 SNAPconnect E12 User Guide — 116-081614-030-B001
You can also forego the previous commands and install updates individually. Note that the steps below
achieve the same outcome as the sudo apt-get update and sudo apt-get install
gateway-updates-latest commands.
First, you can upgrade SNAPconnect and the encryption libraries necessary for AES128 communications
using these commands:
sudo –H pip install snapconnect –i https://update.synapse-
wireless.com/pypi/
sudo -H pip install --extra-index-url https://update.synapse-
wireless.com/pypi snaptoolbelt
sudo -H pip install pycrypto
Finally, check for any updates to other E12-specific packages1:
sudo apt-get install E12-leds E12-buttons E12-gpio-scripts E12-network-
help E12-snap-utils
These installations include the following packages, which are installed in /usr/local/bin except where noted
otherwise:
E12-leds, E12-buttons packages – a simple LED
and button control scripts package
led-1, led-2, led-
3, led-4, led-a Controls lighting for leds
button Reads button states
E12-gpio-scripts package - Initializes GPIO lines
(/etc/rc2.d) S30gpios Startup script to initialize
GPIO lines package
E12-snap-utils package – maintenance and
support scripts for RF220SU.
reset-snap-node resets the RF220SU
wake-snap-node wakes the RF220SU (if it
was sleeping)
flash-bridge performs maintenance on
the RF220SU
1Remember that copying and pasting from PDF files can give unpredictable results. Try pasting into a text editor first
to be sure that the complete command comes across as one line, and that there are not added characters in your
pasted text. Then, copy from the text editor and paste into your command window. Or, type it into the command
window directly.

E12 Physical Interfaces
The E12 includes a tri-color LED that you can control from your programs, plus a button you can monitor. Control
scripts in the E12-led and E12-button packages assist with controlling the LED and monitoring the button.
E12 LEDs
The four processor-controlled LEDs are single color - green - and by
default are activity indicators. The LEDs are numbered 1 - 4 proceeding
from left to right. You can set the LED state using the following commands:
lled-1 on / led-1 off
lled-2 on / led-2 off
lled-3 on / led-3 off
lled-4 on / led-4 off
lled-a [red | green | amber | off]
led1 is closest to the terminal blocks and is labeled "1".
An additional LED is on the side of the E12 next to the antenna. This LED, known as LEDA, is
controlled via the Linux instance running on the E12. The other LED, LEDB, is controlled via
the SNAPpy script running on the internal SM220 module.
Finally, there are two LEDs on the E12 ethernet port. A green LEDthat indicates the E12 is
connected to the network, and a yellow LEDthat illuminates when the E12 is configured for
100Mbps communications.
The SNAPModule-Controlled LED
The unit's SNAPmodule controls the tri-color LED on the antenna side of the case (LEDA) via GPIO_1 (green) and
GPIO_0 (red). (For amber, use both green and red.) This LED is only accessible via the SNAPmodule. It cannot be
controlled by the E12’s AM335x processor, except through calls to the SNAPmodule.
These two IO lines from the SNAPmodule will light their respective colors when written high. This sample code
demonstrates its use:
from synapse.platforms import *
GREEN=GPIO_1
RED=GPIO_0
@setHook(HOOK_STARTUP)
def onStartup():
setPinDir(RED, True)
11

12 SNAPconnect E12 User Guide — 116-081614-030-B001
setPinDir(GREEN, True)
LED_off()
def LED_off():
writePin(RED, False)
writePin(GREEN, False)
def LED_green():
writePin(GREEN, True)
writePin(RED, False)
def LED_red():
writePin(GREEN, False)
writePin(RED, True)
def LED_amber():
writePin(RED, True)
writePin(GREEN, True)
LEDA is the only LED controllable directly from the SNAPmodule. The other three LEDs are controlled from the E12’s
AM335x processor.
The E12 Button
The button on the bottom of the E12 is fully user-accessible. You can monitor the button state at GPIO 112. The E12-
buttons package provides a Bash script that prints the button status to STDIO and returns the button status (as 1 for
up or 0 for pressed).
You can monitor the AM335x processor GPIO directly rather than using the Bash script if you find that to be easier.
Unlike the Bash script that set states on the E12, this script does not require sudo access to run.

Working With the Gateway's SNAPModule
The E12 supports an internal SNAPmodule for 915MHz or 2.4GHz
communications depending on the unit you purchased. These modules are
interchangable, and the E12 can access the SNAPmodule serially via serial ports
/dev/snap0 and /dev/snap1 connecting to UART0 and UART1 on the
module, respectively. By default, SNAP-powered modules communicate serially
over UART1, so when making your SNAPconnect or SNAPtoolbelt connection to
the module, you should use /dev/snap1 unless you have modified your
modules’s default UART settings.
For detailed instructions on SNAPconnect, please consult the SNAPconnect
Python Package Manual, available from http://developer.synapse-
wireless.com/software/snapconnect.
In addition to the serial connections, there is one GPIO pin from the E12 that is tied to the module for controlling and
signaling.
lGPIO 48: Tied to the Reset pin on the RF220SU, you can use this pin to reboot the module.
Waking the SNAPModule
At times it may be helpful to have the SNAPmodule in your E12 sleep, and then be woken by the E12’s processor. If
you have installed the recommended E12-snap-utils package, you can easily do this by defining GPIO_F1 on the
SNAP module as a wake pin, like this:
from synapse.pinWakeup import *
from synapse.platforms import *
@setHook(HOOK_STARTUP)
def onStartup():
setPinDir(GPIO_12, False)
setPinPullup(GPIO_12, True)
wakeupOn(GPIO_12, True, True)
Now, whether your SNAP module is in a timed sleep or an untimed sleep, having the code on your E12 invoke this
command will wake the SNAP module:
/usr/local/bin/wake-snap-node
This command invokes a Bash script to pull the E12s GPIO33 high, pause a second, and then pull the line low. The
Bash script must be invoked as sudo or by a process invoked as sudo. You can examine the Bash script to see
how the GPIO value is controlled for use in your own scripts, should you wish to use the pin as a one-bit signal to the
SNAP module.
13

14 SNAPconnect E12 User Guide — 116-081614-030-B001
Resetting the SNAPModule
There is a pin you can use to reset your module should you need to. (This is necessary, for example, when you reset
factory parameters on the node.)
The E12-snap-utils package also provides a script to assist with this. Invoke this Bash script to briefly pull the reset pin
low and then release it to high, resetting the node:
/usr/local/bin/reset-snap-node
While it is important to be able to do this, in most circumstances it will be less useful day-to-day. (If you need to reset
your SNAPmodule daily, you may have code issues you need to address.)
Restoring Functionality to an Unresponsive SNAPModule
The risk of having a module that provides several configuration options is it expands the possibility of a
misconfiguration causing you to lose contact with the module. Several things can make a module unresponsive,
from setting an encryption key that you then forget, to putting a script on the device that sends the node to sleep with
an invalid wake pin defined.
The Synapse Wireless Portal software provides mechanisms for node recovery, but since you cannot make a serial
connection from the SNAPmodule in your E12 to Portal, that functionality needs to exist on the E12 as well.
If you find that your SNAP module is unresponsive or unreachable over the air or serially, the first suspect is typically
the user script on the module. Many a programmer has accidentally specified the wrong wake pin or accidentally
dropped a node into an endless loop. So, the first thing to try in module recovery is forcibly removing the SNAPpy
script from your SNAPmodule:
sudo flash-bridge -e -p RF220 (for 2.4GHz equipped gateways)
sudo flash-bridge -e -p RF320 (for 915MHz equipped gateways)
WARNING: Addressing the wrong firmware for your unit may render it inoperable, perhaps even permanently. If
you are unsure of which firmware to address, contact Synapse customer support.
This leaves your SNAP module’s NV parameters untouched, but removes the existing SNAPpy script from the node.
You can then load an appropriate script over the air or serially.
If this does not restore your access to the node, the most likely reason for your inability to communicate is
mismatched configuration (NV) parameters on the node. This could be the result of different encryption keys or
encryption types, misconfigured UARTs, differences in how many CRCs are expected, or some other configuration
setting. The easiest thing to do next is to have the node default its NV parameters, which you can also do with
flash-bridge:
sudo flash-bridge -nv -p RF220 (for 2.4GHz equipped gateways)
sudo flash-bridge -nv -p RF320 (for 915MHz equipped gateways)

This clears the encryption settings (no key, no encryption), sets UART connections to their default settings (UART1,
38,400 baud, 8N1), and clears other settings to their default levels. (Refer to the SNAP Reference Manual for what
the defaults are for your firmware version.)
Typically it is best to start with clearing the script in your node before resetting its parameters, because it is possible
for the script to reset (away from default values) parameters that you just reset (to default values).
NOTE: Resetting your SNAP module to default settings does not automatically mean that other devices can talk
to it, over the air or serially. It does mean that you now know how to configure those devices to talk to it.
If you have another radio device on channel 13 using network ID 0xABCD, you will have to set that device to
channel 4, network ID 0x1C2C to talk to your defaulted SNAP module. You can then use that radio connection to
move the E12’s SNAP module to your preferred network settings. Or, you could change those settings serially
from your E12 — if your E12 is set to communicate serially the way that your SNAP module is (considering
encryption keys and types, serial rates, etc.).
The point is: defaulting a device doesn’t mean you have it where you want it, only that you now know where to
go look for it.
Upgrading the SNAP Module Firmware
Synapse Wireless is always working to improve the experience with SNAP-powered networks, and that means new
firmware every now and then. If you find that you want to upgrade the firmware in your gateway's SNAP module, you
can do it over the air or serially from the E12. You'll need to download the firmware appropriate to your SNAPmodule
by typing:
sudo -H pip install snap_firmware_2.8.1 -i https://update.synapse-
wireless.com/pypi/
The flash-bridge command we’ve been using for clearing scripts and resetting parameters saves the day again:
sudo flash-bridge –i <imageName> -p RF220 (for 2.4GHz gateways)
sudo flash-bridge –i <imageName> -p RF320 (for 915MHz gateways)
For this command, <imageName> refers to an absolute or relative path to a Synapse firmware image file, which will
have the extension .sfi.
Loading new firmware erases the script previously in the node but does not change any NV parameters (unless the
two firmware versions, old and new, have different default values for something).
15

16 SNAPconnect E12 User Guide — 116-081614-030-B001
For example:
First, download SNAPfirmware version 2.8.1 by typing:
sudo -H pip install snap_firmware_2.8.1 -i https://update.synapse-
wireless.com/pypi/
This will download the firmware images and put them in the folder:
/usr/local/lib/python2.7/dist-packages/snap_firmware_2_8_1/
Then you can update the E12 by typing:
For 2.4GHz Gateways:
sudo flash-bridge -i /usr/local/lib/python2.7/dist-packages/snap_firmware_
2_8_1/RF220SU_AES128_SnapV2.8.1.sfi
For 915MHz Gateways:
sudo flash-bridge -i /usr/local/lib/python2.7/dist-packages/snap_firmware_
2_8_1/RF320SU_AES128_SnapV2.8.1.sfi