PrototypeParkingMeterPhaseVIII

FinalReport

Projectteam:Dec0702

Client
IowaStateUniversityParkingDivision

Advisors
JohnW.Lamont,RalphE.PattersonIII,GregorySmith

TeamMembers
BretSchuring,PoojaRamesh,
WilsonKwong,MattSwanson
AlexWernli

DISCLAIMER:Thisdocumentwasdevelopedasapartoftherequirementsofanelectricalandcomputer
engineeringcourseatIowaStateUniversity,Ames,Iowa.Thisdocumentdoesnotconstituteaprofessional
engineeringdesignoraprofessionallandsurveyingdocument.Althoughtheinformationisintendedtobe
accurate, the associated students, faculty, and Iowa State University make no claims, promises, or
guarantees about the accuracy, completeness, quality, or adequacy of the information. The user of this
documentshallensurethatanysuchusedoesnotviolateanylawswithregardtoprofessionallicensing
andcertificationrequirements.Thisuseincludesanyworkresultingfromthisstudentprepareddocument
thatisrequiredtobeundertheresponsiblechargeofalicensedengineerorsurveyor.Thisdocumentis
copyrighted by the students who produced this document and the associated faculty advisors. No part
maybereproducedwithoutthewrittenpermissionoftheseniordesigncoursecoordinator.

Nov14,2007

TableofContents
1

Planning....................................................................................................................... 4
1.1
RequirementsSpecification ................................................................................ 4
1.1.1
StatementofNeed...................................................................................... 4
1.1.2
ConceptfortheProject............................................................................... 4
1.1.3
Systemblockdiagram ................................................................................. 5
1.1.4
Systemdescription...................................................................................... 6
1.1.5
Operatingenvironment............................................................................... 7
1.1.6
Userinterfacedescription........................................................................... 7
1.1.7
Functionalrequirements............................................................................. 7
1.1.8
Nonfunctionalrequirements ..................................................................... 8
1.1.9
Deliverables................................................................................................. 8
2 Design.......................................................................................................................... 8
2.1
Engineeringspecification .................................................................................... 8
2.1.1
TechnicalApproach ..................................................................................... 9
2.1.2
IntendedUsersandUses ............................................................................ 9
2.1.3
Hardwarespecification ............................................................................. 10
2.1.3.1 MasterComputerDesign ...................................................................... 10
2.1.3.2 SlaveComputerDesign ......................................................................... 11
2.1.4
Softwarespecification............................................................................... 13
2.1.5
Testspecification....................................................................................... 13
2.1.6
TestingResults........................................................................................... 14
2.1.6.1 PrinterJam ............................................................................................ 14
2.1.6.2 SoftwareCrashTesting.......................................................................... 15
2.1.6.3 DayLightSavingsTime.......................................................................... 16
3 Implementation ........................................................................................................ 16
3.1
Build .................................................................................................................. 16
3.1.1
Prototype .................................................................................................. 16
3.1.2
PlannedTasksandEndofSemesterDeliverables ..................................... 17
3.1.3
EstimatedResources ................................................................................. 19
3.1.4
Schedules .................................................................................................. 20
3.1.5
AccomplishmentsbasedonPlannedTasks............................................... 21
3.1.6
EarnedvalueAnalysis................................................................................ 22
3.1.7
Parts/vendorlist........................................................................................ 22
3.1.7.1 WindowsXPDevelopmentSystem....................................................... 22
3.1.7.2 Laptop ................................................................................................... 22
3.1.7.3 Computer .............................................................................................. 22
3.1.7.4 ComputerCase&PowerSupply ........................................................... 23
3.1.7.5 ComputerRAM ..................................................................................... 23
3.1.7.6 SolidStateMemory............................................................................... 23
3.1.7.7 WindowsXPEmbeddedRunTimeLicense .......................................... 23
3.1.7.8 LCD ........................................................................................................ 23
3.1.7.9 Keypad................................................................................................... 24

4
5
6
7
8
9

3.1.7.10
CoinAcceptor.................................................................................... 25
3.1.7.11
Printer ............................................................................................... 26
3.1.7.12
Power ................................................................................................ 26
3.1.7.13
Casecomponents.............................................................................. 26
3.1.7.14
Installation ........................................................................................ 28
3.1.7.15
DiscontinuedParts ............................................................................ 29
3.1.7.16
SpareParts ........................................................................................ 29
3.1.7.17
UnitPartsBreakdown ....................................................................... 30
AppendixAProjectPlan......................................................................................... 32
AppendixBDesignReport ..................................................................................... 32
AppendixCSoftwareFunctionalityDocument ...................................................... 32
AppendixDWiringDiagram .................................................................................. 33
AppendixEMechanicalCADDrawing.................................................................... 34
AppendixFInstallationGuide ................................................................................ 36

ListofFigures
Figure1:SystemOverview................................................................................................. 5
Figure2:SystemBlockDiagram......................................................................................... 6
Figure3:MasterHardwareBlockDiagram ...................................................................... 11
Figure4:SlaveComputerBlockDiagram......................................................................... 12
Figure5:Master/slaveunitblockdiagram ...................................................................... 13
Figure6:PrinterJamIssue ............................................................................................... 15
Figure7:MemoryLeakTestResults................................................................................. 16
Figure8:Personneleffortrequirements(original) .......................................................... 19
Figure9:Personneleffortrequirements(updated)......................................................... 19
Figure10:Projectschedule(original) .............................................................................. 20
Figure11:Projectschedule(updated)............................................................................. 20
Figure12:Deliverablesschedule(original)...................................................................... 20
Figure13:Deliverablesschedule(updated) ..................................................................... 21
Figure14:WiringDiagram ............................................................................................... 33
Figure15:LCDKeypadPlate ............................................................................................ 34
Figure16:PrinterPlate .................................................................................................... 35
Figure17:LCDShelfBracket ............................................................................................ 35
Figure18:Shelving........................................................................................................... 36

1 Planning
1.1 RequirementsSpecification
1.1.1 StatementofNeed
Traditional parking meter systems require one unit for every parking spot. In contrast,
two of the existing lots at Iowa State have been installed with computerized parking
meterunitsthatareabletoacceptmoney,printreceipts,andtrackmultiplespacesfrom
one or two locations. This setup provides advantages over the traditional parking
meters, such as the ability to monitor the entire lot and collect money from one
location.

However, there are still several problems with the current Iowa State parking meter
system. The current parking meter units lack the ability to communicate with one
another.Also,ifauserwishestoaddtimetoaparkingspaceforwhichtheyhavealready
paid,theymustreturntothesameexactparkingmeterunit.Thecurrentparkingmeter
units are difficult to program and require a specialist from a company that no longer
exists.Finally,thecostofanewparkingmetersystemtoreplacethecurrentsystemand
overcome these problems is too expensive for the university to consider. The cost of
each new programmable unit begins at $10,000 and rapidly escalates to more than
$75,000asfeaturesareadded.

1.1.2 ConceptfortheProject
BycollaboratingwiththeISUParkingDivision,theobjectiveofthisprojectistodevelop
an improved parking meter system to monitor the payforparking lots at Iowa State
University.Thissystemwillbesimilartothecurrentpayforparkinglotsimplementedon
the Iowa State University campus, but will allow for more functionality and flexibility.
Thenewsystemwillalsobemoreaffordable,userfriendly,andeasiertomaintain.

Commercial systems on todays parking meter market implement single processor

designs. The approach to the problem was to develop a parking meter system that
implementsmultipleunits,allofwhichwillcommunicatewithacentralparkingmeter
serverthroughasetofmaster/slaveconnections.Thisallowscommunicationbetween
units,andforusersofthelottobeabletoaddtimeviaanyparkingmeterunit.Thenew
system will also allow DPS parking enforcement officers to receive a single list of lot
activity instead of multiple lists. In addition, the system will have a redundant central
processorandadditionalmemory,whichwillcreateamuchmorerobustsolutionthanis
currentlyavailable.

Thenewparkingmeterunitswillhaveaneasytouseinterfacethatwillmakethemmore
user friendly, and allow DPS to effectively maintain the parking meter system. Finally,
the system will be implemented with standard computer hardware, which will make
duplicationeasieranddecreasethecostofconstructionandmaintenanceoftheparking

meterunits.

Alongwiththeactualparkingmeter,othersoftwareandhardwareisrequiredtomake
theprojectuseful.Nowthattheparkingmeterisintheparkinglot,itisdifficulttosolve
problemsonlocation.Thisdictatedtheneedforasimulatorthatcanbekeptinalabto
beabletosimulateproblemsandsimulatesolutions.Oncesolutionshavebeenfound,a
way to update the meters in the lot was needed. That is where the idea of a laptop
updating system started. These objectives are supplemental to making the prototype
parkingmeterunit.

1.1.3 Systemblockdiagram
Eachparkinglotwillconsistofasingleprimaryunitandmultiplesecondaryunitsplaced
in different locations of the parking lot servicing specific lots of the parking lot as
describedinFigure1.

SecondaryUnit

PrimaryUnit

ParkingLot
S

Secondary
Unit

Figure1:SystemOverview

ThesystembreakdownofeachunitisillustratedinFigure2below.Eachparkingmeter
unitconsistsofthefollowingcomponents.Thesecomponentsconstitutetheuser
interfaceperipherals
LCD
Keypad
Printer
CoinAcceptor
Italsoconsistsofthemasterand/orslavecomponentcomputers,UPSandthermostat.

LCD

Keypad

Computer

Coin
Acceptor

Printer

Thermostat

UPS

Figure2:SystemBlockDiagram

1.1.4 Systemdescription
This project will attempt to solve these problems by providing an improved parking
meter system to monitor the payforparking lots. This system will be similar to the
currentpayforparkinglotsimplementedontheIowaStateUniversitycampus,butwill
allowformorefunctionalityandflexibility.Thenewsystemwillalsobemoreaffordable,
userfriendly,easytoreproduce,andeasiertomaintain.

Theparkingmetersystemindevelopmentmaybeimplementedwithmanyunits,allof
which will communicate with a central parking meter server though a set of
master/slaveconnections.Usersofthelotwillbeabletoaddtimeviaanyparkingmeter
unitinthatlot.ThenewsystemwillallowDPSparkingenforcementofficerstoreceivea
singlelistoflotactivityfromanyoftheunitsinthatlot.Inaddition,thesystemwillhave
a redundant central database and additional memory, which will create a much more
robustsolutionthaniscurrentlyavailable.

Thenewparkingmeterunitswillhaveaneasytouseinterfacethatwillmakethemmore
user friendly, and allow DPS to effectively maintain the parking meter system. Finally,

the system will be implemented with standard computer hardware, which will make
duplicationeasieranddecreasethecostofconstructionandmaintenanceoftheparking
meterunits.

1.1.5 Operatingenvironment
Thenewparkingmetersystemwillbeinstalledinthenortheastportionoftheparking
lotwestoftheArmorybuildingatIowaStateUniversityinAmes,IA.Itmustbeableto
withstand extreme temperatures ranging from 30 F to 115 F (34 C to 46 C). The
parking meter units will also be able to deal with all forms of precipitation such as
humidity,rain,snow,andhail.

The parking meter units will be used on a regular basis, and often by users who may
treat the unit roughly. Because of this, the units must be durable and designed to
withstandextremeuses.Finally,becausetheunitswillbelocatedonacollegecampus,
itmustbesturdy,andresistanttoattemptsatvandalism.

1.1.6 Userinterfacedescription
TheUserInterfaceissupportedandprovidedbytheSlavecomponentunit.The
UnitinterfaceperipheralsareaLCDpaneltoobtainuserinputandfeedback,akeypad
fortheuserstoentertheinput,aprintertoprintthereceiptofthetransaction,lot
statisticsandotherinformation,andacoincollectortocollectthemoneypaidbythe
usersandtodispensethechangeifany,totheuser.

1.1.7 Functionalrequirements
Thefunctionalrequirementsfortheprimaryunitare
Theprimaryunitisatwocomponentunitwillconsistofamastercomputerthat
supportstheparkinglotMySQL5.0databaseandaslavecomputerthatprovides
theuserinterface.TheslavewillsupporttheuserinterfaceperipheralsCoin
acceptor,Printer,Keypad,LCDscreen.
TheSlavecomputerwillinteractwiththemastercomputertoaddandretrieve
usertransactioninformation.
Thesecondaryunitisaonecomponentunitthatwillconsistoftheslave
computerandthusprovideuserinterface.Itwillsupporttheuserinterface
peripheralsCoinacceptor,Printer,Keypad,LCDscreen.
Alldatabaseactivityontheactivemasterwillbereplicatedonthebackupmaster
byadatareplicationsupportedonthemasterunits.
TheunitswillonlyacceptthefollowingUScurrency:nickels,dimes,andquarters.
Theunitswilltimeoutaftera15secondinactivityperiod.
Theunitsshallgivecorrectchange
Changestothesystemratesshallnotaffectpreviouslypaidstalltimes.
Changestothesystemratesshalltakeaffectat12:00AM.

Thesystemshallnotacceptdatesfromthepast.
Softwareupdatestothesystemmustbemadethroughthelaptopbyremotely
connectingintothemaster/slavecomputers.

1.1.8 Nonfunctionalrequirements

Thesystemshouldbeabletorunforfouryearswithoutanymajorfailures
Alldocumentationmustbeavailabletomaintainthesystem
Partsforbackupunitshouldbemadeavailable
Allexposedmetalpartsshouldbegrounded(leakagecurrent)
WeatherresistanceTheentiresystemmustbeabletowithstandallpossible
weatherconditionspresentthroughouttheyearontheIowaStateUniversity
campus.Theseincludetemperaturesrangingfrom30Fto115F,aswellas
precipitation,severewindsandassociateddebris.
DurabilityThesystemmustbedurable,longlasting,andsecure.Sinceitwillbe
builtaboveground,itmustbeabletowithstandtheftattempts,vandalism,
corrosion,andminorcollisions.
ConstantOperationThesystemmustbeabletorunforconstantlyverylong
periodsoftimewithoutanyproblems.
PowerrequirementsThemaster/slavesystemmustrunoffofstandard110V
ACpower,aswellashavetheabilitytorunoffofbatterybackupforupto4
hoursincaseofmainpowerfailure.
HardwarerequirementsThemasterunitstoresasingledatabaseforallslave
unitsinasingleparkingarea.

1.1.9 Deliverables
ThedeliverablesforthisphaseoftheprojectistheProjectPlan.Thisconsistsofareport
thetasksplannedfortheyear2007fortheprojectDec0702,thedeliverablesandthe
milestones.Thedocumentalsoconsistsoftheworkbreakdownstructure,alistofthe
resourcerequirementsintermsofequipment,manhoursetcandtheprojectschedulea
detailedtimelineforwheneachtaskwillbeginandend.Thisdocumentisavailableat
AppendixA.

2 Design
2.1 Engineeringspecification
Thissectiongivestheoveralldetaileddesignfortheparkingmeterprototypeproject.
ThebasicblockdiagramfortheprototypeparkingmetersystemisshowninError!
Referencesourcenotfound..Thissectionfurtherexpandsonthatdiagramby
describingthedesignoftheparkingmeterunitsandthecomputersthatruntheunits.
Thissectionalsocontainsanupdatedpartslistthatlistsinformationaboutalltheparts
onthesystem.Theblockdiagramsarecomparedtothepartslisttodeterminewhat
partsareneededtobuildaspecificpartoftheparkingmetersystem.Thedesignreport

inappendixBdescribeseachofthebelowsectionsindetail.

2.1.1 TechnicalApproach
Most of the technical approach considerations have already been addressed, as
development of the master and slave units has been finished. The specific technical
considerations at this stage of the project will be in how to support and replicate the
unit, how to develop simulation capability, and how to update the unit via a laptop
computer.

Thecurrentmasterunitisadualprocessorredundantserverunit,withautomatic
failureprotection,runningLinuxonanx86architecture.Thisofftheshelfunitallows
for reliability and quick and easy software development, since the architecture is
common.Themasterunitwillhavethedatabaseinformationaboutthelotstored
onit.Storingthedatabaseontheredundantunitwillensurethattheinformationwill
notbelost.

The slave units are single processor units. They must support the user interface
peripherals:coinacceptor,printer,keypad,andLCDscreen.Theslaveunitswillhavethe
softwarepackagethatrunstheinterfacebetweentheuser,thehardware,andthe
database.

Themasterandslaveunitswillcommunicatethroughsoftwarethathasbeenpreviously
designedtoquerythedatabase.Themasterunitwillhavethissoftwareonit.Theslave
unitwillhavesoftwareonittointerpretthesignalsfromthehardware,andpass
themalongtothesoftwareonthemasterunit.Thesoftwareonthemasterwillthen
query the databases and pass the information back to the slave unit. From there the
slaveunitwillpasstheinformationtothehardwareandthustotheuser.

Thesoftwarepackagemustberobustandfeaturefilled.C++wasusedtoimplementthis
package. For the slave, the development environment is Windows XP Embedded
Operating System. XP Embedded was chosen because it takes up less space and does
nothavethemultimediafunctionalitythatXPhas.Themultimediafunctionalitywillnot
be needed and therefore does not need to take up the limited memory space on the
boards. For the master, Windows XPe was used. The database system, located in the
masterunit,usesMySQL,offeringcrossplatformcompatibilitybetweenthemasterand
slave. The task of keeping the databases redundant will fall to the utility MySQL
replicationfunctionality.

Simulationcapabilitywillmirrorthetechnicalimplementationoftheexistingsystemso
itcanbeusedasaneffectivedebuggingtool.

2.1.2 IntendedUsersandUses
Thesystemwillhavethreeclassesofuser(seeabove).

Forthefirstclassofusers(customers),thatparkinthelotthesystemwill:
Allowparkingspacestobepaidforbyaspecifyinganamountoftime,specifying
anendtime,orinsertingmoney.
Allowtimetobeaddedtoanyparkingspacefromanyunitinlot.
Printahardcopyreceiptiftheuserdesires.

Forthesecondclassofusers,theDepartmentofPublicSafety,thesystemwill:
AllowDPStomonitorpaidandunpaidparkingspotinthelot.
AllowDPStogatherparkinglotusagestatistics.

Forthethirdclassofusers,theDepartmentofPublicSafety,thesystemwill:
AllowDPStomonitorpaidandunpaidparkingspotinthelot.
AllowDPStogatherparkinglotusagestatistics.
AllowDPStochangehourlyratesandsetholidays.
Allowuserstoaddanddeletesecondandthirdclassusers.

Therearethreeclassesofuserswillusethesystem:

Firstclass:
Thecustomer(client).Thisincludesthefollowingcategoriesofusers:
o CollegestudentsatIowaStateUniversity.
o FacultyandstaffofIowaStateUniversity
o VisitorstotheIowaStateUniversitycampus

Secondclass:
Theadministrator.TheIowaStateUniversityDepartmentofPublicSafetystudent
employees. They need additional functionality in order to monitor the parking
lots.

Thirdclass:
The supervisor. This user will have to access to all the features available to
supervisorclass.

2.1.3 Hardwarespecification
2.1.3.1 MasterComputerDesign
The master computer shown in Figure 3 has the responsibility of hosting the mySQL
database for the parking meter system. The master computer does not need to
interface with anything except anEthernet switch. This basic design requires only the
motherboard,RAM,andadiskonchip,withaswitchandUPS.

Serial

PS/2

USB

CPU

PSU

Serial

Motherboard

RAM

UPS

IDE

Ethernet

Disk On Chip

Switch

110V AC

Master/
slaves

Figure3:MasterHardwareBlockDiagram

2.1.3.2 SlaveComputerDesign

The slave computer shown in Figure 4 is much more complicated than the master
computer. Since the slave is responsible for handling all the user input/output
functionality,morehardwareisrequiredthanthemastercomputer.Theextrahardware
makesthecostoftheslavemuchmorethanthemastercomputer.


Figure4:SlaveComputerBlockDiagram

Figure5showstherelationshipamongthecomponentsintheslaveunit.Thisunitisnot
as complicated as the master/slave unit because it does not house any master
computers.Alltheabovecomponentsarehousedinthehousingcasethatwasprovided
totheteambyDPS.

Thermostat

110V AC

UPS

Light Bulb

Keypad

Master

Master

Slave
LCD Display

Switch

Printer

Coin Acceptor

Secondary Unit(s)

Figure5:Master/slaveunitblockdiagram

2.1.4 Softwarespecification
ThesoftwarespecificationofthesystemisdescribedintheSoftwareFunctionality
Document.ThisisavailableinAppendixC.Itdescribesthefunctionalityofferedforeach
userclassandtheresultforeachofthefunctionality.

ThesoftwareforthissystemiswritteninC++.

2.1.5 Testspecification
Thefollowingisadefinitionofthemethodologiesandacceptancecriteriatobeusedin
thetestingoftheintermediateandendproductsresultingfromthisproduct.

Softwaretesting
Softwareisintheprocessofbeinginstalled,andtestedonasimulatorto
ensure proper operation. The software is being tested against existing
implementationstoensureuniformoperationbetweenunits.Thisalsoinvolved
testingdatabaseredundancysetuponthedualmasters.

Hardwaretesting
The simulator unit will require thorough testing upon completion. Tests have
been conducted to verify that the individual components were functioning as
well as the unit as a whole. For example, the team tested the hardware
functionalityoftheparkingmeterunittomakesureitworkedproperly.Testing
wascompletedbyasmanysubjectsaspossible,includingallDec0502,May06
02, Dec0602, May0702, and Dec0702 group members. Each test was
performed and documented with a PASS/FAIL that ensured timely fixing of any
problemsthatwereencountered.

Prefieldandfieldtesting
This team will assist the May0702 team in the testing that must occur before
thesystemisplacedintheparkingarea.
o The existing slave unit will be tested for full functionality in all
user interfaces prior to placement in the field. A set of defined
test cases will be used to test all user interfaces and boundary
conditions, as well as extreme cases. Once proper operation has
beenverified,theunitwillbemountedsemipermanentlyforfield
testing.
o Fieldtestingwillinvolveoperationoftheparkingmeterunitina
'reallife' non simulated environment for a specified period of
time. The teams will work closely with DPS to ensure proper
operationandsystemrepairsshouldanyproblemsarise.

Simulationsystemtesting
Thesimulationsystemwillbetestedforfullfunctionalityusingthesame
testcasesdevelopedfortheactualmasterandslaveunits.

2.1.6 TestingResults
Working with the May0702 team, five major rounds of software testing have been
completedtoverifythefunctionalityoftheapplication.Thesetestingroundshaveeach
identifiedbugswiththeparkingmetersoftware.Asofthedateofthisreport,allknown
criticalbugswithintheparkingmetersoftwarehavebeenfixed.Regressiontestingwas
usedtoverifythatthesoftwarechangesmadefixedthebugsinquestion.Thereisno
bugfree software, however, this team, in conjunction with the Dec0702, has done
everythinginitspowertoensurethatnomajorbugsexistwithinthecode.

Duringfieldtestingphaseofthisproject,theteamencounteredafewproblems.
2.1.6.1 PrinterJam
TheproblemwasthattheOnsiteprinterwouldjamwhileprintingreceipts.Thesystem
wouldonceevery23days.Todiagnosetheproblem,theprinterwastestedwith
differentpaperthickness,testedagainsttheprinterinthelab,differentdirectionsof

pull,anddifferenttesters.Wecouldthenconcludethatthemountingplatewas
obstructingthesmoothdispensingofprinterpaper.Asasolutiontotheproblem,we
decidedtocutthelidasshowninFigure6below.Theresultwasthattheprinternow
jammedonceevery23weeksagainsttheearlierjamofonceevery23days.

Figure6:PrinterJamIssue

2.1.6.2 SoftwareCrashTesting
Theissuewasthattheparkingmetersoftwarebegantocrashveryoften.Wefounda
temporaryfixtotheproblembysettingupasoftwarewatchdog.Thetestingapproach
usedforthisproblemwastotestthecommonuserfunctionality.Thememoryusagewas
monitoredthroughthetaskmanager.Theresultwasfoundtobeamemoryleakcaused
inathirdpartylibraryusedfortheprintfunction.Eachtimeareceiptwasprinted,a
largeamountofmemorywasallocatedandthismemorywaslaternotreleased.This
causedmemorytogrowrapidlyandeventuallyleak.

Memory Leak Tests

Memory Usage

Add coin

Print lot status (Paid)

Mem ory (KB )

4000

3800
3600

Print individual lot usage

Print individual lot usage

Print audit inf ormation

10

3200

11

3000
1

11

Use cases

13 15

17

19

Print lots status (Unpaid)

Print lot usage

3400

Initial

Print yearly audit inf ormation

Clear audit information

Clear audit information - repeat 6 times

12

Print list of Admin

13

Print ID

14

Specif y time

15

Added time to parking lot

16

Print list of invalid login attempt

17

Clear audit inf o - repeat twice

18

Clear yearly audit inf ormation

19

Add coin and cancel - repeat twice

Figure7:MemoryLeakTestResults

2.1.6.3 DayLightSavingsTime
Issuewaswithrecentdaylightsavingtimechange.AlawpassedbyLegislationshifted
theDSTbyaweekandhencenowthetimechangedoneweekearly.Thisproblemwas
fixedbyapplyingawindowspatch.Wealsoappliedpatchtotargetdesignersonew
imageswouldnothavethisproblem.

This team was also responsible for testing various hardware components inside the
primary server/client system. Previous teams testing found that the original heating
elementwasnotoperational,andareplacementparthadtobeorderedtofixit.This
teamdiscoveredthatthebatterybackupsupplythatwasoriginallyinsidetheunitwas
not functioning properly anymore to meet the power requirements demanded of the
system and the bad battery backup was replaced with a new backup supply. A power
surge problem surfaced during testing that caused other hardware failure due to
incorrectwiring.Theproblemwascorrectedandtheprimaryunitwasinstalledintothe
Armoryparkinglot.

3 Implementation
3.1 Build
3.1.1 Prototype
This project teams primary implementation activities involved preparing the original
unit for installation into the Armory parking lot, preparing customer use instructions,

devisingamethodofsupportingtheunitonceitisinstalled,andbeginningconstruction
ofthesecondslaveunittobeadded.

In order to prepare the original unit for installation into the Armory parking lot, a few
looseendsneededtoberesolved.Thefirstoftheseconsistedofproperlyinstallingthe
WindowsXPEmbeddedsoftwareneededtoruntheclientapplication.Byworkingwith
the teams advisors, and contacting representatives from Microsoft Corporation, the
Dec0702 team was able to properly install a functional version of Windows XP
Embedded.

To ensure that customers know how to use the unit once it has been installed,
instructions were written up by the May0602 team that gave stepbystep details on
how customers may purchase parking time using the various methods offered by the
software.TheseinstructionswereapprovedbytheteamsadvisorsandbyDPS,andare
ondisplayonasignovertheunitintheArmoryparkinglot.

Apreliminaryversionoftheerrorreportingformshavebeencreatedandapprovedby
both the teams advisors and DPS. These forms are currently in use and found at DPS
offices.

The parts have been received to begin construction on the second client unit. While
most of the internal connections and software installation will be done in conjunction
with the May0702 team, the finished construction, installation, and testing of the
secondclientunit.

3.1.2 PlannedTasksandEndofSemesterDeliverables

Maintenance/Support
o BetaTestinginPhaseI
Buildandinstallsecondslave
Developlongtermsupportstrategy
Fixdatabaseredundancy
Completedocumentation
o ProjectPlanTheprojectplanisadocumentthatdefinesthatprojectand
theplanforthecompletionoftheproject.Itdescribeshowdesign
decisionsweremadefortheprojectanddefinestheoverallproblem
domain.

o DesignReportThedesignreportisadocumentdescribingtheoverall
designoftheproject.Itisintendedtoprovideallthedetailsnecessary
forreplicationoftheprojectbyanindependentteam.

o SoftwareFunctionalityReportThecurrentteamwillprovide

documentationtosupporttheparkingmetersoftwareforfuture
programmerswhomustworkonthecode.Thesoftwarefunctionality
descriptionisacompletedescriptionofallpossiblefunctionsanyusercan
carryout.TheclassdescriptionswillbeaUMLdiagramforthesoftware
andthesoftwareflowchartswilldescribetheuserinteractionanddata
flowthroughthewholeprogram.

o UserGuideThecurrentteamwillprovideasetofdocumentation
instructingemployeesofDPShowtousetheparkingmetersystem.Alist
ofcommonoperations,andtheinstructionsforperformingthose
operations,willbegeneratedforeachofthethreeclassesofusersforthe
parkingmetersystem.

o Installation and setup guide The assembly/setup instructions are

containedinacookbookthatdetailsthestepsrequiredtoassemblethe
hardwareforaserverorclientunitandtocorrectlysetupthesoftwareto
runtheparkinglotapplication.Thisdocumentationismeanttoallowthe
building of subsequent parking meters using the same interchangeable,
cheap, easytoacquire parts. After setting up the secondary slave unit,
additional information was added to the cookbook to help subsequent
groups.

o TestdocumentsDocumentconsistingoftestcasestotesteachsoftware
functionallyoftheparkingmetersystem.

o Parts List The parts list is a document containing a complete list of

hardwarepartsneededtobuildeitheraclientoraserverparkingmeter
unit. This list has changed from previous semesters list due to former
parts no longer being available and online retailers no longer existing.
The team was able to find parts made by the same company, in most
cases, with the same functionality, and the list was updated to reflect
thesechanges.

o FinalReportThefinalreportisadocumentthatprovidesthemost
completedescriptionoftheprojectalongwitharecordofits
development.Itcontainsallaspectsoftheproject,fromthebackground
developmenttothetestingandendproductdescription.Thisdocument
alsoprovidessuggestionsforfutureworkontheproject.

3.1.3 EstimatedResources
Task1ProjectFamiliarization
Task2UpdateSpecSheetandDesignDocument
Task3TestingoftheCurrentUnit
Task4PreparationandInstallationofUnit
Task5SupportUnit
Task6BuildSecondUnit
Subtask6.1HardwareAssemblyofSecondUnit
Subtask6.2InstallationofSoftware
Subtask6.3TestingofSecondUnit
Task7ParkingMeterSimulationSystem
Subtask7.1InstallationofSoftware
Subtask7.2Testingofsimulationsystem

11

10

Personnel Effort Requirements

7.2
7.1
9
10
7.2.1 7.2.2 7.2.3
0
3
1
0
15
30
5

148

25

20

35

15

156

15

10

15

35

10

157

10

15

35

10

133

15

20

15

35

10

158

38

80

55

34

11

80

170

40

14

25

35

752

Name\Tasks

Wilson Kwong
Pooja Ramesh
Bret Schuring
Matt Swanson
Alex Wernli
Total

35

25

20

15

25

20

35

35

150

12

13

Total

Figure8:Personneleffortrequirements(original)

11

12

13

Total

10

Personnel Effort Requirements

7.2
7.1
9
10
7.2.1 7.2.2 7.2.3
0
5
1
10
5
30
0

142

35

20

35

150

12

10

15

35

20

10

167

15

35

10

124

15

25

15

50

156

36

75

65

38

21

70

185

20

14

25

35

739

Name\Tasks

Wilson Kwong
Pooja Ramesh
Bret Schuring
Matt Swanson
Alex Wernli
Total

32

27

21

13

27

20

33

25
138

Figure9:Personneleffortrequirements(updated)

Figure8andFigure9showtheoriginalandupdatedPersonneleffortrequirementsfor
thisproject.Theupdatedpersonneleffortrequirementsreflecttheactualtimespentto
dateonthecompletedtasks1,2,3,4,6,7.1,and10.Thehoursfortheremainingtasks
wereupdatedtoprovidethegroupwithbetterutilizationofthepersonnel.

The updated personnel effort requirements (from Figure 8 to Figure 9) reflect the actual
timespenttodateonthecompletedTasks1,2,3,and4.Thehoursfortheremaining
tasksdidnotchange;theyarestillaccurateestimatesoffutureeffort.Thehoursspent
on Task 1 (project familiarization) increased because more time was needed to fully
familiarize the team with the project. Tasks 3 and 4 increased due to unforeseen
complications.

3.1.4 Schedules
This section includes Gantt charts included to illustrate the project schedule and
deliverables. The project schedule is dependent on collaboration with the May0702
team,andtheDec0702team.

Figure10:Projectschedule(original)

Figure11:Projectschedule(updated)

Figure12:Deliverablesschedule(original)

Figure13:Deliverablesschedule(updated)

3.1.5 AccomplishmentsbasedonPlannedTasks
1.MaintenanceandSupportBetaTesting
PhaseI
ProvideunitsupportMarch07December07
ECpETechnicianswillprovidelongtermsupport
PhaseII
NewSeniorDesignTeam
ECpETechnicians

2.BuildandInstallSecondSlave
Newslaveunitwasbuilt
NewshelvingdesignedwiththehelpofmechanicalengineeringstudentKyle
Banwart
Heater/LightCircuit
o Normalthermostatoperation
o AlwaysOnstateforworkingatnight
Filtertoblocksnowingress
Newlayoutforincreasedsafetyandefficiency
Canbeconnectedtocurrentunitinthefield

3.DatabaseRedundancy
XPeimageswereredonetoenablethefollowingfeatures
o supportMySQL
o AdvancedFirewallsettings
o Timesynchronizationbetweenthe2masters
InstallationofMySQL5.0onbothmasters
Setupdatareplication
Testeddatabaseredundancy
Updatedocumentation

4.Documentation

3.1.6 EarnedvalueAnalysis
PlannedTasks
forsemesterFall07

Status

Planned
Semester
Hours

Hours
Spent

Cost
Performance
Index

Schedule
Performance
Index

Maintenance/Support
PhaseI

Completed

113.33

260

0.436

Build&InstallSecond
Slave

Completed

100

85

1.176

Developlongterm
supportstrategy

Completed
(LelandHarker)

DatabaseRedundancy

Completed

34

50

0.68

Documentation

Completed

78

60

1.3

Total

325.33

465

0.813

3.1.7 Parts/vendorlist
3.1.7.1 WindowsXPDevelopmentSystem

Source:Microsoft
Price:$995
3.1.7.2 Laptop

Source:ComputerSupportGroup
Price:$0
3.1.7.3 Computer

3.1.7.3.1 SlaveMotherboard

VIAEPIAME6000GFanlessMiniITXMainboard
Source:http://www.logicsupply.com
Cost:$154.00
Notes:Motherboardcontainsintegratedprocessor.Additionalneededfeatures
includeonboardEthernet,2USBports,2serialport.

3.1.7.3.2 MasterMotherboard

VIAEPIAML8000AGMiniITXMainboardwithFan

Source:http://www.logicsupply.com
Cost:$119.50
Notes:Motherboardcontainsintegratedprocessor,Additionalneededfeatures
includeonboardEthernetandaUSBport.
3.1.7.4 ComputerCase&PowerSupply

TravlaC158MiniITXCase
90WPowerSupply
Source:http://www.itxdepot.com
Cost:$128.00
Notes:The60Wpowersupplyisselectedbydefault.Makesuretoselectthe
90Wsupply.
3.1.7.5 ComputerRAM

256MBPC2100RAM
Source:http://www.newegg.com
Cost:$23.00
Notes:Anycompanywilldo.
3.1.7.6 SolidStateMemory

MD1665D512XP
Source:http://www.digikey.com/
Cost:$37.65
Notes:Servesastheharddisk.NomovingpartsanditusesanUSBinterface.
3.1.7.7 WindowsXPEmbeddedRunTimeLicense

Source:Microsoft
Price:$79
3.1.7.8 LCD

3.1.7.8.1 LCDModule

MatrixOrbitalLk40425E
Source:http://www.matrixorbital.com/
Cost:$99.95
Notes:Thismodulehasa4x40characterdisplay,aswellasaserialinput.No
driversneeded.

3.1.7.8.2 SerialCable

DB9MaletoDB9Female9CSerialStraightthruCableMelded1ft
Source:http://www.sfcable.com/
Price:$2

Notes:1ftissuggestedanyMaletoFemaleStraightthruSerialwilldofromany
provider
3.1.7.9 Keypad

3.1.7.9.1 Keypad

StormInterface16KeyWhiteBacklitGLXseriesGSLW160203
Source:http://www.digikey.com
Cost:$70.23
Notes:Providestheneededkeyconfigurationandisbacklit

3.1.7.9.2 KeypadEncoder

VIP313MGR1
Source:http://www.vetra.com/312txt.html
Cost:$35
Notes:Convertsa4x4keypadmatrixtoPS/2scancodes

3.1.7.9.3 Keypadbuttonslabels

GSA0T203
Source:Digikey
Cost:$2.58
Notes:ThiscontainslabelsforallkeypadbuttonsexceptCancel.Thecancel
buttonneedstobecreatedbyprintingononeoftheincludedblanklabels.

3.1.7.9.4 PS/2Cable

Cutoffofusedkeyboard
Source:CSG
Cost:$0
Notes:PS/2connectortoconnectkeypadtotheslavecomputer

3.1.7.9.5 ConnectorHousing(20pin)

A26978ND
Source:Digikey
Cost:$1.39
Notes:Usedtoconnectthekeypadencodertothekeypad.

3.1.7.9.6 ConnectorHousing(6pin)

A26967ND
Source:Digikey
Cost:$0.62
Notes:UsedtoconnectthekeypadencodertothePS/2cable.

3.1.7.9.7 ContactCrimp

A25943ND
Source:Digikey
Cost:$6.26(10)
Notes:Usedtoconnectthekeypadencodertothekeypadandthekeypad
encodertothePS/2cable.

3.1.7.9.8 Wire

18gauge
510spool
Source:Lowes
Cost:$2
Notes:Usedtoconnectthekeypadencodertothekeypadandthekeypad
encodertothePS/2cable.
3.1.7.10 CoinAcceptor

3.1.7.10.1 CoinAcceptor

CoincoGlobal700
Source:IowaStateDPS
Cost:$0
Notes:DPShasextrasoftheseonhandastheyareusedinthecurrentparking
meters.Thisitemconnectstothecoinacceptorcontroller(MDB2PC).

3.1.7.10.2 CoinAcceptorController

UpstateNetworksIncorporatedMDB2PC
Source:http://www.upstatenetworks.com/mdb/
Cost:$299.50
Notes:ThisconvertstheMDBprotocoloutputtedfromthecoinacceptorto
serialdatathatthecomputercanread.Nodriversneeded.

3.1.7.10.3 CoinAcceptorControllerEnclosure

SR171BNDblackplasticprojectenclosure
Source:http://www.digikey.com
Cost:$10.65
Notes:Any4.88X6.88X1.5orsimilarenclosurewilldo.

3.1.7.10.4 CoinAcceptorControllerPowerCable

Source:CSG
Price:$0
Notes:Takefromausedpowersupply.

3.1.7.10.5 3ftSerialStraightthruCable

DB9MaletoDB9Female9CSerialStraightthruCableMolded3ft

Source:http://www.sfcable.com/
Price:$3
Notes:Cablemustbeatleast3ft.Otherwisesameasthe1ftSerialNotes.
3.1.7.11 Printer

3.1.7.11.1 ThermalPrinter

ReplacementforIPFXTRKioskPrinter
Source:http://www.ipcprint.com
Cost:approx.$350.00
Notes:CallBobJonesat(214)2211049forreplacementforIPFXTRKioskPrinter

3.1.7.11.2 PowerSupplyCable

4pinconnectormotherboard
Source:CSG
Price:$0
Takefromausedpowersupply.

3.1.7.11.3 3ftUSBtoPrinterCable

USB2.0AtoBRightAngle3ft.Cable
Source:http://www.cooldrives.com
Price:$7
Note:ThePrinterConnectionhastobeatarightangletopreventfromthewire
interferingwiththepaper.
3.1.7.12 Power

3.1.7.12.1 CoinandPrinterPowerSupply

MeanwellAD155ASwitchingPowerSupply
Source:http://www.switchingpowersupplies.com
Cost:$93.00
Notes:Dualpowersupplyprovidespowerforboththeprinterandthecoin
acceptor/controllercard.

3.1.7.12.2 BatteryBackup(UPS)

OPTIUPSValueSeriesVS575C575VA345W6OutletsUPS
Source:http://www.newegg.com
Price:$50.00
Notes:Thismodelwasselectedbecauseofdimensions,butanyUPSwilldo.
3.1.7.13 Casecomponents

3.1.7.13.1 OuterCase

Source:DPS
Price:Unknown
Notes:DPSprovidedthecasesfortheparkingmeterunits.Thecurrentparking
metermachinesintheArmoryparkingusethesamecase.

3.1.7.13.2 Thermostat

Source:Camewithparkingmetercase
Price:Unknown

3.1.7.13.3 EthernetSwitch

NETGEARFS10510/100MbpsDesktopSwitch5xRJ45
Source:http://www.newegg.com/
Price:$30
Notes:AnySwitchwilldofromanysource.Numberofportsneeddependson
thenumberofunitsinthatlot4forprimaryunitplus1foreachadditionalslave.

3.1.7.13.4 EthernetCables

RJ45
Source:CSG
Price:Free
Note:Cablesneedtobespeciallymadetogobetweenslaveunitandprimary
unitthreeadditional5ftcablesareneedinsidetheprimaryunit.

3.1.7.13.5 LCD/Keypadplatesteel

1x1SteelPlate(1/16)thickness
Source:CustomSteelServices,AmesIA
Price:$14.00
Notes:Thereareplansinthedesignreportforcuttingtheplate.

3.1.7.13.6 Printerplatesteel

2x2SteelPlate(1/8)thickness
Source:CustomSteelServices,AmesIA
Price:$33.75
Notes:Thereareplansinthedesignreportforcuttingtheplate.

3.1.7.13.7 Plexiglas

6x12Plexiglas(1/4)
Source:Lowes
Price:$3.00
Notes:ThisisusedforprotectingtheLCDscreen.

3.1.7.13.8 LightSwitch

Whitelightswitchwithoptionallight
Source:Lowes
Price:$3.00
Notes:Anybrandwilldo.

3.1.7.13.9 Lightswitchfaceplate

Whitefaceplate
Source:Lowes
Price:$1.50
Notes:Anybrandwilldo.

3.1.7.13.10

Utilityboxforthelightswitch
Source:Lowes
Price:$1.50
Notes:Anytypewilldo.

3.1.7.13.11

Lightbulb(Heater)

300Wstandardlightbulb
Source:Lowes
Price:$5.00
Notes:Actsastheinsideheaterfortheparkingmeters.

3.1.7.13.12

UtilityBox

Lightbulbsocket

Lightbulbsocket
Source:Lowes
Price:$3.00

3.1.7.14 Installation

BlueSprayPaint
SprayPrimer
SealantGlue
Screws
Metalsteelroll
Ties
Cableties
Cabletiesw/mountingholes
Doublesidedadhesive
ElectricalWire(16Gauge)
Maleplug

1.

2.

3.

4.

3.1.7.15 DiscontinuedParts
SlaveMotherboard
VIAEPIAME6000Motherboard
P/N:SKU#07241126421
Source:www.itxdepot.com
Notes:Motherboardcontainsintegratedprocessor.Additionalneededfeatures
includeonboardEthernet,2USBports,2serialport.
MasterMotherboard
VIAEPIA800Motherboard
SKU#R7241106350
Source:http://www.caseoutlet.com
Notes:Motherboardcontainsintegratedprocessor,Additionalneededfeatures
includeonboardEthernetandaUSBport.
ThermalPrinter
IPFXTRKioskPrinter
FujitsuFTP639MCL
Source:http://www.ipcprint.com
Cost:approx.$350.00
Notes:ConnectstotheclientviaUSB.
Keypad
StacoSwitchM151XX05
Source:http://www.stacoswitch.com
Cost:$90.00
Notes:Providestheneededkeyconfigurationandisbacklit

3.1.7.16 SpareParts
1. ReplacementKeycaps
MGR1561ND
Source:Digikey
Cost:$5.16
Notes:Theseareonlyneededifoneoftheexistingkeycapsistakenoffthe
keypadandneedstobereplaced.

3.1.7.17 UnitPartsBreakdown
3.1.7.17.1 PrimaryUnit

Part

SlaveMotherboard
MasterMotherboard
ComputerCase&PowerSupply
ComputerRAM
SolidStateMemory
WindowsXPEmbeddedRunTimeLicense
LCDModule
SerialCable
Keypad
KeypadEncoder
Keypadbuttonslabels
PS/2Cable
ConnectorHousing(20pin)
ConnectorHousing(6pin)
ContactCrimp
Wire
CoinAcceptor
CoinAcceptorController
CoinAcceptorControllerEnclosure
CoinAcceptorControllerPowerCable
3ftSerialStraightthruCable
ThermalPrinter
PowerSupplyCable
3ftUSBtoPrinterCable
CoinandPrinterPowerSupply
BatteryBackup(UPS)
OuterCase
Thermostat
EthernetSwitch
EthernetCables
LCD/Keypadplatesteel
Printerplatesteel
Plexiglas
LightSwitch
Lightswitchfaceplate
UtilityBox

Quantity
1
2
3
3
3
3
1
1
1
1
1
1
2
4
30
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1

Lightbulb(Heater)
Lightbulbsocket

1
1

3.1.7.17.2 SecondaryUnit

Part

SlaveMotherboard
MasterMotherboard
ComputerCase&PowerSupply
ComputerRAM
SolidStateMemory
WindowsXPEmbeddedRunTimeLicense
LCDModule
SerialCable
Keypad
KeypadEncoder
Keypadbuttonslabels
PS/2Cable
ConnectorHousing(20pin)
ConnectorHousing(6pin)
ContactCrimp
Wire
CoinAcceptor
CoinAcceptorController
CoinAcceptorControllerEnclosure
CoinAcceptorControllerPowerCable
3ftSerialStraightthruCable
ThermalPrinter
PowerSupplyCable
3ftUSBtoPrinterCable
CoinandPrinterPowerSupply
BatteryBackup(UPS)
OuterCase
Thermostat
EthernetSwitch
EthernetCables
LCD/Keypadplatesteel
Printerplatesteel
Plexiglas
LightSwitch
Lightswitchfaceplate
UtilityBox

Quantity
1
0
1
1
1
1
1
1
1
1
1
1
2
4
30
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1

Lightbulb(Heater)
Lightbulbsocket

1
1

4 AppendixAProjectPlan
Thisdocumentisavailableat
http://seniord.ece.iastate.edu/dec0702/docs/ProjectPlanDec0702.pdf

5 AppendixBDesignReport
Thisdocumentisavailableat
http://seniord.ece.iastate.edu/dec0702/docs/DesignReportDec0702.doc

6 AppendixCSoftwareFunctionalityDocument
Thisdocumentisavailableat
http://seniord.ece.iastate.edu/dec0702/docs/SoftwareFunctionalReport.doc

7 AppendixDWiringDiagram

Figure14:WiringDiagram

8 AppendixEMechanicalCADDrawing
LCDKeypadPlate

Figure15:LCDKeypadPlate

PrinterPlate

Figure16:PrinterPlate

LCDShelfBracket

Figure17:LCDShelfBracket

Shelving

Figure18:Shelving

9 AppendixFInstallationGuide
Thisdocumentisavailableat
http://seniord.ece.iastate.edu/dec0702/docs/InstallationGuide.doc