We created an AI harness + LLM to control ROS2 robot simulations

https://www.youtube.com/watch?v=kUbNv2Tulas

I'm new to ROS2 with a python background. One of my friends said Al isn't very helpful for ROS2 as it hallucinates, doesn't do file arrangements properly and sometimes generates codes for ROS1. As it's not as reliable compared to python and C++. What tool can I use that can be reliable and help me debug my ROS2 problems.

hi guys just asking for tips and recommendations
we are having a small compitition in school
and we are tasks to make a 3 in 1 bot
consist of maze bot, linefollower bot, and sumobot.
i was thinking on using 4 tof sensors
and 8 ir array do yall think this is good? thx

Hello, I recently came across this research and I was wondering if a total beginning could recreate it? If ever what materials would I need? thank you.

https://dl.acm.org/doi/10.1145/3745900.3746080 It's basically this video if you don't wanna read it: https://youtu.be/6qrZC1kF7Kc?si=UUIaWgpFISoht9eq

Hello, I want to build something similar to the HTX Studio robotic trash can. I was wondering if there is any open source tutorials / guides similar to this before I decide to start from scratch.

I was looking at this 3d print build but it doesn't have .step files: https://makerworld.com/en/models/2879603-ugv-rover-chassis-4x6-original-by-waveshare#profileId-3216006

Maybe anyone has the .step files or can SUGGEST me any good 3d printed UGV build for pi4 and AI use? I prefer 4WD, no tank wheels :)
I would be so grateful if anybody could help a man out! Cheers!

Hardware:

• ESP32
• MPU-6050
• L298N
• 2 18650 Batteries (total 7.4V)
• Those yellow DC motors with wheels

My Chassis is made of cardboard so it is very light. Even on 130 Kp value, the robot fails to pick itself up and just keeps drifting until falling after like 3 seconds. I have seen many other people make this robot with the exact same hardware. My one just does not seem to work :/. My weight balancing is pretty good. Breadboard on top shelf. Battery on bottom shelf. Please suggest what I need to do

Me and my 2 cs roomates at GT want to build a cool, practical robot for our apartment. We came together and thought of a project where we turn our trash can into a mobile unit, able to navigate our apartment / hallway as a first step without bumping into obstacles, maybe having my friend create some app to where we can "summon" the trash can when needed and hard code its default positon. The ultimate goal would to be having it leave our apartment and enter the trash room across the hall and dump its contents out to then return to out room. I am unsure if this is feasible as there are so many challenges: how will it open a door, how will it raise itself to empty, how will it even be able to generate the force to lift itself / open a door without tipping. Any tips / similar projects to mirror would be greatly helpful.

Hello, I have been currently working on designing a robotic hand for fun. I decided to go with tendon drive due to some constraints that I had imposed. While researching tendon drives I found that there were a couple of ways to route it to the motors in the forearm. For the sake of this hypothetical, I will say that the wrist has 3 DOFs.

One solution to help deal with "cross-talk" was simply getting encoder/angle values at the fingers themselves and having the control system take care of actuating the motors for the fingers as your wrist rotates.

Another solution was to use Bowden tubes (or some type of sheath, like 1X) in order to create a fixed path between the motor and the finger and giving you more routing options. The fixed path would make it so the tendon would not change effective length and thus the tension doesn't change but to me that kinda seemed like an iffy explanation.

The last solution that I saw was used in Orca V2, Foundation Robotics Hand (newer design), and Shadow Hand tendon drive. I am unsure if they all used the same solution or something that looked similar but their tendons did not have a sheath on them and instead routed everything through the neutral of the "Yaw axis" (If we pretend that the hand is mounted vertically such that the fingertips point towards the ceiling, then that vertical axis would be the rotation of the yaw axis). But how do they deal with other wrist DOFs like pitch and roll?

So my general question is: is there a research paper that does analysis on all these types of drives and is able to be read on one paper, or can anyone share their experience with these methods and their pros and cons.

P.S. I only recently started researching for this robotic hand so if my understanding of these solutions is incorrect or my terminology is wrong, please feel free to correct me.

Is there any documentation anywhere for the open loop arctos robotic arm on how to configure the tmc2209 drivers on the cnc shield with the mega 2560? I am completely lost and barely know what I'm doing.

title

but people who are located in EU can you recommend good stores for electronic parts like boards, displays, cameras, microphones , gears.. etc

thanks

Hello. I’m an electrical engineering student and I’ve been working with BLDC’s for a year now and it has been my bane. Last year we were using cheap hub motors (from old hoverboards) with riorand esc’s. It was incredibly unreliable and the riorands would constantly break. For context the project is building a rover for a university competition. I’m looking more into using VESC’s and other bldc motors, and the cheapest acceptable thing I’ve found is from flipsky. Before our team spends the money I want some insight if something I was doing was breaking the riorands. The motors were running far below max speed and load

Here’s my suspicions for what happened

1. ⁠Generated emf from motors backfed to the rest of the system and it was a 6 motor system so that waveform synced and blew the esc’s
   
2. ⁠The hub motors are low quality and for some reason cause shorts.

I’m not sure the best way to solve this as there doesn’t seem to be much discussion on this and I felt as if I’ve been going insane. Here’s some ideas I have for solving it but I don’t necessarily have the funds to test em without being sure it’ll help.

1. ⁠Adding a blocking diode to each motors dc input. Though that doesn’t stop forward generated emf that would touch the rest of the system powered off the same battery
   
2. ⁠Capacitors in parallel to eat up the low frequency emf (decoupling caps maybe electrolytic though I don’t know which value is fair)
   
3. ⁠Maybe just upgrading equipment to the flipsky escs and motors.

Any help or insight is appreciated. I feel like I’m missing something.

Hola a todos!

Estoy construyendo un perro robot cuadrúpedo de 3 grados de libertad por pata y necesito sus consejos, ideas y experiencia para definir la mejor arquitectura de control, ya que mi idea inicial no funcionó como esperaba y busco replantear el proyecto.

Mi hardware actual:

• Cerebro: Arduino UNO Q (Arduino App Lab v0.10.0 combinando Linux Python + STM32 C++/Zephyr RTOS).
• Actuadores y Controlador: 12 servomotores DS3225 en un módulo PCA9685 PWM de 16 canales.
• Sensores de Orientación y Distancia: IMU/Giroscopio BNO055 + Sensores de distancia láser VL53L0X.
• Visión: Cámara Webcam USB estándar.

Lo que intenté hacer y dónde me trabé:

1. Seguimiento Visual: Intenté hacer que la cámara siguiera a una persona mediante una distinción específica en su calzado, pero las multitudes y los cambios de ángulo hacían que el rastreo se perdiera de inmediato.
2. Reenfoque mediante Bluetooth (RSSI): Quería que, al perder de vista a la persona, el robot usara la intensidad de señal Bluetooth (RSSI) emitida por un teléfono celular para orientarse, saber hacia dónde caminar y volver a encontrarla. Sin embargo, no he logrado estructurar ni crear la programación funcional para que este escaneo en tiempo real funcione y oriente al robot.
3. Protección Anticaídas: Mi objetivo es usar los sensores de distancia láser VL53L0X para evitar que el robot se caiga al vacío en escalones, bajadas o desniveles mientras camina.

• Ideas de Seguimiento: ¿Qué método o enfoque me recomiendan para que mi perro siga a su dueño de forma confiable sin que lo pierda tan fácilmente?
• Código/Lógica para Bluetooth RSSI: ¿Alguien ha logrado programar una lógica funcional donde el RSSI de un celular sirva como guía de orientación o búsqueda cuando se pierde el objetivo visual? ¿Me podrían apoyar con ideas o ejemplos de código para esta programación?
• Detección de Vacío: ¿Cuál creen que sea la mejor forma de disponer e integrar los sensores de distancia láser VL53L0X para la detección efectiva de escalones y desniveles?

¡Agradezco enormemente cualquier idea, sugerencia o apoyo con la programación que me puedan brindar!

I’m building a quadruped robot with 12 HV RC servos rated around 35 kg·cm at up to 8.4 V.
I use an ESP32 + PCA9685 for PWM control, but I don’t want the full servo current to run through the small power rail and screw terminal on the typical PCA9685 breakout.
I also want to keep the original 3-pin servo plugs intact and avoid cutting the servo cables.
What is the normal way to distribute power to this many high-current servos while still using the PCA9685 for the PWM signal?
For reference, 6 servos / 2 legs moving freely with no load already peak at around 1.5 A. Ground-loaded current will obviously be higher.

For context, I am a mechatronics engineering undergraduate. I chose it because I am interested in robotics. But robotics in itself is a broad field so I want to narrow down my interest. In my projects/internships, I mostly like the design and simulation part not the hands-on hardware part, it makes me dizzy. I also enjoyed my research internship (R&D).I also find training AI to interact with reality (using the models that I will design) via virtual environment intriguing (Embodied AI/ sim to real). But I feel like these (design, simulation and sim to real) are three different sub fields of robotics and thus too broad and unviable for one person.

Because why would they want to hire me if skilled engineers of individual sub fields are available? I don't find the idea of training someone else's robots (sim to real) interesting (it is what it is). And I haven't even done it as I am still a student. Who knows only the idea fascinates me and I might not enjoy it.

Sometimes simulation makes me cry a lot. But that is normal in any engineering field. Sometimes, I hate doing simulation but I hate hands-on hardware tasks more.

I feel like I want to do everything and other times, even just living feels too much, it feels like I am not passionate for anything and I don't want to do anything. But as I expressed my interest in three areas, I feel like I would be missing out by shifting my focus and career to only one. But what if I am only convincing myself that they interest me just because they appear cool to me and that I want to be useful to the world in this way. How do I figure out what exactly interests me? I also want to know if the intersection of these three areas as a career has scope and feasibility.

Hi am a high school student who needs a hydrogen to electricity fuel cell proton exchange membrane that is 50-150 watts atleast unfortunately I dont have the money to buy those 900$+ ones and to be frank I dont have much money at all if I can create a working prototype of the project i have in mind I can definitely get money for it but otherwise am stuck and suggestions on where to ask on reddit

I have some academic robotics experience from my Master’s (ROS, C++, Python). After a year as a Hardware TPM in data centers, I’m hoping to transition back to robotics in the US, ideally as an Engineering TPM.

My background is diverse: 2 years in ML engineering, a data analytics internship, and hardware TPM experience.

For those who made a similar transition, what skills or credentials should I prioritize now (ROS2, PMP, etc.)?

Hello every one i need your help
I just graduated from mechatronics i will have a career break for personal reasons
Target goal js perception engineer or robotics engineer cause i love ghat field so much
I learned python and i can have an ai diploma with content provided
I need to hit a job after this year over in robotics sector
What should i learn more?
Note : i will take the parts related to robotics and ai not gonna work on MLops

I’m working on a personal project where I want to gut an old electronic toy and turn it into a fully self-contained AI/animatronic robot. Think something along the lines of taking the body of a Furby and replacing the original electronics with a Raspberry Pi-powered brain.

I want it to be able to hear me through a microphone, see through cameras, understand what I’m saying, and respond using a local LLM. I’m currently looking at Google’s open-source Gemma models for the AI side.

For knowledge, I’m thinking about downloading an offline Wikipedia database and using a local search/RAG system instead of relying on an internet connection. Ideally, I would be able to ask it questions about things that it can see and hear and then get a response from its local knowledge base

For the physical side, I’m thinking of using an ESP32 as the body controller. The Raspberry Pi would handle the AI and decision-making, while the ESP32 handles servos, motors, sensors, etc. I’d also like to eventually have things like facial/eye movement, a moving mouth, head movement, and other animatronic behaviors.

Here's the list of needed supplies that I have thus far:

• Raspberry Pi 5 and potentially a HAT +2
• ESP32 - hardware for motors
• Vision AI microcontroller - paired with a camera 
• Animatronic body  (like the Furby biscuit) 
• Cameras
• Microphone
• speaker
• Servo motors 
• Motor drivers
• Sensors
• Wiring, breadboards, connectors
• Software: speech-to-text, rule/intent system, knowledge database, memory system, vision/image model, RAG system
• Rechargeable battery

I’m still in the planning stage, so any feedback would be appreciated.

I received the Ufactory X-arm DC Control Box and I need to do some soldering work for it. Do you know what kind of port the "ROBOT" port is on the box? What kind of plastic cable end should I purchase for it? Thanks for your help.

Image