1.13.2020 - 2:00 PM
Met with prof. Notash in office quickly to discuss meeting times, and project ideas
1.16.2020 - 12:00 PM
Large group meeting with prof. Notash, discussed expectations, grading, and project ideas.
Scheduled regular meeting time for Tuesdays at 12:30 PM.
Will make flow charts and engineering requirements for at least 3 ideas to be reviewed at the next meeting.
1.21.2020 - 12:30 PM
Reviewed several ideas, most had been done before, but the possibility of expanding the idea or different approaches when discussed for each: Smart Helmet, Pool Treatment system, Smart Sprinkler.
Ideas that had some interest were the Visual-aid Vest, and the Backpack computing system. The merging of the two ideas was discussed also. Various applications IR camera for night vision, in addition to visual aid application.
Takeaway: We like the idea of the backpack computer a lot. And believe we can design a system that has a lot of great basic functionality by incorporating HUD glasses, a headset microphone with earpiece(headphone) and then a touch navigation button. If we can build a viable system that is user friendly that can improve productivity (replace phone functionality) and offer greater computing power with great mobility.
1.28.2020 - 3:30 PM
We discussed the MC Pack idea at length, and the idea was approved at the conclusion of the meeting.

We are focusing on the basic functions of the computer with the use of the cameras, HUD glasses and finger sleeve peripherals. If we can accomplish that then other applications, features, or peripherals can be explored ( prof. Notash had idea of optical image keyboard / Kevin had an idea about a possible AR keyboard.)

Things needed to do for the next meeting: Getting everything organized for the project, finalizing design ideas (laptop analog vs built in display/ wireless keyboard)(how are we going to do it)Start Documents: Engineering Requirement, Time and Effort,  Proposed Timeline,  Proposed Budget,documentation that details who is responsible for what duties may be needed.
2.4.2020 - 11:45 AM
We discussed some product name ideas. We feel we are creating and developing a new type of device and experience, akin to the smartphone, or going back further the laptop. Therefore we aren’t overly worried about a name for the individual product. We are thinking bigger picture, and the device family name, which is more a description of the device rather than the various products and variations that this system can be adapted for. (System adaptation with unique peripherals were discussed for various professions.)
The secondary display device was also considered. Cutting edge technology like a foldable screen would be more likely a future development / innovation. Some research was done in the meeting. Cost and expected budget is beginning to be a factor going forward on what we are able to do. Cutting edge tech is expensive, and the cost effective older components don’t highlight innovation and next generation computing.
The methods we choose to accomplish the individual objectives is the main focus. The finger sleeve is still under discussion, other ideas have been mentioned that maybe be easier, reduce components, but also future looking solutions have been discussed too if we have unlimited time and resources. We like the idea of using and dismantling a laptop to get a lot of the components needed, although we won’t know exactly what is needed until we are in the process.
Communication methods were talked about for data out to glasses peripheral. Optical link was suggested by Professor Notash. Some focus was put on the ease of connection for consumer ease of use.
2.11.2020- 11:45 AM

Started meeting talking about a new solution for the navigation peripheral, and the latest idea is a key FOB looking device, and it would be the typical size so it could fit on your key ring or it can be clipped to any easy accessible place.The beetle microcontroller would fit easily and we have more than enough pins so we talked of added functionality like a volume control (+/-buttons) Other additional functionality discussed was a simple LED flashlight which is right in line with the agenda to replace the cellphone and its extra features.
The Power Blocks were discussed and the idea of building our own is the only way to get long ampere hours we will need for the system to run a full 8 hours. The weight of batteries will be an issue and needs to be explored more, and we may lose our ease of mobility if it’s too heavy.
We talked about contacting TSA to find out what they would do if they encountered a system like this. Mobility and Travel are very important to the device’s usefulness and it could be beneficial to get a TSA Approved certificate. Battery sizes could have limitations. Customs and border patrol for Cruise ships may have different guidelines than TSA.
We talked about how and why this is different and better than a laptop. That led to another interesting idea brought up by Prof Notash to make a normal laptop able to be integrated into our system. We liked this idea very much, and planned to explore it to discuss more in the next meeting.
2.18.2020- 11:45 AM

The meeting started with us discussing the latest changes/ updates to the project. It has been decided that to make the project more inclusive we are going to make the mobile computing bag interface to any laptop that is running windows OS. We think that this will solve a couple of additional things we want to accomplish, like having a secondary display to use and we no longer need to do a laptop analog. The handheld controller has also changed a little bit too, and we also talked about ways to lock-out the glasses with a fingerprint detection device.We also talked about making the headset wireless again, the advantages it would have, how difficult it might be, some security concerns.
We will not have a meeting for two weeks, and we are to move forward with the engineering requirements and writing the report. We are to make a power budget, and analyze the different power supplies we will need for the project.
3.3.2020- 11:45 AM

We started the meeting discussing some changes we wanted to make with Professor Notash. The first major change was to make the HUD completely wireless, and place another micro controller in the HUD assembly for some advanced video applications, doing this will prevent us from having to send the video from the camera to the laptop for processing and back to the HUD assembly for display. 
The next major change we discussed was to eliminate the actual lenses and glasses frame since the function of these was to serve as a mount, and just the frame was needed for the Vufine. The Vufine doesn't project onto the lenses of the glasses, the Vufine is best described as a veiwfinder you might see on point and shoot camera oran older type of video camera. Our desicion also stems from the fact that not everybody wants to wear glasses with prescriptionless lenses when they don't have to, and or having to mount the HUD on a pair of prescription glasses seems like it could be problematic. Therefore we would mount the Vufine/HUD assembly on the bluetooth headset and microphone we will be using.
We then examined the Vufine device since it was recently purchased and received. This is a great device for the 200 dollar price tag, but of all the HUD glasses option to purchase this was the entry level device. It is easy to imagine what improvements the 2000 dollar level devices are capable of, and the different methods used to either project or display images. A detailed blog post regarding the research done on the current state and option of HUD device and Virtual/Augmented reality might be in order to rationalize our decision for the Vufine device . Seeing it for the first time was a little anticlimactic for Professor Notash as he had some concerns about how small the display actually is, making reading text sized for a laptop display difficult to read, and the ease of usage of the device. Changing the resolution on the laptop did make text more readable, but like a phone or tablet larger fonts and small display friendly formatting is needed, akin to the GUI we had in mind, (swiping through application, radial menus for application selection)  He suggested we magnify the display in some way, to make it about a square inch, since as it is now it is about a square centimeter. Some discussions were had on how to enlarge the display, with optics and lenses, with software. Making our own HUD display was also discussed, we looked at OLED displays, and options on how we might make it look presentable with a small form factor.Details about the engineering requirements were discussed, and some updates need to be reflected asap, our engineering specifications need to be revamped as well. Power budget also needs to be more involved and include every aspect, and the minimum value for any ranges needed. This was a great meeting and a lot was accomplished.
3.17.2020 - 11:45am
No official meeting took place with Prof Notash, our supervisor. Although a telephone meeting was had between group memebers to discuss, recent changes and the plan of action going forward during this time period. Just a minor set-back. We will continue to report our progress with a weekly email.
3.24.2020
Due to the spread Covid-19, all in-person meetings were cancelled.
5.7.2020




5.10.2020
Prof. Notash send an email welcoming the team to the Senior Design course. Online meeting options were presented and the new syllabus was made available. Prof. Notash also identified differences between this course and the proposal course for the report requirements.


Group Communication regarding purchasing components, discussed what parts should be bought as soon as possible and what could wait for another order. Kevin shared researched links for possible purchase.
5.20.2020 - 5.21.2020
There was communication via email with Prof. Cara about creating a circuit that will allow all components of the headset to be switched on at the same time. This process would be triggered by detecting if there is a current flow between the trigger device  (Vufine board) and the power source.
The first methods discussed to achieve this involved the use of an optocoupler. The trigger device would have a ouptocoupler in series with it and when the trigger device turns on, the current flow would trigger the normally-open optocoupler to close, allowing the other devices to turn on.
The second method discussed involved the use of an op-amp to detect the small voltage drop across a sensor resistor that is in series with the trigger device. When the device is turned on, the differential op-amp would amplify the small voltage drop across the sensor resistor enough to bias the base terminal of a transistor. The other devices would then be pulled to ground by being connected to the collector of this transistor.
Component requirements were then discussed for both methods and specific components were suggested by Prof. Cara. The importance of testing the circuit design before applying them to the more expensive components was also stressed by Prof. Cara.
5.22.2020
There was correspondence between team members about the correct use of an op-amp. Text concerning the use of op-amps were shared between team members.
Sent an email to Prof. Notash updating him on the progress of the project. Each team member’s status for their respective responsibilities was shared with Prof. Notash.

Marty:
Main focus has been the cooling system and module. All parts needed have been received except the Beetle micro controller and I have researched examples, and various circuits. Currently coding (troubleshooting) the thermistor input (on another microcontroller for now), then will move on to coding the fan speed output based on the temperature reading. Building the circuit and testing should be completed by the end of next week, earlier next week. Then will work on installing the system inside of a “cheaper test bag” to see what problem might be encountered there. As I have been working on the above I have also started to test the individual components. USB Camera is working, and I have coded an image capture, and a video capture. Other researching has been taking place as well. I made myself familiar with the feather and beetle microcontrollers that I will be using. Also getting aquintanted with the capacitive touch sensor, how to wire, and program. After the cooling module is completed I will be moving on to the much more difficult task of the controller module. So I’m hoping to start on this by end of next week by getting the feather and touch sensor working together.

Kevin:
My main focus up to this point has been to get the headset done. I should be able to have everything done by mid June. This includes the 3D printed case. Currently, all the components are stripped down to their boards and are being externally powered. I had already tested them to know that they are communicating as expected. So the main thing I am currently working on is powering them all via a rechargeable battery. The next hurdle that I have to overcome is turning on all the components with one button press.Concerning the programming, I've bushed up on the libraries that I have to use. I'm focusing on the headset first because I can "rush" the coding towards the end if needed, but i cannot do that with physical components that I may need to order.
5.28.2020
Team members had conversation about coordinating updates to the website. Progress on the project report was also discussed.
There was communication via email to setup a meeting between the team and Prof. Notash for the following day.
5.29.2020
The online meeting with Prof. Notash covered four aspects ofthe project: current progress, future plans, troubleshooting problems and progressdocumentation.The team members shared their current progress on theproject. The focus for the first part of the development focused on the bag and the headset. The issue of turning on all the components of the headset with a singular user input was covered. Parts needed for the backpack were delayed, but the current progress on the cooling system was shared. The microcontroller for the cooling system was accurately measuring the temperature values. Kevin shared his plans going forward to complete the headset within two weeks. This would involve getting a 3D printer to produce the housing for the device and completing the switching circuit. Martin also planned to have the backpack system completed within that timeframe because the ordered parts would be delivered by then. Prof. Notash also suggested looking into patenting and publishing the idea. There was a question concerning measuring the internal resistance of a PCB. An effort was made to discern the test points on the Vufineboard that would allow for the measurements to be obtained. There was also an attempt to find any online technical information on the Vufine. No sources werefound, and Prof. Notash suggested contacting the manufacturer directly to ascertainthe relevant information. Prof. Notash shared concerns with the website design, the meeting minutes section of the website, and an updated version of the budget. The two versions of the website were deemed to be unwieldly, so consolidating the information into one website while keeping a similar format was suggested.The meeting minutes section was empty up to this point because it waspreviously used, in the proposal section, to record in-person meetings betweenthe team and the supervisor. Prof. Notash suggested expanding the entry criteria to include various conversations between team members and other relevant persons. Prof. Notash suggested that there be two budgets, one that memorializes the proposed budget, and another that tracks the current budget for the design phase.Team members had a conversation about workarounds for thelack of access to tools usually available via Valencia’s facilities.
6.10.2020
Zoom meeting with Professor Notash on Wednesday June, 10th. Meeting was originally schedule for Monday the 8th, but due to delays in parts (Power Transistor) and schedule changes the meeting was moved to Wednesday at 2pm.

Martin reported that the cooling module is mostly complete, but it has been made using PWM to control the fan speed instead of the intended MOSFET circuit that would vary the voltage to control fan speed. Also reported the Beetle microcontroller is having communicating problems, the system is modeled on an Arduino Mega2560 board at the momment.
6.12.2020
Martin has sent an email requesting the usage of some lab equipment at home. The email and response are as follows.

Good Afternoon,
As a student currently participating in the Senior Design course, and currently building their project.I would like to explore the possibility of borrowing Valencia's BSECET lab equipment for usage at home.

I know it may be late in the process to be requesting something like this amidst the COVID-19 closures and
procedures in place at the moment. I am just now realizing it would be a great convenience to have continual
and easy access to an oscilloscope, and a power supply for general troubleshooting as it happens, and data collection.

I am not currently needed any equipment to proceed, at the moment, so this is not an urgent matter. It would just
be really great to have instant access to real equipment we are familiar with to easily examine our systems. The little conveniences like have a nice multi-meter with alligator clips would be nice. Also thinking about possible future troubleshooting needs, and if monitoring all of our Bluetooth signals with a spectrum analyzer may be a useful tool, and provide useful data to report.

I know safety may be a concern with equipment usage, especially since I am asking to take the pieces home. So I would be
happy to sign any agreement that would release the school from liability, and make me responsible for any damages.

Thank you for your time,Martin MacNeill and The Leitch-MacNeill Design Team

I wanted to cc: Will from the open lab on this but couldn't locate his email.
---------------------------

Martin,
Will is copied who can help you out with your request.
-----------------------------
Hello Marty,
Thank you for letting us know of your group's needs.  There should not be any problems to check out the needed equipment.  Please work with Will (included in this reply) to coordinates any access requirements to the labs or use of.

Best,​
Prof. Notash
----------------------------------
A follow up email to Will may be needed - mm 6/23/2020
6.14.2020
Communication between group members regarding website updating. We discussed to need make a push for more in depth project details on the website, and knowing the report is due in a month, and presentations on 7.20.20

Team members had a discussion on how to proceed with Beetle Microcontroller. Martin has found very little documentation on the microcontroller and how to troubleshoot the connection issues and the only troubleshooting technique discribe in the official literature do indeed admit the timing of reseting and being able to upload code is in the microseconds. It was decided to not waste anymore time on the beetle and a Arduino Nano has been selected to replace the Beetle in the Cooling Assembly.
6.23.2020
Progress meeting may be needed soon. It is getting to the point where the Team member may need to meet up in person for bag installations decisions.

Some options like battery placement, cable management, micro-controller installation position, fan position can all have an affect on the overall system performance. Group will need to meet to 3D print controller case, and External Hub 3D printing.
6.28.2020
Group Meeting:
Discussed finishing details for the camera mount, the need for an additional 3D print for the camera. The camera will then will mounted by velcro to the desire location. Multiple velcro attachment areas may be possible for many options.

Talked about controller progress, and the set back with feather MC being damaged. Marty has reordered the device but it might not arrive in time. Ideas on 3D printing/ PCB and general assembly were discussed, and the design was modified to excluded the side buttons.

7.5.2020
Group Communication via Texts
Since controller progress has been stalled Kevin has offered to take over the controller to finish it up. This will allow Marty to focus on the data collection, the report and general documentation that will be due very quickly.

Also due to the controller assembly not on schedule the competition of the finger print scanner is in question. It has been decided that the fingerprint device will be left out of the 3D printed controller design. If there is time the fingerprint scanner can be added to the still on breadboard prototype phase controller since we will have an additional feather MC board to work on.

Kevin will email Professor Notash to inform and update.
7.13.2020
Zoom Meeting with Professor Notash scheduled for 1pm on Monday 7.13.2020.
The controller was talked about at length, and it was brought to the attention of Prof Notash that the size of the current controller design is larger than expected. The dimensions are 88mm by 57mm and it is a concern that it is not quite the keyfob design proposed, and more like a remote controller. Some ideas were discussed to reduce the size of the controller. Prof Notash had an excellent idea to change our physical button design to a touch screen device, and it was well received by all, and plans to change the design have begun.

The plan for the camera was discussed and shown. Velcro will beinstall on Friday during the group meeting we have planned.

The backpack and cooling system were discussed, and the fan installation was shared. Progress needs to be made on the testing, validation, and evaluation of cooling system.

It was also talked about the projects progress and the time schedule. We are running behind, and we feel like we could rush and get everything done, documented in time. But if we are to make changes to a major design choice like physical buttons and ajoystick to all touch screen navigation more time will be needed. More time would also allow for better testing of the systems all working together, benefiting the documentation and reporting, and overall presentation. As it is right now we would be integrating all systems and testing on Friday 7.17.20 trying to get it all in the report by Monday 7.20.20. A decision on a time extension will be made by Wednesday 7.15.2020.
7.15.2020
Emailing with Professor Notash:
A decision on a time extension will be made by Wednesday 7.15.2020.
7.17.2020
Group Meeting planned for installation and testing.