Transpotter: Difference between revisions
No edit summary |
|||
Line 31: | Line 31: | ||
[[File:300636B8-9384-4E0C-A36E-5E547FEC40C0.jpeg|200px]] [[File:9613A0EC-681C-4E41-90F1-7C75919AA4B1.jpeg|200px]] | [[File:300636B8-9384-4E0C-A36E-5E547FEC40C0.jpeg|200px]] [[File:9613A0EC-681C-4E41-90F1-7C75919AA4B1.jpeg|200px]] | ||
==Update== | |||
[[File:3A27934D-5EA2-412C-8B84-31F043CE65AC.jpeg|200px]] [[File:67501B27-150C-4F55-933B-4A38721E0F3A.jpeg|200px]] [[File:13F5071F-C9A1-4AFF-9299-C70D6B1143A7.jpeg|200px]] | |||
Installed the GameTrak in a nice sturdy box so it's a little bit more safe to use and hopefully this sensor won't break. Next up is an emergency stop! | |||
==Videos== | ==Videos== |
Revision as of 23:56, 2 February 2019
Project Transpotter | |
---|---|
Status | In progress |
Contact | Sebastius |
Last Update | 2019-02-02 |
Safety
Please note that Hoverboards are very dangerous and way overpowered toys. Some of the dangers:
- Motors are really powerful and when the firmware glitches or a sensor fails, you will lose control and cause accidents
- Most batteries are horrific and will flame, burn, explode or cause other misery during charging, usage or just whenever the damn thing feels like exploding.
- Most controllers are built with the cheapest parts and will burn
Be careful and NEVER charge a hover board unattended.
Story
I found an interesting talk on Moving Objects by JanHenrik and NiklasFauth: https://media.ccc.de/v/gpn18-95-howto-moving-objects which was very instructive on how to build a software driven movable platform. You could build it with a chair on top or just a sheet of plywood and use it as a transporter. The simplicity of it and the really low price point of broken hover boards got me convinced i should build a movable object!
Purchasing
Broken hoverboards can be bought cheaply. These two (User:F0x got the other one) we purchased for 15 euro's each and were brand new DOA's (dead batteries in both, and one had a gyro issue). So the motors were never used!
Initial experiments
To test the microcontroller and motor-drivers i first made a rig for testing and uploaded the firmware. I could control motor speed with two potentiometers!
Construction
Two sheets of 18mm plywood, 40cmx60cm. Two old caster-wheels in front, the motors in the back. I used the old metal frame to mount the motors and electronics and the pink fenders were reinstalled for extra safety and because they look awesome. The fenders add two safety features: protect a rider from the wheels and in the event of an uncontrollable speed you can just flip it over and disconnect the battery. Metal frame was cut down to size and i cut a few centimeters of one of the plastics to make it fit the 40cm width of the board.
Update
Installed the GameTrak in a nice sturdy box so it's a little bit more safe to use and hopefully this sensor won't break. Next up is an emergency stop!
Videos
https://youtu.be/mWy38XpZTqE - My first test with two cases of Mate on top and using the GameTrak sensor.
Resources
- https://media.ccc.de/v/gpn18-95-howto-moving-objects - Video on how to get started with your own moving object
- https://github.com/NiklasFauth/hoverboard-firmware-hack - firmware. Please note the Transpotter is in a separate branch!
Future plans
- Replace the capacitors with properly made ones ;)
- Maybe write some more safety features, like something to detect loss of signal with nunchuck or Gametrak, and prevent immediate acceleration. Or maybe slow down the acceleration-curve a bit.
- Do a nicer bit of woodworking, maybe laser-engrave the top, add something to attach a seat easily
- Make a proper connection box for software updates, battery-disconnect (emergency stop?) and wii nunchuck connector
- Maybe some waterproofing
Accident log
Break right!
When riding while someone was controlling the transpotter with the gametrak sensor, the board did two hard rights, the second causing the rider to fall of and nearly smash an arm or some teeth. Luckily the rider was made of rubber and springs ;)
Cause: probably related to the breaking of the gametrak (see below)
Thoughts: software needs to think a bit about sudden increases in speed. Maybe do some more measurements and compare?
Burnout
Yeah i caused a burnout on the space-floor. The Gametrak broke, and the board went into full power against a post.The damage was done in under ten seconds...
Cause: A disconnected distance sensor causes the motors to go full speed.
Thoughts: software needs to cease function when gametrak breaks, failing high (internal pullup?). Maybe install pulldowns? Speed-limits? Might want to invert the gametrack that infinite resistance (HIGH input) will cause lowest speed (standing still)