![]() I have already had a look at this thread and also this thread, but they don’t mention anything similar to what I have been seeing here. ![]() It is looking like the error is not actually being calculated as zero when the measured value reaches the setpoint, which is pretty odd. The measured value starts working as you would expect, by ramping up very slowly and going up to the setpoint, but when it gets there, it keeps rising. ![]() Basically it is working as if it only had an F value.Ī similar thing happens if I have all values to zero and a small I. The steady-state error is actually even negative, with the measured value overshooting the setpoint, yet the output still stays positive. When I give it a setpoint, the output goes straight to 40% and does not change. ![]() I tried to set all values to zero and begin with only P, but it is not behaving like a P controller should. When I was trying to tune the PIDF to get a better spin up time, I found some things that make me believe the PID is not working as shown on this diagram. Currently I have a setup that works but still takes too long to spin up. Hello, I am trying to tune a PIDF on the spark max for a flywheel using two neos on a 1:1 reduction and using the internal encoder to read speed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |