Skip to main content

Non-elegant programming solution

Here's the problem: I have a bot that uses motor B and an arm to lift a heavy item. The motor is powerful enough to lift the item. After the item is lifted, the bot program continues on its way (maybe moving forward or backwards or moving into a LOOP block with a sensor trigger.) The problem occurs after motor B completes its lifting motion. As soon as the program moves forward, the weight of the heavy object causes motor B to spin in the opposite direction (gravity, not powered) and the arm (and object) slowly lowers (sometimes quickly).

So my next solution was to put motor B's action in parallel with the rest of the graphical code. I created a branch off of the main one and put motor B there... but here's the next problem. I can either program motor B to spin (rotation or degrees) in an Unlimited fashion, BUT I must have something for motor B to lift the item against and then when it hits, keep applying upward force (motor B still running, but the motor isn't actually spinning). This might work, but I actually need the item held parallel to the floor and not being pushed against something to hold it... once again, doing it this way works until motor B finishes its rotation and then the heavy object lowers again to the ground.

My solution isn't elegant, but I figured it was worth sharing in case someone else encounters this problem. What I did was configure Motor B to spin 90 degrees (.25 rotations) and at that point the object is being held, parallel to the ground. I then inserted a LOOP block - inside the loop block is MOVE block for Motor B to spin down .1 rotation and then another MOVE block that has Motor B spin up .1 rotation... I set the LOOP to loop Forever, and it worked... the bot holds the object parallel to the floor... the .1 rotation up and down motion isn't even noticeable... but the solution is that the motor is quickly spinning up and down, up and down and never powers down for the object to sink down again.

Anyone have a better solution? I tried applying a MOVE block that stops Motor B (braking) after the initial Motor B block lifts the object, but I didn't think it would work... and it didn't. What is really needed is for the MOVE blocks to have a check box that says "After motion is completed, lock the motor" or something similar to keep the motor from spinning.

If anyone else has any ideas, please post them.

Popular posts from this blog

Celebrating MINDSTORMS with a Remix - Part 2

The ROBOTMAK3RS continued their celebration of the 25th Anniversary of MINDSTORMS through these summer and fall remix projects. Each ROBOTMAK3R was tasked with selecting one LEGO set of their choice and combining it with a MINDSTORMS set. Below are the five amazing models they came up with. Remote controlled material handle r by Jozua van Ravenhorst (aka Mr Jo) This remix combines the LEGO Technic Material Handler (42144) with MINDSTORMS EV3 (31313) It uses the power of pneumatic cylinders to move objects around. By using a bluetooth remote control, very precise movements can be made with this model. Touch sensors in the base chassis prevent the turret twisting the cables that go through the turntable to much. The program has several protections to prevent over pressurizing the system for each of the 3 individual pumps and valves that control the 2 booms and claws. The real version of this machine is mostly used in waste material sites to bring the material to machines that sort and

MINDSTORMS Retires!

2023 is the 25th Anniversary of the MINDSTORMS brand. For 25 years, MINDSTORMS has educated and inspired a generation of robot builders, both children and adults. Unfortunately, the LEGO Group decided to end the line on December 2022. Many ROBOTMAK3RS have been passionately involved with the development of MINDSTORMS through the MUP and MCP programs. Even with the newest Robot Inventor line, several ROBOTMAK3RS were invited to submit additional bonus models that were included in the official app. Regardless of the retirement of a major LEGO robotics product line, ROBOTMAK3RS continue to MAKE-SHARE-INSPIRE using all LEGO robotics platforms available to us. Here is the official statement from LEGO. Since its launch in September 1998, LEGO MINDSTORMS has been one of the core ‘Build & Code’ experiences in the company’s portfolio, carrying with it significant brand equity and becoming a stand-out experience for the early days of consumer robotics and leading to current Build & Code

Celebrating 25 Years of MINDSTORMS

In celebration of the 25th Anniversary of MINDSTORMS, we take a trip through history. Please also visit ROBOTMAK3RS Community every week as we highlight different projects all through 2023 in celebration of the anniversary. Some of the early history is based on the content shared by  Coder Shah  in our  MINDSTORMS EV3 Community Group . Some of the text and links may have been edited from his original posts for consistency and clarity.  1984 - Kjeld Kirk Kristiansen watched a TV program called "Talking Turtle," where MIT professor Seymour Papert demonstrated how children could control robot "turtles" using LOGO, a programming language he developed. 1988 - The collaboration between MIT and LEGO resulted in LEGO TC Logo in 1988, which allowed students to control LEGO models using computer commands. The video shows Papert demonstrating TC Logo. 1990 - LEGO TC Logo was hampered since the robots you built had to be tethered to a personal computer. LEGO and MIT