User's Manual
Table Of Contents
- Application and Integration
- Developers Guide
- DECLARATION OF CONFORMITY
- DECLARATION OF CONFORMITY2Revision History5Purpose Of This Document5Distribution5Related Documentation5Module Descriptions and Specifications6iO15 Modem Product Specificationss6Electrical specifications:6Environmental Specifications6Other Specifications
- Purpose Of This Document
- Distribution
- Related Documentation
- Module Descriptions and Specifications
- iO1500R Evaluation board
- Safety Notice - ATTENTION
- iO1500R Hardware Interfacing Information
- Design Considerations For iO1500R OEM Developers
- Module Software And Interface Modes
- Managing User Image Profiles
- How To Use Hayes Compatible Packet Data mode
- iDEN data modules – Software integration.
- Additional Information For Registering and Going Offline
- Summary Of AT Commands
- Appendix A: Requirements For FCC Testing
Design Considerations For iO1500R OEM Developers
Hardware Considerations
• Developers need to work with carriers to approve applications on their network.
• The end product must display the IMEI and serial # of the module.
• The module must use OEM_ON-OFF (Pin 17) to power on and off.
• Be aware of current consumption when unit is not registered.
• The external connector on the end product MUST have direct access connections
to the iO1500R’s PINS, with no relays through other microprocessors or buffers.
• The end product needs FCC approval
• Developers need system test procedures for production processes.
• Developers need to be aware of the requirements of certain pins, mentioned in
the pin description section in order to communicate via RS232.
• Care should be taken when interfacing RS232 lines to external interfaces. RS232
pins must not exceed 3.0 volts or the iO1500R will be damaged.
• To use RS232, the MUX_CNTL input (pin 15) must be held at logic low
(internal pull down provided).
• The MOD pin is pulled low through an internal 22 KOhm resistor. Motorola
recommends routing the MOD signal to an external connector.
Software Considerations
• When integrating the unit inside a terminal, it is required that the user will have
access to the module basic service utilities such as: Master Reset, RSSI Display,
SQE Display and others. This is accomplished by use of AT commands, as
explained later in this document.
• The end product needs to be able to perform a Module Reset and Master Reset
commands on the module.
• It is recommended that the unit will be able to display system registration
information and RSSI/SQE readings.
• Developers who change default User Image profiles must use proper profile
management processes outlined in this document to properly back them up
before overwriting them. Packet data services can be lost if this is not handled
properly.
• Developers should be able to implement network specific status messages to the
end user as an aid for users and for customer care to query the current status the
iO1500R.
20/5/03 page 13 of 37