| 18 | | Time Schedule for the technical challenge “!StartUP” |
| 19 | | Like RCLL, the TC “StartUp” should last over 3 days. Additionally, 2 setup days are available. A skill sequence should not last longer than 15 minutes including preparation time of playing field and setup of the team. This should allow 4 sequences in one hour. If the first two days are from 9.00 to 19.00, 80 skills-slots would result (If needed). If we assume that 10 teams participate, then over 8 timeslots would result per team. |
| | 20 | == Time Schedule for the technical challenge “StartUP” == |
| | 21 | Like RCLL, the TC “!StartUp” should last over 3 days. Additionally, 2 setup days are available. A skill sequence should not last longer than 15 minutes including preparation time of playing field and setup of the team. This should allow 4 sequences in one hour. If the first two days are from 9.00 to 19.00, 80 skills-slots would result (If needed). If we assume that 10 teams participate, then over 8 timeslots would result per team. |
| | 22 | |
| 36 | | Possible Rules: |
| 37 | | General |
| 38 | | - Each team can choose the skill before the start (to define lead time) |
| 39 | | - The exact rule is defined in the skills rule |
| 40 | | - Once a skill has been successfully passed, it may no longer be chosen. |
| 41 | | - If a skill has started, one maintenance per robot is possible (Like RCLL). |
| 42 | | - For communication, we assume that OPC UA, the industry standard, will be used in the future. |
| 43 | | - The tags used to recognize the stations are based on the tags of Roboview (AR tags, the “dll” exist) |
| 44 | | - Whenever possible, the standard Refbox should be used so that no 2nd Refbox has to be programmed and maintained. For some crossover challenges an adaptation will be needed. |
| 45 | | Area |
| 46 | | - The skills area is about 5mx5m with 25 square zones 1mx1m, just like RCLL |
| 47 | | - Ideally, no boarders are used for the TC. If necessary, 2 boards of 1m each are installed in the corner area S11, S15, S55, S51. |
| 48 | | |
| 49 | | Points |
| 50 | | - A successfully completed skill cannot be repeated. |
| 51 | | - If 2 or more teams have the same number of points, then whoever has reached the highest level in an exercise wins, or if this is the same, whoever has more of higher levels wins. |
| 52 | | - If the robot leaves the game area (out of the border the skill is not fulfilled) = 0 points |
| 53 | | - If the robot touches an obstacle, for each obstacle -5 points. |
| 54 | | Flexibility of different organisations |
| | 42 | |
| | 43 | == Possible Rules: == |
| | 44 | * General |
| | 45 | - Each team can choose the skill before the start (to define lead time) |
| | 46 | - The exact rule is defined in the skills rule |
| | 47 | - Once a skill has been successfully passed, it may no longer be chosen. |
| | 48 | - If a skill has started, one maintenance per robot is possible (Like RCLL). |
| | 49 | - For communication, we assume that OPC UA, the industry standard, will be used in the future. |
| | 50 | - The tags used to recognize the stations are based on the tags of Roboview (AR tags, the “dll” exist) |
| | 51 | - Whenever possible, the standard Refbox should be used so that no 2nd Refbox has to be programmed and maintained. For some crossover challenges an adaptation will be needed. |
| | 52 | |
| | 53 | * Area |
| | 54 | - The skills area is about 5mx5m with 25 square zones 1mx1m, just like RCLL |
| | 55 | - Ideally, no boarders are used for the TC. If necessary, 2 boards of 1m each are installed in the corner area S11, S15, S55, S51. |
| | 56 | |
| | 57 | * Points |
| | 58 | - A successfully completed skill cannot be repeated. |
| | 59 | - If 2 or more teams have the same number of points, then whoever has reached the highest level in an exercise wins, or if this is the same, whoever has more of higher levels wins. |
| | 60 | - If the robot leaves the game area (out of the border the skill is not fulfilled) = 0 points |
| | 61 | - If the robot touches an obstacle, for each obstacle -5 points. |
| | 62 | |
| | 63 | == Flexibility of different organisations == |
| 60 | | Skill-Definition-Sheet |
| 61 | | Nbr 11 Topic Driving |
| 62 | | Points 10 Robots 1 |
| 63 | | Setup 5 min. Game 5 min. |
| 64 | | Skill-Description Driving the robot in 2 different field-squares with a defined orientation and move back to start position. The robot should hold its position in the square for at least 5 seconds. |
| 65 | | At the start of the setup-phase, the squares and alignments of the positions to be approached are communicated to the team |
| 66 | | Skill-Example |
| 67 | | Fulfilled If the Robot positionned (square and orientation) it self on the two position from the startpoint and get back to the endpoint within the 5 minuten. Manual interaction only permitted in setup phase and maintance. |
| 68 | | Additional |
| 69 | | Information First position in the zone S12 to S53, second position in the zone S14 to S55 |
| 70 | | 36 szenarios are prepared, they are choosen by throwing two times a dice |
| 71 | | One maintenance permitted |
| 72 | | Used material Gaming field |
| 73 | | 36 scenarios (Nbr 11) |
| 74 | | 1 dice |
| 75 | | |
| 76 | | |
| 77 | | |
| 78 | | Skill-Definition-Sheet |
| 79 | | Nbr 12 Topic Driving |
| 80 | | Points 30 Robots 1 |
| 81 | | Setup 5 min. Game 5 min. |
| 82 | | Skill-Description Driving the robot in 2 different field-squares with a defined orientation and move back to start position. The robot should hold its position in the square for at least 5 seconds. On the field are two station aligned. |
| 83 | | At the start of the setup-phase, the squares and alignments of the positions to be approached are communicated to the team. Also the positions of the two stations (dummy) are communicated at the start of the setup-phase |
| | 69 | == Skill-Definition-Sheet == |
| | 70 | ||Nbr ||11 ||Topic ||Driving|| |
| | 71 | ||Points||10 ||Robots||1|| |
| | 72 | ||Setup ||5 min.||Game ||5 min.|| |
| | 73 | * Skill-Description |
| | 74 | * Driving the robot in 2 different field-squares with a defined orientation and move back to start position. The robot should hold its position in the square for at least 5 seconds.[[br]] |
| | 75 | At the start of the setup-phase, the squares and alignments of the positions to be approached are communicated to the team |
| | 76 | * Skill-Example |
| | 77 | * Fulfilled |
| | 78 | * If the Robot positionned (square and orientation) it self on the two position from the startpoint and get back to the endpoint within the 5 minuten. Manual interaction only permitted in setup phase and maintance. |
| | 79 | * Additional Information |
| | 80 | * First position in the zone S12 to S53, second position in the zone S14 to S55[[br]] |
| | 81 | 36 szenarios are prepared, they are choosen by throwing two times a dice[[br]] |
| | 82 | One maintenance permitted |
| | 83 | * Used material |
| | 84 | * Gaming field |
| | 85 | * 36 scenarios (Nbr 11) |
| | 86 | * 1 dice |
| | 87 | |
| | 88 | == Skill-Definition-Sheet == |
| | 89 | ||Nbr ||12 ||Topic ||Driving|| |
| | 90 | ||Points||30 ||Robots||1|| |
| | 91 | ||Setup ||5 min.||Game ||5 min.|| |
| | 92 | * Skill-Description |
| | 93 | * Driving the robot in 2 different field-squares with a defined orientation and move back to start position. The robot should hold its position in the square for at least 5 seconds. On the field are two station aligned.[[br]] |
| | 94 | At the start of the setup-phase, the squares and alignments of the positions to be approached are communicated to the team. Also the positions of the two stations (dummy) are communicated at the start of the setup-phase |
