@davecrawley today I was finally resume the testings on the robot! The robot stand still for the last 3weeks with no one touching him! But today when I press both the buttons to turn it on I hear a noise and saw a sparkle from the board! But the robot remained on! But I can’t do anything! Even connecting the monitor directly to the HDMI port the robot seems dead! But all the lights are normal! When I made an visual inspection I noticed that this resistor may have burned! But I can’t tell! Can you see in the picture? Later I will disassemble the main board to make a thorough inspection! This is bad I was so hyped to resume the testing and this happens

The part you highlight is the real time clock. They’ve never been known to fail - but there is always a first time. Also the good news is the robot should operate without it - however if it fails badly then it could short out the power and cause all kinds of problems.

Please do the following initial checks.

Make sure there are no stray metal parts (Screws, stray wires etc.) making contact with either the rear side of the connector to the sonar board or to the under-side of the sonar jack.

Turn on both the motor and main power - see if the wheels are mostly locked in place and see if they resist movement. When you try to turn the wheels with you hands you should feel resistance and the wheels should move back mostly to to the original position on their own.

Check to see if the LED lights above the switch board are on. All 5 lights should be on the top light should blink briefly every 6 seconds.

Let me know how you get on and we can help you. If the above are fine then.

Power on the robot and see if you can log in to to the robot - I am guessing that the answer is no.

If you can’t log in to the robot, disconnect the Pi and plug it in to a separate power supply (e.g. a phone charger) and try to see if you can connect to the raspberry pi by itself. If you can’t the Raspberry pi is probably dead. We’ve seen the raspberry pi spontaneously fail a few times, the good news is they are easy to replace.

If the raspberry pi has failed we’ll need to replace it - let me know if you’d like me to order a new one for you.

If the raspberry pi has not failed but you aren’t able to log in when its connected to the robot then the fault is on the motor board, and we’ll have to repair it. email dc@ubiquityrobotics.com and we’ll arrange a return. You can try removing the damaged chip yourself if you like - if that’s the only failure the robot will work - however it will not keep an accurate clock. This might not affect you, though it can affect some other operations.

@davecrawley the pi on the robot was randomly creating aproximately 100log files per second, and that was the case, i manage to fix that! The sd card is genuine 32gb kingston class 10 hc! I will try now again now that i believe all the problems are solved!

@alexis i know ive promised a time-lapse but i was not able to do it in the time being, i will let a video here with the robot doing a complete path on my garage, basicaly the magni do this in 12+ straight hours. On my final project the robot will do the exact same thing, but on a bigger space, and it will have “checkpoints” to precise localization every 10meters, and “stop points” where it will stop for 2 minutes for loading purposes!

My objective is to put 7/8 robots in line, every one following the robot in front of him, like a train!

Im very optimistic, and i believe i have the project 90% complete! Right now im waiting for the final warehouse to be finished to start testing on the production scenario!

BTW this is not the final cabinet! The final cabinet is gona be made in “T-Frame Aluminium”, again, this is for tests only

@davecrawley the problem of the device running out of space its related to a bad script i have running on the magni´s pi! Its not ubiquity vm image related!

When i have no map, i´ve used the robot commander android app to generate the first map, with a couples of times passing by all the fiducials with 0.3/0.3 on the linear/angular speed seted-up on the app!

Then i´ve put the robot in automatic-loop mode passing for all the fiducials using the @alexis script at the same velocity for aproximately 10hours/day! Then when i believe i have a good map i put the map in “read_only” mode and its done!

@davecrawley can you help me with this question? i have an emergency stop button i would like to attach to the magni board in order to shut-him down if an emergency occur! Can you or someone guide me trough that?

Although before you do this - check to see if you get E-Stop functionality on your Magni currently. The Red button on your power board should stop the motors from driving - although some people from the first batch had trouble with this functionality working.

You’ll need to remove the switch board and put your big red button in place of the red switch on the switch board.