Task D1
The Test planning
Sound testing
This is the evidence of sound sensor testing. These screenshots provide evidence that I have tested the Formula Flowcode program.
This is the evidence of sound sensor testing. These screenshots provide evidence that I have tested the Formula Flowcode program.
Light testing
This is the evidence of light sensor testing. These screenshots provide evidence to show that I have tested the Formula Flowcode program.Here is the video that I have recorded to show the proof when the buggy was reacted based on my design program.
Here is the evidence of the Formula Flowcode programs on the flowchart that I have created two sensors. One is a sound sensor and the second one is a light sensor. Firstly, I created both of them independently and then I joined both of them together to be able to work with multiple systems and also to become a complex program of robot. I created these programs to be able to perform 'dancing'. When you play the music or make it sound above 65 variables the buggy will dance. The other sensor works with light to perform dancing as well. The only difference between these program was when they started to activate the buggy and the movements of the buggy.
whilst I was creating and designing the two sensors I had a few problems using the ‘Call Component Macro’, ‘Call Macro’ and ‘Loop’ icon properly. It then took me a long time to understand the tools, how I can use them and their usability in times of creating a formula flowcode program. After I had practised some simple programs and asked my tutor. Especially, whilst I was designing the program to create a “Macro” independently to join with my initial program such as using variables and actions.Later on I became to understand how I can create different types of macros in order to use my initial program.
When I finished creating the program completely, I tested the sound sensor on the virtual test bed to simulate on the screen. It was working exactly how I had planned on the flowchart program and then I downloaded into the buggy to see if the program is able to activate the buggy. I tried by clapping my hands for the final running of my program system to see if the buggy reacted by the sound sensor but it took a long time for the buggy to respond . On this case it did not go well during the testing plan so that I had to improve the program in order to fix the problem.
In order to solve the problem I had to improve my sound sensor program which I changed the decision of variable from 65 into 45. This solution improved my program so that when I clapped my hand again the buggy responded much better to sound.
I think after I had used the main components to make my program complex, it worked well but I had to improve my design system. I would say it might add more components with variety actions to react on the buggy such as ‘Component Macro’ and ‘Macro’ by doing spinning or turning 90 or 180 degrees and moving forwards or backwards and so on.
I think I could make my design system better by improving what I have created for this task. In order to improve my design if I had more time, I could improve the activation code to make the buggy perform as a Hoover and covering the whole floor. This could be quite a complex design to improve my design program but at the sametime, it had been really cool to see that my design had turned into real action to be able activate the machine. The sound sensor could also be improved by pressing the button because the Hoover might start to activate with any sound, so this would be helpful for the better functionality and for the safety of the equipment.
Imagine, that when my design turned into real action and the Hoover is fully working, this would be a great moment to see it.




















