Blog

4/19/2019

Uploaded final deliverables to website

Touched up development notes

Submitted final product

4/15/2019 (DOY 105)

Completed final demo!!

To do:

• Upload final deliverables to website
• Touch up development notes

Hours in lab: 1.5 (Marcel hours: 1.5)

4/13/2019 (DOY 103)

Completed after action review

Debugged things I thought I already fixed... cause of bugs unknown

Took screenshots

Next step:

• Final demo

To do:

• Final demo

Hours in lab: 4.0 (Marcel hours: 4.0)

4/12/2019 (DOY 102)

Completed dry run of demo

Next step:

• Final demo

To do:

• Final demo
• Take screenshots of working system for project poster
• Complete after action review

Hours in lab: 2.0 (Marcel hours: 2.0)

4/11/2019 (DOY 101)

Marcel straightened out vsat sim issues

Added timestamp to inst page

Fixed final bugs with page & scenario procs

Completed full system test

Next step:

• Go through a demo dry run
• Finish development notes
• Map basic user information (like which supplies power which systems)

To do:

• Demo dry run
• Final demo

Hours in lab: 4.0 (Marcel hours: 4.0)

4/9/2019 (DOY 099)

Fixed heartbeat, pointing, & image issues with procs/databases

Finished initial condition proc

Had some issues with the vsat sim connecting properly (not my instrument sim, although it did affect performance)

Next step:

• Fix temperature procs
• Run through a full system test

De-Scopes:

• Developing a scenario proc to induce an anomaly to the instrument system
• Writing user documents for Standard Operating Procedures

To do:

• Run through a full system test
• Demo dry run

Hours in lab: 2.0 (Marcel hours: 2.0)

4/5/2019 (DOY 095)

Tested display page & debugged scenario procedures

Next step:

• Build proc to set initial conditions
• Fix heartbeat & temperature procs
• (Time permitting) Develop a scenario proc to induce an anomaly to the instrument system

To do:

• Run through a full system test
• Potentially de-scope writing user documents

Hours in lab: 3.0 (Marcel hours: 3.0)

4/4/2019 (DOY 094)

Built telemetry display page

Next step:

• Test display page
• Build proc to set initial conditions
• (Time permitting) Develop a scenario proc to induce an anomaly to the instrument system

To do:

• Test display page
• Run through a full system test
• Write user documents

Hours in lab: 7.0 (Marcel hours: 2.0)

4/2/2019 (DOY 092)

Completed testing of all instrument scenario procs

Next step:

• Build display page
• (Time permitting) Develop a scenario proc to induce an anomaly to the instrument system

To do:

• Build display page
• Run through a full system test
• Write user documents

Hours in lab: 2.0 (Marcel hours: 2.0)

3/28/2019 (DOY 087)

Developed the rest of the scenario procs

Next step:

• Work w/ Marcel to make sue back-end stuff is all set for the scenario procs
• (Time permitting) Develop a scenario proc to introduce an anomaly to the inst system

To do:

• Test scenario procedures
• Build display page
• Run through a full system test
• Write user documents

Hours in lab: 4.0 (Marcel hours: 3.0)

3/19/2019 (DOY 078)

Tested interaction of cmds/tlm between the S/C & ground

Commands transmit & are received by the S/C

Marcel needs to troubleshoot on his end for transmission/receipt of telemetry

Next step:

• Add counter to inst_mode.proc
• Continue writing procedures for other commands

To do:

• Write scenario procedures
• Build display pages
• Run through a full system test
• Write user documents

Hours in lab: 1.0 (Marcel hours: 1.0)

3/18/2019 (DOY 077)

Started writing scenario procedures

Next step:

• Continue writing procedures

To do:

• Write scenario procedures
• Build display pages
• Run through a full system test
• Write user documents

Hours in lab: 2.0 (Marcel hours: 2.0)

3/8/2019 (DOY 067)

Discussion with Marcel about writing simulation procedures

Next step:

• Continue writing documentation
• Learn how to write the simulation procedures

To do:

• Write scenario procedures
• Build display pages
• Run through a full system test
• Write user documents

Hours in lab: 0.5 (Marcel hours: 0.5)

2/28/2019 (DOY 059)

Tested the telemetry/command database conversions!

Next step:

• Continue writing documentation
• Learn how to write the simulation procedures

To do:

• Write scenario procedures
• Build display pages

Hours in lab: 1.0 (Marcel hours: 1)

2/22/2019 (DOY 053)

Created the ground control telemetry/command databases!

Next step:

• Test the isolated databases & perform any debugging

To do:

• Test ground databases of telemetry/commands
• Connect the commanding and telemetry functions
• Write scenario procedures
• Build display pages

Hours in lab: 2.0 (Marcel hours: 2.0)

2/19/2019

Presented Critical Desing Review for AE 458

Feedback:

Check with Marcel

• License of 15 runtime excutions
  • Is the limit per workstation or accross the board?
  • Is the limit amount changeable?
• Are there any system updates to be aware of?
• Are there any end of the semester projects that interfere with development
  • Get a lab schedule ahead of time
• File sharing
  • Can I put all documentation on the website or is it sensitive to Hammers Co?

Fix

• Test plans
  • Update website
  • Cite conversation with Marcel
• User stories
  • Split #1 and #2 for inst vs gnd
• Update blog for Monday's development
• Strike separate server from plan
  • Backing up files on flash drive is fine for closed network project

Other

• A skeleton STOL proc should suffice
  • Template for procs or create a basic one
  • Can pass on for future dev
• Email Antunes spring break development plans

2/18/2019 (DOY 049)

Created the simulator command database!

Set up the ground control mnemonic database for conversion of the inst mnemonics

Next step:

• Finish creating menmonic conversions for the ground database

To do:

• Build ground database of telemetry/commands
• Connect the commanding and telemetry functions
• Write scenario procedures
• Build display pages

Hours in lab: 4.0 (Marcel hours: 3.0)

2/8/2019 (DOY 039)

Created the simulator telemetry database!

Need to revise user stories

Next step:

• Make a list of mnemonics for a command database off of telemetry
  • Think about hazardous and critical commands

To do:

• Build ground database of telemetry
• Build command database for the simulator and ground sides
• Connect the commanding and telemetry functions
• Write scenario procedures
• Build display pages

Hours in lab: 2.0 (Marcel hours: 1.5)

1/28/2019

Created scrum board

User story chosen for the week:

• Model the new simulator using the existing database for time efficiency (Priority 1)
  • Create mnemonic list
  • Add to database
  • Compile
  • Test
  • Repeat

1/24/2019 (DOY 024)

Met with Marcel in the SFOTC, discussed planning and database building

Hours in lab: 1.5 (Marcel hours: 1.5)