User's Manual

July 10, 2002 3-1
CreataLink2 XT Hardware Integrator’s Guide Integration Overview
Integration Goal and Objectives
Integration Goal and Objectives
SmartSynch, Inc. recommends that you consider the impact of each task on the
development plan and allow sufficient time for required activities. Try to identify
critical path activities early in product development. The following list summarizes
the development tasks. These tasks are discussed in detail in the following chapters.
• Define a usage model.
• Define a message model that specifies how many messages will be sent/
received and how often.
• Define a service strategy.
• Define system design of integrated product
• Design the hardware.
• Consider power supply options.
• Identify the source antenna.
• Design, code, and test an end-to-end application between the data transceiver
and host device.
• Obtain regulatory approval.
• Set up an assembly and final test environment.
• Perform a field installation functional verification procedure.
• Develop an in-the-field problem isolation test strategy and the necessary test
tools.
Usage Model
As a developer, you must have, above all, a clear understanding of the end-use of
the product. End-use directs the development process; all design considerations aim
to meet the needs of the final customer.
Design issues related to a mobile device, such as alternator noise and vibration and
handling of changing RF conditions, are different from design issues required for a
fixed-point telemetry application powered by line power, battery, or solar panel.
End-user priorities should determine the critical engineering tradeoffs in the
product design.
You are responsible for defining the usage model. SmartSynch, Inc. is available to
provide assistance and answer questions but is not directly involved in this phase
of the project.
Message Model
The message model is related to the usage model. Create the message model to
determine how much and how often data is sent in each of the uplink and downlink
directions. Power supply requirements and network message routing selection
depend on this data determination. The amount of data sent and received is also
relevant in calculating the cost of airtime. Many engineering decisions require the
message model as source data.
You are also responsible for defining the message model. A typical approach to
creating the message model is to define the peak and average throughput
requirements based on the type of application. Take into account both normal and
unique conditions. Typical current consumption figures for each of the various
models of operation (transmit, receive, standby) are provided in this manual.
For ReFLEX networks, message latency is inherently longer than in circuit-
switched connections. Use shorter messages to minimize latency and increase
reliability.
3Integration Overview