Final Project

Senior Projects II Jency Jacob/Talat
Ozyagcilar
Final Project Report February 9,2004
I. Project Description:
The objective of this project was to equip 2 (two) PDA devices in a way such that
users are able to send and receive messages between one PDA and another !ence" the
established connection between the two PDAs is point#to#point The list of components
that will be used in this project is as follows$
% 2 PDA devices
2 2 Transmitters and 2 &eceivers
' ( &) antennas for over#the#air communication
( *evel +hifter for ,nterfacing &) ,-s to the PDA
. Two /0 batteries as power supplies for the transmitters and receivers
The message pac1ets that are sent bac1 and forth are described by a %2#byte
pac1et format" where %3 bytes out of the total %2 bytes were data )irst" the pac1et format
started with a header field that signified the beginning of the pac1et )ollowing this" the
pac1et contained a field for encoding and decoding purposes Then" a field was used to
indicate the sequence number of the pac1et and the following ( fields represented ( data
(message) bytes Then" the ne4t byte in the pac1et format was the chec1sum for error
detection purposes After the chec1sum field" the ne4t 2 bytes represented the rest of the
data Then" to determine the end of the entire message" an end data field was used
)ollowing the end data field" an end pac1et field was used to determine the end of the
entire pac1et )or resolving the interference with other nearby &) devices or signals" the
communication will use a simple encryption
%
Ozyagcilar
II. Overall User Interface of Proposed System:
Please refer to the diagram below for the user interface for the general software
and hardware aspects of the proposed system ,n general" the user interface was
composed of a PDA" interface circuitry" and )5 transmitter6receiver modules The
interface circuitry was composed of combinational circuitry to translate the receiver
output from TT* to -57+ data for the PDA ,n the software" the user was able to write a
message" send the message" view the sent and received message" and close the messaging
session by using the standard home button

2
Communication
Distance
Approx 150ft.

Antenna Antenna Antenna Antenna

SONY
Serial
In/Out
Serial
In/Out
Interface
Circuitry
Level Shifter
Interface
Circuitry
Level Shifter
TXM-41-! !M SI"#X-4$$-!M
Transmitter #ecei%er

1 1
CLIE
&T 'ireless Messa(in(

SONY
CLIE
&T 'ireless Messa(in(

:
Messa(e:))))))))
Sent:))))))))))))
))))))))))))))))
#ecei%e*:))))))))
))))))))))))))))
Sent:))))))))))))
))))))))))))))))
#ecei%e*:))))))))
))))))))))))))))
Messa(e:))))))))
TXM-4$$-! !M SI"#X-41-!M
Transmitter #ecei%er
1 1
Ozyagcilar
III. Software Aspect: This section contains the subsections concerning &eliability"
Program Description" Pac1et Definitions" Pac1et )low6-ontrol +tates" 8rror !andling"
8ncryption6Decryption" Debugging" and Difficulties
IIIA+ #elia,ility:
The data pac1et format designed for the data transmission between the two nodes
was very useful for determining any corruption in the data as well as any missed or lost
bits in the pac1et The data is sent at /233bps and the message is broadcasted at every
%6%3 of a second ,f the data received was corrupted" then the same pac1et will be sent
again until it is received correctly The actual final software reliability of the system was
about //9" but the reliability of the hardware affected the results for wireless" such as
over#the#air noise
'
Ozyagcilar
III-+ .ro(ram Descri/tion 0 S/ecific 1ser Interface on Sony C"I2 :
&egarding software development" there were many programming languages to
choose from for developing software for a PDA :y using -" it was possible to code
using ;-ode <arrior= or ;P&- Tools= Also" the ;Palm 7+ 8mulator= helped simulate
the PDA environment on a P- for debugging purposes The website wwwpalmoscom
has many useful tools for software development on Palm 7perating systems Also" this
subsection describes what the user sees once the PDA wireless messaging program has
been initiated Please refer to )igure ,,,:% for the e4act user interface
7nce the program was initiated" the user was greeted with a welcome screen and
must tap continue to proceed with the program ,f the user ever wanted to e4it the
program" then the user was able to e4it the program with the standard PDA home button
After tapping the continue button" the user was presented with three options such as ;get
new screen name=" ;connect=" and ;cancel= ,f the user tapped the ;cancel= button" then
the user would go bac1 to the welcome screen ,f the user tapped the ;connect= button
without registering a screen name" then an error pop#up window saying ;please get a
screen name before connecting= showed up After tapping ;o1= on the pop#up window"
the user will go bac1 to the screen with the options ;get new screen name=" ;connect="
and ;cancel= once again The user can only tap the ;connect= button after registering a
screen name Therefore" by tapping on the ;get new screen name= button" a screen name
can be registered After tapping ;get new screen name= button" the user can register
his6her %3#byte screen name or tap ;cancel= ,f the user taps ;cancel=" then the user will
go bac1 to the screen with the options ;get new screen name=" ;connect=" and ;cancel=
!owever" the user cannot yet tap the ;connect= button because a screen name was not
registered ,f the user fills in a screen name and taps ;o1= on the user info screen" then the
user will go bac1 to the screen with the options ;get new screen name=" ;connect=" and
;cancel= !owever" this time" the user can tap connect because a screen name was
registered Then" the user will be presented with the actual chat screen !owever" the user
cannot send any messages until a connection has been established The title of the chat
screen will change from ;connecting= to ;connected= when a connection has been
established with the other user During the connection process" a connect pac1et as well
as its connect ac1nowledge pac1et was e4changed 7nce the connect and connect A->
pac1ets are e4changed and verified" the screen name entered by the user will be sent in
the %2#byte pac1et format 7nce the screen name data pac1et and its pac1et A-> are
e4changed and verified" a connection has been established After a connection has been
established" the other user?s screen name will show up in a pop#window saying
;-onnection 8stablished" Tal1ing to$ (screen name)= @ow" the user can send and receive
messages simultaneously ,f a user sent a message recently" then the user can only send
another message once the ac1nowledgement of the sent message has returned !owever"
the user can still write a message regardless ,f the user wanted to e4it the program from
the chat screen" then user can tap the standard home button once again
(
Ozyagcilar

A+ -+
C+
.
Tap
;-ancel=
Tap
;-ontinue=
31+ Tap ;Aet
@ew +creen
@ame=
34+ ,f Tap
;-onnect=
when @o
+creen @ame
&egistered=
31+
Aoto :
after
tapping
;71=" but
registered
Aoto : after
tapping
;-ancel=" but
not registered
Aoto 8" <hen
tap ;-onnect="
and screen name
was registered
After connection
establishment"
chat can happen
Ozyagcilar
D+ 2+
!i(ure III-+1 User Program
IIIC+ .ac5et Definitions:
This section describes the format of the data pac1et" such as its particular
fields and their descriptions Also" this section describes the format of the
connection pac1et" connection ac1nowledgement pac1et and data
ac1nowledgement pac1et
Data Packet Format
16 ,ytes
Data Packet Field Description
7ea*er: ,ndicated the beginning of a pac1et The receiver distinguished the
beginning of the pac1et with this byte and verified it for valid pac1et acceptance
This byte will always be B)2" where all other values were invalid
2nco*in( Se8uence 3: This number gave the receiver information on how
the received data should be decoded This number ranges from B3% # B)) and
was used as an offset in the encryption6decryption table The encoding sequence
number gets incremented for every pac1et sent <hen the encoding sequence
2
7ea*er 2nco*in( .ac5et 1
st
Data C9ec5sum 4
n*
Data 2n* of Data 2n* of
Se8uence 3 Se8uence 3 .ac5et
% byte % byte % byte ( bytes % byte 2 bytes % byte % byte
34+
Aoto :
after
tapping
;71=
Ozyagcilar
number reaches 2.." the encoding number is reset to % ,n this case" 3 is not used
for the encoding sequence number
.ac5et Se8uence 3: This number was the sequence number of the particular
pac1et within a data stream )or e4ample" if the sender sent ( pac1ets to transfer
the te4t at hand" then the sequence numbers was 3"%"2"' respectively !ence" the
receiver 1new if there were any pac1ets missed" or if the pac1et was corrupted
+ince the ma4imum siCe of an entire message was 2( bytes and each pac1et can
only have %3 bytes of data" the ma4imum number of pac1ets allowed is D
Therefore" the sequence numbers ranged from 3#2
1
st
Data: The first part of the actual data sent" where the data was A+-,,
characters
C9ec5sum: This byte was the mid#point in the pac1et This was another byte
to chec1 if the data pac1et was properly received without any data corruption
This byte was always the chec1sum of the entire pac1et
4
n*
Data: The second part of the actual data sent This will be A+-,,
characters
2n* of Data: This byte indicated if there were more pac1ets to follow the
current pac1et ,f the byte was a value of B3%" then it indicated more data to be
received ,f the byte was a value of B33" then it indicated no more data to be
received Also" all other values were invalid
2n* of .ac5et: ,ndicates the end of this particular pac1et This byte will
always be B/)" where all other values were invalid
Connection & Connection Acknowledgement
& Acknowledgement Data Packet Format
4 ,ytes
Connection & ACK Field Description
7ea*er: ,ndicated the beginning of the control pac1et &eceiver distinguished
the beginning of the pac1et by this byte and verified it for valid pac1et
acceptance This byte was always B). for the connection pac1et and data A->
D
7ea*er Control In*icator 2n* of
.ac5et

% byte 2 bytes % byte
Ozyagcilar
pac1et Also" this byte was always B-. for the connection A-> pac1et All other
values were invalid
Control In*icator: ,ndicated the type of control" such as control values for
pac1et ac1nowledgement" connection pac1et" and connection A-> Therefore"
regarding data ac1nowledgement control" regardless of the certain user message"
the first byte was the encoding sequence number that gets incremented for every
pac1et sent <hen the encoding sequence number reaches 2.." the encoding
number is reset to % ,n this case" 3 is not used for the encoding sequence number
Then" the second byte will always be the pac1et sequence number of the data
pac1et for the certain message &egarding connection establishment control" these
static bytes was always be B)%)A &egarding connection ac1nowledgement
control" these static bytes was always be BD'%2 As a result" all other values were
invalid
2n* .ac5et: ,ndicated the end of this particular pac1et This byte was always
B/) for connection pac1et and data ac1nowledgement pac1et )or the connection
ac1nowledgement pac1et" this byte was always BE- All other values were
invalid
IIID+ :eneral Al(orit9m Descri/tion:
Connection Estalis!ment & Exc!anging "ser #dentification #nformation$
Sending Side:
+end connect pac1et with proper control bytes indicating connection
request
<ait for connect A-> from the receiver end to stop the repeated
transmitting of the connect pac1et
+end Data pac1et with screen name
<ait for data pac1et A->
Receiving Side:
&eceive connect pac1et and chec1 pac1et format
,f connect pac1et format and control bytes are verified to be correct"
then send the connect A->
&eceive data pac1et with screen name and chec1 pac1et format
,f format of data pac1et with screen name and control bytes are
verified to be correct" then send the data pac1et A-> for finaliCing the
connection establishment
%ending message data:
:rea1 up the entire message into %3#byte pieces
Aenerate all pac1ets according to the specified format
E
Ozyagcilar
8ncode each pac1et according to the current sequence number
+tart transmitting each pac1et one by one
<ait for data A-> from the receiver end to stop the repeated transmitting of the
current pac1et
Also" if the sequence number in the received data A-> does not match the sent
message?s sequence number" resend the message pac1et repeatedly for the correct
data A->
7therwise" when data A-> is received" send the ne4t %3#bytes and 1eep sending
pac1ets until the entire user te4t message is transmitted
&ecei'ing message data:
&eceiver will constantly chec1 the pac1et !eader (,D) of the sent pac1et 7nce it
verifies the header" it will start processing the Data6Data A-> pac1et
,f the format of the data received does not match the e4pected pac1et format" then
ignore that data and no data A-> is sent
,f the format of the pac1et is accepted" then decode and continue processing until
the end of data indicator byte is read <hen end of data indicator byte is valid"
then deliver entire message to user screen
III2+ .ac5et !lo;/Control States:
)ollowing is a flowchart of how the full duple4 networ1ing between the two PDAs was
handled$
% ,nitial !andsha1ing $
A sending side sends a connect pac1et
The receiving side sends ac1nowledgement pac1et
,nitially" user profile information is e4changed between both ends

/
Sen*er/
#ecei%er
Sen*er/
#ecei%er
Connect .ac5et
Connect AC< .ac5et
Data .ac5et =
S
c
Sen*er/
#ecei%er
Sen*er/
#ecei%er
Ozyagcilar
2 -ommunication once the A-> is verified $
All other times" the sending side will send message (data pac1et)
The receiving side sends data ac1nowledgement pac1et to indicate acceptance of the
properly received sender pac1et

III!+ 2ncry/tion/Decry/tion:
A very simple static encryption was used for this project &eferring to the
data pac1et format" an encryption number was within the 2
nd
field of the sent
pac1et ,n the receiver and the transmitter" two identical tables of random
numbers were used for the encryption of the sent data

The identical table used is$ F(."%%2"2'"/E"%%"(E"22"2'."%"2."D("%%'"%(".'G
!ere is how the encryption6decryption wor1s$
% The sender increments the encoding sequence number it is sending out within
the pac1et just before it sends out a pac1et
2 Then" by ta1ing the encoding sequence number modulus %( (%( represents the
siCe of the encoding6decoding table)" the offset in the encryption table was
determined Then" the offset was used to find the number that will be added to
the first byte of data in the pac1et
' After this" it increments to each byte in the pac1et with the ne4t number in the
encryption table until all the pac1ets are encrypted
( The receiver gets the encoding sequence number from the 2
nd
field of the data
pac1et received
%3
Data .ac5et
Data AC< .ac5et
Sen*er/
#ecei%er
Sen*er/
#ecei%er
Data AC< .ac5et
Ozyagcilar
. ,t follows to same steps for determining the encryption numbers" but this time it
subtracts the numbers in the encryption table rather than adding
III:+ 2rror 7an*lin(:
The main source of sensor#related errors came from the over#the#air
transmission between PDAs +ome of the possible error estimates were as
follows$
Possible Error Source 1: The system has to 1now if the message just sent
has received by the intended target" also it is supposed to 1now if it was
received at all
Possible Error Source 2: There might be other systems that use the same
frequency that the two PDAs are usingH in this case the system should be
able to identify that current message is being sent from the other PDA
Possible Error Source 3$ A particular ;chun1= of information getting
corrupted once it reached the other end (,f all the handsha1ing was done"
and the devices transmitted te4t" there was a possibility of data becoming
corrupt over#the#air)
8rroneous data transfer was a major issue to overcome in the wireless data
%%
Ozyagcilar
lin1 There are several ways of avoiding errors occur during transmission The
way of error chec1ing for this project was as follows$
Header & Encoding Seuence !umber$ 8ach pac1et contained a header
that has a certain formatH there were certain developer pre#defined
characters within the header The receiver will e4pect these characters in
certain locations Also" the pac1et contained an encoding sequence
number ,f the format of the header and encoding sequence number is
anything different than e4pected" the message was ignored
Pac"et Seuence !umber #hec"ing$ +ince the ma4imum number of
pac1ets allowed is D pac1ets" where the sequence number ranges from 3#2"
the receiver 1nows what sequence number in the data pac1et it is
e4pecting Also" since the sender side sent the pac1et" the sender 1nows
what pac1et to send ne4t and what sequence number in the data A->
pac1et it is loo1ing for so that the ne4t pac1et can be sent !ence" invalid
pac1ets will not be allowed into the system
These two above#mentioned ways of error chec1ing
overcame the first two possible error sources completely !owever"
overcoming the '
rd
possible error source completely was not possible
because both ends had no control over the information traveling over#
the#air Also" the correction algorithms for errors that originate from
corrupted data are very hard to implement on a PDA due to limited
memory and processing power
III7+ Test Strate(y/De,u((in(:
A debug mode was written for the data transmission software The
debugger was able to monitor the raw data received" and was able to send single
test bytes to the listener As the code was developed further" certain information
obtained from the messages was read using the debugger" such as the sequence
number to be used for encoding the data and the actual created pac1ets for the
entire user message ,t was very important to define and develop the modules that
were needed in the code" before starting to code 8ach module was complete and
was not e4tremely dependent on any other module in the code )irst" testing was
done modularly in the code using the Palm 7+ 8mulator for P- Then" testing
was done in real#time The 8mulator for software debugging was obtained from
the ;palmsource= website (P7+8) This software was capable of emulating the
PA*5 7+ environment on a P- and made it possible to debug the software
without actually downloading it to the PDA !owever" after a certain point in the
project" real#time testing and debugging was necessary :y using pop#up
windows" the data received and sent can be seen on the PDA screen As a result"
errors within pac1et formats and missing data can be revealed to the developers
,nitially" the encryption and decryption process was removed so that actual sent
and received data can be verified Thereafter" the encryption and decryption was
%2
Ozyagcilar
implemented because all other data verification procedures were correct ,n the
end" all these procedures fi4ed minor as well as major errors
IIII+ Difficulties:
,n this project" a 2#way full duple4 data lin1 was established +eparating
the transmitting part from the receiving part was challenging since
these two major aspects of the project had to perform simultaneously and
independent from each other Another difficulty was synchroniCing the rate of
data between the two ends Also" managing the data buffers in memory required
the utmost attention
%'
Ozyagcilar
IV. Hardware Aspect: This section will contain subsections concerning the specific
-omponent Descriptions" 8rror !andling" Debugging" and Difficulties
I>A+ Com/onent Descri/tions: ,n general" the components that will be used are
PDA" parts for the ,nterface -ircuitry" and )5 transmitter6receiver modules
1+ .DA Son$ #lie PE%&S'2(
%(
Ozyagcilar
This PDA itself was a perfect platform for developing software and it was
a stand#alone device that did not require any support from another device to
control the &) ,-s to be used in the project ,t had a processor in it and used an
operating system that made it just li1e a simplified P- The components that
made up a PDA can be seen in )igure ,0A%% Developing software for PDAs
was just li1e developing software for any other P- environment if not easier
5ost applications were created on a P-" where the source code would be
compiled into the Palm &esource )ile )ormat The cost for the investigated part
for this project is currently ?144+@@ A taB" however this may go down eventually"
since the prices for PDAs are getting cheaper and cheaper
!i(ure I>A+1+1
The Iniversal -onnection port that was present in +ony -lie P8A#+J23
was capable of connecting to a P-?s I+: or +erial (&+2'2) port The /#pin serial
connection port" which was a part of the Iniversal connection port in this PDA"
made it very easy to interface the PDA to the &) chips used in this project The
PDA and the &) chips were connected to each other on a board The pin
connections were soldered The &) chips do not use all of the / pins required for
a &+2'2 connection" instead the data was supplied to transmitters through TKD
(pin %()" and data was read from &KD from receivers (pin %') The receivers
constantly chec1ed for data at /233 baud for flow control purposes" where
%.
Ozyagcilar
transmitters broadcasted at the same rate when necessary The PDA operated
with a .20 battery or a power supply ,t draws E33mA of current that ma1es the
power consumption (%2< The / pins on the PDA corresponding to the &+2'2
protocol was not a true &+2'2 connection Although the signals followed the
&+2'2 standard" the voltage range was between 3 and ''0 -57+ level
2 Interface Circuitry )e*as +nstruments S!,-.H#(/! 2&in0ut .!1 %ate
The receiver module outputs the over#the#air message at a voltage level of
3#.0 !owever" the PDA accepted input between voltage levels of 3 to
''0 The output of the receiver module and the input of the PDA was at
the same voltage range Therefore" this was accomplished by supplying a
''0 voltage level to the A@D gate The A@D gate was strong enough to
accept a higher voltage level than its supply voltage Then" both inputs of
%2
Ozyagcilar
the A@D gate was connected to the receiver output As a result" the A@D
gate accepted 3 to . volts and it output 3 to ''0

' Transmitter/#ecei%er )23&***&4 5 S+LR2&***&4
<hen regarding full duple4 communication and the PDA" the transmitter
and receiver connected to the PDA was able to send and receive messages at the
same time Therefore" a transmitter for one PDA was wor1ing at the same
operational frequency as the receiver for the other PDA !ence" each PDA was
able to send messages at one frequency and receive messages at another
frequency" but at the same time Therefore" for this project" the two chosen
%D
Ozyagcilar
transmitters operated at (%E 5!C (TK5#(%E#)#' )5 Transmitter 5odule) and at
('' 5!C (TK5#(''#) )5 Transmitter 5odule) The two corresponding chosen
receivers operated at (%E 5!C (+,*&K#(%E#) )5 +uper!eterodyne &eceiver
5odule) and at ('' 5!C (+,*&K#(''#) )5 +uper!eterodyne &eceiver
5odule) ,n general" please refer to )igure ,0A2% for general characteristics of
the transmitter series (TK5#444#)) and the receiver series (+,*&K#444#)) Please
refer to )igure ,0A22 and )igure ,0A2' for specific details regarding the
specific transmitters and receivers !ence" the final cost for a transmitter6receiver
pair is B2DD%
TXM-BBB-! !M Transmitter Mo*ule SI"#X-BBB-! !M Su/er7etero*yne
#ecei%er Mo*ule
#0ertical or horiContal placement
#+mall +iCe
#Analog or Digital modulation input
#Ip to 231bps
#Available in (%E5!C" (''325!C
#+upply range" 2Dv#.v
#-ompatible with the +,*&K series )5 &)
receiver modules
#0ertical or horiContal placement
#+mall siCe
#+A< controlled double conversion
superheterodyne architecture
#&) -arrier Detect 7utput
#Digital and Analog Demodulated )requency
outputs
#)ast enable time
#Ip to 23>bps data rates
#.v operation" %2mA
#-ompatible with TK5 series transmitter
modules
# #%3Dd:m sensitivity
#Available on (%E 5!C and ('' 5!C
!i(ure I>A+4+1
TXM-BBB-! !M Transmitter Mo*ule: To operate the transmitter" an addition of
power to the module supply pin" serial data to its data input" and the addition of an
suitable antenna were needed
%E
Ozyagcilar
!i(ure I>A+4+4
SI"#X-BBB-! !M Su/er7etero*yne #ecei%er Mo*ule: This receiver provided
an ideal counterpart to the )5 range of transmitters To operate the receiver" a
clean power supply" and an antenna were needed
TXM-41-!-$ TXM-4$$-!
Frequency 418MHz 433.92MHz
Supply VCC 2.7-3.6V < 10mA 2.7-3.6V < 10mA
Data < 20000bps Serial < 20000bps Serial
Radiated Power 0.25mW 0.25mW
Cost $25.80 $25.80
%/
Ozyagcilar
(@ote$ Pin2#A) represents )5 demodulator output)
!i(ure I>A+4+$

( Antenna 15-&***&6!#
The portable antenna was supplied with :@- connectors as standard This
series of antennas was used for the transmitters CTXM-BBB-!D and the
SI"#X-41-! SI"#X-4$$-!
Frequency 418MHz 433.92MHz
Supply VCC 4.5V 9V,
Iq < 13mA
4.5V 9V,
Iq < 13mA
Data 20000bps max 20000bps max
Cost $41.91 $41.91
23
Ozyagcilar
receivers CSI"#X-BBB-!D previously specified Please refer to )igure ,0A'%
for details of the antenna
!i(ure I>A+$+1
I>-+ 2lectrical Sc9ematics:
1/4-41--NC 1/4-4$$--NC
Description
Moulded 1/4 wave
antenna with BNC
connector
Moulded 1/4 wave
antenna with BNC
connector
Frequency
418 MHz 433 MHz
Price
B%3E3 B%3E3
2%
Ozyagcilar
!M Transmitter CTXM-4$$-!D / !M #ecei%er CSI"#X-41-!D .air 1
22
Ozyagcilar
!M Transmitter CTXM-41-!D / !M #ecei%er CSI"#X-4$$-!D .air 4
2'
Ozyagcilar
I>C+ 2rror 7an*lin(:
&egarding hardware error handling" hardware errors were only managed
by the software on the fly Therefore" if anything went wrong in the hardware and
caused the transferred or received data to be corrupted" the software detected and
handled this 7therwise" when the hardware malfunctioned or caused the unit to
fail" the hardware was debugged with an oscilloscope and multimeter
2(
Ozyagcilar
I>D+ Test Strate(y/De,u((in(:
There were certain testing and verification approaches employed to avoid
errors among the transmitters and receivers ,n order to test the transmitter and
receiver components" there were certain specifications to be verified )or
e4ample" the operating frequencies were chec1ed between the communication of
the corresponding transmitter and receiver pair To test the correct voltage supply
for the transmitter or receivers" a range of voltages were used to verify the
operation of the transmitter or receiver 7ne way to chec1 the rate at which the
transmitter sent the data was to try different baud rates" and then to see if the data
was received at the correct time +ince the most of the chips being used in this
project were purchased" the data sheets were very useful when debugging the
hardware The operating characteristics of each individual component that was
being connected together had to match The oscilloscope revealed noise problems
and was constantly chec1ed to see whether the signal ended up better or worse
Also" the multimeter was used to chec1 the voltages of all components and the
results were compared to those specified in the datasheets
2.
Ozyagcilar
I>2+ Difficulties:
As far as the noise problems were concerned" different types of
transmitters6receivers introduce noise problems to the system The major
hardware difficulty was the interference between the transmitter and the receiver
on one end of the system The transmitter on one frequency ended up jamming
the signal received by the receiver on the other frequency )irst" a single bo4 was
considered for each pair of transmitter6receiver !owever" there was still
significant noise As a result" each module ended up in its own metal bo4" but
isolating these two modules was very difficult Although each module was placed
in a metal bo4 to overcome the noise problem" the result did not fully solve the
interference The noise introduced when using transmitters and receivers in a
full#duple4 system was e4tremely cumbersome !ence" in future situations"
further advanced filtering should have been investigated and probably
implemented to overcome such a problem

22
Ozyagcilar
V. Overall Flow Diagram:
The following flow diagrams show the general flow for the sender and receiver
Sender Side

Connection 2sta,lis9e*

Receiver Side
(eader
:oo*
7ea*er No :oo*
2D
Create 1ser
.rofile
2sta,lis9
Connection
CSen* Connect
.ac5etD
'ait for
AC<
Create Data
.ac5et from
2ntere*
Messa(e
Sen* Data
.ac5ets
one ,y one
2sta,lis9
Connection
C#ecei%e
Connect .ac5et 0
user /rofile
/ac5etD
.rocess
.ac5et
CC9ec5
7ea*erD
Sen* AC<
.ac5et
Continue
.rocessin(
I(nore
/Discar*
.ac5et
Deli%er
2ntire
Messa(e
'aitin( to
#ecei%e
Messa(e
.ac5ets
Sen* .rofile 'ait for
AC<
Ozyagcilar
>I+ .erformance S/ecifications:
7perating range$ L%.3ft
)requencies used$ (%E5!C" ('' 5!C
A reliability of E39#/39 or higher
The ma4imum number of characters in one particular message was limited to 2(
characters
<hen indoors" there was a possibility that certain metal objects such as iron or other
interferences disturbed the connection between the two PDAs" thus ma1ing the system
malfunction
2E
Ozyagcilar
VII. Deliverables:
A E39#/39 reliable" 2#way full#duple4 data lin1
A user#friendly graphical interface
%.3 ft range
2 different transmission frequencies ((%E 5!C" ('' 5!C)" used simultaneously
2/
Ozyagcilar
VIII. Total Cost Estimates :
Item Count Price Vendor Total Cost
Sony Clie S& Series
.DA
2 B%.3 +ony B'33
SNE4A7CFN
4-In/ut AND :ate
2 B3%3 Te4as
,nstruments
)ree
(donated by
+pectracom)
TXM-BBB-! !M
Transmitter
2 B2.E3 A:A-75
Technologies
B.%23
SI"#X-BBB-! !M
Su/er7etero*yne
#ecei%er
2 B(%/% A:A-75
Technologies
BE'E2
1/4-BBB--NC
Antenna
( B%3E3 A:A-75
Technologies
B('23
Serial 7otsync Sync
Ca,le C"I2
2 B%.33 +) Planet B'333
.o;er Su//ly
2 B. 8nergiCer B%3
:eneral Costs
Cs9i//in( G taBG etcD
# # # B.3
Necessary !uture
com/onents/materials
C,oar*G etcD
# # # B%33
A//roB+ Total Cost
# # # B22E22
'3
Ozyagcilar
IX. Project Team Information:
Jency Jacob
237 Institute Drive, Rochester, N.Y., 14623
jxj9279@rit.edu
(585) 424-8874
Talat Ozyagcilar
757 Kimball Drive, Rochester, N.Y., 14623
tozyagcilar@hotmail.com
(585) 424-8847
'%

Final Project

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Final Project

Încărcat de

Drepturi de autor:

Formate disponibile

Senior Projects II Jency Jacob/Talat

S-ar putea să vă placă și