Enes Palaz Status Update

• What did you personally accomplish this week on the project?

I managed to edit my code to fit the requirements of the ILDA file format because there were some ambiguous parts like format being Big endian and also center of the coordinate system. As a result of this, we were able to successfully project an ILDA file generated by our own code. It can be seen in the team update section.

I also worked on integration of ILDa frame generation, buffer and DAC code with Eliana. It is still in progress.

 

•  Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?

No, everything is on schedule.

 

• What deliverables do you hope to complete in the next week?

I am hoping to complete the integration of other software parts and move to designing a case to put all the components in.

 

Jake Zimmer Status Update

• What did you personally accomplish this week on the project?
  • I worked on the embedded firmware for the safety subsystem. The initial results are promising and it is almost ready to be actually deployed on the board.
  • As such, the boards arrived earlier than expected. BOM has been finished and parts should arrive wednesday or so.

 

•  Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?
  • On track, but could see a potential slowdown once boards are assembled due to errors. There is not a great way to prevent this at this stage but it should have been mitigated by the design review that I performed. If there are errors, then they will be resolved with jumpers.

 

• What deliverables do you hope to complete in the next week?
  • Fully assembled boards and safety system on boards and working.

 

Eliana Cohen Status Update

• What did you personally accomplish this week on the project?
  • Integrated high level software pipeline with low level software, with assistance from Enes
  • Modified high-level software for greater performance improvements by using statically-allocated arrays rather than vectors in C++
  • Confirmed timing of whole system was in specs, 30-50ms ILDA conversion time simultaneously with 30-50ms frame to contour conversion time while another thread also reads from system’s double buffer.
  • Helped debug hardware system via analyzing ILDA format, now have demo ready for monday demonstrating laser image projection
•  Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?
  • On track, though waiting on boards to debug next week.

 

• What deliverables do you hope to complete in the next week?
  • Since I’ll be away for most of next week for interviews, I won’t be able to accomplish as much. 
    • Help debug any other hardware/software integration issues with new combined software pipeline when I return
    • When boards arrive, begin work on assembling them and testing them

Team Status Update

 

• What are the most significant risks that could jeopardize the success of the project? How are these risks being managed? What contingency plans are ready? 

Timing is much less of an issue now that we’ve worked on optimizing our software pipeline some more. Ensuring our safety subsystem works is then our next biggest issue now that we’ve confirmed our hardware is able to render images. We have less time to test this system as board production eats time from our schedule, so we’re preparing to make up for that time by planning in more time to work on the boards once they arrive. DAC-speed was also confirmed to be less of a concern than expected, since we are able to draw more than 12k points per second. 

 

 

Additionally, board errors could be a risk but by choosing relatively large parts for the board, creating jumps and fixes should be easy.

 

• Were any changes made to the existing design of the system (requirements, block diagram, system spec, etc)? Why was this change necessary, what costs does the change incur, and how will these costs be mitigated going forward? 

 

No major changes, some minor optimizations to our software stack.

 

• Provide an updated schedule if changes have occurred.