CPE101 Learning Journal - Yuil Tripathee [650...]
ProfileGitHub
  • Introductions
  • Weekly Diary
    • Week 1 - Introduction, Syllabus
    • Week 2 - Storytelling for communication, consensus
    • Week 3 - 2D CAD using LibreCAD application
    • Week 4 - 3D CAD Drawing using Constructive Solid Geometry
    • Week 5 - TinkerCAD Circuits
    • Week 6 - micro:Bit
    • Week 7 - Build a Simple Game
    • Week 8 - Introduction to Application Development
    • Week 9 - Project 1 (Gambler Bot)
    • Week 10 - Introduction to AI and Machine Learning
    • Week 11 - Happy Coding
    • Week 12 - Cyber Security
    • Week 13 - The Three Challenges
    • Week 14 - Project Progress Report
    • Week 15 - CPE101 Game Day 'Poker'
    • Holidays
  • Projects Diary
    • #1 - Gambler bot
    • Final Project
  • Experiments Diary
    • Try running code of different languages using micro:Bit
    • Collaboration in Coding Team
Powered by GitBook
On this page
  • Coursework (the 'what?') 🤷‍♂️
  • Impact (the 'so what?') 🚀
  • Reflections (the 'now what?') 🤔
  • A detailed exploration of this coursework/activity 📄

Was this helpful?

Edit on GitHub
  1. Weekly Diary

Week 13 - The Three Challenges

POP168 board usage

November 18, 2022

The phrase "three pillar challenges" refers to the three test challenges we must complete on this day using the ATMega-168 CPU (based model) and POP168 BOARD. Given that we are provided with a few sample sheets of information and that we must update code in order to complete the objective, I would say that the obstacles today are pretty difficult in comparison to past days.

Coursework (the 'what?') 🤷‍♂️

The first challenge, "racing track," requires us to create computer code to drive a robot. In addition to the robots, there are two walls that must not be hit in order for the vehicle to reach the track's terminus.

The **third challenge ** is to get the robot to move toward the location that is thought of as the goal without utilizing any sensors. Therefore, we had to change the code that was provided in the information and go back to the code that we wanted. To get to the location we desired, we changed both wheels' speeds and added delay to a few lines of code.

The last challenge is to utilize two buttons as a bumper to make the robot change course when it collides with something. Within three minutes, we must strike some toys called TAs as hard as we can.

Impact (the 'so what?') 🚀

We must employ the skills that are taught in the "Happy Coding" session in order to complete all of the missions that have been assigned to us. We had to exercise good judgment, and when combined with the lecture and our general knowledge, we hardly completed the one lab. I may still claim that this lesson helped me better.

Reflections (the 'now what?') 🤔

I learned a lot in this session, and I now appreciate how valuable micro-controllers are in everyday life. For a computer engineer, understanding how they operate and how they perform is unquestionably essential. I'll therefore try to use the knowledge I've learned from these issues in future scenarios.

A detailed exploration of this coursework/activity 📄

Keynotes 📝

  • Embedded C++

void setup( ) {
  // run once
}

void loop() {
  // run forever
}

Issue: avrdude: stk500_recv(): programmer is not responding

Labs:

  1. Blink LED

  2. Frequency output (Piezo Electric Speaker) P15 (D9) -> C1 (10 uF) -> +(speaker)- -> GND

void setup() {
	pinMode(9, OUTPUT);
}

void loop() {
	for (int i = 0; i < 500; i++) {
		digitalWrite(9, HIGH);
		delayMicroseconds(500);
		digitalWrite(9, LOW);
		delay Microseconds(500);
	}
}
	
  1. LDR control for LED

  2. Display on SLCD

PreviousWeek 12 - Cyber SecurityNextWeek 14 - Project Progress Report

Last updated 2 years ago

Was this helpful?