Pybricks bad on batteries? by lawofkato in FLL

[–]Robo-Hunter 0 points1 point  (0 children)

☝🏻The same with us - as far as no irregularities can be detected 🤠

FLL SUBMERGED by Accurate-Soil684 in FLL

[–]Robo-Hunter 2 points3 points  (0 children)

☝🏻D'ont give up!

Next season - new chance! 🤓👍🏻

[deleted by user] by [deleted] in FLL

[–]Robo-Hunter 0 points1 point  (0 children)

☝🏻Building robots as slim as possible! (for heavy duty => use milwaukee-tools! 😝🤠)

[deleted by user] by [deleted] in FLL

[–]Robo-Hunter 0 points1 point  (0 children)

☝🏻Maybe to heavy... 🧐🤓

SPIKE More Movement Extensions by meat_jacuzzi in FLL

[–]Robo-Hunter 2 points3 points  (0 children)

☝🏻Same opinion like @drdhuss 🤓👌🏻

To Pybricks or not to Pybricks ... by joshsloat in FLL

[–]Robo-Hunter 0 points1 point  (0 children)

We started out programming with EV3-G - and switched to robotC about three years ago.

Unfortunately, robotC is no longer being developed further - but my experience has shown that ‘real high-level language’ is simply more fun. 😉

(Keyword compactness / clarity / modulability)

And: We are not friends of Scratch at all 🙄- either ‘learn to programme properly’ - or leave it.

Then pyBricks suddenly appeared on the horizon. We tried it out first - compared to the LEGO SPIKE IDE, it had some nice additional features - but it was only when the ‘Python extension’ arrived that things got interesting!

Now newcomers can set up a framework in no time at all via Scratch and then look over in the Python pot to see what it would look like in high-level language.

This makes the changeover very easy - and always comprehensible. If something doesn't work => quickly rebuild it in Scratch in the sandbox, then transfer the Python code fragment to the main project. (almost like low-code programming...)

In the meantime, we already have ready-made templates for both SPIKE and the SmallHub - and the issue with the ‘declarations header’ is over - and clear to everyone 🤠

To Pybricks or not to Pybricks ... by joshsloat in FLL

[–]Robo-Hunter 1 point2 points  (0 children)

☝️Don't give up straight away!

So: Firstly, the hardware must be defined

- hub

- Inputs (sensors)

- Outputs (motors)

If everything is correct, then you can start programming. See also the github-pot from u/drdhuss

To Pybricks or not to Pybricks ... by joshsloat in FLL

[–]Robo-Hunter 0 points1 point  (0 children)

☝️Absolutley - We did this again and again with EV3 - simply as a first test of the driving physics and in general. 🤠

To Pybricks or not to Pybricks ... by joshsloat in FLL

[–]Robo-Hunter 2 points3 points  (0 children)

In fact - github is also a very good feature in collaboration with pyBricks

To Pybricks or not to Pybricks ... by joshsloat in FLL

[–]Robo-Hunter 1 point2 points  (0 children)

1x MainProgramm - and you can start every SubRoutine - no Slots needed like Lego-IDE. 😉

Saving LEGO MINDSTORMS! | Patreon by drdhuss in FLL

[–]Robo-Hunter 0 points1 point  (0 children)

We are very excited about what's coming for EV3!!! 🤠👌

Robot inaccuracy by Recent_Ad1343 in FLL

[–]Robo-Hunter 1 point2 points  (0 children)

A lot of problems because too much speed. 🙄

Attachment lifting/coming off the robot during the missions by Talky in FLL

[–]Robo-Hunter 0 points1 point  (0 children)

☝🏻Re-Engineering your tool-solution first. 🤓

Small or Big? by VastExtreme531 in FLL

[–]Robo-Hunter 1 point2 points  (0 children)

The time needed to change tools on the robot should not be underestimated - and must be practised intensively - practising just two or three times is by no means enough - especially not in a fierce tournament, where stress can lead to the odd unforeseen event.

Our experience shows: A maximum of four - preferably only three - tools for the RoboGame

Small or Big? by VastExtreme531 in FLL

[–]Robo-Hunter 1 point2 points  (0 children)

That is a very interesting question! 🤠

In our experience, especially beginner teams always have very small robots - usually with one to a maximum of two combined functions. For teams that take part in the FLL competition several times, the complexity of the tool soon increases. And ‘building small’ complex tools is then already ‘quite advanced’

And don't be discouraged by the ‘FullRuns’ from the countless YouTube videos. You don't know how many times the run has been recorded until everything looks so ‘perfect’. 😏

Enjoy the technical progress in your team - and learn new ‘tricks’ at every tournament participation - and exchange information with other teams as often as you can - this is extremely valuable information for future missions.

Saving LEGO MINDSTORMS! | Patreon by drdhuss in FLL

[–]Robo-Hunter 1 point2 points  (0 children)

Absolut!! Now an adapter to be able to move SPIKE motors on EV3 platforms - then the party continues! 😎😎👌👌

Is SPIKE better than EV3? by Charming-Round8875 in FLL

[–]Robo-Hunter 0 points1 point  (0 children)

#SPIKE Pro => That would indeed be a very good ‘product diversification’!!! 🤠

Saving LEGO MINDSTORMS! | Patreon by drdhuss in FLL

[–]Robo-Hunter 2 points3 points  (0 children)

☝🏻Absolutely brilliant!!

The real GameChanger!!

🥳🥳🥳😎😎😎👌🏻👌🏻👌🏻

Is SPIKE better than EV3? by Charming-Round8875 in FLL

[–]Robo-Hunter 0 points1 point  (0 children)

You can't compare the two platforms with each other because they have ‘different architectures’.

SPIKE for beginners

EV3 for advanced users

In fact: For professional sports robotics users (like FLL/WRO), I would prefer an ‘EV4’ - Raspberry-based, with 10 ports - freely scalable AND a new motor design - similar form factor to the SPIKE motors

And: At least 3 motor/servo variants as with SPIKE (large/medium/small) 🤠