D2- Evaluate the design and performance of a control
system
Introduction
In this report I will be evaluating my own MO Way Robot control system which was
designed and implemented by myself. I will be explaining how well the design was and my
opinions of it. I will further talk about the actual system working when I tested it for the
necessary actions to be taking place. With me testing and analysed it I will then talk about
the strengths (what went well) and weaknesses (what did not go so well) of the robot and
further improvements I could make from this.
Design
In my opinion the design of the control system was well laid out and had a similar
representation to the actual program such as the sensor and actions boxes were the same
colours like they were in the program, the Ticks and Crosses shown the paths like you would
see if you connected everything in the program and the connector arrows were pointing the
right way. With it being similar it can easily be copied into a new project file if you wanted to
do so. The design also had suitable annotations pointing to the correct items it was talking
about, the annotations were straight to the point explaining what each box does and other
features like connectors were also explained. The font on the design was fairly small
however it was still readable.
Efficiency
The robots program needs to be efficient and only do the actions it needs to. The code in
the MO Way Program is organised well correctly as you can check by the diagram. The
programs code was organised going downwards with the important steps at the top such as
the robot moving and detecting the black line and the least important steps at the bottom
such as flashing the light, the connectors were also in chronological order as the arrows
were facing the way the next action should be and also none of them were leading to the
same place twice. In my opinion the MO Way program was understandable by anyone who
wanted to program it or use the same kind of concept as it was simple to follow. As far as
any unnecessary processes there were not any as they were all involved in some kind of
away, for example the white line detection was necessary because if I didn’t have it I
couldn’t connect the process on top of it so basically I needed it for the system to carry on
looping.
Performance of finished system
The performance of the finished system was better than i expected and met all the
requirements I wanted it to do. The whole program works well when tested on the obstacle
course and does what it is intended to which was to avoid obstacles without going straight
through them or going backwards in its path. You can see by the test table I didn’t have to
do any retests so the outcome was good.
system
Introduction
In this report I will be evaluating my own MO Way Robot control system which was
designed and implemented by myself. I will be explaining how well the design was and my
opinions of it. I will further talk about the actual system working when I tested it for the
necessary actions to be taking place. With me testing and analysed it I will then talk about
the strengths (what went well) and weaknesses (what did not go so well) of the robot and
further improvements I could make from this.
Design
In my opinion the design of the control system was well laid out and had a similar
representation to the actual program such as the sensor and actions boxes were the same
colours like they were in the program, the Ticks and Crosses shown the paths like you would
see if you connected everything in the program and the connector arrows were pointing the
right way. With it being similar it can easily be copied into a new project file if you wanted to
do so. The design also had suitable annotations pointing to the correct items it was talking
about, the annotations were straight to the point explaining what each box does and other
features like connectors were also explained. The font on the design was fairly small
however it was still readable.
Efficiency
The robots program needs to be efficient and only do the actions it needs to. The code in
the MO Way Program is organised well correctly as you can check by the diagram. The
programs code was organised going downwards with the important steps at the top such as
the robot moving and detecting the black line and the least important steps at the bottom
such as flashing the light, the connectors were also in chronological order as the arrows
were facing the way the next action should be and also none of them were leading to the
same place twice. In my opinion the MO Way program was understandable by anyone who
wanted to program it or use the same kind of concept as it was simple to follow. As far as
any unnecessary processes there were not any as they were all involved in some kind of
away, for example the white line detection was necessary because if I didn’t have it I
couldn’t connect the process on top of it so basically I needed it for the system to carry on
looping.
Performance of finished system
The performance of the finished system was better than i expected and met all the
requirements I wanted it to do. The whole program works well when tested on the obstacle
course and does what it is intended to which was to avoid obstacles without going straight
through them or going backwards in its path. You can see by the test table I didn’t have to
do any retests so the outcome was good.
