Week 4 summary

In week 4, we were mainly making small changes to our code for the bench inspection. Heres Erik's summary for week 4

During testing the communication after connecting the computer and Arduino, I discovered that at seemingly random points the Arduino would be reset and the rest of the program break as a result. I believe the cause of this issue is that the destructors for the ‘SerialPort’ objects are called once functions end. This issue could not be fixed in time for bench inspection, so instead of having the game code and arduino code interface with each other, they will both run independantly and the user will use the arduino to read the voltage and confirm its correct, then use the game code to input the resistance value and move onto the next level.

Adams progress for week 4:

After the change in functionality because of the communication code not working, we decided to have th game code and arduino code run independantly. I had to modify the game code to prompt the user for a value for resistance, instead of relying on ther arduino to feed a simple '0' or '1' for incorrect or correct. We also added some leeway for resistamce, allowing a range of values instead of just asking for the exact values.#

Abdul wahab outlined his progress below:

In the fourth week, we finished what we could finish from the code as some parts were not working to the extent that we hoped but hopefully everything will work out in the end before the bench inspection. Some modification needs to be done to the Arduino circuit in order to make it better in communicating with the game code without the communication code the suitable idea that we got is to make the user try the circuit first on the Arduino code then he type in the value he got in the game code. 


Comments

Popular posts from this blog

Week 3 Summary