OptConnect ema:Play User manual

OptConnect ema™
ema:Play User Guide
V1.0 Updated May 2020

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.0
2
Table of Contents
Table of Contents 2
1. Introduction 4
1.1 Scope 4
1.2 Contact Information 4
1.3 Orderable Part Numbers 4
1.4 Additional Resources 5
1.5 Activation 5
2. Overview 5
2.1 Contents 5
2.2 Features 5
3. Hardware 7
3.1 At a Glance 7
3.2 System Architecture 9
3.3 Power 9
3.4 Communications 11
3.5 Onboard MCU (U16) 14
3.6 Onboard Programmer/Debugger 15
3.7 User Application Headers and Connectors 15
3.8 Antennas 18
3.9 Mechanical 18
3.9.1 Dimensions 18
4. Software 19
4.1 Native Development Environment 20
4.1.1 Overview 20
4.1.2 Setup and Building 20
4.1.3 Sample Program/Debug Session 25
5. Reference 28
5.1 Schematics 29
5.2 Bill of Materials (BOM) 37
5.3 Assembly Reference 39

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.0
3
5.4 Sample ema:Play configurations 40
5.4.1 On-board MCU control (default) 40
5.4.2 External S2USB control 40
5.4.3 External USB control 41
5.4.4 External MCU control 42
5.4.5 External RS232/RS485/RS422 control 42
5.5 Sample Project –Getting Started with ema 43
5.5.1 Overview 43
5.5.2 Features Supported/Demonstrated 43
5.5.3 Hardware Configuration 43
5.5.4 Software Project Hierarchy 44
5.5.5 Software Configuration 44
5.5.6 Software Architecture & Description 46
5.5.7 Console Debug Output Sample 49
5.5.8 OptConnect Summit Portal 52
5.5.8.1 Overview 52
5.5.8.2 Login and Find ema 52
5.5.8.3 Device Attributes and Location 53
5.5.8.4 Events, Usage and Analytics 54
5.5.9 Board Notify via Summit API 55
5.5.9.1 Overview 55
5.5.9.2 Create a New API Application in Summit 56
5.5.9.3 Authenticate User Application with Summit API 58
5.5.9.4 Send Data to ema Using Board Notify 60
5.5.10 Banyan Hills Canopy IoT™Platform 62
5.5.10.1 Overview 62
5.5.10.2 Login and Find ema:Play 62
5.5.10.3 Device Operations and Leaf Messaging 63
5.5.10.4 Control Actions 64
5.5.10.5 Automation using IoT Campaigns 66
5.5.10.6 Summary 70
6. Revision History 71

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.0
4
1. Introduction
1.1 Scope
The OptConnect ema:Play Evaluation Kit is a hardware platform designed and optimized for evaluating
OptConnect ema™ modems. ema:Play provides easy access to the features of OptConnect ema™
modems, and acts as a launching point for translation into custom IoT/M2M applications using
OptConnect ema™. This document serves as a guide and point of reference for using ema:Play correctly
and efficiently.
1.2 Contact Information
For more information regarding OptConnect ema™ contact OptConnect Sales at 1.877.678.3343 ext. 2020
during normal business hours. For technical support contact OptConnect Customer Care Center at
1.877.678-3343 ext. 2021 from 8 am till 9 pm MST Monday through Saturday.
1.3 Orderable Part Numbers
Orderable Device
Primary
Module
Firmware
Revision
Operating
Temperature
LTE Bands
3G
UMTS
Network
Region
EMA-L4-1-XX-A-A
20.00.505
-40 to +85˚C
FDD B2, B4,
B5, B12, B13
B2, B5
AT&T,
Verizon
North America
EMA-L4-1-US-B-A
20.00.005
-40 to +85˚C
FDD B2, B4,
B5, B12, B13
B2, B5
AT&T,
Verizon
United States
EMA-L4-1-XX-A-A-000
20.00.506
-40 to +85˚C
FDD B2, B4,
B5, B12, B13
B2, B5
AT&T,
Verizon
North America
EMA-L4-1-US-B-A-000
20.00.006
-40 to +85˚C
FDD B2, B4,
B5, B12, B13
B2, B5
AT&T,
Verizon
United States
Unless instructed otherwise EMA-L4-1-XX…will utilize AT&T as the primary carrier and Verizon as the
secondary carrier. Unless instructed otherwise, EMA-L4-1-US…will utilize Verizon as the primary carrier and
AT&T as the secondary carrier.
Orderable
Device
Description
Operating
Temperature
Region
EMA-ZZ-1-XX-Z-B
ema:Play Evaluation Kit, OptConnect ema™ evaluation
platform
-40 to +85˚C
North America
EMA-L4-1-XX-A-B
ema:Play Evaluation Kit, OptConnect ema™ evaluation
platform, EMA-L4-1-XX ema modem included
-40 to +85˚C
North America
EMA-L4-1-US-B-B
ema:Play Evaluation Kit, OptConnect ema™ evaluation
platform, ema EMA-L4-1-US ema modem included
-40 to +85˚C
United States

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.0
5
1.4 Additional Resources
OptConnect ema™ is supported by a full range of documentation, including User Guides and Application
Notes as well as related code samples. The latest versions of these resources can be found at
http://optconnect.com/ema . Suggested prerequisites for this document are the following:
-OptConnect ema™ Hardware Guide
-OptConnect ema™ Getting Started
-OptConnect ema™ emaLink AT Command Manual
1.5 Activation
If ema is not activated/registered upon receipt, please visit https://summit.optconnect.com/ema to
activate/register ema. Once activated, ema:Play includes a free trial period that will last for three months,
with 1 GB of data being available per month. Please contact OptConnect (see section 1.2) for further
questions and requests in regard to the trial period.
2. Overview
2.1 Contents
The ema:Play Evaluation Kit is shipped as a ready to use, “all-in-one” platform for evaluating OptConnect
ema™ modems for IoT/M2M applications. The contents of the kit are listed below.
1. ema:Play Evaluation Kit with/without ema installed (see section 1.3 for device p/n’s)
2. OptConnect Gemini MIMO Antenna
3. 5VDC Power Supply
4. 2 x USB cables
2.2 Features
•On-Board Microcontroller Unit (MCU)
oMicrochip ATSAME51J20A.
o120MHz Core Processor
o1 MB Flash, 256 KB Ram
oOn Board programmer/debugger
JLink OB Technology
Cortex SWD Connector for external programmers/debuggers
oDebug Port
UART to USB access
External Header access
oVoltage Monitors
Input Voltage
ema Voltage
•Configurable Power Supply
oWide input voltage range 4.5V –30V
oExternal power input terminal for other sources (Battery, benchtop, etc.)
oStandard barrel connector input
oUSB power input (excludes powering ema)

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.0
6
oema load switch for low power applications
•Configurable ema Communication Interfaces
oModem UART interface access
RS485/422 full-Duplex
RS485 half-Duplex with Auto Direction Control
On-Board MCU
External header access
Serial 2 USB (S2USB) for computer terminal access
oemaLink interface access
On-Board MCU
External header access
oema USB interface
oScrew terminal block access for wire to board
oShrouded connector access for board to board
•Built in sensors and feedback
oTemperature and humidity
oLight/photo
o2 user push buttons
oLED cellular signal array (Blue)
o2 x LEDs (Red)
•User Application Headers
oInput/Output Application Header
Access to On-Board MCU
•1 x i2c
•1 x CAN bus
•4 x UART
•1 x Analog to Digital (ADC)
•1 x Digital to Analog (DAC)
•6 x General Purpose Input Output (GPIO)
Access to ema communication interfaces
•Modem UART
•emaLink
oPower Application Header
ema power control
3.3V power control
ema IOVREF control
ema Reset Request control
ema On/Off control
3.3V, 4.0V for external usage
•Easy grab test points for measurements
•Efficient design
oCost and availability optimized
•Antenna adaptors built in
oU.FL to SMA for both main and diversity
•Electrical design CAD available for reference

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.0
7
3. Hardware
Section 3 outlines the hardware of ema:Play from a user perspective. Figures 1-3 can be used as quick
reference guides for navigating the various components and features of ema:Play. The hardware is
designed for flexibility and configurability to support different user IoT/M2M applications and integration
architectures, and to also serve as a reference for custom hardware designs integrating ema.
3.1 At a Glance
Figure 1

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.0
8
Figure 2

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.0
9
3.2 System Architecture
Figure 3
3.3 Power
ema:Play can be powered through multiple connectors and/or ports. Furthermore, depending on which
connector/port is powering ema:Play, will also determine which sub systems of the hardware are powered.
There are various feedback LED’s that are provided to let the user know which sub systems are currently
powered. In addition to power input configurations, ema:Play also offers power output for applications
requiring off board power:
Table 1 summarizes the power input architecture and configurations.
Table 2 summarizes related power control signals.

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.0
10
Description
Voltage (ref)
Sources
Inputs Ports (ref)
Outputs Ports (ref)
Systems
Powered
Feedback
(ref)
Main Power
Input
Min 4.5V (VIN)
Max 30V (VIN)
Min 6.75W
External
Source
Barrel Connector (J9)
External VIN (J2/J1)
Test Hook (J9+)
Test Hook (ExtVIN, VIN)
4V,
4VMOD(ema),
3.3V
4V (D5)
4VMOD (D6)
3.3V (D7)
S2USB USB
5V (5V_S2USB)
External USB
Port
S2USB Port (J10)
Test Hook (5vS2USB)
3.3V, S2USB
3.3V (D7)
S2USB (D9)
JLink USB
5V (5V_USBJL)
External USB
Port
JLink USB Port (J13)
Test Point (TP76)
3.3V, JLink
3.3V(D7)
JLink (D28)
Main
Regulator
(U5) Output
4V (4V0)
Max 3A
Main Power
Input
na
Test Hook (4V0)
Pwr App Hdr (J4.1)
4V,
4VMOD(ema),
3.3V
4V (D5)
4VMOD (D6)
3.3V (D7)
Load Switch
(U6) Output
4V (4VMOD)
Max 2A
4V (4V0)
na
Test Hook (4VMOD1,
4VMOD2)
Pwr App Hdr (J4.7)
4VMOD(ema)
4VMOD (D6)
MCU &
Interface
Power (U7)
3.3V (3V3)
Max 1A
4V (4V0)
5V (5V_S2USB)
5V (5V_USBJL)
na
Test Hook (3.3V)
Pwr App Hdr (J4.3)
IO App Hdr (J5.12)
3.3V
3.3V (D7)
ema IOVREF
Min 1.8V
(IO_VREF)
*Max 5.5V
(IO_VREF)
3.3V (3V3)
External via
Pwr App Hdr
(J4.9)
Pwr App Hdr (J4.9)
Test Hook (VIOREF1,
VIOREF2)
ema IO
interface
na
Table 1 * Onboard MCU (U16) must be held in reset if IOVREF is supplied as >4.1V
Description
Signal (ref)
Systems Disabled
Notes
ema Power disable
4VMOD_DIS (J4.2)
ema Power
This signal can be driven high to disable ema’s
power for power sensitive applications
MCU & interface Power
disable
3V3_DIS (J4.4)
3.3V Power rail
This signal can be driven high to disable the entire
3.3V power rail. Typically, this would be used if an
external host embedded system is interfacing to ema
using the Application headers
Onboard IOVREF
disable
OB_uP_IOVREF_DIS (J5.28)
Onboard 3.3V IOVREF
This signal can be used to set ema’s IOVREF level
from an external source
Table 2

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.0
11
3.4 Communications
ema:Play provides several useful and common communication interfaces for sending and receiving data
to and from ema. Additionally, standard interfaces are offered to communicate directly with the Onboard
MCU (U16) for further flexibility. Refer to the following tables for identifying which interface will work best
for the application:
Table 3 summarizes the ema Modem, emaLink, and USB Interface configurations.
Table 4 summarizes the Onboard MCU (U16) interface configurations.
ema Interface
ema:Play
Interface
Access Port
(ref)
Configuration
Switches (ref)
Use Case Example
ema Modem
UART Interface
S2USB Standard
Comm Port
S2USB USB Port
(J10)
Dipswitch (SW2)
This interface can be used to access
the ema Modem UART from a
computer terminal program and
manually send AT commands
RS232
Wire to Board Terminal
(J2.3-J2.6)
Board to Board
Terminal
(J1.3-J1.6)
Dipswitch (SW2)
Slide Switch (SW4)
This interface can be used to access
the ema Modem UART using RS232
from an external device, to send AT
commands
RS422/RS485-4
Wire to Board Terminal
(J2.3-J2.6)
Board to Board
Terminal
(J1.3-J1.6)
Dipswitch (SW2)
Slide Switch (SW4)
This interface can be used to access
the ema Modem UART using
RS422/RS485 full duplex from an
external device, to send AT commands
RS485-2
Wire to Board Terminal
(J2.3, J2.4)
Board to Board
Terminal
(J1.3, J1.4)
Dipswitch (SW2)
Slide Switch (SW4)
This interface can be used to access
the ema Modem UART using RS485
half-duplex from an external device, to
send AT commands
Onboard MCU
(U16)
Onboard MCU
(U16.44, U16.45)
Dipswitch (SW2)
This interface can be used by the
Onboard MCU (U16) to access the ema
Modem UART to send AT commands
External Device
IO App Hdr
(J5.17-J5.20)
Dipswitch (SW2)
This interface can be used by an
external embedded device to access
the ema Modem UART to send AT
commands
emaLink Interface
Onboard MCU
(U16)
Onboard MCU
(U16.35, U16.36)
Dipswitch (SW3)
This interface can be used by the
Onboard MCU (U16) to access the
emaLink interface for ema
management features
External Device
IO App Hdr
(J5.15, J5.16)
Dipswitch (SW3)
This interface can be used by an
external embedded device to access
the emaLink interface for ema
management features

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.0
12
ema USB
ema USB Port
ema USB Port
This interface can be used to directly
access the ema USB interface
Table 3
Onboard
MCU (U16)
Interface
ema:Play
Interface
Access Port (ref)
Configuration
Switches (ref)
Use Case Examples
UART
RS232
Wire to Board Terminal
(J2.3-J2.6)
Board to Board
Terminal
(J1.3-J1.6)
Slide Switch (SW4)
This interface can be used to access
the Onboard MCU (U16) using RS232
from an external device
RS422/RS485-4
Wire to Board Terminal
(J2.3-J2.6)
Board to Board
Terminal
(J1.3-J1.6)
Slide Switch (SW4)
This interface can be used to access
the Onboard MCU (U16) using
RS422/RS485 full duplex from an
external device
RS485-2
Wire to Board Terminal
(J2.3, J2.4)
Board to Board
Terminal
(J1.3, J1.4)
Slide Switch (SW4)
This interface can be used to access
the Onboard MCU (U16) using RS485
half-duplex from an external device
External Device
IO App Hdr
(J5.21-J5.24)
This interface can be used to access
the Onboard MCU (U16) using an
external embedded device using UART
S2USB Enhanced
Comm Port
S2USB USB Port
(J10)
This interface can be used as a
debug/console input/output port for
the Onboard MCU (U16)
i2c
External Device
IO App Hdr
(J5.13, J5.14)
This interface can be used to interface
to the Onboard MCU (U16) using an
external device over i2c
CAN
External Device
IO App Hdr
(J5.25, J5.26)
This interface can be used to access
the Onboard MCU (U16) using an
external CAN transceiver
GPIO
External Device
IO App Hdr
(J5.2-J5.7)
This interface can be used to interface
to the Onboard MCU (U16) using GPIO
and/or peripherals supported by the
MCU.
Table 4
ema:Play has built in configuration switches to allow the user to easily select which communication
interface to use in their application. Alternatively, the Onboard MCU (U16) can be used to control the
communication interface selection via custom firmware. The architecture is such that the ema Modem
UART signals and the emaLink interface signals can be directed according to Table 5 using dipswitches
(SW2, SW3), and the slide switch (SW4).

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.0
13
Table 5 summarizes how to configure the ema:Play hardware for the desired ema interface. Alternatively,
the switch settings are also labeled on the ema:Play PCB silkscreen for quick reference.
Desired
ema Interface
Desired
ema:Play
Interface
Access Port
(ref)
Switch Configuration
ema Modem UART
Interface
S2USB Standard
Comm Port
S2USB USB Port
(J10)
Dipswitch (SW2):
S2USB
RS232
Wire to Board Terminal
(J2.3-J2.6)
Board to Board
Terminal
(J1.3-J1.6)
Dipswitch (SW2) Slide Switch (SW4)
Ser 232
RS422/RS485-4
Wire to Board Terminal
(J2.3-J2.6)
Board to Board
Terminal
(J1.3-J1.6)
Dipswitch (SW2) Slide Switch (SW4)
Ser 485 4
RS485-2
Wire to Board Terminal
(J2.3, J2.4)
Board to Board
Terminal
(J1.3, J1.4)
Dipswitch (SW2) Slide Switch (SW4)
Ser 485 2
Onboard MCU
(U16)
Onboard MCU
(U16.44, U16.45)
Dipswitch (SW2)
OBuP

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.0
14
External Device
IO App Hdr
(J5.17-J5.20)
Dipswitch (SW2)
Ext
emaLink Interface
Onboard MCU
(U16)
Onboard MCU
(U16.35, U16.36)
Dipswitch (SW3)
OBuP
External Device
IO App Hdr
(J5.15, J5.16)
Dipswitch (SW3)
Ext
ema USB
ema USB Port
ema USB Port
(J6)
Table 5
3.5 Onboard MCU (U16)
ema:Play provides an onboard MCU (U16) to allow users to develop their own custom IoT/M2M
applications using ema. There are various sensors, peripherals, and LED’s integrated into the ema:Play
hardware that can be accessed by U16. Please visit the following website for more information regarding
the onboard MCU (U16):
https://www.microchip.com/wwwproducts/en/ATSAME51J20A
Table 6 summarizes the various sensors and peripherals available to U16 for customization.
Sensor/Peripheral
(ref)
Interface to U16
(ref)
Temperature/Humidity
(U1)
i2c
(U16.29, U16.30)
Photo/Light
(Q2)
A/D
(U16.61)
Main Voltage Monitor
(VIN_MON)
A/D
(U16.63)
ema Voltage Monitor
(MOD_V_MON)
A/D
(U16.62)

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.0
15
External A/D Monitor
(OB_uP_AIN)
A/D
(U16.64)
External High Accuracy Crystal
(XTAL1)
XIN/XOUT
(U16.31, U16.32)
Push Buttons
(SW7, SW8)
Digital Input
(U16.19, U16.20)
Manual Reset
(SW5, SW6)
Digital Input
(U16.52)
External D/A Output
(OB_uP_DAC)
Digital Output
(U16.3)
GPIO
(PA06-PA08, PB06-PB07)
GPIO
(U16.15, U16.16, U16.9, U16.10, U16.17)
User LEDs
(BLU_LED0-BLU_LED3,
RED_LED0-RED_LED1)
GPIO
(U16.23-U16.28)
Table 6
3.6 Onboard Programmer/Debugger
ema:Play provides an onboard Segger JLink In Circuit Programmer/Debugger (ICP/D) USB port (J13) for
loading firmware into the onboard MCU (U16) for custom applications. This ICP/D also functions as a
debugger for development and evaluation purposes. This allows the user to eliminate purchasing an
external ICP/D to use with the onboard MCU (U16). Additionally, a Cortex Single Wire Debug (SWD)
Connector (J11) is provided for use with any compatible external ARM Cortex ICP/D. For more information
regarding the onboard Segger JLink ICP/D, please visit this website:
https://www.segger.com/products/debug-probes/j-link/models/j-link-ob/
3.7 User Application Headers and Connectors
ema:Play provides a wire to board screw terminal connector (J2) and a board to board shrouded
connector (J1) to interface to external devices and allow them direct access to ema, or the onboard MCU
(U16). Also provided are a power application header (J4) and an IO application header (J5), for ultimate
flexibility when developing custom applications for ema.
The wire to board screw terminal connector (J2) and the board to board shrouded connector (J1) are
electrically connected in parallel and can be used to allow external devices with common interfaces
(RS232, RS422, RS485) to directly access ema and the onboard MCU (U16). Flow control (CTS/RTS) is also
provided at these connectors where applicable. Reference section 3.4 for further details on these
interfaces.
Table 7 summarizes the signals relative to J2 and J1

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.0
16
J2/J1 Pin Number
J2/J1 Signal Name
Usage Example
1
EXT_VIN
This signal can be used to supply 4.5V-30V to power the
ema:Play/ema platform
2
DGND
Connect this to the external devices’ system Ground/return
3
232TX/A
(RS232) Connect this to the external devices’ RX signal
(RS422/485-2/4) Connect this to the external devices’ TXD+ signal
4
232RX/B
(RS232) Connect this to the external devices’ TX signal
(RS422/485-2/4) Connect this to the external devices’ TXD- signal
5
232RTS/Y
(RS232) Connect this to the external devices’ CTS signal
(RS422/485-4) Connect this to the external devices’ RXD+ signal
6
232CTS/Z
(RS232) Connect this to the external devices’ RTS signal
(RS422/485-4) Connect this to the external devices’ RXD- signal
7
EMA_RNG
This signal can be monitored by an external device. It is
programmable in ema via an AT command
8
EMA_STS
This signal can be monitored by an external device. It will go high
(IO_VREF) when ema’s communication interfaces become ready
Table 7
The power application header (J4) can be used to control various power functions on ema:Play as well as
ema.
Table 8 summarizes the signals relative to J4.
J4 Pin Number
J4 Signal Name
Usage Example
1
4V0
This signal can be used to power external devices (4V @ 1.25A max)
2
4VMOD_DIS
This signal can be used by an external device to remove power from
ema. Drive high (max 5.5V) to disable ema power via load switch
(U6).
3
3V3
This signal can be used to power external devices (3.3V @ .75A max)
4
3V3_DIS
This signal can be used by an external device to disable the onboard
3.3V power rail. Drive high (max 5.5V) to disable the 3.3V power rail.
5
DGND
Connect this to the external devices’ system Ground/return
6
MODEM_RESET
This signal can be used by an external device to request an ema
reset in the event that ema becomes unresponsive. Drive high (max
5.5V) for a minimum of 1 seconds, then release.

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.0
17
7
4VMOD
This signal can be used to power external devices that may require
the ability to have power removed by the load switch (U6). (4V @
1.25A max)
8
MODEM_ON_OFF
This signal can be used to request ema to turn ON or OFF. Drive
high (max 5.5V) to request ema to turn ON. Drive low to request
ema to turn OFF.
9
MODEM_IO_VREF
This signal can be used by an external source to set ema’s IO voltage
levels (1.8V-5.5V)
10
Unused
Unused
Table 8
The IO application header (J5) can be used to control, monitor, and interface with various signals and
systems throughout the ema:Play hardware, as well as ema.
Table 9 summarizes the signals relative to J5.
J5 Pin Number
J4 Signal Name
Usage Example
1, 10, 27
DGND
Connect this to the external devices’ system Ground/return
2, 3, 4, 5, 6
PA08, PB07, PB06, PA07
PA06
These signals connect directly to the onboard MCU’s (U16) GPIO’s
and can be used according to the limitations of U16
7
OB_uP_RESET
This signal can be used by an external device to force a hardware
reset of the onboard MCU (U16)
8
MOD_DTR
This signal can be used by an external device to assert the Data
Terminal Ready (DTR) signal for ema
9
OB_uP_AIN
This signal can be used by an external device to input an analog
voltage (max 3.3V) for reading by the onboard MCU (U16)
11
OB_uP_DAC
This signal can be used by the onboard MCU (U16) to generate
analog voltage (max 3.3V) for use by an external device
13, 14
OB_uP_SCL,
OB_uP_SDA
These signals can be used to connect external i2c devices for use by
the onboard MCU (U16)
15, 16
EXT_EMA_RX,
EXT_EMA_TX
These signals can be used by an external device to communicate
directly over the emaLink interface. See section 3.4.
17, 18, 19, 20
EXT_RTS, EXT_CTS,
EXT_RX, EXT_TX
These signals can be used by an external device to communicate
directly over the ema Modem UART interface. See section 3.4.
21, 22
OB_uP_APP_HDR_RX,
OB_uP_APP_HDR_TX
These signals can be used by an external device to communicate
directly with the onboard MCU (U16)
23, 24
OB_uP_DBG_RX,
OB_uP_DBG_TX
These signals can be used by the onboard MCU (U16) to send and
receive debug/console messages over UART.
25, 26
CAN/RX, CAN/TX
These signals can be used by the onboard MCU (U16) to interface to
a CAN transceiver for communications

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.0
18
28
OB_uP_IOVREF_DIS
This signal can be used by an external device to disable the onboard
3.3V IO_VREF. Drive high (max 5.5V).
Table 9
3.8 Antennas
ema:Play provides two U.FL to SMA antenna adaptor cables. The external antennas should be connected
at the SMA ends of the adaptor cables (primary-J3, diveristy-J12). The U.FL ends of these adaptors should
be carefully connected to ema after it has been seated correctly in the modem socket (J7/J8).
Table 10 lists recommended antennas for use with ema:Play
Type
Manufacturer
Part Number
External Cellular Antenna
Taoglas
TG.30.8113
External Cellular Antenna
Taoglas
GSA.8841.A.105111
External Cellular MIMO Antenna *
2J
2J7724Ma
Table 10 * Available from OptConnect
3.9 Mechanical
3.9.1 Dimensions
Width = 3.250 inches, 82.55 mm
Length = 3.330 inches, 84.58 mm
Max height, ema seated, not including standoffs = .5825 inches, 14.8 mm
Max height, ema seated, including standoffs = .8770 inches, 22.3 mm

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.0
19
The PCB assembly for ema:Play includes a 40 mil(.0400 inches) clearance area along both short sides(x) of
the PCB assembly along the edge. This allows the PCB assembly to slide into an enclosure that is suitable
for the slide mounting method.
4. Software
Section 4 outlines the software architecture and framework that is compatible with ema:Play. The methods
and techniques outlined in this section represent different ways to develop software for ema:Play and
ema, and are by no means the only methods and techniques that can be used.
There are four main methods for interfacing software with ema using ema:Play.
1. Develop software that runs on ema:Play onboard MCU (U16). This method closely follows the
procedure outlined in section 4.1, and involves a technical understanding and knowledge of
writing code for embedded systems. Typically, this method will involve a Real Time Operating
System (RTOS) runtime environment, such as freeRTOS or similar, and will use the U16 UARTs to
access ema, along with any other desired features that ema:Play offers. See section 3.5. Reference
section 5.4.1 for ema:Play configuration to support this method.

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.0
20
2. Develop software that runs external to ema:Play on a host platform that has a standard serial
COMM interface. This method requires that ema:Play be connected to the host platform using the
S2USB USB interface (J10). The most common host platform in this scenario is a standard
computer with a terminal program. This method grants access to ema via its Modem UART
interface. Reference OptConnect ema™ Getting Started with ema and OptConnect ema™
Application Note 001: HTTP Using Socket Dials for guidance on this method. Reference section
5.4.2 for ema:Play configuration to support this method.
3. Develop software that runs external to ema:Play on a host platform that can access ema using
USB drivers. USB drivers are available for download at http://optconnect.com/ema . This
method involves writing software at a higher application level, with easy access to the hardware’s
USB drivers. The interface to ema via ema:Play would occur at the ema USB port (J6). Reference
OptConnect ema™ Application Note 002: Windows Networking Guide for guidance on this method.
Reference section 5.4.3 for ema:Play configuration to support this method.
4. Develop software that runs external to ema:Play on a different embedded development kit or
custom piece of embedded hardware or machine. ema can be accessed via ema:Play at the user
Application Headers (J4, J5). Additionally, built in features of ema:Play can also be accessed using
this method. See section 3.5 and 3.7. Reference section 5.4.4 and 5.4.5 for ema:Play configuration
to support this method.
4.1 Native Development Environment
4.1.1 Overview
ema:Play has an onboard MCU (U16) that is provided for custom user applications utilizing ema as the
cellular connection. This section demonstrates how to use Atmel Studio 7 to get up and running,
developing code quickly on ema:Play. The hardware for ema:Play is setup for flexibility relative to the
development environment, and Atmel Studio 7 was chosen due to its simplicity and availability.
Additionally, more in-depth documentation about Atmel Studio 7 is available than this User Guide
provides. To reduce development time, and spend more time developing the application versus the driver
and register initialization code, Microchip offers the Atmel | Start tool. The samples used in ema:Play have
been developed using this tool. For more information regarding Atmel | Start, visit
https://start.atmel.com/.
Any development environment that supports the onboard MCU (U16, Microchip ATSAME51J20A) and a
Segger JLink In Circuit Programmer/Debugger (ICP/D), or the ARM Cortex SWD Debug Connector (J11)
interface can be used. Reference section 3.6 for more details on the ICP/D.
4.1.2 Setup and Building
1. Download and install Atmel Studio 7:Go to the following website for the download link:
https://www.microchip.com/mplab/avr-support/atmel-studio-7
Make sure to select the following options during the installation. See Figure 4.