Nancy Babiarz
1) Progress Reports 30 min
3) Meetings, Attend 1 h
8) Doc, Plan 1.5 h
Mostly, just worked on the project plan revisions.
Haven't had a chance to look at design doc yet.
Didn't spend enough time doing small things
(ie talking to spencer about MT presentation)
to really log...
No problems.
plans:
Start a Video - Idea Notebook.
Re-do schedule.
Talk to Chris about the web stuff.
================================================
Prabhath
1) Hours spent on each activity
- Progress reports <- about 20 minutes
- Meetings Attend <- 1 hours (Friday meeting)
- Research <- 2 hours , Delphi Book, Examining old code
- Code Basic - Pc <- 7 hours (3 sunday, 1 Tuesday, 3 Wednesday)
2) Any problems you have encountered. This is important, as the
people at the meetings will hopefully be helping you get solutions!
- No real problem,s just should have checked about equipment ahead
of time, it seemed we had to hunt for each thing because I didnt
check about equipment before everyone left.
3) Plans for next week.
- Thursday (today) -> Test our positioning app, debug it
- Friday(and Thursday) -> Look over design, make comments
- Saturday - Tuesday -> Work on adding serial communications, possibly
according to design doc drafts
- Wednesday -> Have a finsihed Analysis document.
- Thursday -> Decide how to approach adding more functionality, i.e,
work with old cyberguide, etc.
=================================================================
Derek:
Progress Report for April 11-18
4/11 - Meeting with design group to discuss high level functionality
of Cyberguide. Started to assign function for objects.
2.5 hours
4/12 - Status meeting with entire Cyberguide Group.
1 hour
4/14 - Meeting with design group to continue discusing high level
functionality. Also discussed scenarios that a user may have
when using Cyberguide. Also discussed the way the map will be
represented in Cyberguide.
3 hours
4/15 - Meeting with designteam to discuss low level communication of
Cyberguide. Also discussed scenarios that a user may have.
2 hours
4/16 - Meeting with design team to finalize high level design and discuss
communication between objects. Discussed design implications
of using a certain platform, such as limitations of the hardware
and functionality of a certain platform.
Began to write rough draft of the design document.
4 hours
4/17 - Finished writing the rough draft.
3.5 hours
=======================================================================
Jason
Analysis - 11 hours
o Found design specifications of the IR transceiver off Apple Newton site
o Range: 8 cm - 1 meter (at 19.2 kbps)
o Emission directional cone +/- 13 degrees
o Receive directional cone +/- 13 degrees
o Tested design specifications of the IR transceivers between two Newton
120's.
o Practical range is about 1 meter. One Newton (Screwdriver) transmits
and receives better than the other (Highball).
o Emission and receive cones is about the same as the specs.
o Tested IR communication between the two Newton 120's
o The first way was using a sample communication program. This
program came with source code, but requires that there be a receiving
side
o Tried two similar programs, typeomatica and beamomatica, which
transmit IR without having to have an established receiver. This
seems to be more of what we need. However, no source code was
available.
o Found program called Newtl which uses Slurpee. It allows connections to
UNIX boxes (several OS's, including Sun Solaris 2.5 / Sun SPARCstation.
Source code is available to check. This may be useful when communicating
from Newton to Unix box.
Problems
o Have not located Zip drive yet.
o No success with creating a prototype of IR communications between two
Newton 120's without establishing a formal connection yet.
Future plans
o Backup the Delphi files and Santana files as soon as I locate the ZIP
drive
o Am reading more on Newton 2.0 OS and communications. I recently found
a lot of documentation for it.
o Write a NTK script to setup an IR communications link between two
Newton 120's without having to establish the receiver (in other words,
do what beamomatica and typeomatica do)
==================================================================
Greg:
1) Hours Spent per Activity
Meetings - 1 hr.
Design - 22 hrs
2) Problems
So much design, so little time... As we went through the doc, we
were unsure of the levels of detail wanted on some portions... Hopefully
we did the right thing...
3) Plans for next week
Take any and all feedback from the design document, make corrections,
changes, etc...
=========================================================================
Mike:
Work done in the previous week:
PC/Delphi research 2hrs
Code-Basic (demo application) 6hrs
Code-Comm 4hrs
Web (equipment page, includes
tagging all items.) 3hrs
Meetings (Group) 1hr
Meetings (SubGroup) 8hrs
Problems encountered:
Difficulty with interfacing of Motorola transciever to PC for testing
(Couldn't find a proper cable).
Complications with COM ports on PC. The mouse--normally connected to
COM1--seems to be sending info to COM2, which is the port we are
using for the test.
Plans for next week:
Have demo finished, and begin working on actual incoropation into
Cyberguide.
Overall, I think Delphi is the way to go, at least if we develop on a
PC. Delphi is quick, fairly clean, and well documented.
=================================================================
Rich:
Friday April 12
1 hour - weekly status meeting
.5 hour - obtained equipment for installing Windows NTK at home
2 hours - attempted to install and learn Windows NTK
- found program crashes when trying to use browser
- found a good IR comm program on the cd-rom to attempt using
.5 hour - gathering necessary cabling tools for work on Saturday
hours worked: 4 hours
Saturday April 13
5.5 hours - worked with Jason Hong in open systems lab, spent most of
my time getting several Sharp IR devices wired up.
hours worked: 5.5 hours
total hours: 9.5 hours
Sunday April 14
.5 hours - attempted to make Windows NTK work on my pc, no success.
hours worked: .5 hours
total hours: 10 hours
Monday April 15
.25 hour locating a 20" monitor for Santana.
2.5 hours determining how to build cable from pc to motorola.
.5 hour building db-9 side of cable.
1 hour trying to debug Windows NTK, still no success.
hours worked: 4.25 hours
total hours: 14.25 hours
Wednesday April 17
.5 hour completing pc to motorola cable, notified cyberguide.
hours worked: .5 hour
total hours: 14.75 hours
Thursday April 18
.25 hour helping Prabbath with equipment for Delphi.
hours worked: .25 hour
total hours: 15.0 hours
=================================================================
Chris:
Hours Description
1 Meetings, Attend
22 Doc, Design
12 Web
Goals:
* Clarify and reorganize the design document, incorporating the
feedback generated by the design review.
* To web status report form:
* Add annotation fields to each classified task and allow naming
of unclassified tasks
* Add automatic tracking of classified activites
* Un-hack the form code :)
Problems:
The writing of the design document ended up taking enough time
that some of the actual design issues were muddled over.