top of page

Weekly Meetings

Here is a log of activities preformed on a weekly basis with our project sponsor.

Meeting #11 - 04/11/2023

Began - 5:30 pm
Adjourned - 5:54 pm

Discussion:

  • Final report is done updates made 

  • Grammer adjustments in report and presentation 

  • Website verifications and checking 

  • Presentation is in room 11-106

Deliverables

  • CAN Driven to CAN-Driven in report 

  • CAN Driven to CAN-Driven in presentation 

  • CAN Driven to CAN-Driven in website 

  • Visual adjustment to fonts in presentation. Nothing too small. 

  • Slide rearrangement in ppt, problem then solution. 

Meeting #10 - 04/04/2023

Began - 5:38 pm
Adjourned - 6:03 pm

Discussion:

  • Updates on the work 

  • Remove the additional contributions to follow - Done 

  • Thursday 9am to 1pm on the 20th is presentation, 20 minutes long and 10 minutes of questions and answers. 

  • Send an email and copy all students about scheduling for the presentation 

  • Presentation is 20 minutes and 10 minutes of questions. 

  • Just show the table of contents, only a few seconds on that slide. 

  • Slide 6 – discuss more of what is much better about our device than our competition. 

  • 10-15 seconds overview of TOC 

  • Introduction should be thorough 

  • Put down our solution to the problems 

  • Don’t go through each slide word for word, just overview. 

  • Reviewed the first version of the presentation 

Deliverables

  • Setup public planner 

  • Reach out to Dr. Davis for patenting the device 

  • Put the timelines in landscape view for the report 

  •  

  •  

  • Remove last line in acknoledgements. 

  • Reformat subsection headers in report 

  • Prepare senior design order email to all other groups. 

  • Describe current system and solutions, then put down proposed solution to the problem in presentation 

  • Change engineering requirements to be more of an overview in presentation 

  • Final draft of proposal presentation to be done next week. 

Meeting #9 - 03/07/2023

Began - 5:30 pm
Adjourned - 6:00 pm

Discussion:

​

  • Go over report again and make some minor changes. 

  • Reviewed survey results. 

  • Reviewed Proposed Timelines 

Deliverables

  • Fix indentation for references. 

  • Wait till industry feedback comes back to add to acknowledgement. 

  • Just put the timeline, don't have them download it. 

  • Fix dates on the timeline. 

Meeting #8 - 2/28/2023

Began - 5:30 pm
Adjourned - 6:00 pm

Discussion:

​

  •  Go over the proposal report

  • Discuss plans moving forward with the project.

  • Discuss continued meeting schedule after meeting 9 next week.

  • Short meeting

Deliverables

​

  • More grammatical corrections to project report.

  • Adjustment of tables in proposal report.

  • References in [ ] in report.

  • Add timeline to report.

  • Adding in survey results to report and website.

Meeting #7 - 2/23/2023

Began - 5:45 pm
Adjourned - 6:39 pm

Discussion:

​

  •  Go over previous concerns and check over connections. 

  • Future Recommendations if we think it won't get done, but don't have them on the requirements. - Chapter 4. 

  • Upload the PDF version of the word file for review 

  • Words to use "satisfy the specifications"  "Group intends to use. 

  • Use that table format in word instead of the  

  • Always state the ethical aspects of the references used to complete the project 

​

​Deliverables

​

  • Fix engineering requirements "continuity" 

  • Time and effort missing in week 6 for Bryan 

  • Update the power table 

  • "Introduction to the Proposed Project" 

  • Fix the reference missing in chapter 1 for J1939 

  • Fit "requirements and specifications" in to the summary 

  • Clean up the block diagram to make it easier to read 

  • Fix 2.1.3 description of table 

  • Move requirements  before the block diagram  

    • 2.1.1 will be engineering requirements 

    • 2.1.2 will be block diagram 

    • 2.1.3 Engineering specifications 

  • Start 2.2 as "hardware of the project" 

    • 2.2.1 Control Module 

    • 2.2.2 Power Module 

  • Use the number for references not the name. 

  • Incorporate the flowchart with the software following after talking about the hardware. 

  • Flowchart for testing 

  • Update the plastic for the case 

  • Reference for IEEE code 

  • Ethical aspect is to give proper credit for sources that we use. (IEEE)  

  • Should be first draft of final report available 

  • Put the picture of the device in the report 

  • Put survey on website and in chapter 1 

  • Put a link under the design proposal tap to access the survey. 

Meeting #6 - 2/14/2023

Began - 5:42 pm
Adjourned - 6:56 pm

Discussion:

​

  • Review Chapter 1 and start of report

​

  • Details on main page for the

​

  • How to do the update

​

  • Don't use should - use shall

​

  • Survey in Chapter 1

​

  • Chapter 3 is non-technical issues

​

Deliverables:

​

  • Engineering Requirements

    • Remove Data should be transferred wirelessly too.

    • Clean up the GPIO modules

​

  • Order of pages from links -> Ideas, Requirements, Block Diagram, Specifications, Time and Effort, Project Log, Power Budget, Monetary Budget, Weekly Meetings, Project Documents

    • Can do one link to project documents for presentation and report

​

  • Block diagram - fix the font size

​

  • Need to conduct a consumer survey - Put in progress log and report (surveymonkey or qualtracs) put link on website or describe in the survey.

    • What do they think

    • The usefulness

    • What would they like to see

​

  • Revise the block diagram for the screen as only one module

​

  • Represent the whole week instead of just the start of the day

​

  • Explain how many analog and digital inputs are needed in the Specifications document

​

  • Check the power budget and clean up power

​

  • Monetary budget should be for the whole project

​

  • Report should follow the template - Make sure table header is same as template

​

  • Keep the TOF and TOT to same format

​

  • Clarify the time stamp of how the frames are stored

​

  • Engineering Requirements in chapter 2

​

  • End of chapter 1 we explain what the reader will see in the rest of the report…

​

  • Clean up Chapter 1 and work on chapter 2

​

Meeting #5 - 2/7/2023

Began - 5:42 pm
Adjourned - 6:21 pm

Discussion:

​

  • J1939 - talk about the database.

​

  • How would it work for beep

​

  • Need to be very specific in requirements for the databases that we will utilized

​

  • Need more specifics on the conversion from

​

  • Add option as a future recommendation if it is not able to be implemented - Chapter 4

​

  • Chapter 1 introduction and similar projects.

​

  • Chapter #1 will get the background information about the CAN Bus in proposal.  What is available and what is going to be considered.

​

  • There is an IEEE code of ethics that must be followed and referenced.

​

  • Reference any of the codes that apply IEEE - IEEE Code of Ethics

​

  • Talk to Dr. Davis about patents

Deliverables:

​

  • Address how we measure to make sure there is no overflow for the data coming in.

​

  • Clearly mention the device shall utilize which database shall be decoded, how to test that - J1939 and a Custom Database.

​

  • Clear up add on modules in the engineering requirement page and the GPIO (what does it mean)

​

  • Verification and success how will we measure using trials to test a requirement, operate 20 trials with two different CAN speeds and data processes for those specific requirements.

​

  • Put down at least on the topics instead of specific amount

​

  • Put down just a touchscreen for display module fix on the Block Diagram

​

  • Clean up the flowchart to match the block diagram

​

  • Clean up time and effort to fix Week #3 for Jan, 30 to Week #4

​

  • Fix the similar projects and put the pdf version in with the clickable links

​

  • Work on first chapter of the report for next week.

​

  • Create a separate monetary budget

​

  • Show the CAD model with the measurements and what we need.

Meeting #4 - 1/31/2023

Began - 5:27 pm
Adjourned - 6:04 pm

Discussion:

​

  • Interpreting the data?  What does that mean to interpret the data can - show example

​

  • Other devices how do they work that this is different

​

  • Interested in patenting the device?

​

  • Specify heavy duty vehicles.

​

  • Block name change from microcontroller to control module, display module and GPIO module.

​

  • Checked engineering specifications over and need to adjust for less specific

​

  • Connect power supply with vehicle

​

  • Group time is only our time working on the project together including meetings

​

  •  Can setup a blog format for progress log and use the information in the information in the report so be specific! - Look at Neil and Jacob page.

​

  • Make battery removeable to there is no need to make a charge circuit

​

  • Project approved

​

  • Need to be very clear of what we are proposing from the beginning of the report

​

  • Industry experts will check the website over

Deliverables:

​

  • Fix what we mean by interpreting the data on the primary page

​

  • Be more descriptive on what the GPIO means

​

  • Write down each success for each requirement on the engineering requirements page.

​

  • Move microcontroller into the component level and then the microcontroller and what the requirements are. Also need to justify why those specifications are needed, using the bare minimum specs for this.

​

  • Clean up block diagram to show module level components such as WiFi and power supply

​

  • Progress log (for each person) is for each one of us and group - remove the sponsor on the meetings tab.

​

  • Use minutes of meeting to cover time with Dr. Ejaz

​

  • Put market comparison into progress log and clean up.

    • Need picture of all the devices on the comparison

​

  • Need to start writing the report and all CAD should have dimensions - Use template!

​

  • References link - ieee

Meeting #3 - 1/24/2023

Began - 5:30 pm
Adjourned - 6:02 pm

Discussion:

​

  • Move cost analysis to "Project Ideas" tab for each proposal.

​

  • Proposed Smart Pet Feeder - similar project done so not viable at this time for a 3rd project idea.

​

  • Focus on proposal #1

    • How is it different - emphasis on this​

Deliverables:

​

  • Update main page abstract for proposal #1

​

  • Create Engineering specification table.

​

  • Find more similar products for comparison.

​

  • Create Engineering requirements.

​

  • Create power budget - including battery.

​

  • Clean up the monetary budget.

​

  • What needs to be done for project and how long will it take.

Meeting #2 - 1/17/2023

Began - 5:38pm
Adjourned - 6:17pm

Discussion:

​

  • Current progress on the website.

​

  • Project 1:

    • This project is a bridge between a basic telematics system and a simple datalogger.

    • Could be used for automotive cars as well, just need to accommodate the different CAN networks.

​

  • Project 2:

    • Aims to balance each room in concert with thermostat.

    • Talked about how we balance each room using pressure and temperature.

    • There was a similar project in spring 2019 called “Sensible Flow System”

      • Need to see what the difference is between our system and their setup.

      • Do a comparison chart between the two.

​

  • Project 3:

    • Use Lidar to do automated vehicle inspections.

    • Full 360 terrestrial scanner is very expensive.

    • Trying to address cost concern is using simpler lidar sensors with small distance measurements.

    • Intend to reduce training by having the scanners preset in a grid pattern.

    • Software can do most of the controls and the user only need to push a button when vehicle is in place.

    • How to handle the roof on taller vehicles

    • What would be the cost of this system – need a cost analysis.  Keep the total cost of the project lower even if the items are provided for free from a vendor for testing purposed.

​

  • Second project has a good potential for project and a prototype.

Deliverables:

​

  • Project 1 - Do a comparison of CAN system and one done in advanced programming class to show the difference.

​

  • Project 2 – Review the previous project and do a comparison of the differences between the two.

​

  • Do some cost analysis for both projects.

​

  • Look for a 3rd project to use and discuss next week.

    • Project 3 does not have potential for this class.

​
 

Meeting #1 - 1/12/2023

Began - 10:00am
Adjourned -

Discussions:

  • Sylabus

  • Layout of program

  • Example past projects discussed

  • Setup meeting time with Dr. Ejaz

Deliverables:

  • Work on 3 project proposals for first meeting

  • Build website

Senior Design Project - 2023

bottom of page