OptConnect ema User manual

OptConnect ema™
Windows Networking Guide
Application Note: 002
V1.2 Updated May 2020

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.2
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
2. Windows 7 Environment 5
2.1 Overview 5
2.2 CDC_NCM Mode 6
2.2.1 Overview 6
2.2.2 Relevant ema Ports 6
2.2.3 ema Configuration 7
2.3 Windows Configuration 8
2.3.1 Overview 8
2.3.2 Configure the CDC_NCM Connection Settings 8
2.3.3 Windows Command Prompt Settings 13
2.3.4 Verify the Internet Connection 14
2.3.5 Closing and Re-opening the Connection 14
2.4 Troubleshooting CDC_NCM Data Connections 15
2.5 Telit Connection Manager 15
2.5.1 Overview 15
2.5.2 Installation Instructions 15
2.5.3 Configuration 16
2.5.4 Troubleshooting 18
3. Windows 8/10 Environments 19
3.1 Overview 19
3.2 MBIM Mode 19
3.2.1 Overview 19
3.2.1 Relevant ema Ports 19

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.2
3
3.2.2 ema Configuration 20
3.3 Windows Configuration 21
3.3.1 Overview 21
3.3.2 Verify ema Enumeration 21
3.3.3 Window Cellular Settings 22
3.3.4 Verify the Internet Connection 27
3.4 Troubleshooting 28
3.4.1 Verify the Internet Connection 28
3.4.2 Windows Fails to Open the Connection 29
4. Revision History 30

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.2
4
1. Introduction
1.1 Scope
This document serves as a guide to Windows networking using an OptConnect ema™ modem and
Windows 7, 8, and 10 operating systems. For demonstration purposes, OptConnect’s ema:Play Evaluation
Kit will be used as ema’s host system throughout this document. Also, the ema:Play USB port (J6) that is
directly beneath ema (when plugged into the modem socket on ema:Play) will be used for both the data
connection and AT command parser serial connection.
This application note demonstrates a few Windows networking options for OptConnect ema™ users
running Windows 7, 8, and 10 on their host platform.
Windows 7 users have the option to use CDC_NCM protocol, or Telit's Connection Manager tool, while
Windows 8 and 10 users must use MBIM protocol.
Each of the aforementioned connection protocols enables the OptConnect ema™ modem to provide an
Internet connection to the host platform over USB. The provided Internet connection then functions
similarly to a normal ethernet connection on the host platform. As such, these connection methods are
often categorized as "Ethernet Over USB" connections.
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.

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.2
5
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
1.4 Additional Resources
OptConnect ema™ is supported by a full range of documentation in addition to this document; including
User Guides and Application Notes as well as an ema:Play User Guide and 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™ emaLink AT Command Manual
-OptConnect ema™ Getting Started with ema
-ema:Play User Guide
This document assumes that the user has familiarized
themselves with the prerequisites listed above.
Furthermore, this document is written under the assumption
that ema is the sole Internet connection source. If other
Internet connection sources are intended for use alongside
ema, additional steps may be required to ensure proper
functionality.
Additionally, the configuration of ema on the host platform
may interfere with existing Internet connections.
2. Windows 7 Environment
2.1 Overview
There are two options for establishing an Internet connection using ema when running a Windows 7
environment. The first option involves using the ema’s CDC_NCM stack to establish a data connection.
The second option involves using Telit's Connection Manager tool.
Section 2.2 covers the procedure for setting up ema to use CDC_NCM protocol, as well as the steps to
configure the relevant Windows settings. Section 2.3 explains how to install, configure, and use Telit's
Connection Manager Tool.

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.2
6
Useful troubleshooting information is available in Section 2.4.
2.2 CDC_NCM Mode
2.2.1 Overview
Section 2.2 contains instructions for configuring ema using CDC_NCM protocol to establish a data
connection. CDC_NCM protocol enables a high-speed peripheral, such as a cellular modem, to establish
an internet connection over USB. This internet connection then behaves like a regular ethernet
connection.
2.2.2 Relevant ema Ports
First, the user should familiarize themselves with the available ports that ema presents to Windows 7.
When ema is powered on with the USB cable connected at ema:Play (J6), several USB ports will
enumerate. To see the available ports, open the Windows Device Manager, and open the "Ports" tab. ema
should enumerate in the device manager similarly to the example Figure 1:
Figure 1
From Figure 1, one modem and five USB Ports have enumerated in the device manager. The USB0 port
enumerates as “Telit Mobile Highspeed Modem x”, while the other USB ports enumerate as “Telit Mobile
(USBx)(COMx)”. The COM port associated with USB0/“Telit Mobile Highspeed Modem x”, can be found by
right-clicking on the device in the “Modems” tab, and clicking “Properties”. In the Properties window that
opens, click the “Modem” tab and the COM # will be listed as shown in figure 2. Take note of the COM #
for USB0 port for later use in this section. In this example the COM # is 24. Only USB0 and USB3 are

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.2
7
capable of being configured to use CDC_NCM protocol by default so it is recommended to use the USB0
port.
Figure 2
Note: If the ports do not enumerate or Windows 7 does not recognize the drivers, visit
http://optconnect.com/ema for the latest drivers.
2.2.3 ema Configuration
1. Open a Terminal Window: ema must be configured to use CDC_NCM protocol. As mentioned in
Section 2.2.2, The USB0 port should be used as the AT interface for the CDC_NCM setup.
Open a terminal window and select the COM port that corresponds to the USB0 port. In the case
of this example, the COM # was 24.
2. Verify the USB Mode Configuration: Verify that the USB ports are configured in the proper
manner. Issue the following AT command to ema:
AT#USBCFG=0
This command instructs ema to configure each of its USB ports to ACM mode, with CDC_NCM
enabled. To confirm the success of the above command, issue the following AT command:
AT#USBCFG?
ema should respond with:

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.2
8
#USBCFG: 0
If ema does not respond with the above result code, reissue the first AT command, or consult
Telit's AT command manual.
3. Enable GPRS Network Attaching: In order to establish a data connection, ema must attach to
the General Packet Radio Services (GPRS) network. Issue the following AT command:
AT+CGATT=1
4. Assign PDP Context to the CDC_NCM stack: The proper PDP context must be assigned to the
CDC_NCM stack. Issue the following AT command:
AT#NCM=1,<cid>
where <cid> is replaced with "1" for AT&T users, and "6" for Verizon Users.
5. Activate the PDP Context: Activate the PDP context by issuing the following AT command:
AT+CGACT=1,<cid>
where <cid> is replaced with "1" for AT&T users, and "6" for Verizon Users. If the activation fails,
retry the above AT command, check signal quality, or try a device reset.
6. Open the Data Connection: To open the data connection, issue the following AT command:
AT+CGDATA="M-RAW_IP",<cid>
where <cid> is replaced with "1" for AT&T users, and "6" for Verizon Users.
ema will respond with:
CONNECT
OK
At this point, the data connection has been opened. Additionally, ema is still able to accept AT
commands if needed.
2.3 Windows Configuration
2.3.1 Overview
Now that ema has been properly configured to use CDC_NCM protocol to establish a data connection,
several settings must be configured in Windows to enable the internet connection.
2.3.2 Configure the CDC_NCM Connection Settings
1. Open the CDC_NCM Connection Settings: Open the Windows “Network and Sharing Center”
and click on the link “Change Adapter Settings”. The window should generally look like Figure 3.

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.2
9
Figure 3
Double click on “Local Area Connection x/Telit Mobile (NCM1)” to open the Properties dialogue
as shown in Figure 4.
Figure 4

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.2
10
Double click the selection “Internet Protocol Version 4 (TCP/Ipv4)”. This dialogue allows the
TCP/IPv4 settings of the CDC_NCM connection to be modified. The dialogue is shown in Figure 5.
Figure 5
The settings listed in the window will need to be updated with ema’s connection data.
2. Get ema Connection Data: The fields in Figure 5 must be updated with ema specific parameters.
To get this data, issue the following AT command:
AT+CGCONTRDP=<cid>
where <cid> is replaced with "1" for AT&T users, and "6" for Verizon Users.
ema will output an assortment of relevant connection data including it’s IP address, gateway
address, and primary and secondary DNS addresses. The format of the result is as follows:
+CGCONTRDP:<cid>,<bearer_id>,"<APN>","<ip_addr and subnet_mask>", "<gw_addr>"
"<DNS_prim_addr>","<DNS_sec_addr>", "<P_CSCF_prim_addr>", "<P_CSCF_sec_addr>"
For the purposes of the CDC_NCM connection settings, only the PDP context identifier <cid>,
the <ip_addr and subnet_mask>, the <gw_addr>, the <DNS_prim_addr>, and the
<DNS_sec_addr> are of consequence. Record the relevant data, and continue.

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.2
11
For more information on these parameters, please refer to Telit's AT command manual for the
LE910-V2 cellular module.
3. Update the CDC_NCM connection settings: In the dialogue that was opened in step 2 above,
select the radio buttons next to “Use the following IP address:” and “Use the following DNS server
addresses:”. Enter the corresponding values that were recorded in step 2 above. When complete,
the dialogue should look similar to Figure 7.
Figure 7
Click “OK” to save the connection settings and return to the Network Connections window as
shown in Figure 8. Double click on “Local Area Connection #”. It should now take you to the
Status Dialogue. Click on “Details”. Locate the “Physical Address” line and record this value.
Reference Figure 9.

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.2
12
Figure 8
Figure 9

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.2
13
2.3.3 Windows Command Prompt Settings
The final step is to issue two commands in the Windows Command Prompt. Open a Command Prompt in
administrator mode and enter the command below:
netsh interface ip delete arpcache
This command will clear the ARP (Address Resolution Protocol) cache in Windows.
The ARP cache is used by the operating system to translate a hostname that has been resolved to an IP
address into a hardware MAC address and vice versa. This effectively allows a hardware MAC address to
be associated with an IP address, allowing the device at the MAC address to communicate directly with
the IP address.
In the case of ema and the CDC_NCM setup procedure, it is a good practice to clear this cache to avoid
any potential errors or MAC address conflicts.
After issuing the above command, enter the following command (as one line):
netsh interface ip add neighbor "Local Area Connection x" <gw_addr> <phys_addr>
Where xis replaced with the number of the local area connection as seen in Figure 8, <gw_addr> is
replaced with the gateway address that was retrieved from ema in Section 2.3.2 step 2, and <phys_addr>
is replaced with the physical address that was recorded in Section 2.3.2 step 3.
This command creates an association between ema’s gateway address and ema’s physical address for
"Local Area Connection x" in the ARP cache.
If desired, the ARP cache can be examined to make sure that the above command was successful. To
check this, type the following into the Command Prompt:
arp -a
The output from the above command should look similar to Figure 10.
Figure 10

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.2
14
As shown in Figure 10, the ARP cache has an entry of ema’s physical address and its gateway address. At
this point, the internet connection should be established.
2.3.4 Verify the Internet Connection
After the Windows settings have been properly configured, the host platform should be connected to the
Internet via cellular using ema.
A quick way to test the connection status is to open a web browser, and attempt to load a page. If the
page loads, then the computer is connected to the internet.
Another way to test the internet connection is to use the Windows Command Prompt to ping an online
resource. For instance, issue the following command to ping one of Google's public IPv4 DNS addresses:
ping 8.8.8.8
If the connection is successful, the Command Prompt window should look similar to Figure 11.
Figure 11
2.3.5 Closing and Re-opening the Connection
When desired, the connection can be closed by issuing the following AT command:
AT+CGATT=0
ema will respond with:
OK
NO CARRIER
Once the connection has been closed, it can be reopened at any time. The settings for “Local Area
Connection x” are saved by Windows so to reopen the data connection, issue the following AT command:
AT+CGDATA="M-RAW_IP",<cid>
where <cid> is replaced with "1" for AT&T users, and "6" for Verizon Users.
ema will respond with:

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.2
15
CONNECT
OK
Note: It may take a few minutes for the connection to resume. If the modem still has not connected after
a few minutes, verify that the Windows settings for "Local Area Connection x" are still valid, and retry
opening the data connection again.
2.4 Troubleshooting CDC_NCM Data Connections
If a CDC_NCM connection has been set up on ema, and the Windows is connected to the proper "Local
Area Connection x" network, but the host platform cannot load webpages or ping online resources, follow
the steps below.
First, open a Windows Command Prompt with administrator privileges. Next, enter in the following four
commands:
netsh winsock reset
netsh interface ipv4 reset
netsh interface ipv6 reset
ipconfig /flushdns
The above four commands reset Windows' TCP/IPv4 stack, its TCP/IPv6 stack, and clears its DNS cache. Be
aware that this may disrupt any other connections that are in use such as ethernet and Wi-Fi. As such, it is
recommended to only issue these commands as an absolute last resort so as to avoid disrupting any
existing user settings and configurations.
After issuing the above commands, restart the computer and re-attempt the CDC_NCM configuration
procedure from the beginning in Section 2.2.
2.5 Telit Connection Manager
2.5.1 Overview
Telit offers a tool called "Telit Connection Manager (TCM)" that can be used in conjunction with ema to
easily establish a data connection. To obtain the installer for this program, please visit
http://optconnect.com/ema .
2.5.2 Installation Instructions
To install TCM, run the installer and follow the instructions listed. The initial installation window should
look like Figure 12.

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.2
16
Figure 12
Note: The installer may also try to install the latest Windows drivers for ema. However, it is not
recommended to allow the installer to update the drivers on the host platform.
After the installation is finished, close the installer, and open Telit Connection Manager (TCM).
2.5.3 Configuration
The landing window for the TCM should look like Figure 13.
Figure 13

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.2
17
Observe the middle-left section of the window. The text in the above image that says "AT&T" will be
replaced with the name of the network operator for the currently inserted SIM card. If this text is replaced
by something other than the carrier name (such as "No Service"), check the status of the SIM card and the
cellular antenna.
If a valid carrier is listed, click on the “Settings” oval button. This will open up the settings for Telit
Connection Manager.
Next, click on the "Network Profiles" button. The window should look like Figure 14.
Figure 14
This window contains the settings for the APN that will be used for the data connection. Generally, the
APN is populated automatically by the program, and will be configured by default. However, if this is not
the case, edit the relevant fields to reflect the proper APN for ema. Be sure to save the configuration when
finished.
When a valid APN has been entered and saved, return to the main window by clicking the “Connection”
button. Click the “Connect” button in the bottom left corner of the TCM window. This will begin the
connection process.
Once ema is connected, a message will appear in the bottom-center text box that says something similar
to "Telit_Dialup: Connected", and the graph in the center will begin to be populated with data. Reference
Figure 15. At this point, the data connection is ready for use, and will function as any other Wi-Fi or
ethernet connection.

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.2
18
Figure 15
2.5.4 Troubleshooting
The TCM can occasionally say that it has disconnected after the "Connect" button has been pressed.
In this case, shut down ema and close out of TCM. Then, restart the program, followed by ema. The
"Connect" button should now function as intended, and will not automatically disconnect. The TCM can
also show that the connection is valid, but Windows is reporting no internet connection. To resolve this,
power cycle ema, and disable the “Local Area Connection x” in the Network Connections window.

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.2
19
3. Windows 8/10 Environments
3.1 Overview
The networking protocol that is available to Windows 8 and 10 users is the Mobile Broadband Interface
Model (MBIM) protocol. MBIM is a networking protocol created by the USB Implementers Forum, and is
designed for USB-based networking solutions, such as cellular modems. This protocol facilitates the
connection of USB-enabled embedded modems with other USB-enabled electronics such as personal
computers.
Section 3 describes how to configure MBIM mode on ema using a Windows 8 or Windows 10
environment.
3.2 MBIM Mode
3.2.1 Overview
Section 3.2 contains instructions for configuring ema using MBIM protocol to establish an internet
connection.
3.2.1 Relevant ema Ports
First, the user should familiarize themselves with the available ports that ema presents to Windows 8 and
10. When ema is powered on with the USB cable connected at ema:Play (J6), several USB ports will
enumerate. To see the available ports, open the Windows Device Manager, and open the "Ports" tab. ema
should enumerate in the device manager similarly to the example in Figure 16:
Figure 16

© OptConnect Management, LLC 2020. All rights reserved. Revision 1.2
20
From Figure 16, one modem and five USB Ports have enumerated in the device manager. The USB0 port
enumerates as “Telit Mobile Highspeed Modem x”, while the other USB ports enumerate as “Telit Mobile
(USBx)(COMx)”. The COM port associated with USB3 is “Telit Mobile (USB3)(COM21)”. Take note of this
COM #, 21 for USB3 port for later use in this section. Only USB3 and USB5 are capable of being
configured to use MBIM protocol by default so it is recommended to use the USB3 port.
Note: If the ports do not enumerate or Windows 8/10 does not recognize the drivers, visit
http://optconnect.com/ema for the latest drivers.
Note: It is possible for the COM #’s to change between CDC_NCM and MBIM enumerations. Please be
mindful of this in subsequent sections.
3.2.2 ema Configuration
1. Open a Terminal Window: ema must be configured to use MBIM protocol. As mentioned in
Section 3.2.1, The USB3 port should be used as the AT interface for the MBIM setup.
Open a terminal window and select the COM port that corresponds to the USB3 port. In the case
of this example, the COM # was 21.
2. Verify the USB Mode Configuration: Verify that the USB ports are configured in the proper
manner. Issue the following AT command to ema:
AT#USBCFG=3
This command instructs ema to configure each of its USB ports to ACM mode, with MBIM
enabled on the USB3 port. To confirm the success of the above command, issue the following AT
command:
AT#USBCFG?
ema should respond with:
#USBCFG: 3
If ema does not respond with the above result code, reissue the first AT command, or consult
Telit's AT command manual.
3. Assign PDP Context to the MBIM stack: The proper PDP context must be assigned to the MBIM
stack. Issue the following AT command:
AT#MBIMCFG=<cid>
where <cid> is replaced with "1" for AT&T users, and "6" for Verizon Users. To confirm the
success of the above command, issue the following AT command:
AT#MBIMCFG?
ema should respond with:
#MBIMCFG: <cid>