Hi everyone, I recently finished my MS in mechanical engineering (focus on simulation modeling and controls) and started as a GNC engineer at a well established aerospace company. My team does very little actual GNC design, though. The work is mostly system integration and testing: hardware validation, software updates to subsystem components, and hardware-in-the-loop testing. The system is already mature and in production, so I haven't needed to use my modeling, simulation, or controls background. There's an upside. The pace lets me learn aerospace terminology and understand the system as a whole, and my role requires broad knowledge of many subsystems. But I worry my title is a bit misleading, and that if I want to move into more technical work later, my academic skills will fade. I'd like a side project where I can work on the GNC side directly, with a platform that's ready to use. I tried building a drone before, but I spent most of my time debugging hardware (ESP32s, sensors, ESCs) when what I really want is to write and tune control algorithms. Any suggestions for projects, platforms, or simulation environments? Perspectives, ideas or stories are greatly appreciated!!!
Estoy cursando mi tercer año de Ingeniería Electrónica Industrial Y automática, pero tengo una sensación de que en la universidad no me estoy preparando de verdad, tengo ciertos conocimientos teóricos, pero mucha falta de experiencia práctica que no siento que vaya a adquirir en este año y el siguiente, personas que estén en el sector o hayan tenido sensaciones similares, qué consejos me darían, cómo puedo intentar ganar experiencia o aprender de forma autónoma algo más enfocado a la parte práctica de este sector. Gracias.
I am currently designing a "Peak Current Control Mode" buck converter. If you design the Type II compensator, can you simulate the buck converter successfully without implementing the current feedback yet? Or do you have to implement the current feedback as well when testing it? The reason that I am asking is that I am attempting to simulate the plant with the Type II compensator ONLY but it is not regulating based on the calculated values. I am hoping to validate the Type II compensator first prior to implementing the current feedback (with slope compensation). However, I am not sure if this is allowed. Is it REQUIRED you HAVE to test it along with current feedback?
Interested in looking up topics, papers, authors, and institutions, more interactively ? Also, want to know about the ranking of institutions, authors, or areas by the number of papers?
Hey, I'm a mechanical engineering student heading into my final year, and I'm looking for advice in the field. I've fallen in love with control theory—I'm currently finishing my control systems course and enjoyed it immensely. I'm now trying to come up with an industrially applied idea for my thesis.
As I said, I fell in love with control and dynamical systems. It combines the advanced math I enjoyed in rational mechanics and mathematical physics courses with heavy industrial applications, while also allowing you to delve into more experimental or cutting-edge fields. I'm even considering doing a PhD in control and dynamical systems.
The next step is choosing my thesis topic. At my university, we spend the entire final year dedicated to our final project—you can see it almost as a research-oriented mini master's thesis. I want to choose an 'advanced' control topic, leveraging the most sophisticated theory I can. For reference, we just finished covering state-space control.
On the other hand, here in Argentina, we are seeing a boom in the energy sector, and I would like to work towards developing solutions for these areas. However, it's not just energy; mining, the chemical industry, and most export-led sectors are showing strong yields. It could also be a great idea to tackle an agricultural problem, given it is the most critical sector here.
So my questions are: do you know of any applications for advanced control techniques (MPC, nonlinear control, robust control, RL) in these fields? Any broader recommendations?
This is my first time attempting system identification of a simple battery / inverter. From what I understand, you can use either the measured or predicted values as previous values in the regression mode. I'm able to get a good fit using measured values (one-step prediction), but when attempting "free running simulation" using the prediction as previous values, I get a first-order like response and the max pole value is always close to 1.
I a using na = 2, nb = 2, nk = 1 and also tried a bunch of different combinations, but they all give me relatively the same results.
Could it be maybe my data doesn't have enough dynamic activity to fit the data or something? I'm a bit lost as to what else I can try.
Hi everyone - I'm currently trying to get a 3d printed bike to self balance, but keep running into issues with the final control loop. (see github link down below for video).
For reference it is very similar to REMRC's self balancing bike - I just use SimpleFOC + GM3506 BLDC motor with an STM32 to run the loop instead of using Arduino and a Nidec 24h motor.
Here's the hardware I am using:
STM32F411 Blackpill
ICM-20948 IMU (through I2C, couldnt get spi to work for some reason)
GM3506 BLDC motor + AS5048A encoder
SimpleFOC with voltage-mode torque control
12 cm reaction wheel with additional rim weights
Lots of wires (ik I need to clean the wiring up)
For software:
Arduino for SimpleFOC
STM32 HAL for pretty much everything else (steering, IMU I2C, Transceiver SPI)
I use a complementary filter to combine accelerometer and gyroscope data. The loop frequencies are roughly:
IMU measurement loop: ~200 Hz (IMU is mounted rigidly onto the body of the bike pretty tightly)
Balance control loop: ~100 Hz
Main loop - ~11.9 kHz
The controller itself uses a PD loop with three feedback terms:
u = K1 * angle (proportion)
+ K2 * gyro_rate (derivative)
+ K3 * reaction_wheel_velocity (this one is weighted pretty small tho)
My control knowledge isn't the best but from what I am aware of:
K1 corrects the lean, K2 damps the bike's angular motion, and K3 provides reaction-wheel speed feedback. Chat says this is the main equation for it:
Also I can't lie I used ChatGPT for help on a lot of the control theory - I originally was trying to do this to learn more about embedded system communication protocols, but this turned into a much bigger control problem than I thought lmao (who would've guessed).
ANYWAY THE MAIN ISSUE:
The reaction wheel can like catch the bike in one direction pretty well, but as soon as it like crosses that midpoint of balance, the motor attempts to catch it, but it just spins ands spins until it falls over.
I am realizing that I think the main issue is that it doesn't have enough initial "pop" at the start of crossing mid balance. The only time i feel like it does this is when I was tuning K1, but it would kinda just oscillate out of control.
The other big thing issue is that I feel like I need to increase K2 (derivative), to give it more initial pop so it doesn't like saturate itself, BUT when when I increase K2 passed a certain degree, the bike just starts vibrating like crazy especially around the point of oscillation. It's not even a shaking back and forth its a very rapid vibration. Maybe it's a mechanical motor mount issue? I am not sure.
I've tried experimented with the gains, gyro filtering, and motor voltage limits, but haven't found any solutions and am genuinely losing hope for this to ever work lol.
The longest balances I've had were when it slowly corrects itself one way for quite a while, but then it crosses the midpoint and relatively quickly speeds up and isn't able to get back to the midpoint.
With all of that said for reference here are all of the control variables that I can change within my loop - I am also not sure like what's best to change, and what's best to keep constant. Ex. to deal with vibration reducing K2 helps, but so does lowering GYRO_FILTER_TAU.
HERE ARE ALL THE VARIABLES: Balance Controller
K1: Controls how aggressively the bike corrects its lean angle
K2: Controls how strongly the bike reacts to falling speed (damping)
Gyro hardware DLPF: Controls gyro noise filtering and response delay
Accel hardware DLPF: Controls accelerometer noise filtering and response delay
Loop Timing
BALANCE_PERIOD_US: Controls IMU/filter update frequency (currently 200 Hz)
CONTROL_PERIOD_US: Controls balance controller update frequency (currently 100 Hz)
So yeah if anyone has any advice please let me know! Attached are a couple of videos and pictures of the bike. The code and a video is posted in my GitHub below. For the control loop, pretty much ignore everything except for balance_control.c, and main.cpp. All the other files are for a servo for front steering, and a transceiver for remote control.
Hi guys I'm going to publish a conference paper soon, and this is my first paper.
My PI think we're ready but I'm wondering if it's normal for a conference paper to be more on the "work in progress" side.
We're trying to use some "theoretical algorithms" and Adaptive them to make them work also ok more realistic scenario.
I mean we got the results, but while on toy problems the algorithm work pretty fastly the convergence is smooth etc
With this adaptation on a more difficult problem it still works but it's way more wobbly, the convergence is not as "neat"
I would say We have some ""preliminary "" result that are encouraging but still a lot of open question to answer, there is probably a better and faster way to do it etc.
Is this normal for a Conference Paper ? Or we should be more "Mature"?
The general idea of my PI is that this is a good thing bc it means that there are opportunities for research and improve in the next paper, but I feel a bit like we're just publishing something """""wrong""""" in the sense that could be a lot better with some work on it .
I’m a Master’s student working on the positioning subsystem of a gas-blending setup, and I’d like a sanity check on my actuator architecture before I commit to hardware.
The process
The system meters hydrogen into a natural gas line at around 10 bar, targeting roughly 10 vol.% H2 in the final mixture. A needle valve sets the hydrogen flow, and the gas composition is measured by an analyzer located downstream of the valve. Because of this, there is a transport delay of several seconds between a valve movement and its effect on the measurement.
The control is a two-loop cascade:
Outer loop (slow): composition control, with a Smith predictor to handle the transport delay.
Inner loop (fast): valve position, running on a STM32 NUCLEO-H503RB under an RTOS
Requirements:
Small moves and good repeatability of the final position. Speed and bandwidth don’t matter much because the outer loop is dominated by the delay.
No silent lost steps.
Low heat at standstill. It’s a flammable gas environment, so I’d like to avoid hot, noisy electronics.
Stiction and hysteresis are significant, especially the ladder.
Where I am
I haven’t bought hardware yet and I’m working on modelling and simulation first, so I can still change the architecture. I’ve been reading about three levels of “closed loop” for steppers:
STEP/DIR + external encoder: the MCU compares commanded vs measured position, detects lost steps and corrects the end point.
Same, but correcting continuously (closed-loop microstepping).
Full FOC, treating the stepper as a 2-phase PMSM with current control. I read a TI technical article on this, which also describes a “semi-closed-loop” variant where the MCU only generates the current references and the driver does the current chopping.
My questions
For this kind of slow, high-repeatability positioning task, is the encoder-based correction in (1) or (2) enough, or does FOC bring real benefits (heat, efficiency, smoothness, stall margin)? My gut feeling is that FOC is overkill here, but I’d like to hear from people who’ve done it. I’m also wondering if the torque lost because of microsteeping can be gained with FOC.
2. Encoder on the motor shaft vs on the valve stem: is it worth it given coupling compliance and thread backlash?
Any pitfalls I should expect, such as limit cycles around the setpoint with stiction, microstepping at low torque margin, or tuning the inner loop at such a low bandwidth?
Hardware suggestions are welcome: integrated closed-loop stepper motors (have crossed this option out, mainly for its complexity and the time it would need to “think” vs separate motor + driver + encoder (heavily leading on this), and specific drivers or encoders you’ve had good experience with.
I’m a control engineer, and I’ve been building a small desktop app (Mac and Windows) for tuning from an open-loop step test. Disclosure: I’m at CSI, the consultancy that’s developing it.
What it does:
Fits four models with dead time (first order, overdamped and underdamped second order, integrating) and recommends one by AICc. You can override it.
Applies rules suited to the model: IMC/Lambda, SIMC, Ziegler-Nichols and Cohen-Coon, plus integrating-process rules.
Adds a Smith predictor case when θ/τ ≥ 1.
Simulates every rule on the same setpoint step (overshoot, settling, IAE, OP travel), with optional noise, OP limits and deliberate model mismatch to test robustness.
Optional AI suggestions, using your own API key. Every suggestion is simulated before you can apply it, and raw data never leaves your machine.
Known gaps: setpoint steps only (no load-disturbance case yet), and no setpoint weighting.
Two questions for this sub:
Which rules or models would you expect to see that are missing?
Would a disturbance-rejection simulation change how you’d use it?
Happy to share the waitlist link if the mods allow it.
I am having a problem where no matter how I interpret the problem i cannot reach the exact given transfer function in the question. Image 1 and 2 show the question and transfer function respectively while images 3 and 4 show my steps where
in image 3 I interpreted it as the total torque of the motor accelerates both j_m and j_l which should be the correct way to interpret it i think. Here the transfer function is completely different from the given one.
In image 4 I interpreted it as the torque affecting j_m is equal to the torque affecting j_l. Here the transfer function matches exactly but has an extra term that I can't justify removing as well as just being an incorrect interpretation of the problem mechanically
Consider the class of nonlinear systems of the form :
x' = f(x, u), y = h(x,u)
It can be re-written as
x = int f(x,u) dt, y = h(x, u)
This results in a very complicated expression due to the integral and various properties of function f. This said, we can potentially identify the system using a neural network NN:
x = NN(u)
The idea is to grab input-state pairs (u(t), x(t)) of a real system and fit a neural network.
After all x' = f(x,u) is just an approximation of the real system, and x = NN(u) is also an approximation. If the network has enough capacity, NN could potentially contain the entirety of x = int f(x,u) in some part of the network.
Of course, x' = f(x,u) has greater amount of interpretability for small systems, but potentially difficult to justify for very complicated systems. x = NN(u) could be used instead. But is this idea doomed because (u(t), x(t)) are difficult to get (and using a simulator means we need to solve x' = f(x,u) anyways)?
Seem there is a precedent is in machine learning, where the RNN model h_t+1 = Ah_t + Bu_t was replaced with the transformer model x = NN(u). Can control engineering ever be re-imagined so that its foundation are input-output systems x = NN(u) as opposed to dynamical systems x_{t+1} = f(x_t, u_t)?
Hi mods, I’m a control engineer at CSI and I’ve built a desktop app that fits a FOPDT model to an open-loop step test and compares Ziegler-Nichols, Cohen-Coon and IMC/Lambda tunings in closed-loop simulation. Would a post sharing it (with a link to a waitlist) be acceptable under rule 6, or is there a preferred format or thread for this? Happy to keep it to the technical content if that’s better. Thanks.
In most discussions on industrial automation (and manufacturing, "hard industry"), I get the sense that it involves more towards the type of tools that you learn or use (SCADA, PLC, MPC, Industrial robots, etc.) rather than something that you research.
Are there still active research opportunities in this area, especially from a system control approach, or have things matured to a degree that research will be increasingly incremental or have poor expected returns?
From my understanding there was a period in the 70s-80s when MPC research became very dominant and all types of MPC were proposed during that time, and applied to all sorts of industrial plants. Then there is a wave in SCADA, distributed systems, PUMA and FANUC robots, ... But that all happened decades ago.
A follow-up would be: if there is research opportunities, are these mostly in academia or industry?
I'm looking for some advice on how to transition from studying control theory academically to actually applying it in practical, industrial contexts.
I'm a Mechanical Engineering graduate with a background in Machine Learning and Computer Vision. My previous work involved developing deep learning pipelines for automated damage assessment in CFRP composites. I'm now trying to broaden my skills towards industrial automation, robotics and machine vision integration.
What I've studied so far
I've been independently studying the Automatic Control / Dynamic Systems syllabus taught by Professor Seatzu, following his material and textbook (Analisi dei sistemi dinamici).
So far, my studies have covered the mathematical foundations of linear dynamical systems, including:
Mathematical modelling of dynamic systems using differential equations.
Laplace transforms and transfer functions.
Poles, zeros and system dynamics.
Transient and steady-state responses.
Stability analysis.
Interconnections of dynamic systems.
Block diagram algebra, including series, parallel and feedback configurations.
I'm currently working through interconnected systems and block diagram reduction.
The broader syllabus also includes topics such as:
Root locus and frequency-domain analysis (Bode and Nyquist).
State-space representations.
Controllability and observability.
Nonlinear dynamical systems.
I want to get a solid understanding of the theoretical foundations, but I'm increasingly feeling that spending all my time solving mathematical exercises without implementing anything is not the best use of my time at this stage.
What I'd like to learn next
My goal is to move towards practical industrial automation, particularly at the intersection of control systems, robotics and computer vision.
I'm interested in understanding how the theoretical concepts translate into actual engineering systems.
PID controllers: Implementing and tuning controllers on real or simulated systems.
Motors and actuators: DC motors, encoders, motor control and feedback loops.
Robotics: Forward/inverse kinematics, trajectory planning, motion control and eventually ROS 2.
Sensors and acquisition: Encoders, proximity sensors, industrial cameras, hardware triggering and real-time acquisition.
Computer Vision integration: Connecting vision systems to PLCs or robotic systems, for example detecting and classifying objects on a conveyor belt and triggering a robotic sorting operation.
I'm particularly interested in building small projects, even using simulations initially, that combine these different components.
My questions
Which parts of classical control theory should I absolutely master before moving towards practical applications? For example, how important are root locus, Bode/Nyquist, controllability and observability in everyday industrial engineering?
Which theoretical topics are worth studying in depth, and which ones can be approached more selectively until I encounter a practical need for them?
What would be a good progression from basic control theory to PLC programming, motor control and robotics?
Are there any practical projects, simulation environments, books or courses you would recommend to someone with my background?
Would you recommend starting with MATLAB/Simulink, Python (e.g. python-control), C++, or going directly into PLC environments?
I don't want to abandon the mathematical foundations. I just want to start using them to build and understand actual systems rather than spending another few months exclusively manipulating transfer functions on paper.
I'd appreciate advice from people working in industrial automation, control engineering or robotics, particularly regarding which skills are genuinely useful in industry.
edit: I'm reading all your comments and trying to find the most optimal way to integrate what you suggest, thank you everyone, if you have source material or want to DM I'll answer when I'm able to
So my Final year project advisor has given me DIY kit from ali express now he is saying to make the 3d model of it , It is called something wheeltec kit but the problem is i am EE major and i dont have full dimensions and material list of it so please help me how can i make the cad model of it
I’m not talking about what qualifies me in the eyes of an employer to get an R&D position at a company or academic job. Just purely for the sake of R&D competence itself, is the training that comes with a PhD programme strictly necessary?
Can I get away with a research masters? With one long thesis year?
EDIT: specifically, assume I have my own source of funding and my goal is to do my own research alone in an area that doesn’t depend on expensive gate-kept equipment to eventually turn it into something I can make money out of (so for example maybe something like learning based control for dexterous hands?), do I need PhD training to know what I’m doing? How would I even verify whether my work is good enough?
I'm an engineering student, I took control system two semesters ago and now I need to study it again for an exam I'm taking.
I need help in going back.
So i remember i studied it really well that time and i remember there was a "AH! I FINALLY GOT IT" moment where I linked the chapters to one another and finally understood why I was studying what I was studying.
Why i studied a topic prior to some topic like there was a link between the two, some limitations in the prior chapter that were overcome by the next chapter.
Unfortunately i don't remember it now.
Can anyone help me exactly with this, like giving an overview or flow chart of why something came and what's the need to it.
Hi everyone, I have a solid background in control theory, and I'm comfortable with ROS and MATLAB. I also have the basics of machine learning algorithms. I'd like to become a robotics engineer who is truly ready for the job market, but I'm not sure what the next step should be. Some things I'm wondering about: Should I learn simulation tools like Isaac Sim (or Gazebo, MuJoCo)? Which skills matter most to employers right now: C++, perception, motion planning, embedded systems, RL? Where can I find good resources (courses, docs, open-source projects) to learn them? What kind of portfolio projects would make a real difference? Any advice, roadmap, or personal experience would be really appreciated. Thanks!
I am sharing a small NMPC project I've been building as part of a larger thesis on drone target-tracking. Check here: https://github.com/brunopinto900/argus/tree/px4-ros2-bridge . Result in the video: ~10cm tracking error, target held inside the FOV cone throughout with Occlusion cost ON vs OFF.
Alongside the usual position/velocity tracking terms, there's a soft cost keeping a ground target inside the camera's FOV cone. Collision avoidance is a slacked nonlinear inequality constraint.
However, the optimizer has no notion of what's between camera and target. It can fly a path that's perfectly collision-free and still have a tree or wall sitting right in the shot. That gap is what the occlusion-aware cost below is for.
I added an occlusion-aware cost, separate from the FOV term. I march the same ESDF along the straight line from drone to target each stage, find s* (where the worst point on that segment sits), and linearize there:
When testing I observed that the occlusion cost evaluates risk at the worst point along the sightline, occ_p0 = (1-s*)·drone_p0 + s*·p_target. Differentiating w.r.t. the drone's own position gives ∂occ_p0/∂drone_p0 = (1-s*)·I, so as s*→1 (obstacle near the target) the gradient the solver actually sees scales to zero, even though r_occ itself stays large. At s*→0 (obstacle near the drone) the factor is ≈1, full gradient, but that's exactly where collision avoidance's own gradient is already active on the same obstacle.
I’m considering moving from a single-point ESDF sample to an area/volume frustum-intersection metric: how much of the camera's view cone actually overlaps the obstacle, instead of a point sample along one line.
Thank you!
##################################
Simulation details
This is a simulation of a 12-state quadrotor (position, velocity, ZYX Euler angles, body rates), 4 inputs (collective thrust + commanded body rates, matching a PX4-style body-rate setpoint interface). Formulated as a NONLINEAR_LS OCP in acados, code-generated to C and called from C++. I am using an sampled/voxel-grid ESDF as the map framework.
AI usage: camera visualisation/rendering code was AI-generated.
Hey all! I have enrolled in a graduate program titled Systems and Control Engineering. With all the uproar of AI solving some of the long standing problems in Mathematics, I am curious to know if there are any open problems in the area of controls.
From my presumption, control is just applied Mathematics with constrains defined by the real-world Physics. So, if the long standing problems in Mathematics would be solved by AI, it would imply that there wouldn't be any problems left to be solved in the area of systems and control.
So, I want to know what the community honestly thinks about this.