Multi-Tech Systems, Inc. makes no representations or warranties, whether express, implied or by estoppels, with respect to the content, information,
material and recommendations herein and specifically disclaims any implied warranties of merchantability, fitness for any particular purpose and noninfringement.
Multi-Tech Systems, Inc. reserves the right to revise this publication and to make changes from time to time in the content hereof without obligation of
Multi-Tech Systems, Inc. to notify any person or organization of such revisions or changes.
Legal Notices
The MultiTech products are not designed, manufactured or intended for use, and should not be used, or sold or re-sold for use, in connection with
applications requiring fail-safe performance or in applications where the failure of the products would reasonably be expected to result in personal injury or
death, significant property damage, or serious physical or environmental damage. Examples of such use include life support machines or other life
preserving medical devices or systems, air traffic control or aircraft navigation or communications systems, control equipment for nuclear facilities, or
missile, nuclear, biological or chemical weapons or other military applications (“Restricted Applications”). Use of the products in such Restricted
Applications is at the user’s sole risk and liability.
MULTITECH DOES NOT WARRANT THAT THE TRANSMISSION OF DATA BY A PRODUCT OVER A CELLULAR COMMUNICATIONS NETWORK WILL BE
UNINTERRUPTED, TIMELY, SECURE OR ERROR FREE, NOR DOES MULTITECH WARRANT ANY CONNECTION OR ACCESSIBILITY TO ANY CELLULAR
COMMUNICATIONS NETWORK. MULTITECH WILL HAVE NO LIABILITY FOR ANY LOSSES, DAMAGES, OBLIGATIONS, PENALTIES, DEFICIENCIES, LIABILITIES,
COSTS OR EXPENSES (INCLUDING WITHOUT LIMITATION REASONABLE ATTORNEYS FEES) RELATED TO TEMPORARY INABILITY TO ACCESS A CELLULAR
COMMUNICATIONS NETWORK USING THE PRODUCTS.
The MultiTech products and the final application of the MultiTech products should be thoroughly tested to ensure the functionality of the MultiTech
products as used in the final application. The designer, manufacturer and reseller has the sole responsibility of ensuring that any end user product into
which the MultiTech product is integrated operates as intended and meets its requirements or the requirements of its direct or indirect customers.
MultiTech has no responsibility whatsoever for the integration, configuration, testing, validation, verification, installation, upgrade, support or maintenance
of such end user product, or for any liabilities, damages, costs or expenses associated therewith, except to the extent agreed upon in a signed written
document. To the extent MultiTech provides any comments or suggested changes related to the application of its products, such comments or suggested
changes is performed only as a courtesy and without any representation or warranty whatsoever.
Contacting MultiTech
Knowledge Base
The Knowledge Base provides immediate access to support information and resolutions for all MultiTech products. Visit http://www.multitech.com/kb.go.
Support Portal
To create an account and submit a support case directly to our technical support team, visit: https://support.multitech.com.
Pin Descriptions of Board to Board Connector........................................................................................................... 9
Logging into the MultiConnect OCG-E Gateway......................................................................................................... 21
Safety Notices and Warnings ...................................................................................................................................... 21
Radio Frequency (RF) Safety ..................................................................................................................................... 21
Securing Your Device ............................................................................................................................................... 23
Chapter 2 – Installing Gateways on the Developer Board....................................................................................... 24
Installing Gateways on the Developer Board ............................................................................................................. 24
Installing a MultiConnect OCG-E Gateway onto the Board ........................................................................................ 24
Installing a Universal Socket Communications Device onto the Board ...................................................................... 25
Installing a SIM Card onto the Board ......................................................................................................................... 25
Making Other Board Connections............................................................................................................................... 25
General Purpose Input Output (GPIO) Cable .............................................................................................................. 26
GPIO Connector Pin Out ............................................................................................................................................. 26
Before You Begin ...................................................................................................................................................... 31
PC Board Layout Guideline ......................................................................................................................................... 34
User Accessible Areas ............................................................................................................................................... 34
FCC Grant Notes.......................................................................................................................................................... 37
Grant Limitations ....................................................................................................................................................... 37
Antenna System Cellular Devices................................................................................................................................ 39
Approved Antenna Cable Parts ................................................................................................................................ 40
Antennas Available from Multi-Tech ......................................................................................................................... 41
Activating Accounts for Cellular Devices .................................................................................................................... 42
Cellular Approvals and Labeling Requirements ......................................................................................................... 42
Related Documentation .............................................................................................................................................. 45
Power Measurements................................................................................................................................................. 48
Powering Down Your Device ...................................................................................................................................... 48
Chapter 1 – Developer’s Kit and Developer’s Board
Overview
Welcome
Thank you for using the MultiConnect open communications gateway embedded (MultiConnect™ OCG-E)
developer’s kit. This guide describes how to use the kit to design, develop and test custom applications for your
business. This chapter describes the gateway product, the developer board, and other kit contents. It also includes
safety notices that you can include in your product’s documentation, if desired.
Product Overview
The MultiConnect™ OCG-E helps you quickly create custom applications. The gateway is made up of an open Linux
development environment and fully certified hardware. The gateway includes multiple interfaces (serial, USB,
Ethernet and SD card) and internal peripherals (including a cellular modem and a GPS receiver) in one, applicationready end user solution. This gateway is ideal for companies with hardware and software competencies and
provides maximum design flexibility.
Applications that require device networking capability can now reside directly on select Multi-Tech gateways. This
product brings together a cellular hardware development kit, Multi-Tech’s CoreCDP Linux distribution and a
complete Linux build environment, allowing you to quickly create custom applications. The MultiConnect OCG-E
gateway provides a flexible, quick and cost-effective way to bring your solution to market.
For detailed information about the CoreCDP Development Platform, please visit the Multi-Tech website at:
http://www.multitech.net/
The developer’s board is available without a cellular modem. You can also develop your solution by choosing an
MT100EOCG model that uses the standard you desire:
GPRS, by selecting the MT100EOCG-G2 model
HSPA or HSDPA, by selecting the MT100EOCG-H5 model
EV-DO Rev A, by selecting the MT100EOCG-EV3 model
For complete ordering details, see the section “Product Ordering Options” in this manual. An illustration of an
MT100EOCG gateway follows. Your gateway may look slightly different, depending on the type of model you select
(-G2, -H5, -EV3 or gateway without cellular modem).
Product Ordering Options
ProductDescriptionRegion
MT100EOCG-G22G, GPRS Embedded Open Communications
Gateway (OCG)
MT100EOCG-G2-GP2G, GPRS Embedded OCG with GPSGlobal
MT100EOCG-H53G, HSPA Embedded OCGGlobal
MT100EOCG-H5-GP3G, HSPA Embedded OCG with GPSGlobal
MT100EOCG-EV3-N33G, EV-DO Embedded OCG with GPS, VerizonUS
MT100EOCG-EV3-N163G, EV-DO Embedded OCG, AerisUS
MT100EOCG-EV3-GP N163G, EV-DO Embedded OCG with GPS, AerisUS
MT100EOCGOpen Communications Gateway without cellular
modem
MT100EOCG-GPOpen Communications Gateway without cellular
modem, with GPS
MT100EOCG-DKEmbedded OCG Developer Kit – Includes all cables
and Core CDP DVD
Global
Global
Global
Global
Developer’s Kit Contents
Use the MultiConnect OCG-E Developer’s Kit MT100EOCG-DK and the models described in this guide to develop
and evaluate your products and applications. This kit contains:
Four screws for mounting gateway to developer’s board
One Multi-Tech screwdriver
Developer’s Board Components
The developer board is an auxiliary board that helps you develop and debug products that use an embedded
MT100EOCG gateway. Using the developer board, you can connect the embedded MT100EOCG gateway to your
device.
The developer board provides multiple interfaces, such as USB, serial, Ethernet and SD card. The test points of key
signals are led out on the developer board. In addition, the board is designed with switches or pins of commonly
used signals such as the reset signal and the enable signal for converting the working state of the gateway. You can
use the board to test the performance of the gateway.
You can implement both the wired connection test and the wireless connection test (connect the gateway model
to the antennas). You can also test the signal points when you maintain and repair the gateway.
The board provides two, universal socket connectors that give you the option to develop and test your solutions
that might include Wi-Fi or other types of technologies.
9ADC0IAnalog-to-Digital converter Input. (0 to 3v).
10ADC2IAnalog-to-Digital converter Input. (0 to 3v).
11GPI7IGeneral-Purpose Input.
12GPI9IGeneral-Purpose Input.
13TDOOJTAG Data Output.
14NTRSTI/OJTAG Reset (Active Low).
15GPS-PPSOGPS PPS - Pulse Per Second.
16GPS-TXOGPS - Transmit Data.
17-DTR_1IData Terminal ready. The DTE uses the -DTR_1 line to signal to the
module that it is ready to accept communication. The signal is also
used to signal to the module to terminate communication (hangup).
18-RXD_1OReceived Data. The gateway uses the RXD1 line to send data to
the DTE and to send gateway responses to the DTE. In command
mode, -RXD1 data presents the gateway responses to the DTE.
19-TXD_1ITransmitted Data. The DTE uses the -TXD1 line to send data to the
gateway for transmission or to transmit commands to the
gateway. The DTE holds this circuit in mark state when no data is
being transmitted or during intervals between characters.
20-RTS_1I"Request to Sent (Active Low). -RTS1 signal is used for hardware
flow control. -RTS1 input ON (low) indicates that the DTE is ready
to send data to the device. In the command state, the device
ignores -RTS1.
21-DCD_1OData Carrier Detect (Active Low). DCD is controlled by processor.
You can program how DCD is set.
22-CTS_1OClear to Send (Active Low). -CTS_1 is controlled by the gateway to
indicate whether or not the gateway is ready to receive data from
the DTE on the -TXD_1 input signal.
23GPO4OGeneral-Purpose Output.
24GPO3OGeneral-Purpose Output.
25GPO2OGeneral-Purpose Output.
26GPO1OGeneral-Purpose Output.
2727 GND Logic Ground.
28-RESETIDevice Reset (with pull-up). The active low -RESET input resets the
device logic. -RESET is tied to VCC through a time-constant circuit
for proper reset of the device if -RESET is not being externally
driven.
29BATT-INIBattery Backup Input 3V.
30USBH_DPI/OUSB Host Data Positive. Positive pin of USB data pair.
All models of the MultiConnect OCG-E gateway share the following specifications. Specifications that are unique to
a particular model are documented in the chapter dedicated to the model.
To log into the MultiConnect OCG-E gateway and open the modem port, use SSH or the debug serial port.
1.To use SSH to log into the gateway:
The default IP address is 192.168.2.1.
The default username and password are: root and root.
2.To use the debug serial port:
The debug port serial settings are 115200 baud, 8N1, with no flow control.
The default username and password are: root and root.
Safety Notices and Warnings
This section describes safety statements that OEMs can use in their product documentation.
Radio Frequency (RF) Safety
Due to the possibility of radio frequency (RF) interference, it is important that you follow any special regulations
regarding the use of radio equipment. Follow the safety advice given below.
Operating your device close to other electronic equipment may cause interference if the equipment is
inadequately protected. Observe any warning signs and manufacturers’ recommendations.
Different industries and businesses restrict the use of cellular devices. Respect restrictions on the use of
radio equipment in fuel depots, chemical plants, or where blasting operations are in process. Follow
restrictions for any environment where you operate the device.
Switch OFF your wireless device when in an aircraft. Using portable electronic devices in an aircraft may
endanger aircraft operation, disrupt the cellular network, and is illegal. Failing to observe this restriction
may lead to suspension or denial of cellular services to the offender, legal action, or both.
Switch OFF your wireless device when around gasoline or diesel-fuel pumps and before filling your vehicle
with fuel.
Switch OFF your wireless device in hospitals and any other place where medical equipment may be in use.
Vehicle Safety
When using your device in a vehicle:
Do not use this device while driving.
Respect national regulations on the use of cellular devices in vehicles.
If incorrectly installed in a vehicle, operating the wireless device could interfere with the vehicle’ s
electronics. To avoid such problems, use qualified personnel to install the device. The installer should verify
the vehicle electronics are protected from interference.
Using an alert device to operate a vehicle’s lights or horn is not permitted on public roads.
UL evaluated this device for use in ordinary locations only. UL did NOT evaluate this device for installation in
a vehicle or other outdoor locations. UL Certification does not apply or extend to use in vehicles or outdoor
applications.
Device Maintenance
When maintaining your device:
Do not attempt to disassemble the device. There are no user serviceable parts inside.
Do not misuse the device. Follow instructions on proper operation and only use as intended. Misuse could
make the device inoperable, damage the device and/or other equipment, or harm users.
Do not apply excessive pressure or place unnecessary weight on the device. This could result in damage to
the device or harm to users .
Do not use this device in explosive or hazardous environments unless the model is specifically approved for
such use. The device may cause sparks. Sparks in explosive areas could cause explosion or fire and may
result in property damage, severe injury, and/or death.
Do not expose your device to any extreme environment where the temperature or humidity is high. Such
exposure could result in damage to the device or fire.
Do not expose the device to water, rain, or spilled beverages. It is not waterproof. Exposure to liquids could
result in damage to the device.
Do not place the device alongside computer discs, credit or travel cards, or other magnetic media. The
information contained on discs or cards may be affected by the device.
Using accessories, such as antennas, that MultiTech has not authorized or that are not compliant with
MultiTech's accessory specifications may invalidate the warranty.
If the device is not working properly, contact MultiTech Technical Support.
Handling Precautions
To avoid damage due to the accumulation of static charge, use proper precautions when handling any cellular
device. Although input protection circuitry has been incorporated into the devices to minimize the effect of static
Chapter 2 – Installing Gateways on the Developer
Board
Installing Gateways on the Developer Board
These topics describe how to install gateways on the developer board. You can install a Multi-Connect OCG-E
gateway or, optionally, a universal socket communications device.
Installing a MultiConnect OCG-E Gateway onto the Board
To install a MultiConnect OCG-E gateway:
1.Align the 80-pin connector on the bottom of the gateway with the 80-pin connector on the developer
board.
2.Press the 80-pin connector of the gateway firmly into the 80-pin connector on the developer board.
Ensure that the mounting holes on the ends of the gateway align with the four standoffs on the
developer board.
GPI pins are 5 V tolerant. GPI pins have a 10K pull-downs to ground. This increases the input current to 330 uA
from the standard 1uA.
GPO pins output range:
> 2.58 V@4ma is a high
<= .36 V @4ma is a low
Maximum current on a GPO pin is +25 mA not to exceed 70ma total for all 4 GPO.
GPIO11 / GPIO 12 and SPI/I2C pins:
These are directly connected to the processor.
If the pin is programmed as an output, the high is 2.9V minimum and low is 0.4V maximum with a maximum
current draw of 8 mA. If the pin is programmed as an input, a high must be greater than 2.3V and a low
must be less than 1V.
These pins also have an optional pull-up resistor with a range of 40k ohm to 190k ohm, with a typical value
of 75k ohm.
Otherwise the input leakage is 1 uA.
Additional hardware is needed to drive the I2E and SPI signals if any additional wire is added to the signals.
For the I2C there are bus repeaters available that would be suitable, for example, Texas Instruments
LEVEL-TRANSLATING I2C BUS REPEATER PCA9517.
For the SPI signal, any logic level buffer that works at 3.3V would work.
LED Signals
GPO1-GPO4,LED1, and LED4-LED6 are sourced from the same IC.
Each pin can source 25 mA, but all pins, 4 GPO and 4 LED, can only source 70 mA total. This means the
cumulative output current of those pins is limited by the maximum output current rating of the IC.
GPO1-4 each can drive +25 mA, but total for all four is 70 mA (25 mA * 4 = 100 mA, but it cannot drive
that much all at the same time). It also means that if the IC dies, then all of those outputs die.
LED2 is directly connected to the processor GPIO pin PA30 and has the same characteristics as GPIO11
and GPIO12. The default operation of LED2 in CoreCDP is as a Linux Status indicator.
LED3 is sourced by a LVC open drain buffer and has a max current draw of 32 mA. LED3 is directly
connected to the Link Status pin of the device and is therefore dedicated.
LED7 and LED8 are driven directly by the Ethernet PHY chip and can drive about 4 mA. They are usually
used for Ethernet speed, link, and activity indicators.
Restoring the U-Boot Memory or the Bootstrap Memory
If the U-boot memory or the bootstrap memory becomes corrupted, you can restore either of them.
Before You Begin
You need to short out a resistor to run internal boot code instead of code in bootstrap or u-boot memory. To do
this, find some tweezers that fit around the resistor. You also need to download a utility to help you restore
memory. To do so:
1.Download Atmel SAM-BA utility from the following location: http://www.atmel.com/tools/ATMELSAM-
BAIN-SYSTEMPROGRAMMER.aspx
2.Unzip the utility package onto your Linux development system.
Restoring Memory Overview
1.Power down.
2.Short out the R108 resistor by squeezing it with tweezers.
3.Restore power.
4.Remove tweezers from the resistor.
5.Restore the bootstrap memory or the u-boot memory. The following sections describe these steps in
greater detail.
Shorting the R108 Resistor
To access the internal boot code directly, first short the R108 resistor so the boot code and u-memory code do not
run.
1.Power off the device.
2.Locate the R108 resistor on the board. The following figure shows the location of the resistor.
3.Place tweezers around the R108 resistor and squeeze the resistor, to short it out.
This topic describes how to restore memory by using the Atmel SAM-BA utility, connecting with the hardware,
mounting the serial driver and restoring the bootstrap memory or u-boot memory.
1.If you have not already done so, download the Atmel SAM-BA utility and unzip the utility package onto
your Linux development system: http://www.atmel.com/tools/ATMELSAM-BAINSYSTEMPROGRAMMER.aspx
2.Connect the USB cable between Linux system and the MTEOCG hardware.
3.Mount the USB CDC serial driver as described in the topic for the Ubuntu operating system you are using.
Mounting USB CDC serial driver for Ubuntu version 9.10 and older
1.Log in with administrator rights.
2.If the usbserial and cdc_acm module is already running, unload it by using the following command:
Adhere to engineering noise-suppression practices when designing a printed circuit board (PCB). Noise suppression
is essential to the proper operation and performance of the modem and surrounding equipment.
Any OEM board design must consider both on-board and off-board generated noise that can affect digital signal
processing. Both on-board and off-board generated noise that is coupled on-board can affect interface signal levels
and quality. Noise in frequency ranges that affect modem performance is of particular concern.
On-board generated electromagnetic interference (EMI) noise that can be radiated or conducted off-board is
equally important. This type of noise can affect the operation of surrounding equipment. Most local government
agencies have certification requirements that must be met for use in specific environments.
Proper PC board layout (component placement, signal routing, trace thickness and geometry, and so on)
component selection (composition, value, and tolerance), interface connections, and shielding are required for the
board design to achieve desired modem performance and to attain EMI certification.
Other aspects of proper noise-suppression engineering practices are beyond the scope of this guide. Consult noise
suppression techniques described in technical publications and journals, electronics and electrical engineering text
books, and component supplier application notes.
PC Board Layout Guideline
In a 4-layer design, provide adequate ground plane covering the entire board. In 4-layer designs, power and ground
are typically on the inner layers. Ensure that all power and ground traces are 0.05 inches wide.
The recommended hole size for the device pins is 0.036 in. +/-0.003 in. in diameter. Use spacers to hold the device
vertically in place during the wave solder process.
All creepages and clearances for the device meet requirements of safety standards listed in the technical
specifications. The requirements are based on a working voltage of 125V or 250V. When implementing the
recommended DAA* circuit interface in a third party design, strictly follow all creepage and clearance
requirements to meet safety standards. The third party safety design must be evaluated by the appropriate
national agency according to the required specification.
User Accessible Areas
Based on where the third party design is marketed, sold, or used, it may be necessary to provide an insulating
cover over all TNV exposed areas. Consult with the recognized safety agency to determine the requirements.
Note: Even if the recommended design considerations are followed, there are no guarantees that a particular
system complies with all the necessary regulatory requirements. Make sure a qualified and recognized agency
evaluates specific designs. .
*DAA stands for Data Access Arrangement. DAA is the device's telephone line interface.
Mounting Hardware
When mounting modems to the board, use #4 or M2/M3 hardware.
The following guidelines are offered specifically to help minimize EMI generation. Some of these guidelines are the
same as, or similar to, the general guidelines. To minimize the contribution of device-based design to EMI, you
must understand the major sources of EMI and how to reduce them to acceptable levels.
Keep traces carrying high frequency signals as short as possible.
Provide a good ground plane or grid. In some cases, a multilayer board may be required with full layers for
ground and power distribution.
Decouple power from ground with decoupling capacitors as close to the device's power pins as possible.
Eliminate ground loops, which are unexpected current return paths to the power source and ground.
Decouple the telephone line cables at the telephone line jacks. Typically, use a combination of series
inductors, common mode chokes, and shunt capacitors. Methods to decouple telephone lines are similar to
decoupling power lines; however, telephone line decoupling may be more difficult and deserves additional
attention. A commonly used design aid is to place footprints for these components and populate as
necessary during performance/EMI testing and certification.
Decouple the power cord at the power cord interface with decoupling capacitors. Methods to decouple
power lines are similar to decoupling telephone lines.
Locate high frequency circuits in a separate area to minimize capacitive coupling to other circuits.
Locate cables and connectors to avoid coupling from high frequency circuits.
Lay out the highest frequency signal traces next to the ground grid.
If using a multilayer board design, make no cuts in the ground or power planes and be sure the ground
plane covers all traces.
Minimize the number of through-hole connections on traces carrying high frequency signals.
Avoid right angle turns on high frequency traces. Forty-five degree corners are good; however, radius turns
are better.
On 2-layer boards with no ground grid, provide a shadow ground trace on the opposite side of the board to
traces carrying high frequency signals. This will be effective as a high frequency ground return if it is three
times the width of the signal traces.
Distribute high frequency signals continuously on a single trace rather than several traces radiating from
one point.
Electrostatic Discharge Control
Handle all electronic devices with precautions to avoid damage due to the static charge accumulation.
See the ANSI/ESD Association Standard (ANSI/ESD S20.20-1999) – a document “for the Development of an
Electrostatic Discharge Control for Protection of Electrical and Electronic Parts, Assemblies and Equipment.” This
document covers ESD Control Program Administrative Requirements, ESD Training, ESD Control Program Plan
Technical Requirements (grounding/bonding systems, personnel grooming, protected areas, packaging, marking,
equipment, and handling), and Sensitivity Testing.
MultiTech strives to follow these recommendations. Input protection circuitry is incorporated in MultiTech devices
to minimize the effect of static buildup. Take precautions to avoid exposure to electrostatic discharge during
handling.
MultiTech uses and recommends that others use anti-static boxes that create a faraday cage (packaging designed
to exclude electromagnetic fields). MultiTech recommends that you use our packaging when returning a product
and when you ship your products to your customers.
The OEM should follow all the grant notes listed below. Otherwise, further testing and device approvals may be
necessary.
The antenna gain, including cable loss, for the radio you are incorporating into your product design must not
exceed the requirements at 850 MHz and 1900 MHz as specified by the FCC grant for mobile operations and fixed
mounted operations as defined in 2.1091 and 1.1307 of the FCC rules for satisfying RF exposure compliance. Power
output listed is conducted.
This device is a mobile device with respect to RF exposure compliance. The antenna(s) used for this transmitter
must be installed to provide a separation distance of at least 20 cm from all persons, and must not be collocated or
operate in conjunction with any other antenna or transmitter except in accordance with FCC multi-transmitter
product guidelines. Installers and end-users must be provided with specific information required to satisfy RF
exposure compliance for installations and final host devices. (See note under Grant Limitations.) Compliance of this
device in all final host configurations is the responsibility of the Grantee.
Grant Limitations
This device has been granted modular approval for mobile applications. Portable applications may require further
RF exposure (SAR) evaluations. Examples of mobile devices include wireless routers, desktop computers, utility
meters, etc. Examples of portable applications include devices such as a laptop, USB dongle, mobile phone, tablet
PC, and any device that can be worn on the body during use.
Your final product with this embedded device may need to pass FCC Part 15B.
This device has not been evaluated or approved for simultaneous transmission. Any simultaneous transmission
conditions should be evaluated per the current FCC KDB 447498 requirements. Simultaneous transmission
requirements for mobile devices are contained in Section 8.
KDB 447498 Section 8
Transmitters and modules certified for mobile or portable exposure conditions and categorically excluded by §
2.1091(c) can be incorporated in mobile host devices without further testing or certification when:
The closest separation among all simultaneous transmitting antennas is ≥ 20 cm;
or
The antenna separation distance and MPE compliance boundary requirements that enable all simultaneous
transmitting antennas incorporated within the host to comply with MPE limits are specified in the application
filing of at least one of the certified transmitters incorporated in the host device. In addition, when
transmitters certified for portable use are incorporated in a mobile host device the antenna(s) must be ≥ 5 cm
from all other simultaneous transmitting antennas. All antennas in the final product must be at least 20 cm
from users and nearby persons.
If the host device requires further authorization, consult an accredited FCC laboratory for guidance.
FCC Definitions
Portable: (§2.1093) — A portable device is defined as a transmitting device designed to be used so that the
radiating structure(s) of the device is/are within 20 centimeters of the body of the user.
Mobile: (§2.1091) — A mobile device is defined as a transmitting device designed to be used in other than fixed
locations and to generally be used in such a way that a separation distance of at least 20 centimeters is normally
maintained between the transmitter’s radiating structure(s) and the body of the user or nearby persons.
Host Labeling
The following statements are required to be on the host label:
This device contains FCC ID: {Add the FCC ID of the specific device}
This device contains equipment certified under IC ID: {Add the IC ID of the specific device}
For labeling examples, see Cellular Approvals and Labeling Requirements.
The cellular/wireless performance depends on the implementation and antenna design. The integration of the
antenna system into the product is a critical part of the design process; therefore, it is essential to consider it early
so the performance is not compromised. If changes are made to the device's certified antenna system, then
recertification will be required by specific network carriers.
The antenna system is defined as the UFL connection point from the device to the specified cable specifications
and specified antenna specifications.
CDMA Antenna Requirements/Specifications
CategoryDescription
Frequency range824 – 894 MHz / 1850 – 1990 MHz
Impedance50 Ohms
VSWRVSWR shall not exceed 2.0:1 at any point across the
bands of operation
Typical radiated gain (to meet PTCRB)0 dBi on azimuth plane / 2 dBi on azimuth plane
Maximum radiated gain allowed by FCC10 dBi on azimuth plane /8.9 dBi on azimuth plane
RadiationOmni-directional .
PolarizationVertical
TRP/TISThe total radiated power (TRP) at the antenna shall be
no less than +21/20 dBm for PCS/CELL channels
respectively, and the total isotropic sensitivity (TIS) at
the antenna shall be no less than -104/104 dBm for
PCS/CELL channels respectively
GSM/EGSM Antenna Requirements/Specifications
CategoryDescription
Frequency Range824—960 MHz / 1710—1990 MHz
Impedance50 Ohms
VSWRVSWR should not exceed 2.0:1 at any point across the bands of operation
6.9 dBi on azimuth plane /3.1 dBi on azimuth planes
Page 40
CELLULAR INFORMATION
CategoryDescription
TRP/TISIncluding cable loss the total radiate power (TRP) at the antenna can be no less than
+22/24.5 dBm for 850/1900 MHz respectively, and the total isotropic sensitivity (TIS)
at the antenna can be no less than -99/101.5 dBm for 850/1900 MHz respectively.
SMA-to-UFL and RSMA-to-UFL Coaxial Cables
Your product includes the following cables:
Two SMA-to-UFL cables.
One RSMA-to-UFL cable for use with products that include a GPS receiver.
RSMA-to-MMCX for socket modem, if needed.
Note:
RSMA cables are not supported for CDMA products.
Coaxial Cable Specifications
Cable TypeCoaxial Cable
Attenuation<1.0db
Connector Impedance50 ohm
Maximum Cable Length16" (40 cm)
The SMA bulkhead can also be an RSMA bulkhead if RSMA cables are supported by your product.
Optional antenna cables can be ordered from Multi-Tech Systems, Inc.
Some Multi-Tech products have been pre-configured to operate on a specific cellular network. However, before
you can begin to use the modem, you must set up a cellular data account with your cellular network provider.
Refer to Multi-Tech’s Cellular Activation Web site http://www.multitech.com/activation.go for information on
activating your cellular modem.
The cellular carrier asks you for device identification information:
For CDMA: The modem's MEID is printed on the label.
For EV-DO, the modem’s MEID is printed in hexadecimal format on the label.
For GPRS/HSPA+: The modem's 15-character IMEI (International Mobile Equipment Identity) number is
printed on the modem's label.
Refer to the device labels for the location of the device identification.
IMPORTANT: When the cellular carrier asks you to provide the modem's model identification, give them the MultiTech model identification, not the host device model number. The Multi-Tech model identification allows the
carrier to verify the modem as one of its approved models. This information is located on the modem's label.
Cellular Approvals and Labeling Requirements
Approvals and Certification
The Multi-Tech SocketModem used in the product is an industry or Carrier Approved modem. In most cases, when
integrated and used with an antenna system that was part of the Multi-Tech modem certification, no additional
approvals or certifications are required (however, EV-DO has a few exceptions) for the device you develop as long
as the following are met:
The antenna system cannot be altered.
Model Identification The Multi-Tech model identification allows the carrier to verify the modem as one of its
approved models. This information is located on the modem's label.
The MT100EOCG-EV3 model is a 3G model supporting CDMA EV-DO Rev A and below. Based on industry-standard
open interfaces, the MT100EOCG-EV3 model is equipped with dual-band 800/1900 MHz bands with receive
diversity support on both bands. Use this model to design and develop solutions for CDMA networks.
Related Documentation
Use the EV-DO AT Commands to configure the MT100EOCG-EV3 model. These commands are documented in the
EV-DO and CDMA AT Commands Reference Guide part number S000546x. You can download this manual from the
Multi-Tech website. http://www.multitech.com/en_US/DOCUMENTS/Collateral/Manuals/
MT100EOCG-EV3 Specifications
CategoryDescription
General
Performance3G EV-DO
Frequency BandsDual band 800/1900 MHz
Speed
Data Speed3.1 Mbps downlink, 1.8 Mbps uplink
Interface
USBUSB 2.0 high speed compliant
Physical Description
Weight1.536 oz
43.5 g
Dimensions3.15 in x 1.375 in
80.010 mm x 34.93 mm
Connectors
AntennaAll models have surface mount UFL antenna connectors.