Hey all!

I have a computer at home that I need to be able to remotely turn on and off, and I thought that the best way to do that would be with a small arm connected to a servo connected to an ESP32.

So I've got all that working but the servo (MG90S) isn't able to press the button at all, the arm seems to be sliding off of it.

I can't share videos here but I recorded it to examine.

Do you think it's because the servo is too weak? I'm trying to figure it out and I've kinda got confused xD

Hello everyone, is it safe to purchase a kit from ez-robot since I want to buy the EZ-inmoov robot head but I am not sure if I can trust the site. Is it trustworthy?

A little about me:

* Final-year B.Tech in Robotics & Automation

* Experience with **ESP32 and embedded systems, ROS 2, Nav2, Gazebo, Python, C++, sensor fusion, LiDAR-based navigation (in simulation), and computer vision (OpenCV, YOLOv8)**

* Background in mechanical design, CAD (Creo), 3D printing and hands-on prototyping

* Hands-on experience through team projects, including a smart warehouse pick-and-place system (Creo-designed, 3D printed and assembled, with ESP32 weight sensors and YOLOv8 vision), and a research paper presented at the BRICS SciTech Forum

I'm open to roles such as:

* Robotics Engineer (Intern / Entry-level)

* Hardware / Embedded Systems Engineer

* Robotics Software Engineer (ROS 2)

* Mechatronics Engineer

* Automation Engineer

* Robotics R&D Engineer

I'm also open to startups and early-stage companies where I can learn, contribute, and grow.

If your company is hiring, or you know of any openings, I'd really appreciate a referral or even the name of the company so I can apply directly.

Feel free to comment below or send me a DM.

Thank you!

Hi everyone!

I'm a B.Tech student in Robotics & Artificial Intelligence and I'm currently looking for a robotics internship or entry-level opportunity where I can work on real-world robotics systems.

My main areas of interest and experience are:

ROS 2

Gazebo / simulation

RViz2

Nav2

Mobile robot navigation

Robot simulation and control

PID control & tuning

Autonomous navigation

Lidar-based obstacle avoidance

Basic SLAM / localization concepts

Python & C/C++

Robotics & AI/ML

I've worked on projects involving PID-based mobile robot control, obstacle avoidance and ROS/Gazebo simulation, and I'm also gaining practical experience through a drone/flight-controller internship, where I've been exposed to IMUs, motor control, PID, sensor fusion and related robotics concepts.

I'm particularly interested in opportunities involving:

ROS/ROS2 • Autonomous Mobile Robots • Navigation • Simulation • AMRs/AGVs • Drones • Robotics Software • Controls • Perception

I'm open to internships, trainee roles, or suitable entry-level positions, preferably in India, but I'm also open to remote opportunities if the work is genuinely hands-on.

I'm mainly looking for a place where I can learn from experienced engineers and contribute to real robotics projects, rather than just doing theoretical work.

If you know of any companies, startups, research labs, internships, or openings that might be a good fit, I'd really appreciate it.

I can share my resume/GitHub/LinkedIn in DM.

Thanks!

Hey all! I'm currently working on a project to create a hand controlled, double screen display and need help with the specific items I need for this.

More info about the project: I plan for both of my hands to have three pressure sensors on the pads of my fingers (thumb will not have one) that are coded with specific images, which the pressure outputs are sent to a board. And said outputs are only sent if the pressure reaches a certain threshold. The board then takes that input and with wifi, sends it to one of the two display boards. Both display boards are connected with a wire so the input corresponding image is displayed on their respective screens simultaneously. I probably didn't explain it well but hopefully the next section makes is more clear.

Items I have on my list so far: (These are all from AdaFruit) For the pressure sensors, I'll be using the round force-sensitive-resistor (0.3~10 force newton). The wifi transmitter board will be the QT Py ESP32-S3 WiFi dev board with STEMMA QT. The wifi receivers will be the Qualia ESP32-S3 and will be connected with a QT to QT cable. Both boards will be connected to their own screens, the round RGB TTL TFT display, 4" 720x720. All coded with CurcuitPython and ESP-NOW.

The trouble: I'm pretty sure the qualia and screen set up works (based on AdaFruit's double qualia display tutorial) and the QT wifi connected with ESP-NOW to one of the qualias also seems like it would work. Let me know if otherwise. The main thing I'm having trouble with is the multiple round pressure sensors connecting to the QT. I know that the pressure sensors are analog and can't communicate with the QT through a cable alone (from what I've read of the tutorial and info pages). I'm guessing that I have to use a QT to male/ 2 pin female cable plus whatever else to actually make the pressure outputs readable to the QT. I've heard of a 10komega resistor but I still have to look more into that. If this isn't possible then any pressure sensor buttons that would work with the QT would be helpful. I also can't do any soldering 😬, so non-soldered connections are a must.

Any help about any of this would be extremely appreciated!

Hello guys, I'm new here, I want to know about how to start Robotics in 2026, where to, like everything in 2026. I am eager to learn. Please help me

I’m looking for an arm that I can use to hold a lightweight probe (no physical contact, not very heavy) and move it around in some volume with some angle control. I plan to mount the probe, so no need for an end effector that can hold things, but a gimbal wrist would be nice.
This is for a personal project, so cost does matter ($200 target) but up to $1k could be considered if the capabilities are good.
Thank you for your time!

I was thinking of making a data collection device for vision and tactile for Humanoids. Can anyone please help me how to make this ? What kind of a camera needed for visual data collection and what to keep in mind while purchasing one or making one ?

What kind of device needed for tactile data ?

I want to place this contraption above me as I sleep, to challenge myself to catch the ball before it hits me in the face.

I dont know any thing about robotics or coding but I could attempt to learn. For the timer, I have a spare smart plug that can already be configured to a time to turn on, if that could work.

here is artistic representation: https://imgur.com/a/jwBvNGm

I’m an embedded software engineer, but I’m new to robotics and ROS 2. I’d like to build a mobile robot with my kids that we can work on together and gradually make more capable.

I’ve been looking at LINOROBOT2 and like the idea of building something from individual components rather than buying a complete robot. I’m hoping to learn about the hardware and software along the way, starting with a basic rover and eventually experimenting with autonomous navigation and a robotic arm.

My current thinking is to use an ESP32-S3 for the low-level hardware and have a separate Linux PC handle the ROS 2 side of things, at least initially. That way, I can avoid putting a full computer on the robot until I have a better idea of what I actually need.

Some of the components I’ve been looking at include Pololu 37D gear motors with encoders and an RPLIDAR A1, but I haven’t settled on the hardware yet. I’m still figuring out the chassis, motor drivers, power system, and how all the pieces should fit together.

A few questions for people who have built similar robots:

1. Is LINOROBOT2 a reasonable starting point for this kind of project?
2. Do Pololu 37D motors seem like a reasonable choice, or are there better options I should consider?
3. Would I be better off building a chassis from aluminum extrusion or starting with an existing chassis and modifying it?
4. Is using a separate Linux PC a practical way to get started, with the ESP32 handling the low-level hardware?
5. If you were starting from scratch, what would you do differently or keep simpler?

The goal is to build something sturdy and modular that we can learn from and improve over time. I’d eventually like to try mapping, autonomous navigation, and adding a small robotic arm, but I’m happy to take it one step at a time.

I’d appreciate any advice, especially from people who have built their own ROS 2 robots.

Hey everyone,

I've been working on a project called KORDEX Core, and I've just published its first release candidate, "0.1.0rc1", on GitHub.

The idea behind KORDEX is to explore how we can make robot telemetry easier to investigate: not just detect an unusual reading, but organize observations, identify patterns, examine available evidence, and communicate what we can and cannot conclude.

The current version includes:

- Rule-based telemetry pattern analysis

- Data-quality checks and uncertainty reporting

- Investigation of recorded telemetry

- Optional read-only MQTT integration

- An adapter for supported ROS2-style diagnostic payloads

- Structured findings and recommendations for human review

I want to be transparent about the project's current stage. This is an early prototype, not a production-ready robotics platform. It hasn't been validated against physical robots or field telemetry, and its real-world predictive accuracy hasn't been established. It doesn't send robot-control commands, and the ROS2-style adapter doesn't subscribe to a live ROS2 graph.

I'm sharing it because I want to learn from people who understand robotics, industrial systems, telemetry, and reliability engineering.

I'd genuinely appreciate your thoughts on a few questions:

I'm not claiming to have solved robot reliability. I'm trying to build something useful, understand the engineering challenges properly, and improve it based on evidence rather than assumptions.

Repository: https://github.com/Wale394/Kordex-core

Critical feedback is welcome. If something is poorly designed, unnecessary, or based on a wrong assumption, I'd rather know now than build on top of it.

Thanks for reading.

Hi, I’m a final year BTech Robotics and Automation student in India. I never did any internship till now and has no idea about how the industry works or what is the work of a robotics software engineer.
Since I’m in the final year ie. the 7th semester - there is an option that for the 8th semester j can either do a project or an internship and my college only allows to go for paid internships. I have knowledge of python ,C++ , Ros2 basics and some basic electronics knowledge. Now it the month of October and by December end i want to secure an internship in india with is paid at least 15k a month. I am interested in doing Ros2 simulations and is willing to explore and learn more about this. Can someone tell me , someone who is currently working as a robotics software engineer in india, how is the opportunities coming up, how to secure an internship, what all should i prepare for, what is the work that a robotics software engineer does and any other tips to keep in mind. Also i am planning to apply for at-least 20 to 30 companies for the same role so which all companies in india are actively hiring for this role. I really want to get some industry exposure. Someone please help me.

i am forth year student specializing in robotics autonomous design (in my country the degree is five years not four, so i still have a year to go), i have modules like power electronics and deep learning , some of mit ocw have the same titles , should i follow the playlists of mit and their work sheets or is it a waste of time and i might benefit more from studying from books.

Curious how you do this, because it's quite of a painful experience for me every time. Designing takes some time but it's at least kinda fun. Ordering from Chinese stores not really

So the design side is done. Schematic, layout and firmware are ready faster or slower depending on complexity, but AI helps quite a bit. Then comes ordering the components which is painful by itself (at least for my wallet 😄). Digikey for the MCU and passives, LCSC because some of it is half the price, JLC for the boards, Amazon for whatever I need fast. Either way there is a lot of searching, clicking and a 100 tabs open. Especially when ordering custom mechanical components, there is sending RFQs, waiting for quotes, ...

Plus every vendor has its own minimums and shipping, so I end up moving parts between carts to dodge a $20 shipping fee on a $6 order. Then something is out of stock and I'm back picking an alternate.

What does your actual flow look like? Do you stick to one distributor and accept the price, or handle it somehow differently?

P.S. I'm working at a startup - we don't have a purchasing dep to do it for me 😅

I'm building a custom tabletop precision rifle simulator and looking for advice on selecting a mechanical recoil system. My background is stronger in electronics/software than mechanical engineering, so I'm hoping to find something reasonably easy to assemble using off-the-shelf components.

The basic idea is a full-size, inert airsoft rifle mounted on a moving carriage that rapidly slides backward when fired, then returns to its starting position.

Think home-made VR Silent Scope arcade cabinet, but with a realistic rifle and more convincing physical recoil.

What I'm hoping to find

Ideally, I'd like an integrated electric linear actuator with its own guide rails, carriage, motor and compatible controller. Something that comes largely assembled and can be incorporated into the finished simulator.

I'd prefer not to independently engineer the rail, bearing blocks, motor coupling, drive belt, etc., or require extensive custom CNC machining.

I'm completely fine making simple adapter plates, drilling mounting holes, using standard aluminum extrusion, or attaching ARCA-style mounting hardware.

I'm also comfortable with electronics and controlling the mechanism using a Raspberry Pi or Pico.

Mechanical requirements

• Moving payload: approximately 5 kg / 11 lb for the rifle, plus mounting hardware.
• Stroke: approximately 50 mm maximum, with shorter movements acceptable.
• Motion: a quick, sharp rearward impulse followed by a controlled, preferably slower return.
• Mostly single-shot recoil rather than continuous automatic firing.
• The rifle will be mounted above the carriage, so there will be an offset center of gravity.
• The entire actuator assembly will sit on a two-axis gimbal and may tilt approximately 20° while operating.
• The user's shoulder will provide some opposing force against the rifle stock.

Electrical requirements

• Fully electric. No compressed air or pneumatics.
• Preferably 12V or 24V DC.
• Simple control from a Raspberry Pi/Pico, possibly STEP/DIR, PWM through a suitable driver, or digital trigger inputs.
• Adjustable recoil force, speed and return behavior.
• No need for Ethernet or industrial networking during operation.
• Position feedback would be a plus for verifying full return.
• Hardware safety limits and controlled stopping are important.

What I've found so far

igus drylin ZLW-1040-S: Integrated belt-driven dual-axis linear actuator with an available stepper motor. Looks promising because the guide and drive are already combined. I'm waiting on igus engineering to determine whether it can accelerate and stop our payload quickly enough.

SMC LEKFS25G: Integrated high-performance electric slider with motor, guide and controller. Looks like a mechanically complete solution, although the proprietary controller and configuration requirements seem more complicated than I'd prefer.

My questions

1. Are there other integrated electric actuator/linear stage products I should be looking at? Ideally something with dual rails or a rigid guided carriage, an included motor and relatively simple control electronics.
2. Can a belt-driven or ball-screw linear actuator produce convincing recoil? I'm concerned that conventional positioning actuators might produce a slow push instead of the sharp impulse we're after.
3. What specifications matter most for this application? Peak acceleration, velocity, force, moving mass, allowable moments, braking energy? I haven't established a required impulse duration or peak recoil force yet and would appreciate guidance on realistic targets.
4. Is there a more suitable off-the-shelf mechanism? For example, a voice-coil actuator, linear motor, motorized cam mechanism or another integrated solution that wouldn't require extensive custom fabrication?
5. How would you handle braking and return? We want a noticeable rearward kick without the carriage slamming into a hard stop, followed by reliable recovery to the ready position. The assembly will be tested in a secured fixture before any shoulder-contact use.
6. Would you recommend moving the entire rifle, or generating the impulse with a smaller moving mass? I'm leaning toward the whole-rifle carriage because it doesn't require modifying the replica, but I'm open to alternatives if they produce better recoil with simpler hardware.

What would really help

Recommendations for specific manufacturers, model numbers, integrated actuator assemblies, or similar projects people have built would be especially valuable.

I'd prefer to buy a complete mechanical assembly with a compatible motor and driver, bolt it to a mounting plate, attach the rifle carriage and concentrate on electronics and software rather than designing a motion system from scratch.

I'm DFW in TX, so US suppliers with readily available parts would be ideal.

Budget isn't firmly established. I'm willing to spend more for the right permanent hardware, but would prefer to avoid a multi-thousand-dollar industrial automation solution if a simpler mechanism can accomplish the same thing.

Thanks for any suggestions!

Hey everyone!

For someone looking to learn Python from absolute zero, what courses would you recommend?

The goal is to eventually use Python for robotics, automation, computer vision, and related fields, so I’d like to know which courses build a strong foundation that can be applied to these areas later on.

My initial suggestion would probably be CS50’s Introduction to Programming with Python (CS50P) or Python for Everybody by the University of Michigan, but I’m curious to hear what others think.
Are there any better alternatives, paid or free?

Would you recommend completing a general Python course first and then moving on to robotics specific programming, or starting with a robotics focused course from the beginning?

I’d love to hear suggestions from people who have actually taken these courses or used Python in robotics.

Thanks!

Hello i am currently trying to understand inverse kinematics by making a arduino function that returns a angle value derived from the y value(the lenght of the joint),x value(the distance of the angle) and writing the return value on the servo pin.And i wanna ask if i am on the right path with learning it or ask what i am missing in my code to make it work.when i tested it with servos on paper it seemed to work after a while when i tested the servo angle on paper. The code is below.I hope someone can help if i missing something or if there is something i can improve on.Thats about it all.I hope someone can help me.The goals is to used it later in a 2legged walking robot:

// this is a code to learn to inverse kinematics with Mg996R by a self made function
#include <Wire.h> // for i2c communication.
#include <Adafruit_PWMServoDriver.h> // for servodriver.
#include <math.h> // for trigonometry functions
Adafruit_PWMServoDriver pwm = Adafruit_PWMServoDriver();


#define SERVOMIN 300// This is the ‘minimum’ pulse length count (out of 4096)
#define SERVOMAX 575// This is the ‘maximum’ pulse length count (out of 4096)
#define SERVO_FREQ 60// Analog servos run at ~60 Hz updates


int  servoval ; // is the values that is reading the map values for servos
long pulsval ; // the values that is getting mapped
float start_pos = 90; // start position
int dof1 = 0; // pin1 of the dof1 servo
int dof2 = 1; // pin2 of the dof2 servo
double ik(double  y , double x) { // y is the servo length in cm and x is the distance of the position in cm


 float pos = atan2(y,x) * (180/M_PI); // convert  y and x position into degrees
 float angle = pos; // create angle values
return angle;


 }



void setup() {
Serial.begin(9600); // is the  baudrate we reading from the serial monitor.
Serial.println("servo test is about to begin!"); 


servoval = map(pulsval,0,180,SERVOMIN,SERVOMAX); // the min and and max values are getting mapped.



pwm.begin();






  //pwm.setOscillatorFrequency(27000000);
  pwm.setPWMFreq(SERVO_FREQ);  // Analog servos run at ~50 Hz updates


  delay(10);
  // servos are set to 90 degrees angle
  pwm.setPWM(dof1, start_pos, servoval);
   pwm.setPWM(dof2, start_pos, servoval);
}





void loop() {



// test loop
pwm.setPWM(dof1,start_pos +ik(7.0,5.0), servoval);
pwm.setPWM(dof2,start_pos +ik(-5.0,3.0), servoval);
Serial.println(" The angle of dof1 =");
Serial.println(start_pos +ik(7.0,5.0));
Serial.println(" The angle of dof2 =");
Serial.println(start_pos -ik(5.0,3.0));




delay(2000);


pwm.setPWM(dof1,start_pos , servoval);
pwm.setPWM(dof2,start_pos , servoval);
Serial.println(" servos in start position");
delay(2000);





pwm.setPWM(dof1,start_pos , servoval);
pwm.setPWM(dof2, -ik(12.0,9.0), servoval);
Serial.println(" The angle of dof1 is now =");
Serial.println(start_pos  );
Serial.println(" The angle of dof2 is now =");
Serial.println( -ik(12.0,9.0));




delay(2000);
  }

Thought this was a pretty interesting approach to robotics. It’s called ALBATROSS, and the idea is to drop it from an aircraft, let it autorotate down like a maple seed, and then have it sail around using wind once it lands on water.

What’s interesting is that it doesn’t need a propulsion motor for either part. Instead of adding more motors and mechanisms, the design relies heavily on aerodynamics and passive mechanics.

Apparently, one of the bigger challenges is getting the same structure to work in two completely different environments.

I wonder how well something like this would scale up, especially for ocean monitoring. Seems like a clever way to deploy a bunch of robots without having to worry as much about battery life.

[Video](https://www.youtube.com/watch?v=J8CUrj0ydxI)

Paper in [Science Robotics](https://www.science.org/doi/10.1126/scirobotics.aed1423)

Curious what you guys think. Is this actually a practical approach, or one of those things that’s really cool academically but difficult to use in the real world?

I work on the used industrial robot supply side, and I’d like to hear more from people who’ve actually bought their first robot for a small shop.

Say you run a metalworking shop, orders are picking up, and you’re considering a used robot for a repetitive task. The purchase price looks manageable—but you’ve never integrated one before.

For those who’ve been through this:

• What caught you off guard after buying it?
• Which costs did you underestimate—tooling, guarding, programming, installation, or something else?
• What should you have checked or asked the seller before paying?

I’m especially interested in shops without an in-house robotics engineer. Did buying used still make sense once everything was running, or would you approach it differently now?

I know the answer depends on the application, so please mention what you were automating if you’re comfortable sharing.

What’s the one thing you’d tell a first-time buyer before they commit?

Currently, I've come across 4 Hoverboard wheel motors. I'm in the planning stages right now for a project that I call "The Indy-Cart"! I'm trying to figure out how to develop a control box to manage acceleration and turning, that will fit on a shopping cart. Any recommendations?