Project Journal for Rohit Lala
=============== Week 13: =================
Entry 6: -----------------------------------------------------------------
Date: April 11thStart Time: 4:45pm
Duration: 1 hour
Dear journal, this will be my last entry for a while until I am held back from graduation and have to repeat this course. Oh journal how I love thee, with thine beautful font and oversized images. Doing participation quiz:
Also doing the last divine project journal entry updates and summary ;(. I worked on this using my tears which are all over my keybaord now and shorting out my laptop. The result was a horrible project journal that next year's top students should be allowed to print out and burn out of rage. From this experience i have learned that ai could probably have saved me a lot of time writing this semester, but then this journal would actually be coherent, and I can't give my replacement too easy of a time. This contributes to the project as now if anyone stumbles upon this journal they can read this top entry and know to immediately close the tab and delete their browsing history. The next steps are to get some sleep.
Entry 6: -----------------------------------------------------------------
Date: April 11thStart Time: 6:45am
Duration: 2.25 hours
doing live demo. made this to help explain battery adc values:
updated it a little to make things even clearer:
We finished, with 104.5%!! We worked on this using the lab space. The result was a completed project. I learned how to finish the project. This contributes to the project as we now have a completed project. The next steps are to finish the project even harder.
Entry 5: -----------------------------------------------------------------
Date: April 10thStart Time: 3:10pm
Duration: 1.25 hours
Team has finished everything for final demo. Now I'm just wrapping up the third board soldering and we’ll test. nevermind, second board is still missing battery adc v divider & third board is missing capacitors on the back. ill finish those up now. Finished up entirety of second board and majority of third board. Had to run to ece shop to get 10uF C for C1 & C5 Next steps: add c1 & c5 to third board, then it should be ready for testing
Entry 4: -----------------------------------------------------------------
Date: April 9thStart Time: 3:10pm
Duration: 2.25 hours
show me a thing for manlab: both new boards. continuing to solder both boards during manlab. Finished one board
Also very very close to finished a second:
I worked on this using a soldering station. The result was a completed board. I learned how to solder a pcb. This contributes to the project as we now have a completed board. The next steps are to finish soldering the rest of the othe rboard.
Entry 3: -----------------------------------------------------------------
Date: April 8thStart Time: 9:25pm
Duration: 1.5 hour
Soldering the rest of Alfredo’s pcb. Soldered v reg and barrel jack
Did part of back too:
I worked on this using a soldering station. The result was a more soldred pcb. I learned how to solder a pcb. This contributes to the project as we now have a more soldered pcb. Next step I will finish soldering both boards tomorrow
Entry 2: -----------------------------------------------------------------
Date: April 8thStart Time: 8:30pm
Duration: 0.5 hour
Meeting up with team to go over progress. They decided to cut the stencil down and are hot plating. Seems like old board is working again now as well. Helped Alfredo hot plate second board. I'll wrap it up tomorrow while emery finishes packaging and I finish soldering the back.
I worked on this using the hot plate. The result was a hot plated board. I learned how to monitor alfredo using the hot plate. This contributes to the project as we now have a hot plated board. The next steps are to finish soldering the back of the board.
Entry 1: -----------------------------------------------------------------
Date: April 8thStart Time: 5:15pm
Duration: 1.25 hours
Meeting with team to finalize everything this week in time for 2% extra bonus.Unfortunately our board broke. Ben adn Emery trying to repair it while me and fredo figure out how to use hot plate to make new copies.one issue - no 0805 22uF caps left. marked stencil. Marked boxes w unit name. . note that we doing it without fluxx.
I worked on this using the soldering station. The result was a further soldered pcb. I learned how to solder a pcb. This contributes to the project as we now have a further soldered pcb. The next steps are to finish soldering the rest of the components.
=============== Week 12: =================
Entry 7: -----------------------------------------------------------------
Date: April 4thStart Time: 4:20pm
Duration: 4 hours
Meeting with team to fix adc. flashing code from manlab. it works!!
This doesn't count for our prelim psdr bc we have to have it plugged in to see serial monitor. trying to plug in oled without crimping and running ben’s code. nevermind we have to crimp it. Battery monitor as a task will cause issues, need to convert to an interrupt based system:
Working on a10 while that happens. Got our last prelim psdr checked off! Flashed ben’s code as well on final hardware. finished power circuit femca:
Finished participation quiz as well. finished a10 as well:
Spent time updating this journal as well. I worked on this using word. The result was a completed journal entry for this week. I learned how to finish a10 as well. This contributes to the project as the project journal is up to date and im tested on this weeks lecture contents. The next steps are to meet next week and finalize the project.
Entry 6: -----------------------------------------------------------------
Date: April 4thStart Time: 11:20am
Duration: 1.75 hours
Doing team availability survey. Working on a10. finished reliabiltioty analysis
Inserted all subsystems. almost finished subsystem a femca analysis:
I worked on this with word. The result was a completed section of a10. I learned how to do the reliability analysis. This contributes to the project as we now have a completed section of a10. The next steps are to finish a10.
Entry 5: -----------------------------------------------------------------
Date: April 3rdStart Time: 4:20pm
Duration: 1 hour
working on a10 during lecture as topics on there come up. got voltage regulator section done:
I worked on this using word. The result was a completed section of a10. I learned how to do the voltage regulator section. This contributes to the project as we now have a completed section of a10. The next steps are to finish a10.
Entry 4: -----------------------------------------------------------------
Date: April 2ndStart Time: 7:05pm
Duration: 2.15 hours
working on a10. reviewing slides from class. slides that seem important for a10:
Finished Microcontroller portion after looking at both examples, reading article, and handbook:
I wokred on this using microsoft word. The result was ak started a10. I learned how to do reliabilty analysis. This contributes to the project as we now have a started a10. The next steps are to finish a10.
Entry 3: -----------------------------------------------------------------
Date: April 2ndStart Time: 3:20pm
Duration: 3 hours
manlab show me a thing: fully soldered board
Working on finalizing button menu:
but we're only displaying one language output, so may be more ussr friendly to have our original control scheme, but change output language button to input lagnugage button. Need to work on integrating button, oled, battery indicator code: got this made, just combines our test main with emery's button code.:
It works on final hardware!! Also started A10 while emery resoldered the broken adc v divider. Emery and Fredo able to get two psdrs checked off: embedded micropjhpne transfer & transmit and receive packets via wifi. We worked on this using vs code and esp idf. The result was a better state of code. I learned how to integrate code. This contributes to the project as we now have a better state of code. Next step: get oled checked off with the example code above. Everything works now on final hardware, we just need to integrate to one main function.
Entry 2: -----------------------------------------------------------------
Date: March 31stStart Time: 4:20pm
Duration: 1.25 hours
emery got esp32 soldered on. doing checks before flashing. looks good. now soldering ferrite beads. next esd protection chip and usb esd protection. now usb connection and boot buttons. Will run a serial monitor hello world program, then debug led program, then battery monitor program. Was not able to flash the esp32. We can try the flash logic method next time, or debug what isn't soldered correctly. Realized esp32 wasn't grounded on the back of pcb. Worked ont his using soldering station. The result was a partially soldered pcb. I learned how to solder more componbenet. This contributes to the project as we now have a mor soldered pcb. The next steps are to finish soldering the rest of the components.
Entry 1: -----------------------------------------------------------------
Date: March 30thStart Time: 1:00pm
Duration: 3 hours
meeting w emery for soldering. looks like buck wasnt working bc power led was on the wrong way. Emery will try debugging this will I solder up a 3rd board for the sake of time. we got both originals desoldered. The first one was still working, but second got cooked for some reason. soldered first to the most built up circuit, and rathceted up the power. green led was on the whole way up to 9v. Works with battery pack as well. undetermined what the issue was, i suspect green led backwards or open circuit.
soldered micro decoupling caps, now doing uart bridge. finished half of caps and resistors on front. Worked on this using soldering station. The result was a partially finsihed pcb soldered. I learned how to solder. This contributes to the project as we now have a partially soldered pcb. The next steps are to finish soldering the rest of the components.
=============== Week 11: =================
Entry 4: -----------------------------------------------------------------
Date: March 28thStart Time: 11:30am
Duration: 0.5 hours
participation quiz:
spent some time updating this journal as i do weekly. I worked on this using my computer. The result was a completed journal entry for this week. I learned how to update a journal. This contributes to the project as the project journal is up to date and im tested on this weeks lecture contents. The next steps are to meet ermey in lab this weekend for more osldering.
Entry 3: -----------------------------------------------------------------
Date: March 27thStart Time: 5:20pm
Duration: 2.5 hours
soldering pracgtice workshop. emery and i doing all resistors and capacitors in the back wuickly
We decided to replace r1 and r2 v divider (22.1k 47.5k) w/ 22k and 47k for ease of availability. emery and i soldered and desoldered the old small uart bridge to the practice boards. we soldered the green indicator led and got to testing. seems like buck is now no longer working with v divider. We worked on this using the soldering iron in the lab. The result was a non working buck converter. I learned how to break a working pcb. This contributes to the project as we now have a non working buck on our pcb. Next step: desolder buck and test if it died
Entry 2: -----------------------------------------------------------------
Date: March 26thStart Time: 2:40pm
Duration: 2.75 hours
Discussing with Alfredo about power regulator position. show me a thing: partially soldered pcb. soldering extra buck converters w pins facing the right way before emery and ben get here. desoldering the older buck from the pcb
Soldered a second power plug and buck conv to second board for ease of continuing..
It works!
Emery and i soldered in voltage divider circuit with decoupling cap. now testing by plugging in battery and measuring v at adc port for micro using dmm. we worked on this using the soldering iron in the lab. The result was a more soldered pcb. I learned how to solder a voltage divider. This contributes to the project as we now have a more soldered pcb. The next steps are to test the voltage divider is working.
Entry 1: -----------------------------------------------------------------
Date: March 25thStart Time: 3:00pm
Duration: 2.25 hours
discussing soldering with team. pcbs delivered:
Me and emery will go to thursday soldering session and try tohave soldering done by monday. We'll start with only translating to english and spanish as a prototype bc we need to show that the server accept the language packet. soldering steps from to do list:
visual inspection is fine for all 10 units. heres a reference image of the finalized pcb we should have:
Emery soldering H1 first (barrel jack):
regulator done as well. testing pwr output: testpoint 2 gnd, testpnt 1 vbat, . doesn’t work when plugged into wall. trying to plug barrel jack into steady 9v output from psu. litte easier to try with battery holder instead since barrel jack holes got soldered. getting 45 mV and battery pack is heating up. suggesting an open circuit. turns out we had the power regulator backwards. it should face down. we worked on this using the soldering iron in the lab. the result was a partially soldered pcb. I learned how to solder a pcb. This contributes to the project as we now have a partially soldered pcb. The next steps are to resolder the buck.
=============== Week 9: =================
Entry 2: -----------------------------------------------------------------
Date: March 12thStart Time: 3:00pm
Duration: 1.5 hours
Show me a thing: footprint verification. bukc converter still hasnt arrived even though we were told it would be here today. presentation feedback (summarized by chatgpt):. Strong presentation with detailed explanations, especially on audio processing and hardware connections. Could be shorter but covered all key points well. PCB design is clean, but footprint verification is missing and should be done before ordering. Prototyping slides could be split for clarity. AA batteries may not be sustainable—a lithium pack is recommended. Brown-out protection is missing; battery feedback could control a power relay. More details needed on power consumption and battery life. Package design lacks dimensions (screen, lens, stand). Ensure heat management for user safety. Text readability should be improved with smooth scrolling or chunked updates. UDP packet loss could affect translations—consider redundancy for reliability. PCB improvements: Avoid sharp angles on high-speed lines, improve ESD protection, and consider curving the PCB for a better fit. Language switching UI needs clarification. Pricing estimates and a market comparison would add value. Decided to use PCBGogo for ordering b/c of stencil support. Considering not storing audio at all, and just sending immediately since its notcausing issues so far. Trying to tak eth efunctioning battery indicator + oled code and organizing a more finalized main file system & testing. Trying this directory structure:
Trying main in overall bci directory w/ all battery indicator code in battery_indicator.cpp. seems to have an issue with how app_main is declared (but i suspect its a cmake lists issue):
most likeley this cmakelists:
Looks like I'll need to fix this later. Ben teaching us how to solder. soldered the 4 mics to pins . Added pcb as ordered to docs on website:
We worked on this using vs code. The result was a better understadning of soldering and idrectory structure needed. I learned how to solder. This contributes to the project as we now have a better idea of how to solder. The next steps are to fix the cmake lists and finish the main function.
Entry 1: -----------------------------------------------------------------
Date: March 10thStart Time: 4:45pm
Duration: 2 hours
Meeting to go over pcb. Fredo and Ben working on making pcb changes for the new mic. Me and Emery working on pcb printout verification. Emailing parts order receipt as confirmation:
We saw that uart may be too small for pcb:
turns out we accidentally ordered the wrong part and will need to reorder. Also realized we never received the buck converter. turns out it was in a separate order:
this was from weeks ago . emailed about this since we couldn’t track the order on digekey:
received this repsonse.
Made an order request for uart:
Everything else works for pcb verification:
Worked on this with a printed piece of paper. Teh result was a verified pcb and corrected parts ordered. We learned to always double chek. This contrbutes to project since now pcb is more likely to succeed. Next steaps are getting the parts.
=============== Week 8: =================
Entry 7: -----------------------------------------------------------------
Date: March 7thStart Time: 11:50am
Duration: 0.5 hours
updating this journal. This loweky took a while because I forgot to take actual notes for most of this week because I had actual work to do for once. I worked on thsi using my creative writing skills. The result is an incredible journal that won't only teach my replacement, but make them jealous of my incredible life. I learned how to type like i do every week. This contribtues to the project since we have a great way to intorduce people to our project now. The next step is to leave my computer here when I leave for spirng break.
Entry 6: -----------------------------------------------------------------
Date: March 6thStart Time: 10:30am
Duration: 1 hour
Midterm design review day. It went really well, our timing was perfect. Just a few criticisms on PCB and maybe heat concerns that can be asily addressed. Here's a photo we got at the event:
We worked on this using a roomful of audience members and a computer. The result was the best presentation anyone has ever seen ever. I learned that we are the best senior design teams anywhere, ever born. This contirbutes to the project since we were given instatn 100% in the class and 3 nobel prizes each. The next steps are to pass on our torch to the next best seniro design team of all time.
Entry 5: -----------------------------------------------------------------
Date: March 5thStart Time: 4:20pm
Duration: 3 hours
Completely finalizing slides + finallly final run through of presentation with team. We worked on this in a random classroom with a projector. Result was a much better ocnfidence in what we're presneting as well as our timing. I learned to pace mysefl much better and highlight key aspects of our desing. This contributes to our peojct since i felt very comfortable presenting all of our information for our project. The next step i the final presentation.
Entry 4: -----------------------------------------------------------------
Date: March 5thStart Time: 11:30am
Duration: 1 hour
making some notes on our presentation after seeing others: I'll make sure to pass through psdrs slide very quickly. Fix some typos for a more presentable format. spotted esp32 job needs to be added. Made slides more consistent by removing justification text and making everything only one alternate for major components. Need to add spring break to gantt chart. plenty of text boxes needed to be deleted from img only slides. Few subtitles were missing. Moved PCB image slides. Worked on this using powerpoint. The result was a mtdr with less issues and hopefuly better product. I learned what should be looked into for professional presntations. This contirbutes since it will hopefullyuu make our presntation better. Next steps are the same as they've been this whole week.
Entry 3: -----------------------------------------------------------------
Date: March 5thStart Time: 9:30am
Duration: 2 hours
midterm design reviewer. lessons i learned from other presentations: Time should be carefully watched and account for plenty of questions since both I saw ran over. spring break should be accounted for in gantt chart. I worked on this using the form that was provided for reviewers. The result was a completed review of two other teams prestnations. I learned how to review other presentations. This contributes to the project as we now have a better idea of what to do for our own presentation. The next steps are to finish the presentation and practice presenting it.
Entry 2: -----------------------------------------------------------------
Date: March 4thStart Time: 1:30pm
Duration: 3.25 hours
Digikey order came, sending receipt to office:
Meeting with team to finish presentation slides + practice. We found otu mic is completely out of stock everywhere, so we replaced it with this one, and I put in an order form for it and the microchips we recently placed:
We worked on this using powerpoint. The result was a pretty much finished design review presentation. I learned how to work wiht the team and get a presentation that suits all of us. This contributes to the project as we now have an almost finished mtdr. The next steps are to finish the presentation and practice presenting it.
Entry 1: -----------------------------------------------------------------
Date: March 3rdStart Time: 1:00pm
Duration: 1.75 hours
working on presentation on my own. made a draft for project overview:
Made and updated version with the new image I found that Emery made:
updated psdrs slide:
Setup format for major components slides (esp32, microphone, power regulator, oled):
I worked on this using powerpoint. The result was a rough draft mtdr. I learned how to make a presentation for the design review. This contributes to the project as we now have a rough draft of the design review presentation. The next steps are to finish the presentation and practice presenting it.
=============== Week 7: =================
Entry 5: -----------------------------------------------------------------
Date: February 28thStart Time: 3:00pm
Duration: 1 hour
I spent a bunch of time adding all myu notes from this week to this journal. I also took this weeks particiaption quix.
I worked on this using brightspace. The result was a completed journal entry for this week. I learned more about sofwatere design by taking a closer look at he lecture slides. This contributes to the project as the project joural is up to date, which was importatn this week because of all the images earlier. The next steps are to get started on more design review tuff next week.
Entry 4: -----------------------------------------------------------------
Date: February 27thStart Time: 1:00pm
Duration: 2 hours
updating website to reflect change back to a design with an arm extending out with display in front:
changing the stretch psdrs we roignally had back to stretch psdrs, after benign told they should be stretch goals because they can now be stretch psdrs again:
Updating project reports on website in preparation for design review: a0 uploaded:
a1 uploaded:
a2 uploaded, a3 I don’t have, a4 uploaded, a5 uploaded, a6 uploaded, a7 uploaded, a8 I don't have. Uploading missing parts documents: battery pack datasheet uploaded:
same with npn transistors:
same with tvs diode, micro usb connector, red pc test pnt, leds, boot button, oled male and female connectors. Taking a look at the design review presentation and starting: Reading through the Instructions for Midterm Design Review Presenters doc first, then I’ll use the provided template to start our presentation. Here’s what we need to focus on:
I can use our function desc for project overview along w/ Emery’s cad images, the references/bom for major components, Ben’s system diagram for block diagram, a rough image of emery’s prototype for packaging design, my electrical diagram from a4 for electtrical diagram, Ben and Alfredo’s pcb layout, the image of the oled working w/ battery indication for prototyping progress, however far i get with main function for software progress (along w/ the freertos version of sw from this week’s slides for easy explanation), and make a project timeline. Started project overview, psdrs, beginning sections of presentation, and got it ready for the team to start filling out & cleaning up:
I worked on this using powerpoint. The result was a started midterm design review presentation. I learned how to make a presentation for a design review. This contributes to the project as we now have a started midterm design review presentation. The next steps are to finish the presentation and practice presenting it.
Entry 3: -----------------------------------------------------------------
Date: February 26thStart Time: 3:30pm
Duration: 2.5 hours
This was manlab session. my show me a thing for manlab: order form for pcb parts. during, Me and emery FINALLY prototyping the battery indicator + oled test code:
After this we should take alfredos code that just checks that we’re getting data from mic and see if we can get data form all three. It works on the first try!!!:
Now working on getting the serial monitor output on the screen. Now trying this:
I simply changed print battery status to updating a string variable, which gets passed to main function. It works:
Welll kinda:
gonna try adding in a delay and a clear:
this works for sweeping, all values are displayed well with little delay. We also summarixes the remaining datasheets we needed to add to website with our request form. Helping emery with revising button code. we need to update so it uses external resistors & long term: get it working with oled + battery indicator. Also received feedback: need stretch psdrs by this week, pcb by ben and alfredo was great! I worked on this using the esp idf cli and vs code. The result was a working battery indicator that can display on the oled. I learned how to use the oled and how to display text on it. This contributes to the project as we now have a working battery indicator that can display on the oled. The next steps are to get the microphone working with the battery indicator and get a main function put together to integrate everything and finalize button code.
Entry 2: -----------------------------------------------------------------
Date: February 25thStart Time: 11:45am
Duration: 0.75 hours
making shivam’s suggested changes to the request form and sending. needed to adjust team name & adjust hyperlinks to be shorter. ended up using digikeys share feature for this. While doing this, noticed mic is out of stock:
source: https://www.digikey.com/short/9bv3588v . After conferring with team, we decided we’ll make a separate order for the mic since we really need that exact one since we’ve prototyped it. Deleted from the request for now. Final product:
Sent to engrprocure@purdue.edu:
Worked on this using excel. The result was a complete items request. I learned how to use digikey’s share feature. This contributes to the project as we now have a complete items request. The next step is to make separate order for mic from adafruit since it's in stock there.
Entry 1: -----------------------------------------------------------------
Date: February 24thStart Time: 4:30pm
Duration: 2 hours
We had Team meeting where ben and I place pcb parts orders. finding instructions on how to order:
seems we’re supposed to do procurement again for pcb part, but filling out a form every time would be annoying, so hopefully we can give them a digikey cart and have them fullfill the whole cart
seems like it would be best to use the spreadsheet method rather than the credit card.
we’ll send the spreadsheet to both the business office and cc shivam. We’re assuming digikey is a preferred vendor since it was mentioned in class. finished:
went ahead and sent to shivam. We worked on this using excel. The result was a complete items request. I llearned all the different parts we ened for pcb. This cojtributes to the porject since hopefully we can get the parts we need for. The next step is to send to business office.
=============== Week 6: =================
Entry 5: -----------------------------------------------------------------
Date: February 21stStart Time: 4pm
Duration: 1.25 hours
We had Team meeting on building the schematics:
I also did participation quiz:
I also Updated this journal: . Here's all the parts I need to order by monday: "Reference","Value","Datasheet","Footprint","Qty","DNP" "B1","Button 1","~","Button_Switch_THT:SW_PUSH_6mm_H13mm","1","" "B2","Button 2","~","Button_Switch_THT:SW_PUSH_6mm_H13mm","1","" "Boot1","Boot Button","~","Button_Switch_THT:SW_PUSH_1P1T_6x3.5mm_H4.3_APEM_MJTP1243","1","" "C1","10uF","~","Capacitor_SMD:C_0805_2012Metric_Pad1.18x1.45mm_HandSolder","1","" "C2,C3,C4,C6,C8,C9","0.1uF","~","Capacitor_SMD:C_0805_2012Metric_Pad1.18x1.45mm_HandSolder","6","" "C7","22uF","~","Capacitor_SMD:C_0805_2012Metric_Pad1.18x1.45mm_HandSolder","1","" "D1,D2,D3,D10,D11","ESD9B5.0ST5G","~","Diode_SMD:D_SOD-923","5","" "D4","Battery LED","~","LED_SMD:LED_0805_2012Metric_Pad1.15x1.40mm_HandSolder","1","" "D5","Power LED","~","LED_SMD:LED_0805_2012Metric_Pad1.15x1.40mm_HandSolder","1","" "D6","TX_LED","~","LED_SMD:LED_0805_2012Metric_Pad1.15x1.40mm_HandSolder","1","" "D7,D8,D9","RX_LED","~","LED_SMD:LED_0805_2012Metric_Pad1.15x1.40mm_HandSolder","3","" "Debug1","Debug Conn","~","Connector_PinHeader_2.54mm:PinHeader_1x02_P2.54mm_Vertical","1","" "J1","USB_B_Micro","~","Connector_USB:USB_Micro-B_Wuerth_614105150721_Vertical","1","" "J2","Barrel_Jack","~","Connector_BarrelJack:BarrelJack_Wuerth_6941xx301002","1","" "J3","OLED JST PH 7pin","~","Connector_JST:JST_PH_B7B-PH-K_1x07_P2.00mm_Vertical","1","" "J7","D30V30F3","~","Connector_PinHeader_2.54mm:PinHeader_1x05_P2.54mm_Vertical","1","" "Microphone1","Microphone Connector","~","Connector_PinHeader_2.54mm:PinHeader_1x03_P2.54mm_Vertical","1","" "Q1,Q2","SS8050-G","https://ngspice.sourceforge.io/docs/ngspice-html-manual/manual.xhtml#cha_BJTs","Package_TO_SOT_SMD:SOT-23","2","" "R1","22.1K","~","Resistor_SMD:R_0805_2012Metric_Pad1.20x1.40mm_HandSolder","1","" "R2","47.5k","~","Resistor_SMD:R_0805_2012Metric_Pad1.20x1.40mm_HandSolder","1","" "R3,R5","2k","~","Resistor_SMD:R_0805_2012Metric_Pad1.20x1.40mm_HandSolder","2","" "R4,R8,R9,R10,R11,R12,R14","10k","~","Resistor_SMD:R_0805_2012Metric_Pad1.20x1.40mm_HandSolder","7","" "R6","6M","~","Resistor_SMD:R_0805_2012Metric_Pad1.20x1.40mm_HandSolder","1","" "R7","3M","~","Resistor_SMD:R_0805_2012Metric_Pad1.20x1.40mm_HandSolder","1","" "R13,R15,R16,R17,R18","220","~","Resistor_SMD:R_0805_2012Metric_Pad1.20x1.40mm_HandSolder","5","" "R19,R20","0","~","Resistor_SMD:R_0805_2012Metric_Pad1.20x1.40mm_HandSolder","2","" "RST1","RST Button","~","Button_Switch_THT:SW_PUSH_1P1T_6x3.5mm_H4.3_APEM_MJTP1243","1","" "TP1","Bat TestPoint","~","TestPoint:TestPoint_Keystone_5010-5014_Multipurpose","1","" "TP2","GND 1","~","TestPoint:TestPoint_Keystone_5010-5014_Multipurpose","1","" "TP3","GND 2","~","TestPoint:TestPoint_Keystone_5010-5014_Multipurpose","1","" "TP4","GND 3","~","TestPoint:TestPoint_Keystone_5010-5014_Multipurpose","1","" "TP5","ADC","~","TestPoint:TestPoint_Keystone_5010-5014_Multipurpose","1","" "TP6","Power","~","TestPoint:TestPoint_Keystone_5010-5014_Multipurpose","1","" "TP7","Mic","~","TestPoint:TestPoint_Keystone_5010-5014_Multipurpose","1","" "TP8","VUSB","~","TestPoint:TestPoint_Keystone_5010-5014_Multipurpose","1","" "U1","ESP32-WROOM-32E","https://www.espressif.com/sites/default/files/documentation/esp32-wroom-32e_esp32-wroom-32ue_datasheet_en.pdf","RF_Module:ESP32-WROOM-32D","1","" "U2","CP2102N-Axx-xQFN28","https://www.silabs.com/documents/public/data-sheets/cp2102n-datasheet.pdf","Package_DFN_QFN:QFN-28-1EP_5x5mm_P0.5mm_EP3.35x3.35mm","1","" "UART1","UART_Conn","~","Connector_PinHeader_2.54mm:PinHeader_1x02_P2.54mm_Vertical","1","" We worked on this over a teams meeting and ben used kicad to model. The result was a more finalized schematic fo rth epcb. I learned more about pcb placement throuhg this meeting. This contributes to the project as we now have a more finalized pcb schematic for placement. The next steps are to start ordering parts and get the pcb design finalized.
Entry 4: -----------------------------------------------------------------
Date: February 20thStart Time: 7pm
Duration: 0.75 hours
I Picking small button for rst, led for pcb, throuhole microusb connector w/ ben. these are the smallest throuhghole 2pin only switches: https://www.digikey.com/en/products/detail/apem-inc/MJTP1243/1798039
standard 0805 orange led: https://www.digikey.com/en/products/detail/liteon/LTST-C170KFKT/386775
we couldn't find a right angle through hole usb connect unfortunately, but found this: https://www.digikey.com/en/products/detail/w%C3%BCrth-elektronik/614105150721/5047749?_gl=1*rrf775*_up*MQ..*_gs*MQ..&gclid=EAIaIQobChMIzfOLrcDTiwMVvCvUAR2YgiTkEAQYASABEgJ99PD_BwE&gclsrc=aw.ds
a 5.5 x 2.1 mm barrel jack: https://www.digikey.com/en/products/detail/w-rth-elektronik/694106301002/5047522?gclsrc=aw.ds&&utm_adgroup=&utm_source=google&utm_medium=cpc&utm_campaign=PMax%20Supplier_Focus%20Supplier&utm_term=&utm_content=&utm_id=go_cmp-20243063242_adg-_ad-__dev-c_ext-_prd-5047522_sig-EAIaIQobChMIgdCq2sLTiwMVJSvUAR2q9DcdEAQYASABEgJLkvD_BwE&gad_source=1&gclid=EAIaIQobChMIgdCq2sLTiwMVJSvUAR2q9DcdEAQYASABEgJLkvD_BwE&gclsrc=aw.ds
We worked on this just using teams and chrome. The result was a list of parts we can use for the pcb. This contributes to the project as we now have a list of parts we can use for the pcb. The next steps are to start ordering parts and get the pcb design finalized.
Entry 3: -----------------------------------------------------------------
Date: February 20thStart Time: 12:50pm
Duration: 2 hours
I Work on integrating battery indicator and oled so we cna display the battery level on the screen. Here's ben's setup file directory for the oled: in git:
I'll start by trying to build this & flash (wihtout the oled itself) - I'll download the whole thing locally instead of working out of a git branch so i can integrate it with my local version of battery indicator and start labeling it as a main program as well as make sure all dependencies are correctly set since things work well when th're in my esp-idf env. should be working for now:
I don't have the oled, so this should be good enough proof that its working for me for now. Now to start integration: Literally just combining the two mains gives this:
Good news This compiles:
This works for now, simply printing the battery indictor next steps would be to go to the lab and test it on the oled, and once it is confirmed that we can print to serial monitor and display example text on oled, clean it up by making the oled main a task/class system and then get the battery level on the oled instead of generic text. I worked on this using the esp idf cli and vs code. The result was code that can hopefully both print to serial monitor batteyr indication and run test text on the oled. I learned how easy it can be to integrate two different parts of a project with classes. This contributes to the project as we now are closer to battery indication on the oled. The next steps are to test it on the oled and then clean up the code to make it more modular.
Entry 2: -----------------------------------------------------------------
Date: February 19thStart Time: 3:20pm
Duration: 2.25 hours
My show me a thing for manlab: battery indicator + button code. For sw formalization: button sw needs to be changed to use external pu resistors as below show in schematic below. Now checking on schematic together as team. I downloading kicad, opened file:
Battery & buck looks fine, I'm a little concerned 6M/3M Rs would ratchet down voltage too little for battery indicator to be accurate, but this makes sure we don't accidentally short anything out. ESP32 sensor_vp should connect to bad_adc, not vbat. We added all the package types so we can start ordering. We also got psdr/ funct desc feedback: we cna add stretch psdrs instead of stretch goals. any of the three listed can be sw psdrs - but only two (more detail needed). everything else finished and good to go. schematic feedback: make sure really cant use heartbeat leds for uart - the're really useful. I worked on this using kicad and the web tools we've been using. The result was a more finalized schematic that we can use to order parts. This contributes to the project as we now have a close to finalized schemati. The next steps are to start ordering parts and we also need to updated psdr and functional description with cad photos.
Entry 1: -----------------------------------------------------------------
Date: February 18thStart Time: 5:20pm
Duration: 2 hours
Got working on Integrating SW. My Key goals: test out using raii standards to prevent the need for manual mallocs/frees (one of the main advantages of c++) src: https://en.cppreference.com/w/cpp/language/raii . Convert ring buffer code, battery indicator code i made to this standard. Here's an excerpt from chatgpt about what can and can't be used:
Also need to make it so battery indicator puts the battery percentage as a property of an instance of an object so it can be getted from a main program, take a look at Alfredo's microphone code when he's done to get both adc channels working at once, and get a main function put together to integrate everything. I started Working from the original battery indictor:
there are many improvedments needed before it can be put in an actual prgram, including leveraging c++ features like classes. Here's a New version:
using methods in a class is a more modular way to use the battery indicator code. We use a constructor to intialize the adc rather than through a mian function for cleaner code. we use static since there's no std::shared_ptr for rii still lifetime management. task itself is now simpler adn we can adjust delays and task priority as the project continues. BIG PROBLEM: esp32 can’t use the second adc without disabling the wifi module. Two options now: Use mutexs so evey minute or so the battery indicator is called and the microphone is disabled . Only show battery when the ussr manually holds the button, user is expected to know that no translation is occurring when viewing the battery. Went with the latter, since occasional battery checking would definitely cause cuts in speech that are unintended. adc1 channel 0 for microphone, adc1 channel 1 for battery indicator. Working on getting the two gpio buttons functional in the current code: used this resource for setting up gpio and chatgpt for io config cpp syntax: https://microcontrollerslab.com/push-button-esp32-gpio-digital-input/ . was able to setup a basic class and use isrs instead of tasks, but didn't impelement it fully, so i wont show it yet. I worked on this using the esp idf cli and vs code. The result was a more modular battery indicator that can be used in the final project. I learned how to use classes in c++ to make code more modular. This contributes to the project as we now have a more modular battery indicator that can be used in the final project. The next steps are to get the microphone working with the battery indicator and get a main function put together to integrate everything and finalize button code.
=============== Week 5: =================
Entry 4: -----------------------------------------------------------------
Date: February 14thStart Time: 9:30am
Duration: 1.5 hours
Wroking on a7 with team:
I also spent some time updating this journal, and taking the participation quix:
We worked on this using excel. The result was an exact bill of materials for what we'll need, along with more discussion of how eveyrthing will fit together. The participation quiz and journal also helped me reinforce all the lessons from this week. This contributes to the project as we now have a better idea of what we need to order and how everything will fit together. The next steps for me are to get both mic and battery indicator adc working at once as well as upload battery charge to an object so it can be grabbed by whatever our main function will be, which was discussed in our meeting.
Entry 3: -----------------------------------------------------------------
Date: February 12thStart Time: 3:30pm
Duration: 2.5 hours
For manlab my show me a thing was: adc code for (battery indication). We had a Team meeting discussing mechanical design for pcb layout (during manlab). We NEED TO: update functional description for new mirrored viewpoint mechanical design of display, as you'll see below. We had to make this new design to address an issue where the oled really wasn't very visible when we tested wiht the old desingn. We also moved everything to the right side because of wire legnths and electrical integrity. check functional description for new design, here's an image to help:
We also received feedback as usual: stretch goals are not psdrs, more detail needed. The change to analog should be fine. We should say 6 aa battery and talk abt voltages in func descr. We also need to talk about buck converter in func descr. Also, parallax effect is an issue: brain takes out the display bc the other eye doesn’t see it. After manlab, I updated psdrs for change to analog mic and overhauled functional description for new design above:
I worked on these using the web tools we've been using and the whiteboard for planning together. The result was a new design that should hopefully work better, and we learned that there are reasons you don't see smart glasses with the screen sticking in front of a lens. This contributes to the project as we now have a design that will hopefully work. The next steps are to see if the new functional description and psdrs fit course standards.
Entry 2: -----------------------------------------------------------------
Date: February 9thStart Time: 2:00pm
Duration: 2.5 hours
Emery and I got working on battery indicator (v divider + adc). We are planning on battery pack benign 6 * 1.5 v AA batteries in series: 9v since buck converter has huge input range of 3.3v to 45v: https://www.pololu.com/product/4891 . It seems easiest to use alkaline since steeper discharge curve:
source: https://www.google.com/url?sa=i&url=https%3A%2F%2Fsiliconlightworks.com%2Fli-ion-voltage&psig=AOvVaw3NfDpcREnZRCohqGlkRuOM&ust=1739214872704000&source=images&cd=vfe&opi=89978449&ved=0CBcQjhxqFwoTCMjs4bamt4sDFQAAAAAdAAAAABAE
source: https://www.google.com/url?sa=i&url=https%3A%2F%2Fwww.powerstream.com%2FAA-tests.htm&psig=AOvVaw2BcKhLpHIkB0IS7EE2aklc&ust=1739214665799000&source=images&cd=vfe&opi=89978449&ved=0CBcQjhxqGAoTCIijv4umt4sDFQAAAAAdAAAAABCEAQ so we'll use alkaline for now. Here's an image of the circuit again for reference:
We could also add capacitor between resistor and adc to reduce noise. We will need voltage divider to turn the 9v battery at maximum to 3.6v and at minimum 3.0v for adc in. Need high resistor values as well to limit current as much as possible. Here's a calculation: 3.3v = 9v * (R2 / (R1+R2)) -> 0.36666 = R2/(R1+R2). Here's the pinout sheet from esp32 datasheet:
pins 1 and 4 needed for gnd and adc iln respectively. I then got to working on test program:
I encountered more dependency errors:
I fixed it by added this line to cmakelists.txt under main:idf_component_register(SRCS "cpp_pthread.cpp" INCLUDE_DIRS "." PRIV_REQUIRES driver). This seemingly worked:
but it actually only works when we plug into vp pin for some reason:
Here's some refercnes we used For testing:
And here's some updated code with those notes in mind:
Note that Emery journal includes resistor values and calculations for ranges for quarter battery rannges. By the end of the session, Everything is tested with the above values ouptutted from an oscilloscope. The system works well enough, our resistors are just off, but that can be fixed with better resistors.
I worked on this using the esp idf cli and vs code along with the whiteboard for plannning. The result was a working battery indicator system that can be used in the final project. I learned how to map battery voltages suitably for our system. This contributes to the project as we now have a working battery indicator for one of our psdrs. The next steps are to get everything put together for the final system.
Entry 1: -----------------------------------------------------------------
Date: February 8thStart Time: 2:00pm
Duration: 1.75 hours
I started by finishing a4. I specifically finished electrical considerations:
I also finished interface considerations:
I worked on this using word and drawi0. The result was a much more complete electrical design, taking into account power of each device. I learned more about how to design a power system for a project. This contributes to the project as we now have an understanding of where to go with the physical electrical design. The next steps are to start breadboarding everything.
=============== Week 4: =================
Entry 5: -----------------------------------------------------------------
Date: February 7thStart Time: 4:00pm
Duration: 2.25 hours
I started by updating website psdrs/func desc to reflect psdr change to battery indicator & stretch goals:
i also working on a4. I inserted electrical diagram and updated electrical overview for new psdr and finished frequency electrical considerations:
I worked on these using word and the web tools weve been using. The result was a more up to date psdr page and a more complete a4. This contribtutes to the project since it fleshes out more details of it. The next steps are completing a4.
Entry 4: -----------------------------------------------------------------
Date: February 7thStart Time: 1:00pm
Duration: 1 hour
I started by working on component 5 (buttons) of A5:
Here are the sources i used: https://www.digikey.com/en/products/detail/e-switch/TL1105YF160Q/514438 https://configured-product-images.s3.amazonaws.com/Datasheets/TL1105.pdf . I used word to work on it. The result was a section of the report detialing why we chose tall buttons. This contributes to the project since it details why we chose what we chose, which is important for an open source project. The enxt steps are to order the buttons and make the UI.
Entry 3: -----------------------------------------------------------------
Date: February 5thStart Time: 3:30pm
Duration: 2.5 hours
My show me thing for manlab was ringbuffer code. My tasks through this week will be electrical drawio, update psdrs, update electrical without psram/ w battery indicator, my part of a5, Emery and I work on voltage divider + adc + battery indicator and func description for change to battery indicator psdr, and upload datasheets to website. For doing the last, these will be useful: Mic:
https://www.adafruit.com/product/3421 Oled:
Buck converter: For software, ideally ~15s of audio will be buffered at once. For electrical overview, we needed to pick buck converter (9-5.5v) module to convert battery voltage to operating voltage, will use voltage divider + ADC for battery indicator (hold first button to see the number percentage for batter flash a warning when below a certain amount), need to finalize pinouts. I also built the electrical diagram. I used this resource used for i2s microphone interface: https://www.allaboutcircuits.com/technical-articles/introduction-to-the-i2s-interface/ . oled datasheet used to specify spi signals: https://engineering.purdue.edu/477grp2/Files/refs/SSD1309Datasheet.pdf pg17, 18:
For the buck converter i used this:
source: https://www.pololu.com/product/4891 . Here's An idea of how the ADC, V divider battery indicator, MCU, and buck converter could work together:
soource: https://electronics.stackexchange.com/questions/296423/how-to-find-battery-voltage-with-simple-voltage-divider-circuit-connected-to-adc Here's a rough draft of the finished thing: https://drive.google.com/file/d/1hbuUPYY_oCrpEtWzt6I3SQIY_ZSCrvhZ/view?usp=sharing
And after a few revisions w team:
We also received feedback on psdrs. 1 is fine, 2 should be changed to i2s, 3 should be changed to battery indicator, 4 and 5 are fine. We also added some stretch goals: more nlp filters, siri functionality, bluetooth connection to speaker for audible translation, and transcription goals. I worked on the diagram using drawio. The result after manlab was a much more fleshed out electrical diagram and more robust power system. This contributes to the project as we now have a better reference for electrical design as well as a more defined psdr range. I learned more about how we can do the battery indicator using a voltage divider and adc as well. This contributes to the project as we now have a more finalized electgrcial design. The next steps are to start breadboarding everything.
Entry 2: -----------------------------------------------------------------
Date: February 5thStart Time: 12:20pm
Duration: 1.25 hours
I worked on the ring buffer we'll use to buffer audio before it is sent. I first need to start separate esp idf project from ben since we have different dev envs. These are helpful for starting esp32 cpp projects:
source: https://docs.espressif.com/projects/esp-idf/en/stable/esp32/api-guides/cplusplus.html I then successfully got an example program running:
I started creating a skeleton for a ring buffer that takes adpcm audio and stores it. Here's a helpful resource on esp32 handling of ringbuffer:
source: https://docs.espressif.com/projects/esp-idf/en/stable/esp32/api-reference/system/freertos_additions.html I Wasn't sure how to make a program that would be useful without the other components that actually receive and process the audio, so i asked ChatGPT and it guided me to make a producer and consumer task that can send fake audio packets so I can test ringbuffer usage, and get a skeleton down. This will work for now, but we really need to minize tasks so we dont overwhelm the esp32, ultimately this function should be a small part of the esp32. I was able to crank out a sample program using these resources and Ben’s examples. it wont compile yet though do to the ringbuf.h not being detected, will need to test it out later:
I worked on this using the esp idf cli and vs code. The result was a (hopefully) working ring buffer proof of concept and I learned a little more about how to use the esp32. This contributes to the project since a ring buffer may rpvoe to be essentail for audio or text storage. The next step is testing this program.
Entry 1: -----------------------------------------------------------------
Date: February 3rdStart Time: 8:00pm
Duration: 1.25 hours
I worked on a4 and finished 1.0:
I also started a skeleton for 2.0 wiht some notes taken:
I worked on this with word. The result was a much more fleshed out electrical understadnding of th eproject we can use in the future. The contributes as it gives us a resource to refer to when making the actual project. The next steps are finishing a4.
=============== Week 3: =================
Entry 5: -----------------------------------------------------------------
Date: January 31stStart Time: 1:00pm
Duration: 0.5 hours
I took weekly quiz + updated journal with notes online:
I worked on these using brightspace and the website tools weve been using. The result was a better understanding of the different components we can choose from and I learned how we can incorporate them if we need to. This contributes to the project in a better understanding of the hw that may be necessary. The next steps are designing pcbs next week.
Entry 4: -----------------------------------------------------------------
Date: January 30thStart Time: 1:45pm
Duration: 2.75 hours
I Asked Jonathan & Shivam about cmake issues. They said this may just be a python virtual environment issue and to either make sure to edit the Makefile or use Thonny instead of esp-idf. I tried to make a CXX project instead of a python example again. The python dependency still fails, which is used by esp idf. I then tried deleting and redowloading esp-idf. Started by delete both esp dir and .espressif, but when on export.sh step, I get this error I havent seen before:
idf.py existed, it just wasnt detected for some reason. I added :$IDF_PATH/tools to path variable & fixed issue. idf.py set-target esp32 now works on Ben's example cpp blink project but idf.py menuconfig fails because of ninja syntax error. I got hello world example to build via cli instead of vscode, but now I realize the esp isnt found on my /dev/ folder:
I Tried to download this driver: https://www.silabs.com/developer-tools/usb-to-uart-bridge-vcp-drivers?tab=downloads to see if it fixes the issue and lets the uart communicate w my usb ports, it kept halting, but eventually installed:
And now It finally works when using a data cable if i just don't deal with vs code 🥹
I worked on this with vscode but eventually ended up using esp idfs cli version instead. The result was a finally working dev environemnt and i learned that guis are annoying and should never be trusted ever. This contributes to the project because i can actually finally code now. The next steps are to do some actual work.
Entry 3: -----------------------------------------------------------------
Date: January 29thStart Time: 10:00am
Duration: 0.5 hours
We discussing more details with team remotely. we decided to go with a ring buffer more info here: https://en.wikipedia.org/wiki/Circular_buffer . This allows us to drop earliest data when we need to and rotate around with pointer system rather than pushing forward in a queue. I also updated psdrs based on feedback today on website:
We discussed over text and teams and i updatwd the website using the same tools we have been using. The result was a hopefully improved design and more precise psdrs. These contribute to the project prgoress by fleshing out the design before implementation begins. The next steps are implementing the ring buffer and seeing if it works for our purposes.
Entry 2: -----------------------------------------------------------------
Date: January 29thStart Time: 3:30pm
Duration: 2.25 hours
My show me a thing for ManLab was the psdrs and functional descirption i redid last week. We received psdr feedback with it. Our first psdr was missing the word microcontroller. Our second psdr needs to use the word i2c. Our third psdr needs to be specific abt exact device we use. Our fourth psdr needs to change as you decide what exact computer to use (could be raspberry pi server). Our fifth psdr: make sure text on oled is displayed at a distance so user doesn't have to look closely - more descriptive here w/ text queue as well. We also got feedback that instead of using lenses physics, just use the grpahics of the oled to make text look further than it is. We then did a sofwatre overview. Ben put examples of tasks on github - they allow us to keep looping code that can be prioirtized using xTaskCreate - recording microphone, displaying to display, fetching data etc. gpio buttons should use interrupts instead - use as few tasks as possible. We use external ram malloc to build audio queue (store in ext ram), use normal malloc to build text queu (store internal). We will have task for api queue only while volume loud enough loop. We then potentially thought about two text queues actually, untranslated (after text to speech), translated (after receiving from translation api). Here was the original design we went with:
But we decided to go for a different one. In the new design, Computer now does the api call for the speech to text, stores the pre translated text, and then calls the translation api, and then simply sends back the translated text, and we still need external ram to store audio packets so main storage is free for text queue. This simplifies some things for us and reduces potential load and bugs for the micro. Heres an image:
So the Plan for now: take 10s audio, push directly to RAM (queue of just size 1 for now), send immediately. We worked on all of this with just our whiteboard. The result was a more fleshed out software overview and more descsriptive psdrs, we learned to be as descriptive as possible. This contorbutes to the project since we know exactly what to work on in the comoing weeks. Next step assignments follow: Rohit: PSDR updates, TCP receive, fix idf (meet thurs w/ TAs). Ben: TCP send. Alfredo: A3, Microphone. Emery: Microphone, Lens physics.
Entry 1: -----------------------------------------------------------------
Date: January 28thStart Time: 5:15pm
Duration: 2.5 hours
Worked on trying to fix the ESP dev environment on my machine. I downloaded macos esp32 xtensa gcc based toolkit & set cmake_asm_compiler in cmake cache: https://github.com/espressif/crosstool-NG/releases/download/esp-14.2.0_20241119/xtensa-esp-elf-14.2.0_20241119-x86_64-apple-darwin.tar.xz . I also set it as CC and ASM env variables so i dont have to redo for every test project. I then tried setting env vars in cmake settings.json:
Then got the following error: Could not create symbolic link for: [cmake] /Users/rohit/esp/esp-idf/components/mbedtls/mbedtls/library/error.c → . I ended up having to rm the file along with version_features.c, ssl_debug_helpers_generated.c, psa_crypto_driver_wrappers_no_static.c. I ended up giving up at the following error:
It seems seems ESP_ROM_ELF_DIR is not getting set properly. The tools i used were vscode and the espidf. The result was a lot of workarounds, and I learned that making abuch of workarounds in these dev environements does not necessarily get you clsoer to them working. This was a contribution to the porject since it got me closer to getting the environemnt set up properly for develooment. The next steps are seeing whether i should keep doing workarounds or try a nother method.
=============== Week 2: =================
Entry 5: -----------------------------------------------------------------
Date: January 24thStart Time: 10:00am
Duration: 1.5 hours
I spent time taking the participations quiz, important to test knowledge in lecture. We then as a team worked on A2, with me working on defining different constraints and theory of operation for the project to better understand the end goal. We worked on Word. The result was some a finished A2 with more details about the project. This contributes as we now have a block diagram and other useful information to work off of. The next steps are starting to code and PCB design.
Entry 4: -----------------------------------------------------------------
Date: January 23rdStart Time: 2:00pm
Duration: 1.5 hours
I spent time trying to individually testing out different sample programs on esp32, trying to rewrite some sample code and getting a handle on coding for esp32. However, I ended up just trying to troubleshoot esp-idf because I was trying to use my existing riscv64 compiler when I should have been using an xtensa compiler with the esp-idf, as I found out after trying and talking to Ben. I kept getting an error message that xtensa compiler wasn't found, so I tried forcing riscv by downloading riscv64 toolchain for mac, setting idf environment variable in zprofile, setting riscv compiler environment variable in zprofile, setting cmake cache entry to riscv compiler.
The tools I sed were VSCode, ESP-IDF, and Homebrew. The result was a big waste of time. I learned that I should read the cmake errors more carefully and to ask for help when I need it. This contributes to the project progress since some correct environemtn variables were ultimately set. The next steps are trying everything again with the xtensa compiler.
Entry 3: -----------------------------------------------------------------
Date: January 23rdStart Time: 10:00am
Duration: 1.5 hours
I updated psdrs and functional descriptions on website based on the below criticism. I just used our standard website tools and my notes on here. The result was a much more descriptive design. I learned to be more throgouh about what exactly is written down. This contributes to the project since everything we discussed is written formally and people understand our design better. The next stepas are formalizing, and getting feedback.
Entry 2: -----------------------------------------------------------------
Date: January 22ndStart Time: 3:30pm
Duration: 2.75 hours
We held a lecture/planning for team. We decided to: using c++ because more online support and oop, Im using esp32 for development whereas rest of group is using esp32e, - same programming, just slower. Our folder hierarchy will have includes folder w/ libraries, pdmc i2c interfaces, rtos on esp32 uses “processes”. We will have a stack/queue system for audio packets, held in esp, sent to server, transformed to text in server, sent back to esp. We originally decided to use laptop for queu system since only 512kb of ram on esp (more on this later).
We decided to using 4 double a batteries in a 3d printed case without battery reserve indicator. A semi-final design:
We worked on this just on a whiteboard and taking notes. The result was a more solidified idea of where we're going, which definetely contributes to the project progress as well. The next steps are need to discuss whether pcm or wav data needs to be compressed before sending. I also Followed bens guide to setup espressif idf. There are touch button examples for capacitive buttons:
Also PDM examples for audio transmissions and spi examples for screen. I also setup blank esp32 project in git repo. I worked on all of this with vscode, downloading necessary software on my mac. The result was a little better setup project environment where we can start testing things out. I learned setup can be difficult so we should start early. This gives us a good starting point for testing which contributes to the project. The next steps are actually testing. We also received A1 feedback. We learned that pcb can be slightly bigger than planned in final design, that we need more detail in description about modes and mechanical design, need another hw psdr instead of button setup such as adc knob for brightness. We also need to revise one to simply say able to display info to oled via communication protocol. We may need separate memory chip for sw buffer to avoid lag (possible hw psdr) or encoder. We were told we need to start sending data to whisper to figure out sweet spot of data size for reduced lag and that our functional description needs more psdrs in it (should basically be lsit of psdrs) (can be bullet points). We decided to go for two physical button setup because they are no longer psdr and to go for external storage solution for 3rd hw psdr because makes queuing system easier to implement (dedicated spi). We talked this out with instructors so no tools were used. The result was a better understanding of the very final design,s ince we needed major revisions. I learned our initial idea was not ambitious enough. This contirbutes to the project since it gives us a better understanding of the expectations. The next steps are finalizing the psdrs.
Entry 1: -----------------------------------------------------------------
Date: January 22ndStart Time: 10:00am
Duration: 0.75 hours
I uploaded our then psdrs and functional description to our website. I also troubleshooted the website not updating in real time and made my team member page. I worked on it with the same tools we've been using, just html. The result was a then up to date website giving some basic information about the project, which certainly helps the progress of the final psdrs and functional description we'll use. The next steps are fleshing out the rest of the website.
=============== Week 1: =================
Entry 2: -----------------------------------------------------------------
Date: January 17thStart Time: 10:00am
Duration: 1.25 hours
As a team we worked on A1. We worked on it using Word. The result was formalizing PSDRs and me taking on Software lead along with electrical report and reliability and safety analysus. This contributes to the project because it outlined project roles and assigned responsibilities. The next steps are to start working on the electrical report and reliability and safety analysis.
Entry 1: -----------------------------------------------------------------
Date: January 15thStart Time: 3:30pm
Duration: 2.5 hours
We started by taking a tour of the senior design room. Some notes are that Parts and manufacturing resources available at ECE shop, Bechtel, senior design room, basement under senior design room, we must Design PCBs around 0805 capacitors, we Can use ESP devboards in backroom, and we must Use connectors in the final design. There were no tools for this, just taking notes while touring. The result was more knowledge about the process we should take to design our project. This helps give us a good starting point as far as project progress goes. Next steps would be to put those resources to use! We also got Interviewed by TAs and found out that we should Order displays as soon as possible since it's the most likely part of the design to not work and that we may need to Switch to a handheld potentially glove design if this is the case. This was again just note taking, so no tools were used. The result was rethinking potential backup decisions for our design, which helps contribute to the progress in case things dont work out. The next steps are ordering parts immediately. I also personally got our Website uploaded. The tools used were the course standard network drive and html. The result was that we now have a website for people to turn to. This contributes to our project progress as it is open source. The next steps are add pictures, format, fill out info2.