First attempt at floodfill based Micromouse (Arduino nano) (Link to code in Description) 

Thanks!

The bot does use PID for wall following (pid is used on both the ir sensor reading and the encoder reading) Threshold is only used for detecting walls after the bot has reached the centre of a block and wants to scan its surrounding walls.

@@pranjalagrawalrobotics in your code i could see that you are calculating error based on encoder count difference and computing the pid value from that. And then computing wall error as difference between left and right ir sensors. Wall error +/- pid error+/- constant speed is the final output. Wall error is not from pid , it's computed directly. I was curious to know why no pid for ir sensor and only for encoder count

@@suricool99 just checked, and yeah, you’re right, I misremembered. Basically, what happened was that we started working on the bot around a week before the competition. In fact, we were still working on it on the day of the competition. We simply ran out of time and weren’t able to tune the PID for the sensors and so we computed it directly.

@@pranjalagrawalrobotics we are also in a similar situation. We have got the constant speed part and wall follower part to work independently. We are stuck at a place where we are struggling to combine both speed/position based control along with wall follower pid control . Do you have any suggestions? How can we do this. ?

@@suricool99 I can’t be sure, since I never got around to implementing pid for the ir sensors and combining it with the encoders, but maybe you could try computing the pid value from the ir sensors and encoders independently and then combine them in a ratio you tune. Like, instead of directly adding/subtracting either the encoder pid value or the ir sensor pid value, you could compute smth like (0.7*ir_pid + 0.3*encoder_pid) and add/subtract that from the speed. I would assume that giving a higher weightage to ir sensors would work slightly better since they can actually sense and avoid the walls whereas if you start off slightly off angle, the encoders would be fighting to drive you closer to the walls.

I think atleast 3 are needed. One for each of the side walls and one for sesing the front wall. Wall following will be pretty tough though woth so few sensors. With 4, you could place two directly perpendicular to the side walls and two slightly angled. Although, this setup may have difficulty identifying the front wall in time. 5 really is convenient.

I used this simulator - github.com/mackorone/mms They have provided code to connect the simulator to an arduino. In the arduino code, you can simply make calls to the provided simulator API instead of the motor driver and similarly make calls to the API instead of reading data from the sensors,

@@pranjalagrawalrobotics can i have your eg code in mms , thanks for replied

Code

@@m4s0314 drive.google.com/drive/folders/1xG0jK4TJxe-gcxNtGWqhTgi0iRqMKp3k?usp=share_link The code modified to work with the simulator is older though

@@komilelmurodov3401 drive.google.com/drive/folders/1xG0jK4TJxe-gcxNtGWqhTgi0iRqMKp3k?usp=share_link

The bot stopped at the centre because I have set it as the target. I haven’t programmed the bot to return to the start point so it stopped once it reached the target. The bot constantly updates its map of the maze as it explores. Hence, each subsequent run is better than the previous until the maze is completely mapped out. Hence, I restart it from the start point so that it can explore more and find better oaths (as it did!) You can learn more about floodfill and other maze solving algorithms here - www.123seminarsonly.com/Seminar-Reports/038/59360985-Maze-Solving-Algorithms.pdf, marsuniversity.github.io/ece387/FloodFill.pdf

@@pranjalagrawalrobotics that's helps thanks

IR Sensor to measure distance

As stated in the title, the link to the code is in the description.

The code should work as is, though you should check how much ram the uno has. If it is less than the nano then you may have to modify the code a bit.

@@pranjalagrawalrobotics and how to make it learn the make and fix the finish point to find the smallest path

@@pranjalagrawalrobotics hey bro i checked your coed and tried to verify it but its showing an error that the encoder is missing. how do i solve it.

In coding he just follows the right wall

@@cowboygamer6980 I know it's wall follow algorithm, but I want to know how does it determine the goal position?

@@cowboygamer6980nah, this uses the floodfill algorithm, not the wall following algorithm. That’s why it takes two completely different paths in the two runs.

@@rexcode9366it knows it’s starting position and that the goal is as the centre. It doesn’t know the wall layout.

@@pranjalagrawalrobotics yeah, I saw your GitHub repo. Can you make a tutorial on it, explaing in detail

I am using 600 rpm micro metal gear motors. .h files are called header files

@@pranjalagrawalrobotics thanks

are you using encoder motor ?

@@kinhkong69z62 Yes

can you please provide the link to buy this motor, also what batteries are you using @@pranjalagrawalrobotics​