https://micromouseonline.com/micromouse-book/robot-dynamics/...
https://micromouseonline.com/wp-content/uploads/2015/06/MINO...
299 karma · joined June 30, 2018
https://micromouseonline.com/micromouse-book/robot-dynamics/...
https://micromouseonline.com/wp-content/uploads/2015/06/MINO...
In particular, in A*, the "to be explored" queue has to be kept sorted. This sorting dominates the compute time.
For example, using the "flood fill" method on an 8-bit processor, depending on the state of the maze, it took less than 3milliseconds (hand optimized assembly) to solve a maze. On a Cortex M4, with decently thought through maze representation, but not optimized beyond that, it takes under 1.5milliseconds. This is in the "don't need to bother" category.
This is a great article to start from: https://dl.acm.org/doi/10.5555/26011.26020
PDF version of this can be found online.
What we have done is extended it to be time based rather than distance based i.e. we take into account the motion parameters - acceleration, maximum speed on the straight and through different turns, distance and use that together to generate a cost table and then use the cost table to generate the fastest path.
Currently mice use reflective infrared sensors. The reflected infrared light is used to estimate the distance. Based on this reading, one can determine the position of the mouse and the presence/absence of the wall. This information is used to create a maze map and to navigate.
The Circuit Cellar article mentioned in this thread is an awesome comprehensive introduction to micromouse.
I'll watch this thread for more questions.
Funny story - I was in college and the IEEE chapter was having a meeting with free pizza. I went to the meeting but went into the wrong room and in that room they were having the Robotics club meeting. I was intrigued enough to sit through it and wanted to do this. One of the the presenters said that no one had yet made a working mouse at our college. I was determined that I would be on the team that was the first. And we were!
FIRST is a fine competition.
With the use of a fan, the limit is now how much down force can you generate and then can you drive the wheels to take advantage of that. And then how much time do you have to maximize this loop.
I think one can be made for under $50 USD.
MCU: $5 PCB: $5 Sensors: $8 Motor driver: $3 Battery: $5 Misc. electrical components: $5 Motors: $4 3D printed parts: $15
I could use the routines that the MCU manufacturer provides but when I've tried, I've found that I spend a large amount of time understanding the API and what they are doing and writing the drivers myself is faster.
Take a look at this code base: https://github.com/ukmars/ukmarsbot
Please take a look at the repos at:
https://github.com/ukmars/ukmarsbot <- this mouse was shown in the Veritasium video. It is exceptionally low cost and easy to assemble, source parts for and there is enough code in the repo to make good progress.
I hope you do this!
For Micromouse, there are several methods people use. One is to create a trapezoidal angular velocity profile while holding the forward speed constant. The trapezoidal profile parameters are determined through iterative simulation.
Another approach - the one I use - uses cubic spirals which is described in: Smooth Local Path Planning for Autonomous Vehicles by Yutaka Kanayama and Bruce I. Hartman. What is amazing about this technique is that it is closed form, is like four or five multiply and adds and executes in trivial time on (even) an 8-bit processor. For my latest entry, I have a more sophisticated scheme where I try to maximize the load on the tires and the lateral and longitudinal loads are asymmetric.
In this article: http://www.dtweed.com/circuitcellar/xottenda.htm#183 - David Otten describes a scheme where he controls the rotational velocity such that the load on the tires is maximised.
I think you can get very far with simulations and then trying it on a RC car and then on a real car.
A few years back, there was some amazing work that was done at Stanford where they developed tire models and a controller that could handle sliding modes.
I encourage you to explore because if nothing else, you will learn.
Happy to answer questions.
Ditto for Artemis.
I haven't checked but I think there were a couple others, too.
https://en.m.wikipedia.org/wiki/Action!_(programming_languag...
There were fewer outlets for information but they were of high quality. So, the "signal to noise ratio" was significantly better.
As others have mentioned the systems were simpler and therefore more understandable. This meant that people's creativity really came out. Look up copy protection or how people cranked up the speed of the disk system on the C64 or Atari or Apple.
Tools cost money - free compilers or assemblers were few and far between. The syntax and usage was simpler and compile times were quite low.
There was no memory protection, so, the application you were development could easily take down your development system.
I really want to find something that has good attributes so that I minimize the learning of bad habits.
I'm speculating but I think the reasons it veers to the right are some combination of the following: 1) There is water on the left hand side of the lane. I was going back and forth on the video and you can see "Raining" along the left edge turn green. So, it has detected the water and is avoiding it? At the same time it has turned green "Wet road". 2) There is a vehicle on the right side of the lane - it has been identified with an upside down green triangle / crosshairs and a square (is that block the license plate?) and the Tesla is "following" it.
Again speculating based on watching the display change.
I found this clip amazing for the following reasons: a) Around 0:02, it starts to notice the right edge of the road. Along the right edge of the video, you can see the estimated road. Around 0:04, you can see the right turn lane and the dots along the right edge change to show the vehicle has detected it. b) Detection of arrows on the road surface. They are labeled with "RA", "FA" and "LA". RA = Right Arrow, etc. c) Around 0:04, a "container" type of black outline appears on the right edge - it is a vehicle! d) Around 0:05, another container appears in the right turn area and it is another vehicle. e) Around 0:09, another container appears on the left middle and it is another vehicle.
Jumping to 0:22: f) It has seen the vehicle about to enter the scene from the left and "CutinExcited" probability starts to increase and when the vehicle has moved through the scene, it goes away. g) If you see the frame at time 28668.2612540 (?), it has picked up and classified a person on the left of the red 44.
Super impressive real-time classification.
Summary of steps are:
A) Create Windows image with stuff I don't want removed
B) Create Windows settings and clean up script
C) Clean install using step A but do it with a local account [1]
D) Clean up Windows using script from step B
E) Rename PC
F) Connect to Microsoft account - this will bring over settings from your other Windows PC(s)
F) Install software using Chocolatey
Over time, as I make further changes to my setup, I usually apply them manually and then incorporate them into either step A or step B.
Steps for A:
A1) Download ISO from Microsoft. For an example on how to do this, see instructions at: https://pureinfotech.com/download-windows-10-iso-without-media-creation-tool/
A2) Create script for removing unnecessary items and then apply them to the Windows ISO image from step A1. I use: https://github.com/DrEmpiricism/Optimize-Offline to modify the Windows ISO image.
A3) Use Rufus or similar tool to create bootable USB drive from image from step A2.
A4) Clean install Windows.
A5) When creating the image in step A2, you can add scripts that end up in c:\windows\setup\scripts. Run these scripts
Steps for B: B1) Use script from https://github.com/Disassembler0/Win10-Initial-Setup-Script and customize it to your liking
[1]: If you install with a Microsoft account, your user directory is the first five letters/numbers of your Microsoft account. When installing using a local account, the local account name, in its entirety is used.edit1: fixed formatting.
I'd love to switch to Vim...