GROUP MEETING MINUTES
MINUTES FROM MEETING WITH GROUP MEMBERS and advisor
Start 5:30pm
-Semester expectations
-Example project minutes(Essie)
-Project rubric
       Implementation grade is solely off industry professionals
-Syllabus review
-Project touch-base
       Update landing page(match Convey IQ)
       Update following tabs:
       Redefine requirements and separate from implementation
       Redefine block diagrams
       Keep detailed progress log
       Track codes and standards and citations as we work on them
-Conduct survey
End 7:10pm
Start: 6:30 pm
Professor reviewed everyone’s websites and suggested updates across the board to everyone’s website from the proposal class.
Progress log page:
->should provide updates, can add pictures and video
  Ex: put in the cadd models
Update the following pages to match everything else:
1. Financial budget page
2. Proposal Ideas
3. Preliminary drawings
4. Survey page(*was messed up due to AI on wix*)
5. Proposal Testing and result fix the header
6. Proposal final report and presentation
7. CADD drawings
8. Code and standard
Progress log- get rid of the link on top and put it in Project tab
Scale back project to only 1 joint:
 ->not enough time for 2 joints, only need 1 to prove the point
 ->only use wrist joint
 ->make it a grabbing mechanism
Documents:
 ->create document on why we are not using NFC and Qi charging
       ->discuss this during presentation at end oof semester
Specifications:
 ->Update components that are going to be used in the project
 ->upload spec sheets of components
 ->description of specifications
Block Diagram:
 ->update to be for each component
Task clear up:
 ->describe week, group contribution, and individual contributions
end: 7:26pm
Start 8:02 pm
reviewed last week notes
   -block diagram needs update
       -Control block diagram is just the raspberry pi and HMI system
       -Create electrochemical module
   -Engineering Specifications needs update
       -Component detail->make descriptions more vague, not exact components. ex: 5Vpower supply not puls 5v-120vdcxxxxx
   -Project TimelineÂ
      -needs to be its own page, include an updated gnatt chart and weekly timeline
   -Progress log
      -Text log of individual contributions, not pictures. pictures help to enforce what progress was made
   -Engineering requirements
      -get rid of first one: "The system Shall be able to swap components in under five minutes"
      -Combine these into 1 requirement
​       "The system shall have Individual functional modules that can be replaced by pre-assembled unit for maximum efficiency.
​       " The system shall disengage the modules via a button press"
      -Keep:
      "The system shall have Integrated safety mechanisms prevent mechanical collapse if electrical supply is severed."
      -get rid of smart goals and convert that into a timeline on Project timeline page
     -engineering requirements should be in the form of a table.
     -simplify requirements:
         What it does
         Safety mechanism
Main Project:
  -Make 1 joint, with it disconnecting and reconnecting it proves the projects purpose. no need for multiple joints
Goals for this week:
   Troy:
     Work on finishing ki-cadd PCB board
     Assemble components that have arrived
     HMI hook up with the raspberry pi
   Michael:
     Work on updated CADD drawing to see limitations that might occur with housing print
   Group
      Both work on programming of the entire project
End 8:39pm
Start: 5:30 pm
Notes for the website:
In group meeting tab add 9/1/26
Weekly timeline
  ->be more specific for task to complete
  ->example Esse
Gannt Chart
  ->add the report preparation, and presentation preparation and delivery
Progress log
  ->edit progress log to have week dateÂ
  ->suppose to be an explanation of what's on the time and effect table
  ->Add deception of what CADD drawings are forÂ
  ->be more specific with progress logs
  ->Add in any troubleshooting processes
Time and effort table
  ->split from proposal
Codes and standards
  -> mention relevance to project and why that code applies
  ->add Canbus code and standards
Engineering Requirements
  ->clean up requirement 1,remove "without worrying"
  ->requirement 1 should be the main operational requirement
  ->only have requirements that apply to our system
  ->more specific on requirements no emotions
  ->change one of the requirements to state "disengage module power and communication connection with the press of a button
  ->change one of the requirements to state "under normal operation it should not detach"
  ->figure out how to prove its not going to disconnect while moving
Can use Chatgpt to help clean up Website
Home page
  ->rewrite to clean up as it was changed by AI
Block Diagram
  ->4 modules in the system:control,electro-mechnical, power, mechnical
Engineering Specification
  ->Don't repeat labels on the left side
  ->Don't use wix to create the table, create in excel
  ->Don't put the exact component name put specification
​
​
Start: 6:30 pm
Website Updates:
Weekly Timeline:
  ->Should be contributions of each member
  ->Create timeline to be weekly, not the whole month. Specify jobs to be done per week
  ->Example Esie
Home brew example for engineering requirements
Progress Log->latest should be on the top
Engineering requirements:
  ->1rst requirement is still too vague, define what the module is, aka "wrist"
  ->4th requirement, add in wording "for system integrity"
  ->2nd requirement is good
  ->rewrite requirements to only apply to actual project, not future items
    ex:'have a grabber wrist that can be removed and replaced without "screws"
    ex:'HMI to engage and disengage
Component details:
  ->separate hardware and components
     hardware: 3D print, strut
     Components: motor, gearbox, electromagnet
Home page:
  ->add CADD drawings
  -> add phrase about no 'existing solutions'
Time and effort table
  ->update for Michael time and effort
Talked about deliverables and past work
  ->Troy:HMI box, PCB
  ->Michael: 3D print, hardware for HMI box, Website
end: 7:26pm
Start 5:32 PM
Reviewed website:
  -timeline doesn't change->its an established timeline done during senior proposal
     variations are mentioned in time and effort table or progress log
  -Weekly timeline
     -add individual tasks per person
     -Repeat per week if task take longer then one week
  -Engineering requirement
     -Still need to rework, should be along the lines of 'Shall have a base connected to a wrist that with the push of       a button can be replaced
    -The system requirements should only be for our project scope
    -update requirements and concentrate on the wrist aspect
  -Block diagrams
    -Update Motor controller 1 to Motor controller 2
  -Engineering Specifications
    -Specifications should be minimal not exact, ex: microcontroller with 12 outputs, instead of Ardunio exact          specs
    -Change hardware module to match block diagrams
       -electro-mechanical module
       -hardware module should just have hardware
  -Group task
    -distribution of task
  -Survey-asked if we did it
    -No, but we did receive feedback in design elements of our project, this will be written up during the final            report
End 7:00pm
​
Start 6:00 pm
Reviewed Website:
  -Timeline->discussed how it has changed from original to realistic
Withdrawal deadline is Oct 30th
  -Progress log:
     -Spell check
  -System requirements
     -grammar and spell check
     -remove the "system shall" from the top.
     -minor rework and update requirements
     -4th condition, update to include what conditions it won’t collapse in
  -Engineering specifications
    -add in @ least or no more than for the specific requirements
    -update HMI to include specifications
    -electromagnet holding force
  -Block diagram
    -review Essie, create an overall block diagram for whole system
​
Troy goals: program HMI, solder PCB
Michael goals: wire fixture, make base
end 6:30PM