Of course! Here is the link to all the documents. Use the battery holder, Driver station v2 holder, and controller holder tabs. The assembly has the old driver station holder but you can see how it all goes together. cad.onshape.com/documents/6a0437b49bf8e8ddade3d5cf/w/4adeac444df26fd6459667da/e/894719eea4b0ebcb18b87526?renderMode=0&uiState=65c426dad67c07490233ad08
Sorry but can anyone explain this to me At 2:54 , i can see that 3 first Pixels (1 white and 2 yellow) have been counted as backdrop point, 5pt each But then in the Driv-ctrled, they counted all 30 pixels on the backdrop (3pt each) So that mean the first 3 pixels have been counted as backdrop point 2 time, 1 at auto and 1 time in driv-ctrled So my question is, is it normal? I have both manual but maybe im missing some rule, language barrier thing
This is the way scoring works in this game. Pixels on the backdrop at the end of Auto are worth 8 points (5 for auto and 3 more for teleop) if you don't knock them off before the end of the game. See GM2 for more details. Thanks!
Our coach is a programmer and he used codehs.com/ to teach us Python last summer. Once we knew Python, we spent the last part of the summer creating a code library for our robot based on Pybricks and testing it.
We do not. Instead, we rely on good wheels, a balanced robot, smooth acceleration (thanks Pybricks!) and light sensors in all 4 corners of our robot. Thanks for the question. You can see more about our robot design here: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-F3gmzGW3fWI.html
@@bernardoloures9848 We do a proportional line follow for a very short time on the way down to the treadmill but that is the only one. Mostly we use the light sensors to detect distance and to "square" the robot on lines to adjust both distance and heading. Thanks for the great questions.
Hi!!!!! I see you guys are also doing robotics this year, so good luck!!! My team was wondering if you guys would want to get together and do a fun core values exercise?
Hi! We have been getting together with other teams to do Q&A sessions on our approach to FLL. We could maybe do something with your team as well. Please contact us using our website: sites.google.com/view/failurearchitects/home
Thanks for asking! We don't use a gyro. Instead, the combination of our wheels (znap 41mm), the build of the robot, and smooth acceleration (thanks to Pybricks) allows our robot to move in a very consistent manner. This allows us to use 4 light sensors in the four corners of the robot to find, follow, and square on lines, which we do almost all the time. For more on this, you can check our Robot Design Judge Presentation Video: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-F3gmzGW3fWI.html
We are sorry to say that there was no broadcast. We only had a Southern California Championship which was completely remote. But they did have one "live" round when the referees watched us do the robot game and scored it. We got 580 on that round. Our pre-recorded run was 600 which was tied by another Southern California team, but our live round score was the highest.
Hey Everyone, we are getting lots of interest in our robot work this year. If your team would like to meet with ours for a Q&A session about it, we are happy to try and do that via zoom. Your coach can contact us using our website contact form at sites.google.com/view/failurearchitects/home
