![]() ![]() ![]() Leaving a blank distance vector or pressing 'u' in the input will set it to the current distance. writing "Xn.n" will change only the x-axis, "Yn.n" only the Y-axis, "Xn.n Yn.n" the X-axis & Y-axis, and so on.Įxample: writing "x-2.5 z3.7" will change the distance in x to -2.5m & z to 3.7m, leaving y to its former state. Implicitly, a distance vector set at 0 0 0 allows a smooth automatic docking (choose wisely your own waypath before or.:facepalm. When the two docks are set (target dock & user dock), trim will use your thrusters to set the target vessel at the distance defined with DST button from the user dock (user dock reference). In fact, this is not so useful (TOR & RPM are more 'graceful'). ![]() If HLD or APD is hit in the same time and relative velocity is >0.05m/s, the vessel will orient itself to the target relative velocity, allowing the use of thrusters to zeroing relative velocity. In trim alignement (one dock not set or set to 0), trim will put your vessel at the distance vector (DST button) from the target vessel ( target vessel center reference) and the relative velocity should be close to 0 on final.Ģ. Trim modes are nice for remote control (or lazy days.) but need more explanations, i admit:ġ. RPM & TOR modes are more immersive and should be used with AttitudeMFD3. My intention was not to replace totally the very helpful MFD from tblaxland (OK the name i chose is quite confusing), but only to share some tools i wrote to help my flights (dock alignement in particular, and the landing AP was included for testing pupose). new calculation in orbital trajectory prediction for better deorbiting burn time prediction, DOWNLOAD ![]() possibility of autobreak when landed to give full stop on non-flat terrain (Orbiter 2016), introduction of 3 decision landing modes with a manual cutoff alitude setting, Improvements in attitude control (internal use of quaternions for large attitude changes). Supports Orbiter 2016 elevation modeling of planetary surfaces. just remove the relevant MFD part inside the SCN file. There can be some incompatibilities with scenario saved with previous version of PMFD. It should works fine with most of the vessels (I haven't try everyone.).įor a correct control, MFD refresh rate in the Orbiter parameters should not be set too low (0.1 or less is good)Īnd the maximum acceleration should not be higher than 100x (however limited at some critical phase). To stop the background calculations, you will have to delete the spacecraft from the list in the Summary page (except the focus vessel). To do so you will have to toogle off manually the Hold mode (directly or in the Summary page). Up to 32 spacecrafts can be controlled simultaneously and every spacecraft can have up to 32 instances of PursuitMFD running in the same time.īe aware that closing or changing the mfd WON'T stop the attitude control. The landing mode can make an autoland on gravitational reference bodies with no atmosphere or tiny atmosphere (ex:Mars), with tailsitting or hovering method (pitch up or pitch down). It can also control the relative distance between the 2 spacecrafts and therefore it allows pseudo autodock (obviously a direct manual input method, not an fully autopilot). There is a docking mode which allows to set the correct orientation between the 2 docks or with the targeted vessel relative velocity. Orientation relative to orbital velocity (prograde, retrograde or whatever, TOR & RPM pitch up control) or to a target velocity,Īnd absolute orientation in ecliptic frame. Initially based on the Attitude MFD this MFD offers basic features in orbital attitude control: I release it today, after a brief overview, because it gives some corrections and improvements. This release for the 20160828 Orbiter version was written some month ago. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |