Technion – Israel Institute of Technology
Department of Electrical Engineering
High Speed Digital Systems Lab
Virtual Traffic Signs Controller
- Midterm Presentation Performed by:
Shahar Wolf
Ido Raz
Project instructor:
Mony Orbach
Spring Semester ‘04
1
Project Goals

Design and Implement a controller
for virtual traffic signs alert system,
that will:
• Manage data from the Motorola GSM/GPS
G18 card.
• Cross-analyze and integrate the GPS data
and the traffic data from the GSM, according
to known profiles.
• Send appropriate feedback to driver (if
necessary).
2
Hardware Architecture
3
Hardware Architecture
GSM
DSP
GPS
DB
4
Block Diagram
g18 evaluation board
RS-232
GPS
RS-232
GSM
Level Converter
eZdSP
SCIA
F2812
HOST PC
DSP
Code Composer
Studio
DRX
DTX
UART
SCIB
JTAG
DRX
DTX
On-board 1MB
External memory
5
Inputs

From GPS module:
• Data:
•
•
•
•
Coordinates (location)
Velocity
Direction of progress
etc…
• Communication feedback:
• Satellite communication status (locked/unlocked)

From GSM module:
• Data:
• Regional traffic data (signs, traffic info, etc…)
• Communication status with the GSM cellular network
• Contacting GSM network cells
• Reception level
• etc..
6
Outputs

Driver’s alert feedback:
• Deviation from regional traffic profile (for example:
exceeding max. speed, attention to risky situations,
etc..)

Motorola G18 card (communication
management):
• GPS module:
• Seek Satellite, lock Satellite, etc..
• GSM modules:
• Seek cellular cell, contact cell, cells handshake,
make sign of life, etc..
7
Layers and Modules Description
-Search and manage Database
-Analyze data according to known profiles
-Send feedback to driver
GPS Module:
GSM Module:
-Communication functions
-Communication functions
-Get data: location, velocity
-Request/get traffic data
GPS
GSM
Application
Interface/Drivers
Physical Layer
8
The Controller – G18 Interface

The F2812 DSP has two UART Serial Communication
Interfaces (SCIA, SCIB), with which it will
communicate with the g18 card, via two RS-232 ports.

RS-232 – CMOS level conversion between the two
cards.

Communication with the g18 card will be at the HWI
level.

Left to do:
– Acquire RS-232 - 3.3V CMOS level converter.
– Implement the communication drivers.
9
The Device Drivers
Application Interface Level
-control functions
For Example: Init_communication(), Receive_Location()
G18 Control Level
- Implement control functions that send ATcommands:
For Example: Network_Register(), Send_SMS(char *massage)
- Interpret G18 feedback (SWI)
RS-232 – UART Connection Level
send(string), receive(string) interrupts through SCIA,SCIB
10
Analyzing System’s Performance
Considerations for analyzing the systems
performance:

Analyze effective communication buad rate (BPS).
 Analyze application’s Modules Memory
consumption on the DSP controller (working
with/without DSP/BIOS).
– The external memory is up to 1M total memory

Analyze response time of the system.
11
System Characteristics - DSP
F2812 DSP
CPU Frequency
150MHz
Connection Speed
SCI programmable to 64K different baud
rates
On Chip Memory
L0 and L1: 4K x 16
ROM: 128K x 16
Flash: 128K x 16
External Memory
Up to 1MB
12
System Characteristics – g18
Motorola g18
Connection Speed
baud rate 4,800 up to 57,600bps
ONCORE GPS Receiver
Typical < 50 sec (warm)
Reacquisition: < 1 sec
Acquisition time
Accuracy
100m with Selective Availability (SA) as per DoD
specification
 25m without SA
 1 – 5m in Motorola differential mode (?)

Timing Accuracy
Aprox < 130 nsec
Serial
Cummunication
Baud rate up to 9,600bps
13
Schedule –

st
1
Semester
Study the development environment:
– Code Composer Studio – DONE!
– The TI Controller features – DONE!
– The Motorola G18 card interface – DONE!

Design the interface between the controller and
the G18 card – 2 weeks until 30/5 - Started
- While physical connection between the two cards is not yet
established, the G18 card will be simulated using internal
loopback of the SCIs.

Build GPS/GSM drivers – 6 weeks, milestones:
– Build the Connection level interrupt handlers - 13/6
– Build the G-18 control level – 30/6
– Build the Application interface level – 18/7

Simulate a primal test-case – End of 1st semester14