The Risk Analysis is here.
Description | Prob | Imp | PxI | Response A | Response B | |
RI1 | Communication problem: delay in sending camera images to the student. | 2 | 4 | 8 | Decreased resolution of the uploaded image. Only sends the camera image useful for the task. | Sending a video at the end of the execution instead of the image in real time. |
RI2 | Pincers not strong enough | 2 | 4 | 8 | include wheels in the boxes. | Redo the task so that it is possible to complete without holding the box, remove the related tasks. |
RI3 | Pincers fail to grab item | 1 | 4 | 4 | Use a different, simpler pincer format. | |
RI4 | Robot ESP32 is overloaded | 3 | 2 | 6 | Reduce robot camera capture frequency and resolution. | Move baterry level processing to Arduino |
RI5 | Too low visibility for the RGB LEDs | 3 | 2 | 6 | Multiple LEDs with surface lighting. | Use the student monitor to signal colors. Send arena color to robot using wifi connection |
RI6 | Buttons fail to press | 3 | 2 | 6 | Use infrared sensor to simulate a button | Use distance sensor to simulate a button |
RI7 | Robot needs more space for maneuver in the maze | 2 | 3 | 6 | Increase the spacing between maze walls, redesign and reduce the complexity of the maze. | |
RI8 | The PVC camera support doesn't work | 3 | 2 | 6 | Use tripod with PVC pipe extender | Fix the cameras in the ceiling |
RI9 | Not having enough space for the color sensor on the underside of the robot | 2 | 2 | 4 | Use a 3d printed platform | replace with an infrared and use black and white detection only |
RI10 | Battery duration too short. | 2 | 2 | 4 | Extra batteries. Set a maximum time for tasks. | Set a minimum time between the execution of two tasks |
RI11 | Induction charger not charging enough | 2 | 2 | 4 | Make a physical contact charging connector using magnets for alignment | Remove the automatic charger |
RI12 | Not aligning the robot correctly with the charger | 2 | 2 | 4 | Include floor markings to read with the color sensor | |
RI13 | Problems in not separating the power supply between motors and controllers | 2 | 2 | 4 | split the supplies, only charge motors supply | |
RI14 | DC motors insufficient power | 2 | 2 | 4 | Uppower the motors, rework power supply | |
RI15 | Problems aligning with the grid | 2 | 2 | 4 | Use a PID control | Use steep motor to control the robot |
RI16 | Someone steps on the arena and breaks something | 2 | 2 | 4 | Warnings around the arena, fix it | |
RI17 | Robot Arduino processing overload | 1 | 3 | 3 | Use a second arduino, or substitute the Arduino for a RPi | Move processing to the arena PC |
RI18 | Problem with coordination, communication, or other problems with multiple robot processors | 2 | 3 | 6 | Use a single RPi on the robot | |
RI19 | Problems to movement the box | 1 | 3 | 3 | include a servo motor to lift the claw | |
RI20 | Robot detection error | 1 | 3 | 3 | use a bigger tag or a different tag model | |
RI21 | Box detection error | 1 | 3 | 3 | Include a structure uses a structure on top of the box to use a larger tag. Use color detection. | Removes task accomplished detection in boxes tasks |
RI22 | Robot escapes bounds | 3 | 1 | 3 | include a margin between the camera boundary and the walls. Send a stop signal to the robot if it is in a wrong position. | Someone has to manually put the robot back in the starting position and fix any damaged walls. |
RI23 | Battery measurement inaccuracy | 1 | 2 | 2 | Use an INA219 to read the level | use runtime to define charging need |
RI24 | ESP32-cam and arduino communicantio problems | 2 | 1 | 2 | Use i2c protocol | |
RI25 | The polystyrene walls fails | 2 | 1 | 2 | Draw maze in the arena's floor, use walls only in colored ends. | |
RI26 | Local pc unable to handle all server requests | 1 | 2 | 2 | Use a scalable cloud based serve (Azure or AWS) | |
RI27 | Misaligned center of mass | 2 | 1 | 2 | move components | |
RI28 | Electronic Compoponent failure | 2 | 2 | 4 | Preventive: Buy spares for the ones whith long delivieries. Check the sale in stores close to UTFPR. | Buy a new componnent. |
RI29 | Loss of a team member permanently | 2 | 3 | 6 | remove the tasks with box, the robot's claw and related requirements. Soft-FR10 Robot-FR03, 3.1, 3.2, 3.3 Arena-FR07, 07.1, 07.1 | |
RI30 | Loss of two team member permanently | 2 | 4 | 8 | Same as RI29, the robot charger and completeness review. Robot-FR07, 07.1, 07.2, 07.3, 07.4, 07.5, 07.6 Arena-FR08 | |
RI31 | Loss of three team member permanently | 2 | 5 | 10 | Same as RI30 and the teacher webapp. Soft-FR02, 02.1, 02.2, 02.3, 02.4 | |
RI32 | Temporary single team member unavailable | 1 | 3 | 3 | Redistribute on going tasks between the other members | |
RI33 | Temporary multiple team members unavailable | 3 | 3 | 9 | Redistribute on going tasks between the other members | |
RI34 | Blocks created for the block programming language not being enought to complete the proposed tasks | 4 | 1 | 4 | Create more Blocks, so the user can solve all tasks |
- Get link
- X
- Other Apps
- Get link
- X
- Other Apps
Comments
Post a Comment