@ToeTips sure, you can add of rate(Altitude) as well. Precalculate a constant value that roughly counteracts the weight, and then have a PID for rate(Altitude)
@ToeTips the realistic method would be to make one engine produce more thrust than the other to produce rotation. Try PID with the monitored value PitchRate, and target value proportional to Pitch input.
@hpgbproductions
No, the mission is to acheive stability without them.
Also it does, but i guess the Jets being different and outputing differently might be the cause.
For more context it is using an F-35B type system although it is not an F35.
Okay assuming making the thrust output of both engines equal doesnt solve the problem (I dont think it will due to the COT and COM placement), could dividing by pitchangle or even Pitchrate work?
@hpgbproductions
My setup uses two main engines (A lift fan and Main thrust)
Is it possible to like divide by pitchangle or something to keep it from tilting
@Arne2007 I already have loads
https://www.simpleplanes.com/a/Y3aA42/Nexus-R90
Just grab the thruster off the bottom of this thing and slap it on, if you're still struggling then just tell me
What I used in the past was HeliRotors but recently I started using a thruster with the input set to 0.1 and the engine to 10
(Activate4) - ((AltitudeAgl/10) + (rate(AltitudeAgl/2))
And this works great for me
Just about the most simple thing you can do is take 4 air brakes, add a couple of zeros to their power, and put them inside of each other, and make them face every main direction. And then you take an engine that is activated by the same input as the air brakes, and put it on the aircraft near the air brakes.
This causes the aircraft to stay in one place while essentially hovering. Hope this helps!
hey i just did this lol
. clamp01(PID(INPUT, rate(Altitude)/VS, 1000, 1, 1))
Replace INPUT with the input like Throttle or VTOL, and VS with the max vertical speed. This is for a very responsive engine, J15 with max 0.01
For fixed altitude agl you could replace rate(Altitude)/VS with some function using AltitudeAgl
@ArcturusAerospace check the dev console as it might have an error, or wait a minute with VTOL full up as it starts at around -17 instead of 0. I'm not entirely sure why.
i managed to get a six part rocket thing to hover with PID(VTOL, rate(Altitude), 1, 0.25, 0.5), with VTOL adjusting the climb rate. The PID values will probably need to be adjusted depending on craft weight and engine response time, and for some reason the output started off at around -17, depending on the Integral scalar, which lead to about a minute of waiting for it to return to zero.
I've been testing this a bit myself..
I think the biggest problem Is that you need the engines to work from 0 to a few Feet/meters AGL, but you'll also need thrust in the opposite direction to limit the height, so it doesn't go flying..
Another big problem, Tho I'm not entirely sure how this works.
but from what I noticed, your altitude is calculated from the Cockpit block XYZ position.
I.E. Lets say your Thrust point (engine XYZ) is 4 feet AGL when starting, and you Limit it to 10 feet AGL.
If your cockpit Starts at 9 feet off the ground, your Thrust point will be 5 feet off the ground not the 10 you setup, because the cockpit only needs to gain 1ft to reach 10 ft AGL.
@hpgbproductions
Okay, when I can I will test it out and get back to you.
@ToeTips sure, you can add of rate(Altitude) as well. Precalculate a constant value that roughly counteracts the weight, and then have a PID for rate(Altitude)
@hpgbproductions
Do i add
rate(Altitude)
in the current also?@ToeTips the realistic method would be to make one engine produce more thrust than the other to produce rotation. Try PID with the monitored value PitchRate, and target value proportional to Pitch input.
@hpgbproductions
No, the mission is to acheive stability without them.
Also it does, but i guess the Jets being different and outputing differently might be the cause.
For more context it is using an F-35B type system although it is not an F35.
Okay assuming making the thrust output of both engines equal doesnt solve the problem (I dont think it will due to the COT and COM placement), could dividing by pitchangle or even Pitchrate work?
@ToeTips are you using gyros? Those can help.
If your hover jet applies thrust in line with the CoM, your aircraft should not tilt.
@hpgbproductions
My setup uses two main engines (A lift fan and Main thrust)
Is it possible to like divide by pitchangle or something to keep it from tilting
@Arne2007 I already have loads
https://www.simpleplanes.com/a/Y3aA42/Nexus-R90
Just grab the thruster off the bottom of this thing and slap it on, if you're still struggling then just tell me
@Mixx could you make a build using this bc it won't work for me and i don't know why
@Mixx
Thanks!
What I used in the past was HeliRotors but recently I started using a thruster with the input set to 0.1 and the engine to 10
(Activate4) - ((AltitudeAgl/10) + (rate(AltitudeAgl/2))
And this works great for me
Just about the most simple thing you can do is take 4 air brakes, add a couple of zeros to their power, and put them inside of each other, and make them face every main direction. And then you take an engine that is activated by the same input as the air brakes, and put it on the aircraft near the air brakes.
This causes the aircraft to stay in one place while essentially hovering. Hope this helps!
hey i just did this lol
.
clamp01(PID(INPUT, rate(Altitude)/VS, 1000, 1, 1))
Replace INPUT with the input like Throttle or VTOL, and VS with the max vertical speed. This is for a very responsive engine, J15 with max 0.01
For fixed altitude agl you could replace rate(Altitude)/VS with some function using AltitudeAgl
@ArcturusAerospace check the dev console as it might have an error, or wait a minute with VTOL full up as it starts at around -17 instead of 0. I'm not entirely sure why.
@Avro683Lancaster
I attached an engine with it to a jet, but the engine won't power on.
i managed to get a six part rocket thing to hover with
PID(VTOL, rate(Altitude), 1, 0.25, 0.5)
, with VTOL adjusting the climb rate. The PID values will probably need to be adjusted depending on craft weight and engine response time, and for some reason the output started off at around -17, depending on the Integral scalar, which lead to about a minute of waiting for it to return to zero.I've been testing this a bit myself..
I think the biggest problem Is that you need the engines to work from 0 to a few Feet/meters AGL, but you'll also need thrust in the opposite direction to limit the height, so it doesn't go flying..
Another big problem, Tho I'm not entirely sure how this works.
but from what I noticed, your altitude is calculated from the Cockpit block XYZ position.
I.E. Lets say your Thrust point (engine XYZ) is 4 feet AGL when starting, and you Limit it to 10 feet AGL.
If your cockpit Starts at 9 feet off the ground, your Thrust point will be 5 feet off the ground not the 10 you setup, because the cockpit only needs to gain 1ft to reach 10 ft AGL.
@UltimatePlayer123
Don't understand them. At all.
you can also use a pid
@asteroidbook345
I'll try it.