all | frequencies |
|
|
|
|
|
exhibits | applications |
---|---|---|---|---|---|---|---|---|
manuals |
app s | submitted / available | |||||||
---|---|---|---|---|---|---|---|---|
1 |
|
Users Manual 1 | Users Manual | 38.93 KiB | November 05 2006 | |||
1 |
|
Users Manual 2 | Users Manual | 66.40 KiB | November 05 2006 | |||
1 |
|
Users Manual 3 | Users Manual | 186.28 KiB | November 05 2006 | |||
1 |
|
Users Manual 4 | Users Manual | 679.57 KiB | November 05 2006 | |||
1 |
|
Users Manual 5 | Users Manual | 1.85 MiB | November 05 2006 | |||
1 | Cover Letter(s) | November 05 2006 | ||||||
1 | Cover Letter(s) | November 05 2006 | ||||||
1 | External Photos | November 05 2006 | ||||||
1 | ID Label/Location Info | native | November 05 2006 | |||||
1 | Internal Photos | November 05 2006 | ||||||
1 | Cover Letter(s) | November 05 2006 | ||||||
1 | RF Exposure Info | November 05 2006 | ||||||
1 | Test Report | November 05 2006 | ||||||
1 | Test Report | November 05 2006 | ||||||
1 | Test Report | November 05 2006 | ||||||
1 | Test Setup Photos | November 05 2006 |
1 | Users Manual 1 | Users Manual | 38.93 KiB | November 05 2006 |
Created on 05/05/2006 Prism TM2 Teletrac Prism TM2 Information and Installation Desired Learning Outcomes At the conclusion of this module you will:
Know the physical components that make up a Prism TM2 installation
Know the current feature set of the Prism TM2
Know the components and processes used to acquire and transmit Prism TM2 information
Know the requirements and processes to install and test a Prism TM2 Teletrac, Inc. - Prism TM2 Information and Installation Guide KEY PERFORMANCE INDICATORS With no direct supervision and with written guidelines, the Prism TM2 installer will be able to:
Describe the peripheral equipment used in a Prism TM2 installation TM2 location
Identify the internal components that make up a Prism
Describe the method of how a Prism TM2 determines its
Identify what the Prism TM2 communicate when different systems are hindered information
List current features of the Prism TM2
List the steps to replace a VLUplus with a Prism TM2
List the steps to initially install a Prism TM2 can 2 1622-0300 B1 5/05/06 Teletrac, Inc. - Prism TM2 Information and Installation Guide Table of Contents Introduction .................................................................................................................................................. 4 Physical characteristics................................................................................... Error! Bookmark not defined. PRISM TM2 ..........................................................................................ERROR! BOOKMARK NOT DEFINED. ANTENNAS ...........................................................................................ERROR! BOOKMARK NOT DEFINED. PERIPHERALS .......................................................................................ERROR! BOOKMARK NOT DEFINED. The GPS and GPRS Systems.......................................................................... Error! Bookmark not defined. GLOBAL POSITIONING SYSTEMS (GPS)................................................ERROR! BOOKMARK NOT DEFINED. GPRS...................................................................................................ERROR! BOOKMARK NOT DEFINED. THE OVERALL TELETRAC PICTURE ......................................................ERROR! BOOKMARK NOT DEFINED. SUBSCRIBER IDENTITY MODULE (SIM) CARD .....................................ERROR! BOOKMARK NOT DEFINED. Prism TM2 Functionality................................................................................ Error! Bookmark not defined. DEFAULT SETTINGS..............................................................................ERROR! BOOKMARK NOT DEFINED. Feature Comparison........................................................................................ Error! Bookmark not defined. COMPARISON CHART ...........................................................................ERROR! BOOKMARK NOT DEFINED. PRISM TM2 FEATURES DEFINED .........................................................ERROR! BOOKMARK NOT DEFINED. Long Inbound Messaging ........................................................................ Error! Bookmark not defined. Scheduled Locations................................................................................ Error! Bookmark not defined. In Motion detection.................................................................................. Error! Bookmark not defined. Speed Threshold ...................................................................................... Error! Bookmark not defined. Dynamic Power Management ................................................................. Error! Bookmark not defined. Message Store and Forward (Message History) ..................................... Error! Bookmark not defined. PRISM TM2 Installation Instructions .......................................................... Error! Bookmark not defined. PRE-INSTALLATION CONSIDERATIONS ....................................ERROR! BOOKMARK NOT DEFINED. ITEMS REQUIRED FOR PRISM TM2 INSTALLATION.............................ERROR! BOOKMARK NOT DEFINED. WIRING SCHEMATIC.............................................................................ERROR! BOOKMARK NOT DEFINED. ANTENNA PLACEMENT.........................................................................ERROR! BOOKMARK NOT DEFINED. PRISM TM2 INSTALLATION PROCEDURES.........................................ERROR! BOOKMARK NOT DEFINED. SWAPPING OUT A PRISM TM2...............................................................ERROR! BOOKMARK NOT DEFINED. Prism TM2 Administration & Provisioning.................................................. Error! Bookmark not defined. Appendix A An Introduction to Global Positioning Satellite Systems..... Error! Bookmark not defined. Appendix B Teletrac Prism TM2 Antennas............................................... Error! Bookmark not defined. Appendix C Installation Equipment ........................................................... Error! Bookmark not defined. Appendix D How Messages Are Used In Scripts ....................................... Error! Bookmark not defined. Appendix E FCC Statement ........................................................................ Error! Bookmark not defined. Appendix F - Safety Information ................................................................... Error! Bookmark not defined. 1622-0300 B2-5 05 2006 3 Teletrac, Inc. - Prism TM2 Information and Installation Guide INTRODUCTION Welcome to Teletracs Prism TM2 Information and Installation Guide. The goal of this guide is to give you an understanding of how the Prism TM2 functions and how the different systems it uses function, as well as, how to install the Prism TM2 itself. As you make your way through this guide, you will start to become familiar with many aspects of the Prism TM2, however, nothing will replace the hands-on experience of installing a unit and seeing how it functions in person. It is hoped that you will use this guide as a reference to give you guidance whenever a problem is encountered. This guide starts with a discussion of the physical characteristics of the Prism TM2 and the equipment it requires to function. Next is a brief introduction to the systems the Prism TM2 relys upon to do its job. After that will be a feature list to compare the Prism TM2 to an RF & CDPD VLU along with descriptions of the features. Lastly is a section on how to install and test the Prism TM2. Now, lets get going 4 1622-0300 B1 5/05/06
1 | Users Manual 2 | Users Manual | 66.40 KiB | November 05 2006 |
Teletrac, Inc. - Prism TM2 Information and Installation Guide
--------------Unit One--------------
PHYSICAL CHARACTERISTICS PRISM TM2 The Prism TM2 is a custom built transceiver made for Teletrac. The device is a black ABS plastic box roughly the same size as a small CD carrying case. Internally it consists of a GPRS modem, a GPS receiver, a controller board and a SIM card. The GPRS modem and GPS receiver are basically off-the-shelf devices. Its the SIM card that makes this product unique. The SIM (subscriber identity module) card is a small electronic board that contains the personality of the unit. The SIM is a programmable card that can easily be moved from one unit to the next so that in the event of hardware failure the card can be remove and placed in a new unit without any reprogramming. SIM cards and the GPRS system run on the GSM network which is considered to be one of the most secure communication systems since both data and voice are encrypted to prevent eavesdropping. See Section Two for more information about how GSM, GPRS and SIM cards work. In theory, the Prism TM2 should work about the same as a VLUplus. It has been purposefully designed to have a similar wiring scheme and to use the same installed peripherals. See Unit Five for installation information. Teletrac, Inc. - Prism TM2 Information and Installation Guide ANTENNAS The Prism TM2 uses a hidden combo antenna or roof mount combo antenna. In the future there will be more antenna options once the physical connector has changed. PERIPHERALS Combo Hidden Antenna Roof Mount combo Antenna MDT The Prism TM2 is designed to use the same peripherals or accessories that the RF and CDPD VLU and previous GPRS units uses. In addition to the same peripherals, the Prism TM2 currently has two inputs and one outputs. Input 0 is configured to work with ignition on/off and inputs 1 &
2 allow for the connection of PTOs. 1622-0300 B2-5 05 2006 2
1 | Users Manual 3 | Users Manual | 186.28 KiB | November 05 2006 |
Teletrac, Inc. - Prism TM2 Information and Installation Guide
--------------Unit Two--------------
THE GPS AND GPRS SYSTEMS There are two systems that the Prism TM2 uses outside of the Teletrac system. One is the Global Positioning System, more commonly called GPS and the other is the General Packet Radio System otherwise known as GPRS. The following pages will give you a basic introduction to where these systems came from as well as how they work. At the end of this section will be a summary of how Teletrac uses these two systems together to get the location of a vehicle. GLOBAL POSITIONING SYSTEMS (GPS) The following information was taken from information posted to the Teletrac Intranet. Included here is the abridged version of GPS. The full text appears in Appendix A at the end of this Information Guide. AN INTRODUCTION TO GLOBAL POSITIONING SATELLITE SYSTEMS Global Positioning Systems GPS uses "man-made stars" or satellites as reference points to calculate positions on Earth accurate to within meters. In fact, with advanced forms of GPS you can make measurements to better than a centimeter. In a sense, it's like giving every square meter on the planet a unique address. Since GPS receivers have been miniaturized to just a few integrated circuits and have become very economical, the technology has become increasingly accessible. Here's how GPS works in five logical steps:
Here is a summary of each of the steps involved with GPS in order to determine a location. This is the first part of Teletrac finding the locations of vehicles using a Prism TM2. Once a location is determined then it is sent via another system. We'll explain each of the following points in the next five sections. 1. The basis of GPS is "triangulation" from satellites. 2. To "triangulate," a GPS receiver measures distance using the travel time of radio signals. 3. To measure travel time GPS needs very accurate timing, which it achieves with some tricks. Teletrac, Inc. - Prism TM2 Information and Installation Guide 4. Along with distance, you need to know exactly where the satellites are in space. High orbits and careful monitoring are the secret. 5. Finally you must correct for any delays the signal experiences as it travels through the aTM2osphere. Step 1: Triangulating from Satellites Improbable as it may seem, the whole idea behind GPS is to use satellites in space as reference points for locations here on earth. That's right, by very, very accurately measuring our distance from three satellites we can "triangulate" our position anywhere on earth. Step 2: Measuring Distance from a Satellite a s en , se the arrive at our receiver. ow long it takes for a signal sent from the satellite to But how can you measure the distance to something that's floating around in space? We do it by timing h THE BIG IDEA, MATHEMATICALLY In in high school. Remember the old: "If a car go travel.?"
Velocity (60 mph) x Time (2 hours) = Distance (120 miles) In the case o light, or roughly 186,000 miles per second. le thing boils down to those "velocity times travel time" math problems we did es 60 miles per hour for two hours, how far does it f GPS we're measuring a radio signal so the velocity is going to be the speed of who Step 3: Getting Perfect Timing ng the travel time of a radio signal is the key to GPS, then our stop watches had better because if their timing is off by just a thousandth of a second, at the speed of light, If measuri be darn good that translates into almost 200 miles of error!
The secret to perfect timing is to make an extra satellite measurement. That's right, if three perfect measurements ca imperfect measurements can do the same thing. n locate a point in 3-dimensional space, then four 1622-0300 B2-5 05 2006 2 Teletrac, Inc. - Prism TM2 Information and Installation Guide le point (which is o ct with the first three. uld intersect at a sing EXTRA MEASUREMENT CURES TIMING OFFSET If everything were perfect (i.e. if our receiver's clocks were perfect) then all of our satellite ranges wo ur position). But with imperfect clocks, a fourth measurement, done as a cross-check, will NOT interse So the receiver's computer says "Uh-oh! There is a discrepancy in my measurements. I must not be perfectly synced with universal time."
Since any offset from universal time will affect all of our measurements, the re ceiver looks for a single correction factor that it can subtract from all its timing measurements that would cause them all to intersect at a single point. That correction brings the receiver's clock back into sync with universal time, and bingo! - you've got atomic accuracy time right in the palm of your hand. Once it has that correction it applies precise positioning. to all the rest of its measurements, and now we've got Step 4: Kno wing Where a Satellite is in Space all GPS receivers have an almanac programmed into their computers that tells the sky each satellite is, moment by moment. On the ground them where in CONSTANT MONITORING ADDS PRECISION The basic orbits are quite exact but just to make things perfect, the GPS satelli m onitored by the DeparTM2ent of Defense. tes are constantly They use very precise radar to ch eck each satellite'
s exact altitude, position and speed. 1622-0300 B2-5 05 2006 3 Teletrac, Inc. - Prism TM2 Information and Installation Guide GETTING THE MESSAGE OUT Once the DoD has measured a satellite's exact position, they relay that information back up to the satellite itself. The satellite then includes this new corrected position information in the timing signals it's broadcasting. Step 5: Correcting Errors ROUGH TRIP THROUGH THE ATM2OSPHERE First, one of the basic assumptions we've been using throughout this tutorial is not exactly true. We've been saying that you calculate distance to a satellite by multiplying a signal's travel time by the speed of light. But the speed of light is only constant in a vacuum. As a GPS signal passes through the charged particles of the ionosphere and then through the water vapor in the troposphere it gets slowed down a bit, and this creates the same kind of error as bad clocks. 1622-0300 B2-5 05 2006 4 Teletrac, Inc. - Prism TM2 Information and Installation Guide ROUGH TRIP ON THE GROUND Trouble for the GPS signal doesn't end when it gets down to the ground. The signal may bounce off various local obstructions before it gets to our receiver. This is called multipath error and is similar to the ghosting you might see on a TV. Good receivers use sophisticated signal rejection techniques to minimize this problem. PROBLEMS AT THE SATELLITE The atomic clocks they use are very, very precise but they're not perfect. Minute discrepancies can occur, and these translate into travel time measurement errors. SOME ANGLES ARE BETTER THAN OTHERS There are usually more satellites available than a receiver needs to fix a position, so the receiver picks a few and ignores the rest. If it picks satellites that are close together in the sky the intersecting circles that define a position will cross at very shallow angles. That increases the gray area, or error margin, around a position. Commonly refered to as HDOP. If it picks satellites that are widely separated, the circles intersect at almost right angles and that minimizes the error region. 1622-0300 B2-5 05 2006 5 Teletrac, Inc. - Prism TM2 Information and Installation Guide Intentional Errors!
as it may be to believe navigation system in t
, the same government that spent $12 billion to develop the most As hard accurate he world can cause errors by intentionally degrading its accuracy. The policy is called "Selective Availability" or "SA" and the idea behind it is to make sure that no hostile force or terrorist group can use GPS to make accurate weapons. Basically the DoD introduces some "noise" into the satellite's clock data which, in turn, adds noise
(or inaccuracy) into position calculations. The DoD may also be sending slig htly erroneous orbital data to the satellites which they transmit back to receivers on the ground as part of a status message. Together these factors make SA the biggest single source of inaccuracy in the system. Military receivers us Note: As of Spring 2000, the DoD eliminated the intentional error in the calculation, however, this may come back at any time. e a decryption key to remove the SA errors and so they're much more accurate. The Bottom Line tely, all of these inacc uracies still don't add up to much of an error, and a form of GPS Fortuna called "Differential GPS" can significantly reduce these problems. PRS G nd system used by the Prism TM2 is the General Packet Radio System, more The seco commonly called GPRS. This system is meant to be an invisible link from a mobile unit, such as a wireless modem, to land line systems. The next few pages will give you an introduction to GPRS and how it works to transmit information. The following information was taken from information posted to http://www.rysavy.com/Articles/GPRS2/gprs2.hT http://www.geocities.com/mobile4g/gprs.hTM2l. AN INTRODUCTION TO GENERAL PACKET RADIO SERVICE and M2l What is GPRS?
ffers packet-switche faster and easier In d connections to data networks via mobile technology. It is designed GPRS o to allow ternet access with continuous connectivity, and enables applications including multimedia messaging, wireless corporate intranet, remote control and maintenance of appliances. It is also considered part of the migration to third generation (3G) mobile networks. The advantages of GPRS technology allows users to stay connected to the Internet by using packet switching technology, providing faster downloads as no time is spent attempting to access a dial-up connection. How does GPRS work?
ransports packets between mo GPRS t X.25, though with the Internet's popularity, operators and device vendors will probably emphasize IP. Mobile devices will have an IP address, either static or dynamic, and, once on the network, I P packets can originate from mobile devices and travel to external networks, such as the Internet or privately connected intranets. IP packets from external networks will reach mobile devices, even bile devices and packet networks. Packets can be IP or 1622-0300 B2-5 05 2006 6 Teletrac, Inc. - Prism TM2 Information and Installation Guide when moving. GPRS doesn't care what protocols operate above IP. This indifference enables all standard Internet protocols to operate, including TCP, UDP, HTTP, Secure Sockets Layer (SSL), and IPSec. GPRS uses two essential new infrastructure elements, the Serving GPRS Support Node (SGSN) and Gateway GPRS Support Node (GGSN). The SGSN, which connects to base-station controllers, tracks the mobile station's location and sends data packets to and from the mobile ay to station. It forwards packets using a tunneling protocol to the GGSN, which acts as a gatew external networks, such as the Internet or private intranets. An operator will have multiple SGSN for different service areas, but needs only one GGSN for each external network it interconnects with. The GGSN assigns IP addresses to mobile stations, and IP packets from external networks route to the GGSN, which tunnels them to the appropriate SGSN for delivery to the mobile station. s o users actually connect to the network and send Architecture and protocols are fine, but how d data, and how does the network keep track of users as they move around? When users turn on the GPRS device (GPRS PC Card modem) in a GPRS coverage area, the device first registers with the network and then requests a Packet Data Protocol (PDP) context. The PDP context activates an IP address for the device, generally a dynamic address assigned by the GGSN. At this stage the device can send and receive data. s requests using a packet random-access To actually send a packet of data, the device make channel. Channels are logical data paths consisting of predefined time slots in select GPRS radio channels, and are the primary mechanism in the MAC layer. The network responds by assigning a data-traffic channel for a temporary period sufficient to send the data packet. GPRS networks use 200KHz radio channels, with each channel divided into eight time slots. Each time slot can support 13Kbits/sec of throughput in today's networks (though options exist to increase data rate to over 20Kbits/sec), and so actual user throughput will depend on the number of time slots a user's device can handle and the particular service options from the carrier. s w base station's To support mobility, the GPRS device informs the SGSN when it's within a ne coverage range. If the user travels out of one SGSN's coverage to another, then the old SGSN and the new SGSN must collaborate and inform the GGSN of the user's new location. Users w ill also be able to roam into networks operated by other GPRS carriers. T HE OVERALL TELETRAC PICTURE Now that you have an understanding of GPS and GPRS, lets talk about how Teletrac uses these systems in order to provide location an d messaging services to our customers. In Unit One we talked about the components that make up the Prism TM2, now lets talk about how those components work together. As shown in the diagram, a computer ent connects to the Teletrac NCC via the Internet. The NCC is where customer databases are stored and where location requests are processed. From there, the NCC contacts the customers vehicles via the Internet. The vehicles that use customer running CDPD Site GPRS Site eCli the VLUplus or VLU-G eClient eClient all GPS Satellite Internet Internet Teletrac NCC Radio Tower RF VLU 1622-0300 B2-5 05 2006 The three types of location systems Teletrac uses 7 Teletrac, Inc. - Prism TM2 Information and Installation Guide GPRS Communication to NCC Satellite When receiver will determine GPS to determine their location send that information directly to the NCC and it is in turn sent back to the eClient workstation. The GPS receiver built into the Prism TM2 works to determine the location of itself. As long as the receiver is able to see enough satellites it can tell the Prism TM2 where it is. If a vehicle drives into an underground garage, inside a warehouse or even under an overpass, the receiver may not be able to see enough, if any, satellites to determine its location. Since the signals coming from the satellites to the receiver are very low they can easily be blocked, even dense cloud cover can reduce the actual signal. The GPS its location every few seconds and store the the Prism TM2 information. Controller is contacted through the GPRS modem, the Controller contacts the GPS receiver and a request is made for its location at a certain time. Once the Controller receives the location information from the GPS receiver, it relays the locate to the Teletrac NCC via the GPRS modem. Even if the GPRS modem cannot be contacted by the NCC, the GPS receiver is still collecting the information on where it is located. When the GPRS modem is able to communicate with the NCC, the Prism TM2 will download the location information that the GPS receiver has been providing. Now, lets say your driver is taking a lunch break under the awning of a drive-up restaurant. In this location the GPS receiver probably cannot see enough satellites to determine its location. In this event, when the controller requests a locate from the GPS receiver, the last known location will be used. Since the receiver takes its own readings every few seconds the last known location is probably just outside the restaurant awning. When its time to send in a locate to the NCC, the Prism TM2 can still pick up the GPRS modem and contact the NCC. But, the only location that will be returned is the last known location reported to the Prism TM2 Controller, which was probably just outside the awning. This location will be reported as a poor quality locate and display as the last known location. Even though the GPS receiver is blocked, a dispatcher can still send messages to a driver. Since the messages travel over the GPRS system they will be sent to the Prism TM2 and simply a poor locate (last known location) will be returned to the dispatcher. Lastly, the Prism TM2 can be set up to store events such as ignition on/off, messages and location information when the GPRS modem is out of its coverage area. The events, messages and locations can be stored in a memory buffer and later transmitted once the modem is able to communicate. See the following chart to help explain what happens when each system is able to operate or is blocked. Location Unit GPRS Modem GPS Receiver Control Board 1622-0300 B2-5 05 2006 8
1 | Users Manual 4 | Users Manual | 679.57 KiB | November 05 2006 |
Teletrac, Inc. - Prism TM2 Information and Installation Guide PRISM 2 PRISM PRISM PRISM Can Locate, Message & Send Events Storing of Locations, Events &
Messages in a buffer to transmit later Can Message & Send Events, Last Known Good Location is Sent Store Events, Messages & Locates, Last Locate is sent to W/S SUBSCRIBER IDENTITY MODULE (SIM) CARD Each Subscriber Identity Module is programmed with specific identification features for a unique user, allowing the device that contains a module to be used for such things as online banking and purchasing that require a secure means of identification. They can be swapped between other GSM devices, so the Subscriber Identity Module owner isn't confined to a single device. Teletrac will use the SIM Cards as a quick way to move specific programming information from one location unit to another. The SIM Card will contain information such as location schedules, landmarks, service reminders etc. When the hardware of a locator unit goes bad an installer will replace the hardware and take the SIM Card from the broken device and place it in the new device. This will move all the programmed information and alleviate the need to reprogram units.
-
--Unit Three--------------
PRISM TM2 FUNCTIONALITY Teletrac, Inc. - Prism TM2 Information and Installation Guide The Prism TM2 is designed to behave the same way as the VLUplus unit and have the same features available. However, the Prism TM2 is not as programmable as the VLUplus. Instead of having a script, the Prism TM2 has a hard coded set of instructions that can have some small configuration changes. Below is a list of how the unit will act by default; changes to the configuration will be a future implementation. See Unit Four for a description of the features available, as well as, a feature comparison between all the Teletrac units. DEFAULT SETTINGS Power Management:
Default
----
Wait time until unit goes to sleep How long should it sleep When it wakes, how long should it wait to acquire GPS and CDPD signals Wait time between sending going to sleep message and actually going to sleep Will the units use Ignition On/Off messaging 4 hours 4 hours 4 minutes 6 minute
----
Y N New
----
Will the unit self locate when in coverage How will the unit be located? Workstation or Locate itself Location schedule when the vehicle locates itself
----
----
15 min / -- miles Y N Wkstn Itself Maximum speed limit Reminder message for exceeding the speed limit
(i.e. when a vehicle exceeds the speed limit you will get a message, then, every 5 min that the driver is speeding you will get another message.) Would you like to use Service Mileage?
Number of miles between services Number of miles to receive service reminder message 75 mph 5 minutes
----
3000 miles 50 miles Y N Will the units use Tow Away messaging If yes, how soon after the vehicle moves should a message be sent The Prism TM2 can also be programmed with landmarks, either rectangles or circles. When a vehicle goes into or out of the zone a message is sent in, no matter what time of day it is. Programming the unit with the Lat/Long of the center then either the radius of the circle or the distance North/South and East/West in meters creates a landmark. 60 seconds Y N
----
1622-0300 B2-5 05 2006 2 Teletrac, Inc. - Prism TM2 Information and Installation Guide
--------------Unit Four--------------
FEATURE COMPARISON Following is a chart to allow you to quickly see each of the features followed by a description of the feature. The chart and feature descriptions are broken down into RF VLU, VLUplus and Prism TM2 features. We will also go over how these features will be implemented to the field. COMPARISON CHART Feature Standard VLU VLUplus Prism Prism TM2 Feature Description Teletrac Towers GPS Locations CDPD Connections GPRS Connection Low Power Idle Current Dynamic Power Management Location Store and Forward Message Store Forward Event Store and Forward Peripherals Input Configuration Long Inbound Messaging Over-the-Air Programming X X X X X X
(optional) Built-in Link Diagnostics X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X to the Teletrac RF system of to determine locations and Uses towers transmit information. Uses Global Positioning System to determine locations only. Uses Cellular Digital Packet Data Systems locations, messages and events. Uses General Packet Radio System to transmit locations, messages and events, Draws a low amount of electricity and places less of a strain on vehicle resources. Allows for low power consumption transmit Can determine location and store for later transmission if out of coverage. Allows messages to be stored in the unit while out of the coverage area Can capture an output event such as ignition on/off and store it for later transmission if out of coverage. Can be used with other Teletrac equipment such as MDTs, SMTs, panic buttons and other Teletrac approved peripherals. RF VLU, VLUplus & PRISM TM2 can be wired for inputs such as ignition on/off, lift up/down, alarm activation, etc. Send long inbound messages without additional equipment added to the Teletrac system. Change characteristics by sending information over the airwaves. More comprehensive programming for the VLUplus. Diagnostics connection point. 1622-0300 B2-5 05 2006 3 Teletrac, Inc. - Prism TM2 Information and Installation Guide Scheduled Locations Scheduled Events In Motion Detection Zone Compliance Speed &
Heading Threshold Speed Time & Distance Events MDT Time Calibration X X X X X X X X X X X X X X X X X X X X X X X X Ability to perform locates based upon a schedule programmed into the unit and downloaded upon request to the workstation. This is in addition to the locates scheduled by the workstation Used to turn on/off timers or triggers such as Exception Conditions or Ignition on/off Can determine when it is in motion and act upon the information Send an alert exception condition has been thrown that a preprogram Send an alert that a preprogrammed speed or heading has been exceeded or changed its Unit can accurately determine actual speed using GPS system Send an alert when a specified time of day and week is reached or distance is traveled Time on the MDT is set by the unit automatically change depending on what time zone it is currently located in and will PRISM TM2 FEATURES DEFINED The Prism TM2 has many new features in addition to the features seen in the Standard units. Below is an explanation of these features. Long Inbound Messaging Long Inbound Messaging (LIM) is a feature that allows the Prism TM2 to send alphanumeric form fill messages that are longer than five form characters, up to 197 of free text or field characters. With LIM comes a larger amount of applications such as bar code readers, credit card readers, data terminals and driver identification can be supported. LIM requires a messaging terminal and optional keyboard. Scheduled Locations A vehicle is able to send locates to the dispatcher without the workstation sending a request. This means a vehicle can automatically send in a locate at the end of a designated amount of time or distance. Now, if a vehicle is in motion, you will get locates at a given interval no matter if the ignition is on or not. Further, the vehicle will send in located at a given interval if the ignition is on no matter if the vehicle is moving or not (i.e. idling). By having location schedules in the Prism TM2, the unit changes its own schedule through the condition of the vehicle and doesnt require a message with a status change be sent 4 Note: Scheduled Locations is not dependant upon what time of day it is, only what condition the vehicle is in. 1622-0300 B2-5 05 2006 Teletrac, Inc. - Prism TM2 Information and Installation Guide to the workstation in order to change its location schedule. Also, since a location schedule can also be stopped due to the vehicles condition (Ignition off and Not moving), a lot of unnecessary locates and locations requests are eliminated thereby, reducing airtime usage. 1622-0300 B2-5 05 2006 5 Teletrac, Inc. - Prism TM2 Information and Installation Guide For Example
< 4 mph 6 mph<
Stationary In Motion 1622-0300 B2-5 05 2006 6 Teletrac, Inc. - Prism TM2 Information and Installation Guide In Motion detection The Prism TM2 will be capable of detecting when the vehicle is stationary or moving with +/- 1 mph accuracy. Upon detecting either of the events, the Prism TM2 can send messages or begin timers. The ultimate goal of this feature is to eliminate locations unless the vehicle is moving or the ignition is on, which will save location units. (Min. detectable speed is 3 mph due to jitter) This feature can be used to perform several capabilities currently being done by Fleet Director but without the high rate of location requests and possibility of missed information. For example, this feature can be used as a security feature to determine if a vehicle is parked where is supposed to be without the use of Landmarks or Exception Conditions and the workstation does not have to locate the vehicle every 15 minutes to see if it is still stationary. With this feature the Prism TM2 will identify that it is stationary and send a message upon detecting movement. Once in motion, the Prism TM2 can send locates on a regular bases to keep the workstation up to date. This prevents the problems of unnecessary locations and status change requirements to get a different location. Since the Prism TM2 locates itself, there is no dropped/lost information. This feature may be used in place of the zone feature for security applications. Zone Compliance or Landmark Detection The feature of Zone Compliance is the capability to store a set of coordinates inside the Prism TM2 that make up an area called a zone. The Prism TM2 can then perform certain actions upon detecting where the vehicle is in relation to the zone. This function acts similar to Exception Conditions in the Fleet Director software depending on how it is programmed. Upon entering or leaving a zone, the Prism TM2 can send a message or change its operating condition. To most people it is obvious what zone compliance means due to the Fleet Directors current standards, but with the Prism TM2 having the internal zone capabilities, a whole new level of zone compliance is capable. A few examples of this new capability would be that by setting up a zone around a customers yard, the truck driver is no longer required to press an In Yard or Left Yard button. When set up around a customer site, the driver would no longer be required to send a message if he was at a site too long, nor would Fleet Director have to time the At Site condition or locate the vehicle to insure it is still there. And, when combined with the In Motion Detection feature, the customer would not have to locate his truck all night long to make sure it has not left the yard due to theft. In addition, since the GPS Receiver is locating itself continually, the Prism TM2 would send a message with the exact time of the event happening. This would eliminate the 15-minute error factor in Fleet Director. There are a maximum of three (3) zones that can be configured into each unit. A zone can either be a circle with a center and radius or a square with a center and distance to the edge. In order to determine a zone, you will need to find the Latitude and Longitude for the center of the zone. Next, determine the distance, in meters, from the center of the zone to its edge. Next, you will need to determine the Hysteresis. This is a gray area outside and inside the edges of the zone that will account for jitter in the locations. You will be able to select the size of the Hysteresis from 0 meters to 250 meters. Within the Hysteresis, you will not be considered inside or outside the zone. The vehicle will effectively be in No Mans Land. The Hysteresis can also be turned off so that the actual edges of the zone are used for the exception. Teletrac, Inc. - Prism TM2 Information and Installation Guide Speed Threshold A natural spin-off from time and distance is speed. The Prism TM2 can detect its own speed more accurately then Fleet Director (+/- 1 mph accuracy). Because of this, the Prism TM2 can detect speed violations thus alerting dispatch of possible violations or exception condition. Thresholds can be set in the Prism TM2 to trigger warning messages when the vehicle goes above a specific speed. Even more, a timer can be set to alert dispatch only if the threshold is detected for a required length of time. In order for the messages to be sent, the speed must pass through the set speed. Note: The actual speed must pass through the set speed in order to trigger the message. Note: Unit must have the following conditions in order to go to sleep:
Dynamic Power Management By default, the Prism TM2 is programmed with a robust interactive power management routine. This routine forces the Prism TM2 to periodically shut down its internal high current components
(the GPRS modem and the GPS receiver) while the vehicle ignition is OFF. This feature will decrease the Prism TM2 current consumption significantly. While these components are shut down, the workstation is incapable of setting up a communications link with the Prism TM2 for the requesting of location or the sending of messages. While the Prism TM2 is asleep the ability to send messages from the MDT and do vehicle status changes (in motions, input change, etc.) will not be prevented but may suffer a slight delay caused by the Prism TM2 waking up. To the customer (and the system) it appears as though the Prism TM2 is out of the coverage area while the Prism TM2 is asleep. To reduce the possible confusion as to if the unit is asleep or out of coverage, when the unit goes to sleep it will send a message prior to shutting down to indicate the shut down and to inform how long the unit will be asleep. Otherwise, if no message is captured then the unit is out of the coverage area. When the unit does go to sleep, it will check its operating conditions to see if it is allowed to go to sleep then, it will start a timer, if the conditions remain the same at the end of the timer then the unit will go to sleep. The unit will send a message to the workstations saying that in X minutes it will be going to sleep for Y hours (this message must be set up in Fleet Director as a message for now). Once the Prism TM2 has gone to sleep it is unreachable until the operating conditions change or it is time to wake up. If the unit wakes up and determines that the operating conditions have not changed it will send out the same message as above. In order to keep a unit awake, the operating conditions must change. For instance, since the Prism TM2 is connected to sense ignition on/off, when the ignition is turned on the unit will wake up. Another way to keep the unit awake is to keep it busy. By moving the unit into a status that locates it more frequently than the time required for it to go to sleep, it will remain awake since the timer is reset after each activity with the unit. When a unit is out of the coverage area or asleep, it will send messages to the buffer. Once the messages are in the buffer they are stored until they are downloaded. The unit will still go to sleep with messages in the buffer. Events or reports that occur while the unit is asleep will still be stored in the buffer. When programming the Prism TM2, you will have the option to fill in the amount of time the unit will wait once it has determined that it can go to sleep, how long it will remain asleep and how long it will stay awake when it does wake up. Ignition Off Not moving Teletrac, Inc. - Prism TM2 Information and Installation Guide Message Store and Forward (Message History) The unit has ability to store locations, event history and messages. Any of these pieces of data can be stored while the Prism TM2 migrates outside the GPRS coverage area. The unit will first attempt to send the message or event, if it fails, the message will be sent to a memory buffer for later delivery. When a report is run, the coverage area will appear greater. With the addition of storing message, this feature will allow the driver to continue to send status messages while outside the GPRS coverage area to time stamp his activities so a compliance report can be generated when he returns to the GPRS coverage area. Also, the messages will be stored even if the unit goes to sleep.
--------------Unit Five--------------
PR 1622-0300 B2-5 05 2006 2 Teletrac, Inc. - Prism TM2 Information and Installation Guide ISM TM2 INSTALLATION INSTRUCTIONS This unit covers the installation of the PRISM TM2. We will take a look at the equipment and walk through a typical installation. As a note, this section does not cover the programming of the PRISM TM2. NOTE: This section discusses a typical installation in a step-by-step fashion. Please e-mail the Field Service group for questions concerning special installations. PRE-INSTALLATION CONSIDERATIONS a) Perform a Pre-installation Vehicle Checkout. Ensure that major electrical/mechanical components are in working order in the event anything happens to the vehicle at a later date. Check the headlamps, air conditioner, dome lights, turn signals, radio, windshield wipers and, if at all possible, start the vehicle engine. b) Prior to beginning the PRISM TM2 installation, record the units IP address and vehicle ID on the installation form. The stickers, created at the time of provisioning, need to be affixed to the installation forms. A set of these forms is to be left with the customer and a set placed in their file. This reduces the need to uninstall the unit then reinstall it in order to find the units number. The units will have their MIN activated upon provisioning in the metro. Upon MIN activation Teletrac starts paying for its use and therefore, units should be installed as quickly as possible and not kept in stock. c) Next, remove the courtesy light fuse in order to avoid running the vehicles battery down during installation. d) Before beginning any work you will need to find suitable locations for the following equipment. As a courtesy, all equipment will be installed in a manner that will conceal its location, usually behind the dashboard. You will need a flat surface for mounting. Also, keep in mind that coax for the antennas must be run behind panels and in pillars. Review the equipment location with the customer and obtain their approval. PRISM TM2 Transceiver Combo antennas Cable runs MDT 12 VDC and ground spots e) While you are determining the mounting location use the system layout as a reference to plan the wiring harness routing and connection points. Typical locations are under or behind the vehicle dashboard. Avoid places with extreme vibration, heat or moisture. f) Once the hardware is mounted and when you are making the wiring connections, hold the PRISM TM2 in place and route the units wiring harness to the connection point at the target wire. Cut the wires to the correct length and make the connections. Once the first installation is complete you can prepare the rest of the equipment (harnesses) in advance of the actual installation. NOTE: Due to the importance of the connections, it is mandatory that all connections be either Soldered or Crimped with the proper crimping tool. Wrap and tape, Scotch-Loc., or T-Tap connections MAY NOT BE USED when installing this system. Teletrac, Inc. - Prism TM2 Information and Installation Guide ITEMS REQUIRED FOR PRISM TM2 INSTALLATION In order to complete the installation of a Prism TM2 you will need to have the following equipment on hand:
PRISM TM2 - Previously tested and activated with GPRS service and IP address GPS Antenna - Through-hole or magnetic mount or a combo antenna GPRS Antenna - 3dB gain whip, with either NMO or magnetic mount or a combo antenna Wiring harness - Standard PRISM TM2 harness with 8-pin connector or VLU to PRISM PRISM TM2 to VLU Adapter One foot long wiring adapter to connect the Teletrac harness adapter to the Prism. Installation Tools - Soldering iron, crimper, press hole punch, 7/8" punch, and misc. tool kit. Hook-up wire - 22 AWG, minimum MDT optional Laptop with HyperTerminal to do testing WIRING SCHEMATIC There are two unique wiring schematics; one for replacing a VLUplus with a PRISM TM2 and one for a new installation of a Prism. For a replacement installation you will need to use the VLU to PRISM TM2 adapter and for a new installation you will need to use the PRISM TM2 harness. There are a couple of differences between the standard VLU and PRISM TM2 harnesses, in particular, the PRISM TM2 ground is a bare wire and the PRISM TM2 ignition is orange. Figure 1: Replacement Schematic with VLU to PRISM TM2 Adapter Prism White - RS232 TX Yellow - RS232 RX Black - RS232 Ground White - Ignition Black - Main Ground Red - Main 12 VDC (+) Black - Ground (-) Blue - Relay 1 Yellow - Relay 2 Red/White - Led 1 Green/Blue - Led 2 Red - Batt (+) 12 VDC Orange - High 1 IN Gray - High 2 IN Orange/Black - Low 1 IN Gray/Black - Low 2 IN See Appendix F for complete Teletrac harness pinouts GPRS Antenna GPS Antenna SMA SMB Figure 2 PRISM TM2 Wiring Scheme 1622-0300 B2-5 05 2006 2 Teletrac, Inc. - Prism TM2 Information and Installation Guide NOTE: To insure that the GPS receiver and power management functions operate properly, it is essential that the Power input be connected to a constant (unswitched) +12 VDC supply and the Ignition input be connected to the vehicle ignition or another appropriate key operated line, such as ACCESSORY that goes low during engine cranking. ANTENNA PLACEMENT Available Antennas NAME VLUplus PRISM PRISM TM2 X NO NO X X X X X X X X X Black 3db Whip White Combo Hidden Combo ARC (see note below) Glass Mount Combo GPS Antenna Now that there are two antennas and one is a GPS antenna, placement becomes critical. The received signal levels for the GPS antenna from the satellites are very low in power
(approximately -136 dBm) so that any blockage of the antenna can affect the quality of the location computed by the receiver. The following figures show examples of good and poor vehicle GPS antenna mounting locations. When installing the GPS antenna on a vehicle roof, make sure there are no obstructions close to the antenna that might block the view 360 to the horizon. Nothing should block the antenna 5 above the horizon - for example, air horns or marker lights. The best location is usually near the center of the roof, although it is also desirable to locate the cellular antenna as far from the GPS antenna as is practical. It is best to keep the antenna at least 12 from any other antenna. IF using the hidden combo antenna, it should be placed on the highest part of the dash or inside the headliner, see the note below. Be sure to use the correct antenna for this application. Also, kinks or tight knots in the antenna cable can cause problems that will not allow the PRISM TM2 to operate. When laying out the antenna cable, care should be taken so that the cable will not be subjected to crushing or strain. Examples of good and poor GPS antenna placement No Blockage above 5 NOTE: To insure that Hidden Combo ARC antenna will function properly, mount the antennas base (large flat side) against a metal surface. NEVER shorten or lengthen the antenna co-ax cable. NEVER locate the antenna near the transceiver unit, or other black box device. NEVER mount the antenna vertically. NEVER mount the antenna below the beltline of the vehicle. NEVER mount the antenna in the trunk or engine comparTM2ent. NEVER use silver (metallic) duct tape to secure the antenna 1622-0300 B2-5 05 2006 3 Teletrac, Inc. - Prism TM2 Information and Installation Guide GPS performance will be less than optimum when using a hidden antenna. When using this type of antenna, be aware of surrounding obstructions that could further reduce GPS operation. GPRS Antenna na used by the PRISM TM2 for GPRS service is a The cellular anten standard black 3dB gain whip. It mounts with a standard NMO
"Motorola" mount and requires ground plane to work properly. If possible, the GPRS antenna should be locate at least 12 from any other antenna. Ensure that the cable does not get crushed during installation. 3 dB Gain Cellular Antenna for GPRS 1622-0300 B2-5 05 2006 4 Teletrac, Inc. - Prism TM2 Information and Installation Guide PRISM TM2 INSTALLATION PROCEDURES Once you have all your tools in order and have planned the location of all the devices, you are ready to install the unit. Following are the steps for two types of installations, replacement of an existing VLUplus OR Prism and installation of a new PRISM TM2. Replacing a VLUplus with a PRISM TM2 You can use all the same wiring and only need to switch out the unit itself. However, there will be an adapter between the unit and the VLUplus harness; see wiring schematic. 1. Locate the existing VLUplus and remove the fuse or disconnect main power to the VLUplus at the power source. 2. Disconnect the antennas from the VLUplus. 3. Disconnect the 37-pin VLUplus wiring harness. 4. Remove VLUplus and note the IP address. 5. Using a volTM2eter, make sure that the ignition line (white harness wire pin 6) is correctly wired to the keyed side of the ignition switch at the ACCESSORY wire. This wire goes high upon turning the key but it goes low when at the CRANK position. Also that the power input
(red wire) is connected to a constant (unswitched) +12v DC supply. Verify that the existing harness has all required wires soldered or crimped for reliability. 6. 7. Attach the VLUplus wiring harness 37-pin connector to the adapter, tighten the screws, and then plug the adapter into the PRISM TM2 unit. 8. Mount the PRISM TM2 to the chassis of the vehicle utilizing the mounting tabs. Secure the unit with four (4) self-tapping machine screws. 9. A new antenna must be installed since the connectors from the Connect the SMA connector to the GPRS antenna port on the unit. Connect the SMB GPS connector to the PRISM TM2. 2. 10. Reattach the main vehicle power and/or replace the fuse. PRISM TM2 New Installations 1. Find suitable locations for the PRISM TM2, and GPS/GPRS combo antenna. Select a PRISM TM2 mounting location that is free of moisture or heat, typically behind the dashboard or under the seat. Install the GPS antenna and route the cable to the PRISM TM2 location. Typically, the installation will require a hole drilled into the vehicle. The exact size of the hole is dependant upon the antenna mount used. Keep in mind that coax must be run behind panels. Note that the GPS antenna should have no blockage 5 above the horizon. (See Antenna Placement page 5.) Install the GPRS antenna and route the antenna cable to the PRISM TM2 location. This will also typically require a hole drilled into the vehicle. The exact size of the hole is dependant upon the antenna mount used. Keep in mind that coax must be run behind panels. (See Antenna Placement page 5.) If a Combo antenna is being used only one hole will be required. 3. 4. Apply silicone around both antenna bases if holes are required. 1622-0300 B2-5 05 2006 5 Teletrac, Inc. - Prism TM2 Information and Installation Guide 5. Connect the PRISM TM2 wiring harness as recommended below. For safety, remove fuse until installation is complete. Never tap into existing power or ignition wires used from other aftermarket devices. Ground Locate chassis ground within one (1) foot of the PRISM TM2 placement. If chassis has sound absorbent materials, scrape materials and/or paint until you reach clean metallic surface. Always use a star washer when attaching to chassis ground. Run Constant +12 Volt Wire Attach one end of the fuse holder to determined power source. Recommended locations are the starter solenoid, main +12 volt terminal behind fuse box or battery distribution block in ending comparTM2ent / behind dash. Never use the existing factory wires that are attached to ground, this could cause interference. Run Ignition Wire Attach one end of fuse holder to determined +12 volt switched ignition source that will rest at ground (verify with suitable Multimeter). Recommended locations are behind ignition cylinder, behind fuse box or the starter solenoid in the engine comparTM2ent. Never use the existing factory wires attached to ground, this could cause interference. TIP: Using a volTM2eter, make sure that the Voltage on the line you are connecting to does not drop to zero while the engine is started (Cranking). This line will be referred to as True Ignition. 6. Mount the PRISM TM2 to the chassis of the vehicle utilizing the mounting tabs. Secure the unit with four (4) self-tapping machine screws. 7. Zip tie excess wire slack and zip tie around the fuse holder to prevent tampering. 8. Attach PRISM wiring harness to the PRISM TM2. 9. Connect GPRS and GPS connectors to the PRISM TM2. Attach the main power and/or replace the fuse. 10. Attach accessories as necessary:
MDT Determine placement within 10 feet of the PRISM TM2 placement. Run a serial cable to the unit. Be sure to get placement approval from the customer. Ignition On/Off Messaging see schematic for relay placement. PTO On/Off Messaging see schematic for relay placement. 11. Attach laptop and perform a checkout. local installation Constant +12V 86 - Ground Normally Open 87 Ground 87A Normally Closed 30 Orange Ignition Input 85 - Ignition Sense Ground 87 86 - Ground Normally Open Constant +12V 87A 12. Reinstall all vehicle panels. 13. Clean up any debris within your work area. 14. Complete the work order form, including the vehicle license plate number, VIN, installation test results and the PRISM TM2 IP sticker. Normally Closed 30 Blue 85 - Active High Input Sense Sample Input 1 1622-0300 B2-5 05 2006 6 9. Teletrac, Inc. - Prism TM2 Information and Installation Guide SWAPPING OUT A PRISM TM2 1. Locate the current PRISM TM2 and disconnect the main power to it at the power source. 2. Disconnect the wiring harness from the VLU. 3. Disconnect the antenna(s). 4. 5. Install the new PRISM TM2; this should be a floating unit from van stock. Insure the existing harness has all the required wires soldered or crimped for reliability and connect the harness to the new PRISM TM2. 6. Connect the antenna(s). 7. Attach accessories as necessary. 8. Remove the SIM chip from the old unit and place it in the new unit, copper side down, white side up, numbers visible. If the PRISM TM2 fails to register upon installation, verify the RSSI level and move the vehicle to a location with better reception if necessary. Also verify the SIM is installed correctly. Complete the work order for, including the vehicle license plate number, VIN, installation test results and PRISM TM2 MIN sticker. Leave a copy with the customer.
--------------Unit Six--------------
PRISM TM2 ADMINISTRATION & PROVISIONING Administrative Procedures NEW ORDERS 1. CAR does the Site Survey with the customer. 2. The Administrator places the order in TOPSS. 3. The warehouse will receive picking ticket. 4. The warehouse provisions and ships Prism TM2 order to the metro. 5. The VSR installs the equipment. 6. Help Desk program units over the air if needed. 7. CAR sets up the vehicles in Fleet Director during training. REPAIRS Hardware 1. The local metro will retain a vanstock of units (appropriate for market volume). They are generic units that dont have a SIM sticker on them or SIM in them. 2. Upon determining need for replacing a unit, the old unit will be removed from the vehicle, a new one installed and the SIM from the old unit is placed in the new unit
(metal side down, numbers visible. 3. The VSR RMAs the old unit back to the warehouse. The Administrator orders new vanstock at the same time they give a RMA number to the VSR. SIM 1. The local metro will retain a vanstock of SIMs (appropriate for market volume). 1622-0300 B2-5 05 2006 7 Teletrac, Inc. - Prism TM2 Information and Installation Guide 2. Upon determining need for replacing a SIM, the old SIM is removed from the unit and a new blank SIM is placed in the unit. The factory default setting are written to the new SIM by the unit. 3. The VSR RMAs the SIM back to the warehouse. The Administrator orders new vanstock at the same time they give a RMA number to the VSR. 4. Help Desk programs over the air as needed. 5. The CAR or Customer swaps unit numbers in Fleet Director as required. DEACTIVATION 1. In the event the unit is removed and/or returned to Teletrac, RMA the unit and SIM back to the warehouse. Provisioning Procedures 1. Distribution receives equipment and SIMs into inventory. 2. Distribution stages equipment and SIMs for QA Technician. 3. QA Technician assembles equipment:
a. Scan SIM & unit numbers with bar code reader. b. Generate stickers with SIM number on it for the unit, vehicle and paperwork. c. Place SIM in unit and place coresponding SIM sticker on the unit. d. Repackage assembled units and stickers. e. Return prepared equipment to Distribution. 4. Distribution receives TOPSS order and pulls equipment. 5. Distribution gives units back to QA Technician for programming appropriate carrier and configuration. The units are returned to Distribution. 6. Distribution notifies carrier that the SIMs need to be made active and places number in Simon. 7. Distribution sends equipment to the metro. 8. Help Desk programs the units over the air if needed. NOTE: Hardware units that are being used for vanstock are not sent to the QA Technician because they will not have SIM cards in them. 1622-0300 B2-5 05 2006 8 Teletrac, Inc. - Prism TM2 Information and Installation Guide These pages may be updated or added to at any time. Please check the Ops Web for the Appendix most current information. 1622-0300 B2-5 05 2006 9 Teletrac, Inc. - Prism TM2 Information and Installation Guide Appendix A APPENDIX A AN INTRODUCTION TO GLOBAL POSITIONING SATELLITE SYSTEMS Global Positioning Systems - A Primer Navigation and positioning are crucial to so many activities and over the years all kinds of technologies have tried to simplify the task including Teletrac's RF system. The U.S. DeparTM2ent of Defense (DoD) decided the U.S. military needed a super-precise form of worldwide positioning. And fortunately, they had the kind of money ($12 billion) it took to build it. The result is the Global Positioning System. The Global Positioning System (GPS) is a worldwide radio-navigation system formed from a constellation of 24 satellites and their ground stations. GPS uses these "man-made stars" as reference points to calculate positions accurate to within meters. In fact, with advanced forms of GPS you can make measurements to better than a centimeter. In a sense, it's like giving every square meter on the planet a unique address. GPS receivers have been miniaturized to just a few integrated circuits and so are becoming very economical. And that makes the technology increasingly accessible. The U.S. military was able to successfully deploy GPS for the first time during the Gulf War in 1991. It is credited as being one of the factors that led to the fast victory over Iraqi forces as our military units were "visible" (that is, their locations and movements were precisely known) to strategists at all times. Here's how GPS works in five logical steps:
Here is a summary of each of the steps involved with GPS in order to determine a location. This is the first part of Teletrac finding the locations of vehicles using a Prism TM2. Once a location is determined, then it is sent via another system. We'll explain each of the following points in the next five sections. 1. The basis of GPS is "triangulation" from satellites. 2. To "triangulate," a GPS receiver measures distance using the travel time of radio signals. 3. To measure travel time, GPS needs very accurate timing, which it achieves with some tricks. 4. Along with distance, you need to know exactly where the satellites are in space. High orbits and careful monitoring are the secret. 5. Finally you must correct for any delays the signal experiences as it travels through the aTM2osphere. 1622-0300 B2-5 05 2006 10 Teletrac, Inc. - Prism TM2 Information and Installation Guide Step 1: Triangulating from Satellites Improbable as it may seem, the whole idea behind GPS is to use satellites in space as reference points for locations here on earth. That's right, by very, very accurately measuring our distance from three satellites we can "triangulate" our position anywhere on earth. Forget for a moment how our receiver measures this distance. We'll get to that later. First consider how distance measurements from three satellites can pinpoint you in space. THE BIG IDEA GEOMETRICALLY:
Suppose we measure our distance from a satellite and find it to be 11,000 miles. Knowing that we're 11,000 miles from a particular satellite narrows down all the possible locations we could be in the whole universe to the surface of a sphere that is centered on this satellite and has a radius of 11,000 miles. Next, say we measure our distance to a second satellite and find out that it's 12,000 miles away. That tells us that we're not only on the first sphere but we're also on a sphere that's 12,000 miles from the second satellite. Or in other words, we're somewhere on the circle where these two spheres intersect. If we then make a measurement from a third satellite and find that we're 13,000 miles from that one, that narrows our position down even farther, to the two points where the 13,000 mile sphere cuts through the circle that's the intersection of the first two spheres. 1622-0300 B2-5 05 2006 11 Teletrac, Inc. - Prism TM2 Information and Installation Guide So by ranging from three satellites we can narrow our position to just two points in space. To decide which one is our true location we could make a fourth measurement. But usually one of the two points is a ridiculous answer (either too far from Earth or an impossible velocity) and can be rejected without a measurement. A fourth measurement does come in very handy for another reason however, but we'll tell you about that later. Next we'll see how the system measures distances to satellites. Step 2: Measuring Distance from a Satellite a s IDEA MATHEMATICALLY tellites. But how can you measure the distance to We saw in the last section that a position is calculated from distance measurements to at least three sa something that's floating around in space? We do it by timing how long it takes for a signal sent from the satellite to arrive at our receiver. THE BIG In en , in high school. Remember the old: "If a travel.?"
Velocity (60 mph) x Time (2 hours) = Distance (120 miles) In the cas or roughly 186,000 miles per second. The problem is me SYNCHRONIZING OUR WATCHES se the w le thing boils down to those "velocity times travel time" math problems we did car goes 60 miles per hour for two hours, how far does it e of GPS we're measuring a radio signal so the velocity is going to be the speed of light asuring the travel time. ho The timing problem is tricky. First, the times are going to be awfully short. If a satellite were right overhead, the travel time would be something like 0.06 seconds. So we're going to need some really precise clocks. We'll talk about those soon. 1622-0300 B2-5 05 2006 12 Teletrac, Inc. - Prism TM2 Information and Installation Guide ere was a way to get both the satellite and the receiver to start playing "The Star-
Banner" at precisely 12 Noon. If sound could reach us from space (which, of course, is
) then standing at the receiver we'd hear two versions of "The Star-Spangled Banner,"
ur receiver and one from the satellite. But assuming we have precise clocks, how do we measure travel time? To explain it let's use a goofy analogy:
Suppose th Spangled ridiculous one from o These two versions would be out of sync. The version coming from the satellite would be a little delayed because it had to travel over 11,000 miles. If we wanted to see just how delayed the satellite's version was, we could start delaying the receiver's version until they fell into perfect sync. The amount we have to shift back the receiver's version is equal to the travel time of the satellite's version. So we just multiply that time times the speed of light and BINGO! we've got our distance to the satellite. That's basically how GPS works. Only instead of "The Star-Spangled Banner" the satellites and receivers use something called a
"Pseudo Random Code." - which is probably easier to A RANDOM CODE?
The Pseudo Random Code (PRC) is a fundamental part of GPS. Physically it's just a very complicated digital code, or in other words, a complicated sequence of "on" and "off" pulses as shown here:
sing than "The Star-Spangled Banner."
s its own unique Pseudo-Ran
't accidentally pick up another satellite's si unlikely that a stray signal will have exactly the same shape. licated that it almost looks like random electrical noise. Hence the name The signal is so comp
"Pseudo-Random."
There are several good reasons for that complexity: First, the complex pattern helps make sure that the receiver doesn't accidentally sync up to some other signal. The patterns are so complex that it's highly Since each satellite ha dom Code this complexity also guarantees that the receiver won gnal. So all the satellites can use the same frequency without jamming each other. And it makes it more difficult for a hostile force to jam the system. In fact the Pseudo Random Code gives the DoD a way to control access to the system. But there's another crucial to making GPS economical. The codes make it possible to use "information theory" to "amplify" the GPS signal. And that's why GPS receivers don't need big satellite dishes to receive the GPS signals. We glossed over one point in our goofy Star-Spangled Banner analogy. It assumes that we can guarantee that both the satellite and the receiver start generating their codes at exactly the same time. But how do we make sure everybody is perfectly synced? Stay tuned and see. reason for the complexity of the Pseudo Random Code, a reason that's 1622-0300 B2-5 05 2006 13 Teletrac, Inc. - Prism TM2 Information and Installation Guide Step 3: Getting Perfect Timing st 200 miles of error!
ceivers here on the ground?
entially an atomic-accuracy clock. uring the travel time of a radio signal cate a point in 3-dimensional space, then four satellite and the receiver need to be able to precisely synchronize their te side, timing is almost perfect because they have incredibly precise atomic clocks is the key to GPS, then our stop watches had better se if their timing is off by just a thousandth of a second, at the speed of light, If meas be darn good, becau that translates into almo On the satelli on board. But what about our re Remember that both the pseudo-random codes to make the system work. If our receivers needed atomic clocks (which cost upwards of $50K to $100K) GPS would be a lame duck technology. Nobody could afford it. Luckily the designers of GPS came up with a brilliant little trick that lets us get by with much less ocks in our receivers. This trick is one of the key elements of GPS and, as an added accurate cl side benefit, it means that every GPS receiver is ess The secret to perfect timing is to make an extra satellite measurement. That's right, if three perfect measurements can lo imperfect measurements can do the same thing. EXTRA MEASUREMENT CURES TIMING OFFSET If everything were perfect (i.e. if our receiver's clocks were perfect) then all of our satellite ranges fourth would intersect at a single point (which is our position). But with imperfect clocks, a measurement, done as a cross-check, will NOT intersect with the first thr So the receiver's computer says "Uh-oh! There is a discrepancy in my measurements. I must not be perfectly synced with universal time."
Si will affect all of single correction factor that it can subtract from all it them all to intersect at a single point. That correction brings the receiver's clock back into sync with universal time, and bingo! - you've got atomic accuracy time right in the palm of your hand. Once it has that correction it applies to all the rest of its measurements and now we've got precise positioning. One consequence of this principle is that any decent GPS receiver will need to have at least four channels so that it can make the four measurements simultaneously. O.K, with the pseudo-random code as a rock solid timing sync pulse, and this extra measurement trick to get us perfectly synced to universal time, we have got everything we need to measure our distance to a satellite in space. But for the triangulation to work we not only need to know distance, we also need to know exactly where the satellites a our measurements, the receiver looks for a s timing measurements that would cause nce any offset from univ ersal time ee. re. 1622-0300 B2-5 05 2006 14 Teletrac, Inc. - Prism TM2 Information and Installation Guide Step 4: Knowing Where a Satellite is in Space E GATHERS NO MOSS assuming that we know where the GPS satellites are so we can use exactly where they are? After all they're floating around 11,000 miles up in 1,000 mile altitude is actually a benefit in this case, because something that high is well In this tutorial we've been s. them as reference point But how do we know space. A HIGH SATELLIT That 1 clear of the aTM2osphere. And that will mean it will orbit according to very simple mathematics. The Air Force has injected each master plan. On the g th CONSTANT MONITORING ADDS PRECISION The basic orbits are quite exact but just to make things perfect the GPS satellites are constantly monitored by the DeparTM2ent of Defense. round all GPS receivers have an almanac programmed into their computers that tells GPS satellite into a very precise orbit, according to the GPS em where in the sky each satellite is, moment by moment. They use very precise radar to ch The errors they're checking for a orbit or "ephemeris." These erro by the pressure of solar The errors are usua s exact altitude, position and speed. eck each satellite'
re called "ephemeris erro rs are caused by gravitational pu rs" because they affect the satellite's lls from the moon and sun and radiation on the satellites. lly very slight but if you want great accura cy they must be taken into account. 1622-0300 B2-5 05 2006 15 Teletrac, Inc. - Prism TM2 Information and Installation Guide GETTING THE MESSAGE OUT Once the DoD has measured a satellite's exact position, they relay that information back up to the satellite itself. The satellite then includes this new corrected position information in the timing signals it's broadcasting. So a GPS signal is more than just pseudo-random code for timing purposes. It also contains a navigation message with ephemeris information as well. With perfect timing and the satellite's exact position you'd think we'd be ready to make perfect position calculations. But there's trouble afoot. Check out the next section to see what's up. Step 5: Correcting Errors Up to now we've been treating the calculations that go into GPS very abstractly, as if the whole thing were happening in a vacuum. But in the real world there are lots of things that can happen to a GPS signal that will make its life less than mathematically perfect. To get the most out of the system, a good GPS receiver needs to take a wide variety of possible errors into account. Here's what they've got to deal with. ROUGH TRIP THROUGH THE ATM2OSPHERE First, one of the basic assumptions we've been using throughout this tutorial is not exactly true. We've been saying that you calculate distance to a satellite by multiplying a signal's travel time by the speed of light. But the speed of light is only constant in a vacuum. As a GPS signal passes through the charged particles of the ionosphere and then through the water vapor in the troposphere it gets slowed down a bit, and this creates the same kind of error as bad clocks. 1622-0300 B2-5 05 2006 16 Teletrac, Inc. - Prism TM2 Information and Installation Guide exactly typical. There are a couple of ways to minimize this kind of error. For one thing we can predict what a typical delay might be on a typical day. This is called mod eling and it helps but, of course, aTM2ospheric conditions are rarely Another way to get a handle on these aTM2osphere-induced errors is to compare the relative speeds of two different signals. This "dual frequency" measurement is very sophisticated and is only possible with advance ROUGH TRIP ON THE GROUN Trouble for the GPS signal doe off various local obstructio D sn't end when it gets down to th e ground. The signal may bounce ns before it gets to our receiver. d receivers. rs ATELLITE sophisticated signal rejection techniques to minimize this problem. s are very sophisticated they do account for some tiny errors in the clocks they use are very, very precise but they're not perfect. Minute discrepancies his is called multipath error and is similar to the ghosting you might see on a TV. Good receive T use PROBLEMS AT THE S Even though the satellite system. The atomic can occur, and these translate into travel time measurement errors. And eve second. So slight position or "ephemeris" errors can sneak in between monitoring times. SOME ANGLES ARE BETTER THAN OTHERS Basic geometry itself can magnify these other errors with a principle called "Geometric Dilution of Precision" or GDOP. It sounds complicated but the principle is q ere are sually more satellites Th picks a few and ignores the rest. If it picks satellites that are close together in the sky the intersecting circles that define a position will cross at very shallow angles. That increases the gray area or error margin around a position. ble than a receiver needs to fix a position, so the receiver s are constantly monitored, they can't be watched every n though the satellites position uite simple. availa u 1622-0300 B2-5 05 2006 17 Teletrac, Inc. - Prism TM2 Information and Installation Guide If it picks satellites that are widely separated the circles intersect at almost right angles and that minimizes the error region. st GDOP. h satellites will give the lowe lieve, the same government that spe in the world is intentionally degradi Good receivers determine whic INTENTIONAL ERRORS!
As hard as it may be to be accurate navigation system called "Selective Availability" or "
or terrorist group can use GPS to make B asically the DoD introduces some "noise" into the satellite's clock data which, in turn, adds noise
(or inaccuracy) into position calculations. The DoD may also be sending slightly erroneous orbital data to the satellites which they transmit back to receivers on the ground as part of a status messag Together these factors make SA th receivers use a decryption key to re e biggest single source of inaccuracy in the system. Military move the SA errors and so they're much more accurate. nt $12 billion to develop the most ng its accuracy. The policy is s to make sure that no hostile force SA" and the idea behind it i accurate weapons. e. The Bottom Line Fortunately all of these inaccuracies still don't add up to much of an e called "Differential GPS" can significantly reduce these problems. rror. And a form of GPS 1622-0300 B2-5 05 2006 18 Teletrac, Inc. - Prism TM2 Information and Installation Guide Appendix B APPENDIX B TELETRAC PRISM TM2 ANTENNAS Teletrac has approved 5 antennas compatible with the Prism TM2. Two of these designs are GPS only and need to be installed along with the GPRS only antenna. The other two have both GPS and GPRS antennas. GPS Roof Mount Antenna - Part # 335-0054 This antenna mounts on the outside of the vehicle trough a 5/8-inch perforation of the roof. This antenna features a 15-foot antenna cable and a SMB connector. Voltage: +5 VDC supplied by unit Gain: +18 dBm trought internal amplifier Omni directional loaded patch when on top of vehicle Top mount attached with retaining nut from inside the vehicle. Top mount when screwing mounting nut to the vehicle from the outside, this eliminates need to secure the nut from the inside. Specs:
Polarization:
Mounting Options:
GPRS 3dB Antenna - Black Part # 335-0053 Cable & Mast Part # 335-0058 Mast Only Part # 335-0083 W/ 4 Bolt Spring, Special Order This antenna is the most common CDPD/GPRS antenna used today due to its low loss cable, elevated gain mast and low price. The antenna features a M mount which requires a perforation. There is no need of adjusTM2ents and the mast will work on any 900 MHz antenna mount currently used by us. Options are Mag Mount, Trunk Lip Mount, and Though Hole. Teletrac, Inc. - Prism TM2 Information and Installation Guide Roof Mount Combo Antenna - Part # 335-0060 Self contained antenna that encloses all its components inside a single unit. GPRS and GPS both share the same ground plane in order to minimize noise. The body of the antenna is a 4-inch disc that is 100 % waterproof. Its low profile and ease of installation and high gain makes it a very flexible option. Color is white. Hidden Combo Antenna - Part #
This is a combo antenna used on VLUplus and PRISM TM2 units. It is intended to be installed in the headliner with a view out all four sides of the vehicle. Specs:
Polarization:
Mounting Options:
Roof mount. Voltage: +5 VDC Supplied by unit Gain 27 dB @ GPS and 3 dB 820 to 900 MHz Omnidirectional 335-0074 1622-0300 B2-5 05 2006 2 Teletrac, Inc. - Prism TM2 Information and Installation Guide Appendix C APPENDIX C INSTALLATION EQUIPMENT Metro Equipment Each metro should have the following available on site for the installers. Eltron Printer for printing labels to affix to units (TLP 2242 Series or equivalent) Installer Equipment Each installer should have the following equipment in their vanstock. Laptop with working serial port Working VLUplus in their Vehicle (can be mobile unit) Working RF VLU in their Vehicle (can me mobile unit) Working PRISM TM2 in their vehicle (can be mobile unit) VLUplus Programming tools RF VLU Programming tools*
PRISM TM2 Programming tools VLU Terminal software (VLU_PRO) HyperTerminal SW (part of std. Windows Install) VLUplus Programming Cable (or Technocom Tester) CDPD Diagnostics MDT Good-Working CDPD/GPRS Mag-mount Antenna (for reference) Good-Working GPS Mag-mount Antenna (for reference) Good-Working RF VLU Mag-mount Antenna (for reference)*
MDT Serial Cable MDT Programming Cable MDT Programming Software Std. Tool Kit with the usual electrical tools (soldering iron, wire cutters, volt meter, etc.) GPS Receiver Part # 400-3070 (Garmin GPS48) NOTE: * RF VLUs and its support hardware and software are only needed in markets with both RF and CDPD coverage. 1622-0300 B2-5 05 2006 3 Teletrac, Inc. - Prism TM2 Information and Installation Guide Appendix D APPENDIX D HOW MESSAGES ARE USED IN SCRIPTS Message Code Usage General NOTE: The term VLU means all Teletrac location units. The purpose of this paper is to give guidelines on how to standardize message code usage for Fleet Director, MDTs and VLUs. The standardization of message codes is intended to help make it easier to develop and support customer applications. The following bullet list expresses the basic reasons for message code standardization. Training Standardization of codes make the code usage intuitive by using the same codes for similar messages. This helps both the newcomer and the trainer since code usage has common rules that easily understood. Customer Support As in training the code standards make it easier to support the customer when all customers are setup with common rules on code usage. This avoids the confusion associated with have multiple customer applications using similar messages but uncommon codes. Installation Support By standardizing code usage standard workstation, MDT and VLU configurations can be developed as packages with minimal customization requirements. This prevents mistakes in application setup and decreases the cost and time to install customer equipment. Code Conservation Message codes are limited, especially for inbound messages. All messages cannot be given unique. By standardizing codes, commonly used messages can be given unique codes leaving the remaining codes for reuse in new applications. Script Development By developing standardized relationships for codes and script features and VLU hardware, script development is made less costly. Without standardization far more scripts would need to be developed for different uses of the codes for similar functions or features. This would be very confusing since most scripts would have minor differences and keeping track of the difference would be difficult. Ultimately the support personnel would standardize on script usage by using the script most familiar to them thus achieving a similar affect as code standardization. Unfortunately different installers would have different standards and engineering would still have to produce large numbers of scripts to meet everyones expectations. System Development As new system capabilities are developed along with new workstation software and mobile equipment, the usage of message codes play a part on service privileges and expectations. By standardizing codes, the system can more easily be developed to handle ranges of codes or a selected 1622-0300 B2-5 05 2006 4 Teletrac, Inc. - Prism TM2 Information and Installation Guide few codes with similar function or features rather than being expected to handle all codes with different with a variety of possible functions or features. Code standardization should take into consideration both inbound and outbound message usage. It should also consider the limitations within the System, the VLU, the MDT, and the workstation software that force some messages to be reserved or identified for special usage. For example, the MDT has built in limitations due to resource limitations and the VLU has unchangeable firmware where codes force VLU behavior differences. There are three forms of inbound messages: ACM which are also known as ECM or canned inbound messages, RCM_A which are known as Form Fill message and LIM which are variable length free form message, which can be either Form Fill or Free Text. This paper focuses on only canned inbound messages. The Teletrac Air Interface protocol restricts inbound canned messages to ACM 11-99 codes. There are other message codes available for special services and emergency messages but have system restrictions due to EMS (Episode Management System) services (i.e. ACM 235-Panic, ACM 207-Stolen, ACM 167-Roadside Assistance, etc). There are two types of outbound message that are called FCM and Long FCM. The FCM codes are allocated by the Teletrac Air Interface Protocol and are not the subject of this paper. However, this paper does address the usage of codes within the use of FCM 220, 221 and 222. To date all outbound canned messages sent to the MDT use the FCM 220 message and send one of 256 possible codes (0-255) within the message structure as a canned message code. Inbound Message Guidelines As mentioned above the ACM 11-99 codes can be used for inbound canned messages. From those available 89 message codes the following considerations must be made:
The MDT supports 40 canned inbound messages. The MDT supports 10 emergency messages. The VLU has 4 inputs capable of 8 messages (each ON and OFF). The VLUplus & PRISM TM2 has zones requiring 2 messages each (zone entry and exit). The VLUplus & PRISM TM2 will have common script functions like Power Management and Tow-Away which require message codes. The VLUplus & PRISM TM2 uses code 0 for Store and Forwarded locations. The current system has allocated messages ACM 90-99 as alternate notification messages. The RF VLU has special functionality for ACM 94, 97 and 99. Although the system currently may not take advantage of these features or in the future may change the definition, the standardization of codes should expect that the codes are used as intended. The following table shows how the inbound message codes could be allocated. 1622-0300 B2-5 05 2006 5 Teletrac, Inc. - Prism TM2 Information and Installation Guide Table 1 - Standardized Inbound Message Code Usage IB Codes Definition 0 S&F Location 11-50 MDT inbound canned message 51-58 VLU input messages (i.e. Ign, Alert, etc.) 59-70 VLUplus & PRISM TM2 Zone Entry and Exits messages 71-79 VLUplus PEG script status messages Comments VLUplus & PRISM TM2 uses this message code for S&F locations. The definition of these messages depends on customer requirements. Ign ON/OFF = 51/52 Input 1 ON/OFF= 53/54 (Fleet Director Panic) Input 2 ON/OFF = 55/56 Input 3 ON/OFF = 57/58 Zone 1 Entry/Exit=59/60 Zone 2 Entry/Exit=61/62 Zone 3 Entry/Exit=63/64 Zone 4 Entry/Exit=65/66 Zone 5 Entry/Exit=67/68 Zone 6 Entry/Exit=69/70 Sleep Message=71 72-79 reserved for future PEG usage.
(i.e. StopToLong, TimeForService, etc.) 90-96 reserved for PEG usage. AfterHours=97 (VAR Panic in RF VLU) Speeding=98 TowAway=99 (VAR Stolen in RF VLU) 80-89 MDT Emergency Menu messages Per customer requirements. 90-99 VLU Service and Emergency messages Outbound Message Guidelines As mentioned above the inbound canned message codes can be 0-255 and are sent as part of the FCM 220 message structure. From these available 256 message codes the following considerations must be made:
The MDT can support up to 40 canned outbound messages. The MDT allows codes 1-6 to control its outputs. The Prism TM2 can use any of the 256 codes for script controls and commands. The Prism TM2 passes all 256 message codes to the MDT thus causing the MDT to display text if the message is understood by the MDT. The RF VLU allows message codes 80-143 to control its output, however only 20 of the codes are utilized (80-84, 96-100, 112-116 and 128-132). 1622-0300 B2-5 05 2006 6 Teletrac, Inc. - Prism TM2 Information and Installation Guide The following table shows how the outbound message codes could be allocated. Table 2 - Standardized Outbound Message Code Usage OB Code Definition 1-6 MDT Output Control Messages 7-10 PEG Control Message Comments 1-3=Output 1 On/Off/Pulse 4-6= Output 2 On/Off/Pulse PEG operation control messages (i.e. Disable Sleep Mode, Reset Mileage, etc.) Customer defined messages. 11-50 MDT OB Canned messages 51-79 PEG Status Requests and Control To request PEG to send reports or identify operating status (i.e. Send Mileage Report, Send Run Time, etc.). Same as RF VLU definition. For future use. 80-143 VLU Output Control Messages 144-255 Undefined 1622-0300 B2-5 05 2006 7 Teletrac, Inc. - Prism TM2 Information and Installation Guide Final Comments The key to good standardization is to keep similar message grouped together and to make the code usage intuitive. Unfortunately sometimes intuitive and grouping dont mix. The best standardization method would never use the same message code twice however we dont have that luxury due to limited code availability (especially on the inbound messages). For Teletrac the best approach is to review our message code usage and anticipate future needs. As we already know, some messages definitions are similar and used by all customers (or nearly all-Ignition On/Off, VLU Sleep, etc.). These commonly used messages should become standardized. We also know that some messages are used for status, some for information and others for control. We should try to group these three groups as best we can. Unfortunately, some messages cant fit neatly into standard grouping definitions due to either multiple uses in the same installation (i.e. Panic might be in the MDT emergency menu and also in the VLU for a hidden switch). When dealing with these conflicts its best to think of installation support and script standardization. We dont want to make it difficult on support personnel when similar functions end up being different for each case. Furthermore, if we keep changing which message is used for standard script functions
(input activity) we will end up with a lot of scripts with minor differences that will be hard to track. For the above Panic message example it would be best to use the Input 2 message code ACM 53 for Panic in both the MDT and VLU so that the basic multi-input script could work without changes and the installer knows that input two always causes an ACM 53 message. 1622-0300 B2-5 05 2006 8 Teletrac, Inc. - Prism TM2 Information and Installation Guide Appendix E APPENDIX F FCC STATEMENT Statement according FCC part 15.19 FCC identifier has to be on the equipment This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. Statement according FCC part 15.21 Modifications not expressly approved by Teletrac, Inc. could void the user's authority to operate the equipment. Statement according FCC part 15.105 NOTE: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. RF Exposure Note: The antenna of this device is installed on the top of a vehicle, which is a mounted antenna location. Thus, the truck driver and passenger are at least 20 cm from the antenna. Health and Safety Information Exposure to Radio Frequency (RF) Signals This product is a radio transmitter and receiver. It is designed and manufactured not to exceed the emission limits for exposure to radio frequency (RF) energy set by the Federal Communications Commission of the U.S. Government. These limits are part of comprehensive guidelines and establish permitted levels of RF energy for the general population. The guidelines are based on standards that were developed by independent scientific organizations through periodic and thorough evaluation of scientific studies. The standards include a substantial safety margin designed to assure the safety of all persons, regardless of age and health. 1622-0300 B2-5 05 2006 9 Simple Guidelines Teletrac, Inc. - Prism TM2 Information and Installation Guide Appendix F APPENDIX G - SAFETY INFORMATION Please follow these guidelines when configuring or using the Prism TM2. Violating these guidelines may be dangerous, illegal or otherwise detrimental. Further detailed information is provided in this manual. Do Not Operate Where Prohibited Do not allow the Prism TM2 to operate wherever wireless phone use is prohibited or when doing so may cause interference or danger. Examples include but are not limited to operation in hospitals, aircraft, near blasting sites or wherever operation can cause interference. Interference Like all wireless devices, the Prism TM2 may encounter electrical interference that may affect its performance. Avoid Body Contact with Device During Operation Do not operate the Prism TM2 in direct contact with your body. Maintain minimum separation distance of 6.2 inch (20 cm) between the device antenna and any parts of your body. Antenna must be installed on the top of the vehicle or the windshield area of the vehicle, in order to maintain a distance of 20 cm from a human body. Qualified Service Except for batteries and Subscriber Identification Module (SIM) card, the Prism TM2 contains no user serviceable or replaceable parts. Non-functioning units must be returned to an authorized service center for repair or replacement. Water-Resistance The Prism TM2 is not waterproof. Even though it is water-resistant, it is recommended that it be used where it is relatively dry and not subjected to either water streams or submersion. 1622-0300 B2-5 05 2006 10 Teletrac, Inc. - Prism TM2 Information and Installation Guide Detailed Safety Information Exposure to Radio Frequency Signals The Prism TM2 is a low power radio transmitter and receiver. When it is ON, it receives and also sends out radio frequency (RF) signals. In August 1996, the Federal Communications Commissions (FCC) adopted RF exposure guidelines with safety levels for hand-held wireless phones. Those guidelines are consistent with safety standards previously set by both U.S. and international standards bodies:
ANSI C95.1 (1992) NCRP Report 86 (1986) ICNIRP (1996) Those standards were based on comprehensive and periodic evaluations of the relevant scientific literature. For example, over 120 scientists, engineers, and physicians from universities, government health agencies, and industry reviewed the available body of research to develop the ANSI Standard (C95.1) While the Prism TM2 is not intended for hand-held use, its design nonetheless complies with the FCC guidelines (and those standards). Electronic Devices Most modern electronic equipment is shielded from RF signals. However, certain electronic equipment may not be shielded against the RF signals generated by the Prism TM2. Pacemakers The Health Industry Manufacturers Association recommends that a minimum separation of six (6) inches be maintained between a handheld wireless phone and a pacemaker to avoid potential interference with the pacemaker. These recommendations are consistent with the independent research by and recommendations of Wireless Technology Research. Persons with pacemakers:
Should ALWAYS keep the Prism TM2 more than eight inches from their pacemaker with the device is operational. Should not carry the Prism TM2 on their person If there is any reason to suspect that interference is taking place, the Prism TM2 battery pack should be removed immediately. Other Medical Devices If any other personal medical devices are used in the vicinity of a Prism TM2, consult the manufacturers of the medical devices to determine if they are adequately shielded from external RF energy. Physicians may be able to assist in obtaining this information. Disable operation of the Prism TM2 by removing the battery pack in health care facilities when any regulations posted in these areas prohibit the use of wireless phones or two-
way radios. Hospitals and health care facilities may be using equipment that could be sensitive to external RF energy. 1622-0300 B2-5 05 2006 11 Teletrac, Inc. - Prism TM2 Information and Installation Guide Vehicles RF signals may affect improperly installed or inadequately shielded electronic systems in motor vehicles. Check with the manufacturer or its representative regarding the vehicle. Also consult the manufacturer of any equipment that has been added to the vehicle. Posted Facilities Disable operation of the Prism TM2 by removing the battery pack in any facility where posted notices prohibit the use of wireless phones or two-way radios. Aircraft FCC regulations prohibit using wireless phones while in the air. Disable operation of the Prism TM2 by removing the battery pack prior to boarding or loading in an aircraft Blasting Areas To avoid interfering with blasting operations, disable operation of the Prism TM2 by removing the battery pack when in a blasting area or in areas posted: Turn off two-way radio. Obey all signs and instructions. Potentially Explosive ATM2ospheres Disable operation of the Prism TM2 by removing the battery pack prior to entering any area with a potentially explosive aTM2osphere and obey all signs and instructions. Sparks in such areas could cause an explosion or fire resulting in bodily injury or even death. Areas with a potentially explosive aTM2osphere are often, but not always marked clearly. Potential areas may include: fueling areas (such as gasoline stations); below deck on boats; fuel or chemical transfer or storage facilities; vehicles using liquefied petroleum gas (such as propane or butane); areas where the air contains chemicals or particles
(such as grain, dust, or metal powders); and any other area where it would normally be advisable to turn off motor vehicle engines. For Vehicles Equipped with an Air Bag An air bag inflates with great force. DO NOT place objects, including the Prism TM2, in the area over the air bag or in the air bag deployment area. If in-vehicle wireless equipment is improperly installed and the air bag inflates, serious injury could result. 1622-0300 B2-5 05 2006 12 Teletrac, Inc. - Prism TM2 Information and Installation Guide Overview Introduction This manual covers the Prism TM2 operating on 900 MHz, 1800 MHz and 1900 MHz GSM networks. As used in this manual, the term GSM shall include any and all of these frequencies. Regulatory Approvals CE The Prism TM2 product complies with the essential requirements of the R&TTE Directive 199/5/EC as stated by the EC Declaration of Conformity (CE0681) and the EC R&TTE Type Examination Certificate. The Prism TM2 product complies with the European Telecommunications Standards Institute Specifications ETS300-342-1 (EMC for GSM 900MHZ and DCS 1800MHZ Radio Equipment and Systems). EEC The Prism TM2 product complies with Directive 72/245/EEC as amended by Directive 95/54/EC (el*72/245*95/54). FCC The Prism TM2 product complies with FCC Part 15, FCC Part 24, and Industry Canada requirements. The Prism TM2 product complies with Part 15 of the FCC rules. Operation is subject to the following two conditions:
(1) This device may not cause harmful interference, and
(2) This device must accept any interference received, including interfer ence that may cause undesired operation. 1622-0300 B2-5 05 2006 13
1 | Users Manual 5 | Users Manual | 1.85 MiB | November 05 2006 |
MC46 Siemens Cellular Engine Version:
DocID:
03.05 MC46_HD_V03.05 MC46 Hardware Interface Description Confidential / Released s mo b i l e Document Name: MC46 Hardware Interface Description Version:
Date:
DocId:
Status:
03.05 November 13, 2003 MC46_HD_V03.05 Confidential / Released General Notes Product is deemed accepted by recipient and is provided without interface to recipients products. The documentation and/or product are provided for testing, evaluation, integration and information purposes. The documentation and/or product are provided on an as is basis only and may contain deficiencies or inadequacies. The documentation and/or product are provided without warranty of any kind, express or implied. To the maximum extent permitted by applicable law, Siemens further disclaims all warranties, including without limitation any implied warranties of merchantability, completeness, fitness for a particular purpose and non-infringement of third-party rights. The entire risk arising out of the use or performance of the product and documentation remains with recipient. This product is not intended for use in life support appliances, devices or systems where a malfunction of the product can reasonably be expected to result in personal injury. Applications incorporating the described product must be designed to be in accordance with the technical specifications provided in these guidelines. Failure to comply with any of the required procedures can result in malfunctions or serious discrepancies in results. Furthermore, all safety instructions regarding the use of mobile technical systems, including GSM products, which also apply to cellular phones must be followed. Siemens or its suppliers shall, regardless of any legal theory upon which the claim is based, not be liable for any consequential, incidental, direct, indirect, punitive or other damages whatsoever
(including, without limitation, damages for loss of business profits, business interruption, loss of business information or data, or other pecuniary loss) arising out the use of or inability to use the documentation and/or product, even if Siemens has been advised of the possibility of such damages. The foregoing limitations of liability shall not apply in case of mandatory liability, e.g. under the German Product Liability Act, in case of intent, gross negligence, injury of life, body or health, or breach of a condition which goes to the root of the contract. However, claims for damages arising from a breach of a condition, which goes to the root of the contract, shall be limited to the foreseeable damage, which is intrinsic to the contract, unless caused by intent or gross negligence or based on liability for injury of life, body or health. The above provision does not imply a change on the burden of proof to the detriment of the recipient. Subject to change without notice at any time. The interpretation of this general note shall be governed and construed according to German law without reference to any other substantive law. Copyright Transmittal, reproduction, dissemination and/or editing of this document as well as utilization of its contents and communication thereof to others without express authorization are prohibited. Offenders will be held liable for payment of damages. All rights created by patent grant or registration of a utility model or design patent are reserved. Copyright ' Siemens AG 2003 MC46_HD_V03.05 Page 2 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released Contents s mo b i l e 0 1 2 3 Document History ...................................................................................................... 7 Introduction ................................................................................................................ 8 1.1 Related documents ............................................................................................. 8 1.2 Terms and abbreviations..................................................................................... 9 1.3 Type approval ....................................................................................................12 1.4 Safety precautions .............................................................................................14 Product concept........................................................................................................16 2.1 MC46 key features at a glance...........................................................................17 2.2 Circuit concept ...................................................................................................20 3.3.3 3.3.2 3.3.1 Application Interface.................................................................................................21 3.1 Operating modes ...............................................................................................22 3.2 Power supply .....................................................................................................24 3.2.1 Power supply pins on the board-to-board connector.............................24 3.2.2 Minimizing power losses.......................................................................25 3.2.3 Monitoring power supply.......................................................................25 3.3 Power up / down scenarios ................................................................................26 Turn on MC46 ......................................................................................26 3.3.1.1 Turn on MC46 using the ignition line /IGT (Power on)...............27 3.3.1.2 Timing of the ignition process ...................................................28 3.3.1.3 Turn on MC46 using the POWER signal...................................29 3.3.1.4 Turn on MC46 using the RTC (Alarm mode).............................29 Turn off MC46 ......................................................................................30 3.3.2.1 Turn off MC46 using AT command ...........................................30 3.3.2.2 Maximum number of turn-on / turn-off cycles ............................31 3.3.2.3 Emergency shutdown using /EMERGOFF pin...........................31 Automatic shutdown .............................................................................32 3.3.3.1 Temperature dependent shutdown............................................32 3.3.3.2 Temperature control during emergency call ..............................33 3.3.3.3 Undervoltage shutdown if battery NTC is present .....................33 3.3.3.4 Undervoltage shutdown if no battery NTC is present ................34 3.3.3.5 Overvoltage shutdown ..............................................................34 3.4 Automatic GPRS Multislot Class change............................................................35 3.5 Charging control.................................................................................................36 Battery pack characteristics..................................................................37 3.5.1.1 Recommended battery pack .....................................................38 3.5.2 Implemented charging technique..........................................................39 3.5.3 Operating modes during charging ........................................................40 3.5.4 Charger requirements ..........................................................................41 3.6 Power saving .....................................................................................................42 3.6.1 No power saving (AT+CFUN=1)...........................................................42 3.6.2 NON-CYCLIC SLEEP mode (AT+CFUN=0) .........................................42 3.6.3 CYCLIC SLEEP mode (AT+CFUN=5, 6, 7 and 8) ................................43 3.6.4 Timing of the /CTS signal in CYCLIC SLEEP modes ...........................43 3.6.5 Wake up MC46 from SLEEP mode ......................................................45 3.7 Summary of state transitions (except SLEEP mode)..........................................46 3.8 RTC backup.......................................................................................................47 3.9 Serial interfaces .................................................................................................48 3.5.1 MC46_HD_V03.05 Page 3 of 99 13.11.2003 3.9.1 MC46 Hardware Interface Description Confidential / Released s mo b i l e Features supported on first and second serial interface .......................49 3.10 Audio interfaces .................................................................................................51 3.10.1 Microphone circuit ................................................................................52 3.10.2 Speech processing...............................................................................53 3.10.3 DAI timing.............................................................................................53 3.11 SIM interface......................................................................................................55 3.11.1 Requirements for using the CCIN pin ...................................................56 3.11.2 Design considerations for SIM card holder ...........................................57 3.12 Control signals ...................................................................................................58 3.12.1 Inputs ...................................................................................................58 3.12.2 Outputs.................................................................................................59 3.12.2.1 Synchronization signal .........................................................59 3.12.2.2 Using the SYNC pin to control a status LED ........................60 3.12.2.3 Behavior of the /RING0 line (ASC0 interface only)...............61 Antenna interface......................................................................................................63 4.1 Antenna installation............................................................................................63 Antenna pad.........................................................................................65 4.1.1.1 Suitable cable types ..................................................................65 4.1.2 Hirose antenna connector ....................................................................66 4.1.1 Electrical, reliability and radio characteristics .......................................................70 5.1 Absolute maximum ratings.................................................................................70 5.2 Operating temperatures .....................................................................................70 5.3 Electrical specifications of the application interface............................................71 5.4 Power supply ratings..........................................................................................76 5.4.1 Current consumption during transmit burst...........................................77 5.5 Electrical characteristics of the voiceband part...................................................78 Setting audio parameters by AT commands.........................................78 5.5.1 5.5.2 Audio programming model ...................................................................79 5.5.3 Characteristics of audio modes ............................................................80 5.5.4 Voiceband receive path ........................................................................82 Voiceband transmit path.......................................................................83 5.5.5 5.6 Air interface........................................................................................................84 5.7 Electrostatic discharge.......................................................................................86 5.8 Reliability characteristics....................................................................................87 Mechanics..................................................................................................................88 6.1 Mechanical dimensions of MC46........................................................................88 6.2 Mounting MC46 onto the application platform ....................................................91 6.3 Board-to-board connector ..................................................................................92 6.3.1 Mechanical dimensions of the Hirose DF12 connector .........................93 6.3.2 Adapter cabling ....................................................................................93 6.4 Heat sinks and thermally conductive tapes ........................................................94 Test conditions and results...................................................................94 6.4.1 Reference Approval ..................................................................................................96 7.1 Reference Equipment for Type Approval ...........................................................96 7.2 Compliance with FCC Rules and Regulations....................................................97 List of parts and accessories...................................................................................98 4 5 6 7 8 MC46_HD_V03.05 Page 4 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e Figures Figure 1: MC46 block diagram .............................................................................................20 Figure 2: Power supply limits during transmit burst ..............................................................25 Figure 3: Power-on by ignition signal....................................................................................27 Figure 4: Timing of power-on process if VDDLP is not used ................................................28 Figure 5: Timing of power-on process if VDDLP is fed from external source........................28 Figure 6: Deactivating GSM engine by /EMERGOFF signal.................................................31 Figure 7: Schematic of approved charging transistor, trickle charging and ESD protection..36 Figure 8: Battery pack circuit diagram ..................................................................................37 Figure 9: Charging process ..................................................................................................39 Figure 10: Timing of /CTS signal (example for a 2.12 s paging cycle)..................................44 Figure 11: Beginning of power saving if CFUN=5 or 7..........................................................44 Figure 12: RTC supply from capacitor..................................................................................47 Figure 13: RTC supply from rechargeable battery................................................................47 Figure 14: RTC supply from non-chargeable battery............................................................47 Figure 15: Serial interfaces ..................................................................................................48 Figure 16: Audio block diagram............................................................................................51 Figure 17: Schematic of microphone inputs .........................................................................52 Figure 18: DAI timing on transmit path .................................................................................54 Figure 19: DAI timing on receive path ..................................................................................54 Figure 20: SIM card holder of DSB45 Support Box ..............................................................57 Figure 21: Pin numbers of Molex SIM card holder on DSB45 Support Box ..........................57 Figure 22: SYNC signal during transmit burst ......................................................................59 Figure 23: LED Circuit (Example).........................................................................................60 Figure 24: Incoming voice call..............................................................................................61 Figure 25: Incoming data call ...............................................................................................61 Figure 26: URC transmission ...............................................................................................61 Figure 27: U.FL-R-SMT connector .......................................................................................63 Figure 28: Antenna pad and GND pad .................................................................................63 Figure 29: Never use antenna connector and antenna pad at the same time.......................64 Figure 30: Restricted area around antenna pad ...................................................................64 Figure 31: Mechanical dimensions of U.FL-R-SMT connector..............................................66 Figure 32: U.FL-R-SMT connector with U.FL-LP-040 plug ...................................................67 Figure 33: U.FL-R-SMT connector with U.FL-LP-066 plug ...................................................67 Figure 34: Specifications of U.FL-LP-(V)-040(01) plug.........................................................68 Figure 35: Pin assignment (top view on MC46) ....................................................................71 Figure 36: Peak current during transmit burst in mA vs. antenna impedance.......................77 Figure 37: AT audio programming model .............................................................................79 Figure 38: MC46 top view..................................................................................................88 Figure 39: Mechanical dimensions of MC46.........................................................................89 Figure 40: MC46 bottom view...............................................................................................90 Figure 41: Hirose DF12C receptacle on MC46.....................................................................92 Figure 42: Header Hirose DF12 series .................................................................................92 Figure 43: Mechanical dimensions of Hirose DF12 connector..............................................93 Figure 44: Reference equipment for approval ......................................................................96 MC46_HD_V03.05 Page 5 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e Tables Table 1: MC46 key features .................................................................................................17 Table 2: Coding schemes and maximum net data rates over air interface ...........................19 Table 3: Overview of operating modes.................................................................................22 Table 4: Power supply pins of board-to-board connector .....................................................24 Table 5: AT commands available in Alarm mode .................................................................29 Table 6: Temperature dependent behavior ..........................................................................33 Table 7: Bill of material for external charging circuit .............................................................36 Table 8: Specifications of XWODA battery pack ..................................................................38 Table 9: Comparison Charge-only and Charge mode ..........................................................40 Table 10: AT commands available in Charge-only mode......................................................41 Table 11: Wake-up events in NON-CYCLIC and CYCLIC SLEEP modes............................45 Table 12: State transitions of MC46 (except SLEEP mode) .................................................46 Table 13: DCE-DTE wiring of 1st serial interface .................................................................49 Table 14: DCE-DTE wiring of 2nd serial interface ................................................................50 Table 15: Signals of the SIM interface (board-to-board connector) ......................................55 Table 16 : Pin assignment of Molex SIM card holder on DSB45 Support Box ......................57 Table 17: Input control signals of the MC46 module.............................................................58 Table 18: MC46 synchronization signal (if SYNC pin is set to mode 0 via AT^SSYNC)........59 Table 19: Coding of the status LED......................................................................................60 Table 20: MC46 ring signal...................................................................................................62 Table 21: Return loss ...........................................................................................................63 Table 22: Product specifications of U.FL-R-SMT connector .................................................66 Table 23: Material and finish of U.FL-R-SMT connector and recommended plugs...............67 Table 24: Ordering information for Hirose U.FL Series.........................................................69 Table 25: Absolute maximum ratings ...................................................................................70 Table 26: Operating temperatures........................................................................................70 Table 27: Electrical description of application interface ........................................................72 Table 28: Power supply ratings ............................................................................................76 Table 29: Audio parameters adjustable by AT command .....................................................78 Table 30: Voiceband characteristics (typical) .......................................................................80 Table 31: Voiceband receive path ........................................................................................82 Table 32: Voiceband transmit path.......................................................................................83 Table 33: Air Interface..........................................................................................................84 Table 34: Local oscillator and intermediate frequencies used by MC46 ...............................85 Table 35: Measured electrostatic values ..............................................................................86 Table 36: Summary of reliability test conditions....................................................................87 Table 37: Ordering information DF12 series.........................................................................92 Table 38: Electrical and mechanical characteristics of the Hirose DF12C connector............92 Table 39: Tested heat sinks and thermally conductive tapes and test results ......................95 Table 40: List of parts and accessories ................................................................................98 Table 41: Molex sales contacts (subject to change) .............................................................99 Table 42: Hirose sales contacts (subject to change) ............................................................99 MC46_HD_V03.05 Page 6 of 99 13.11.2003 Document History s mo b i l e MC46 Hardware Interface Description Confidential / Released 0 Preceding document: "MC46 Hardware Interface Description" Version 02.8xb New document: "MC46 Hardware Interface Description" Version 03.05 Chapter 1.3, 7.2 3.1, 3.3.1.4, 3.5.3 3.3.1.4 3.3.3.5 3.4 3.6 3.11.1 5.1 Page What is new 12, 97 MC46 now fully type approved and labeled with CE mark Removed remark regarding charging during Alarm mode 22, 29;
40 29 34 35 42 56 70 Power saving feature is not available in Alarm mode. Modified description of overvoltage conditions. Modified description of GPRS Multislot Class change. No power saving during Alarm mode. Corrected description (added ISO/IEC 7816-3) Specified max. supply voltage BATT+. Deleted peak supply current. Modified explanation of absolute maximum ratings. Corrected parameter compressor (receive): OFF GND planes marked Description of grounding modified. Updated note regarding FCC compliance. 5.5.3 6.1 6.2 7.2 80 90 91 97 Preceding document: "MC46 Hardware Interface Description" Version 02.8xa New document: "MC46 Hardware Interface Description" Version V02.8xb Chapter 7.2 3.4 Added chapter related to FCC certification. More detailed description of GPRS Multislot Class change. Page What is new 97 35 Preceding document: "MC46 Hardware Interface Description" Version 02.8x New document: "MC46 Hardware Interface Description" Version 02.8xa Chapter 3.3.2.1 Page What is new 30 3.3.2.3 3.12.2.2 3.12.2.3 4.1.1 5.4.1 5.3 5.6 31 60 61 65 77 71ff 84f To keep /EMERGOFF pin and output pins of the serial interfaces from floating when in high impedance state use additional resistors. Added example when /EMERGOFF might be needed. LED mode of the SYNC pin recommended for testing and evaluating product design. Recommendations for utilizing /RING0 line added. More detailed information on how to connect the antenna ground pad. More detailed description of current consumption during transmit burst. Added Smith chart. Table 27 - /EMERGOFF pin and output pins of serial interface: To keep output pins from floating when in high impedance state use additional resistors. Table 34: Channel numbers of GSM 850 MHz frequency band corrected. MC46_HD_V03.05 Page 7 of 99 13.11.2003 Introduction s mo b i l e MC46 Hardware Interface Description Confidential / Released 1 This document describes the hardware interface of the Siemens MC46 module that connects to the cellular device application and the air interface. As MC46 is intended to integrate with a wide range of application platforms, all functional components are described in great detail. So this guide covers all information you need to design and set up cellular applications incorporating the MC46 module. It helps you quickly retrieve interface specifications, electrical and mechanical details and, last but not least, information on the requirements to be considered for integrating further components. Related documents 1.1
[1] MC45 / MC46 AT Command Set, Version 03.05
[2] MC46 Release Notes, Version 03.05
[3] GPRS Startup Users Guide
[4] Remote-SAT Users Guide
[5] DSB45 Support Box - Evaluation Kit for Siemens Cellular Engines
[6] Application Note 23: Installing MC45 / MC46 on DSB45
[7] Application Note 16: Upgrading MC45 / MC46 Firmware
[8] Application Note 14: Audio and Battery Parameter Download
[9] Application Note 02: Audio Interface Design
[10] Multiplexer Users Guide
[11] Multiplex Driver Developers Guide for Windows 2000 and Windows XP
[12] Multiplex Driver Installation Guide for Windows 2000 and Windows XP
[13] Application Note 22: Using TTY / CTM equipment
[14] Application Note 24: Application Developers Guide Prior to using the MC46 engines or upgrading to a new firmware release, be sure to carefully read the latest product information. To visit the Siemens Website you can use the following link:
http://www.siemens.com/wm MC46_HD_V03.05 Page 8 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released 1.2 Terms and abbreviations s mo b i l e Abbreviation Description ADC AFC AGC ANSI ARFCN ARP ASC0 / ASC1 Asynchronous Controller. Abbreviations used for first and second serial interface of Analog-to-Digital Converter Automatic Frequency Control Automatic Gain Control American National Standards Institute Absolute Radio Frequency Channel Number Antenna Reference Point ASIC B B2B BER BTS CB or CBM CE CHAP CPU CS CSD CTS DAC DAI dBm0 DCE DCS 1800 DRX DSB DSP DSR DTE DTR DTX EFR EGSM EMC MC46 Application Specific Integrated Circuit Thermistor Constant Board-to-board connector Bit Error Rate Base Transceiver Station Cell Broadcast Message Conformit Europene (European Conformity) Challenge Handshake Authentication Protocol Central Processing Unit Coding Scheme Circuit Switched Data Clear to Send Digital-to-Analog Converter Digital Audio Interface Digital level, 3.14dBm0 corresponds to full scale, see ITU G.711, A-law Data Communication Equipment (typically modems, e.g. Siemens GSM engine) Digital Cellular System, also referred to as PCN Discontinuous Reception Development Support Box Digital Signal Processor Data Set Ready Data Terminal Equipment (typically computer, terminal, printer or, for example, GSM application) Data Terminal Ready Discontinuous Transmission Enhanced Full Rate Enhanced GSM Electromagnetic Compatibility MC46_HD_V03.05 Page 9 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e Abbreviation Description ESD ETS FCC FDMA FR GMSK GPRS GSM HiZ HR I/O IC IMEI ISO ITU kbps LED Li-Ion Mbps MMI MO MS MSISDN MT NTC OEM PA PAP PBCCH PCB PCL PCM PCN PCS PDU PLL PPP Electrostatic Discharge European Telecommunication Standard Federal Communications Commission (U.S.) Frequency Division Multiple Access Full Rate Gaussian Minimum Shift Keying General Packet Radio Service Global Standard for Mobile Communications High Impedance Half Rate Input/Output Integrated Circuit International Mobile Equipment Identity International Standards Organization International Telecommunications Union kbits per second Light Emitting Diode Lithium-Ion Mbits per second Man Machine Interface Mobile Originated Mobile Station (GSM engine), also referred to as TE Mobile Station International ISDN number Mobile Terminated Negative Temperature Coefficient Original Equipment Manufacturer Power Amplifier Password Authentication Protocol Packet Switched Broadcast Control Channel Printed Circuit Board Power Control Level Pulse Code Modulation Personal Communications Network, also referred to as DCS 1800 Personal Communication System, also referred to as GSM 1900 Protocol Data Unit Phase Locked Loop Point-to-point protocol MC46_HD_V03.05 Page 10 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e Power Supply Unit Radio and Telecommunication Terminal Equipment Random Access Memory Radio Frequency Root Mean Square (value) Read-only Memory Real Time Clock Receive Direction Specific Absorption Rate Safety Extra Low Voltage Subscriber Identification Module Short Message Service Static Random Access Memory Terminal adapter (e.g. GSM engine) Time Division Multiple Access Terminal Equipment, also referred to as DTE Transmit Direction Universal asynchronous receiver-transmitter Unsolicited Result Code Unstructured Supplementary Service Data Voltage Standing Wave Ratio Abbreviation Description PSU R&TTE RAM RF RMS ROM RTC Rx SAR SELV SIM SMS SRAM TA TDMA TE Tx UART URC USSD VSWR Phonebook abbreviations FD LD MC ME ON RC SM SIM fixdialing phonebook SIM last dialing phonebook (list of numbers most recently dialed) Mobile Equipment list of unanswered MT calls (missed calls) Mobile Equipment phonebook Own numbers (MSISDNs) stored on SIM or ME Mobile Equipment list of received calls SIM phonebook MC46_HD_V03.05 Page 11 of 99 13.11.2003 89/336/EC 73/23/EC UL 60 950 MC46 Hardware Interface Description Confidential / Released s mo b i l e Type approval 1.3 MC46 has been approved to comply with the directives and standards listed below and is labeled with the CE conformity mark. European directives 99/05/EC telecommunications radio equipment and
Directive of the European Parliament and of the council of 9 March 1999 on terminal equipment and the mutual recognition of their conformity, in short referred to as R&TTE Directive 1999/5/EC Directive on electromagnetic compatibility Directive on electrical equipment designed for use within certain voltage limits (Low Voltage Directive) Standards of North American Type Approval CFR Title 47
Code of Federal Regulations, Part 2 and Part 24
(Telecommunications, PCS) US Equipment Authorization FCC
Product Safety Certification (Safety requirements) NAPRD.03 Standards of European Type Approval 3GPP TS 51.010-1
Overview of PCS Type certification review board Mobile Equipment Type Certification and IMEI control PCS Type Certification Review board (PTCRB) ETSI EN 301 511 GCF-CC ETSI EN 301 489-1 ETSI EN 301 489-7
Digital cellular telecommunications system (Phase 2); Mobile Station (MS) conformance specification.
V7.0.1 (2000-12) Candidate Harmonized European Standard
(Telecommunications for Mobile communications (GSM); Harmonized standard for mobile stations in the GSM 900 and DCS 1800 bands covering essential requirements under article 3.2 of the R&TTE directive (1999/5/EC) (GSM 13.11 version 7.0.1 Release 1998) series) Global System
Global Certification Forum - Certification Criteria
V1.1.1 (2000-09) Candidate Harmonized European Standard
(Telecommunications series) Electro Magnetic Compatibility and Radio spectrum Matters (ERM); Electro Magnetic Compatibility
(EMC) standard for radio equipment and services; Part 1: Common Technical Requirements
V1.1.1 (2000-09) Candidate Harmonized European Standard
(Telecommunications series) Electro Magnetic Compatibility and Radio spectrum Matters (ERM); Electro Magnetic Compatibility MC46_HD_V03.05 Page 12 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e
(EMC) standard for radio equipment and services; Part 7: Specific conditions for mobile and portable radio and ancillary equipment of digital cellular radio telecommunications systems (GSM and DCS) IP codes Environmental testing Safety of information technology equipment (2000) EN 60 950 Requirements of quality IEC 60068 DIN EN 60529 Compliance with international rules and regulations Manufacturers of mobile or fixed devices incorporating MC46 modules are advised to have their completed product tested and approved for compliance with all applicable national and international regulations. As a tri-band GSM/GPRS engine designed for use on any GSM network in the world, MC46 is required to pass all approvals relevant to operation on the European and North American markets. For the North American market this includes the Rules and Regulations of the Federal Communications Commission (FCC) and PTCRB, for the European market the R&TTE Directives and GCF Certification Criteria must be fully satisfied. The FCC Equipment Authorization granted to the MC46 Siemens reference application is valid only for the equipment described in Chapter 7. SAR requirements specific to handheld mobiles Mobile phones, PDAs or other handheld transmitters and receivers incorporating a GSM module must be in accordance with the guidelines for human exposure to radio frequency energy. This requires the Specific Absorption Rate (SAR) of handheld MC46 based applica-
tions to be evaluated and approved for compliance with national and/or international regulations. Since the SAR value varies significantly with the individual product design manufacturers are advised to submit their product for approval. For European and US markets the relevant directives are mentioned below. It is the responsibility of the manufacturer of the final pro-
duct to verify whether or not further standards, recommendations of directives are in force outside these areas. Products intended for sale on US markets ES 59005/ANSI C95.1 Considerations for evaluation of human exposure to Electro-
magnetic Fields (EMFs) from Mobile Telecommunication Equipment
(MTE) in the frequency range 30MHz-6GHz Products intended for sale on European markets EN 50360 Product standard to demonstrate the compliance of mobile phones with the basic restrictions related to human exposure to electro-
magnetic fields (300 MHz - 3 GHz) MC46_HD_V03.05 Page 13 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e Safety precautions 1.4 The following safety precautions must be observed during all phases of the operation, usage, service or repair of any cellular terminal or mobile incorporating MC46. Manufacturers of the cellular terminal are advised to convey the following safety information to users and operating personnel and to incorporate these guidelines into all manuals supplied with the product. Failure to comply with these precautions violates safety standards of design, manufacture and intended use of the product. Siemens AG assumes no liability for customer failure to comply with these precautions. is forbidden to prevent in an aircraft When in a hospital or other health care facility, observe the restrictions on the use of mobiles. Switch the cellular terminal or mobile off, if instructed to do so by the guidelines posted in sensitive areas. Medical equipment may be sensitive to RF energy. The operation of cardiac pacemakers, other implanted medical equipment and hearing aids can be affected by interference from cellular terminals or mobiles placed close to the device. If in doubt about potential danger, contact the physician or the manufacturer of the device to verify that the equipment is properly shielded. Pacemaker patients are advised to keep their hand-held mobile away from the pacemaker, while it is on. Switch off the cellular terminal or mobile before boarding an aircraft. Make sure it cannot be switched on inadvertently. The operation of wireless appliances interference with communications systems. Failure to observe these instructions may lead to the suspension or denial of cellular services to the offender, legal action, or both. Do not operate the cellular terminal or mobile in the presence of flammable gases or fumes. Switch off the cellular terminal when you are near petrol stations, fuel depots, chemical plants or where blasting operations are in progress. Operation of any electrical equipment in potentially explosive atmospheres can constitute a safety hazard. Your cellular terminal or mobile receives and transmits radio frequency energy while switched on. Remember that interference can occur if it is used close to TV sets, radios, computers or inadequately shielded equipment. Follow any special regulations and always switch off the cellular terminal or mobile wherever forbidden, or when you suspect that it may cause interference or danger. Road safety comes first! Do not use a hand-held cellular terminal or mobile when driving a vehicle, unless it is securely mounted in a holder for handsfree operation. Before making a call with a hand-held terminal or mobile, park the vehicle. Handsfree devices must be installed by qualified personnel. Faulty installation or operation can constitute a safety hazard. MC46_HD_V03.05 Page 14 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released SOS s mo b i l e rely solely upon any wireless device IMPORTANT!
Cellular terminals or mobiles operate using radio signals and cellular networks cannot be guaranteed to connect in all conditions. Therefore, you should never for essential communications, for example emergency calls. Remember, in order to make or receive calls, the cellular terminal or mobile must be switched on and in a service area with adequate cellular signal strength. Some networks do not allow for emergency calls if certain network services or phone features are in use (e.g. lock functions, fixed dialing etc.). You may need to deactivate those features before you can make an emergency call. Some networks require that a valid SIM card be properly inserted in the cellular terminal or mobile. MC46_HD_V03.05 Page 15 of 99 13.11.2003 Product concept s mo b i l e MC46 Hardware Interface Description Confidential / Released 2 Designed for use on any GSM network in the world, Siemens MC46 is a tri-band GSM/GPRS engine that works on the three frequencies GSM 850 MHz, GSM 1800 MHz and GSM 1900 MHz. MC46 features GPRS multislot class 10 and supports the GPRS coding schemes CS-1, CS-2, CS-3 and CS-4. To save space on the application platform, MC46 comes as an extremely slim and compact module. This makes it ideally suited for a broad range of mobile computing devices, such as laptops, notebooks, multimedia appliances, and particularly offers easy integration with PDAs, pocket organizers or miniature mobile phones. The tiny MC46 module incorporates all you need to create high-performance GSM/GPRS solutions: baseband processor, power supply ASIC, complete radio frequency circuit including a power amplifier and antenna interface. The power amplifier is directly fed from the supply voltage BATT+. The MC46 software is residing in a flash memory device. An additional SRAM enables MC46 to meet the demanding requirements of GPRS connectivity. The physical interface to the cellular application is made through a board-to-board connector. It consists of 50 pins, required for controlling the unit, transferring data and audio signals and providing power supply lines. MC46 comprises two serial interfaces (ASC0 and ASC1) giving you maximum flexibility for easy integration with the Man-Machine Interface (MMI). An extremely versatile audio concept offers various audio interfaces, each available on the board-to-board connector: a digital audio interface (DAI) and two analog audio interfaces. This allows you to connect up to three audio devices in any combination, all at the same time. Using AT commands you can easily switch back and forth and select different audio modes. The external dual-band or triple-band antenna can be connected optionally to a connector on the top side or to a pad on the bottom side. The power saving technique minimizes current consumption to as low as 3mA. In SLEEP mode, MC46 is able to wake up on demand and to resume power saving automatically if no activity is required. For battery powered applications, MC46 features a charging control which can be used to charge a Li-Ion battery. The charging circuit must be implemented outside the module on the application platform. MC46_HD_V03.05 Page 16 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released 2.1 MC46 key features at a glance s mo b i l e Table 1: MC46 key features Feature Power supply Power saving Charging Frequency bands GSM class Transmit power GPRS connectivity SIM interface External antenna Audio interfaces Audio features Two serial interfaces:
ASC0, ASC1 GPRS:
DATA Implementation Single supply voltage 3.2V 4.5V Minimizes power consumption in SLEEP mode to 3mA Supports charging control for Li-Ion battery Tri-band GSM 850, GSM 1800, GSM 1900 Compliant to GSM Phase 2/2+
Small MS Class 4 (2W) at GSM 850 Class 1 (1W) at GSM 1800 and GSM 1900 GPRS multi-slot class 10 GPRS mobile station class B Supported SIM card: 3V External SIM card reader has to be connected via interface connector
(note that card reader is not part of MC46) Connected via 50 antenna connector or antenna pad Two analog audio interfaces, one digital audio interface (DAI) Speech codec modes:
Half Rate (ETS 06.20) Full Rate (ETS 06.10) Enhanced Full Rate (ETS 06.50 / 06.60 / 06.80) Adaptive Multi Rate (AMR) Handsfree operation Echo cancellation Noise reduction 2.65V level, bi-directional bus for AT commands and data ASC0 full-featured 8-wire serial interface. Supports RTS0/CTS0 hardware handshake and software XON/XOFF flow control. Multiplex ability according to GSM 07.10 Multiplexer Protocol. ASC1
- 4-wire serial interface. Supports RTS1/CTS1 hardware handshake and software XON/XOFF flow control. Baud rate: 300bps ... 230kbps on ASC0 and ASC1 Autobauding (on ASC0 only) detects 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200, 230400 bps GPRS data downlink transfer: max. 85.6 kbps (see Table 2) GPRS data uplink transfer: max. 42.8 kbps (see Table 2) Coding scheme: CS-1, CS-2, CS-3 and CS-4 MC46 supports two protocols PAP (Password Authentication Protocol) and CHAP (Challenge Handshake Authentication Protocol) commonly used for PPP connections. the Support of Packet Switched Broadcast Control Channel (PBCCH) allows MC46_HD_V03.05 Page 17 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e Feature SMS Implementation CSD:
WAP:
you to benefit from enhanced GPRS performance when offered by the network operators. CSD transmission rates: 2.4, 4.8, 9.6, 14.4 kbps, non-transparent, V.110 WAP compliant MT, MO, CB, Text and PDU mode SMS storage: SIM card plus 25 SMS locations in the mobile equipment Transmission of SMS alternatively over CSD or GPRS. Preferred mode can be user-defined. Group 3: Class 1, Class 2 Unstructured Supplementary Services Data (USSD) support Supported phonebook types: SM, FD, LD, MC, RC, ON, ME FAX USSD Phonebook management SIM Application Toolkit Supports SAT class 3, GSM 11.14 Release 98 Ringing tones Offers a choice of 7 different ringing tones / melodies, easily selectable with AT command Implemented Programmable via AT command To benefit from TTY communication via GSM, CTM equipment can be connected to one of the three audio interfaces.
-20C to +55C Normal operation:
Restricted operation:
-25C to -20C and +55C to +70C Constant temperature control prevents damage to MC46 when the specified temperature is exceeded. When an emergency call is in progress is deactivated. temperature shutdown the automatic functionality 53 +0.15 x 34 +0.15 x 3.5+0.3 mm 10g Weight:
Firmware upgradable over serial interface and SIM interface The DSB45 Support Box is an evaluation kit designed to test and type approve Siemens cellular engines and provide a sample configuration for application engineering. See Chapter 8 for ordering information. Real time clock Timer function Support of TTY/CTM Temperature range Temperature control and auto switch-off Firmware upgrade Evaluation kit Physical characteristics Size:
MC46_HD_V03.05 Page 18 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released Table 2: Coding schemes and maximum net data rates over air interface s mo b i l e Coding scheme CS-1:
CS-2:
CS-3:
CS-4:
1 Timeslot 9.05 kbps 13.4 kbps 15.6 kbps 21.4 kbps 2 Timeslots 18.1 kbps 26.8 kbps 31.2 kbps 42.8 kbps 4 Timeslots 36.2 kbps 53.6 kbps 62.4 kbps 85.6 kbps Please note that the values stated above are maximum ratings which, in practice, are influenced by a great variety of factors, primarily, for example, traffic variations and network coverage. MC46_HD_V03.05 Page 19 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e Circuit concept 2.2 Figure 1 shows a block diagram of the MC46 module and illustrates the major functional components:
GSM / GPRS baseband block:
Baseband controller operating at 26MHz Power supply ASIC Flash SRAM Application interface (board-to-board connector) GSM RF block:
RF transceiver RF power amplifier RF frontend (antenna connector) RF Power Amplifier RF Section Interface RF - Baseband Send Receive Control Measuring Network MC46 Baseband Controller Data Adr Control Data Adr Control SRAM Flash 5 9 8 4 DAI 2x Audio ASC0 ASC1 SYNC 6 SIM Interface VDD VDDLP
/EMERGOFF e c a f r e t n I n o i t a c i
) s n p 0 5
(
/IGT POWER i l p p A CHARGE BATT+
GND 5 5 BATT_TEMP CCIN CCVCC 4 SIM Charger input Ext. Charging Circuit
+
NTC CCRST CCCLK CCIO CCIN CCVCC
(GND) 4 2 Power Supply ASIC Figure 1: MC46 block diagram MC46_HD_V03.05 Page 20 of 99 13.11.2003 Application Interface s mo b i l e MC46 Hardware Interface Description Confidential / Released 3 MC46 is equipped with a 50-pin 0.5mm pitch board-to-board connector that connects to the cellular application platform. The host incorporates several sub-interfaces described in the following chapters:
Power supply and charging control (see Chapters 3.2 and 3.3) Dual serial interface (see Chapter 3.9) Two analog audio interfaces and a digital audio interface (see Chapter 3.10) SIM interface (see Chapter 3.11) Electrical and mechanical characteristics of the board-to-board connector are specified in Chapter 6.3. Ordering information for mating connectors and cables are included. interface MC46_HD_V03.05 Page 21 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e Operating modes 3.1 The table below briefly summarizes the various operating modes referred to in the following chapters. Table 3: Overview of operating modes Mode Normal operation Function GSM / GPRS SLEEP Various powersave modes set with AT+CFUN to allow permanent access command. Software is active to minimum extent. If the module was registered to the GSM network in IDLE mode, it is registered and paging with the BTS in SLEEP mode, too. Power saving can be chosen at different levels: The NON-CYCLIC SLEEP mode (AT+CFUN=0) disables the AT interface. The CYCLIC SLEEP modes AT+CFUN=5, 6, 7 and 8 alternatingly activate and deactivate the AT interfaces to all AT commands. Software is active. Once registered to the GSM network, paging with BTS is carried out. The module is ready to send and receive. Connection between two subscribers is in progress. Power consumption depends on network coverage individual settings, such as DTX off/on, FR/EFR/HR, hopping sequences, antenna. Module is ready for GPRS data transfer, but no data is currently sent or received. Power consumption depends on network settings and GPRS configuration (e.g. multislot settings). GPRS data transfer in progress. Power consumption depends on network settings (e.g. power control level), uplink / downlink data rates and GPRS configuration
(e.g. used multislot settings). GSM IDLE GSM TALK GPRS IDLE GPRS DATA POWER DOWN Alarm mode Normal shutdown after sending the AT^SMSO command. The Power Supply ASIC (PSU-ASIC) disconnects the supply voltage from the baseband part of the circuit. Only a voltage regulator in the PSU-ASIC is active for powering the RTC. Software is not active. The serial interfaces are not accessible. Operating voltage (connected to BATT+) remains applied. Restricted operation launched by RTC alert function while the module is in POWER DOWN mode. Module will not be registered to GSM network. Limited number of AT commands is accessible. MC46_HD_V03.05 Page 22 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e Function Mode Charge-only mode Limited operation for battery powered applications. Enables charging while module is detached from GSM network. Limited number of AT commands is accessible. There are several ways to launch Charge-only mode:
From POWER DOWN mode: Connect charger to the charger input pin of the external charging circuit and the modules POWER pin when MC46 was powered down by AT^SMSO. Charge mode during normal operation From Normal mode: Connect charger to the charger input pin of the external charging circuit and the modules POWER pin, then enter AT^SMSO. Normal operation (SLEEP, IDLE, TALK, GPRS IDLE, GPRS DATA) and charging running in parallel. Charge mode changes to Charge-only mode when the module is powered down before charging has been completed. See Table 11 and Table 12 for the various options of waking up MC46 and proceeding from one mode to another. MC46_HD_V03.05 Page 23 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e Power supply 3.2 The power supply of MC46 has to be a single voltage source of VBATT+= 3.2V...4.5V. It must be able to provide sufficient current in a transmit burst which typically rises to 2A. Beyond that, the power supply must be able to account for increased current consumption if the module is exposed to inappropriate conditions, for example antenna mismatch. For further details see Chapters 3.2.2 and 5.4.1. All the key functions for supplying power to the device are handled by an ASIC power supply. The ASIC provides the following features:
Stabilizes the supply voltages for the GSM baseband using low drop linear voltage regulators. Controls the modules power up and power down procedures. A watchdog logic implemented in the baseband processor periodically sends signals to the ASIC, allowing it to maintain the supply voltage for all digital MC46 components. Whenever the watchdog pulses fail to arrive constantly, the module is turned off. Delivers, across the VDD pin, a regulated voltage of 2.9V. The output voltage VDD may be used to supply, for example, an external LED or a level shifter. However, the external circuitry must not cause any spikes or glitches on voltage VDD. This voltage is not available in POWER DOWN mode. Therefore, the VDD pin can be used to indicate whether or not MC46 is in POWER DOWN mode. Power supply pins on the board-to-board connector Provides power to the SIM interface. The RF power amplifier is driven directly from BATT+. 3.2.1 Five BATT+ pins of the board-to-board connector are dedicated to connect the supply voltage, five GND pins are recommended for grounding. The values stated below must be measured directly at the reference points on the MC46 board (TP BATT+ and TP GND illustrated in Figure 40). The POWER and CHARGE pins serve as control signals for charging a Li-Ion battery. VDDLP can be used to back up the RTC. Table 4: Power supply pins of board-to-board connector Signal name BATT+
Parameter 3.2 V...4.5 V, Ityp 2 A during transmit burst The minimum operating voltage must not fall below 3.2 V, not even in case of voltage drop. 0 V I/O Description I/O Positive operating voltage Reference points are the test points Ground This line signalizes to the processor that the charger is connected. Control signal for external charging transistor
-
I O I/O Can be used to back up the RTC when VBATT+ is not applied. See Chapter 3.8 UOUT,max < VBATT+
UIN = 2.0 V...5.5 V Ri = 1kW Iin,max = 30A GND POWER CHARGE VDDLP MC46_HD_V03.05 Page 24 of 99 13.11.2003 s mo b i l e MC46 Hardware Interface Description Confidential / Released 3.2.2 Minimizing power losses When designing the power supply for your application please pay specific attention to power losses. Ensure that the input voltage VBATT+ never drops below 3.2 V on the MC46 board, not even in a transmit burst where current consumption can rise to typical peaks of 2A. It should be noted that MC46 switches off when exceeding these limits. Any voltage drops that may occur in a transmit burst should not exceed 400mV. For further details see Chapter 5.4. The best approach to reducing voltage drops is to use a board-to-board connection as recommended, and a low impedance power source. The resistance of the power supply lines on the host board and of a battery pack should also be considered. Note:
If the application design requires an adapter cable between both board-to-board connectors, use a flex cable as short as possible in order to minimize power losses. Example:
If the length of the flex cable reaches the maximum length of 200mm, this connection may cause, for example, a resistance of 50m in the BATT+ line and 50m in the GND line. As a result, a 2A transmit burst would add up to a total voltage drop of 200mV. Plus, if a battery pack is involved, further losses may occur due to the resistance across the battery lines and the internal resistance of the battery. Transmit burst 2A Transmit burst 2A BATT+
min. 3.2V Ripple Drop Figure 2: Power supply limits during transmit burst The input voltage VBATT+ must be measured directly at the test points on the MC46 board (TP BATT+ and TP GND illustrated in Figure 40). 3.2.3 Monitoring power supply To help you monitor the supply voltage you can use the AT^SBV command which returns the voltage measured at TP BATT+ and GND. The voltage is continuously measured at intervals depending on the operating mode on the RF interface. The duration of measuring ranges from 0.5s in TALK/DATA mode to 50s when MC46 is deregistered. The displayed voltage (in mV) is averaged over the last measuring period before the AT^SBV command was executed. For details please refer to [1]. MC46_HD_V03.05 Page 25 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e Power up / down scenarios 3.3 In general, be sure not to turn on MC46 while it is out of the operating range of voltage and temperature stated in Chapters 5.2 and 5.3. MC46 would immediately switch off after having started and detected these inappropriate conditions. 3.3.1 MC46 can be activated in a variety of ways, which are described in the following chapters:
via ignition line /IGT: starts normal operating state (see Chapters 3.3.1.1 and 3.3.1.2) via POWER line: starts charging algorithm (see Chapters 3.5.3 and 3.3.1.3) via RTC interrupt: starts Alarm mode (see Chapter 3.3.1.4) Turn on MC46 MC46_HD_V03.05 Page 26 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e Turn on MC46 using the ignition line /IGT (Power on) 3.3.1.1 To switch on MC46 the /IGT (Ignition) signal needs to be driven to ground level for at least 100ms and not earlier than 10ms after the last falling edge of VDD. This can be accomplished using an open drain/collector driver in order to avoid current flowing into this pin. min. 10ms HiZ min. 100ms ca. 60ms HiZ BATT+
/IGT VDD
/TXD0
/TXD1
/DSR0
/EMERGOFF Serial interfaces ASC0 and ASC1 Software controlled Undefined ca. 300ms For details please see Chapter 3.3.1.2 Inactive ca. 900ms Active Figure 3: Power-on by ignition signal If configured to a fix baud rate, MC46 will send the result code ^SYSSTART to indicate that it is ready to operate. This result code does not appear when autobauding is active. See Chapter AT+IPR in [1]. In a battery operated MC46 application, the duration of the /IGT signal must be 1s minimum when the charger is connected and you may want to go from charging to Normal mode. MC46_HD_V03.05 Page 27 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e Timing of the ignition process 3.3.1.2 When designing your application platform take into account that powering up MC46 requires the following steps. The ignition line cannot be operated until VBATT+ passes the level of 3.0V. The ignition line shall not be operated earlier than 10ms after the last falling edge of VDD. 10ms after VBATT+ has reached 3.0V the ignition line can be switched low. The duration of the falling edge must not exceed 1ms. Another 100ms are required to power up the module. Ensure that VBATT+ does not fall below 3.0V while the ignition line is driven. Otherwise the module cannot be activated. If the VDDLP line is fed from an external power supply as explained in Chapter 3.8, the
/IGT line is HiZ before the rising edge of BATT+. 3.0V BATT+
0V
/IGT HiZ HiZ 10ms min. 100ms max. 1ms Figure 4: Timing of power-on process if VDDLP is not used 3.0V BATT+
0V
/IGT HiZ HiZ 10ms min. 100ms max. 1ms Figure 5: Timing of power-on process if VDDLP is fed from external source MC46_HD_V03.05 Page 28 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e Turn on MC46 using the POWER signal 3.3.1.3 As detailed in Chapter 3.5.3, the charging adapter can be connected regardless of the modules operating mode (except for Alarm mode). If the charger is connected to the charger input of the external charging circuit and the modules POWER pin while MC46 is off, processor controlled fast charging starts (see Chapter 3.5.2). MC46 enters a restricted mode, referred to as Charge-only mode where only the charging algorithm will be launched. During the Charge-only mode MC46 is neither logged on to the GSM network nor are the serial interfaces fully accessible. To switch to normal operation and log on to the GSM network, the /IGT line needs to be activated. Turn on MC46 using the RTC (Alarm mode) 3.3.1.4 Another power-on approach is to use the RTC, which is constantly supplied with power from a separate voltage regulator in the power supply ASIC. The RTC provides an alert function which allows to wake up MC46 while power is off. To prevent the engine from unintentionally logging into the GSM network, this procedure only enables restricted operation, referred to as Alarm mode. It must not be confused with a wake-up or alarm call that can be activated by using the same AT command, but without switching off power. Use the AT+CALA command to set the alarm time. The RTC retains the alarm time if MC46 was powered down by AT^SMSO. Once the alarm is timed out and executed, MC46 enters into the Alarm mode. This is indicated by an Unsolicited Result Code (URC) which reads:
Note that this URC is the only indication of the Alarm mode and will not appear when autobauding was activated (due to the missing synchronization between DTE and DCE upon start-up). Therefore, it is recommended to select a fixed baud rate before using the Alarm mode. In Alarm mode only a limited number of AT commands is available. For further instructions refer to the AT Command Set. Table 5: AT commands available in Alarm mode
^SYSSTART ALARM MODE AT command AT+CALA AT+CCLK AT^SBC AT^SCTM AT^SMSO Use Set alarm time Set date and time of RTC In Alarm mode, you can only query the present current consumption and check whether or not a charger is connected. The battery capacity is returned as 0, regardless of the actual voltage (since the values measured directly on the cell are not delivered to the module). Query temperature range, enable/disable URCs to report critical temperature ranges Power down GSM engine For the GSM engine to change from the Alarm mode to full operation (normal operating mode) it is necessary to drive the ignition line to ground. This must be implemented in your host application as described in Chapter 3.3.1.1. If your host application uses the SYNC pin to control a status LED as described in Chapter 3.12.2.2, please note that the LED is off while the GSM engine is in Alarm mode. MC46_HD_V03.05 Page 29 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released 3.3.2 To switch the module off the following procedures may be used:
Normal shutdown procedure: Software controlled by sending the AT^SMSO command s mo b i l e Turn off MC46 over the serial application interface. See Chapter 3.3.2.1. Emergency shutdown: Hardware driven by switching the /EMERGOFF line of the board-
to-board-connector to ground = immediate shutdown of supply voltages, only applicable if the software controlled procedure fails! See Chapter 3.3.2.3. Automatic shutdown: See Chapter 3.3.3 a) Takes effect if undervoltage is detected. b) Takes effect if MC46 board temperature exceeds critical limit. Turn off MC46 using AT command 3.3.2.1 The best and safest approach to powering down MC46 is to issue the AT^SMSO command. This procedure lets MC46 log off from the network and allows the software to enter into a secure state and safe data before disconnecting the power supply. The mode is referred to as POWER DOWN mode. In this mode, only the RTC stays active. Before switching off the device sends the following response:
After sending AT^SMSO do not enter any other AT commands. There are two ways to verify when the module turns off:
Wait for the URC ^SHUTDOWN. It indicates that all important data have been stored to OK
^SHUTDOWN
^SMSO: MS OFF the Flash and that the complete system turns off in less than 1 second. Also, you can monitor the VDD pin. The low state of VDD definitely indicates that the module is switched off. Be sure not to disconnect the operating voltage VBATT+ before the URC ^SHUTDOWN has been issued or the VDD signal has gone low. Otherwise you run the risk of losing data. While MC46 is in POWER DOWN mode the application interface is switched off and must not be fed from any other source. Therefore, your application must be designed to avoid any current flow into any digital pins of the application interface. Note: In POWER DOWN mode, the /EMERGOFF pin, the output pins of the ASC0 interface
/RXD0, /CTS0, /DCD0, /DSR0, /RING0 and the output pins of the ASC1 interface
/RXD1 and /CTS1 are switched to high impedance state. If this causes the associated input pins of your application to float, you are advised to integrate an additional resistor (100 k 1 M) at each line. In the case of the
/EMERGOFF pin use a pull-down resistor tied to GND. In the case of the serial inter-
face pins you can either connect pull-up resistors to the VDD line, or pull-down resistors to GND. MC46_HD_V03.05 Page 30 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released 3.3.2.2 Maximum number of turn-on / turn-off cycles Each time the module is shut down, data will be written from volatile memory to flash memory. The guaranteed maximum number of write cycles is limited to 100.000. s mo b i l e 3.3.2.3 Caution:
Emergency shutdown using /EMERGOFF pin Use the /EMERGOFF pin only when, due to serious problems, the software is not responding for more than 5 seconds. Pulling the /EMERGOFF pin causes the loss of all information stored in the volatile memory since power is cut off immediately. Therefore, this procedure is intended only for use in case of emergency, e.g. if the host controller experienced a watchdog reset and afterwards MC46 fails to shut down properly or fails to respond. The /EMERGOFF signal is available on the board-to-board connector. To control the
/EMERGOFF line it is recommended to use an open drain / collector driver. To turn the GSM engine off, the /EMERGOFF line has to be driven to ground for 3.2s. BATT+
/IGT VDD Internal reset
/EMERG-
OFF max. 3.2s Controlled by MC46 software Controlled by external application Figure 6: Deactivating GSM engine by /EMERGOFF signal How does it work:
Voltage Vbatt+ is permanently applied to the module. The module is active while the internal reset signal is kept at high level. During operation of MC46 the baseband controller generates regular watchdog pulses at intervals. Once the EMERGOFF pin is grounded these watchdog pulses are cut off from the power supply ASIC. The power supply ASIC shuts down the internal supply voltages of MC46 after max. 3.2s and the module off. output Consequently, voltage at VDD is switched off. turns the MC46_HD_V03.05 Page 31 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released 3.3.3 Automatic shutdown takes effect if Automatic shutdown s mo b i l e the MC46 board is exceeding the critical limits of overtemperature or undertemperature the battery is exceeding the critical limits of overtemperature or undertemperature undervoltage is detected The automatic shutdown procedure is equivalent to the power-down initiated with the AT^SMSO command, i.e. MC46 logs off from the network and the software enters a secure state avoiding loss of data. NOTE: This is not true for overvoltage conditions, and if an unrecoverable hardware or software error occurs, see below for details Alert messages transmitted before the device switches off are implemented as Unsolicited Result Codes (URCs). The presentation of these URCs can be enabled or disabled with the two AT commands AT^SBC and AT^SCTM. The URC presentation mode varies with the condition, please see Chapters 3.3.3.1 to 3.3.3.4 for details. For further instructions on AT commands refer to [1]. Temperature dependent shutdown 3.3.3.1 The board temperature is constantly monitored by an internal NTC resistor located on the PCB. The NTC that detects the battery temperature must be part of the battery pack circuit as described in Chapter 3.5. The values detected by either NTC resistor are measured directly on the board or the battery and therefore, are not fully identical with the ambient temperature. Each time the board or battery temperature goes out of range or back to normal, MC46 instantly displays an alert (if enabled). URCs indicating the level "1" or "-1" allow the user to take appropriate precautions, such as protecting the module from exposure to extreme conditions. The presentation of the URCs depends on the settings selected with the AT^SCTM write command:
AT^SCTM=1: Presentation of URCs is always enabled. AT^SCTM=0 (default): Presentation of URCs is enabled for 15 seconds time after start-up of MC46. After 15 seconds operation, the presentation will be disabled, i.e. no alert messages can be generated. URCs indicating the level "2" or "-2" are instantly followed by an orderly shutdown. The presentation of these URCs is always enabled, i.e. they will be output even though the factory setting AT^SCTM=0 was never changed. The maximum temperature ratings are stated in Table 26. Refer to Table 6 for the associated URCs. All statements are based on test conditions according to IEC 60068-2-2
(still air). MC46_HD_V03.05 Page 32 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released Table 6: Temperature dependent behavior s mo b i l e Caution: Tamb of battery close to overtemperature limit. Caution: Tamb of board close to overtemperature limit. Caution: Tamb of battery close to undertemperature limit. Caution: Tamb of board close to undertemperature limit. Battery back to uncritical temperature range. Board back to uncritical temperature range. Sending temperature alert (15 s after start-up, otherwise only if URC presentation enabled)
^SCTM_A: 1
^SCTM_B: 1
^SCTM_A: -1
^SCTM_B: -1
^SCTM_A: 0
^SCTM_B: 0 Automatic shutdown (URC appears no matter whether or not presentation was enabled)
^SCTM_A: 2
^SCTM_B: 2
^SCTM_A: -2
^SCTM_B: -2 Alert: Tamb of battery equal or beyond overtemperature limit. MC46 switches off. Alert: Tamb of board equal or beyond overtemperature limit. MC46 switches off. Alert: Tamb of battery equal or below undertemperature limit. MC46 switches off. Alert: Tamb of board equal or below undertemperature limit. MC46 switches off. Temperature control during emergency call 3.3.3.2 If the temperature limit is exceeded while an emergency call is in progress the engine continues to measure the temperature, but deactivates the shutdown functionality. If the temperature is still out of range when the call ends, the module switches off immediately
(without another alert message).
^SBC: Undervoltage. 3.3.3.3 Undervoltage shutdown if battery NTC is present In applications where the modules charging technique is used and an NTC is connected to the BATT_TEMP terminal, the software constantly monitors the applied voltage. If the measured battery voltage is no more sufficient to set up a call the following URC will be presented:
The message will be reported, for example, when you attempt to make a call while the voltage is close to the critical limit and further power loss is caused during the transmit burst. To remind you that the battery needs to be charged soon, the URC appears several times before the module switches off. To enable or disable the URC use the AT^SBC command. The URC will be enabled when you enter the write command and specify the power consumption of your GSM application. Step by step instructions are provided in [1]. MC46_HD_V03.05 Page 33 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e 3.3.3.4 Undervoltage shutdown if no battery NTC is present The undervoltage protection is also effective in applications, where no NTC connects to the BATT_TEMP terminal. Thus, you can take advantage of this feature even though the application handles the charging process or MC46 is fed by a fixed supply voltage. All you need to do is executing the write command AT^SBC=<current> which automatically enables the presentation of URCs. You do not need to specify <current>. Whenever the supply voltage falls below the specified value (see Table 28) the URC appears several times before the module switches off.
^SBC: Undervoltage 3.3.3.5 Overvoltage shutdown For overvoltage conditions, no software controlled shutdown is implemented. If the supply voltage exceeds the maximum value specified in Table 28, loss of data and even unrecoverable hardware damage can occur. Keep in mind that several MC46 components are directly linked to BATT+ and, therefore, the supply voltage remains applied at major parts of MC46. Especially the power amplifier is very sensitive to high voltage and might even be destroyed. MC46_HD_V03.05 Page 34 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e Automatic GPRS Multislot Class change 3.4 Temperature control is also effective for operation in GPRS Multislot Class 10. If the board temperature increases to the limit specified for restricted operation1) while data are transmitted over GPRS, the module automatically reverts from GPRS Multislot Class 10 (2 Tx) to Class 8 (1Tx). This reduces the power consumption and, consequently, causes the boards temperature to decrease. Once the temperature drops to a value of 5 degrees below the limit of restricted operation, MC46 returns to the higher Multislot Class. If the temperature stays at the critical level or even continues to rise, MC46 will not switch back to the higher class. After a transition from Multislot Class 10 to Multislot Class 8 a possible switchback to Multislot Class 10 is blocked for one minute. Please note that there is not one single cause of switching over to a lower GPRS Multislot Class. Rather it is the result of an interaction of several factors, such as the board temperature that depends largely on the ambient temperature, the operating mode and the transmit power. Furthermore, take into account that there is a delay until the network proceeds to a lower or, accordingly, higher Multislot Class. The delay time is network dependent. In extreme cases, if it takes too much time for the network and the temperature cannot drop due to this delay, the module may even switch off as described in Chapter 3.3.3.1. 1) See Table 26 for temperature limits known as restricted operation. MC46_HD_V03.05 Page 35 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e Charging control 3.5 MC46 integrates a charging management for Li-Ion batteries. You can skip this chapter if charging is not your concern, or if you are not using the implemented charging algorithm. MC46 has no on-board charging circuit. To benefit from the implemented charging management you are required to install a charging circuit within your application. In this case, MC46 needs to be powered from a Li-Ion battery pack, e.g. as specified in Table 8. The module only delivers, via its POWER line and CHARGE line, the control signals needed to start and stop the charging process. The charging circuit should include a transistor and should be designed as illustrated in Figure 7. A list of parts recommended for the external circuit is given in Table 7. Input from charger
(5.5V - 8V) under load pcb spark gap 470R 1SS355 4V3 SI3441DV CRS04 to POWER to BATT+
1/5 ESDA6V1-5W6 BATT_TEMP 100nF 10k 3k3 1/5 ESDA6V1-5W6 Figure 7: Schematic of approved charging transistor, trickle charging and ESD protection CHARGE Table 7: Bill of material for external charging circuit Part SI3441DV 1SS355 CRS04 4V3 Description p-chan 2.5V (G-S) MOSFET
(TSOP-6) 100mA Si-diode (UMD2) 1A Schottky diode 250mW; 200mA;
4.3V Z-Diode (SOD323) First supplier Second supplier VISHAY: SI3441DV-T1 NEC: UPA1911TE-T1 ROHM: 1SS355TE-18 Toshiba: 1SS352TPH3 Toshiba: CRS04
-
Philips: PDZ4.3B ROHM:
UDZS4.3B UDZ4.3B ESDA6V1-5W6 ESD protection TRANSIL array STM: ESDA6V1-5W6 470R, 3k3, 10k Resistor, e.g. 0805 or 0603 100nF PCB spark gap 0.2mm spark gap on PCB Ceramic capacitor 50V
-
-
-
-
-
-
-
MC46_HD_V03.05 Page 36 of 99 13.11.2003 s mo b i l e Battery pack characteristics MC46 Hardware Interface Description Confidential / Released 3.5.1 The charging algorithm has been optimized for a Li-Ion battery pack that meets the characteristics listed below. It is recommended that the battery pack you want to integrate into your MC46 application is compliant with these specifications. This ensures reliable operation, proper charging and, particularly, allows you to monitor the battery capacity using the AT^SBC command (see [1] for details). Failure to comply with these specifications might cause AT^SBC to deliver incorrect battery capacity values. A battery pack especially designed to operate with MC46 modules is specified in Chapter 3.5.1.1. Li-Ion battery pack specified for a maximum charging voltage of 4.2 V and a capacity of 800 mAh. Battery packs with a capacity down to 600 mAh or more than 800 mAh are allowed, too. Since charging and discharging largely depend on the battery temperature, the battery pack should include an NTC resistor. If the NTC is not inside the battery it must be in thermal contact with the battery. The NTC resistor must be connected between BATT_TEMP and GND. Required NTC characteristics are: 10 k +5% @ 25C, B25/85 =
3435K +3% (alternatively acceptable: 10 k +2% @ 25C, B25/50 = 3370K +3%). Please note that the NTC is indispensable for proper charging, i.e. the charging process will not start if no NTC is present. Ensure that the pack incorporates a protection circuit capable of detecting overvoltage
(protection against overcharging), undervoltage (protection against deep discharging) and overcurrent. The circuit must be insensitive to pulsed current. On the MC46 module, a built-in measuring circuit constantly monitors the supply voltage. In the event of undervoltage, it causes MC46 to power down. Undervoltage thresholds are specific to the battery pack and must be evaluated for the intended model. When you evaluate undervoltage thresholds, consider both the current consumption of MC46 and of the application circuit. The internal resistance of the battery and the protection should be as low as possible. It is recommended not to exceed 150m, even in extreme conditions at low temperature. The battery cell must be insensitive to rupture, fire and gassing under extreme conditions of temperature and charging (voltage, current). The battery pack must be protected from reverse pole connection. For example, the casing should be designed to prevent the user from mounting the battery in reverse orientation. to GND that to BATT+
includes to BATT_TEMP The battery pack must be approved to satisfy the requirements of CE conformity. Figure 8 shows the circuit diagram of a typical battery pack design the protection elements described above. Figure 8: Battery pack circuit diagram Protection Circuit Battery cell Polyfuse
+ -
NTC J MC46_HD_V03.05 Page 37 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e 3.5.1.1 Recommended battery pack The following battery pack has been especially designed for use with MC46 modules. Table 8: Specifications of XWODA battery pack Product name, type
+86-755-27623078 Phone: +86-755-27623789 ext. 370 Fax:
Email: waichard@xwoda.com.cn XWODA, Li-Ion, 3.6V, 800mAh Shenzhen Xwoda Electronic Co., Ltd Building C, Tongfukang Industrial Zone Shiyan Town, Baoan District Shenzen P.R. China Contact:
Waichard Tsui 3.6V 800mAh 10k 5% @ 25C, B (25/85)=3435K 3%
4.325 0.025V 4.075 0.025V 2.5 0.05V 2.9 0.5V 3 0.5A
<5A 0.5A 8~16ms 50s 31~125ms 1s
<130m Vendor To place orders or obtain more information please contact:
Nominal voltage Capacity NTC Overcharge detection voltage Overcharge release voltage Overdischarge detection voltage Overdischarge release voltage Overcurrent detection Nominal working current Current of low voltage detection Overcurrent detection delay time Short detection delay time Overdischarge detection delay time Overcharge detection delay time Internal resistance MC46_HD_V03.05 Page 38 of 99 13.11.2003 s mo b i l e Implemented charging technique MC46 Hardware Interface Description Confidential / Released 3.5.2 If the external charging circuit follows the recommendation of Figure 7, the charging process consists of trickle charging and processor controlled fast charging. For this solution, the fast charging current provided by the charger or any other external source must be limited to 500mA. Trickle charging Trickle charging starts when the charger is connected to the charger input of the external charging circuit and the modules POWER pin. The charging current depends on the voltage difference between the charger input of the external charging circuit and BATT+
of the module. Trickle charging stops when the battery voltage reaches 3.6V. Fast charging After trickle charging has raised the battery voltage to 3.2V within 60 minutes +10% from connecting the charger, the power ASIC turns on and wakes up the baseband processor. Now, processor controlled fast charging begins. If the battery voltage was already above 3.2V, processor controlled fast charging starts just after the charger was connected to the charger input of the external charging circuit and the modules POWER pin. If MC46 was in POWER DOWN mode, it turns on and enters the Charge-only mode along with fast charging (see also Chapter 3.3.1.3). Fast charging delivers a constant current until the battery voltage reaches 4.2V and then proceeds with varying charge pulses. As shown in Figure 5, the pulse duty cycle is reduced to adjust the charging procedure and prevent the voltage from overshooting beyond 4.2V. Once the pulse width reaches the minimum of 100ms and the duty cycle does not change for 2 minutes, fast charging is completed. Fast charging can only be accomplished in a temperature range from 0C to +45C. Voltage 4.3 4.2 3.8 3.4 3.0 100ms 2 ... 0.1s 100ms 0.1 ... 2s Constant current tOFF = 100 ms tON = 100 ms Time Figure 9: Charging process Note: Do not connect the charger to the BATT+ lines. Only the charger input of the external charging circuit is intended as input for charging current! The POWER pin of MC46 is the input only for indicating a connected charger!
The battery manufacturer must guarantee that the battery complies with the described charging technique. MC46_HD_V03.05 Page 39 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released What to do if software controlled charging does not start up?
If trickle charging fails to raise the battery voltage to 3.2V within 60 minutes +10%, processor controlled charging does not begin. To start fast charging you can do one of the following:
Once the voltage has risen above its minimum of 3V, you can try to start software s mo b i l e controlled charging by pulling the /IGT line to ground. If the voltage is still below 3V, driving the /IGT line to ground switches the timer off. Without the timer running, MC46 will not proceed to software controlled charging. To restart the timer you are required to shortly disconnect and reconnect the charger. 3.5.3 Operating modes during charging Of course, the battery can be charged regardless of the engines operating mode. When the GSM engine is in Normal mode (SLEEP, IDLE, TALK, GPRS IDLE or GPRS DATA mode), it remains operational while charging is in progress (provided that sufficient voltage is applied). The charging process during the Normal mode is referred to as Charge mode. If the charger is connected to the charger input of the external charging circuit and the modules POWER pin while MC46 is in POWER DOWN mode, MC46 goes into Charge-only mode. Table 9: Comparison Charge-only and Charge mode Features Battery can be charged while GSM engine remains operational and registered to the GSM network. In IDLE and TALK mode, the serial interfaces are accessible. AT command set can be used to full extent. In the NON-CYCLIC SLEEP mode, the serial interfaces are not accessible at all. During the CYCLIC SLEEP mode it can be used as described in Chapter 3.6.3. Battery can be charged while GSM engine is deregistered from GSM network. Charging runs smoothly due current consumption. to constant The AT interface is accessible and allows to use the commands listed below. How to activate mode Connect charger to charger input of external charging circuit and modules POWER pin while MC46 is operating, e.g. in IDLE or TALK mode in SLEEP mode Connect charger to charger input of external charging circuit and modules POWER pin while MC46 is in POWER DOWN mode in Normal mode: Connect charger to the POWER enter AT^SMSO. then pin, IMPORTANT: While trickle charging is in progress, be sure that the application is switched off. If the application is fed from the trickle charge current the module might be prevented from proceeding to software controlled charging since the current would not be sufficient. e d o m e g r a h C l e d o m y n o
-
e g r a h C MC46_HD_V03.05 Page 40 of 99 13.11.2003 s mo b i l e MC46 Hardware Interface Description Confidential / Released Features of Charge-only mode Once the GSM engine enters the Charge-only mode, the AT command interface presents an Unsolicited Result Code (URC) which reads:
^SYSSTART CHARGE-ONLY MODE Note that this URC will not appear when autobauding was activated (due to the missing synchronization between DTE and DCE upon start-up). Therefore, it is recommended to select a fixed baud rate before using the Charge-only mode. While the Charge-only mode is in progress, you can only use the AT commands listed in Table 10. For further instructions refer to the AT Command Set supplied with your GSM engine. Table 10: AT commands available in Charge-only mode AT command Use AT+CALA AT+CCLK AT^SBC Set alarm time Set date and time of RTC Monitor charging process Note: While charging is in progress, no battery capacity value is available. To query the battery capacity disconnect the charger. If the charger connects externally to the host device no charging parameters are transferred to the module. In this case, the command cannot be used. Query temperature range, enable/disable URCs to report critical temperature ranges Power down GSM engine AT^SCTM AT^SMSO To proceed from Charge-only mode to normal operation, it is necessary to drive the ignition line to ground. This must be implemented in your host application as described in Chapter 3.3.1.1. See also Chapter 3.7 which summarizes the various options of changing the mode of operation. If your host application uses the SYNC pin to control a status LED as described in Chapter 3.12.2.2, please note that the LED is off while the GSM engine is in Charge-only mode. 3.5.4 If you are using the implemented charging technique and the charging circuit recommended in Figure 7, the charger must be designed to meet the following requirements:
a) Simple transformer power plug
- Output voltage: 5.5V...8V (under load)
- The charge current must be limited to 500mA
- Voltage spikes that may occur while you connect or disconnect the charger must be Charger requirements
- There must not be any capacitor on the secondary side of the power plug (avoidance of current spikes at the beginning of charging) b) Supplementary requirements for a) to ensure a regulated power supply
- When current is switched off a voltage peak of 10V is allowed for a maximum 1ms
- When current is switched on a spike of 1.6A for 1ms is allowed limited. MC46_HD_V03.05 Page 41 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e Power saving 3.6 SLEEP mode reduces the functionality of the MC46 module to a minimum and, thus, minimizes the current consumption to the lowest level. SLEEP mode is set with the AT+CFUN command which provides the choice of the functionality levels <fun>=0, 1, 5, 6, 7 or 8, all explained below. Further instructions of how to use AT+CFUN can be found in [1]. IMPORTANT: The AT+CFUN command can be executed before or after entering PIN1. Nevertheless, please keep in mind that power saving works properly only while the module is registered to the GSM network. If you attempt to activate power saving while the module is detached, the selected <fun> level will be set, though power saving does not take effect. For the same reason, power saving cannot be used if MC46 operates in Alarm mode. To check whether power saving is on, you can query the status of AT+CFUN if you have chosen CYCLIC SLEEP mode. If available, you can take advantage of the status LED controlled by the SYNC pin (see Chapter 3.12.2.2). The LED stops flashing once the module starts power saving. The wake-up procedures are quite different depending on the selected SLEEP mode. Table 11 compares the wake-up events that can occur in NON-CYCLIC SLEEP mode and in the four CYCLIC SLEEP modes. 3.6.1 The functionality level <fun>=1 is where power saving is switched off. This is the default after startup. 3.6.2 If level 0 has been selected (AT+CFUN=0), the serial interface is blocked. The module shortly deactivates power saving to listen to a paging message sent from the base station and then immediately resumes power saving. Level 0 is called NON-CYCLIC SLEEP mode, since the serial interface is not alternatingly made accessible as in CYCLIC SLEEP mode. The first wake-up event fully activates the module, enables the serial interface and terminates the power saving mode. In short, it takes MC46 back to the highest level of functionality <fun>=1. NON-CYCLIC SLEEP mode (AT+CFUN=0) No power saving (AT+CFUN=1) MC46_HD_V03.05 Page 42 of 99 13.11.2003 s mo b i l e CYCLIC SLEEP mode (AT+CFUN=5, 6, 7 and 8) MC46 Hardware Interface Description Confidential / Released 3.6.3 The functionality levels AT+CFUN=5, AT+CFUN=6, AT+CFUN=7 and AT+CFUN=8 are referred to as CYCLIC SLEEP modes. The major benefit over the NON-CYCLIC SLEEP mode is that the serial interface is not permanently blocked and that packet switched calls may go on without terminating the selected CYCLIC SLEEP mode. This allows MC46 to become active, for example to perform a GPRS data transfer, and to resume power saving after the GPRS data transfer is completed. The four CYCLIC SLEEP modes give you greater flexibility regarding the wake-up procedures: For example, in all CYCLIC SLEEP modes, you can enter AT+CFUN=1 to permanently wake up the module. The best choice is using CFUN=7 or 8, since in these modes MC46 automatically resumes power saving, after you have sent or received a short message or made a call. CFUN=5 and 6 do not offer this feature, and therefore, are only supported for compatibility with earlier releases. Please refer to Table 11 for a summary of all modes. The CYCLIC SLEEP mode is a dynamic process which alternatingly enables and disables the serial interface. By setting/resetting the /CTS signal, the module indicates to the application whether or not the UART is active. The timing of the /CTS signal is described below. Both the application and the module must be configured to use hardware flow control
(RTS/CTS handshake). The default setting of MC46 is AT\Q0 (no flow control) which must be altered to AT\Q3. See [1] for details. Note: If both serial interfaces ASC0 and ASC1 are connected, both are synchronized. This means that SLEEP mode takes effect on both, no matter on which interface the AT command was issued. Although not explicitly stated, all explanations given in this chapter refer equally to ASC0 and ASC1, and accordingly to /CTS0 and /CTS1. 4.616 ms (TDMA frame duration) * 51 (number of frames) * DRX value. Timing of the /CTS signal in CYCLIC SLEEP modes 3.6.4 The /CTS signal is enabled in synchrony with the modules paging cycle. It goes active low each time when the module starts listening to a paging message block from the base station. The timing of the paging cycle varies with the base station. The duration of a paging interval can be calculated from the following formula:
DRX (Discontinuous Reception) is a value from 2 to 9, resulting in paging intervals from 0.47 to 2.12 seconds. The DRX value of the base station is assigned by the network operator. Each listening period causes the /CTS signal to go active low: If DRX is 2, the /CTS signal is activated every 0.47 seconds, if DRX is 3, the /CTS signal is activated every 0.71 seconds and if DRX is 9, the /CTS signal is activated every 2.1 seconds. The /CTS signal is active low for 4.6 ms. This is followed by another 4.6 ms UART activity. If the start bit of a received character is detected within these 9.2 ms, /CTS will be activated and the proper reception of the character will be guaranteed.
/CTS will also be activated if any character is to be sent from the module to the application. MC46_HD_V03.05 Page 43 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released After the last character was sent or received the interface will remain active for another 2 seconds, if AT+CFUN=5 or 7 or 10 minutes, if AT+CFUN=6 or 8. In the pauses between listening to paging messages, while /CTS is high, the module resumes power saving and the AT interface is not accessible. See Figure 10 and Figure 11. s mo b i l e Paging message 2.12 s Paging message Paging message Paging message 2.12 s 2.12 s
/CTS 4.6 ms 4.6 ms 4.6 ms 4.6 ms 4.6 ms 4.6 ms 4.6 ms 4.6 ms AT interface disabled AT interface enabled Figure 10: Timing of /CTS signal (example for a 2.12 s paging cycle) Figure 11 illustrates the CFUN=5 and CFUN=7 modes, which reset the /CTS signal 2 seconds after the last character was sent or received. Paging message 2.12 s Paging message 2.12 s Paging message Paging message 2.12 s Beginning of power saving 4.6 ms 4.6 ms 2 s 4.6 ms 4.6 ms 4.6 ms 1 character st Last character AT interface disabled AT interface enabled Figure 11: Beginning of power saving if CFUN=5 or 7
/CTS MC46_HD_V03.05 Page 44 of 99 13.11.2003 s mo b i l e MC46 Hardware Interface Description Confidential / Released 3.6.5 Wake up MC46 from SLEEP mode A wake-up event is any event that switches off the SLEEP mode and causes MC46 to return to full functionality. In short, it takes MC46 back to AT+CFUN=1. Definitions of the state transitions described in Table 11:
Yes = MC46 exits SLEEP mode. No = MC46 does not exit SLEEP mode. Table 11: Wake-up events in NON-CYCLIC and CYCLIC SLEEP modes Event Ignition line
/RTS0 or /RTS1
(falling edge) Unsolicited Result Code
(URC) Incoming voice or data call Any AT command
(incl. outgoing voice or data call, outgoing SMS) Incoming SMS depending on mode selected by AT+CNMI:
AT+CNMI=0,0 (= default, no indication of received SMS) AT+CNMI=1,1 (= displays URC upon receipt of SMS) GPRS data transfer RTC alarm2) AT+CFUN=1 From SLEEP mode AT+CFUN=0 to AT+CFUN=1 No Yes1) From SLEEP mode AT+CFUN=5 or 6 to AT+CFUN=1 No No1) From SLEEP mode AT+CFUN=7 or 8 to AT+CFUN=1 No No1) Yes Yes Not possible
(UART disabled) No Yes Not possible
(UART disabled) Yes Not possible (UART disabled) Yes Yes No No Yes No Yes Yes No No No No No No No Yes During all CYCLIC SLEEP modes, /RTS0 and /RTS1 are conventionally used for flow control: The assertion of /RTS0 or /RTS1 signals that the application is ready to receive data - without waking up the module. Be aware that this behavior is different if CFUN=0: In this case, the assertion of /RTS0 and /RTS1 serves as a wake-up event, giving the application the possibility to intentionally terminate power saving. Recommendation: In NON-CYCLIC SLEEP mode, you can set an RTC alarm to wake up MC46 and return to full functionality. This is a useful approach because, in this mode, the AT interface is not accessible. 1) 2) MC46_HD_V03.05 Page 45 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released Summary of state transitions (except SLEEP mode) 3.7 Table 12: State transitions of MC46 (except SLEEP mode) The table shows how to proceed from one mode to another (gray column = present mode, white columns = intended modes) Charging in normal Further mode mode*)**) Present mode POWER DOWN mode without charger
/IGT >100 ms at low level Charge-only mode*) POWER DOWN Normal mode**)
---
POWER DOWN mode with charger
(high level at POWER pins of MC46) Normal mode**)
---
/IGT >1 s at low level, if battery is fully charged AT^SMSO or exceptionally /EMERGOFF pin > 3.2s at low level
---
Charge-only mode *) Disconnect charger (MC46 POWER pin at low level) or AT^SMSO or exceptionally /EMERGOFF pin >3.2s at low level AT^SMSO Charge-only mode, again AT^SMSO;
or exceptionally
/EMERGOFF pin >3.2s at low level AT^SMSO or exceptionally /EMERGOFF pin >3.2s at low level No automatic transition, but via
Charge in Normal mode Disconnect charger from input of ext. charging circuit and modules POWER pin
/IGT >100ms at low level Charging in normal mode*) **) Alarm mode Connect charger to input of ext. charging circuit and POWER pin
(high level at POWER) 100ms < /IGT < 500ms at low level No direct transition, but via Charge-only mode or
Normal mode
/IGT >1 s at low level No automatic transition, but via POWER DOWN Connect charger to POWER pin at MC46
(high level at POWER)
---
/IGT >1s at low level AT^SMSO
---
No transition
/IGT >100ms at low level
---
s mo b i l e Alarm mode Wake-up from POWER DOWN mode (if activated with AT+CALA) Wake-up from POWER DOWN mode (if activated with AT+CALA) AT+CALA followed by AT^SMSO. MC46 enters Alarm mode when specified time is reached. AT+CALA followed by AT^SMSO. MC46 enters Alarm mode when specified time is reached and VBATT+>3.2V No direct transition
*) See Chapter 3.5.3 for details on the charging mode
**) Normal mode covers TALK, DATA, GPRS, IDLE and SLEEP modes MC46_HD_V03.05 Page 46 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e RTC backup 3.8 The internal Real Time Clock of MC46 is supplied from a separate voltage regulator in the power supply ASIC which is also active when MC46 is in POWER DOWN status. An alarm function is provided that allows to wake up MC46 without logging on to the GSM network. In addition, you can use the VDDLP pin on the board-to-board connector to backup the RTC from an external capacitor or a battery (rechargeable or non-chargeable). The capacitor is charged by the BATT+ line of MC46. If the voltage supply at BATT+ is disconnected the RTC can be powered by the capacitor. The size of the capacitor determines the duration of buffering when no voltage is applied to MC46, i.e. the greater capacitor the longer MC46 will save the date and time. The following figures show various sample configurations. The voltage applied at VDDLP can be in the range from 2 to 5.5V. Please refer to Table 27 for the parameters required. Baseband processor RTC PSU 1k BATT+
B2B VDDLP
+
Figure 12: RTC supply from capacitor Baseband processor RTC BATT+
B2B PSU 1k VDDLP
+
Figure 13: RTC supply from rechargeable battery Baseband processor RTC PSU 1k BATT+
B2B VDDLP
+
+
Figure 14: RTC supply from non-chargeable battery MC46_HD_V03.05 Page 47 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e Serial interfaces 3.9 MC46 offers two unbalanced, asynchronous serial interfaces conforming to ITU-T V.24 protocol DCE signaling. The electrical characteristics do not comply with ITU-T V.28. The significant levels are 0V (for low data bit or ON condition) and 2.65V (for high data bit or OFF condition). For electrical characteristics please refer to Table 38. The GSM engine is designed for use as a DCE. Based on the conventions for DCE-DTE connections it communicates with the customer application (DTE) using the following signals:
ASC0 Port /TXD @ application sends data to the modules /TXD0 signal line Port /RXD @ application receives data from the modules /RXD0 signal line ASC1 Port /TXD @ application sends data to modules /TXD1 signal line Port /RXD @ application receives data from the modules /RXD1 signal line GSM module
(DCE) Application
(DTE)
/TXD0
/RXD0
/RTS0
/CTS0
/DTR0
/DSR0
/DCD0
/RING0
/TXD1
/RXD1
/RTS1
/CTS1
/TXD
/RXD
/RTS
/CTS
/DTR
/DSR
/DCD
/RING
/TXD
/RXD
/RTS
/CTS e c a f r e t n i 0 C S A e c a f r e t n i 1 C S A e c a f r e t n i l a i r e s t s 1 e c a f r e t n i l a i r e s d n 2 Figure 15: Serial interfaces MC46_HD_V03.05 Page 48 of 99 13.11.2003 Features supported on first and second serial interface s mo b i l e MC46 Hardware Interface Description Confidential / Released 3.9.1 ASC0 8-wire serial interface Includes the data lines /TXD0 and /RXD0, the status lines /RTS0 and /CTS0 and, in addition, the modem control lines /DTR0, /DSR0, /DCD0 and /RING0. It is primarily designed for voice calls, CSD calls, fax calls and GPRS services and for controlling the GSM engine with AT commands. Full Multiplex capability allows the interface to be partitioned into three virtual channels, yet with CSD and fax services only available on the first logical channel. Please note that when the ASC0 interface runs in Multiplex mode, ASC1 cannot be used. For more detailed characteristics see [10]. The /DTR0 signal will only be polled once per second from the internal firmware of The /RING0 signal serves to indicate incoming calls and other types of URCs
(Unsolicited Result Code). It can also be used to send pulses to the host application, for example to wake up the application from power saving state. For further details see Chapter 3.12.2.3. Autobauding is only selectable on ASC0 and supports the following bit rates: 1200, 2400, MC46. 4800, 9600, 19200, 38400, 57600, 115200, 230400 bps. Autobauding is not compatible with multiplex mode, see [10]. ASC1 4-wire serial interface Includes only the data lines /TXD1 and /RXD1 plus /RTS1 and /CTS1 for hardware handshake. This interface is intended for voice calls, GPRS services and for controlling the GSM engine with AT commands. It is not suited for CSD calls, fax calls and Multiplex mode. On ASC1 no RING line is available. The indication of URCs on the second interface depends on the settings made with the AT^SCFG command. For details refer to [1]. ASC0 and ASC1 Both interfaces are configured for 8 data bits, no parity and 1 stop bit, and can be operated at bit rates from 300bps to 230400 bps. XON/XOFF software flow control can be used on both interfaces (except if power saving is active). Table 13: DCE-DTE wiring of 1st serial interface V.24 circuit Pin function
/TXD0
/RXD0
/RTS0
/CTS0
/DTR0
/DSR0
/DCD0
/RING0 103 104 105 106 108/2 107 109 125 DCE Signal direction Input Output Input Output Input Output Output Output Pin function
/TXD
/RXD
/RTS
/CTS
/DTR
/DSR
/DCD
/RING DTE Signal direction Output Input Output Input Output Input Input Input MC46_HD_V03.05 Page 49 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released Table 14: DCE-DTE wiring of 2nd serial interface V.24 circuit Pin function
/TXD1
/RXD1
/RTS1
/CTS1 DCE Signal direction Input Output Input Output 103 104 105 106 s mo b i l e Pin function
/TXD
/RXD
/RTS
/CTS DTE Signal direction Output Input Output Input MC46_HD_V03.05 Page 50 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e Audio interfaces 3.10 MC46 comprises three audio interfaces available on the board-to-board connector:
Two analog audio interfaces, each with a balanced analog microphone input and a balanced analog earpiece output. The second analog interface provides a supply circuit to feed an active microphone. Serial digital audio interface (DAI) using PCM (Pulse Code Modulation) to encode analog voice signals into digital bit streams. This means you can connect up to three audio devices in any combination, all at the same time. Using the AT^SAIC command you can easily switch back and forth. ADC DAC DSP Air Interface M U X MICP1 MICN1 MICP2 MICN2 EPP1 EPN1 EPP2 EPN2 SCLK RXDDAI RFSDAI TXDDAI TFSDAI Digital Audio Interface
(DAI) Figure 16: Audio block diagram MC46 offers six audio modes which can be selected with the AT^SNFS command, no matter which of the three interfaces is currently active. The electrical characteristics of the voiceband part vary with the audio mode. For example, sending and receiving amplification, sidetone paths, noise suppression etc. depend on the selected mode and can be altered with AT commands (except for mode 1). On each audio interface you can use all audio AT commands specified in [1] to alter parameters. The only exception are the DAC and ADC gain amplifier attenuation
<outBbcGain> and <inBbcGain> which cannot be modified when the digital audio interface is used, since in this case the DAC and ADC are switched off. Please refer to Chapter 5.5 for specifications of the audio interface and an overview of the audio parameters. Detailed instructions on using AT commands are presented in the "MC46 AT Command Set" [1]. Table 30 on page 80 summarizes the characteristics of the various audio modes and shows what parameters are supported in each mode. MC46_HD_V03.05 Page 51 of 99 13.11.2003 s MC46 Hardware Interface Description mo b i l e Confidential / Released When shipped from factory, all audio parameters of MC46 are set to interface 1 and audio mode 1. This is the default configuration optimized for the Votronic HH-SI-30.3/V1.1/0 handset and used for type approving the Siemens reference configuration. Audio mode 1 has fix parameters which cannot be modified. To adjust the settings of the Votronic handset simply change to another audio mode. In transmit direction, all audio modes contain internal scaling factors (digital amplification) that are not accessible by the user. To avoid saturation with a full scale digital input signal on the DAI, and to obtain a one-to-one digital access to the speech coder in audio mode 5 and 6, it is recommended to set the parameter <inCalibrate> of the selected audio mode as follows:
Audio mode 1 and 4:
Audio mode 2:
Audio mode 3:
Audio mode 5 and 6:
3.10.1 Microphone circuit Interface 1 This interface has no microphone supply circuit and therefore, has an impedance of 50kW. When connecting a microphone or another signal source to interface 1 you are required to add two 100 nF capacitors, one to each line. Interface 2 This interface comes with a microphone supply circuit and can be used to feed an active microphone. It has an impedance of 2kW. If you do not use it or if you want to connect another type of signal source, for example, an op amp or a dynamic microphone, it needs to be decoupled with capacitors. The power supply can be switched off and on by using the command AT^SNFM. For details see [1]. Figure 17 shows the microphone inputs at both analog interfaces of MC46. 23196 17396 21901 21402 MICP1 MICN1 MICP2 MICN2 Ri=50k 1 k 1 k 10 F 1 k 1 k Ri=2k 2.65 V Power down to ADC Figure 17: Schematic of microphone inputs MC46_HD_V03.05 Page 52 of 99 13.11.2003 mo b i l e s MC46 Hardware Interface Description Confidential / Released 3.10.2 Speech processing The speech samples from the ADC or DAI are handled by the DSP of the baseband controller to calculate e.g. amplifications, sidetone, echo cancellation or noise suppression depending on the configuration of the active audio mode. These processed samples are passed to the speech encoder. Received samples from the speech decoder are passed to the DAC or DAI after post processing (frequency response correction, adding sidetone etc.). Full rate, half rate, enhanced full rate, adaptive multi rate (AMR), speech and channel encoding including voice activity detection (VAD) and discontinuous transmission (DTX) and digital GMSK modulation are also performed on the GSM baseband processor. Customer specific audio parameters can be evaluated and supplied by Siemens on request. These parameters can be downloaded to MC46 using an AT command. For further information refer to [8] or contact your Siemens distributor. 3.10.3 DAI timing To support the DAI function, MC46 integrates a simple five-line serial interface with one input data clock line (SCLK) and input / output data and frame lines (TXDDAI, TFSDAI, RXDDAI, RFSDAI). The serial interface is always active if the external input data clock SLCK is present, i.e. the serial interface is not clocked by the DSP of the MC46 baseband processor. SLCK must be supplied from the application and can be in a frequency range between 0.2 and 10 MHz. Serial transfer of 16-bit words is done in both directions. Data transfer to the application is initiated by the module through a short pulse of TFSDAI. The duration of the TFSDAI pulse is one SCLK period, starting at the rising edge of SLCK. During the following 16 SLCK cycles, the 16-bit sample will be transferred on the TXDDAI line. The next outgoing sample will be transferred after the next TFSDAI pulse which occurs every 125 s. The TFSDAI pulse is the master clock of the sample transfer. From the rising edge of the TFSDAI pulse, the application has 100 s to transfer the 16-bit input sample on the RXDDAI line. The rising edge of the RFSDAI pulse (supplied by the application) may coincide with the falling edge of TFSDAI or occur slightly later - it is only significant that, in any case, the transfer of the LSB input sample will be completed within the specified duration of 100 s. Audio samples are transferred from the module to the application in an average of 125s. This is determined by the 8kHz sampling rate, which is derived from and synchronized to the GSM network. As SLCK is independent of the GSM network, the distance between two succeeding sample transfers may vary about + 1 SLCK period. The application is required to adapt its sampling rate to the TFSDAI rate. Failure to synchronize the timing between the module and the application may cause audible pops and clicks in a conversation. The timing characteristics of both data transfer directions are shown in Figure 18 and Figure 19. MC46_HD_V03.05 Page 53 of 99 13.11.2003 MC46 Hardware Interface Description mo b i l e Confidential / Released Note: Before starting the data transfer the clock SCLK should be available for at least s three cycles. After the transfer of the LSB0 the clock SCLK should be still available for at least three cycles. SLCK
(input) Internal signal RFSDAI
(input) RXDDAI
(input) Flag SLCK
(input) Internal signal TFSDAI
(output) TXDDAI
(output) Flag T = 100ns to 5,000 ns Figure 18: DAI timing on transmit path T = 100ns to 5,000 ns Figure 19: DAI timing on receive path MC46_HD_V03.05 Page 54 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e SIM interface 3.11 The baseband processor has an integrated SIM interface compatible with the ISO 7816 IC Card standard. This is wired to the host interface (board-to-board connector) in order to be connected to an external SIM card holder. Six pins on the board-to-board connector are reserved for the SIM interface. The CCIN pin serves to detect whether a tray (with SIM card) is present in the card holder. Using the CCIN pin is mandatory for compliance with the GSM 11.11 recommendation if the mechanical design of the host application allows the user to remove the SIM card during operation. See Chapter 3.11.1 for details. It is recommended that the total cable length between the board-to-board connector pins on MC46 and the pins of the SIM card holder does not exceed 200 mm in order to meet the specifications of 3GPP TS 51.010-1 and to satisfy the requirements of EMC compliance. Table 15: Signals of the SIM interface (board-to-board connector) Signal CCGND Separate ground connection for SIM card to improve EMC. CCCLK Chipcard clock, various clock rates can be set in the baseband processor. CCVCC SIM supply voltage from PSU-ASIC CCIO CCRST Chipcard reset, provided by baseband processor. CCIN Serial data line, input and output. Description Input on the baseband processor for detecting a SIM card tray in the holder. The CCIN pin is mandatory for applications that allow the user to remove the SIM card during operation. The CCIN pin is solely intended for use with a SIM card. It must not be used for any other purposes. Failure to comply with this requirement may invalidate the type approval of MC46. MC46_HD_V03.05 Page 55 of 99 13.11.2003 mo b i l e s MC46 Hardware Interface Description Confidential / Released 3.11.1 Requirements for using the CCIN pin According to ISO/IEC 7816-3 the SIM interface must be immediately shut down once the SIM card is removed during operation. Therefore, the signal at the CCIN pin must go low before the SIM card contacts are mechanically detached from the SIM interface contacts. This shut-down procedure is particularly required to protect the SIM card as well as the SIM interface of MC46 from damage. An appropriate SIM card detect switch is required on the card holder. For example, this is true for the model supplied by Molex, which has been tested to operate with MC46 and is part of the Siemens reference equipment submitted for type approval. Molex ordering number is 91228-0001, see also Chapter 8. The modules startup procedure involves a SIM card initialization performed within 1 second after getting started. An important issue is whether the initialization procedure ends up with a high or low level of the CCIN signal:
a) If, during startup of MC46, the CCIN signal on the SIM interface is high, then the status of the SIM card holder can be recognized each time the card is inserted or ejected. A low level of CCIN indicates that no SIM card tray is inserted into the holder. In this case, the module keeps searching, at regular intervals, for the SIM card. Once the SIM card tray with a SIM card is inserted, CCIN is taken high again. If, during startup of MC46, the CCIN signal is low, the module will also attempt to initialize the SIM card. In this case, the initialization will only be successful when the card is present. If the SIM card initialization has been done, but the card is no more operational or removed, then the module will never search again for a SIM card and only emergency calls can be made. b) Removing and inserting the SIM card during operation requires the software to be reinitialized. Therefore, after reinserting the SIM card it is necessary to restart MC46. It is strongly recommended to connect the contacts of the SIM card detect switch to the CCIN input and to the CCVCC output of the module as illustrated in the sample diagram in Figure 20. Note: No guarantee can be given, nor any liability accepted, if loss of data is encountered after removing the SIM card during operation. Also, no guarantee can be given for properly initializing any SIM card that the user inserts after having removed a SIM card during operation. In this case, the application must restart MC46. MC46_HD_V03.05 Page 56 of 99 13.11.2003 s MC46 Hardware Interface Description Confidential / Released 3.11.2 Design considerations for SIM card holder The schematic below is a sample configuration that illustrates the Molex SIM card holder located on the DSB45 Support Box (evaluation kit used for type approval of the Siemens MC46 reference setup, see [5]). X503 is the designation used for the SIM card holder in [5]. mo b i l e Molex card holder Figure 20: SIM card holder of DSB45 Support Box Table 16 : Pin assignment of Molex SIM card holder on DSB45 Support Box GSM module Pin no. Signal name 1 2 3 4 5 6 7 8 CCVCC CCRST CCCLK CCGND CCVPP CCIO CCDET1 CCDET2 I/O I I I
-
-
I/O
-
Function Supply voltage for SIM card, generated by the GSM engine Chip card reset, prompted by the GSM engine Chip card clock Individual ground line for the SIM card to improve EMC Not connected Serial data line, bi-directional Connect to CCVCC Connects to the CCIN input of the GSM engine. Serves to recognize whether a SIM card is in the holder. Pins 1 through 8 (except for 5) are the minimum requirement according to the GSM Recommendations, where pins 7 and 8 are needed for SIM card tray detection through the CCIN pin. Figure 21: Pin numbers of Molex SIM card holder on DSB45 Support Box Place the capacitors C1205 and C1206 (or instead one capacitor of 200nF) as close as possible to the pins 1 (CCVCC) and 4 (GND) of the card holder. Connect the capacitors to the pins via low resistance tracks. 4 5 6 1 2 3 7 8 MC46_HD_V03.05 Page 57 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released 3.12 Control signals 3.12.1 Inputs Table 17: Input control signals of the MC46 module Signal Ignition Pin status Falling edge Left open or HiZ No operation Function Power up MC46 Pin
/IGT Emergency shutdown
/EMERG-
OFF Low Power down MC46 Left open or HiZ No operation
(HiZ = high impedance) s mo b i l e Remarks Active low 100ms (Open drain/collector driver to GND required in cellular device application). Note:
If a charger and a battery is connected to the customer application the /IGT signal must be 1s minimum. Active
(Open drain/collector driver required in cellular device application). At the /EMERGOFF signal the watchdog signal of the GSM engine can be traced (see description in Table 27). low 3.2s MC46_HD_V03.05 Page 58 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released 3.12.2 Outputs s mo b i l e 3.12.2.1 Synchronization signal The synchronization signal serves to indicate growing power consumption during the transmit burst. The signal is generated by the SYNC pin (pin number 32). Please note that this pin can adopt two different operating modes which you can select by using the AT^SSYNC command (mode 0 and 1). For details refer to the following chapter and to [1]. To generate the synchronization signal the pin needs to be configured to mode 0 (= default). This setting is recommended if you want your application to use the synchronization signal for better power supply control. Your platform design must be such that the incoming signal accommodates sufficient power supply to the MC46 module if required. This can be achieved by lowering the current drawn from other components installed in your application. The characteristics of the synchronization signal are explained below. Table 18: MC46 synchronization signal (if SYNC pin is set to mode 0 via AT^SSYNC) Function Synchronization Pin SYNC Pin status Low High Description No operation Indicates increased power consumption during transmission. 1 Tx 577 s every 4.616 ms 2 Tx 1154 s every 4.616 ms Transmit burst SYNC signal*) 300 s Figure 22: SYNC signal during transmit burst
*) The duration of the SYNC signal is always equal, no matter whether the traffic or the access burst are active. MC46_HD_V03.05 Page 59 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e 3.12.2.2 Using the SYNC pin to control a status LED As an alternative to generating the synchronization signal, the SYNC pin can be used to control a status LED on your application platform. To avail of this feature you need to set the SYNC pin to mode 1 by using the AT^SSYNC command. For details see [1]. When controlled from the SYNC pin the LED can display the functions listed in Table 19. Especially in the development and test phase of an application, system integrators are advised to use the LED mode of the SYNC pin in order to evaluate their product design and identify the source of errors. Table 19: Coding of the status LED LED mode Off 600 ms On / 600ms Off 75 ms On / 3 s Off 75 ms on / 75 ms Off / 75 ms On /
3 s Off Flashing On Operating status MC46 is off or run in SLEEP, Alarm or Charge-only mode No SIM card inserted or no PIN entered, or network search in progress, or ongoing user authentication, or network login in progress. Logged to network (monitoring control channels and user interactions). No call in progress. One or more GPRS contexts activated. Indicates GPRS data transfer: When a GPRS transfer is in progress, the LED goes on within 1 second after data packets were exchanged. Flash duration is approximately 0.5 s. Depending on type of call:
Voice call: Connected to remote party. Data call: Connected parameters while setting up or disconnecting a call. to remote party or exchange of included LED Off = SYNC pin low. LED On = SYNC pin high (if LED is connected as illustrated in Figure 23) To operate the LED a buffer, e.g. a transistor or gate, must be in your application. A sample configuration can be gathered from Figure 23. Power consumption in the LED mode is the same as for the synchronization signal mode. For details see Table 27, SYNC pin. Figure 23: LED Circuit (Example) MC46_HD_V03.05 Page 60 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e 3.12.2.3 Behavior of the /RING0 line (ASC0 interface only) The /RING0 line is available on the first serial interface ASC0 (see also Chapter 3.9). The signal serves to indicate incoming calls and other types of URCs (Unsolicited Result Code). Although not mandatory for use in a host application, it is strongly suggested that you connect the /RING0 line to an interrupt line of your application. In this case, the application can be designed to receive an interrupt when a falling edge on /RING0 occurs. This solution is most effective, particularly, for waking up an application from power saving. Note that if the /RING0 line is not wired, the application would be required to permanently poll the data and status lines of the serial interface at the expense of a higher current consumption. Therefore, utilizing the /RING0 line provides an option to significantly reduce the overall current consumption of your application. The behavior of the /RING0 line varies with the type of event:
When a voice call comes in the /RING0 line goes low for 1s and high for another 4s. Every 5 seconds the ring string is generated and sent over the /RXD0 line. If there is a call in progress and call waiting is activated for a connected handset or handsfree device, the /RING0 line switches to ground in order to generate acoustic signals that indicate the waiting call.
/RING0 1s Ring string 4s 4s 1s Ring string 1s Ring string Figure 24: Incoming voice call Likewise, when a Fax or data call is received, /RING0 goes low. However, in contrast to voice calls, the line remains low. Every 5 seconds the ring string is generated and sent over the /RXD0 line.
/RING0 5s 5s Ring string Ring string Ring string Figure 25: Incoming data call All types of Unsolicited Result Codes (URCs) also cause the
/RING0 line to go low, however for 1 second only. For example, MC46 may be configured to output a URC upon the receipt of an SMS. As a result, if this URC type was activated with AT+CNMI=1,1, each incoming SMS causes the /RING0 line to go low. See [1] for detailed information on URCs.
/RING0 1s URC Figure 26: URC transmission MC46_HD_V03.05 Page 61 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released Table 20: MC46 ring signal Function Ring indication Pin
/RING0 Status 0 1 s mo b i l e Description Indicates an incoming call or URC. If in NON-CYCLIC SLEEP mode CFUN=0 or CYCLIC SLEEP mode CFUN=5 or 6, the module is caused to wake up to full functionality. If CFUN=7 or 8, power saving is resumed after URC transmission or end of call. No operation MC46_HD_V03.05 Page 62 of 99 13.11.2003 mo b i l e s Antenna interface MC46 Hardware Interface Description Confidential / Released 4 The RF interface has an impedance of 50. MC46 is capable of sustaining a total mismatch at the antenna connector or pad without any damage, even when transmitting at maximum RF power. The external antenna must be matched properly to achieve best performance regarding radiated power, DC-power consumption and harmonic suppression. Matching networks are not included on the MC46 PCB and should be placed in the host application. Regarding the return loss MC46 provides the following values:
Table 21: Return loss State of module Receive Transmit Idle Recommended return loss of application
> 12dB
> 12dB not applicable Return loss of module
> 8dB not applicable
< 5dB The connection of the antenna or other equipment must be decoupled from DC voltage. Antenna installation 4.1 To suit the physical design of individual applications MC46 offers two alternative approaches to connecting the antenna:
Recommended approach: U.FL-R-SMT antenna connector from Hirose assembled on the component side of the PCB (top view on MC46). See Chapter 4.1.2 for details. Antenna pad and grounding plane placed on the bottom side. See Chapter 4.1.1. Figure 27: U.FL-R-SMT connector Figure 28: Antenna pad and GND pad MC46_HD_V03.05 Page 63 of 99 13.11.2003 s MC46 Hardware Interface Description mo b i l e Confidential / Released The U.FL-R-SMT connector has been chosen as antenna reference point (ARP) for the Siemens reference equipment submitted to type approve MC46. All RF data specified throughout this manual are related to the ARP. For compliance with the test results of the Siemens type approval you are advised to give priority to the connector, rather than using the antenna pad. IMPORTANT: Both solutions can only be applied alternatively. This means, whenever an antenna is plugged to the Hirose connector, the pad must not be used. Vice versa, if the antenna is connected to the pad, then the Hirose connector must be left empty. Antenna connected to Hirose connector:
Antenna connected to pad:
Module PAD U.FL Antenna or measurement equipment Module PAD U.FL 50Ohm 50Ohm 50Ohm Z Z Antenna or measurement equipment 50Ohm Figure 29: Never use antenna connector and antenna pad at the same time No matter which option you choose, ensure that the antenna pad does not come into contact with the holding device or any other components of the host application. It needs to be surrounded by a restricted area filled with air, which must also be reserved 0.8 mm in height. U.FL antenna connector MC46 PCB Antenna pad RF section Restricted area Figure 30: Restricted area around antenna pad MC46_HD_V03.05 Page 64 of 99 13.11.2003 mo b i l e s Antenna pad MC46 Hardware Interface Description Confidential / Released 4.1.1 The antenna can be soldered to the pad, or attached via contact springs. To provide a proper ground for the antenna, MC46 comes with a grounding pad located close to the antenna pad. The positions of both pads can be seen from Figure 28 and Figure 40. The grounding pad should be connected to the ground plane of the application. When you decide to use the antenna pad take into account that the pad has not been intended as antenna reference point (ARP) for the Siemens MC46 type approval. The antenna pad is provided only as an alternative option which can be used, for example, if the recommended Hirose connection does not fit into your antenna design. Also, consider that according to the GSM recommendations TS 45.005 and TS 51.010-01 a 50 connector is mandatory for type approval measurements. This requires GSM devices with an integral antenna to be temporarily equipped with a suitable connector or a low loss RF cable with adapter. To prevent damage to the module and to obtain long-term solder joint properties you are advised to maintain the standards of good engineering practice for soldering. MC46 material properties:
FR4 MC46 PCB:
Antenna pad:
Gold plated pad Suitable cable types 4.1.1.1 For direct solder attachment, we suggest to use the following cable types:
RG316/U 50 coaxial cable 1671A 50 coaxial cable Suitable cables are offered, for example, by IMS Connector Systems. For further details and other cable types please contact http://www.imscs.com. MC46_HD_V03.05 Page 65 of 99 13.11.2003 s mo b i l e U.FL-R-SMT Hirose antenna connector MC46 Hardware Interface Description Confidential / Released 4.1.2 MC46 uses an ultra-miniature SMT antenna connector supplied from Hirose Ltd. The product name is:
The position of the antenna connector on the MC46 board can be seen in Figure 39. Figure 31: Mechanical dimensions of U.FL-R-SMT connector Table 22: Product specifications of U.FL-R-SMT connector Item Ratings Nominal impedance Rated frequency Mechanical characteristics Female contact holding force Repetitive operation Specification 50 W DC to 3 GHz 0.15 N min Contact resistance:
Center 25 mW Outside 15mW No momentary disconnections of 1 s;
No damage, cracks and looseness of parts No momentary disconnections of 1 s. No damage, cracks and looseness of parts. No damage, cracks and looseness of parts. Insulation resistance:
100 MW min. at high humidity 500 MW min when dry No damage, cracks and looseness of parts. Contact resistance:
Center 25 mW Outside 15mW No excessive corrosion Vibration Shock Environmental characteristics Humidity resistance Temperature cycle Salt spray test Conditions Operating temp:-40c to + 90C Operating humidity: max. 90%
Measured with a 0.475 pin gauge 30 cycles of insertion and disengagement Frequency of 10 to 100 Hz, single amplitude of 1.5 mm, acceleration of 59 m/s2, for 5 cycles in the direction of each of the 3 axes Acceleration of 735 m/s2, 11 ms duration for 6 cycles in the direction of each of the 3 axes Exposure to 40C, humidity of 95% for a total of 96 hours Temperature: +40C 5 to 35C
+90C 5 to 35C Time: 30 min. within 5 min. 30 min. within 5 min 48 hours continuous exposure to 5% salt water MC46_HD_V03.05 Page 66 of 99 13.11.2003 s mo b i l e MC46 Hardware Interface Description Confidential / Released Table 23: Material and finish of U.FL-R-SMT connector and recommended plugs Part Shell Male center contact Female center contact Insulator Material Phosphor bronze Brass Phosphor bronze Plug:
Receptacle:
Finish Silver plating Gold plating Gold plating Black Beige PBT LCP Mating plugs and cables can be chosen from the Hirose U.FL Series. Examples are shown below and listed in Table 24. For latest product information please contact your Hirose dealer or visit the Hirose home page, for example http://www.hirose.com. Figure 32: U.FL-R-SMT connector with U.FL-LP-040 plug Figure 33: U.FL-R-SMT connector with U.FL-LP-066 plug MC46_HD_V03.05 Page 67 of 99 13.11.2003 MC46 Hardware Interface Description mo b i l e Confidential / Released In addition to the connectors illustrated above, the U.FL-LP-(V)-040(01) version is offered as an extremely space saving solution. This plug is intended for use with extra fine cable (up to 0.81 mm) and minimizes the mating height to 2 mm. See Figure 34 which shows the Hirose datasheet. s Figure 34: Specifications of U.FL-LP-(V)-040(01) plug MC46_HD_V03.05 Page 68 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released Table 24: Ordering information for Hirose U.FL Series Item Connector on MC46 Right-angle plug shell for 0.81 mm cable Right-angle plug for 0.81 mm cable Right-angle plug for 1.13 mm cable Right-angle plug for 1.32 mm cable Extraction jig Part number U.FL-R-SMT U.FL-LP-040 U.FL-LP(V)-040 (01) U.FL-LP-066 U.FL-LP-066 E.FL-LP-N s mo b i l e HRS number CL331-0471-0-10 CL331-0451-2 CL331-053-8-01 CL331-0452-5 CL331-0452-5 CL331-04441-9 MC46_HD_V03.05 Page 69 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released 5 Electrical, reliability and radio characteristics s mo b i l e Absolute maximum ratings 5.1 The absolute maximum ratings stated in Table 25 are stress ratings under non-operating conditions. Stresses beyond any of these limits will cause permanent damage to MC46. Table 25: Absolute maximum ratings Parameter Max Unit Min Supply voltage BATT+
Voltage at digital pins Voltage at analog pins Voltage at digital / analog pins in POWER DOWN mode Voltage at POWER pin Voltage at CHARGE pin Differential load resistance between EPNx and EPPx
-0.3
-0.3
-0.3
-0.25 15 5.0 3.3 3.0
+0.25 15 15 V V V V V V W Min
-20
-25 to -20
-29
-18 0 Operating temperatures 5.2 Test conditions were specified in accordance with IEC 60068-2 (still air). The values stated below are in compliance with GSM recommendation TS 51.010-01. Table 26: Operating temperatures Parameter Ambient temperature (according to GSM 11.10) Restricted operation *) Automatic shutdown Typ Max 25 MC46 board temperature Battery temperature Unit
C
C
C
C
C 55 55 to 70
>70**)
>60
+45 Charging temperature (software controlled fast charging)
*)
**) MC46 works, but deviations from the GSM specification may occur. Consider the ratio of output power, supply voltage and operating temperature: To achieve Tamb max = 70C and, for example, GSM 850 PCL5 the supply voltage must not be higher than 4.0V. MC46_HD_V03.05 Page 70 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e Electrical specifications of the application interface 5.3 Please note that the reference voltages listed in Table 27 are the values measured directly on the MC46 module. They do not apply to the accessories connected. If an input pin is specified for Vi,h,max = 3.3V, be sure never to exceed the stated voltage. The value 3.3V is an absolute maximum rating. The Hirose DF12C board-to-board connector on MC46 is a 50-pin double-row receptacle. The names and the positions of the pins can be seen from Figure 35 which shows the top view of MC46. BATT+
BATT+
BATT+
BATT+
BATT+
VDD
/RING0
/DSR0
/RTS0
/DTR0
/RTS1
/CTS0
/CTS1
/DCD0
/EMERGOFF
/IGT GND MICN1 MICP1 MICP2 MICN2 EPN1 EPP1 EPP2 EPN2 26 50 GND GND GND GND GND CHARGE POWER VDDLP
/TXD0
/TXD1
/RXD0
/RXD1 SYNC BATT_TEMP RFSDAI TXDDAI SCLK TFSDAI RXDDAI CCGND CCIN CCRST CCIO CCVCC CCCLK 25 1 Figure 35: Pin assignment (top view on MC46) MC46_HD_V03.05 Page 71 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released Table 27: Electrical description of application interface Function Power supply Signal name BATT+
I IO Signal form and level GND Charge interface POWER BATT_TEMP I I VI = 3.2V to 4.5V VInorm = 4.1V Inorm 2A, Imax < 3A (during Tx burst) 1 Tx: peak current 577s every 4.616ms 2 Tx: peak current 1154s every 4.616ms VImin = 3.0V VImax = 15V Connect NTC with RNTC 10kW @ 25C to ground. CHARGE O ICHARGE = -300A ... -600A
@ 3V < VCHARGE < VLOAD External supply voltage VDD O VDDmin = 2.84V, VDDmax = 2.96V Imax = -10mA CLmax = 1F s mo b i l e Comments Power supply input. 5 BATT+ pins to be connected in parallel. 5 GND pins to be connected in parallel. The power supply must be able to meet the requirements of current consumption in a Tx burst
(up to 3A). Sending with two timeslots doubles the duration of current pulses to 1154s
(every 4.616ms)!
This line signalizes to the processor that the charger is connected. If unused keep pin open. Input to measure the battery temperature over NTC resistor. NTC should be installed inside or near battery pack to enable the charging algorithm and deliver temperature values. If unused keep pin open. This line is a current source for the charge FET with a 10kW resistance between gate and source. If unused keep pin open. Supply voltage, e.g. for an external LED or level shifter. The external digital logic must not cause any spikes or glitches on voltage VDD. Not available in POWER DOWN mode. VDD signalizes the ON state of the module. If unused VDD keep pin open. MC46_HD_V03.05 Page 72 of 99 13.11.2003 Function VDD Low Power MC46 Hardware Interface Description Confidential / Released s mo b i l e Signal name IO Signal form and level Comments VDDLP I/O RI =1kW VOmax 4.0V (output) VImin = 2.2V, VImax = 5.5V (input) IItyp = 10A at BATT+ = 0V Mobile in POWER DOWN mode:
VImin = 1.2V Ignition
/IGT I Emergency shutdown
(Watchdog)
/EMERGOFF I RI 100kW, CI 1nF VILmax = 0.5V at Imax = -20A VOpenmax = 2.3V ON
~~~|____|~~~ Active Low 100ms RI 22kW VILmax = 0.5V at Imax = -100A VOpenmax = 2.73V Signal ~~~|______|~~~ Active Low 3.2s Watchdog:
VOLmax = 0.35V at I = 10A VOHmin= 2.25V at I = -10A fOmin = 0.16Hz fOmax = 1.55Hz Synchroni-
zation SYNC O VOLmax = 0.2V at I = 1mA VOHmin = 2.35V at I = -1mA VOHmax = 2.73V 1 Tx: 877s impulse each 4.616ms and 2 Tx: 1454s impulse each 4.616ms, with 300s forward time. Supplies the RTC with power via an external capacitor or buffer battery if no VBATT+ is applied. If unused keep pin open. Input to switch the mobile ON. The line must be driven low by an Open Drain or Open Collector driver. This line must be driven by an Open Drain or Open Collector driver. Emergency shutdown deactivates the power supply to the module. The module can be reset if
/IGT is activated after emergency shutdown. To switch the mobile off use the AT^SMSO command.
/EMERGOFF also indicates the internal watchdog function. To avoid floating if pin is high impedance, use pull-
down resistor tied to GND. See Chapter 3.3.2.1. If unused keep pin open. Indicates increased current consumption during uplink transmission burst. Note that timing is different during handover. Alternatively used to control status LED (see Chapter 3.12.2.2). If unused keep pin open. MC46_HD_V03.05 Page 73 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e Signal name IO Signal form and level Comments CCIN I RI 100kW VILmax = 0.5V VIHmin = 2.15V at I = 20A, VIHmax = 3.3V at I = 30A CCIN = high, SIM card holder closed (no card recognition) Maximum cable length 200mm to SIM card holder. All signals of SIM interface are protected against ESD with a special diode array. Usage of CCGND is mandatory. O RO 47W VOLmax = 0.25V at I = 1mA VOHmin = 2.3V at I = -1mA VOHmax = 2.73V IO RI 10kW VILmax = 0.5V VIHmin = 1.95V, VIHmax = 3.3V RO 220W VOLmax = 0.4V at I = 1mA VOHmin = 2.15V at I = -1mA VOHmin = 2.55V at I = -20A VOHmax = 2.96V O RO 220W VOLmax = 0.4V at I = 1mA VOHmin = 2.15V at I = -1mA VOHmax = 2.73V O ROmax = 5W CCVCCmin = 2.84V, CCVCCmax = 2.96V Imax = -20mA Ground O I O I I O O O O I O I VOLmax = 0.2V at I = 1mA VOHmin = 2.35V at I = -1mA VOHmax = 2.73V VILmax = 0.5V VIHmin = 1.95V, VIHmax = 3.3V
/DTR0, RTS0: Imax = -90A at VIN = 0V
/TXD0: Imax = -30A at VIN = 0V First serial interface for AT commands or data stream. To avoid floating if output pins are high-impedance, use pull-up resistors tied to VDD or pull-down resistors tied to GND. See Chapter 3.3.2.1. If unused keep pins open. VOLmax = 0.2V at I = 1mA VOHmin = 2.35V at I = -1mA VOHmax = 2.73V VILmax = 0.5V VIHmin = 1.95V, VIHmax = 3.3V IImax = -90A at VIN = 0V Second serial interface for AT commands. To avoid floating if output pins are high-impedance, use pull-up resistors tied to VDD or pull-down resistors tied to GND. See Chapter 3.3.2.1. If unused keep pins open. Function SIM interface ASC0 interface ASC1 interface CCRST CCIO CCCLK CCVCC CCGND
/RXD0
/TXD0
/CTS0
/RTS0
/DTR0
/DCD0
/DSR0
/RING0
/RXD1
/TXD1
/CTS1
/RTS1 MC46_HD_V03.05 Page 74 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e Signal name IO Signal form and level Comments Function Digital audio interface Analog audio interfaces
:
s e m a n l i a n g s f o n o i t a n a p x E l e v i t a g e n
=
N
, e v i t i s o p
=
P RFSDAI RXDDAI SCLK TFSDAI TXDDAI EPP2 EPN2 EPP1 EPN1 MICP1 MICN1 MICP2 MICN2 I I I O O O O O O I I I I VOLmax = 0.2V at I = 1mA VOHmin = 2.35V at I = -1mA VOHmax = 2.73V VILmax = 0.5V VIHmin = 1.95V, VIHmax = 3.3V IImax = 330A at VIN = 3.3V VOmax = 3.7Vpp See also Table 31. VOmax = 3.7Vpp See also Table 31. RI 50kW differential VImax = 1.03Vpp See also Table 32. RI = 2kW differential VImax = 1.03Vpp See also Table 32. AGND If unused keep pins open. The audio output is balanced and can directly operate an earpiece. If unused keep pins open. Balanced audio output. Can be used to directly operate an earpiece. If unused keep pins open. Balanced microphone input. To be decoupled with 2 capacitors (CK =
100nF), if connected to a microphone or another device. If unused keep pins open. Balanced microphone input. Can be used to directly feed an active microphone. If used for another signal source, e.g. op amp, to be decoupled with capacitors. If unused keep pins open. Separate ground connection for external audio circuits. MC46_HD_V03.05 Page 75 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released 5.4 Power supply ratings Table 28: Power supply ratings Parameter Description Conditions BATT+
Supply voltage Voltage drop during transmit burst Voltage ripple Reference points on MC46:
TP BATT+ and TP GND (see Figure 40). Voltage must stay within the min/max values, including voltage drop, ripple, spikes. Normal condition, power control level for Pout max Normal condition, power control level for Pout max
@ f<200kHz
@ f>200kHz IBATT+
Average supply current3) Peak supply current
(during transmission slot every 4.6ms) GSM 850 GSM 1800/1900 GSM 8501) GSM 1800/19002) GSM 850 GSM 1800/1900 POWER DOWN mode SLEEP mode @ DRX = 6 IDLE mode TALK mode IDLE GPRS DATA mode GPRS,
(4 Rx, 1 Tx) DATA mode GPRS,
(3 Rx, 2 Tx) Power control level PCL 5 GSM 8501) GSM 1800/19002) GSM 8501) GSM 1800/19002) s mo b i l e Min 3.2 Typ 4.1 Max Unit 4.5 V 50 3 15 15 3004) 2704) 15 15 3604) 3304) 5904) 5404) 2 400 mV 50 2 100 mV
A mA mA 400 mA mA 460 840 mA mA 3 A 1) 2) 3) 4) Power control level PCL 5 Power control level PCL 0 All average supply current values @ IVDD = 0mA Stated value applies to an average antenna performance. MC46_HD_V03.05 Page 76 of 99 13.11.2003 mo b i l e s Current consumption during transmit burst MC46 Hardware Interface Description Confidential / Released 5.4.1 A Smith chart shows the complex impedance plane. The Smith chart in Figure 36 illustrates the dependence between the typical peak current consumption of the application during a transmit burst and an impedance connected to the antenna reference point (ARP). As shown in Figure 36, the typical current consumption is about 2000 mA, but the current is maximized when the minimum supply voltage is used together with a total reflection at the RF interface. The Smith chart in Figure 36 shows the current consumption at the following conditions:
Channel with the highest current consumption: 836.4 MHz (Channel 189) Tamb = 25C Maximum peak current = 3.0A Minimum supply voltage during burst = 3.35V This measurement case was performed with a total resistance of about 100m in the current path. e c n a t s s e r i e v i t c a e r e v i t i s o P 0 e c n a Effective resistance i t s s e r e v i t c a e r e v i t a g e N Figure 36: Peak current during transmit burst in mA vs. antenna impedance MC46_HD_V03.05 Page 77 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e 5.5 Electrical characteristics of the voiceband part Setting audio parameters by AT commands 5.5.1 The audio modes 2 to 6 can be adjusted according to the parameters listed below. Each audio mode is assigned a separate set of parameters. Table 29: Audio parameters adjustable by AT command Parameter inBbcGain Gain range Calculation 0...42dB Range 0...7 6dB steps inCalibrate outBbcGain outCalibrate[n]
n = 0...4 sideTone Influence to MICP/MICN analog amplifier gain of baseband controller before ADC digital attenuation of input signal after ADC EPP/EPN analog output gain of baseband controller after DAC digital attenuation of output signal after speech decoder, before summation of sidetone and DAC present for each volume step[n]
digital attenuation of sidetone is corrected internally by outBbcGain to obtain a constant sidetone independent of output volume 0...32767 -...0dB 0...3 0...-18dB 0...32767 -...+6dB 0...32767 -...0dB 20 * log
(inCalibrate/
32768) 6dB steps 20 * log (2 *
outCalibrate[n]/
32768) 20 * log
(sideTone/
32768) Note: The parameters inCalibrate, outCalibrate and sideTone accept also values from 32768 to 65535. These values are internally truncated to 32767. MC46_HD_V03.05 Page 78 of 99 13.11.2003 mo b i l e s Audio programming model MC46 Hardware Interface Description Confidential / Released 5.5.2 The audio programming model shows how the signal path can be influenced by varying the AT command parameters. The model is the same for all three interfaces, except for the parameters <outBbcGain> and <inBbcGain> which cannot be modified if the digital audio interface is being used, since in this case the DAC is switched off. The parameters inBbcGain and inCalibrate can be set with AT^SNFI. All the other parameters are adjusted with AT^SNFO. MIC2 2.65V 1k 1k 10uF 1k 1k inBbcGain
+0...42dB in 6dB steps outBbcGain 0dB; -6db, -12dB; -18dB inCalibrate
-...0dB sideTone Speech coder
+
Speech decoder outCalibrate[n]
n = 0...4 AT parameters A D D A Figure 37: AT audio programming model MC46_HD_V03.05 Page 79 of 99 13.11.2003 s Characteristics of audio modes MC46 Hardware Interface Description Confidential / Released 5.5.3 The electrical characteristics of the voiceband part depend on the current audio mode set with the AT^SNFS command. Table 30: Voiceband characteristics (typical) Audio mode no. AT^SNFS=
mo b i l e 3 4 5 6 2 Name Purpose 1 (Default settings, not adjustable) Default Handset DSB with Votronic handset Basic Handsfree Siemens Car Kit Portable Headset Siemens Headset inBbcGain outBbcGain Fix 4 (24dB) 1 (-6dB) 1 Adjustable 2 (12dB) 1 (-6dB) 2 Gain setting via AT command. Defaults:
Default audio interface Power supply Sidetone Volume control Limiter (receive) Compressor
(receive) AGC (send) Echo control (send) Suppression Cancellation +
suppression up to 10dB 58mV ON (2.65V) ON (2.65V) ON OFF ON
---
---
Adjustable ON OFF1)
---
23mV
---
---
Noise suppression2) MIC input signal for 0dBm0 @ 1024 Hz
(default gain) EP output signal in mV rms. @ 0dBm0, 1024 Hz, no load
(default gain);
@ 3.14 dBm0 Sidetone gain at default settings 284mV 120mV default @
max volume 22.8dB
- dB User Handset DSB with individual handset Adjustable 4 (24dB) 1 (-6dB) 1 Plain Codec 1 Direct access to speech coder Adjustable 0 (0dB) 0 (0dB) 1 Plain Codec 2 Direct access to speech coder Adjustable 0 (0dB) 0 (0dB) 2 4) Adjustable 5 (30dB) 2 (-12dB) 2 ON (2.65V) ON (2.65V) OFF (GND) OFF (GND) Adjustable Adjustable Adjustable Adjustable Adjustable Adjustable Adjustable Adjustable ON ON
---
---
---
---
---
---
---
Suppres-
sion
---
23mV 284mV default @
max volume 22.8dB ON
---
10dB 7.5mV @
-3dBm0 due to AGC 300mV default @
max volume Affected by AGC, 13dB
@ 7.5mV
(MIC)
---
---
---
---
---
315mV
---
315mV 895mV 3.7Vpp
-2.5dB
@
sideTone
= 81923) 895mV 3.7Vpp
-2.5dB
@
sideTone
= 81923) 1) 2) Adaptive, receive volume increases with higher ambient noise level. The compressor can be activated by loading an application specific audio parameter set (see [8]). In audio modes with noise reduction, the microphone input signal for 0dBm0 shall be measured with a sine burst signal for a tone duration of 5 seconds and a pause of 2 sec. The MC46_HD_V03.05 Page 80 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released mo b i l e sine signal appears as noise and, after approx. 12 sec, is attenuated by the noise reduction by up to 10dB. See AT^SNFO command in [1]. Audio mode 5 and 6 are identical. With AT^SAIC, you can easily switch mode 5 to the second interface. Therefore, audio mode 6 is only kept for compatibility to earlier Siemens GSM products. s 3) 4) Note: With regard to acoustic shock, the cellular application must be designed to avoid sending false AT commands that might increase amplification, e.g. for a high sensitive earpiece. A protection circuit should be implemented in the cellular application. MC46_HD_V03.05 Page 81 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released 5.5.4 Test conditions:
The values specified below were tested to 1kHz and 0dB gain stage, unless otherwise Voiceband receive path s mo b i l e Parameter setup: gs = 0dB means audio mode = 5 for EPP1 to EPN1 and 6 for EPP2 to EPN2, inBbcGain= 0, inCalibrate = 32767, outBbcGain = 0, OutCalibrate = 16384, sideTone = 0. stated. Table 31: Voiceband receive path Parameter Min Differential output voltage (peak to peak) Differential output gain settings (gs) at 6dB stages (outBbcGain) Fine scaling by DSP
(outCalibrate) Output differential DC offset Differential output resistance Differential load capacitance Absolute gain accuracy Attenuation distortion Out-of-band discrimination gs = gain setting
-18
-
60 Typ Max Unit 3.33 3.7 4.07 V Test condition / remark from EPPx to EPNx gs = 0dB @ 3.14 dBm0 no load Set with AT^SNFO dB Set with AT^SNFO 100 mV gs = 0dB, outBbcGain = 0 and -6dB 2 0 0 1000 0.8 1 dB pF dB dB dB from EPPx to EPNx from EPPx to EPNx Variation due to change in temperature and life time for 300...3900Hz,
@ EPPx/EPNx (333Hz) /
@ EPPx/EPNx (3.66kHz) for f > 4kHz with in-band test signal@ 1kHz and 1kHz RBW MC46_HD_V03.05 Page 82 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released 5.5.5 Test conditions:
The values specified below were tested to 1kHz and 0dB gain stage, unless otherwise Voiceband transmit path s mo b i l e Parameter setup: Audio mode = 5 for MICP1 to MICN1 and 6 for MICP2 to MICN2, inBbcGain= 0, inCalibrate = 32767, outBbcGain = 0, OutCalibrate = 16384, sideTone = 0 stated. Table 32: Voiceband transmit path Parameter Input voltage (peak to peak) MICP1 to MICN1, MICP2 to MICN2 Input amplifier gain in 6dB steps
(inBbcGain) Fine scaling by DSP (inCalibrate) Input impedance MIC1 Input impedance MIC2 Microphone supply voltage ON Ri = 4k (MIC2 only) Microphone supply voltage OFF Ri = 4k (MIC2 only) Microphone supply in POWER DOWN mode Min Typ Max 1.03 0
-
2.57 2.17 1.77 50 2.0 2.65 2.25 1.85 0 42 0 2.73 2.33 1.93 Unit V dB dB k k V V V V Test condition/Remark Set with AT^SNFI Set with AT^SNFI no supply current
@ 100A
@ 200A See Figure 17 MC46_HD_V03.05 Page 83 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e Air interface 5.6 Test conditions: All measurements have been performed at Tamb= 25C, VBATT+ nom = 4.1V. The reference points used on MC46 are the BATT+ and GND contacts (test points are shown in Figure 40). Table 33: Air Interface Parameter Max Unit Typ Min Frequency range Uplink (MS BTS) Frequency range Downlink (BTS MS) RF power @ ARP with 50 load Number of carriers Duplex spacing Carrier spacing Multiplex, Duplex Time slots per TDMA frame Frame duration Time slot duration Modulation Receiver input sensitivity @ ARP BER Class II < 2.4%
1) Power control level PCL 5 2) Power control level PCL 0 GSM 850 GSM 1800 GSM 1900 GSM 850 GSM 1800 GSM 1900 GSM 8501) GSM 18002) GSM 1900 GSM 850 GSM 1800 GSM 1900 GSM 850 GSM 1800 GSM 1900 GSM 850 GSM 1800 GSM 1900 33 30 30 123 374 299 45 95 80 200 848.8 MHz 824.2 MHz 1785 1710 1910 MHz 1850 893.8 MHz 869.2 MHz 1880 1805 1990 MHz 1930 dBm 35 31 dBm 32 28 32 dBm 28 MHz MHz MHz kHz TDMA / FDMA, FDD GMSK
-102
-102
-102 8 4.616 577 dBm dBm dBm
-106
-105
-105 ms
s MC46_HD_V03.05 Page 84 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released Table 34: Local oscillator and intermediate frequencies used by MC46 s mo b i l e All frequencies in MHz Frequency Band Channel Local Oscillator Intermediate Frequency GSM 850 PCN 1800 PCS 1900 TX RX TX TX TX RX TX RX 824.2 848.8 869.2 893.8 1710.2 1733.0 1733.2 1759.8 1760.0 1784.8 1805.2 1879.8 1850.2 1909.8 1930.2 1989.8 128 - 251 128 - 251 512 626 627 760 761 885 512 885 512 810 512 810 3612.8 3723.2 3476.0 3575.2 3580.4 3626.0 3628.4 3681.6 3680.0 3729.6 3610.4 3759.6 3860.4 3979.6 3860.4 3979.6 79 0 80 81 80 0 80 0 MC46_HD_V03.05 Page 85 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e Electrostatic discharge 5.7 The GSM engine is not protected against Electrostatic Discharge (ESD) in general. Consequently, it is subject to ESD handling precautions that typically apply to ESD sensitive components. Proper ESD handling and packaging procedures must be applied throughout the processing, handling and operation of any application that incorporates a MC46 module. Special ESD protection provided on MC46:
Antenna interface: one spark discharge line (spark gap) SIM interface: clamp diodes for protection against overvoltage. The remaining ports of MC46 are not accessible to the user of the final product (since they are installed within the device) and therefore, are only protected according to the Human Body Model requirements. MC46 has been tested according to the EN 61000-4-2 standard. The measured values can be gathered from the following table. Table 35: Measured electrostatic values Specification / Requirements ETSI EN 301 489-7 ESD at SIM port ESD at antenna port Human Body Model (Test conditions: 1.5 kW, 100 pF) ESD at the module Contact discharge Air discharge 8kV 8kV 4kV 4kV 1kV Note: Please note that the values may vary with the individual application design. For example, it matters whether or not the application platform is grounded over external devices like a computer or other equipment, such as the Siemens reference application described in Chapter 7. MC46_HD_V03.05 Page 86 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e Reliability characteristics 5.8 The test conditions stated below are an extract of the complete test specifications. Table 36: Summary of reliability test conditions Type of test Vibration Standard DIN IEC 68-2-6 Shock half-sinus Dry heat Temperature change (shock) Conditions Frequency range: 10-20 Hz; acceleration: 3.1mm amplitude Frequency range: 20-500 Hz; acceleration: 5g Duration: 2h per axis = 10 cycles; 3 axes Acceleration: 500g Shock duration: 1msec 1 shock per axis 6 positions ( x, y and z) Temperature: +70 2C Test duration: 16 h Humidity in the test chamber: < 50%
Low temperature: -40C 2C High temperature: +85C 2C Changeover time: < 30s (dual chamber system) Test duration: 1 h Number of repetitions: 100 Damp heat cyclic High temperature: +55C 2C Low temperature: +25C 2C Humidity: 93% 3%
Number of repetitions: 6 Test duration: 12h + 12h Temperature: -40 2C Test duration: 16 h Cold (constant exposure) DIN IEC 68-2-27 EN 60068-2-2 Bb ETS 300019-2-7 DIN IEC 68-2-14 Na ETS 300019-2-7 DIN IEC 68-2-30 Db ETS 300019-2-5 DIN IEC 68-2-1 MC46_HD_V03.05 Page 87 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released 6 The recommendations for integrating MC46 into the host application. following chapters describe Mechanics s mo b i l e the mechanical dimensions of MC46 and give Mechanical dimensions of MC46 6.1 Figure 38 shows the top view on MC46 and provides an overview of the mechanical dimensions of the board. For further details see Figure 39. Size:
Weight:
53 +0.15 x 34 +0.15 x 3.5+0.3 mm 10g Figure 38: MC46 top view MC46_HD_V03.05 Page 88 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e Board-to-board connector All dimensions in millimeter Figure 39: Mechanical dimensions of MC46 MC46_HD_V03.05 Page 89 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released Ground pad, e.g. for heatsink or connection to host device s mo b i l e GND
1.1 TP 402 14.42 4.75 0.00 GND Antenna pad GND 10.60 TP GND GND 0 9
. 6 2 0 4
. 4 2 0 5
. 5 1 GND 0 0
. 0 TP BATT+
Figure 40: MC46 bottom view MC46_HD_V03.05 Page 90 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e Mounting MC46 onto the application platform 6.2 There are many ways to properly install MC46 in the host device. An efficient approach is to mount the MC46 PCB to a frame, plate, rack or chassis. Fasteners can be M1.6 or M1.8 screws plus suitable washers, circuit board spacers, or customized screws, clamps, or brackets. Screws must be inserted with the screw head on the bottom of the MC46 PCB. This is necessary to avoid contacting the shielding covers on top. In addition, the board-to-board connection can also be utilized to achieve better support. A number of ground planes are provided on the bottom of the MC46 module, all of them illustrated in Figure 40. For proper grounding it is strongly recommended to use these ground planes in addition to the five GND pins of the board-to-board connector. To avoid short circuits ensure that the remaining sections of the MC46 PCB do not come into contact with the host device since there are a number of test points. The largest ground pad in the middle of the board can also be used to attach cooling elements, e.g. a heat sink or thermally conductive tape. Refer to Chapter 6.4 for an overview on a variety of cooling elements. Particular attention should be paid to the test point TP 402. Placed beneath the large ground pad it has been added for manufacturing only. When the pad is used for grounding the unit or connecting a heat sink, extra care must be taken not to contact this test point. Figure 40 shows the positions of all test points. To prevent mechanical damage, be careful not to force, bend or twist the module. Be sure it is positioned flat against the host device. All the information you need to install an antenna is summarized in Chapter 4. Note that the antenna pad on the bottom of the MC46 PCB must not be influenced by any other PCBs, components or by the housing of the host device. It needs to be surrounded by a restricted space as described in Chapter 4.1. MC46_HD_V03.05 Page 91 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e Board-to-board connector 6.3 This chapter provides specifications for the 50-pin board-to-board connector which serves as physical interface to the host application. The receptacle assembled on the MC46 PCB is type Hirose DF12C. Mating headers from Hirose are available in different stacking heights. Figure 41: Hirose DF12C receptacle on MC46 Figure 42: Header Hirose DF12 series Table 37: Ordering information DF12 series Item Part number Receptacle on MC46 Headers DF12 series DF12C(3.0)-50DS-0.5V(81) DF12E(3.0)-50DP-0.5V(81) DF12E(3.5)-50DP-0.5V(81) DF12E(4.0)-50DP-0.5V(81) DF12E(5.0)-50DP-0.5V(81) Stacking height (mm) HRS number 3 - 5 3.0 3.5 4.0 5.0 537-0694-9-81 537-0834-6-**
537-0534-2-**
537-0559-3-**
537-0584-0-**
Notes: The headers listed above are without boss and metal fitting. Please contact Hirose for details on other types of mating headers. Asterixed HRS numbers denote different types of packaging. Table 38: Electrical and mechanical characteristics of the Hirose DF12C connector Parameter Number of contacts Quantity delivered Voltage Rated current Resistance Dielectric withstanding voltage Operating temperature Contact material Insulator material Stacking height Insertion force Withdrawal force 1st Withdrawal force 50th Maximum connection cycles Specification (50 pin board-to-board connector) 50 2000 connectors per tape & reel 50V 0.3A max per contact 0.05 per contact 500V RMS min
-45C...+125C phosphor bronze (surface: gold plated) PA , beige natural 3.0 mm ; 3.5 mm ; 4.0 mm ; 5.0 mm 21.8N 10N 10N 50 MC46_HD_V03.05 Page 92 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released 6.3.1 Mechanical dimensions of the Hirose DF12 connector s mo b i l e Figure 43: Mechanical dimensions of Hirose DF12 connector Adapter cabling 6.3.2 The board-to-board connection is primarily intended for direct contact between both connectors. If this assembly solution does not fit into your application design ensure that the used adapter cable meets the following requirements:
Maximum length: 200 mm It is recommended that the total cable length between the board-to-board connector pins on MC46 and the pins of the card holder does not exceed 200 mm in order to meet the specifications of 3GPP TS 51.010-1 and to satisfy the requirements of EMC compliance. Type of cable: Flexible cable or flexible printed circuit board designed to mate with the Hirose receptacle and headers specified above. The equipment submitted for type approving the Siemens reference setup of MC46 includes a 160mm adapter cable. See Chapter 7.1. MC46_HD_V03.05 Page 93 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e Test conditions and results Heat sinks and thermally conductive tapes 6.4 Thermal management solutions vary largely according to the usage of the final product and the design of the host device. Therefore, the focus of this chapter is on a brief overview of standard heat sinks and thermally conductive tapes that have been tested with MC46. 6.4.1 Table 39 shows the results of extensive testing based on different combinations of heat sinks and thermally conductive tapes. All measurements were performed under the same test conditions:
GPRS connection, Power control level 5, GSM Band: 850MHz GPRS Class 10 (3x downlink, 2x uplink), Coding Scheme CS-4 VBATT+ nom = 4.2V Ambient temperature: 55C The conductive tapes were attached either to entire bottom area of the module (in Table 39 referred to as Full area), or only to the ground pad near the power amplifier (in Table 39 referred to as PA only). MC46_HD_V03.05 Page 94 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released Table 39: Tested heat sinks and thermally conductive tapes and test results s mo b i l e Manufacturer Product name Description Rth Website Temperature reduction Conductive tape positioned on Test condition: Thermally conductive tape T2022 combined with different heat sinks (material characteristics of T2022: adhesive on both sides, silicon free, 100m, Rth > 0,1 K/W, manufacturer: Balkhausen) Fischerelektronik Fischerelektronik Fischerelektronik Fischerelektronik www.fischerelektronik.de 65mm x 37.5mm www.fischerelektronik.de www.fischerelektronik.de 80mm x 50mm x 8mm Not specified www.fischerelektronik.de Full area PA only PA only PA only Full area 12-15C 5-10C 4-5C 3-4C 4-6C 3.75 K/W 19 K/W 17 K/W Fischerelektronik 40mm x 50mm x 5mm Not specified www.fischerelektronik.de 1C Wakefield Wakefield Test condition: Heat sink SK 18 with conductive tape TAP 005 Balkhausen 13mm x 5mm 19mm x 8mm TAP 005 adhesive on both sides, silicon free, 125m 32 K/W 27 K/W www.wakefield.com www.wakefield.com 2C 2C Full area PA only PA only
>0,1 K/W www.balkhausen.com 10-13C Full area SK18 ICK R ICK C17 SFP 060-50 Aluminum Profile SFP 007-50 Aluminum Profile Spezial A&D Spezial A&D MC46_HD_V03.05 Page 95 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released 7 Reference Approval s mo b i l e Reference Equipment for Type Approval 7.1 The Siemens reference setup submitted to type approve MC46 consists of the following components:
Siemens MC46 cellular engine Development Support Box (DSB45) Flex cable (160 mm) from Hirose DF12C receptacle on MC46 to Hirose DF12 connector on DSB45. Please note that this cable is not included in the scope of delivery of DSB45. SIM card reader integrated on DSB45 Handset type Votronic HH-SI-30.3/V1.1/0 PC as MMI Antenna or 50 W cable to system simulator PC RS-232 DSB45 Antenna Flex cable 160mm GSM engine DAI cable for acoustic measuring DAI Box SIM Handset Figure 44: Reference equipment for approval Acoustic tester Power supply MC46_HD_V03.05 Page 96 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released s mo b i l e 7.2 Compliance with FCC Rules and Regulations The FCC Equipment Authorization Certification for the MC46 reference application described in Chapter 7.1 is listed under the The MC46 reference application registered under the above identifier is certified to be in accordance with the following Rules and Regulations of the Federal Communications Commission (FCC). FCC identifier QIPMC46, granted to Siemens AG.
This device contains GSM 1800MHz function that is not operational in U.S. Territories. This device is to be used only for mobile and fixed applications. 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 co-located or operating in conjunction with any other antenna or transmitter. Users and installers must be provided with antenna installation instructions and transmitter operating conditions for satisfying RF exposure com-
pliance. Antennas used for this OEM module must not exceed 7dBi (GSM 1900) and 1.4dBi (GSM 850) gain for mobile and fixed operating configurations. This device is approved as a module to be installed in other devices. Each OEM must obtain their own Certification for each device containing this module. IMPORTANT: Manufacturers of mobile or fixed devices incorporating MC46 modules are advised to clarify any regulatory questions, have their completed product tested, have product approved for FCC compliance, and include instructions according to above mentioned RF exposure statements in end product user manual. MC46_HD_V03.05 Page 97 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released 8 List of parts and accessories Table 40: List of parts and accessories s mo b i l e Description MC46 Supplier Siemens Ordering information Siemens ordering number: L36880-N8320-A100 Siemens Car Kit Portable Siemens Siemens ordering number: L36880-N3015-A117 DSB45 Support Box Siemens Siemens ordering number: L36880-N8301-A100 BB35 Bootbox Siemens Siemens ordering number: L36880-N8102-A100-1 Votronic Handset VOTRONIC SIM card holder incl. push button ejector and slide-in tray Molex Battery cell XWODA Shenzhen Xwoda Electronic Co., Ltd DF12C board-to-board connector U.FL-R-SMT antenna connector Hirose Hirose Votronic HH-SI-30.3/V1.1/0 VOTRONIC Entwicklungs- und Produktionsgesellschaft fr elektronische Gerte mbH Saarbrcker Str. 8 66386 St. Ingbert Germany Phone: +49-(0)6 89 4 / 92 55-0 Fax: +49-(0)6 89 4 / 92 55-88 e-mail: contact@votronic.com Ordering numbers: 91228 91236 Sales contacts are listed in Table 41. To place orders or obtain more information please contact:
Shenzhen Xwoda Electronic Co., Ltd Building C, Tongfukang Industrial Zone Shiyan Town, Baoan District Shenzen P.R. China Contact:
Waichard Tsui Info:
See Chapter 6.3 for details on receptacle on MC46 and mating headers. Sales contacts are listed in Table 42. See Chapter 4.1.2 connector, mating plugs and cables. Sales contacts are listed in Table 42. Phone: +86-755-27623789 ext. 370 Fax:
Email: waichard@xwoda.com.cn Http://xwoda.com.cn
+86-755-27623078 for details on U.FL-R-SMT MC46_HD_V03.05 Page 98 of 99 13.11.2003 MC46 Hardware Interface Description Confidential / Released Table 41: Molex sales contacts (subject to change) Molex For further information please click:
http://www.molex.com/
Molex Deutschland GmbH Felix-Wankel-Str. 11 74078 Heilbronn-Biberach Germany Phone: +49(7066)9555 0 Fax:
+49(7066)9555 29 Email: mxgermany@molex.com Molex Singapore Pte. Ltd. Jurong, Singapore Phone: +65-268-6868 Fax:
+65-265-6044 Molex China Distributors Beijing, Room 1319, Tower B, COFCO Plaza No. 8, Jian Guo Men Nei Street 100005 Beijing Peoples Republic of China Phone: +86-10-6526-9628 Phone: +86-10-6526-9728 Phone: +86-10-6526-9731 Fax:
+86-10-6526-9730 Table 42: Hirose sales contacts (subject to change) Hirose Ltd. For further information please click:
http://www.hirose.com Hirose Electric (U.S.A.) Inc 2688 Westhills Court Simi Valley, CA 93065 USA Phone: +1-805-522-7958 Fax:
+1-805-522-3217 Hirose Electric Co., Ltd. 5-23, Osaki 5 Chome, Shinagawa-Ku Tokyo 141 Japan Phone: +81-(0)3-3491-9741
+81-(0)3-3493-2933 Fax:
Hirose Electric UK, Ltd Crownhill Business Centre 22 Vincent Avenue, Crownhill Milton Keynes, MK8 OAB Great Britain Phone: 44-1908-305400 Fax: 44-1908-305401 s mo b i l e American Headquarters Lisle, Illinois 60532 U.S.A. Phone: +1-800-78MOLEX Fax:
+1-630-969-1352 Molex Japan Co. Ltd. Yamato, Kanagawa, Japan Phone: +81-462-65-2324 Fax:
+81-462-65-2366 Hirose Electric GmbH Zeppelinstr. 42 73760 Ostfildern Kemnat 4 Germany Phone: +49 711 4560-021 Fax
+49 711 4560-729 E-mail info@hirose.de Hirose Electric Co., Ltd. Europe Branch First class Building 4F Beech Avenue 46, 1119PV Schiphol-Rijk Netherlands Phone: +31-20-655-7460 Fax:
+31-20-655-7469 MC46_HD_V03.05 Page 99 of 99 13.11.2003
frequency | equipment class | purpose | ||
---|---|---|---|---|
1 | 2006-05-11 | 1850.2 ~ 1909.8 | PCB - PCS Licensed Transmitter | Original Equipment |
app s | Applicant Information | |||||
---|---|---|---|---|---|---|
1 | Effective |
2006-05-11
|
||||
1 | Applicant's complete, legal business name |
Teletrac Inc
|
||||
1 | FCC Registration Number (FRN) |
0010594315
|
||||
1 | Physical Address |
7391 Lincoln Way
|
||||
1 |
Garden Grove, California 92841
|
|||||
1 |
United States
|
|||||
app s | TCB Information | |||||
1 | TCB Application Email Address |
i******@ckccertification.com
|
||||
1 | TCB Scope |
B1: Commercial mobile radio services equipment in the following 47 CFR Parts 20, 22 (cellular), 24,25 (below 3 GHz) & 27
|
||||
app s | FCC ID | |||||
1 | Grantee Code |
NIU
|
||||
1 | Equipment Product Code |
BTLTRC
|
||||
app s | Person at the applicant's address to receive grant or for contact | |||||
1 | Name |
D****** T******
|
||||
1 | Title |
Director, Engineering
|
||||
app s | Technical Contact | |||||
1 | Firm Name |
CETECOM Inc.
|
||||
1 | Name |
L****** S******
|
||||
1 | Physical Address |
411 Dixon Landing Road
|
||||
1 |
Milpitas, California 95035
|
|||||
1 |
United States
|
|||||
1 | Telephone Number |
408-5********
|
||||
1 | Fax Number |
408-5********
|
||||
1 |
L******@cetecomusa.com
|
|||||
app s | Non Technical Contact | |||||
n/a | ||||||
app s | Confidentiality (long or short term) | |||||
1 | Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | Yes | ||||
1 | Long-Term Confidentiality Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | No | ||||
if no date is supplied, the release date will be set to 45 calendar days past the date of grant. | ||||||
app s | Cognitive Radio & Software Defined Radio, Class, etc | |||||
1 | Is this application for software defined/cognitive radio authorization? | No | ||||
1 | Equipment Class | PCB - PCS Licensed Transmitter | ||||
1 | Description of product as it is marketed: (NOTE: This text will appear below the equipment class on the grant) | GSM / GPRS Vehicle Tracking Unit | ||||
1 | Related OET KnowledgeDataBase Inquiry: Is there a KDB inquiry associated with this application? | No | ||||
1 | Modular Equipment Type | Does not apply | ||||
1 | Purpose / Application is for | Original Equipment | ||||
1 | Composite Equipment: Is the equipment in this application a composite device subject to an additional equipment authorization? | No | ||||
1 | Related Equipment: Is the equipment in this application part of a system that operates with, or is marketed with, another device that requires an equipment authorization? | No | ||||
1 | Grant Comments | Power listed is ERP for Part 22 and EIRP for Part 24. 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 co-located or operating in conjunction with any other antenna or transmitter. End Users and installers must be provided with antenna installation instructions and transmitter operating conditions for satisfying RF exposure compliance. Approved for use with antenna(s) as listed in this filing. | ||||
1 | Is there an equipment authorization waiver associated with this application? | No | ||||
1 | If there is an equipment authorization waiver associated with this application, has the associated waiver been approved and all information uploaded? | No | ||||
app s | Test Firm Name and Contact Information | |||||
1 | Firm Name |
Cetecom Inc.
|
||||
1 | Name |
L******** S******
|
||||
1 | Telephone Number |
408-5********
|
||||
1 | Fax Number |
510-2********
|
||||
1 |
l******@cetecomusa.com
|
|||||
Equipment Specifications | |||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
1 | 1 | 24E | BB | 1850.2 | 1909.8 | 0.933 | 0.1 ppm | 247KGXW | |||||||||||||||||||||||||||||||||
1 | 2 | 22H | BB | 824.2 | 848.8 | 1.18 | 0.1 ppm | 281KGXW |
some individual PII (Personally Identifiable Information) available on the public forms may be redacted, original source may include additional details
This product uses the FCC Data API but is not endorsed or certified by the FCC