OpenRocket: How do you change the ejection time?

[Lt72884]

You have a drogue parachute deploying at ejection. The quickest way to see such things is on the Recovery subtab under "Motors and Configuration":
View attachment 568312

For dual deploy, you typically want to have the drogue set to apogee, and then the main set to deploy at a specific altitude.

ok, i changed it and it still does not want to override the time. I updated the laptop as well and opened the exact same file and i get an extra 600 feet. Notice the top image says L2200-22 and the second image says L2200-18. So its not overriding the ejection time for some reason. If i change it to 6 on the desktop OR, it becomes L2200-6 and altitude is then 6050feet even with deploy at apogee. However, i still cant type in NONE or custom time on the desktop like i can on the laptop..

 

[JoePfeiffer]

As @neil_w said in #19, when you're using apogee deployment the motor delay is ignored. So no, it isn't going to change it to match the time to apogee -- and users who are using altimeter deployment with motor backup wouldn't want it to. The simulation results table will tell you the optimal delay time, if that's what you're looking for (but again, the current version only lets you select from the manufacturer-provided delays. I'm guessing the reason you're seeing an 18 second motor delay is because you'd picked that one when you saved the rocket since it looks like you've updated to 22.02).

And setting main to deploy at apogee sort of defeats the purpose of a dual deploy rocket.

 

[jmasterj]

the current version only lets you select from the manufacturer-provided delays.

I've always been able to type in custom numbers for the delay, in 15 and 22.

 

[CalebJ]

I've always been able to type in custom numbers for the delay, in 15 and 22.

Now that you mention it, same here. Just went back to confirm - I can type in delay in 22.

 

[Lt72884]

As @neil_w said in #19, when you're using apogee deployment the motor delay is ignored. So no, it isn't going to change it to match the time to apogee -- and users who are using altimeter deployment with motor backup wouldn't want it to. The simulation results table will tell you the optimal delay time, if that's what you're looking for (but again, the current version only lets you select from the manufacturer-provided delays. I'm guessing the reason you're seeing an 18 second motor delay is because you'd picked that one when you saved the rocket since it looks like you've updated to 22.02).

And setting main to deploy at apogee sort of defeats the purpose of a dual deploy rocket.

correct, and thats not what is happening. It IS changing the altitude is the problem. The apogee deployment is NOT ignoring the delay time for me for some reason haha
If i change the delay time in the motor settings, it re-calculates the altitude again regardless if the deployment is set to apogee for both drouge and parachute so i know im not getting the correct simulated data.

 

[Lt72884]

Now that you mention it, same here. Just went back to confirm - I can type in delay in 22.

see and i cant. It wont accept any number or the parameter "none" for me. i posted a video of it on page one of it not working

 

[JoePfeiffer]

Now that you mention it, same here. Just went back to confirm - I can type in delay in 22.

Oops! We'd been making some refinements to the delay combobox, and somehow I wound up thinking you weren't previously able to enter a delay in seconds. My mistake.

 

[Lt72884]

Oops! We'd been making some refinements to the delay combobox, and somehow I wound up thinking you weren't previously able to enter a delay in seconds. My mistake.

he can enter the time, but i cant. Thats the other issue. I have tried so many time to input my own time and OR wont keep the time i put in. it defaults back to another number

 

[CalebJ]

see and i cant. It wont accept any number or the parameter "none" for me. i posted a video of it on page one of it not working

Which post? I'm not seeing what you're referring to.

This is what I'm talking about:


But again, none of that should be relevant if you have the parachute set to eject based on other parameters than motor ejection.

 

[JoePfeiffer]

he can enter the time, but i cant. Thats the other issue. I have tried so many time to input my own time and OR wont keep the time i put in. it defaults back to another number

Looking again, yeah. When you enter a number by hand it keeps it in the configuration, but when you go back to motor selection it has selected one of the manufacturer motors. Need to make sure our recent changes have corrected that...

But remember, the motor you're concerned about doesn't have a motor delay in the first place so it doesn't really matter.

 

[Lt72884]

Which post? I'm not seeing what you're referring to.

This is what I'm talking about:
View attachment 568389

But again, none of that should be relevant if you have the parachute set to eject based on other parameters than motor ejection.

Ok, im gonna start all over on the 2 issues im having because its confusing to me as well.
1. on the screen shot you have posted, if i change that value on my DESKTOP PC, to what the flight sim says is optimal (before setting deployment to apogee), Open Rocket will NOT keep it. I have tried to type in 22, hit ok, and OR reverts it back to some random value, usually 0 or 6. However, on my laptop, it DOES keep the value. So something is wrong with my dekstop open rocket.

2nd issue. Even with open rocket set to apogee for deployment, it is not calculating the correct altitude. How i know this is because if i change the delay time to one of the preset values 0,4,6,10,18 for the L2200, open rocket does NOT ignore the delay time and recalculates my altitude again. IE, if i have the L2200 set to 6 seconds for delay, but yet its set to deploy at apogee, it calculates my altitude to be 6000 feet rather than the 10,075 it shuld be

 

[Lt72884]

im doin the best i can to supply all the correct information. This issue has been going on for a few weeks now and its confusing me, so i can only imagine how you all feel too haha

 

[Handeman]

I had an issue with the Windows version of ProPep 3 where it would throw errors when trying to save a file. I ended up uninstalling, deleting all the folders, editing the Windows Registry and deleting all entries with ProPep in them and then installing again. The cleaning up of the registry is what ended up fixing it.

Since OpenRocket runs on Java, you might try to uninstall OR, uninstall Java, and then reinstall Java and then OR with the windows installer. If that doesn't work, you can uninstall everything and try to clean the registry before installing again. That's extreme, but might work.

 

[Lt72884]

I had an issue with the Windows version of ProPep 3 where it would throw errors when trying to save a file. I ended up uninstalling, deleting all the folders, editing the Windows Registry and deleting all entries with ProPep in them and then installing again. The cleaning up of the registry is what ended up fixing it.

Since OpenRocket runs on Java, you might try to uninstall OR, uninstall Java, and then reinstall Java and then OR with the windows installer. If that doesn't work, you can uninstall everything and try to clean the registry before installing again. That's extreme, but might work.

thtas actually a good idea. My desktop has had some funky things the last few weeks happen.

 

[T-Rex]

Inappropriate post. Deleted. My apologies again.

 

[dhbarr]

It used to be an M2030 before being slightly reduced, perhaps there's some funny remnants in the motor sims?

 

[Lt72884]

Inappropriate post. Deleted. My apologies again.

i have been busy the last 8 hours with classes so i didnt even see it.

I have to completely uninstall, refresh windows, clean registry and what not for this issue. My win 10 install is acting up... This makes me nervous that my sim data is not correct, even on my laptop haha.

 

[Lt72884]

It used to be an M2030 before being slightly reduced, perhaps there's some funny remnants in the motor sims?

i was thinking of this, maybe its some old data that was not removed. L2200's are not that popular. I could be wrong though, maybe they are popular.