Thursday, 23 June 2016

23/06/16 - Robots

Lesson Aims:
Design a system for a given set of requirements
Write Pseudo code


A
M
S
Learning Aims (what the learner will be able to do)
/


Design a system with 4 sensors
/


Consider a test strategy

/

Justify a test strategy
/


Be able to use the correct shapes for flow charts
/


Able to identify key rules for Pseudocode

/

Can write correct Pseudocode
A
M
S
Learning Objectives (skills, knowledge & attitudes)
/


Create a system diagram
/


Identify possible solutions
/


Consider limiting / restricting factors

Today I have learnt about the line following code for the robots. This was quite simple to do however I did have an issue with the + and - in the code so it did not work.

A strength of today is that I have managed to finish my program and I have a few issues that need fixing while I test. To improve, I would have liked to try and get the code fully functional however it took a while to get everything working together. 

Overall I am pleased with my robot and the program and I will be finishing it all off tomorrow. 

Monday, 20 June 2016

20/06/16 - Analogue and digital

Lesson Aims:
Make a robot react to 3 different event triggers
Understand how signal conversion occurs


A
M
S
Learning Aims (what the learner will be able to do)
/


Create a program to control a 3 sensor automated system
/


Understand how data is converted between analogue and digital
/


Be able to use the correct shapes for flow charts
/


Able to identify key rules for Pseudocode

/

Can write correct Pseudocode
A
M
S
Learning Objectives (skills, knowledge & attitudes)
/


Write code that compiles
/


Solve errors
/


Use 3 sensors and motors to make an autonomous system

/

Convert analogue to digital signals
Today I learnt about analogue and digital data. I did not know too much about this and as we need it for the merit we learnt about it. In the end I understand it now and will be able to easily finish off all the work by tomorrow. All I need to do is a couple edits to the video, and the merit for U24. 

A strength of today is that I have managed to nearly finish off the U14 merit. I only have a couple bits left to do then it will be done. A weakness is that I did not manage to get it all done today however I had a one hour lesson with Adam about employability skills that was quite interesting. 

Overall I am pleased with the progress that I have made today and I have learnt a lot about both analogue and digital signal conversion works. 

Friday, 17 June 2016

17/06/16 - Robots

Lesson Aims:
Make a robot react to 3 different event triggers
Identify how the design of a robot can affects its performance



A
M
S
Learning Aims (what the learner will be able to do)
/


Can explain how precede and mutex commands work in NXC
/


Identify the order of execution in NxC
/


Write readable code
/


Write quality code

/

Design ideas for robot
/


Understand the requirements for U14 A2 and U24 A3


Today I have been working on the code for the NXT robot. I had a few issues that I had to fix before I recorded it. I have learnt today about playing sounds from the robot while it is doing something in between.

A strength of today is that I have managed to finish off the program and commented it in detail and I have recorded however I need to edit them together. To improve, I will comment in more detail when I am going along making the code instead of making short notes that sometimes do not make sense.

Overall today has gone well and I pleased about finishing off the code and recording the robot. I also enjoyed the starter activity where we played the Lightbot game as it was interesting using different solutions for the levels. Below is the code from my impact sensor.


task impact_sensor() //Task for checking impact sensor { while(true) { if(SENSOR_1 == 1) //If the sensor is activated then the program under will run { Acquire(motorMutex); Off(OUT_AC); Wait(HalfSec); OnRevSync(OUT_AC,MaxSpeed ,0); //Reverse at max speed so it can be easily identified from the ultrasonic sensor Wait(HalfSec); PlayTone(500,700); Wait(300); PlayTone(1175,400); Wait(300); //Will play a tone then it will turn around PlayTone(1397,400); Wait(500); OnFwd(OUT_A, HalfSpeed); OnRev(OUT_C, HalfSpeed); //Does a 180 spin so it goes back in the direction it went in Wait(900); Off(OUT_AC); //Turn off motors and wait half a second before releasing the motors Wait(HalfSec); Release(motorMutex); } } }

Thursday, 9 June 2016

09/06/16 - Assignment one

Aim: To evaluate the suitability of event driven programming (EDP)

Objective:
State the features of EDP
Explain how OS can be considered event driven
Understand that not all event driven programs have a GUI implemented
Name some systems that are event driven but do not have a GUI
Explain at least one example of a system that is event driven but does not have a GUI
Describe in detail examples of a system that is event driven but does not have a GUI

Today I learnt about the distinction part of assignment one. I do not think I will be going for the final two distinctions as I have what I need for my grade. 

A strength of today is that I have managed to add in the other parts to the pass and I have also worked more on task two. I have nearly finished this so I will aim to get it all finished and submitted by the end of the day. 

Monday, 6 June 2016

06/06/16 - Assignment one

Aim:
To understand the features of event driven programming

Objectives:
Explain the features of event driven programming
State some advantages and disadvantages of event driven programming
Describe, with examples, how an operating system can be viewed as an event driven application

Today I have learnt about the remainder of assignment one task one and task two. Task two seems quite simple to do I do not think it should take too much time. 

A strength of today is that I have managed to finish off task one and I have started task two. To improve I need to proof read my work as I go along as I did see a few errors in task one. 

Friday, 27 May 2016

27/05/16 - Robots

Aim:

Have a basic understanding of the NxC language
Understand how NXT and NxC relate
Refamiliarize with flowcharts and Pseudo code

Today  we have been learning about the robots that we will be using for the last two units. These are the Lego Mindstorm NXT robots programmed in NxC (Not Exactly C). I have used a newer model of Lego Mindstorms beforehand so I had some knowledge about the robot but not the written programming side. 

A strength of today is that I have managed to learn about NxC and I now understand the basics of the code. To improve, I would have liked to made some more notes about the code however it is in our documents so I can refer back to it. 

Monday, 23 May 2016

2/05/16 - Event Driven Programming

Aim: To explain the key elements of event driven programming

Objectives:
Understand the purpose of event driven programming
Identify the key features of an event driven program
Describe in detail the key features of event driven programming

Today we have started the unit 14 theory. There is only one assignment to this and then we start on the practicals of both units. The bit of task one we learnt was quite simple and I have managed to finish it. 

A strength of today is that I have managed to finish the first part of assignment one task one. To improve, I would have liked to laid out the document while we were learning about it so then I could add notes if needed. 

Overall I am pleased with what I have managed to get done in the time we had today. The starter did take a bit of time however it was interesting seeing all of the different technology on Kickstarter.