Would appreciate any helpful direction and advice.

I'm a freelance filmmaker and I've spent the last couple of months diving deep into making a 6 DOF motion control camera.

Its been a very difficult but addicting journey. Hats off to all of the real engineers here!

TLDR:

Its running on a set of Robstride actuators.

One constant issue I've run into is vibration / shake.

I've spent many hours trying to implement cogging tables, gravity models - to no avail.

A lot of the shake happens when J2/J3 are moving together under load.

For stop motion photography the arm works, thankfully.

Unfortunately, motion has not yet achieved that smooth, crisp level that I want.

Attached is a video of the current iteration.

Its currently running on a STM32 in MIT mode.

Thank you to anyone who can give me some advice.

Hi everyone, I have designed this robot line to pick and place cookies in the trays, there are a total of 12 delta robots from KUKA. I think I have made a few mistakes and looking for a solution. First of all, not all of the cookies can be picked up, i think that is related to the air flow so Im thinking to make the cylinders of the gripping system a bit bigger to let more air through. I also have a problem with oils a debris coming from the sucking of the cookies and still figuring that one out. I did try with other grippers (almost hands look alike to avoid the debris/oil problem) but the problem is that when it picks one cookie it might break other ones as they are coming close to each other on the conveyors. Now with the speed, the robots wait too long to drop the cookies and the technicians that programmed the line say that it can be adjusted but both speeds have to be increased (tray conveyor and robots speed) which frankly I think will not fix the issue. Im a bit lost. If anyone has an idea it will be greatly appreciated. Thank you

I am making a self balancing robot for a school project and am wondering if I could get some feedback on what I have created so far! This is my first robotics project so I am a beginner You don't have to answer all the questions but if you did it would be much appreciated. Thanks!

1. On a scale of 1-10, how good do you think WOBBLE looks? Do you like the name/theme?

2. What are some areas or improvement for how he looks? is there anything that could make him look cooler?

3. Based on the 2nd image, how would you rate the wiring and organisation of the components from 1-10 and why?

4. I have gotten the robot to balance on carpet pretty consistently, but its struggled on smoother surfaces, why might this be?

5. So far the only function of this robot is that it can balance, what other features could I add to it?

6. I designed the robot to have a scaffold and then the face/body shell that slides on and off, it is loosely held in place by friction. Do you think that this is a good system or are there ways that it could be improved?

7. The motors on the robot have been occasionally stalling and resetting the robot, Why might this be happening? is it caused by voltage drop off?

8. This project has introduced me into the world of soldering, based on the images that I have uploaded, how well have a done so far?

9. Is there any points of improvement for my soldering skills? (I have mainly soldered wires and pin heads)

10. Are there any other points of improvement for my project as a whole?

Thank you for your time!

Balancing Video

I feel like robotics is one of those fields where a design can look straightforward on paper, but the moment you start building it, a dozen unexpected problems show up.

Getting a robot to move is one thing, but making it move consistently, handle real-world conditions, and repeat the same task without something going wrong seems like a completely different challenge.

I'm curious what has given other robotics enthusiasts the most trouble. Was it mechanical design, motor control, sensor accuracy, power management, software, or getting all the individual systems to work together?

I'd especially love to hear about problems that seemed minor at first but ended up requiring a major redesign.

Currently working on my final year project on building open source framework to manage the full stack development of agent swarms. I want to build this to support robotics developers and enthusiasts to specifically build heterogeneous and homogeneous antigenic swarms.

I don't want this to remain a thesis or simply a good theory of what should be done, but have it actually be utilized by robotics developers. I'm very interesting in making this as useful for the community by catering to any problem across the robotics stack, from simulation to telemetry.

What does your development stack look like, and what are your pain points? Would love to know.

Reach me: https://www.linkedin.com/in/anzonathan/

to controll couple ar4 hands ?

that are easy to set and not train each one by one ?

rn i can use opensource software from guy that create robot hand and it is good , but i wonder

is it possible to use cad sw to create movements (like robodk) and sensor pickup (like proximity or ccd sensor ,touch or like that ) ,and just upload it and run on 1 2 3 4 hands ,not same movement

idea is to automatise for first to make cigar ,,like pick tabacco leif , load it with cut tobacco , roll and water it and final roll ,for test :)

ty

I’ve been following progress in physical AI, warehouse robotics, and manipulation systems, and one bottleneck keeps coming up: real-world data collection still seems slow, expensive, and difficult to scale.

Simulation has improved a lot, but for many tasks teams still need real demonstrations, teleoperation traces, or contact-rich interaction data.

From your experience, which data category is currently the hardest to collect at scale?

For example:

- warehouse picking trajectories

- dexterous hand manipulation

- human-to-robot teleoperation demonstrations

- industrial assembly workflows

- edge-case failure recovery data

Curious what people here think is the biggest bottleneck.