SHENZHEN I/O

SHENZHEN I/O

Not enough ratings
MICRO-COPTER MK2
   
Award
Favorite
Favorited
Unfavorite
File Size
Posted
7.455 KB
2 Mar, 2018 @ 2:41pm
1 Change Note ( view )

Subscribe to download
MICRO-COPTER MK2

Description
9 Comments
anton.kurkin  [author] 15 Mar, 2018 @ 5:44pm 
Here is another version of the puzzle (it was surprisingly easier to solve and much harder to create spec than for Mk2)
http://gtm.steamproxy.vip/sharedfiles/filedetails/?id=1332119062
pv2b 3 Mar, 2018 @ 12:40pm 
In the end, me and anton.kurkin were able to put our brains together and produce what neither of us could alone - a 9/1440/27 solution. The board layout made that difficult but not impossible!
anton.kurkin  [author] 3 Mar, 2018 @ 8:18am 
Well at least I optimized my solution using automaitic limits of simple output [0; 100] to 12/1803/33
anton.kurkin  [author] 3 Mar, 2018 @ 6:30am 
Damn, I'm pretty sure you're using 200P-14 ROM with ternary double-digits and dst them somehow, but I totally failed to do that :D
pv2b 3 Mar, 2018 @ 6:07am 
Welp, I thought I was done, but nope. 11/1680/30. At this point I don't think there's any better solution, at least not with my current approach. :-)
pv2b 3 Mar, 2018 @ 5:57am 
Turns out there's some room for optimization after I realized one component was potentially unneccessary. Now I'm down to 11/1800/32 and I have no issues with board space whatsoever.
anton.kurkin  [author] 3 Mar, 2018 @ 5:41am 
Ha! my only solution is 16/2040/40!
Glad you like it. I have another idea so maybe Mk3 is coming sometime later. That is if I'm able to solve it...
pv2b 3 Mar, 2018 @ 5:28am 
My best solution: 15/1859/33
pv2b 3 Mar, 2018 @ 5:27am 
This required a completely different approach than MK1, but it was fun to solve. It looked a little daunting until your realize that motor0 = 100-motor3 and motor1 = 100-motor2 . Just like MK1, the limited board space does mean you have to get a bit creative with component placement to get all the components to fit properly.

Hint 1: Consider ternary numbers!
Hint 2: Don't forget about tcp!