Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
What other robots do we need in "demo"?
See original GitHub issueDo you guys think we could attract more users to ev3dev if it shipped with working code for the base ev3 robot designs? @dlech would you be open to including a /home/robot/demo/ folder in ev3dev?
Of the 5 base models we have three of them
- TRACK3R (done)
- SPIK3R
- R3PTAR (done)
- GRIPP3R (tank)
- EV3RSTORM (done)
The 12 fan models are
- BOBB3E (tank)
- BANNER PRINTER
- RAC3 TRUCK (tank)
- DINOR3X
- KRAZ3 (tank)
- EV3D4 (done)
- ELECTRIC GUITAR
- EV3MEG (tank) - looks like a line follower which we do not have a demo of
- EV3 GAME
- MR BEAM
- ROBODOZER (tank)
- WACKEM
For all of the Tank robots the only real thing to program for any of them would be controlling the medium motor and we have examples of this in our TRACKER and EV3D4 demos. So not sure there would be a ton of gain but they also wouldn’t be much work (ignoring construction time). The exception there would be EV3MEG since it looks like a line follower.
I’m not sure how popular all of these others are. I built SPIK3R once but the controls on it were very clunky. I also built WACKEM, it was neat just because it was very different.
thoughts?
Issue Analytics
- State:
- Created 6 years ago
- Comments:17 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
high level 😃
Results of the poll I posted on the EV3 group on facebook. I did not know that EVERSTORM was that popular, I imagine being the build on the box is a significant factor.