Home

SPACEBEL SAS VTS USER MANUAL VTS 2

1. r Import entities Rosetta vts Entity browser Select an entity in the source project and a proper destination to import it in the current project Source project Current project D users gmr VTS VTS dev Data Rosetta Rosetta vts D users qmr VTS VTS dev Data CubeSat CubeSat vts Element Name Element Name 4 Project 4 Project 4 Celestial Bodies 4 Q Celestial Bodies QJ Body 67C G 4 Body Earth 4 Satellites D GroundStation Toulouse W Satellite Rosetta GroundStation Clarksburg W Satellite philae GroundStation Perth D GroundStation Kourou 4 Satellites Satellite CubeSat lt Files Scenario Disabled incompatible dients Events 7 Import 3D models Import scenario states E Import default event decorations v Import icons Remove states outside current project date Import satellite event decorations Import CIC files Dialog for importing entities from an external project The hierarchy of the source project is displayed in the left pane while the hierarchy of the current project is displayed in the right pane To import an entity from the source project simply select the entity to be imported in the source hierarchy its destination entity in the destination hierarchy and click the import arrow button located between the two panes Valid destinations are listed in the above table in the Copy pasting entities section section The import o
2. 3 13 1 2 LRO Let MS Of AE Le sem E Eu Ec Pu vA SCOMANIOSLACCS asenapina asr iaa E e su aenne sp EE gen Naa nets sea same tele devas cosasvusviahedest edneuarsucedeestemeetioceras 3 13 1 2 2 Interacting with the scenario 3 13 1 3 Mission events 3 13 1 3 1 Graphical representation of events 3 13 1 3 2 Interacting with events 3 13 1 4 Project scripts 3 13 1 4 1 Graphical representation of scripts 3 13 1 4 2 Ante rating With SCFIpUS 3 deett etr rers tn eee e ger ie Mu HUN PUR MEE mn eee Rate ni 3 13 1 5 Project data TINGS oh sexe ce roe cottidie diete casebste neon rien dte tete ed bna una fem astu es EEES 3 13 15 1 Graphical representation of files ierra d eer teda te rr le lle ssrtestet rene deua E ERNER ESE eE Sedes e rune ux 3 13 15 2 Interacting with files eerte tecto eere de PNG Slee FERE NEAR ORB din aede e dao eee 3 13 1 6 Timeline toolbar tet rn RE ERREUR PR XRENSNREEORUeR INR UT seg etre ie eee ed RI UIDETUR nites 3 13 2 VieW Droberties editorom eener AR ES EEN ised EE OEA a Eea EENE EEES EA eKA an ENE TEE EER EERS wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 3 13 2 1 Scenario state properties oanien ereere Gis T eE E aE NE REOR N cue EE EE A N N AE E
3. 0 2dWin GE n Points Of Interest in 2DWin General properties POIname CNES Geographical coordinates Coordinates file CNES Sites txt L Browse ul dhe Graphic properties Color MEN Opacity 60 Size Dot Small Medium Q Big Properties of a Point Of Interest 6 1 4 8 1 General properties of a POI The general properties of a POI define its name It must be unique among other POIs in the same parent body 6 1 4 8 2 Graphic properties of a POI The graphic properties of a POI define the shape of the location markers as well as their color and opacity 6 1 4 9 Configuring a Region Of Interest A Region Of Interest abbreviated ROI represents one or many polygons in geographical coordinates Any number of ROIS can be attached to central bodies in the project Refer to the POIs and ROls in VTS chapter for more information of the ROI file format wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 r 0 2dWin Region Of Interest in 2DWin General properties ROI name France Geographical coordinates Coordinates fle Data France_Corse txt Browse F Graphic properties Color M Opacity 40 Properties of a
4. csscccesseeeseeestecsneeceessuecsaeecsuecsaeeusuecsaeesseesenaeesseeseaeeceeseneseaeeseueesaeeseneseaeesseessaseeees 7 3 6 Messages received by 2DWin u ccccsesscscccessesesssacceccessesssnseeecsessessaaescesesesssssasceesecsseesssaeesesseesasaesssesseenaaeesesesees 736d CMD PROP cormitmarids oet ecc pier epe masse legte dame aa bere q anse ane sduspusce teapduai Aer nets en ee redu nan 73 6 2 CMD STRUCT commands eie prep te eee ae eee ec 7 3 6 2 1 Central body properties ie eee einer rene ei i Ps Geese Aree 71 36 22 Satellite Propertie Ssi rre ere eter hae pen ie nie seen TENIR eR e annee eds Unis E Fee se dit vene TEE 1 3 0 23 SENSO prO OT S 73 60 24 POLDFODOTtOS issia eaii names mess ass a see ure aA s aepo tesa cetur uses a aaa a aa en eu deas p e aa aA aE a E aa AEEA NE 7 36 25 els ct ien R 7 3 7 oup ti ese tea 7 3 7 1 Time synchronization with an external time source 7 3 7 2 Supplying real time data 7 3 7 2 1 Data value date 7 3 7 2 2 Dataidentifier ise ya wa MEER CIE 7 3 8 SUmble SESSION Seem aeaaee este E EE ePy ded ue cV ras sine s ete Ero ay Pra a EN IRA e tete t ee dont ere ei Lier 7 4 DESCRIPTION OF APPLICATION PROPERTIES sss 7 22 iso o oae oe ana ee donne RUN ES o Ea nare ek o QUE o FRE Va te ud o aoa ener e taste Va v
5. Celestia Sol Earth CubeSat_ref CubeSat GS_ref wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Identifier Description Examples Sol Earth celestiaFullName Full path to the object in Celestia Sol Earth CubeSat ref CubeSat GS ref GS 3 8 2 Central body of an object Objects orbiting Earth are identified starting with the full path to Earth i e Sol Earth 3 8 3 Usage The object name name and the path to its parent parentPath are the two main elements visible to VTS users They can be found most notably in e The VTS project file format e The Synchronization protocol for VTS clients 3 9 CENTRAL BODIES IN VTS 3 9 1 Categories of bodies Central bodies in VTS a celestial objects around which orbit the main objects of a visualization i e satellites By default VTS supports the following list of central bodies in its projects e Mercury e Venus e Earth e Mars e Jupiter e Saturn e Uranus e Neptune Other bodies may also be partially supported bodies such as the Moon or some moons of solar system planets are supported out of the box by Celestia Hence they already come with predefined textures but without ephemerides in client applications other than Celestia Custom central bodies can be added to a project How
6. GR 7 3 3 3 1 CMD MME MESSIES i enne rete Erden siennes eerie EP Eden ke Haag cn De eed ete catancicnavsayegeveys a aa Eaa ENADE SANES 7 3 3 3 1 1 PAUSE COMMANA uico re rte rera eoi esent etas espe sce Sock esae sn Si oec ones sax teta e gotas ere EEEE EAEE EET 7 9 3 3 1 2 PEAY COMMANA ood er a enste insiste enims e E TWIN 73 33 1 3 lricreaseTimeRatio comimiald 5 m etse tutte actori eti isum fiae cities E tede ete D cesa ere ENTE SR dE 7 3 3 3 1 4 DecreaseTimeRatio command cccccesssssccceccesssssseeeceecesseseceeeessceseeeeeceseessasecesscesscesaueeseceseaasesesessceseeeeeeseseaes 7 3 3 3 1 5 SetlimehRatio cormimoand reti tenete Coe a re unes ea e RO Us ER Y TEE SEE cent E EREA ESSEE EEEE a ERANS iA 7 3 3 3 1 6 RevertTime command ictor cec cipem teda dene techo tes dire ne dodo asie tan e eve d end n vr Eee EVE EE hue pd 7 3 3 3 2 CMD SERVICE messages nasosini ai ATE EAA E Na a TA EA r A S STEA NE AE E N RASIN 7 3 3 3 2 1 AUTOCLOSE command 7 3 3 3 2 2 Request replies 7 3 3 3 2 3 StartApplication command 7 3 3 3 3 CMD EVENT messages 7 3 3 3 3 1 LoadFile command 7 3 3 3 3 2 ReloadEile command retener da pee ectetuer Aeae re iy ra ance pua e INE EON ER vU e Nene ind ape Eee UEM 73 33 3 3 UnloadFile COMMING orte etta ces tee lit nun eae rne yeu dao sen evo ERN ue aD o dun Eye ERN URE na ema ge ve PEE
7. Import 3d model Total size 336KB Importing a model from the catalog wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 4 1 5 The CIC CCSDS file format This file format is used for various text data e g position and attitude ephemerides Refer to the CIC CCSDS data files in VTS chapter for more information 4 2 3D FILE FORMAT IN VTS VTS relies on the 3ds file format from the Autodesk 3DS Max software suite This is a widely used file format for 3D files 4 2 1 File format of textures 3ds files can make use of external texture files These must be in bmp format and be located in the same folder as the 3ds file 4 2 2 Origin of the reference frame for the 3D file The position and orientation of objects in 3D views depends on their reference frames Refer to the following pages e Position of objects in VTS e Orientation of objects in VTS When position and orientation values are null the object s local frame is aligned with its reference frame VTS offers two options to define the local frame of a 3D object e Either use the 3D coordinates contained in the 3ds file The origin of the local frame corresponds to the point of null coordinates in the file e Either define the origin of the local frame
8. indicates that the command shall be sent to the n th instance of the client application with the specified name e X indicates that the command shall be sent to the n th client application using the order of the Applications tab of the Broker 3 16 3 Command contents Refer to the Synchronization protocol for VTS clients chapter for full details on the syntax of commands and for a list of available commands in the standard client applications In order to allow customized commands to be sent to several client applications with a single line in a script or macro file some special strings in script and macro file commands are automatically replaced before sending the command to clients e APPNAME gets replaced with the recipient client application name and ID in the following format lt Name gt lt ID gt e DATE gets replaced with the sending date in the following format yyyy MM dd hh mm ss zzz e COUNT gets replaced with a sequence number counting from 0 and shared between all script files macro files and client applications in the project e PROJECT gets replaced with the full path to the project folder Note that when taking screenshots in Celestia the PROJECT string is required at the beginning of the screenshot name to store the screenshot in the project folder Otherwise Celestia stores the screenshot in the Apps Celestia bin directory of the main VTS folder 3 16 4 Sample script file The follow
9. ee eeeeeee eene en tnn inni KOSE KORS 131 7 1 CUENT APPEICATIONSIN MTS sire ho diet e tte pho ree aeo Ere gos pa ce et cha toe VEE ai ERTELE ae TR eue Eae pa cd ecd ee coge dre xen ERR d 7 1 1 Ge ne ral architecture m tL 7 1 2 Sequence 7 1 3 Application folder hierarchy and nomenclature 7 1 4 Application IQUNCNETS 0 0E TOTO TET CETT ET EOD TE TTD TQUE 7 1 4 1 Input parameters for a launcher ss 7142 Preparing the client application etse ere ne yore Ec TRE OUR RE YR TANE RENT ee RR FREE DX nc RA a Re ROS M Ar aaiae 7 1 4 3 Building the client application s command line iii 7 1 4 4 Sample command line arguments cscccscccesseessecsseecsneesseeeseecsaeeceesssecsececsaeesseecssasesaeeseseeeaeesneseaeeceuesseeeseesesessseesseeeees 7 1 5 Application CICA ELS EE E 7 2 APPLICATION IBEATR A E gente 7 3 SYNCHRONIZATION PROTOCOL FOR VTS CLIENTS s 7 3 1 MULAO o ne gatio p AE AEA EAEE 7 3 2 Connecting tothe BEOKer sie t d o RR YR UE eR Le Ye Ye dy Eye TAE REPE C Ee FERT Teo sasdentienoeboteadenteae 7 3 3 Messages received by the Broke und aee ironia eua aea PE cavaceveddeaviesesvea sguvectaaesenesiatdeacsesscavdarveceadeseanee 7 3 3 1 INIT message connection to the Broker eene nennen enne ennt nnne nnne enne nennen enne TB 32 TIME M sSages M M Eois yp NEME GN PXULLLAIInpfe E
10. EphemerisMode Ephemeris mode of a body 167 7 5 2 7 1 5 lt Geometry gt Geometric properties of a body 167 7 5 2 7 1 6 GroupGroundStations Ground stations of a body 167 7 5 2 7 1 7 lt GroupPointsOfinterest gt Points of interest of a body 168 7 5 2 7 1 8 GroupRegionsOflnterest Regions of interest of a body 169 y 5 2 4 2 Satellite Satellite orte Fr retener rr HEP EUREN nie rire ERES URS RI Po portet ra COPS eine 7 5 2 2 1 Prop2d 5 2D properties of a satellite 5 eae cente to ee cb ete dae SEENE iS 7 5 2 7 2 2 CommonProp Properties of a satellite ss 7 5 272 3 Component Satellite COMPONENT eei ie esae ianen ai Rea Exe rene a Res PUR EAEE E NER enia dn 7 5 2 7 2 4 lt Events gt Mission events of a satellite esse 7 5 2 8 Events Event decorations for all entities is 7 5 2 9 lt IgnoredFiles gt Ignored files in the project timeline sens 7 5 2 9 1 File Ignored project file in the timeline ss 7 5 2 10 lt AdditionalFiles gt Additional files in the project timeline eene 7 5 2 10 1 File Additional file in the timeline 7 5 2 11 States Project scenario 7 5 2 11 1 Instant Scenario visualization state 7 5 2 11 1 1 lt AppState gt State properties for a client application 7 5 3
11. r Broker VTS Sla MUI 9 2 1 1 03 2010 22 03 2010 S 50 2010 03 21 ooo PEE Target 1 Celestia gt Earth 4 CubeSat Inertial cameras Full display mode The gears menu in the top left corner of the Broker offers the following options e Dock on top of screen dock the Broker in compact mode at the top of the current screen e Dock on bottom of screen dock the Broker in compact mode at the bottom of the current screen Enable always on top whether or not the Broker window should remain always on top of other windows enabled by default in compact mode Glo Mu S Real time za 21 03 10 00 00 21 03 10 08 21 03 10 12 00 21 03 10 18 00 22 03 10 00 00 M ISO 2010 03 21 08 43 09uTc 22 03 10 06 00 Docked display mode 6 2 6 Time management Controls and information regarding time are available in all Broker display modes The following interface allows interacting with visualization time Ci K NH 10x faster 3 UTC 2014 11 04 13 47 01 Q 04 11 13 00 04 11 13 30 04 11 14 00 ISO 2014 11 04T13 18 33Z MID 56965 47913 754132 JD1950 23683 5545573395 Visualization time interaction areas wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev
12. e AUTO The property has a unique value for all scenario states Its value is automatically propagated across the whole scenario upon modification Its name is displayed in italics in the view properties editor This propagation mode should be used in rare cases where the property should remain consistent during the whole project for example the visibility of a toolbar e INITIAL The property is sent to the client application upon startup and may not be altered dynamically nor resent This propagation mode must be used only for properties in the INITIAL section 7 4 6 Available cameras The CAMERAS section lists VTS cameras available in the client application Refer to the 3D Cameras tab section in the Broker user manual chapter for a description of all VTS cameras For each available camera several orientations must be implemented CAMERAS 1 type Body Synchronous 2 type Body Inertial size 2 The following VTS cameras may be declared Target entity Camera name Corresponding Broker cameras Fixed in Earth frame Body Synchronous North pole South pole Central body Body_Inertial Inertial Body Goto Goto Body Center Center Satellite Satellite Inertial Inertial cameras Sun and Body cameras Satellite Sun e View from Sun e View toward Sun Satellite SatFrame Satellite frame cameras wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 S
13. 2D properties Element Name gt Project SMOS Va satellites W Satellite SMOS Symbol File satelliteGreen png Common 2D Properties 3D Properties Geometry Custom icon for a satellite e The user may select an image file to redefine the appearance of the satellite in the 2D view and project hierarchy If the selected file is not located in a sub folder of the project folder a dialog will offer to copy the file inside the project folder 6 1 4 4 4 3D properties of a satellite The 3D properties of a satellite define its appearance in 3D views Model Approximative size 2 meters 3ds File Models Cube body 3ds Light sensitive Use 3ds coordinates Unit m v Center of gravity Coordinates in satellite frame X 0 m Y 0 m 3D properties of a satellite e The Approximate size field only applies to the current component 3ds file It has two meanings o Ifthe Use 3ds coordinates option is enabled it defines the bounding sphere of the 3D mesh to be used by clipping mechanisms This parameter should be set to a realistic value o Ifthe Use 3ds coordinates option is disabled it defines the actual dimensions to be applied to the 3D mesh of the component wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 e The 3ds
14. Catalog mode XL Catalog ephemeris mode 3 9 2 3 Custom ephemeris mode Redefine the ephemerides of an existing Celestia body or define the ephemerides of a body not available in Celestia Custom ephemerides must be defined if the current body is not available in Celestia m Fa Custom mode P User Custom ephemeris mode 3 9 3 Central body frame Coordinates of a central body are expressed in the heliocentric EME2000 frame North Pole of a central body is always the rotation North It is used to display body axes and the planetographic grid 3 10 STRUCTURE OF SATELLITES IN VTS The structure of satellites in VTS matches the organization of the elements composing a satellite wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 This structure can be found in e the VTS configuration utility in the tree hierarchy displayed in the left pane Refer to the VTS configuration utility user manual chapter e the contents of the project file Refer to the VTS project file format chapter e the View Properties and 3D Cameras tabs of the Broker Refer to the Broker user manual chapter The structure can be described as follows e A project contains central bodies and satellites o A satellite is composed of a main component which defines
15. Opening a project file by double clicking on it is currently not supported due to the VTS toolkit being portable 6 1 3 3 Saving a project The current project can be saved to disk by doing one of the following e In the toolbar click the Save button or in the File menu click the Save entry e To save the project under a different name click the Save as entry in the File menu and modify the name of the project file Beware that if the project is saved under a different folder all relative paths in the project will become erroneous 6 1 3 4 Exporting an archived project The current project can be exported as a zip archive by clicking on the Create a Project Archive entry in the File menu The vts project file all the data files in use all the symbol files in use and all the 3ds model files in use will wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 be archived Notice that all the image files bmp png or jpg found in the used models folders will be exported as VTS doesn t know which texture files are effectively reference by the models files 6 1 3 5 Visualizing a project The current project can be visualized by doing the following e Start the visualization by clicking the Run button in the toolbar or the Run entry in the Proje
16. Upmyapp Visualization startup 7 1 2 Sequence 1 The Broker reads the VTS project file and builds the list of client application instances for the project 2 The Broker executes the launchers for all client application instances 3 The launchers pre process the data for their application instances and return the command line for application startup to the Broker on standard ouput 4 The Broker executes all client application instances 5 Clients connect to the Broker on its socket and send the initialization message to indicate they are ready 6 The Broker sends the commands for the initial states of the application declared in the myAppVtsConf ini file with default values or user defined values from the VTS project 7 Clients communicate with the Broker according the the synchronization protocol described in the Synchronization protocol for VTS clients chapter 7 1 3 Application folder hierarchy and nomenclature Client applications must follow the following folder hierarchy and nomenclature e The application folder must be located in the Apps folder of the VTS toolkit The application folder name must start with an uppercase letter This name will be used as the application s name e The application executable and its launcher must be located in the bin subfolder of the application folder e The application executable must have the same name as the application folder case insensitive On a Windows platform the executa
17. wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 3 5 3 1 Quaternion A quaternion defines a rotation from an object s reference frame towards its local frame The convention used for a quaternion sets its real part as the first component A null rotation is defined by the following quaternion 1 0 0 0 0 0 0 0 All orientations can be reached Quaternions are normalized by VTS An all zeroes value 0 0 0 0 is invalid 3 5 3 2 Euler angles Euler angles define a sequence of three rotations from an object s reference frame towards its local frame The convention used for Euler angles defines the order of rotations Z X Z as e Precession around axis Z of the reference frame e Nutation around axis X of the frame resulting from the precession e Intrinsic rotation around axis Z of the frame resulting from the two previous rotations Angles are expressed in degrees All orientations can be reached There is no invalid value 3 5 3 3 Axis and angle Axis and angle rotations allow easy definition of the orientation of objects physically rotating around an axis e g solar arrays The rotation axis must be defined i e non null 0 O 0 Its coordinates are expressed in the object s reference frame The rotation angle in degrees is applied t
18. 03 01 05 06 2012 VTS MU 69 Equipe VTS SPACEBEL SAS Livraison VTS 1 3 1 temps r el 03 00 27 02 2012 VTS MU 69 Equipe VTS SPACEBEL SAS Livraison VTS 1 3 0 wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Issue Rev Date Reference Author s Reasons for evolution 02 00 19 05 2011 VTS MU 69 Equipe VTS SPACEBEL SAS Construction du manuel utilisateur depuis le contenu de la documentation Wiki 01 01 13 10 2010 VTS MU 69 Equipe VTS SPACEBEL SAS Ajout du chapitre de pr sentation g n rale Compl ment des parties manquantes de la version 1 0 Chapitre sur les plugins 01 00 15 03 2010 CELEST MU 69 Equipe VTS SPACEBEL SAS Cr ation du document wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 1 2 3 TABLE OF CONTENTS OVERVIEW Pe 15 Tides REFERENCE DOCUMENTS epe ee tne ae Yee ve duo ey e kh a Cp Fes ve ev EY EN ga ae doses ta gen Vel axo Re VE YR daca XX TERR CER RE e ER Fe e e Eva RAV red ete 15
19. 1 2 APPUCABLEDOCUMENTS ea venei e e aa a oxpiunsescenvaanddcaubengaedusnedhatiienceeaduducvinevccsensd 15 INTRODUCTION Ree E ose 16 2 1 3OVERVIEWOF VIS eiecerunt da buf up rate tie buc me en 16 2 2 MIS QUICKSTART Asian eneotee et eoe reta ee vH a Den Oeo DRAIN E detest DENN a e Qu Ve e ERR ER Ce EE ERR teen YE RUE RUNE ERN UR VER P ve EV tenet 16 2 2 1 Installing thE toolkit eene epa ba De QETRIRISE EYES la SERA ten sa en EE PAS Open ne ERR dei ERR eRRE PRA YU REF e eee o Vase papae 16 2 2 2 Starting the toolKit issss dunes R 16 2 2 3 Opening an existing project e E 17 2 2 4 Starting the visualization inserer 17 2 2 5 Interacting WIth the Btoker aiat rt re eoe rY e SS seine EXER E E TIRE O XS SERERE itunes r s eie une o soa a don 17 225 1 St rt Of a Visualization cedere te etes ter icta aaa ara EE EAER EEA EAr a r equa et olea aeie aE ra eisa eA Rda pei ders 17 2252 Eridiof a Visualization ui e erre rhet iO e name aR aa O e Aaa Ei Ee AN Ecke eS THREE Eea E aiai aea 17 2 2 5 3 Time management 2 2 5 3 1 Time controls 2 2 5 3 2 Timeline sss 22S dca Uc re 2 3 SOFTWARE REQUIREMENTS FOR V TS iive eei i eere its doivent accu aa e eE opa tu Eae ce eu amet eade ma poeta CR Nd evan dE a a Re drames ait 18 2 3 1 WHILE ACCESS DCTI
20. 1950 and modified julian day MJD days and seconds reference date November 17th 1858 The Edit date button pops up a dialog in which the current visualization time can be accurately defined in all of the above time formats Refer to the Date formats in VTS for further information on dates 6 2 7 Interacting with client applications The Timeline tab displays graphical information on the progress of the visualization The View Properties and 3D Cameras tabs allow interacting with client applications Available actions are hierarchised according to the project structure for each application The Events tab allows controlling the visibility of events in client applications Event types are displayed in a tree structure for applications that support events The Applications tab allows managing the Broker s client applications The Server tab displays information warning and error messages from the Broker or its client applications provides a log of all messages received by the Broker and sent to its clients and displays some technical information on all currently connected clients 6 2 8 Timeline tab The Timeline tab displays graphical information on the progress of the visualization wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Date 14 11 2014 Reference VTS MU 69 E B
21. 6 1 6 4 1 Clear all client application data caches sise 102 6 1 7 Orbit propagation with the Propagator iii 102 61 71 Using the PrOparato uie itti etie Roe aee Cernere e ERES EAR Se shacededesssessaccavece iaaea ee a SA aT E Eaa ERR DE 103 617411 Generating a position file uci cie eee ERE E eee HE eC e ask e SEHE HIS Eo Eres Ay ERN EA On Ege I Ede RET pua ee dique 103 6 L 7 1 2 Streaming POSITIONAL rere chive tette EE eT Oeste ee re this esee e rr PE Gee epe cU YER EY ERES RENT 104 6 2 BROKER USER PIT BE M 104 6 2 1 Command line arg ments peii e tet Pese E HH REA EAREN UE Ve FAL NERRR T EEVER ES Ce ERE EE He read vend EN ICE Ux ENTE FPES UR ERR a re 104 SES MEET ec drhuc m in 104 6 2 1 2 specificargs lt appldName gt lt SpecificArgs gt sise 104 6 2 2 Start of a visualization 6 2 3 ENG Of a VISUGIIZQTION ER 6 2 4 Leda 6 2 5 Display modes R 6 2 6 Time uvim2uqnem 6 2 6 1 Time controls 6 2 6 2 Timeline 6 2 6 3 Time information xut teet retirer seti etin cre da Eee E EX A gate e reset nes rco enter e Year Ha iaaa aai AAEE 6 2 7 Interacting with client applications ccccccccccccsesssn
22. 614 3 12 Texture ofa body aceite eere te ec ee dbi inest esistere oneri ene cer i RR ne ie ie 6 1 4 3 2 2D properties of a body 6 1 4 3 3 3D properties of a body 6 1 4 3 4 Position and orientation of a body 6 1 4 4 Configuring a satellite sss 6 1 4 4 1 General properties of a satellite 6 1 4 4 1 1 Name and central body of a satellite 6 1 4 4 1 2 Orbit path of a satellite e e T e 6 14 4 2 Events attached toa satellites sincsen INE etin EH EUER E ETE ALMAE epe ete n aa SHEER ie 6 14 4 3 2D properties of a satellite mte en te e pe pi ee ee ne eae 6 1 4 4 4 3 3D properties of a satellite enne nnne nnne nennen nnn nennt nennen nenne nnne nnn nennen 6 1 4 4 5 Position and orientation of a satellite sisi 6 41 45 Configuring a s b component ete tiene ecce re ute Fen ERU o EE Ee ETE Ee Ese Eee ide Iove Lec Ee Pe cen 6 1 4 5 1 General properties of a sub component seine 6 1 4 5 2 3D properties of a sub compon nt inen deerit Erit ii e eter eed Poor eate dct sacr E ETE EEEE SE Cua cO E ERR Niue 6 1 4 5 3 Position and orientation of a sub component ses 89 6 1 4 6 Configuring a satellite sensor seine 90 6 14 61 Generalproperties of a satellite sensor itecto det ote dieere Ide UR ERE eV ARE Y deena deo date red nhe cen 90 614 62 Properties of asatellit sensOr unici tee ettet rente tna pei tesis
23. Fr I Broker VTS amp Q Ki 9 Head 2 21 03 2010 22 03 2010 23 03 20 S urc 20032 0052 PO Log Clients Received packets Sent packets Serveur status Active on port 8888 Identifier Name Time type Socket 2dWin Constraint 1484 1 Celestia Constraint 1712 Timeline View Properties 3D Cameras Applications Server Connection state of client applications e Server status indicates the TCP port used by the Broker The following information is available for each client e Identifier the client s ID e Name the client application s name Time type the time behaviour of the client Constraint or Regulating Refer to the Synchronization protocol for VTS clients section for further information e Socket the socket ID for Broker client communication 6 2 13 3 Received packets and Sent packets tabs The Received packets and Sent packets tabs display the messages respectively received and sent by the Broker from or to client applications wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 E Broker VTS GM US wm s a Pas 2025 ae ure 2010 03 21 0
24. Orientation 7 5 3 4 2 1 lt Quaternion gt Orientation as a quaternion The Quaternion tag defines the orientation of an object as a quaternion This tag has no attributes It must contain a Value tag Refer to the Orientation of objects in VTS chapter for more information Sample Quaternion tag lt Quaternion gt lt Value gt Quaternion value The Value tag defines the value of the quaternion data Refer to the documentation of the lt Value gt generic tag in the lt Value gt Data value section for further information For a fixed quaternion value the Fixed tag must contain a character string of four real numbers defining the four components of the quaternion By convention the first component must be the real part of the quaternion Sample Value tag lt Value gt Fixed Data 1 0 0 0 Value wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 7 5 3 4 2 2 lt EulerAngle gt Orientation as Euler angles The EulerAngles tag defines the orientation of an object as three Euler angles This tag has no attributes It must contain a Value tag Refer to the Orientation of objects in VTS chapter for more information Sample EulerAngle tag EulerAngle lt Value gt Euler angles values The Value tag def
25. Visualization automatically starts to play with time ratio 1 once initialization is finished unless specified otherwise in the VTS project 2 2 5 2 End of a visualization The visualization can be stopped directly by clicking the top right cross button to close the Broker It also stops once all client applications have been closed by the user or if the VTS configuration utility is closed if the visualization was started from there 2 2 5 3 Time management Controls and information regarding time are available in all Broker display modes The following interface allows interacting with visualization time Broker VTS 04 11 13 30 04 11 14 00 ISO 2014 11 04T13 18 33Z MJD 56965 47913 754132 JD1950 23683 5545573395 Time control areas 2 2 0 0 1 Time controls The buttons in area 1 control time in all client applications wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 e Repeat Toggles loop playback for the visualization e Restart Resets time to the project s start date The play pause status remains unchanged e Play Pause Plays pauses the time flow Pausing does not prevent interaction with the visualized entities in the client applications or navigation in visualization time using the timeline e Slowe
26. client and relays the visualization date to all constrained clients similarly to what happend in playback mode To ensure correct interpolation of streamed data the Broker may introduce a delay between the moment it receives the current visualization date from the regulating client and the moment it relays it to constrained clients This delay is based on the refresh rate of Stream data it is computed as twice the maximum refresh rate of all INTERPOL mode streamed data For example if all streamed data values from a simulator are broadcasted every second the Broker will introduce a 2 seconds delay in visualization time However if all streamed data are in DIRECT mode no delay is introduced Lastly it should be noted that it is important for the visualization date sent by the regulating client to be recent i e it wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 must be a good representation of the regulating client s clock The Broker uses the system time at packet reception to relate system time to regulating client time T 3 7 2 Supplying real time data Besides visualization date data values may also be supplied by a client application This is the purpose of DATA messages DATA JD1950 date data ID data value gt For example
27. e QRect aultValue Rect 0 0 640 480 pagation MANUAL el Window geometry 1 LLITE elliteScale SatelliteScal SatelliteScale t aultValue 1 0 wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 1 propagation MANUAL 1 label Satellite scal size 1 7 4 4 Available property types There are three categories of property types basic types VTS types and Qt types 7 4 4 1 Basic types The table below lists the available basic types Type Description Example Editor bool Boolean value true false Checkbox int Integer number 42 Text box double Real number 1 618 Text box 7 4 4 2 VTS types VTS types are convenience types handled by VTS The table below lists the available VTS types Type Description Example Editor Scale factor for a celestial body double 0 5 Slider with a zoom factor of 1000 EntityScale t Scale factor for a satellite 1000 Slider with a zoom factor of 100 double SatelliteScale t Slider with min value 0 max value 1 default EntityRange_t Interval of real values 0 1 0 75 value 30 Relative path to a data file in the project folder Text field with browse button and copy dialog if Datapie t the selected file is outside the project fold
28. effect This allows drawing the sensor swath by patches e g to visualize instrument power on power off cycles wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Fichier Navigation Temps Rendu Vue Signets Aide 3 375 t Kkm Rayon 1 00004m Phaseanale 1 Satellite sensor in Celestia Satellite sensor in 2DWin wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 6 1 4 6 3 Position and orientation of a satellite sensor The position and orientation of a satellite sensor are defined as described in the Position and orientation of an entity section Transformations are expressed in the satellite s frame Note The Direction and Azimuth and elevation modes are not available for the orientation of a sensor as the induced degree of freedom implies the orientation of the sensor cannot be correctly specified 6 1 4 7 Configuring a ground station Any number of ground stations can be attached to central bodies in the project 6 1 4 7 1 General properties of a ground station The general properties of a ground station define its name position on its centra
29. linked QGLShader link Vertex shader s linked fragment shader s linked QGLShader link Vertex shader s linked fragment shader s linked QGLShader link Vertex shader s linked fragment shader s linked E lies r Timeline View Properties 3D Cameras Applications Server Logged messages The color code of logged messages is as follows e Blue informational messages about the state of the visualization Only emitted by the Broker e Orange warning messages Only emitted by the Broker These messages usually appear when an action fails without causing the visualization to stop e Red error messages Only emitted by the Broker These messages usually appear when a client application crashes e Grey messages printed to the standard output of client applications These messages are prefixed with the name of the client application that emitted them They can be either informational warning or error messages Note Always remember to send a copy of the message log to the VTS support team when an error occurs during visualization 6 2 13 2 Clients tab The Clients tab displays the connection state of client applications wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69
30. 0 000000000 Angle Constant File Stream 9 value deg 9 900000000 Orientation by axis and angle e An orientation by axis and angle is defined by the direction vector of the axis and the angle of rotation in degrees Both can be defined independently e It is possible to define a fixed axis and a sampled streamed angle as well as a sampled streamed axis and a fixed angle However it is not possible to define both a sampled streamed axis and a sampled streamed angle wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 6 1 4 2 2 4 Orientation by direction Orientation Quaternion Euler angles Axis and angle Direction Direction Constant 9 Fie Stream X 1 000000000 Y 0 000000000 Z 0 000000000 Orientation by direction e An orientation by direction is defined by a direction vector in the entity s local frame This orientation mode does not strictly define an orientation there remains a degree of freedom around the direction of the vector This mode offers a simple solution to define the orientation of a satellite component based for example on a file containing the direction of the Sun in the satellite s local frame 6 1 4 2 2 5 Orientation by azimuth and elevation Orientation Quaternion Euler angles Axis and
31. AimContourVisible Sol Earth CubeSat Sensor true Cameras CMD CAMERA lt CameraType gt lt CameraParameters gt Note that the CameraType parameter is not identical to the camera name listed in the CAMERAS section of the INI file For example CMD CAMERA CameraSensorView Sol Earth CubeSat_ref CubeSat Sensor_sens_ref Sensor 0 872665 0 349066 7 5 VTS PROJECT FILE FORMAT A VTS project file describes all the elements of a visualization It is written in XML format for clarity Its name must end with the vts extension wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 A sample file is provided at the end of this chapter 7 5 1 Notation The sections below are structured as a tree representing the XML tags contained in a VTS project file Section names follow this nomenclature e Tags written as Tag may contain other tags e Tags written as Tag are self contained they may not contain other tags e Tags written as lt 7ag gt are generic tags which are used in various contexts Generic tags are indicated under the sections of tags they may be child of However they are only fully described in separate sections outside of the main structure 7 5 2 Project Project definition The Project tag contains all
32. Approximate size label The user must also specify the unit of the 3ds file s coordinates The default unit is the meter wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 4 3 CIC CCSDS DATA FILES IN VTS 4 3 1 References The data files used by VTS and its client applications are written in the CIC CCSDS format a column based text format derived from the CCSDS OEM AEM and MPM formats This format is described in the reference document CIC exchange protocol v1 0 DCT DA PA 2009 0021267 Good knowledge of this document is mandatory when generating or altering VTS data files 4 3 2 Summary Here are some main features of the CIC CCSDS file format e Standardized header depending on file type e Data as timestamped lines e MJD date format with 2 fields respectively for days and seconds see the Date formats in VTS section e Satellite position in kilometers e Orientation as quaternions from EME2000 towards satellite local frame wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 5 STARTING VTS 5 1 1 Starting the VTS configuration utility The VTS
33. E IJ 0 2dWin cis CubeSat VTS approximative coordinates Longitude 6 398 Latitude 44 165 Altitude 723 981km Zoom on a satellite 6 3 4 2 Cursor coordinates e The cursor coordinates can be displayed by pressing the Ctrl key The coordinates expressed in latitude longitude are displayed in the window status bar e Use Ctrl left click to grab the cursor coordinates into the clipboard You can grab multiple coordinates by maintaining the Ctrl key pressed and left clicking on different locations They can be directly pasted into a POI or ROI file wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Madagasikara Lat 16 871 Long 59 4174 Grabbing cursor coordinates 6 3 4 3 Interacting with a satellite 6 3 4 3 1 Satellite lock Clicking on a satellite centers and locks the view on this satellite during the animation Zoom actions are also centered on the satellite instead of the mouse cursor Clicking the map unlocks the view 6 3 4 3 2 Geographical coordinates Hovering the mouse over a satellite or ground station displays a tooltip containing their geographical coordinates These coordinates are computed by VTS and are approximate especially when computing the longitude near the pol
34. GENECHIC TAGS REED E PB Bed lt S nsor GO O nement Nain nets 15 31 41 lt SensorProp gt Sensor properties insisi an aaraa E E ae AAR a ARa Raa 7 5 3 1 1 1 SensorAttributes Physical properties of a sensor ccesccsssescessesssesscsecssessesesscsesseesesecsessessaesesensseeseateaesoaes 7 5 3 1 1 2 SensorGraphics Graphic properties of a sensor ssssssesseesseeeeeeee nennen nnne nnne 7 5 3 1 2 Geometry Geometric properties of a Sensor eene eene nennen nnne nnne enne nennen 7 5 3 2 Prop2d 2D properties onec heec ar e e EU Ps cete E Gv dese rv cheveu dense 7 5 3 2 1 SymbolFile 2D symbol file sine 7 5 3 3 Graphics3d 3D graphic properties secre oceedenasceesnxssdecesuca da NAR ICE ERR Y RENE REPRISE VERSA SEEN RD REDE ARE YI QA ERR QA pA n ME SITSERS PIE 7 5 3 3 2 Radius Radius of an object iii 7 5 3 3 3 LightSensitive Light sensitivity of an object 7 5 3 3 4 Use3dsCoords Usage of an object s 3DS coordinates eessssssesseeseeee nennen nnne nnns 7 5 3 3 5 lt RotationCenter gt Rotation CENter ccccccccccsccccsssccsssscesscceseeescsssscceesesccsuasesuessussesusesecesaseceusseccuseseneuaesesesaseeaaeess 75 344 Geometry Geometric properties oiii estre coperte degree dress anse IR ane E lecce RE eevee Pere dece qud 7 5 3 4 1 Position Position of an obje
35. MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 e Quality Low Medium High Quality factor determining the bitrate of the recording e Pause visualization when starting recording Option allowing to start the recording paused at the current visualization time e The movie bitrate is proportional to the movie definition e The quality factor increases or decreases the quality of the movie A Low quality factor produces compression artifacts on moving parts in the video but smaller file size A High quality factor produces good quality video but significant file size The recording can be stopped with the Stop recording entry in the Broker s action menu The Ctrl R keyboard shortcut can also be used when the Broker window is focused File Navigation Time Render View Bookmarks Help CIC SAT Dis 218 km Rac pb ee ee ee PRESSE Gea au P555 Timeline ViewProperties 3D Cameras Server Log 1 Recording area The screen area located within the red frame is recorded in the movie The mouse pointer is not recorded During the recording it is advised not to move recorded windows and to use camera states rather than manual camera movements Otherwise since the movie is not recorded at real time speed camera movements may appear to be slower or faster than expected During the recording additional information is displayed in the Log tab of
36. ORIGINATOR PROTON META_START COMMENT PROTON OEF file COMMENT Misc columns PSO Lat Long Cycle Orbit OBJECT_NAME OBJE CES ED PLEIADES RHR USER_DEFINED_PROTOCOL NONE USER_DEFINED_CONTENT OEF USER_DEFINED_SIZE 6 USER_DEFINED_TYPE STRING USER_DEFINED_UNIT n a TIME_SYSTEM UTC META_STOP 56273 0 000000 DAS_Update_TC_CHCOMRLDDAS mu MESSIS ctae VS RIA 56273 126 809000 AUS 0 DEG AOS LS RATS SR OS NES SPA SES a DIOZH S82 1000 AUS MAX ELEVATION PASS aU MAS SEM MESSE SN Wen WZW 56273 438 342000 AUS 0 DEG LOS US su MGI eu West RC UNSURE 56273 453 909000 STH 0 DEG AOS OS E SO 2 GE ESS SAN Ve 02727 56273 510 640000 STH PHYSICAL_AOS Was WO So Wee SEM We waa 56273 566 297000 STH MAX ELEVATION PASS WU SIL IGS PAIL woes sw MEN 02720 SIG 2 NEGNECPIEI9O009O0 KRN 0 DEG AOS GS miu WP SAGE CMS ECTS GES LZIN KRN PHYSICAL_AOS OS OA A o E MM 56273 678 672000 STH PHYSICAL_LOS UOMO US quw wed Oey M USE 5623 672000001 STH 0_DEG_LOS MST OI ws rw MASON Ee 56273 656000 AUTONOMOUS_MODE_GAP SUP_START 72 TOANT OTN W 50 17 ew S272 56213 478000 KRN MAX ELEVATION PASS rcc LEER M E MEL MM Cora 56273 998000 EARTH_IN_SENSOR_START 3 WA SI WAG OOY Was SAT MG 02727 56213 998000 SUN_IN_SENSOR_START 3 TET SIS UY SU VESS eU WE Ug 56273 998000 SUN IN SENSOR END 3 UB WS Tw wedge one VON wegeu 6299 835000 KRN PHYSICAL LOS DISCO GLEN Wem argu HAN 2727 562179 478000 NPL 0
37. Region Of Interest 6 1 4 9 1 General properties of a ROI The general properties of a ROI define its name It must be unique among other ROIs in the same parent body 6 1 4 9 2 Graphic properties of a ROI The graphic properties of a ROI define the color of the polygon and its opacity 6 1 4 10 Configuring a client application Any number of client applications may take part in the visualization of a project The view properties of these applications can be configured in the project scenario wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Selecting an application in the project hierarchy some information and parameters e Text information about the application found in the application s README file e Some applications define parameters which must be passed on to the application once it has successfully connected to the visualization Those can be specified in the Initial States area e Some applications require specific parameters to be passed on to their launchers Those can be specified in the Specific Args field Information README Dummy for VTS Dummy full blown client Useful for debugging Broker dient related issues Initial States Property name Value 4 Application parameters Absolute file D absolute txt Relative f
38. SatFrame Satellite QswFrame and Satellite TnwFrame Go to the target object and attach to its reference frame This is the camera used by VTS for INI camera types Body Goto and Satellite Goto Point towards the target object The camera remains at its current location attached to its current reference frame This is the camera used by VTS for INI camera types Body Center and Satellite Center Position the camera along the normal vector of the target object s orbital plane pointing along that vector so that the full orbit path of the target object can be Seen This is the camera used by VTS for INI camera type Satellite Orbit Position the camera from the target sensor s point of view pointing along its aim direction The field of view should be adjusted to match that of the sensor This is the camera used by VTS for INI camera type Sensor SensorView See also Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 See Camera name Parameters unit Description also sensorName Celestia full name of the target sensor e g Sol Earth CubeSat_ref CubeSat Sensor_sens_ref Sensor halfAngleOnX and halfAngleOnY real number in radians ru as i i i aperture half angles of the target sensor amerasensorView excep WindowSensorviow that the window is resized width integer number in pixels final width of the window Height to fit exa
39. SensorGraphics Graphic properties of a sensor The SensorGraphics tag defines the graphic properties of a sensor i e its appearance in client applications See Attribute Description Format unit also Maximum display distance of the sensor Range volume in 3D Real number kilometers Three real numbers for red green blue in the 0 1 VolumeColor Color of the sensor volume in 3D range no unit VolumeOpacity Opacity of the sensor volume in 3D Integer in the 0 100 range percentage Three real numbers for red green blue in the 0 1 ContourColor X Color of the sensor footprint in 2D and 3D range no unit Only the ContourColor attribute is used for a ground station sensor Other attributes must be present but their values are unused Refer to the Sensors in VTS chapter for more information Sample SensorGraphics tag SensorGraphics Range 10000 VolumeColor 0 1 0 603326 VolumeOpacity 60 ContourColor 0 1 0 603326 gt SensorTrace Graphic properties of the sensor swath trace The SensorTrace tag defines graphic properties specific to the sensor swath trace for both 2D and 3D applications This tag may not be present under a ground station sensor Attribute Description Format unit See also Duration Duration of the sensor swath trace Real number hours Opacity Opacity of the sensor swath Integer in the 0 100 range percentage A null trace duration displays the instantaneous sensor swath in
40. The file must be in bmp jpg or png format The image will be scaled down to icon size 82x32 before use in 2DWin Refer to the 2dWin user manual chapter for more information If the file name is empty the default icon is used for the object The file name must be relative to the project folder Sample SymbolFile tag lt SymbolFile Name Images ISS jpg wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 1 5 9 3 lt Graphics3d gt 3D graphic properties The Graphics3d tag contains all tags related to the 3D graphic properties of a visualization object This tag has no attributes Sample Graphics3d tag lt Graphics3d gt 7 5 3 3 1 lt File3ds gt 3DS file The File3ds tag defines the 3D file in 3DS format containing the 3D model of an object for use in 3D views Attribute Description Format unit See also Name 3DS file name Character string 3D file format in VTS The file must be in 3ds format The file name must be relative to the project folder Sample File3ds tag lt File3ds Name Models ida ida 3ds gt 7 5 3 3 2 lt Radius gt Radius of an object The Radius tag defines the bounding sphere radius of the 3D model of an object Attribute Description Format unit See also Value Object radius Real kilometers
41. and attitude data have been saved to files 3 3 3 Stream data source This data source is based on a network stream defined by the user upon selection of the source This source can be used for the ephemerides of celestial bodies satellites as well as for the position and orientation of mobile parts on satellites It is most adequate for online visualization in which the position and attitude data are streamed on the fly by external applications such as a simulator The Stream data source provides two modes of operation e INTERPOL in order for visualization clients 2dWin Celestia etc to use interpolated values the Broker will introduce a slight delay between data transmission and time synchronization with visualization clients e DIRECT the data update rate is not taken into account while computing time synchronization delay Beware that no extrapolation is done in standard VTS clients See also the documentation for Real time VTS in the Synchronization protocol for VTS clients chapter wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 3 4 POSITION OF OBJECTS IN VTS The position of an object in VTS is defined as a translation from the object s reference frame towards its location The position can be fixed sampled or streamed This se
42. application name is used by the VTS Broker to build the path to the application s executable The unique application ID is used by the VTS Broker to identify clients upon connection and during the visualization Sample Application tag Application Name Celestia Id 1 gt 7 5 2 6 1 1 SpecificArgs Additional parameters for an application The SpecificArgs tag defines additional command line parameters for an application These parameters are automatically passed to client applications upon startup Attribute Description Format unit See also Args Parameters list Character string Application launchers The parameters list is stored as is in the project file Sample SpecificArgs tag lt SpecificArgs Args bds BDS PHR1A tcl 7 5 2 7 lt Entities gt Entities of the visualization The Entities tag contains all entities of the visualization satellites ground stations sensors etc This tag has no attributes Sample Entities tag Entities 7 5 2 7 1 Body Central body The Body tag defines a central body for the visualization wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Attribute Description Format unit See also Name Central body name Character string Central bodies in VTS ParentPath Path to the body s p
43. architecture also allows it to be extended with any number of compatible applications The toolkit comes with a configuration utility which allows the definition of the elements in the visualization 3D models geometry and mobile parts of the satellites data sources for all positions attitudes angle of rotations etc It also allows configuration for satellite sensors and ground stations for the visualization scenario and for the applications involved in the visualization VTS then uses this configuration to run the animation It handles starting and synchronizing all the chosen applications Its core element the Broker offers functionality for navigating in visualization time controlling 3D cameras and defining a range of other display attributes It also broadcasts visualization settings associated with each scenario state to client applications VTS is designed in a way that allows connected applications to control the visualization time eg time ticks from a simulator time navigation in a plotting software etc As for the visualization data they can be provided either through files or network streams which are broadcasted to all clients The synchronization procotol for client applications is specific to VTS however the data files are based on a CCSDS standard allowing direct compatibility with all tools handling this european format On the technical side VTS relies on Celestia as its default 3D visualization tool Celestia is fre
44. client applications without residual display The SensorTrace tag may contain no child tag or a single FixedColor tag or ColorFile tag If empty the sensor swath color is defined as the satellite s orbit path color be it a fixed color or the color from a color file attached to a Position value This is the Orbit path color sensor swath color mode in the VTS configuration utility Refer to the Graphic properties of a satellite sensor section in the VTS configuration utility user manual chapter for more information Sample SensorTrace tag lt SensorTrace Duration 2 Opacity 60 gt lt FixedColor gt Fixed color for the sensor swath The FixedColor tag defines the fixed color of the sensor swath in client applications wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Attribute Description Format unit See also Value Color for the sensor swath Three real numbers for red green blue in the 0 1 range no unit If present this tag selects the Fixed color sensor swath color mode in the VTS configuration utility Refer to the Graphic properties of a satellite sensor section in the VTS configuration utility user manual chapter for more information Sample FixedColor tag FixedColor Value 1 0 0890059 0 lt ColorFile gt Colo
45. component The Component tag defines a satellite component Some properties of the satellite itself are described in its top level component not visible in the GUI This tag is recursive i e it may contain any number of children Component tags which may themselves contain more Component tags This allows describing an arbitrarily complex satellite structure Refer to the Structure of satellites in VTS chapter for more information Attribute Description Format unit See also Name Component name Character string Structure of satellites in VTS The top level component s name is not used the satellite s name is used instead Sample Component tag Component Name GS gt lt Graphics3d gt 3D graphic properties of a component wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 The Graphics3d tag defines the 3D graphic properties of a satellite component i e its 3D model radius etc Refer to the documentation of the lt Graphics3d gt generic tag in the lt Graphics3d gt 3D graphic properties section for further information lt Geometry gt Geometric properties of a component The Geometry tag defines the position and orientation of a satellite component Refer to the documentation of the lt Geometry gt tag in the lt Ge
46. coordinates file of a POI The CoordinatesFile tag contains the coordinates file name of a POI Attribute Description Format unit See also Name Name of the CIC CCSDS file Character string Graphics graphics properties of a POI The Graphics tag contains the graphics properties of a POI Attribute Description Format unit See also Three real numbers for red green blue in the 0 1 range Color Color of the point of interest no unit wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 See Attribute Description Format unit also Opacity Opacity of the point of interest Integer in the 0 100 range percentage Size of the POI DOT SMALL MEDIUM BIG Integer in the 0 3 range no unit PointSize Sample PointOfinterest tag lt PointOfInterest Name Madagasikara gt lt CoordinatesFile Name Madagasikara txt gt lt Graphics Color 0 0 313832 1 Opacity 100 PointSize 2 gt PointOfInterest 7 5 2 7 1 8 lt GroupRegionsOfinterest gt Regions of interest of a body The GroupRegionsOflnterest tag contains the list of all regions of interest on a central body This tag has no attributes Sample GroupRegionsOflnterest tag GroupRegionsOfInterest lt RegionOfinterest gt Ground station The
47. e the icon displayed in the VTS configuration utility and for projections in 2DWin If this tag is not available and the central body is a standard VTS central body then its default 2D properties are used Refer to the documentation of the lt Prop2d gt generic tag in the lt Prop2d gt 2D properties section for further information 7 5 2 7 1 3 lt Graphics3d gt 3D graphic properties of a body The Graphics3d tag defines the 3D graphic properties of a central body i e its 3D model radius etc If this tag is not available and the central body is a standard VTS central body then its default 3D graphic properties are used Refer to the documentation of the lt Graphics3d gt generic tag in the Graphics3d 3D graphic properties section for further information 7 5 2 7 1 4 EphemerisMode Ephemeris mode of a body The EphemerisMode tag defines the ephemeris mode of a body Attribute Description Format unit See also Mode Ephemeris mode enum Default Character See the Central bodies in VTS for more informations Catalog or User string about the different modes 7 5 2 7 1 5 Geometry Geometric properties of a body The Geometry tag defines the position and orientation of a central body If this tag is not available and the central body is a standard VTS central body then the default ephemerides are used Refer to the documentation of the Geometry tag in the Central bodies in VTS and l
48. ec aaan eds iE eres EE ee EEE EA Ea E aE a 90 6 1 4 6 2 1 Physical properties of a satellite sensor sens 90 6 1 4 6 2 2 Graphic properties of a satellite sensor sisi 91 6 1 4 6 3 Position and orientation of a satellite sensor seen 93 61 4 7 Configuring a amp rouhd station eee iter c ede ren Insee TR cer Ela da apis en ca EE etuer In a A RE caste dm late eiunatee 93 6 1 4 7 1 General properties of a ground station eee 93 6 1 4 7 2 2D properties of a ground station siennes 93 6 1 4 7 3 Properties of a ground station sensor eb e asta o eue aie aec aec te oe een sees 94 6 1 4 7 3 1 Physical properties of a ground station sensor 94 6 1 4 7 3 2 Graphic properties of a ground station sensor is 94 6 14 83 Configuring a Point Of Interest scenic e eet he e ee a E Eri e eee VERE ip Cue NER ohne 95 6 1 4 8 1 General properties of a POI eene nennen nnne nennen entrent nensi inni nrn nennen tenen nennen ennt nn nennen 96 6 1 4 8 2 Graphic properties of a POI siii iere tori Eee a Eau EEA EA xag tua pupa diner Ya De Ev aSE CA SENA T Ue EEE die urnes 96 6 14 9 Configuring a Region Of Int r st cie eiim eie io Det etd rnt a Ee la Eo A CRT MESE su seed dexeseedsenssaceeaeadssecavauceaseacaueas 96 6 1 4 9 1 General properties of a ROI 97 6 1 4 9 2 Graphic properties of a ROI m 97 6 1 4 10 Configuring a client application m em 2 s 97 6 1 5 CONFIQUTING event types sarrasina eens aia iaee a aR
49. for 3DS coordinates Real number no unit A value of 1 enables usage of 3DS coordinates A value of 0 disables usage of 3DS coordinates The scale factor applies to the default mesh coordinates unit the meter Thus e value of 7 defines coordinates in meters e A value of 0 001 defines coordinates in millimeters e A value of 1000 defines coordinates in kilometers Refer to the 3D file format in VTS chapter and to the 3D properties of a satellite section of the VTS configuration utility user manual chapter for more information Sample Use3dsCoords tag lt Use3dsCoords Value 1 MeshScale 0 1 gt 7 5 3 3 5 RotationCenter Rotation center The RotationCenter tag defines the position of the rotation center of an object Attribute Description Format unit See also X X coordinate of the rotation center Real number Y Y coordinate of the rotation center Real number Orientation of objects in VTS Z Z coordinate of the rotation center Real number Refer to the Rotation center section of the Orientation of objects in VTS chapter for more information Sample RotationCenter tag RotationCenter X 2 252 Y 0 Z 0 649 gt 7 5 3 4 lt Geometry gt Geometric properties The Geometry tag defines the geometric properties of an object i e its position and orientation This tag has no attributes Sample Geometry tag lt Geometry gt 7 5 3 4 1 lt Position gt Position of an object The Position tag defines the pos
50. go M o E TCLOG Hee m o o 6G amp uu Timeline View Properties Events 3D Cameras Applications Server Mission events visibility e The list of client applications allows selecting the target client when setting the visibility of mission events e The event type hierarchy displays all event types and allows setting the visibility of an event type for all satellites or for each satellite individually The value indicated in parentheses is the number of events of the corresponding event type in all event files e The visibility status of all event types is maintained in the scenario states and is hence saved between states and visualization sessions e Mission events are also displayed in the Timeline tab for each satellite For more information on events in VTS refer to the Mission events in VTS chapter 6 2 11 3D Cameras tab The 3D Cameras tab allows interacting with standard visualization cameras in 3D applications The various cameras are displayed in a hierarchical fashion for all visualization entities and each column corresponds to a specific instance of a currently running 3D client application wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 r Broker V
51. gt Sensor The Sensor tag defines a sensor either attached to a ground station or to a satellite component Attribute Description Format unit See also Name Sensor name Character string Sensors in VTS The sensor name identifies the sensor It is not used for a ground station sensor Sample Sensor tag lt Sensor Name Panchromatic gt 7 5 3 1 1 lt SensorProp gt Sensor properties The SensorProp tag contains the properties of a sensor both physical and graphic This tag has no attributes Sample SensorProp tag lt SensorProp gt 7 5 3 1 1 1 lt SensorAttributes gt Physical properties of a sensor The SensorAtiributes tag defines the physical properties of a sensor i e its shape and aperture angles Attribute Description Format unit See also SensorType Sensor shape Character string ELLIPTICAL or RECTANGULAR Sensors in VTS HalfAngleX Aperture half angle around X Real number wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Attribute Description Format unit See also HalfAngleY Aperture half angle around Y Real number Refer to the Sensors in VTS chapter for more information Sample SensorAttributes tag SensorAttributes SensorType ELLIPTICAL HalfAngleX 0 174533 HalfAngleY 0 174533 7 5 3 1 1 2
52. is colored and tooltips are available In the screenshot below this display mode is used for line 3 e Event mode Each value is displayed as a diamond at the date of the value Diamonds of identical color indicate identical value In the screenshot below this display mode is used for line 4 e Interval mode Identical to Normal mode except that neutral values 0 for real or integer data are not displayed This mode offers better contrast to visualize the contents of files with on off status such as in out of eclipse status for a satellite etc In the screenshot below this display mode is used for line 5 e Gradient mode The whole file is displayed as a single rectangle filled with a color gradient indicating the value variations in the file This mode offers better visualization of the evolution of values in a file but may not be suited to files of dimension greater than 1 In the screenshot below this display mode is used for line 6 e Color mode Identical to Normal mode except that the color of each rectangle is derived by interpreting the corresponding value as a color This mode allows displaying the contents of color files and is only available for data which may be interpreted as a color i e files of real or integer data of dimension 3 or 4 In the screenshot below this display mode is used for line 7 e Graph mode all values are displayed as a graph This is a preview of the content of the file and may not replace a prop
53. is selected for files of significant size 3 13 1 5 2 Interacting with files The following actions are available for file headers e Double clicking the header sets the zoom level and pans the timeline so that the line s width fits in e The File properties button opens a pop up window with information on the file and parameters controlling its appearance in the timeline e The Remove file button removes the file from the timeline Files referenced in the project structure are not removed from the project they are merely hidden in the timeline and will remain so until they have been added back The file properties pop up apart from displaying information on the file offers the following actions e The Edit file button opens the file in a text editor e The Display mode drop down list allows selecting the display mode for the file e The Merge identical values option enables disables the merging of consecutive identical values in the file into a single value item rectangle or diamond This is on by default to improve the clarity of the timeline s contents e The Color overlay option enables disables the color file overlay for OEM position files Note that the number of lines is not displayed in the Properties tab for partially loaded files Right clicking on values in the file s line displays a context menu with the following actions not available in Block and Gradient modes e The Go to event Go to interval start Go to i
54. once they are synchronized with the current visualization date The Broker will capture a movie frame once all client applications have replied or timed out Note Once the SynchroRequested request has been issued by the Broker client applications are expected to send back a Synchronized command within 500 milliseconds Beyond this time frame the synchronization request will time out for clients which have not responded wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 7 3 4 2 2 3 Other commands TakeScreenshot command The TakeScreenshot command instructs client applications to take a screenshot of the visualization scene This may be used within scripts to save an image of the visualization at specific dates This command has the following syntax CMD SERVICE TakeScreenshot Filename Parameter Description Format unit See also Filename Name of the image file to save the screenshot to Character string The file path must be relative to the project folder 7 3 4 2 3 CMD EVENT messages CMD EVENT messages instruct client applications to add remove or reload CIC CCSDS mission event files attached to project entities 7 3 4 2 3 1 LoadFile command The LoadFile command instructs client applications to load a new CIC CCSDS even
55. project elements II defines the revision number of the VTS configuration utility used to generate the file This revision number is used to guarantee backwards compatibility of project files The current format of this tag has been introduced at revision r1168 If not found the XML reader will attempt loading the project file with an older schema Attribute Description Format unit See also Revision Project revision Positive integer Backwards compatibility in VTS Sample Project tag Project Revision 1645 gt 7 95 21 lt General gt General project parameters The General tag defines the general parameters of a project in its attributes Attribute Description Format unit See also Name Project name Character string e Real number JD1950 StartDateTime Visualization start date e Integer Real number MJD default Date formats in VTS e Character string ISO e Real number JD1950 EndDateTime Visualization end date e Integer Real number MJD default Date formats in VTS e Character string ISO Sample General tag lt General Name CubeSat StartDateTime 21994 000000000 EndDateTime 21995 975690000 gt wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 7 95 22 lt MetaData gt Meta information about the project The Me
56. responsibility wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 3a User Input Broker PAUSE Broker VTS our S Re ih prc t i UTC 16 07 1 CIC Sat POSITION VELOCITY TXT 2 CIC Sat SATELLITE ECLIPSE TXT j E i lt gt LALI FPS Timelne View Properties Events 3D Cameras Applications Server Master Time Loop Socketsever Socketsever 1 Connect Init 1 Connect Init message 3b PAUSE message 2 Time 2 Time each 500ms each 500ms Socket client Socket client Client A Client B Mimi Iso Celestia Jal Local Time Loop Local Time Loop Basic synchronization between Broker and clients wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 4 FILES USED BY VTS 4 1 DATA DESCRIPTION FOR VTS PROJECTS 4 1 1 Hierarchy of a project folder A VTS project consists in a folder containing one or several project files vts file extension and a set of data files used by client applications during visualization The project folder is the root folder contain
57. the Broker during visualization Please refer to the Real time VTS section in the Synchronization protocol for VTS clients chapter for further information on data streaming in VTS File mode Realtime mode Stream ID Streaming mode in the Propagator In this mode the user must define a stream ID e g pos and a time ratio The Propagator starts streaming the generated position data and time data at a 1Hz rate when the Broadcast button is clicked Time ratio 1 00 6 2 BROKER USER MANUAL The Broker is the core application of the visualization phase It starts the client applications regulates the visualization time sends user commands to the client applications and much more 6 2 1 Command line arguments The Broker is started by the VTS configuration utility when the Run button is clicked It can also be started from the command line either directly or through the startVTS binary When started from the command line the following arguments can be specified 6 2 1 1 project lt File vts gt This argument tells the Broker which VTS project file to load and visualize Example broker project C Project CubeSat vts 6 2 1 2 specificargs lt appldName gt lt SpecificArgs gt This argument defines additional arguments which will be passed on to client applications upon startup Client applications can be identified in several ways e The application ID 1 2 etc e The application name Celestia 2dWin e
58. the body of the satellite component may contain sub components These may themselves contain sub components A component may contain sensors The naming scheme of objects relies on this structure e g Sol Earth CubeSat GS See also the chapter about Object paths in VTS NB Throughout this documentation and the VTS GUI satellite components are sometimes referred to as subparts 3 11 SENSORS IN VTS A sensor is either an onboard element on a satellite or an element of a ground station This section presents the properties of sensors in VTS and their representation in client applications 3 11 1 Properties of a sensor When orientated by a quaternion euler angles or axis and angles a sensor is defined by a conical aim volume around the Z axis its apex being located at the origin of the sensor s local frame The sensors s base can be either elliptical of rectangular The cone is characterized by two half angles around the X and Y axes see the Orientation of objects in VTS chapter concerning the reference frame These angles define rotations of the sensors s aim axis around the X axis in the YZ plane and Y axis in the XZ plane When orientated by a direction or altitude and azimuth an additional rotation is made X becomes the main axis i e the sensor looks at the given direction Since the third self rotation is not reliable this orientation mode should be used only with elliptical sensors with similar X and
59. the initial state of the visualization e a grey flag for a disabled state Broker only Also an orange star appears on states which have been modified but not saved In the VTS configuration utility clicking a state makes it become the active state In the Broker the active state is the first enabled state to the left of the time cursor When the time cursor moves past a new state in the Broker it becomes active and its visualization properties are sent to the corresponding client applications This allows for example precisely setting the camera at a user defined location upon key events of the visualization instrument acquisition ground station communication orbital maneuver etc Note that a disabled state is never active when disabling the active state the first enabled previous state becomes active The initial state of the visualization is a fictional state mirroring all scenario states prior to the project s start date It cannot be removed or disabled and its date is automatically adjusted when the project s start date changes 3 13 1 2 2 Interacting with the scenario Right clicking the scenario displays a context menu with the following actions e The Create state entry creates a new scenario state at the selected location e The Select current state entry marks as active the first enabled state to the left of the selected location wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual
60. to paste a component as a sub component of itself a special paste entry is available in the context menu as Paste as subpart When copy pasting an entity all of its structural properties i e those set in the Structure tab are copied and pasted as well as all its scenario properties i e those set per application and per state in the Scenario editor tab Entities are pasted as they were upon copy if an entity is copied modified then pasted the new entity will have the properties its source entity had at the time of the copy The following table lists the compatible destination entities for each source entity Source entity type Valid destinations Central body Project Celestial bodies item Ground station Body Ground stations item Point Of Interest Body Points Of Interest item Region Of Interest Body Regions Of Interest item Satellite Project Satellites item Body Component Satellite SubPart Sensor Satellite Destinations for pasting a copied entity 6 1 3 8 Importing entities from an external project VTS allows entities to be imported into the current project from an external project file This feature is available wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS Reference VTS MU 69 through the Import entities entry in the Project menu VTS MU G 69 SPB Issue 05 01 Date 06 03 2014 Rev Date 14 11 2014
61. width fits in e The File properties button opens a pop up window with information on the script file e The Remove file button removes the script from both the timeline and the project Right clicking on a script command displays a context menu with the following actions e The Go to command entry sets the visualization date to the date of the selected command Broker only e The Select state for command entry marks as active the first enabled state to the left of the selected command e The Create state at command entry creates a new scenario state at the date of the selected command 3 13 1 5 Project data files Data files used by the project position and orientation of satellites sensors etc are displayed in the timeline Each file has its own line 3 13 1 5 1 Graphical representation of files The header of each line shows the name of the file The following display modes are available e Normal mode Each value is displayed as a rectangle extending from the date of the value to the date of the next value Rectangles of identical color indicate identical value In the screenshot below this display mode is used for line 2 e Block mode The whole file is displayed as a single rectangle This display mode is used for files with more than 300 lines or bigger than 500Kb so as not to overload the timeline When the file contents have not been read the block is colored in gray and no tooltip is available Otherwise the block
62. 0 00 55 PO RR Log Clients Received packets Sent packets V TIME 7 CMD V DATA System time Client ID Message El 15 02 00 353 1 Celestia CMD SERVICE SaveStateFinished 15 02 00 333 1 Celestia CMD SERVICE StoreCommand CMD PROP SatelliteLabelsVisible true 15 02 00 333 1 Celestia CMD SERVICE StoreCommand CMD PROP AmbientLight 0 30000001192093 15 02 00 333 1 Celestia CMD SERVICE StoreCommand CMD PROP SelectObject Sol Earth CubeSat 15 02 00 333 1 Celestia CMD SERVICE StoreCommand CMD PROP CameraDesc lock Sol Earth C 15 02 00 332 1 Celestia CMD SERVICE StoreCommand CMD PROP equatorialgrid false 15 02 00 328 0 2dWin CMD SERVICE SaveStateFinished 15 02 00 328 0 2dWin CMD SERVICE StoreCommand CMD PROP ViewInfos Default 15 01 53 182 1 Celestia CMD SERVICE SaveStateFinished a 15 01 53 150 1 Celestia CMD SERVICE StoreCommand CMD PROP SatelliteLabelsVisible true 15 01 53 149 1 Celestia CMD SERVICE StoreCommand CMD PROP AmbientLight 0 30000001192093 15 01 53 149 1 Celestia CMD SERVICE StoreCommand CMD PROP SelectObject Sol Earth 15 01 53 149 1 Celestia CMD SERVICE StoreCommand CMD PROP CameraDesc bodyfixed Sol Ea _ Timeline View Properties 3D Cameras Applications Server Messages received from clients TIME messages deal with time synchronization of clients while CMD messages are related to client commands All messages are displayed truncated when they are too long Further inf
63. 01 Date 14 11 2014 Reference VTS MU 69 6 2 6 1 Time controls The buttons in area 1 control time in all client applications e Repeat Toggles loop playback for the visualization e Restart Resets time to the project s start date The play pause status remains unchanged e Play Pause Plays pauses the time flow Pausing does not prevent interaction with the visualized entities in the client applications or navigation in visualization time using the timeline e Slower Decreases the time ratio Two clicks on this button result in a 5 times slower time flow The current time ratio is displayed next to this button e Faster Increases the time ratio Two clicks on this button result in a 5 times faster time flow e Revert Every click on this button inverts the time flow direction The time ratio remains unchanged 6 2 6 2 Timeline The timeline 2 displays the visualization s time range Dragging the cursor controls the visualization s current time While moving the cursor the current time is kept updated in all client applications synchronously For finer or coarser grained time control the timeline can be zoomed in out using the mouse wheel 6 2 6 3 Time information A text area 3 displays the current visualization time The default format is the ISO time format date and time in UTC The arrow button circles through other available time formats CNES julian day JD1950 fractional days with reference date January 1st
64. 1 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Rev 01 Date 06 03 2014 Date 14 11 2014 Reference VTS MU 69 Camera name Parameters unit objName Celestia full name of the target object e g Sol Earth CubeSat_ref CubeSat refObjectName Celestia full name of the reference frame to attach to e g Sol Earth CubeSat_ref CubeSat_Eme2000Axes Synchronous Sol Earth CubeSat ref CubeSat SunDir direction frame axis from which to point to the object X X Y Y Z Zor XYZ distanceFactor optional distance factor along the direction relative to the default distance Goto objName name of the target object e g Earth Center objName name of the target object e g CubeSat CameraOrbitSat objName name of the target object e g CubeSat sensorName Celestia full name of the target sensor e g Sol Earth CubeSat_ref CubeSat Sensor_sens_ref Sensor CameraSensorView _ halfAngleOnX and halfAngleOnY real number in radians aperture half angles of the target sensor up optional X or Y UP vector for the camera wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Description Generic camera attached to a reference frame pointing to the target object from the given frame axis This is the camera used by VTS for INI camera types Body Synchronous Body Inertial Satellite Inertial Satellite Sun Satellite
65. 15 9999998760581 The field of view of the camera can be entered in the FOV field in degrees Editor for file properties TM HKTMR 20120222 tm D users local Presto binaries PrestoDecom BDS ARGOSA tcl The file path either relative or absolute can be entered in the text field or selected through a file browser using the button 0 Editor for a time window It represents the time distribution before and after a dated event 134h 0 66h 2h total Durations are in hours Further documentation on the properties of standard client applications can be found in the Synchronization protocol for VTS clients chapter In particular the Messages received by Celestia and Messages received by 2DWin sections describe properties of the Celestia and 2DWin client applications wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 3 13 2 2 View properties editor toolbar The view properties editor offers buttons to propagate view properties between scenario states Upon selection of one or several properties in the tree hierarchy these buttons allow copying the selected properties for the same application in one or several other scenario states e The Propagate selection to all previous states button copies the selected view properties
66. 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 ratio The predefined time ratio sequence is 1x 2x 5x 10x 20x 50x 100x etc This is equivalent to pressing the corresponding button in the Broker s GUI This command has the following syntax CMD TIME IncreaseTimeRatio 7 3 3 3 1 4 DecreaseTimeRatio command The DecreaseTimeRatio command decreases the time ratio in the Broker It is the opposite of the IncreaseTimeRatio command This is equivalent to pressing the corresponding button in the Broker s GUI This command has the following syntax CMD TIME DecreaseTimeRatio 7 3 3 3 1 5 SetTimeRatio command The SetTimeRatio command sets a custom time ratio in the Broker It is redundant with the TimeRatio parameter of the TIME message but does not require a visualization date to be provided This command has the following syntax CMD TIME SetTimeRatio lt TimeRatio gt Parameter Required Description Format unit See also TimeRatio Yes Time ratio Real number For example the following commands set a visualization time ratio 10x slower than wall clock time CMD TIME SetTimeRatio 0 1 7 3 3 3 1 6 RevertTime command The RevertTime command reverses the time flow direction This is equivalent to pressing the corresponding button in the Broker s GUI This command has the following syntax CMD TIME RevertTime 7 3 3 3 2 CMD SERVICE messages 7 3 3 3 2 1 AUTOCLOSE command The AUTOCLOSE command ins
67. 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 If you want to focus on sensor swath accuracy increase the SensorGeometrySectionCount parameter and favor a short residual trace If you want to view long missions coverage lower the SensorGeometrySectionCount parameter with a long residual trace e Sensor swath resolution Change the interval in seconds between two instantaneous sensor aiming surfaces Use a small value for an agile satellite but affects the performance Use a high value for a long coverage mission with good performance The default setting creates a lot of overlapping traces BB 2 Celestia ejm w i CubeSat ERN T ll A matching value between sensor width and satellite speed gives a better appearance wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 7 PLUGIN DEVELOPMENT 7 1 CLIENT APPLICATIONS IN VTS The VTS toolkit is conceived to allow generic integration of new client applications Client applications must provide a number of interfaces to be able to successfully connect to the toolkit This chapter describes the architecture of the VTS toolkit and the interfaces to implement for new client applications T 1 1 General architecture A project consists in a
68. 3 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Attribute Description Format unit See also Altitude Target altitude Positive real number km Sample TargetAltitude tag lt TargetAltitude Altitude 1000 lt TargetEntity gt Target satellite of a station sensor The TargetEntity tag defines a satellite s altitude as the target of a ground station sensor Attribute Description Format unit See also Name Full name of the target satellite Character string Object paths in VTS Sample TargetEntity tag TargetEntity Name Sol Earth CubeSat Sensor Station sensor properties The Sensor tag defines the properties of a ground station sensor used for displaying the sensor s footprint projected on its central body in 2DWin Refer to the documentation of the lt Sensor gt generic tag in the lt Sensor gt Sensor section for further information 7 5 2 7 1 7 GroupPointsOflnterest Points of interest of a body The GroupPointsOflnterest tag contains the list of all points of interest on a central body This tag has no attributes Sample GroupPointsOflnterest tag GroupPointsOfInterest lt PointOfinterest gt Point of interest The PointOflnterest tag defines a point of interest POI of a central body Attribute Description Format unit See also Name POI name Character string Sample PointOfinterest tag PointOfInterest Name Landing site lt CoordinatesFile gt
69. 5 2 5 5 TimelineStream Stream display parameters in the timeline The TimelineStream tag defines a stream display parameters in the timeline Attribute Description Format unit See also Name Must be Stream lt i gt lt existing stream ID gt lt i gt Character string Pos Row position in the timeline Positive integer Size Row height in the timeline Pixels Sample TimelineStream tag wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 TimelineStream Name Stream amp lt i amp gt Pos amp lt i amp gt Pos 4 Size 23 gt Note the escaped character sequence represents an italic tag 7 5 2 6 ToBeUsedApps Client applications for the visualization The ToBeUsedApps tag lists all project client applications which are launched at the start of the visualization This tag has no attributes Refer to the VTS Broker and Client applications in VTS chapters for further information Sample ToBeUsedApps tag lt ToBeUsedApps gt 7 5 2 6 1 lt Application gt Project client application The Application tag defines a client application for the visualization Attribute Description Format unit See also Name Application name Character string Application launchers Id Unique application identifier Positive integer Application IDs in VTS The
70. 5248 Si ge social 48 843445 Zo 200007 DLA 43 561948 1 481500 CST Do AUIS 2525775470 CSG 3 15 1 3 Sample ROI file The following is a sample CIC CCSDS ROI file containing two polygons CIC_MPM_VERS 1 0 CREATION DATE 2014 04 23T15 25 04 268055 l ORIGINATOR VTS wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 META START USER DEFINED PROTOCOL NONE USER DEFINED CONTENT REGION OF INTEREST USER DEFINED SIZE 2 USER DEFINED TYPE REAL USER DEFINED UNIT deg META STOP 30 30 3 16 SCRIPTS AND MACROS IN VTS Scripts and macros in VTS are commands from the VTS synchronization protocol which are sent by the Broker to client applications during visualization Scripts are timestamped commands sent at predefined dates while macros are non timestamped commands sent in a batch upon macro execution When the visualization date reaches the timestamp of a script command the command is sent to all client applications specified in the recipient field of the script line Scripts are displayed in the project timeline Macros are listed in the Broker menu For more information on how to use scripts and macros in VTS refer to the Timeline section in the Scenario in VTS chapter and the Broker menu section in the Broker user manual c
71. 6 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 o Remove removes the selected component e ona Sensor item o Remove removes the selected sensor e onthe Applications item o Add Application adds a new client application to the project selected in the dropdown menu e onany client application item o Remove removes the selected client application The Del keyboard shortcut can be used to remove an item from the hierarchy if the selected item can be removed 6 1 3 7 Copy pasting entities The copy paste feature can be used to quickly create entities in the project hierarchy An entity can be copied through the clipboard either through the Ctrl C keyboard shortcut or through the Copy entry in the context menu Central bodies satellites components sensors ground stations points and regions of interest can be copied A previously copied entity can be pasted through the Ctrl V keyboard shortcut or through the Paste entry in the context menu once a compatible destination entity has been selected e g a satellite to paste a component a central body to paste a ground station etc If the selected entity is not a valid destination for the entity currently in the clipboard the paste operation will fail If the destination is the same entity as the one currently in the clipboard i e when hitting Ctrl C and Ctrl V in sequence a duplicate of the selected entity is created on the same level of the hierarchy Note that in order
72. 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 7 3 6 Messages received by 2DWin Apart from the common messages described above 2DWin handles the following commands corresponding to properties declared in its INI configuration file 7 3 6 1 CMD PROP commands Property name Parameters E iei Propagation Proporiy label format unit Description Default value mode See also Window ition and WindowGeometry i Posi nm Size 0 0 640 480 MANUAL Window geometry pixels x y width height Viewlnfos i i iti asd pu Mire A Default MANUAL View parameters internal format and zoom leve AllPoiVisible Boolean Display of all Mi Points of true MANUAL POIS and ROIs All POI visibility false or true Interest n AllRoiVisible Boolean Display of all M Regionsof rue MANUAL POS and ROIS All ROI visibility false or true Interest in VTS 2dWin user Number of manual section SensorGeometrySectionCount Positiveinteger points making 108 INITIAL Specific Sensor geometry section count number up the outline application polygon parameters in VTS 2dWin user manual section SensorCoverageSignificantThreshold Positive real Minimal linea Specific 1 ercentage o dues Sensor coverage significant threshold number ids Pu application parameters in VTS 2dWin user Minimal manual section Senso
73. AINT time behavior may provide a time ratio For REGULATING clients the actual time ratio is computed by the Broker 7 3 3 3 CMD messages Command messages allow some level of control over the visualization They are divided in several categories e CMD TIME commands alter the flow of time but do not modify the visualization date or time ratio refer to the T ME messages above for this e CMD SERVICE commands control various aspects of the visualization unrelated to time e CMD EVENT commands deal with CIC CCSDS mission event files for the visualization 7 3 3 3 1 CMD TIME messages 7 3 3 3 1 1 PAUSE command The PAUSE command stops the time flow in the Broker This is equivalent to pressing the Pause button in the Broker s GUI This command has the following syntax CMD TIME PAUSE When paused the Broker keeps sending TIME messages with the current visualization date even though it remains constant 7 3 3 3 1 2 PLAY command The PLAY command resumes the time flow in the Broker This is equivalent to pressing the Play button in the Broker s GUI This command has the following syntax CMD TIME PLAY 7 3 3 3 1 3 IncreaseTimeRatio command The IncreaseTimeRatio command increases the time ratio in the Broker The increase depends on the current time wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03
74. Applications tab allows managing currently connected client applications as well as starting new clients wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 l UTC 2010 03 21 00 00 20 b Project Applications La 2dWin 0 v Celestia 100 3 E 1 indude launcher start Z Cosmographia parameters iVTS test celx extrasdir D users jee vts Apps Celestia bin extras_100 Time type Constraint Address 127 0 0 1 8594 PrestoPlot 4 PrestoPlot 101 x External Applications zie Simulateur 1000 Time type Regulating Address 192 168 1 249 57025 Timeline View Properties 3D Cameras Applications Server Client applications 6 2 12 1 Managing client applications e To start a new instance of a client application double click its icon in the nstalled list or drag and drop it into the right area of the window Clients started this way are listed in the Dynamic Applications category e Clients not started by the Broker but connected to it are listed in the External Applications category e More details about a client can be displayed by clicking the arrow button next to each client o To s
75. Axis of rotation X 0 Y 1 Z 0 e Angle of rotation 30 The object s position vector is null and its center is located at the origin of its reference frame A single rotation has been applied The center of rotation is null The axis of rotation is O 1 0 i e the rotation is counterclockwise around the Y axis as if screwing in the direction of the axis The diagram shows that the Y axis is shared by the two objects while the X and Z axes have rotated 30 The direction of the rotation can also be observed clockwise when looking in the direction of the axis of rotation 3 6 4 4 Case 4 translation and rotation e Position X21 Y 0 Z 0 e Center of rotation X0 Y 0 Z0 e Axis of rotation X20 Y21 Z 0 e Angle of rotation 30 wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 This case combines both cases It illustrates the order in which the transformations are applied the object is first rotated then translated to its position 3 6 4 5 Case 5 offset rotation e Position X 0 Y 0 Z 0 e Center of rotation X 1 Y 0 Z 0 e Axis of rotation X 0 Y21 Z 0 e Angle of rotation 30 For a single rotation the origin of the reference frame is used as rotation center The rotation center can be modified so that the object is rotated around another poin
76. CMD PROP WindowGeometry 640 480 640 480 3 17 VTS BROKER The Broker is the core application during visualization of a VTS project It controls and synchronizes all client applications in time Client applications see the Broker as a socket server to which they connect and with which they communicate Each client has a dedicated communication channel with the Broker When an action or event within the Broker requires communication with its client applications the Broker decides whether to broadcast the corresponding message to all clients or only to specific ones Client Broker communications follow a protocol based on text socket described in more detail in the Synchronization protocol for VTS clients section Messages from the Broker to its clients concern e time synchronization e view controls e camera controls e events management e scripted commands e context saving e relayed messages from other clients Some messages expect reply messages from the clients Refer to the Synchronization protocol for VTS clients chapter for more information The Broker also has the responsibility of managing the life cycle of its clients either configured in the VTS project or started by user interaction spawning new clients relaying client log messages to the user displaying connection status about the clients informing the user of client terminations or crashes External clients not started by the Broker obviously fall outside of this
77. Clear all client application data caches action is available in the Configurator settings menu Each client application can provide a cleaner that removes all temporary files which could be let after many visualization runs The executable will be started with the clear option as other options could appear in the future e Example for Celestia cleaner under Windows launched by Apps Celestia bin cleanerCelestia bat clear e This cleaner removes all temporary folders containing 3D models and data files duplicated and generated for each run It removes all the extras temporary folders echo off for p in do rem Remove temporary folders if p clear for d a in dp0 extras_ do rd s q a rem Return success exit B 0 7 2 APPLICATION IDS IN VTS Application IDs in a VTS visualization uniquely identify any client application taking part in the visualization There are three classes of application IDs project IDs dynamic IDs and external IDs The distinction between the three is merely used to quickly determine the origin of an application and is not required to be strictly followed e Project IDs are attributed in sequence by the VTS configuration utility when adding a new client application to the project The ID is chosen as the first available i e not already attributed application ID starting from 1 e Dynamic IDs are attributed in sequence by the Broker when starting a new client app
78. DATA 20447 000174 pos 6538 3475061863419 2703 5361504162843 197 30707005759857 DATA 20447 000174 quat 0 22339793344197931 0 65359251975872334 0 53489502701655522 0 48661842497202529 DATA 20447 000174 angle 0 175 The sections below describe the parameters to a DATA message Note that previous versions of VTS required DATA messages to provide a protocol version number Since this version number is now specified in the INIT message they should no longer be provided with DATA messages In order to retain compatibility with previously written clients the Broker still handles a version number in DATA messages 7 3 7 2 1 Data value date The JD1950 date field provides the recording date of the data value In most cases this date is the same as the sending date of the message Due to the visualization date delay introduced by the Broker clients receive data messages slightly in advance This allows them to store the values and interpolate data for the current visualization date as opposed to extrapolation were no future data values available 7 3 7 2 2 Data identifier The lt data ID gt field provides the unique identifier of the data This ID is matched with the Stream ID set for streamed data in the VTS configuration utility Refer to the Data sources in VTS chapter for further information on streamed data configuration 7 3 7 2 3 Data value The lt data value gt field provides the value for the data at the given date
79. DEG AOS UON SU Viggo MSS ze WU u 56213 329000 NPL PHYSICAL AOS UO GAL Wer uw esa quw MEN 272 56213 s55 LOOO YAU LONOMOUSEMODEMECAR SURIE ND MAG Sh OS MEOR ZO SiO ee TET 56273 742000 KRN 0_DEG_LOS HS AL Wage sur wee SGEN RSI AN 56273 195000 SHADOW_PENOMBRA HS SSI US UNE LS ME a 56213 008000 PENOMBRA LIGHT N S OU WUD SS woe meu Mau ue 3 14 3 Event decorations Event decorations define the appearance of events in the project timeline and in compatible client applications Each event type may have its own custom decoration in order to be easily distinguishable from other event types Note that all events of a single event type have the same appearance Thanks to the hierarchy of event types event decorations are inherited all children type of an event type share the same decoration as their parent type This inheritance mechanism can be overridden by specifically customizing the decoration of an event type For more information on the specifics of event decoration configuration refer to the Configuring event types section wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 of the VTS configuration utility user manual chapter 3 15 POIS AND ROIS IN VTS POIs and ROls in VTS are files defining Points and Re
80. Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 e The Auto compute option enables automatic computation of the project s date range when the user starts the visualization This option is not saved in the project XML and can be changed manually after loading the project if needed By default this option is unchecked but this can be modified in the Options Settings dialog e The Change date button located besides the project start and end dates allows manually editing the dates in CNES julian day format JD1950 modified julian day format MJD and calendar format ISO The Synchronize with system time option allows synchronizing the visualization time with the computer s system clock In this mode time controls are disabled during visualization Data files must provide data for the visualization time range Refer to the Date formats in VTS for further information on dates 6 1 4 1 2 Configuring initial properties of the visualization e The Initial time ratio setting allows specifying the initial visualization time ratio e The Pause visualization option allows starting the visualization paused unpaused e The Loop visualization option allows the visualization to start over once it reaches the end of the time range e The Minimize broker option allows the Broker
81. E E EEEE ste Feed EE E tenter AERE RE E ten ce Ee a aX Rt ERA VR ATE aad 23 3 4 2 Position of satellite components uii re rita teh o her Ee Ey Y A ERU EFE TERREA E KR V ENT ERE CERTE ERE ARRA VY S teste aa 23 3 4 3 SOC ISO C L HO 3 5 ORIENTATION OF OBJECTS IN VTS 3 5 1 Reference frames 3 5 2 Rotation center 3 5 3 Orientation types 3 5 3 1 Quaternion 3 5 3 3 Euler ahgles non ete e ber totes actes task E AE aE AA ee Etre dudes uit ab ie iod wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 14 11 2014 Reference VTS MU 69 3 5 3 3 Axis and angle 3 5 3 4 Direction 3 5 3 5L Azitmuthvand elevation credit ee rere etie es erai dod ccnicagesdvadssssasasecewiceedeaas sneplu a na Er ceded cute n REN PO eles 25 3 5 4 VGHIGiEY COMGINS m 26 3 5 5 see e 26 3 6 EXAMPLES FOR POSITION AND ORIENTATION OF OBJECTS IN VTS eines 26 3 6 1 Methodology iocis eie rosa venter ta Yu Yee ERE ERI YER ETT NER RATS cided FERAE ETE CY V Ea VE Ea ERE MEHR SERE AR ERREUR e V TV YR AREE 3 6 2 List of tests 3 6 3 Illustration of the result 3 6 4 Description Of the res
82. EnaA E Ea ei EE aae E Eea aaia ARE SOEREN 98 615 1 Loading eventfiles oen ete pee tardes tan bte slot ae OEE TESEN EEEE c tee Lc EET e rag e Ei 99 6 1 5 2 Configuring default event type decorations siennes 99 OEC MEME EIE DC E 99 D1 52 2 To L ET ER PS 100 6 1 5 3 Configuring satellite specific event type decorations ses 100 6 1 6 Settings GIGI OG EE 100 GG Ts ProJectoptioris a etc AA ee 2e cau pesce eere mis tels Fes eus ede ursa galee ce ce cl lay saeeyteceaveveh cous Eea E EEEE veges 101 wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 14 11 2014 Reference VTS MU 69 6 1 6 1 1 Use auto compute dates by default 6 1 6 2 Broker Options sess a 6 16 2 1 Allow multiple instances aan coi ke t Sue cdases sbedeascevsoedgvedetdcevvecstedsasteasevdersncselanazes 6 10 22 Stream buffer length eee eo eise e p EO ded TEE e Ee ERE Ree Bees eae demie ees 6 1 6 2 3 Log message max length sise Las EEUU I 6 1 6 3 1 Auto load file size linait iecit te tene eene t e ta ua ua Peer e dendi ai adeta edad dx ena euo et neu aont 6 6 3 2 A to load item count limit ceret rte ree et nente E XE tte EXER E Een Ee E aR E Ee Eee cre ENSS EEGA Launcher el
83. File field defines the 3ds mesh file to use for the component It must be point to an AutoDesk 3DS Max file If the selected file is not located in a sub folder of the project folder a dialog will offer to copy it inside the project folder e The Light sensitive option enables or disables shading of the 3D mesh Objects such as satellite bodies or solar arrays usually should be shaded while abstract objects such as frame axes or vectors should not Unshaded objects are only lighted in a diffuse manner and do not show specular reflections from light sources such as the Sun e The Use 3ds coordinates option allows using the intrinsic coordinates of the 3ds mesh file If the 3ds mesh file originates from a known CAD source it is advised to leave the option enabled and to set the Approximate size field accordingly to define a bounding sphere for the 3D mesh If the 3ds mesh file originates from an unknown source it is advised to disable the option and to set the Approximate size field to the desired size for the 3D mesh The Unit drop down list defines the unit to use when reading coordinates in the 3ds mesh file e The Center of gravity for a satellite or Rotation center for a subpart field defines the XYZ coordinates of this point in the current item s local frame in meters Note Modifying the center of gravity of a satellite has no effect on the origin of the satellite s frame The satellite s local frame can only be altered by directly modif
84. MU 69 From revision Toolkit version Revision tag From r3244 onwards 2 4 2 5 project From r1991 to r3243 2 0 2 1 2 1 1 2 2 2 3 project From r1697 to r1990 1 3 1 project From r1554 to r 696 1 3 0 project From r1246 to r1553 1 2 3 project From r1050 to r1245 1 2 1 general From r1000 to r1049 1 1 general Before r1000 NA NA 3 7 2 Upgrading VTS When a new version of VTS is available and if VTS can reach the http msweb cst cnes fr 9350 animgraph vts updater news htm webpage i e on the internal network at CNES a popup message is displayed to indicate the availability of a new VTS version This message only appears when using the VTS configuration utility 3 8 OBJECT PATHS IN VTS The various objects displayed by VTS can all be addressed according to a naming scheme For practical reasons this naming scheme is directly derived from the one used by Celestia 3 8 1 Definitions The table below lists all the definitions used to identify objects in VTS Identifier Description Examples Earth name Name of the object GS Sol Earth fullName Full identifier of object Sol Earth CubeSat GS Sol parentPath Identifier of the object s parent Sol Earth CubeSat Name of the object s reference in Earth celestiaRefNam Celestia GS ref Sol celestiaParentFullName Path to the object s parent in Celestia Sol Earth CubeSat ref CubeSat Sete eee puras Full path to the object s reference in Sol Earth
85. NEENA 51 3 13 2 2 View properties editor toolDat e tie eret etre DAEAR a EE teres aet ae ER c AEE ANAR 54 3 14 MISSION Raus SR E t 54 3 14 1 iaa M 54 3 14 2 CIC CCSDS event N S oi river rec or PER Ee dre avse nc entend de ir arvo REOS eT ed old 54 3 14 3 Event decorations inse eer ER SR Eee ee RIEN Re ee REA eoe ee eh A reden otvacavedeetusongeadssebecevent esses 55 3 15 POIS AND ROISIN VIS ME 56 3 15 1 1 CIC CCSDS POI and ROI file fForMat ccccccssccssscessccssecessecssecessccsseecsecessecsseecstecscaecessecsassessecsuacensseseceaesesecsarseteessaeeessees 56 3 15 1 2 Sample POI file 3 15 1 3 Sample ROI file 3 16 SCRIPTS AND MACROS IN VTS 3 16 1 CIC CCSDS script and macro file format iii 57 3 16 2 Command recipient specification iii 57 3 16 3 COMIMONG Bolo 014212 CORPER ETT TED OT CELO OL LOL LL DITS QUU deud eneagsetsase sbousdsediea dane 58 3 16 4 Sample script file sisti isset Dae bere aret E Pu a E MR eaa TRRRE eR FR Veg Po sa aee eV ra roe bes Eye apes A eR Fre Feu o nb ias 58 3 16 5 Sample macro flle vereinen e E FRE Te RUE E ERR EUREN EAR E dance TR ERA UE ERE V RR TER leds een ATI een s ess ei ERE LFU Pe REM RIA ses 59 3 17 VTS BROKER siidi EE 59 A FILES USED BY VU e E E E E E E E 61 431 DATA DESCRIPTION FORMIS PROJECTS eert
86. NISSION 35 555 seas eae a eere e x pits pate nene aS Eur aan dna e a VER AREE ace tene es sets ARV ancy dae da gae aaa AGE raya Pan e nanas neue 18 2 3 2 Supported operating systems aei roit iaee e ER EVE MERE r a EE ERE RR YEA MEER KE REA AERE ERR ER AERE ERE Fea e OPER PER ra Y Ro dE 18 244 HARDWARE REQUIREMENTS FOR IS is cete sete eet ea couvies ccedebsseawedaiveceevcavovsnatsie re eatwadesvesevcaavasenestecavessevia Sevcesuensdnateeaccs 19 2 4 1 Recommended system requirements inserer 19 2 4 2 Minimal system requirements nibilo etas ees eon osa oo bee oed Y eoa eo aee k E LPS RR Tea RAE Pe RIA RR RAP o ERE Fea En ue deo ce sans 19 2 4 3 VICE OS ere pro Mo gd ERTEILEN PL TL DOTT 20 icis ideo ls dw 21 3 1 CONVENTIONS IN V TS eni oe etr teeth t ed ete etd cit rase tn MERE cde do 3 1 1 Frames 3 1 2 Quaternions 3 2 DATE FORMATS IN VTS 3 2 1 Formats LOT MERE PR RE E A ETTE AE 3 2 2 Entering a Gatesin aa ee e aea a M EMEN e esIUIE 21 3 32 DATA SOURCESIN VS d sir rei Ie ere P e HER URGE ei Eaa iaa EQ WD tre aiaa GA EG Hm es Uude REACER 22 3 3 1 Fix d data CT O1 LL RE eenaa EE EE E EAE E EREE a a aE 22 3 3 2 FH data SOURCE 2 202 see ti nee EA te A A EA EEA 22 3 3 3 xsicoluoloiteito oT 22 3 4 POSITIONOFOBIECTSIN Ba cE tte 23 3 4 1 Reference frames ierit eere TEE e aen R
87. NUA EME2000 inertial frame axes false or true inertial reference frame FrameAxesVisible Boolean Display of the local body fles MANUAL Body frame axes false or true frame PlanetographicGridVisible Boolean Display of the planetographic CAC Planetographic grid false or true grid wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB Issue 05 Date 06 03 2014 14 11 2014 VTS Rev 01 Date Reference VTS MU 69 Property name i perty Parameters Description Default Propagation See also Property label format unit value mode TerminatorVisible Boolean ani Display of the day night false MANUAL Terminator false or true terminator 7 3 5 2 2 Satellite and subpart properties Property name Parameters format unit Description Default value Propagation mode See also Property label Visible Boolean ou Visibility of the object true MANUAL Component visibility false or true 7 3 5 2 3 Satellite properties Property name i Parameters format unit Description ps ult i e See also Property label value mode SatelliteScale Scale Positive real number en actor far tne whole 1 MANUAL factors in Satellite scale satellite VTS OrbitVisible Boolean Display of the satellite s orbit MANUAL Orbit path false or true path Two Positive real numbers OrbitWindow Duration of the satellite s orbit Duration before event
88. Name Data ROSETTA OEM POSITION TXT wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 7 5 3 8 lt ColorFile gt CIC CCSDS color file The ColorFile tag defines a CIC CCSDS color file which describes the evolution of a color with time Attribute Description Format unit See also Name Name of the color file Character string The file path must be relative to the project folder Sample ColorFile tag ColorFile Name Data CUBESAT MODE TXT wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 8 ABOUT 8 1 PROGRAMMING LANGUAGES IN VTS Due to the nature of VTS which deals with synchronization of client applications from various origins several programming languages are used throughout the VTS toolkit The following table lists these languages Language Usage in the VTS toolkit TR e Main language of VTS Used for GUls of the Broker the VTS configuration utility and 2DWin e C is also the main language of the Celestia client application C e CIC CCSDS file I O library e PrestoPlot client application Tcl Tk e VTS cross platform toolkit la
89. Recording movies section below for more information e Add application Start a new dynamic client application refer to the Applications tab section below for more information e Run macro Run a CIC CCSDS macro file refer to the Scripts and macros in VTS chapter for more information o Choose macro Browse for a CIC CCSDS macro file to run o Project macros Run a CIC CCSDS macro file found in the Macros subfolder of the project folder o VTS macros Run a CIC CCSDS macro found in the Apps Broker macros subfolder of the VTS installation folder e Quit Close the visualization 6 2 5 Display modes The Broker can either display itself in compact or full mode In compact mode only time control buttons are displayed and the Broker is pinned in the foreground always on top of other windows In full mode the tabbed interface is displayed allowing access to the scenario timeline all client commands and information on the state of the visualization By default at the start of a visualization the Broker is in compact mode The Unfold arrow button allows switching to full mode Broker VTS om Tues ze 21 03 2010 22 03 2010 2010 03 21 issu gay jJ Compact display mode wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69
90. RegionOflnterest tag defines a region of interest ROI of a central body Attribute Description Format unit See also Name ROI name Character string Sample RegionOflnterest tag RegionOfInterest Name Target gt lt CoordinatesFile gt coordinates file of a ROI The CoordinatesFile tag contains the coordinates file name of a ROI Attribute Description Format unit See also Name Name of the CIC CCSDS file Character string Graphics graphics properties of a ROI The Graphics tag contains the graphics properties of a ROI Attribute Description Format unit See also Color Color of the ROI Three real numbers for red green blue in the 0 1 range no unit FillOpacity Opacity of the ROI surface Integer in the 0 100 range percentage Sample RegionOflnterest tag RegionOfInterest Name Corsica gt CoordinatesFile Name Corsica txt gt Graphics Color 0 363836 0 1 FillOpacity 40 RegionOfInterest 7 5 2 7 2 lt Satellite gt Satellite The Satellite tag defines a satellite for the visualization wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Attribute Description Format unit See also Name Name of the satellite Character string Structure of satellites in VTS ParentPath Full path to the s
91. SOR START 3 SUN IN SENSOR START 3 Satellite CubeSat 1 Event OEF SUN IN SENSOR START 3 74 93 7292 53 85 SUN IN SENSOR START 3 8 272 Simultaneous events for two separate satellites 6 3 5 Technical notes 6 3 5 1 Rotation model 2DWin uses the VTS ephemeris catalog to display an accurate positioning and Sun terminator see the Central bodies in VTS section for more information about ephemeris origin For custom positioning or unsupported bodies suitable ephemerides files will need to be provided to override the catalog ones Refer to the Position and orientation of a body section of the VTS configuration utility user manual chapter for more information 6 3 5 2 Central body texture The current architecture of the 2DWin application enforces a few constraints e The built in texture for Earth is embedded in 2DWin It is based on the Blue Marble photos from NASA image link documentation link using the equidistant cylindrical plate carr e projection e For other solar system bodies or celestial bodies available in Celestia the built in texture will be taken from Celestia e For bodies not available in Celestia a black texture will appear in built in mode A custom texture should then be defined Refer to the Texture of a body section of the VTS configuration utility user manual chapter for more information 6 4 CELESTIA USER MANUAL The main 3D client application in VTS is Celestia Celestia is o
92. TS amp Q Ki di 9 100x faster 2 0 0 14 18 00 04 11 14 20 00 l UTC 2014 11 04 18 22 05 Target 2 Celestia 0 Celestia zi 67C G 4 Rosetta Inertial cameras 4 Sun synchronous cameras n View from Sun View toward Sun Satellite frame cameras QSW frame cameras TNW frame cameras Miscellaneous cameras 4 philae E MEEEESEE F E EEEE F Inertial cameras Sun synchronous cameras a Timeline View Properties 3D Cameras Applications Server Camera controls 6 2 11 1 Central bodies Central bodies such as Earth are top level entities of the visualized project All central bodies defined in the project appear in the hierarchy Available actions are e Fixed in Body frame The camera is positioned in the body s local frame pointed at the body e inertial The camera is positioned in an inertial frame attached to the body pointed at the body e Goto The camera is pointed at the body travelled so that it occupies as much space as possible in the 3D window and attached to the body s local frame The UP vector of the camera is undefined e Center The camera is simply pointed at the body Its reference frame is unchanged The UP vector of the camera is undefined e North pole The camera is positioned above the North pole of the body pointed towards it and attached to the body s local frame The UP vector of th
93. TS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 INTERNAL DISTRIBUTION Name Entity Internal Observations Postal Box EXTERNAL DISTRIBUTION Name Entity Observations wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 CHANGES Issue Rev Date Reference Author s Reasons for evolution 05 01 14 11 2014 VTS MU 69 Equipe VTS SPACEBEL SAS Release of VTS 2 6 Rosetta 05 00 06 03 2014 VTS MU 69 Equipe VTS SPACEBEL SAS Release of VTS 2 5 English translation 04 04 03 12 2013 VTS MU 69 Equipe VTS SPACEBEL SAS Livraison VTS 2 4 Fauch es senseurs Ev nements Bugs fixes et fonctionnalit s mineures 04 03 03 07 2013 VTS MU 69 Equipe VTS SPACEBEL SAS Livraison VTS 2 3 Ergonomie de VTS Lancement dynamique des applications Liste des param tres des applications Bugs fixes et fonctionnalit s mineures 04 02 19 02 2013 VTS MU 69 Equipe VTS SPACEBEL SAS Livraison VTS 2 2 Textures dynamiques Bugs fixes et fonctionnalit s mineures 04 01 13 09 2012 VTS MU 69 Equipe VTS SPACEBEL SAS Ajout de l enregistrement des films 04 00 24 07 2012 VTS MU 69 Equipe VTS SPACEBEL SAS Livraison VTS 2 0
94. TS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 e ifa line of the MEM file contains the string DEFAULT the built in texture of the body is used for this date Beware using a timed texture can make the visualization jerky especially when using Celestia The following circumstances may cause performance issues e timed texture with frequent texture changes every few seconds of wall clock time e timed texture with textures of significant sizes e timed texture visualized at high time ratio causing texture changes every few seconds of wall clock time Acyclic timed texture For an acyclic texture dates in the MEM file are the dates at which the texture changes occur For example the following line 56018 0 Textures Chl a april 2012 png specifies that image file Textures Chl a april 2012 png is to be used as texture for the central body at MJD date 56018 0 Cyclic timed texture For a cyclic texture dates in the MEM file describe the instants of the cycle at which texture changes occur Two additional parameters are required e The epoch of the cycle e The period of the cycle in fractional days The epoch of the cycle must be prior to the start date of the project Periods of an variable number of days such as a month or a year may not be specified The best solution in this case i
95. The value must be quoted no matter its dimension scalar value vector etc The unit for the value depends on the data type e g e Position of a satellite kilometers e Position of a satellite subpart meters e Quaternion no unit e Angle degrees 7 3 8 Sample session This example shows the messages sent by a regulating client defining a square equatorial orbit don t try this at home at 100x wall clock time wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Sending date Message TO INIT example REGULATING TO TIME 23000 000000 TO DATA 23000 000000 pos 10000 0 0 T0 1s TIME 23000 001157 TO 1s DATA 23000 001157 pos 0 10000 0 T0 2s TIME 23000 002315 T0 2s DATA 23000 002315 pos 10000 0 0 T0 3s TIME 23000 003472 T0 3s DATA 23000 003472 pos 0 10000 0 T0 4s TIME 23000 004630 T0 4s DATA 23000 004630 pos 10000 0 0 T0 5s TIME 23000 005787 T0 5s DATA 23000 005787 pos 0 10000 0 T0 6s Etc 7 4 DESCRIPTION OF APPLICATION PROPERTIES The VTS toolkit relies on a command mechanism to control client applications from the Broker in a centralized way This mechanism is used to send view properties commands upon activation of a new scenario state Client applications may describe view properties which will be displayed in the view p
96. Translation and rotation X 1 Y 0 Z 0 X 0 Y 0 Z 0 X 0 Y 1 Z 0 30 5 Offset rotation X 0 Y 0 Z 0 X 1 Y 0 Z 0 X 0 Y 1 Z 0 30 6 Translation and offset rotation X 1 Y 0 Z 0 X 1 Y 0 Z 0 X 0 Y 1 Z 0 30 3 6 3 Illustration of the result att Arte Baron ure Examples of various positions and orientations wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 3 6 4 Description of the result 3 6 4 1 Case 1 no modification e Position X20 Y 0 Z 0 e Center of rotation X0 Y 0 Z 0 e Axis of rotation X20 Y21 Z 0 e Angle of rotation 0 The position and the angle of rotation are null In this case the object is at the same position and is aligned with its reference frame It should be noted that since the angle of rotation is null the axis and center of rotation have no influence 3 6 4 2 Case 2 single translation e Position X 1 Y 0 Z 0 e Center of rotation X 0 Y 0 Z 0 e Axis of rotation X 0 Y21 Z 0 e Angle of rotation 0 In this case the position of the object has been modified Its value defines a position 1 meter forward along the X axis The object is now centered at the end of the X axis of the reference frame 3 6 4 3 Case 3 single rotation e Position X 0 Y 0 Z 0 e Center of rotation X 0 Y 0 Z 0 e
97. U G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 e The ground stations attached to the body Refer to the Configuring a ground station section in the VTS configuration utility user manual chapter for more information e The Regions Of Interest attached to the body Refer to the Configuring a Region Of Interest section in the VTS configuration utility user manual chapter for more information e The mission events attached to all satellites of the body Mission events appear at the date of their occurrence on the ground track of the satellite they are attached to Refer to the Events attached to a satellite section in the VTS configuration utility user manual chapter for more information 6 3 4 Interacting with the application 6 3 4 1 Context menu The context menu accessible by right clicking anywhere in the application window offers the entries e The Zoom Fit entry adjusts the zoom level so that the whole planisphere fits in the window e The Zoom In and Zoom Out entries respectively zoom in an out on the planisphere This can also be achieved using the mouse wheel The zoom is then centered on the current mouse position in the window e The Toggle Satellite Visibility entry shows hides all satellite icons e The Toggle Ground Station Visibility entry shows hides all ground station icons e The Clear All Sensor Swath entry clears the sensor swath overlay if enabled in the project
98. VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 The properties of a new state are copied from the previous state at the date of the new state Right clicking a scenario state displays a context menu with the following actions e The Go to state entry sets the visualization date to the date of the selected state Broker only e The Disable state Enable state entry disables enables the selected state Broker only e The Delete state entry removes the selected state Right clicking on the initial state of the scenario displays a specific context menu e The Go to state entry sets the visualization date to the date of the selected state Broker only e The Create state entry creates a new scenario state at the start of the scenario 3 13 1 3 Mission events Mission events attached to project entities are displayed in the first lines of the timeline Each entity has its own line of events Refer to the Mission events in VTS chapter for more information on events 3 13 1 3 1 Graphical representation of events The header of each line shows the name of the entity for the events on the line Each event is represented by its decoration configured in the event types editor Refer to the Configuring event types section of the VTS configuration utility user manual chapter for more information Each line can be resized by resizing its header
99. VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 BODY Structural properties for central bodies COMPONENT Structural properties for satellite components These will be available for the root component of a satellite and for all of its subparts SATELLITE Structural properties for satellites SENSOR Structural properties for satellite sensors CAMERAS Compatible cameras for the application ROI and POI Properties for regions and points of interest 7 4 3 Property declaration Each property must be declared with the following required fields Below name Name of the property This name must be unique within the current INI section It will be used as command name in the VTS synchronization protocol type Property data type This may be a basic type a Qt type or a VTS type See below for further details defaultValue Default value for the property propagation Propagation mode for the property See below for further details label Label of the property displayed in the view properties editor is an example of an application properties file INIT XML 1 nam 1 typ 1 def 1 pro 1 lab SPEC Win 1 nam 1 typ 1 def 1L ose 1 lab size SATE ENS 1 nam 1 typ 1 def IAL File e XMLFile e DataFile_t aultValue Data ft xml pagation INITIAL el Transfer Function File 1 TRECI dowGeometry e WindowGeometry
100. VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 General properties Satellite Name CubeSat Central Body Sol Earth M Orbit Path Default path color MEN General properties of a satellite 6 1 4 4 1 1 Name and central body of a satellite The name of the satellite will be the satellite s unique identifier during visualization used to identify the satellite in view properties and messages between the Broker and client applications The central body of the satellite defines the reference frame for the satellite in which the satellite s position is expressed 6 1 4 4 1 2 Orbit path of a satellite The orbit path of a satellite is displayed in the 2D and 3D views It has the following property e The Path color field defines the display color of the orbit path This color is used unless a color file is specified along with the sampled position of the satellite Refer to the Position from a file section for further information Note the displayed length of the satellite s orbit path is now configured in the project scenario 6 1 4 4 2 Events attached to a satellite Mission events can be attached to the satellite to be displayed in the project timeline and in compatible client applications These events are provided in CIC CCSDS files in MEM format e The Add button allows selecting an additional CIC CCSDS event file e The Create button allows creating an
101. Y apertures circular sensors There is currently no limit to the effective range of a sensor 3 11 2 Visualization of a sensor 3 11 2 1 Satellite sensor In the 2D view a satellite sensor is represented by the intersection of its volume with its target central body wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Elliptical sensor in 2DWin Kour ou Rectangular sensor in 2DWin In the 3D view a satellite sensor is represented by its aim volume In order not to overload the visualization a maximum range is defined for the sensor in the VTS configuration utility Beyond this range the sensor s volume will not be displayed As a rule of thumb the maximum sensor range should be taken equal to the maximum distance between the satellite and the center of the central body Beware that a too short range could result in an erroneous computation of the sensor volume s intersection with the sensor target wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Fichier Navigation Temps Rendu Vue Signets Aide Distan 376 F on 1 0000 m Phaseanale 1 Ellipti
102. a previously copied item onto the selected tree item e onthe Project item o View XML opens the project file in the text editor associated with the vts file extension o Open project location opens a file browser in the project folder e onthe Celestial Bodies item o Add Body adds a new body to the list of central bodies e ona Body item o Remove removes the selected body e ona Ground stations item o Add GroundStation adds a new ground station to the current body e ona Ground station item o Remove removes the selected ground station e ona Points Of Interest item o Add Point Of Interest adds a new set of points of interest to the current body e onaPOlitem o Remove removes the selected set of points of interest e ona Regions Of Interest item o Add Region Of Interest adds a new region of interest to the current body e onaROlitem o Remove removes the selected region of interest e on the Satellites item o Add Satellite adds a new satellite to the list of satellites e ona Satellite item o Add SubPart adds a new component to the selected satellite o Add Sensor adds a new sensor to the selected satellite o Remove removes the selected satellite e onaSubPart item o Add SubPart adds a new sub component to the selected component o Add Sensor adds a new sensor to the selected component wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 0
103. al VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Page 51 property editors associated with the various property types type Editor for a boolean property e g equatorial grid visibility in Celestia Clicking the checkbox toggles the property Editor for an integer or real number property The integer or real value can be entered manually or increased decreased using the buttons Editor for a string property e g selected object in Celestia Sol Earth CubeSat_ref CubeSat Ss lc The string must be entered manually Editor for a string list property e g visible event types in 2dWin Character 313 1 2897 0 8981 0 1452 The string list must be entered manually Syntax rules of the VTS synchronization protocol apply except the newline rule Refer to the Message syntax section of the Synchronization protocol for VTS clients chapter for a list of these rules Editor for a scale factor property e g satellite scale factor in Celestia 2 1023932919783 des 338822 80893105 The scale factor value can be adjusted by dragging the slider left or right or entered manually or reset using the buttons Editor for a range property e g ambient light level in Celestia The range value can be set by moving the slider or entered manually or reset using the button Editor for a r
104. all client applications The active state is saved others are not e The Save window positions for whole scenario button updates all scenario states with the window position of all client applications All scenario states are saved 3 13 2 View properties editor The view properties editor allows editing the view properties of client applications attached to each scenario state wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 slam 9 aa 2103 1000 00 21 03 10 06 00 ISO 2010 03 03 42 06uTc Label Application Property name Value 0 2dWin 4 Application parameters Window geometry 640 0 640x480 1 Celestia Equatorial grid 7 true Camera parameters Double click to view l 2 PrestoPlot Selected object Sol Earth CubeSat_ref CubeSat 7 Satellite labels 4 true Solar system scale x1 Window menu false Window text false Ambient Light 30 4 Objects parameters 4 Earth Body scale 4 EME2000 inertial frame axes raise Body frame axes false Planetographic grid F false Terminator E false 4 CubeSat W GG uu i e iii Timeline View Properties Events 3D Cameras Applications Server View properties editor in the Broker 3 13 2 1 Scenario sta
105. ally starts to play with time ratio 1 once initialization is finished unless specified otherwise in the VTS project 6 2 3 End of a visualization The visualization can be stopped directly by clicking the top right cross button to close the Broker It also stops once all client applications have been closed by the user or if the VTS configuration utility is closed if the visualization was started from there 6 2 4 Broker menu The Broker menu can be reached through the gears icon in the top left corner of the Broker Broker VTS CubeSat vts 21 03 2010 22 03 2010 9 J M Dock on top of screen Dock on bottom of screen QE BI Disable always on top L amp Save Broker position Record movie M Add application r Run macro gt Quit Broker menu It offers the following options e Dock on top of screen Dock on bottom of screen Enable always on top Control special Broker display modes refer to the Display modes section below for more information wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 e Save Broker position Save the Broker window state and position so that it can be restored at the next startup of project visualization e Record movie Record a movie refer to the
106. ame Name of a satellite Character string Object paths in VTS FullParentPath Full path to the satellite s parent should be a central body Character string Object paths in VTS 7 3 4 2 2 2 Requests Requests are special commands for which the Broker expects replies from client applications within a defined time frame Refer to the Request replies paragraph above for more information on request replies SaveState request The SaveState request informs client applications that a scenario state context save is ongoing and instructs them to send commands for the view properties declared in their INI files back to the Broker This request has the following syntax CMD SERVICE SaveState Client applications should reply using StoreCommand commands described above Once all properties have been sent back a SaveStateFinished command should be issued to inform the Broker that the context save is complete Note Once the SaveState request has been issued by the Broker client applications are expected to send all StoreCommand commands and the SaveStateFinished command within 3 seconds Beyond this time frame the context save will time out for clients which have not responded Refer to the Timeline toolbar section of the Scenario in VTS chapter for more information on scenario state context save actions Note that this request does not concern the special WindowGeometry property This property should only be sent in reply to a SaveWindow
107. and orientation of a sub component are defined as described in the Position and orientation of an entity section The transformations are expressed in the parent component s frame For example for a solar array split in several levels of components the coordinates of the first component are expressed in the satellite s frame those of the second component are expressed in the first component s frame etc The unit for position values is the meter wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 6 1 4 6 Configuring a satellite sensor Satellite sensors can be attached to the main component of a satellite 6 1 4 6 1 General properties of a satellite sensor The general properties of a satellite sensor define the name of the sensor in the project hierarchy This name will be used as a unique identifier during visualization by commands interacting with entities 6 1 4 6 2 Properties of a satellite sensor By convention in its canonical position a satellite sensor frame is aligned with the satellite s frame and the sensor points along the Z axis Physical properties Type Rectangular z Half angle on X 50 deg Half angle on Y 20 deg Graphic properties Range 10000 Km Sensor volume Color MM Opacity 60 Sensor contou
108. angle Direction 9 Azimut and elevation Azimuth Altitude Constant e File _e Stream Alt deg 0 Az deg 9 Orientation by azimuth and elevation e Anorientation by azimuth and elevation is defined by two angles for the azimuth and elevation both in degrees This orientation mode does not strictly define an orientation there remains a degree of freedom around the direction of aim 6 1 4 3 Configuring a central body Missions visualized in VTS are defined around central bodies A spacecraft is attached to a central body and a central body is attached to the Sun At least one central body must be defined for the VTS project to be valid New projects use the Earth as default central body 6 1 4 3 1 General properties of a body The general properties of a body are its name and texture wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 6 1 4 3 1 1 Name of a body General properties Body name Earth v The body name must exist in Celestia or the 3D Properties and Position Orientation must be fully defined General properties of a body e fthe central body has a valid Celestia body name its default ephemerides can be used or overridden refer to the Position and orientation of a body section below A drop down list allows cho
109. application ID for the current visualization If the ID is not registered in the Broker the command is bufferised and will be send when an application connect with this exact ID Client application IDs are displayed in the Applications tab of the Broker The ALL character string may be used instead of a numerical ID to broadcast the message to all clients except the sender wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 The transferred message may contain spaces It will be transferred as is to the recipient s Below are a few sample forward messages e Hide solar arrays in all 3D clients displaying them the clients must implement the Visible structural property for the command to have any effect FWD ALL CMD STRUCT Visible Sol Earth CubeSat GS true e Reset view position and zoom level in client ID O for this command to have any effect client ID 0 must be a 2DWin client application FWD 0 CMD PROP ViewInfos Default 7 3 3 5 DATA messages DATA messages are described in the Real time VTS section below They provide data for streamed values 7 3 4 Common messages received by client applications Some messages received by clients from the Broker are common across all client applications This section describes those messages Applicatio
110. arent Character string Object paths in VTS Central bodies are VTS entities around which visualized satellites orbit When using standard VTS client applications such as Celestia or 2dWin a central body must reference a known object from VTS s default list or provide the data required for its display position and orientation Refer to the Central bodies in VTS chapter for more information on central bodies Sample Body tag Body Name Earth ParentPath Sol 7 5 2 7 1 1 Texture Body texture The Texture tag contains the tags defining the texture of a central body This tag has no attributes Sample Texture tag Texture This tag is empty if the central body uses its built in texture For further information on texture types refer to the Texture of a body section of the VTS configuration utility user manual chapter lt TextureFixedFile gt Fixed body texture file The TextureFixedFile tag defines the fixed texture file for a central body Attribute Description Format unit See also Name Fixed texture file name Character string Texture of a body in the VTS configuration utility user manual Sample TextureFixedFile tag TextureFixedFile Name Textures earth AE8 png The file name must point to an image file and its path must be relative to the project folder TextureTimedFile Timed body texture file The TextureTimedFile tag defines the timed texture file for a central body Attribute Descri
111. arent object e Orientation with the following parameters o Center of rotation o Axis of rotation o Angle of rotation The position and orientation be it quaternion Euler angles axis and angle etc of an object can be defined in the Position orientation dialog of the object For components the center of rotation can be defined in the 3D Properties dialog Refer to the VTS configuration utility user manual for more details The 3D object used for this demonstration is the 3 axes trihedral usually used in VTS to materialize reference frames The X Y and Z axes are respectively colored in red green and blue This object represents here the satellite or any parent object The length of each axis is one meter Then the same model is used scaled down and wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 tarnished to represent the object positioned by the transformations described below Z Materialization of the axes of the reference frame 3 6 2 List of tests Number Designation Position Center of rotation Axis of rotation Angle of rotation 1 No modification X 0 Y 0 Z 0 X 0 Y 0 Z 0 X 0 Y 1 Z 0 0 2 Single translation X 1 Y 0 Z 0 X 0 Y 0 Z 0 X 0 Y 1 Z 0 0 3 Single rotation X 0 Y 0 Z 0 X 0 Y 0 Z 0 X 0 Y 1 Z 0 30 4
112. as the center of the 3ds file object s bounding box These options can be selected in the VTS configuration utility independently for each 3D object The Use 3ds coordinates setting must be checked to enable use of the 3D file s origin unchecked to use the geometric center of the object as origin Refer to the VTS configuration utility user manual chapter for more information It must be well understood that these options make it easier to define satellites composed of multiple components When all 3D files for a satellite s components and sub components are extracted from a single master 3ds file all those files use the same local frame and thus the coordinates can be read directly from the files The SMOS example supplied with VTS perfectly illustrates this situation 4 2 3 Dimensions and units As above the size of a 3D object can either be read as is from the 3ds file or defined by VTS This choice also depends on the option used for the origin of the local frame When the origin is the geometric center of the object the Use 3ds coordinates option is unchecked the size of the object is defined in the VTS configuration utility The specified size in meters is used as the dimension of the smallest bounding box for the object When the origin is taken from the 3ds file the specified size is used as an hint of the object s size for the 3D views to optimize its display The given size should be accurate within a factor of 2 hence the
113. atellite s parent Character string Object paths in VTS Satellites are the main visualization entities in VTS This tag contains all tags related to the definition of a satellite subparts graphic properties etc Refer to the Structure of satellites in VTS chapter for more information Sample Satellite tag Satellite Name SMOS ParentPath Sol Earth 7 5 2 7 2 1 Prop2d 2D properties of a satellite The Prop2d tag defines the 2D properties of a satellite i e the icon displayed in the VTS configuration utility and for projections in 2DWin Refer to the documentation of the lt Prop2d gt generic tag in the lt Prop2d gt 2D properties section for further information 7 5 2 7 2 2 lt CommonProp gt Properties of a satellite The CommonProp tag contains property tags for a satellite This tag has no attributes Sample CommonProp tag CommonProp lt OrbitPath gt Satellite orbit path The OrbitPath tag defines the appearance of a satellite s orbit path i e the line of its past and future locations Attribute Description Format unit See also Color Orbit path color Three real numbers for red green blue in the 0 1 range no unit The satellite s orbit path can be displayed in client applications of the visualization The path length is defined as a dynamic property available in the scenario Sample OrbitPath tag lt Color 0 564706 0 0 00784314 gt 7 5 2 7 2 3 Component Satellite
114. bar or in the File menu wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 e The Open Project File dialog opens Select the Cubesat vts project file located under VTS Data CubeSat and click Open e The project is loaded into the project tree 2 2 4 Starting the visualization e To start the project visualization click the Run button in the toolbar or in the Project menu e The Broker window opens with all the client applications defined for the project the 2D window Celestia PrestoPlot etc 2 2 5 Interacting with the Broker The Broker is the core application of the visualization phase It starts the client applications regulates the visualization time sends user commands to the client applications and much more 2 2 5 1 Start of a visualization When visualization is started from the VTS configuration utility the Broker starts all the client applications defined in the VTS project During this initialization phase the Broker displays the Initializing message in the text fields of the time control area Time does not start flowing until all client applications have signaled they are ready Upon connection of the various client applications the Broker s tabs are populated with commands and information regarding these applications
115. ble must have the exe or bat file extension On a Linux platform the name can be suffixed by sh nx or might not be suffixed wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 e The application launcher must be an executable and its name must start by launcher followed by the application name case insensitive e The optional cleaner must be an executable and its name must start by cleaner followed by the application name case insensitive see the dedicated chapter below e The doc subfolder of the application folder may contain a README file The contents of this file will be displayed in the application s data in VTS configuration tool e The doc subfolder of the application folder may contain a text file with its name starting by the application name and followed by VtsConf ini If present this file must contain a description of the application s view properties appearing in the view properties editor and initial properties editor for the application e The doc subfolder of the application folder may contain an icon file with png or ico file extension If present this icon will be used in the Applications tab of the Broker If not present the application executable s icon will be used instead Sample folder hierarchy for the Celestia clien
116. c doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Initial States Property name Value 4 Application parameters Sensor geometry section count 128 Sensor coverage significant threshold 5 Sensor coverage fusion threshold 90 4 n Celestia application parameters e Sensor geometry section count Number of points making up the outline polygon of the aiming sensor surface Performance and display accuracy depend on this parameter One the one hand performance may be affected by a too high setting and a long residual trace On the other hand accuracy is better with a high setting when the satellite attitude has a large angle with the nadir If you want to focus on sensor swath accuracy increase the SensorGeometrySectionCount parameter and favor a short residual trace If you want to view long missions coverage lower the SensorGeometrySectionCount parameter with a long residual trace e Sensor coverage significant threshold The sensor swath is composed by a set of instantaneous sensor aiming surfaces represented by polygons An instantaneous aiming surface is retained when a significant percentage of new coverage is provided by the new surface The SensorCoverageSignificantThreshold parameter sets the percentage of novelty This is a minimum threshold Use a small value for an agile satellite Use a high value for a long coverage miss
117. cal sensor in Celestia g EB Celestia Fichier Navigation Temps Rendu Vue Signets Aide CubeSat 2 10 Mar 21 Distance 4934 ACT Rayon 1 djs P hagang 6 3 wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Rectangular sensor in Celestia Moreover the 3D view allows rendering the scene from the point of view of the sensor so that what the sensor perceives can be displayed refer to the 3D Cameras tab section in the Broker s user manual r E Celestia eig x Fichier Navigation Temps Rendu Vue Signets Aide Sensor camera in Celestia VTS also allows displaying the sensor s swath both in 2DWin and Celestia wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Sensor swath in Celestia Caution To preserve reasonable performances on the widest possible range of computers the computation algorithm for sensor swath in Celestia is approximate This has the consequence that when a sensor covers a large portion of its target body the computed sensor swath is erroneous near the sides of the body disc wiki kiwi Documents D
118. cccccccssssssssceccessessaaeccecesessssssceseeeseeeessseeesecseesasseeecesseesaaseeeeesgs 108 6 2 8 vli 6 2 9 View Properties COD sis taa tes 6 2 10 Events COD mE E et aies 6 2 11 3D Cameras tab 6 2 11 1 Central bodies 6 2 11 2 Satellites us EN 6 2 12 ADDIICUTIONS QD ene rT cockeds 6 2 12 1 Managing client applications sense 114 6 2 12 2 Promoting a dynamic application into a project application 115 6 2 13 Server tabs 6 2 13 1 dMoAj e te T EE ER E Y 6 2 13 2 Clients ta SRE Re 6 2 13 3 Received packets and Sent packets tabs inserer 6 2 14 Recording MOVIES iste eie teer ie oe inir teen ES d Paene ud Ed eet ee stra exa sen eds ant teen eee enr r id 6 2 15 onde r eleselosol ks 6 3 2D WIN USER MANUAL 2 0e en roe et eeu raa eR CH RU CERE SE added ons ects E lon gestae dau eua Ve vus rar walk D uk deese TERRE rue ER ERROR 6 3 1 Configuration in the VTS configuration utility 6 3 2 Specific application parameters in VTS ssiri resina aaia ia ree iaaea O Rai iae AE EEEE OAAR 6 3 3 Description OF graphic Items see eese ti tit inan a Yao en naeia aR SEa aN easa i enaa Re E ER aaa D 6 3 4 Interacting with the application csssccccccccesssesssscsecs
119. ccccccessesessssceccesssessnssesecessesssaeesecesesensseseeseeceeeesssaaesceseesuassesscesecensaaeaseceseeeauaeauess 66 6 1 2 TOOIDOF GCEONS PE EESTI LIU e e aa aaa ea e EVE Ee 67 621 271 Validity Of the project ore eme cm eet E a E e E b e Ee eme YR Ee d EEES 67 6 1 2 2 Validity of the project and its data files eese eene enne enne nennen nnne nennen nennen nennen nnns 69 6 1 3 Managing a PrOjeCt mE PEOR 69 6 1 3 1 Creating a project 6 1 3 2 Opening a project 6 13 32 Saving a PRO OClrccsecc E 6 1 3 4 Exporting an archived project sise 69 6 1 3 5 Visualizing a project 6 1 3 6 Creating entities 6 1 3 7 Copy pasting entities 6 1 3 8 Importing entities from an external project ecce tete reiche voten nitas nene Fee suat gone inner tente conan E gode une 73 6 1 4 Configuring a project and its entities iii 74 6 1 4 1 General parameters of a project 6 1 4 1 1 Configuring the project dates wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 14 11 2014 Reference VTS MU 69 6 1 4 1 2 Configuring initial properties of the visualization se 75 6 1 4 2 Config ring an entity esenee aeania ain ee erbe Ea AE sa
120. ception of the INIT messages the Broker sends several initialization commands to inform client applications of the main objects for the visualization InitCentralBody command The InitCentralBody command informs client applications of a central body used in the visualization This may be used by client applications to trigger specific initialization for this central body One such command is sent for each central body of the visualization This command has the following syntax CMD SERVICE InitCentralBody CentralBodyName lt FullParentPath gt Parameter Description Format unit See also CentralBodyName Name of a central body Character string Object paths in VTS FullParentPath Full path to the body s parent Character string Object paths in VTS InitSatellite command The InitSatellite command informs client applications of a satellite taking part in the visualization This may be used by client applications to trigger specific initialization for this satellite One such command is sent for each satellite of the visualization This command has the following syntax CMD SERVICE InitSatellite SatelliteName FullParentPath wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Parameter Description Format unit See also SatelliteN
121. coration of an event type Attribute Description Format unit See also Character string Circle Circular target Configuring event types in the VTS shape Shape name Cross Diamond Square configuration utility user manual wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Attribute Description Format unit See also Three real numbers for red green blue in Color Color of the shape the 0 1 range no unit Whether or not to fill the Fill cra Boolean Sample Shape tag Shape Shape Circle Color 1 1 0 Fill 1 gt 7 5 3 5 2 2 Icon Icon event decoration layer The Icon tag defines an icon layer for the decoration of an event type Attribute Description Format unit See also Character string Entity or Configuring event types in the VTS configuration utility user Type Type of the icon Custom renal If the type of the icon layer is Entity the entity icon i e its 2D symbol file is used for the icon layer and the tag may not contain another tag If the type of the icon layer is Custom an icon file must be provided for the icon layer through the File tag Sample Icon tag Icon Type Entity gt File Icon file for an icon event decoration layer The File tag defines a custom icon file for an icon dec
122. ct nennen enne enne rennen nennen enne nennen nnne nnne nnn nnns 75 3441 1 Value 5 Position value Gecseavcececeascivdsceadasseypeticestavsedkcesshudasanescecdevedneiceelenesanceduceateuceondestelavesshesenseantar 7 5 3 4 2 Orientation Orientation of an object ae 7 5 3 4 2 1 Quaternion Orientation as a quaternion 7 5 3 4 2 2 EulerAngle Orientation as Euler angles 7 5 3 4 2 3 AxisAngle Orientation as an axis and angle us 7 5 3 4 2 4 Direction Orientation as a direction 7 5 3 4 2 5 AltAzCoordinate Orientation as an azimuth and elevation 7 5 3 5 Events Events 7 5 3 5 1 lt File gt CIC CCSDS events file 75 3 5 2 Decoration Event type decoration oec tree et eee ee E ENTE eve e ONU FRE er av Pe EVER VON SN tete 7 5 3 5 2 1 Shape Shape event decoration layer einen 7 5 3 5 2 2 lt Icon gt Icon event decoration layer uisi eoe cesa nhe sa Ue Aeg AEA EAREC ne sn EORR e ELA exa aea talents pii ES EIC Ss Data VALU M c 75361 Eixed Fixed vals rte rea tte ti eive pt vestire ioter bese sanddedenditvevduoeesancdSvcetdbuvsisbvendoesedetbcd dusts twevaeece 753 6 2 lt File gt Satmipled valties file neenon decet os teste rere hein ees ee be PER ei ee es 7 5 3 6 2 1 lt ColorFile gt Color file for a sampled data file eene nnne 7 5 3 6 3 lt Stream gt Streamed values
123. ct menu When the visualization ends a popup offers to load any changes made to the project through the Broker during visualization These changes can then be saved or discarded 6 1 3 6 Creating entities The project hierarchy describes the project s entities in a hierarchical fashion The hierarchy can be altered through context sensitive menus Element Name 4 Project 9 Time amp Options 4 Q Celestial Bodies 4 Body Earth 2D Properties 3D Properties Position Orientation 4 Ground stations D GroundStation Toulouse GroundStation Clarksburg GroundStation Perth D GroundStation Kourou 4 5 Points of Interest Por CNES E Uu Regions of Interest ROI France 4 Satellites 4 Satellite CubeSat Events 2D Properties 3D Properties Position Orientation 4 SubPart GS 3D Properties Position Orientation a Ge Sensor Sensor Properties Position Orientation 4 Applications E 2awin 0 2dWin M Celestia 1 Celestia Projet hierarchy The following actions can be accessed by right clicking the project hierarchy e onany item o Collapse folds the selected tree item wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 o Expand unfolds the selected tree item o Copy puts a copy of the selected tree item in the clipboard o Paste pastes
124. ction is dedicated to the contents of position data no matter its source For a definition of the various data sources see the Data sources in VTS section 3 4 1 Reference frames Each object in VTS has its position defined in a reference frame For example the position of solar arrays is relative to the satellite frame An object is located at the origin of its reference frame when its position vector is null Reference frames for the positions of various object types are defined in the table below Object type Reference frame Central body Parent object s frame Ground station Central body s local frame Satellite EME2000 Earth Mean Equator at epoch J2000 Satellite s frame for a top level component Component Parent component s frame for components of other levels Satellite s frame for a top level sensor Satellite sensor Parent component s rotation center for sensors attached to a component Ground station sensor Ground station s frame 3 4 2 Position of satellite components The position for a top level component is defined in the satellite s frame The position for a sub component i e a component not directly attached to a satellite but rather to another component is defined in its parent component s frame When a component is translated or rotated all its sub components are translated and rotated as well This can be illustrated by the operation of a robotic arm each segment is animated locally relative to the previous s
125. ctly the sensor depends on sensor ratio up optional X or Y UP vector for the camera Refer to the Available cameras section of the Description of application properties chapter for more information on camera capability declarations for client applications 7 3 4 2 5 CMD PROP commands CMD PROP commands set new values for specific properties of a client application These properties are declared in the SPECIFIC section of the application s INI file Refer to the Description of application properties chapter for more information on application properties These properties include for example the equatorial grid in Celestia or the zoom level and view position in 2DWin These commands have the following syntax CMD PROP PropertyName PropertyValue Parameter Description Format unit See also PropertyName Property name Character string H Messages received by Property specific may be composed of several space Celestia PropertyValue Property value separated fields Messages received by 2DWin CMD PROP commands are sent upon modification of specific properties in the view properties editor of the Broker and when a scenario state becomes active and its view properties are restored Below are some sample CMD PROP commands e Enable the equatorial grid in Celestia CMD PROP equatorialgrid true e Reset the view position and zoom level in 2DWin CMD PROP ViewInfos Default 7 3 4 2 6 CMD STRUCT commands CMD STRUCT co
126. de esae irte se tes Rand bees pea e ne bene EE etage araa indeed ed 75 6 1 4 2 1 Position and orientation of an entity 75 6 1 4 2 1 1 Fixed positionne ne ien se sena NT sauces NR CEBA ERE e sn ne ete IR e EE VR UE tnt 76 6 14 2 1 2 Position from a file racio RUE EE AE E R N Ra gan EET rise renier EAE GER RETE in e teen net ete 76 6 14 52 1 3 Position ASA SUC AIM irs iier re cone tede pet tet eee ipeo tae li tendre red eaux roto lenelsnasuigependvacteubateeesescucusiotecslinwdeuancedt 77 6 1 4 2 2 Opientationr modes eite epi eR REPRISE a sms en Reims tenue tested rss deser cepe nca Rennes dures tem ARP cusa ce ME RARE Rudi 77 6 1 4 2 2 1 Orientation by quaternion ssssssesssseseseeee eene enne enne nnne enne nnn nennen nenne nnne nn sienne enne nnne reser nnne 78 6 1 4 2 2 2 Orientation by Euler arigles iet ettet et c o re E Peer eee Eee eee 78 6 1 4 2 2 3 Orientation by axis and angle sise 79 611 4224 Orientation by direction eiie decedit decease cides ee ide ies RD ERE NES ER SEE ER le ipex i Aqu a REN NE RENS RUE 79 611 452 2 5 Orientation by azimuth and elevation nece tege sentais ec ER vs asset rege pere ns entiere EE ENS 80 6 1 4 3 Configuring a central body ses 6 14 31 G n ral properties of a body ecu teeser a AE ec vep e kae een ANE Cue Ege LPs e RO CA pesa RE Cue see alt ensue 6 1 4 3 14 Name of aibOdy adm etras Ua arte Fo dia Dare redis e se RE exist rar Fita feud EEA
127. diva dud eue UR yis om EE AT IBETTEEETH CERERI DULL LU DULL IDOL ERA po Sc DATAMESSABRS C 7 3 4 Common messages received by client applications 141 734 1 TIME MESSI S P c 141 Uda 2a CMD MESSI pE Sakna eese coset sdcsavdaceeecctendsentaedeessatsuahtcenaeeasae ceesveaue sacccnai scabs stavaess ot o ege tended Se e RU Ren an pae A DER ede eu ERR 142 13421 CMD TIME Messages ierit tei teu H E Freie Seb RE ERE ER NR UE etienne ni nat Rene e es ei Y ERR R SE Re ka A E ERA REIS tes LER onr 142 7 3 4 2 1 1 PAUSE comimand eerte eie te caves ene Re ip Tee eie eda tec cae egets eer aleae dee E EESE 142 7 3 4 2 1 2 M E ree OT OS LS ERR ERROR 142 F 34222 OCMD SERVICE Messages P 142 7 3 4 2 2 1 InitialiZatiOn COMMMANAS rte tete ree edited te ete Ue eaae E N Er EEE E aaas EE eE E dns 142 1 3 4 22 2 CTI IPM wBvSee 7 3 4 2 2 3 Other COMMAS weiss disce ome vetet E E RR ee SANE IE I EX NR SR SEEKS EA NCANEENN ER dote i CERIS ANN VORNE 1 34 2 3 2CMD EVENT TIG SSaBBS reiten eren nene ie ecu Eee pene eos doses as aee a SE tea Ea sa aae R sers ess doses def RR MEER dns as sun esse ER ER NEEDS 7 3 4 2 3 1 LoadFile command ccccccccssccesscccessseeceesseecesseecesaeecesseeeceseecessseccesse
128. du ru Y nea Pea tu Er Foren dia d 31 3 8 3 SpDILT UVor 3 9 CENTRAL BODIES IN VTS 3 9 1 Categories of bodies 3 9 2 18 wTol Wo Bo eet a e E MA 39 21 Defaultephemieris mode i tec Rr cese EE cotes aE us TERRE QU cxsace a URS DERE INUEN EUER REEL e UN MAR SOR RR E ids EEEE Ea 3 9 22 Catalog ephemeris mode eem ic cet i e dote exe RE ie Er RP pe ee Ped ide ipee eee ee cee 3 9 2 3 QCu stom ephemieris thode 5 nore rrr rtr etg tare e ERN Tre FLY ERE DEINER E Ren Feb EE uS Re XVERE RASSE PE FUER UNIS ewe e eec MAR UE Ye Ie ere eyed 3 9 3 Central DOGGY Trame RE ER LR E e eiaa N EAEE 3 10 STRUCTURE OF SATELLITES IN VTS 3 11 SENSORS IN VT Sirana Em 3 11 1 Properties Of d SCNSOM nd she aie e aae ER ERRE e Eaa anar ra a DR o EROR RES ai aaa des nasaan 3 11 2 Visualization Of aA SensOf i isis oed nee aea raiat e ERR i aasa a OE TREE PRAE EE Hee E ge vene agre aaa 3 11 2 1 III 3 11 2 2 Grourid statiOni E S E E biatesdsbecdessadcedeanstacdagecdeusagcesdanecoscddenesghedsaasdcaveasecsUeashederacceevsd 3 12 kie Jy mre IBur re ses 3 13 SCENARIO IN VTS 3 3 13 1 pce M 3 13 1 1 Erro
129. e The TimelineFile tag defines the display parameters of a CIC CCSDS file in the project s timeline ae Format Attribute Description unit See also Character Name Name of the CIC CCSDS file string Pos Row position in the timeline Positive integer Size Row height in the timeline Pixels Mode Display mode of the file in the timeline DEFAULT for auto selected Character Graphical representation of files mode or Normal Block Event Interval Gradient Color Graph string in Scenario in VTS Overlay Flag to use an associated color file as a color overlay in the Boolean Timeline The file path must be relative to the project folder The specified display mode must be compatible with the contents of the CIC CCSDS file Otherwise it will not be applied Sample TimelineFile tag TimelineFile Name Data CIC Sat SOLAR ARRAY CURRENT TXT Pos 1 Size 23 Mode DEFAULT Overlay false gt 7 5 2 5 4 lt TimelineScript gt Display parameters of a script file in the timeline The TimelineScript tag defines the display parameters of a script file in the project s timeline Attribute Description Format unit See also Name Name of the script file Character string Scripts and macros in VTS Pos Row position in the timeline Positive integer Size Row height in the timeline Pixels The file path must be relative to the project folder Sample TimelineScript tag TimelineScript Name Data SCRIPT TXT Pos 3 Size 23 gt 7
130. e with VTS wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Object type Quaternion Euler angles on Direction Azimuth elevation Yes Central body Possible No No No E g Comet Yes Satellite Possible No No No E g Attitude Yes Yes Yes Yes Yes omponen E E g Mobile part E g Onboard E g Solar E g Representation of a E g Direction of an instrument arrays vector antenna i Yes Yes Satellite No Yes Yes sensor Ex Star tracker Ex Star tracker NB Currently the orientation of ground stations and ground station sensors cannot be modified 3 5 5 See also e Examples for position and orientation of objects in VTS e Conventions in VTS e 3D file format in VTS 3 6 EXAMPLES FOR POSITION AND ORIENTATION OF OBJECTS IN VTS This section illustrates the positioning and orientation of an object with regards to its parent satellite Relevant definitions can be found in the Position of objects in VTS and Orientation of objects in VTS sections 3 6 1 Methodology In order to fully understand the mechanisms at hand in the 3D views of VTS for the display of satellites and their parts components sensors etc the following parameters will be analyzed e Position relative to the satellite or in a more general way relative to the p
131. e Celestia executable The launcher for the 2DWin client application may print the following line to standard output TTG MyPrOJSct Vl Suis e The first field is mandatory and is the ID for the Celestia instance given as input to the launcher e The second field is the absolute path to the project file also given as input to the launcher and required by the 2DWin client application e The third field is the client application ID given as input to the launcher and required by the 2DWin client application The following scripts implement minimal sample launchers that directly return and empty command line argument for the client application only the mandatory client application ID is printed e DOS Batch Programming version launcherSample bat rem Input parameter 1 is the path to the VTS project file rem Input parameter 2 is the client application ID rem Mandatory client application ID output Gecho 2 rem End of file e Shell Script version launcherSample sh BINSA Input parameter 1 is the path to the VTS project file Input parameter 2 is the client application ID wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Mandatory client application ID output echo 2 End of file 7 1 5 Application cleaners A
132. e camera is along the Y axis of the local frame e South pole The camera is positioned above the South pole of the body pointed towards it and attached to the body s local frame The UP vector of the camera is along the Y axis of the local frame wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 6 2 11 2 Satellites Satellites are top level entities of the visualized project All satellites defined in the project appear in the hierarchy Available actions are e Inertial cameras The camera is positioned in an inertial frame attached to the satellite pointed at the satellite Expanding this item allows positioning the camera on all axes of the inertial frame e Sun and Body cameras The camera is positioned in a Sun body synchronous frame attached to the satellite pointed at the satellite Expanding this item allows positioning the camera so that it points towards the Sun body The UP vector of the camera is undefined e Satellite frame cameras The camera is positioned in the satellite s local frame pointed at the satellite Expanding this item allows positioning the camera on all axes of the satellite frame e QSW frame cameras The camera is positioned in the QSW local orbital frame pointed at the satellite Expanding this action allows positio
133. e cs icky couse e E cs A a E E E A 61 4 1 1 Hierarchy of a project folder nir evt ent take doe A EE E SY EEE EENE EEES EUERE A sie 61 4 1 2 2D icons and CORCUTCS en helene ane e a e e a dsibuceavasvaddessdandoveatesies 61 4 1 3 SD models and textures iin iei ice prese FER RAE viancndnachadnse sees LYRA RRRR SERERE ERRAR NR REPRE E A E E REE a E Eei 61 4 1 4 Importing 2D icons and 3D models from the catalog 61 4 1 5 The CIC CCSDS file format 4 2 3DFILEFORMAT IN VTS 4 2 1 File format of textures 4 2 2 Origin of the reference frame for the 3D file 4 2 3 TBI ee oe e No eR IS E ieetetide tee 4 3 CIC CCSDS DATA FILES IN VI S ccccsccccssssccssescscsesscccsususccsseusecseassesaceususecsususeceusassceususccseuaseceusasscaceususussauasecusasseeeuasessauanenes 4 3 1 References era TDI DO LLL LLLI 4 3 2 Aubl aai CAE ce 65 5 1 1 Starting the VTS configuration utility iii 65 5 1 2 Starting the visualization from the command line ss 65 6 VTS APPLICATIONS USER MANUALS sssessssssssssssssssssssssssssssssssssssasssasasasasasasasasasasssasasasasasasasasasasasasasasasasasasasasasasasasae 66 6 1 VTISCONFIGURATION UTILITYUSERMANUAL 2 572255 no eee ar sna eae dessinent dense st a cap aaee araa eub die eaea iaaa ERR ge eo pe 66 6 1 1 User interface AOSCIriIPtiOn cccsss
134. e software well known for its performance and the realism of its rendering All of Celestia s many features are thus available to VTS users As for portability the toolkit is written using C and the Qt framework ensuring stable behavior across Linux and Windows platforms Lastly available client applications come from a variety of origins As an example the PrestoPlot plotting tool is fully interfaced with VTS With these characteristics VTS becomes an essential tool for all data production activities in the satellites flight dynamics field It enables graphical validation of behaviors and attitude strategies and can be used as a practical exchange support for all actors in satellite AOCS and space mechanics 2 2 VTS QUICK START 2 2 1 Installing the toolkit The VTS toolkit comes as a zip archive To install it simply decompress it in a folder This installation folder will be referred to as VTS throughout this manual 2 2 2 Starting the toolkit The VTS toolkit can be started by double clicking the startVTS exe executable file under Windows or by running the command startVTS under Linux The main window that opens is the configuration utility It is used to create a project and define its elements satellites sensors ground stations and client applications This quick start guide will only cover opening and launching an existing project 2 2 3 Opening an existing project e Click the Open project button in the tool
135. e special value of 100 to only merge by orbit path color this mode is useful for long coverage missions where only the current orbit pass should be displayed 6 3 3 Description of graphic items 0 2dWin 2DWin The following items can be seen on the planisphere of 2DWin e The latitude longitude grid automatically adapts to the current zoom level The latitude and longitude values are displayed respectively at the left and top of the window e The terminator is the fictional line that separates the sunlit and obscured faces of the body It is displayed in yellow the obscured face appearing darker than the sunlit one e The subsolar point is the point at the surface of the body where the Sun is at the zenith e The satellite ground track appears before and after the satellite Its length can be defined in the VTS configuration utility In 2DWin the track is displayed in the body s local frame as opposed to an inertial frame in Celestia e The satellite icon is the projection of the position of the satellite in orbit on the surface of the body e The sensor footprint is the intersection of the sensor s aim volume with the surface of the body Refer to the Configuring a satellite sensor section in the VTS configuration utility user manual chapter for more information wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS M
136. e time cursor Broker only e The Follow cursor button automatically locks the view on the time cursor as it moves with the visualization date Broker only e The Reset view button zooms in out the timeline and pans it so that the whole project is displayed In the VTS configuration utility the following buttons allow navigation between scenario states e The initial state button marks the project scenario s initial state as active e The Previous state button marks the active state s previous state as active e The Next state button marks the active state s next state as active e The Final state button marks the project scenario s last state as active In the Broker the following buttons allow saving view properties of client applications into scenario states e The Create state buttons creates a new scenario state at the current visualization date and fills it with view properties gathered from all client applications The new state is saved others are not e The Save current state only button updates the currently active scenario state with view properties gathered from all client applications The active state is saved others are not e The Save all states button button updates the currently active scenario state with view properties gathered from all client applications and saves all scenario states e The Save window positions for current state only button updates the currently active scenario state with the window position of
137. eady connected clients the clients is restarted if it is in a sleeping state If the ID is known and the application is running the application is not restarted 7 3 3 3 3 CMD EVENT messages CMD EVENT messages allow client applications to add remove or reload CIC CCSDS mission event files attached to project entities The Broker will process these commands and forward them to all clients except the sender client 7 3 3 3 3 1 LoadFile command The LoadFile command instructs the Broker to load a new CIC CCSDS event file and attach it to a project satellite This command has the following syntax CMD EVENT LoadFile EventFilePath SatelliteFullName wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Parameter Required Description Format unit See also Absolute or project relative path to a CIC CCSDS event file Character EventFilePath Yes in MEM format string SatelliteFullName Yes Full name of the satellite to attach the event file to Character Object paths in string VTS 7 3 3 3 3 2 ReloadFile command The ReloadFile command instructs the Broker to reload an already loaded CIC CCSDS event file If the specified file is not an already loaded event file this command has no effect This command has the following syntax CMD EVENT ReloadF
138. easily display an overview of the whole project scenario or a detailed view of a small time frame Dates outside of the date range of the project are grayed out in the timeline In the VTS configuration utility modifications to the project in the Structure tab are not reflected automatically in the timeline The Refresh button must be clicked to update the view 3 13 1 1 Time cursor The timeline s red time cursor indicates the current visualization date It can be drag and dropped to modify the visualization date While moving the time cursor the visualization date is broadcasted synchronously to all client applications Double clicking in the timeline moves the time cursor to the mouse location and sets the visualization date accordingly Hovering above the time cursor displays a tooltip indicating the visualization date in ISO format When zooming the timeline holding the Ctrl key locks the zoom on the time cursor The time cursor is not displayed in the VTS configuration utility where time does not flow 3 13 1 2 Project scenario The project scenario is represented as a red line labelled Scenario in the VTS configuration utility and displayed in the compact mode GUI of the Broker 3 13 1 2 1 Scenario states Scenario states appear as flags in the project scenario line e ablue flag for a regular state not currently selected e ared flag for the active state the one displayed in the view properties editor e an green flag for
139. ec 60 Generate VTS Propagator The Propagator allows automatic generation of CIC CCSDS files containing position ephemerides for an elliptical keplerian orbit in a defined time range Positions are computed in the EME2000 reference frame The Propagator relies on the Orekit library to compute the ephemerides Please refer to this library s documentation for further information on how the computations are carried out 6 1 7 1 Using the Propagator 6 1 7 1 1 Generating a position file To generate an orbit ephemerides file all orbital parameters in the Classic elliptical keplerian orbit area must be filled in Note that only elliptical orbits are currently supported i e orbits with eccentricity strictly below 1 wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 The start and end dates for the CIC CCSDS file must also be defined in the Date configuration area as well as the time interval between two position values in seconds Clicking the Generate button prompts the user for the output file location and name then generates the orbit data The output data file can then be used to define the position of a satellite in the VTS configuration utility 6 1 7 1 2 Streaming position data The Propagator is also able to stream position data to
140. ecessseecessseceeeeeceesseesesueeeesseeeesseeseseeeesenes 7 3 4 2 3 2 ReloadFile command 734233 UnloadFile command root terret rer aye raa senes e doa ede ire nsa esa ee raea rE a sa Ea PER M cie a E E RE de wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 7 3 4 8 4 CMD CAMERA COMMAS sisi nine Mn nine tres nn EIN a e ve eer Es av eue Leve ti Uo be vede Met 73 4 2 52 CMD PROP COMMAMNMGS RETO EDT 7 3 4 2 6 CMD STRUCT commands errant Ine nea kv eV e aad e Rn Sade ERES EV sdesceduesecusstiedcseadeentcaceudsecavesalccdenaaees 7 3 5 Messages received by Celestia esee tart i a REPE FERA ERIS EVR VEN Ye Ee AYER AVV eo VERA RN xER E TUE STE EN E VYA SSH etes OR 43 5 1 CMDIPROP comimands cette iter helene sind e a abc Vu esas eov en aede ua Mu a assa E e EEA YE ile een teta Euer EEEE La een Dena ge 735 2 CMD STRUCT commands recens e cece ceeds onc kee Ea eoe tenue eade Attente steel 7 3 5 2 1 Central body properties 7 3 5 2 2 Satellite and subpart properties 7 3 5 2 3 Satellite properties 7 3 5 2 4 Sensor properties 7 3 5 2 5 ROI properties 5s i es 7 3 5 3 Scriptable CMD CAMERA COMMANGG
141. ectangle property e g window position and size SY 0 Width SIT H Height 480 The X Y coordinates and width height of the rectangle can each be entered manually or increased decreased using the buttons wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Page 52 type Camera Reference VTS MU 69 View View 2 1x2 Editor for camera parameters e g point of view in Celestia Reference Sol Earth Frame EME2000 Inertial Frame nol e The camera being configured is selected in the View drop down list The Celestia s mmm view layout can be controlled using the Change view layout button Y 65204 9116344074 Z 102428392735761 The reference frame the camera is attached to is defined by an object selected in Orientation the Reference drop down list and a frame selected in the Frame drop down list Quaternion Euler angles Axis and angle Direction and up mom The position of the camera in its reference frame can be entered in the Position Qi 0 1437247 group in kilometers Q2 0 7425989 Q3 06422163 The orientation of the camera in its reference frame can be entered in the Orientation group either as a quaternion as Euler angles in degrees as an axis and angle in degrees or as a direction and up vector View FOV
142. ed body in client applications Model Radius 6378 14 Km 3ds File Browse Light sensitive Use 3ds coordinates Unit m Center of gravity Coordinates in body frame X 0 Km Y 0 Km Z 0 Km 3D properties of a body The Graphics Definition radio buttons select the 3D properties to use for the body e default use the graphics properties available if Celestia if any e custom redefine the 3D mesh of an existing Celestia body or define the 3D mesh of a body not available in Celestia The parameters are similar to those described in the 3D properties of a satellite section Values are expressed in kilometers All custom 3D properties field must be filled in when redefining the 3D mesh of an existing Celestia body Custom 3D properties must be selected and a 3D mesh must be defined if the current body is not available in Celestia 6 1 4 3 4 Position and orientation of a body The VTS toolkit is mainly geared towards the visualization of missions around central bodies of the solar system In general the ephemerides of these bodies are known However it remains possible to override the ephemerides of predefined bodies or to define the ephemerides of a non default body wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Ephemeris definitio
143. eg ange a Uere ae dents 7 4 1 Application properties file format sise 7 4 2 SOCHONUS C eut 7 4 3 II goeT 1agioI eleisvslotene e 7 4 4 Available property types ccsccccccccscssssssscccccsssessnsssececseecsusesscesseessaseessceseensasssseesceesseessseeseceeseesssaesecseeseeauaseseseens y BNET HIM J A E TABid MTS TYPOS S n y co siu C NN NS NE Nr tn ne SR E E Re Ne ns 7 4 5 Available propagation Modes sses eien e a aea E E a aa a EE Ea ERE OaE raa 7 4 6 Available cameras 7 4 7 Usage in the VTS synchronization protocol 7 5 VTS PROJEGT FILE FORMAT 25 snncauns Gecesteseneacincanciaaandaaancnceed saaaseacsbadadagaasnecuceasadauanseacebadasiageasnddacanesneadibvsasenduasteacenoacavesneads 7 5 1 Notation site H 7 5 2 Project Project definition iii 7 5 2 1 lt G neral gt General project parameters cie ie mi cH WERE mme nd encre ne cave ee Reeth 7 5 2 2 lt MetaData gt Meta information about the project iii 7 5 2 3 lt StartOptions gt Initial parameters for the visualization nnne nennen nnne nnns 7 5 2 4 BrokerOptions Parameters for the Broker window ss 7 5 2 5 lt TimelineOptions gt Display
144. egment There is a special case to the relative position of sub components when using 3D files containing the position of sub components relative to the satellite s frame This case is discussed in section 3D file format in VTS 3 4 3 See also e Conventions in VTS e 3D file format in VTS e Examples for position and orientation of objects in VTS 3 5 ORIENTATION OF OBJECTS IN VTS The orientation of an object in VTS is defined as a rotation from the object s reference frame towards its attitude The orientation can be fixed sampled or streamed This section is dedicated to the contents of orientation data no wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 matter its source For a definition of the various data sources see the Data sources in VTS section 3 5 1 Reference frames Each object in VTS has its orientation defined in a reference frame For example satellites around Earth use reference frame EME2000 An object is aligned with the axes of its reference frame when its rotation vector is null In the case of a satellite defined by a 3D file see the 3D file format in VTS section the X axis of the 3D mesh is aligned with the X axis of the EME2000 frame The same applies for the Y and Z axes Reference frames for the orientations o
145. empty CIC CCSDS event file e The Edit file button on each line opens the selected CIC CCSDS event file in a text editor e The Remove file button on each line removes the selected CIC CCSDS file from the list Mission Events Eg Add 4 Create Events ALARM FILE TXT ALARM gt B Events MISSION_FILE TXT MISSION 2 B List of mission event files Each file has its top level event type displayed next to its name on its line This event type is used to construct the full event type name for events of the file The decoration of all events can be controlled in the Event Type Editor tab of the VTS configuration utility see the Configuring event types section The visibility of the events can be controlled during visualization through the Broker see the Events tab section in the Broker user manual Refer to the Mission events in VTS chapter for more information on events in VTS wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 6 1 4 4 3 2D properties of a satellite The 2D properties of a satellite define the appearance of the satellite in the 2D views and in the project hierarchy 2D properties A Symbol File Default icon for a satellite e lf the Symbol file field is empty a default icon is assigned to the satellite
146. er Data config xml Absolute path to a data file ExternalFile t portability of the project may C Generate today oem break on other machines Text field with browse button allowing absolute paths Camera description for Celestia N A Specific camera editor CameraDesc t Slider setting the total duration distribution bewteen before and after the event Changing the before or after duration modifies the total duration but not the distribution Time distribution before and TimeWindow t after a dated event Durations 5 1 should be in hours 7 4 4 3 Qt types Qt types are those handled by the QVariant class from the Qt library The table below lists the available Qt types wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Type Description Example Editor QString Character string Sol Earth Text box QStringList List of character strings comma separated 2dWin Celestia Text box QRect Rectangle integer coordinates Rect 0 0 640 480 Spin boxes X Y width height 7 4 5 Available propagation modes The following propagation modes are available e MANUAL The property may be set independently for each scenario state Its value may be propagated across states with the propagation buttons in the view properties editor
147. er plotter software such as PrestoPlot In the screenshot below this display mode is used for line 8 wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 1 Scenario 2 CIC Sat SATELLITE CONSUMED POWERtt Fi x 3 CIC Sat SOLAR ARRAY CURRENT TXT Fi lt 4 CIC Sat SATELLITE MODES txt A Ba 5 CIC Sat SATELLITE ECLIPSE TXT Fi E 6 CIC Sat POSITION VELOCITY TXT En GCS COR Comat 777 A 8 CIC Sat BATTERY DOD TXT Fi Display modes available for data files in the Timeline In order to avoid long loading times files bigger than 500Kb are only partially loaded The full contents will however be read if the user selects a mode other than Block for the file When hovered files for which the full contents have been read display a tooltip containing the value at the current location of the mouse Each line can be resized by resizing its header s line number Lines can be reordered by drag and dropping their headers line numbers Color files associated with OEM position files are used to color the line of their position file User selected display modes are saved in the VTS project file and restored upon loading of the project in the VTS configuration utility or the Broker Be aware that this might result in longer loading times if a mode other than Block
148. es 6 3 4 3 3 Moving in time A satellite can be dragged on its ground track to move forward or backward in time The dragged satellite automatically snaps to the nearest point of its ground track The corresponding date is sent to the Broker and all applications are synchronized It is possible to jump from orbit to orbit if the ground track is long enough greater than the period of the satellite s orbit This results in a similar jump in visualization time Notes e Visualization time is automatically paused when dragging a satellite e Near intersections of ground tracks typically near the poles or for ground tracks greater than the period of the satellite s orbit dragging a satellite becomes very unstable the satellite may jump from orbit to orbit depending on the position and movement of the mouse It is advised to avoid dragging a satellite in these areas if jumping from orbit to orbit is not desired wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 6 3 4 4 Mission events Mission events attached to a satellite The 2DWin application displays mission events attached to satellites and allows some interaction with them Refer to the Events attached to a satellite section in the VTS configuration utility user manual chapter fo
149. es for configuration and visualization Moreover installation of new VTS clients consists in copying the client directory in the VTS Apps folder 2 3 2 Supported operating systems OS Version Optimal for VTS Tested Comments XP X X SP3 recommended Windows Seven X X 8 1 X Linux 32bits RHEL 5 6 KDE X X RHEL 5 6 Gnome X RHEL 3 4 X Special build available on demand wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 OS Version Optimal for VTS Tested Comments Ubuntu X Additional packages may be required Debian 6 7 X Additional packages may be required RHEL 5 6 X X Additional packages may be required for RHEL 5 Linux 64bits Ubuntu X Additional 32bits compatibility packages are required Debian 6 7 X Additional 32bits compatibility packages are required Mac OS X 10 7 Lion Available soon 2 4 HARDWARE REQUIREMENTS FOR VTS This page describes the hardware requirements for proper operation of the VTS toolkit 2 4 1 Recommended system requirements e Core i5 processor or better e 4 GB RAM memory e Video card nVidia is recommended for Celestia with 1 GB memory e 1 GB free disk space For nVidia video cards prefer midrange cards GeForce 23456 50 series Here are some example systems on which VTS would run very smoothly Laptop Deskt
150. ess This position mode is mainly used for defining the coordinates of a component in the satellite s local frame 6 1 4 2 1 2 Position from a file Position 9 Constant File 9 Stream CICfile Data CUBESAT OEM POSITION TXT LL p Browse L8 v Link with a color file Data CUBESAT COLOR TXT 2 Browse Position defined by an ephemerides file e The radio button in the File tab allows specifying the path to a CIC CCSDS file containing the position ephemerides for the current entity The CIC CCSDS file format is defined in the CIC CCSDS data files in VTS section e The Edit file button opens the currently selected file in a text editor e The Browse button opens a dialog to select an existing CIC CCSDS file from disk If the selected file is not located in a sub folder of the project folder a dialog offers to copy it inside the project folder e The New CIC file button creates an empty CIC CCSDS file for the user to edit manually Note that the CIC CCSDS file header will depend on the currently selected type of position or orientation e The Link with a color file option allows specifying a CIC CCSDS color file associated with the position file through the same interface as for the position file The color file will be used to colorize the satellite s orbit path in the 2D 3D views Color files format must meet the following requirements e MEM format with 3 or 4 real fields ra
151. ever their appearance and ephemerides must be fully configured by the user wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 3 9 2 Origin of ephemeris 3 9 2 1 Default ephemeris mode Client applications choose their default mode to select the central bodies ephemerides They can use their own calculation or shipped data or VTS ephemerides catalog This option can be also used for application that don t animate the central body or if this information is not relevant for them In this mode Celestia uses its own calculation and 2DWin uses catalog ephemerides files Embedded data Default mode 4 So Ccnes Ephemeris source in default mode 3 9 2 2 Catalog ephemeris mode Client applications use the VTS ephemeris catalog data in this mode The ephemeris catalog contains CIC files describing the position and the orientation of the solar system planets between 01 01 1950 and 31 12 2100 Position files contain one point per day and orientation files contain 6 point per day These files are provided by CNES wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69
152. f an entity can be canceled by selected it in the right pane and clicking the cross button located between the two panes The Files group allows enabling or disabling the following options e Import 3D model import the 3D models and textures used by imported entities e Import CIC files import the CIC CCSDS data files used by imported entities The relative paths to the imported files in the source project will kept after the import If a filename collision occurs the user will have to decide whether to skip the import of the conflicting file rename it or overwrite the existing file The Scenario group is only enabled when client applications are identical in both the source and destination projects It allows enabling or disabling the following options e Import scenario states import the scenario states from the source project which do not already exist in the destination project e Remove states outside current project dates do not import scenario states from the source project which are outside the date range of the destination project wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 The Events allows enabling or disabling the following options e Import default event decorations import the default event decorations for all satellites e I
153. f attached to an entity and event decorations project wide or entity specific This tag has no attributes Refer to the Mission events in VTS chapter for more information Sample Events tag lt Events gt 7 5 3 5 1 lt File gt CIC CCSDS events file The File tag defines a CIC CCSDS events file attached to an entity Refer to the CIC CCSDS event files section of the Mission events in VTS chapter for more information Refer to the documentation of the lt File gt generic tag in the lt File gt CIC CCSDS file section for further information 1535 2 lt Decoration gt Event type decoration The Decoration tag contains a list of decoration layer tags defining the decoration for an event type used by client applications to display events of this type Attribute Description Format unit See also Type Event type full name Character string Event type in the Mission events in VTS chapter The Decoration tag may contain any number of Shape or Icon decoration layer tags They should be ordered from back to front meaning that the last layer tag in the list will be the topmost layer of the decoration Refer to the Configuring event types section of the VTS configuration utility user manual chapter for more information on the contents of this tag Sample Decoration tag lt Decoration Type ECLIPSE DAY gt 7 5 3 5 2 1 lt Shape gt Shape event decoration layer The Shape tag defines a geometrical shape layer for the de
154. f various object types are defined in the table below Object type Reference frame Central body Parent object s frame Z body center X towards geographic North pole Ground station At poles undefined Ground station sensor Ground station s frame Satellite EME2000 Earth Mean Equator at epoch J2000 Satellite s frame for a top level component Component Parent component s frame for components of other levels Satellite s frame for a top level sensor component frame for sub level sensors Satellite sensor Aligned with the satellite s frame and the sensor points along the Z axis Parent component s frame for a sensor attached to a component 3 5 2 Rotation center The rotation center defines the point around which a 3D object is rotated It depends on the object type and is defined in the table below Object type Rotation center Reference frame for the rotation center Central body Central body s center Central body s frame Ground station Ground station s position Central body s frame Ground station sensor Sensor s position Ground station s frame Satellite Center of gravity user defined Satellite s frame Component Rotation center user defined Component s frame Satellite s frame for a top level sensor Satellite sensor Sensor s position Parent component s frame for a sensor attached to a component 3 5 3 Orientation types In VTS an orientation can be defined by several types of rotations in the reference frame
155. ference VTS MU 69 6 VTS APPLICATIONS USER MANUALS 6 1 VTS CONFIGURATION UTILITY USER MANUAL 6 1 1 User interface description The VTS configuration utility is the entry point for the VTS toolkit It allows creating and editing VTS projects as well as starting the visualization of a project A project is composed of a set of configurable entities such as satellites central bodies ground stations and client applications These entities will be used during the visualization phase It is also possible to configure a scenario of view properties which will be played back during the visualization The following paragraphs describe in detail how to edit a VTS project CubeSatvts Visualization Tool for Space data cows File Project Help 1 BGB oo ssv oqc 0 cnes Structure Scenario Editor 4 Project 4 Q Celestial Bodies 4 Q Body 2D Properties 3D Properties Position Orientation 4 Ground stations D GroundStation Toulouse 2010 03 21 GroundStation Clarksburg GroundStation Perth GroundStation Kourou 4 sets 21995 940511 4 W Satellite CubeSat Common 2D Properties 22 34 20 3D Properties Position Orientation 55276 81260 150400 Element Message Validator The project is valid User interface of the VTS configuration utility The user interface is composed of e A menu and toolbar 1 e A pane containing a tree hierarchy of the project s entities 2 e A pane displaying properties
156. for further information For a fixed direction value the Fixed tag must contain a character string of three real number defining the X Y and Z components of the direction vector Sample Value tag Value Fixed Data 0 0 1 0 0 0 gt Value 7 5 3 4 2 5 AltAzCoordinate Orientation as an azimuth and elevation The AltAzCoordinate tag defines the orientation of an object as an azimuth and elevation This tag has no attributes It must contain a Value tag Refer to the Orientation of objects in VTS chapter for more information Sample AltAzCoordinate tag lt AltAzCoordinate gt lt Value gt Azimuth and elevation values The Value tag defines the values for the azimuth and elevation data wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Refer to the documentation of the lt Value gt generic tag in the lt Value gt Data value section for further information For a fixed direction value the Fixed tag must contain a character string of two real number defining the azimuth and elevation Both the azimuth and elevation angles are expressed in degrees Sample Value tag lt Value gt lt Fixed Data 135 6 24 3 gt lt Value gt 7 5 3 5 lt Events gt Events The Events tag defines mission events i
157. formation Sample TimelineOptions tag lt TimelineOptions gt 7 5 2 5 1 TimelineScenario Scenario display parameters in the timeline The TimelineScenario tag defines the display scenario parameters in the timeline There can be only a single such tag in the TimelineScenario section Attribute Description Format unit See also Name Must be Scenario Character string Pos Row position in the timeline Positive integer Size Row height in the timeline Pixels Sample TimelineScenario tag TimelineScenario Name Scenario Pos 0 Size 23 7 5 2 5 2 lt TimelineEvents gt Events for a satellite display parameters in the timeline The TimelineEvents tag defines the events for a satellite display parameters in the timeline This row is automatically filled with existing events attached to a satellite Attribute Description Format unit See also Name Must be Events for existing satellite name gt Character string Pos Row position in the timeline Positive integer Size Row height in the timeline Pixels Sample TimelineEvents tag TimelineEvents Name Events for CubeSat Pos 1 Size 23 gt wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 7 5 2 5 3 lt TimelineFile gt Display parameters of a file in the timelin
158. g defines the value of the coordinates of a ground station on its central body Refer to the documentation of the lt Value gt generic tag in the lt Value gt Data value section for further information This tag may only contain a Fixed tag the ground station coordinates are fixed The Fixed tag must contain a character string defining the three real number values for the latitude longitude and altitude of the ground station Latitude and longitude are expressed in degrees altitude in meters Sample Value tag for ground station coordinates lt Value gt lt Fixed Data 1 22 43 38 0 gt lt Value gt lt SensorStation gt Station sensor The SensorStation tag defines a ground station sensor A ground station may only contain a single SensorStation tag This tag has no attributes Sample SensorStation tag lt SensorStation gt lt SensorTarget gt Target of a station sensor The SensorTarget tag defines the target of a ground station sensor It must contain only a single TargetAltitude or TargetEntity tag This tag has no attributes Sample SensorTarget tag lt SensorTarget gt lt TargetAltitude gt Target altitude of a station sensor The TargetAltitude tag defines a fixed altitude as the target of a ground station sensor wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 0
159. gator start the Propagator A popup window displaying the history of all modifications to the current project can be displayed with the Ctrl Alt Z keyboard shortcut 6 1 2 1 Validity of the project The Check project action checks the following items e Applications check o Client applications of the project exist o Launchers exist for each of those client applications e Central bodies check o Atleast one central body is defined o All central bodies have unique names o Central body textures are valid o If applicable all 3D models used by central bodies exist o If applicable all data files used by central bodies are valid shallow check o All ground stations on a single body have unique names wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 o All POI on a single body have unique names o All data files used by POI are valid shallow check o All ROI on a single body have unique names o All data files used by ROI are valid shallow check e Satellites check o All satellites have unique names o All satellites are attached to a central body o All 3D models used by satellites exist o If applicable all data files used by satellites are valid shallow check o Components check All components of a single satellite have unique names All 3D model
160. gions of Interest for the visualization They are displayed in 2D and 3D applications that support them Both 2dWin and Celestia support displaying POIs and ROls 3 15 1 1 CIC CCSDS POI and ROI file format POIs and ROls are defined in CIC CCSDS files in MPM format For more information on the CIC CCSDS file format refer to the CIC CCSDS data files in VTS chapter A CIC CCSDS POI or ROI file must have the following characteristics e The USER DEFINED PROTOCOL must be NONE The USER DEFINED CONTENT may be arbitrary e The USEH DEFINED SIZE must be 2 or 3 for POls only e The USER DEFINED TYPE must be REAL or STRING for POIs only with a size of 3 e The USER DEFINED UNIT must be deg or n a for POls only with a size of 3 The data values in the file are coordinates in latitude longitude In ROI files the special data value 180 180 is interpreted as a separator and will create a new polygon with the following sequence of coordinates A single POI file may define multiple points of interest In POI files with 3 columns the last column defines a label for the corresponding coordinates 3 15 1 2 Sample POI file The following is a sample CIC CCSDS POI file CIC MPM VERS 1 0 CREATION DATE 2014 04 23T15 25 04 268055 ORIGINATOR VTS META START USER DEFINED PROTOCOL NONE USER DEFINED CONTENT POINTS OF INTEREST USER DEFINED SIZE 3 USER DEFINED TYPE STRING USER DEFINED UNIT n a META STOP 48 861348 2 34
161. hapter 3 16 1 CIC CCSDS script and macro file format Scripts are written as CIC CCSDS files in MEM format Macros are written as CIC CCSDS files in MPM format For more information on the CIC CCSDS file format refer to the CIC CCSDS data files in VTS chapter A CIC CCSDS script or macro file must have the following characteristics e The USER DEFINED PROTOCOL must be NONE e The USER DEFINED CONTENT must be SCRIPT for a script MACRO for a macro e The USER DEFINED SIZE must be 2 The first column after the date in the case of scripts must be the recipient specification for the command see below The second column must be the command to send see below e The USER DEFINED TYPE must be STRING e The USER DEFINED UNIT must be n a 3 16 2 Command recipient specification The recipient for a script or macro command may be specified using any of the following e indicates that the command shall be sent to all clients e broker indicates that the command shall be sent to the Broker itself e Name indicates that the command shall be sent to all client applications with the specified name wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 e lt D gt indicates that the command shall be sent to the client with the specified ID e Name
162. he 3D file format in VTS chapter for more information 4 1 4 Importing 2D icons and 3D models from the catalog VTS supplies a catalog of icons and 3D model Clicking on the import file from catalog S button next to an icon or model browse button will open a dialog window Validating the import will offer to copy these files inside the project folder Concerning 3D models a folder contains only one 3DS file and its textures files Importing the model will import all the files of the folder at once wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 01 Date 14 11 2014 Reference VTS MU 69 E E Import file from catalog gt Name gt j Celestial Object gt di Ground Object b Pinpoints gt Places D Spacecraft 4 Visibility Me EarthinSensorCya Me EarthinSensorMag XE EarthinSensorYello Me EarthOutSensorCy Dimensions 32x32 Me EarthOutSensorM Me EarthOutSensorVel eR 1KB Me MooninSensorCya MooninSensorMa Me MooninSensorVell Me MoonOutSensorC Me MoonOutSensor m Importing an icon from the catalog g Import file from catalog 9 Name D Arrow gt j Celestial Object 4 Satellite gt M CICSat 4 d Rosetta gt Philae b Rosetta
163. he timeline for projects with large files 6 1 6 4 Launcher 6 1 6 4 1 Clear all client application data caches This action triggers an action for all compatible VTS applications that clears the temporary files This action is available for each client application providing an application cleaner see documentation in the developer manual 6 1 7 Orbit propagation with the Propagator The Propagator can be started with the Start Propagator button in the VTS configuration utility toolbar 1 wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 2 VTS Propagator b ta Keplerian Classic elliptical keplerian orbit This program uses Orekit to provide a simple Keplerian Orbit Propagator Please refer to Orekit documentation For more info Reference Frame is EME 2000 a semi major axis km e eccentricity 0 72 currently only e smaller than 1 0 i e elliptical orbits are supported i inclination deg 33 4 w perigee argument deg 180 Q right ascension of the ascending node deg 261 M deg mean anomaly im o Date configuration Start date JD1950 MID 51544 0 000 UTC 2000 01 01 00 00 00 End date JD1950 MID 51545 0 000 UTC 2000 01 02 00 00 00 p File mode Realtime mode Propagation step s
164. ibution of an external ID if Unique client ID Integer VTS not provided Commands can be sent by the client before INIT but no TIME or DATA paquets will be received until the INIT message is sent to the Broker Below are some sample INIT commands INIT PrestoPlot CONSTRAINT 1 0 2 INIT Simulator REGULATING wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 7 3 3 2 TIME messages Client applications may set the visualization date and time ratio This is used for example when drag and dropping a satellite in the 2DWin client application TIME commands have the following syntax TIME lt TimeJD1950 gt TimeRatio Parameter Required Description Format unit See also TimeJD1950 Yes Visualization date in JD1950 format Real number Date formats in VTS TimeRatio Optional Time ratio Real number The date must be provided in JD1950 format The time ratio defines the speed ratio between visualization time and wall clock time If it is not provided the current time ratio is kept For example the following messages set the visualization date to July 9th 2016 at 00 00 03 with a time ratio of 10 compared to real time 10 seconds of visualization time pass with each second of wall clock time TIME 24296 000042 10 00000 Only clients with CONSTR
165. ich means that the visualization must be correctly configured before starting the recording Fr amp Recording settings l Output file C Users movie avi Choose Preset Custom 4 Width 800 i Height 600 Xoffset 0 T Y offset 200 Quality Low Medium High B T Pause visualization when starting recording You can use Ciri R to stop recording the movie ox cena Recording settings The following parameters must be provided e Output file Name of the movie output file The file extension will be either avi MPEG 4 or mpg MPEG 2 For correct integration of the recorded movie within Microsoft PowerPoint the mpg format must be selected e Preset List of standard movie definitions A Custom definition allows manual specification of the movie width and height e Width Height Movie definition the mouse wheel may be used on these fields for faster adjustment of the values For technical reasons linked to the requirements of the encoding codec of the movie these values must be multiples of 8 If not they will be automatically rounded up to the nearest multiple of 8 at the start of the recording e X offset Y offset Position of the recorded area the mouse wheel may be used on these fields for faster adjustment of the values wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS
166. ile 7 3 5 1 CMD PROP commands Property name i ee Description pede Propagation See also Property label ormat unit VAE moce Celestia user AntialiasingSamples oH b 4 8 Antialiasing setting for INITIAL manual section Antialiasing Samples Celestia Specific application parameters in VTS es Celestia user SensorCameraOffset dee real bosition offset of the 1 INITIAL manual section Sensor view camera offset meters Sensor View camera Specific application parameters in VTS Celestia user SensorGeometrySectionCount pogitive integer Number of points manual section making up the outline 128 INITIAL ds uper Sensor geometry section count number Boden P Specific application parameters in VTS S SwathResoluti Interval between two Celestia user E MM Hc M Positive rea instantaneous sensor 1 INITIAL mental section Sensor view camera offset number s aiming surfaces Specific application parameters in VTS Window position and WindowGeometr i i Pea size 0 0 640 480 MANUAL Window geometry x y width height equatorialgrid Boolean Display ofthe celestial equatorial false MANUAL Equatorial grid false or true grid wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Property name i Parameters Description Default Propagati
167. ile lt EventFilePath gt Parameter Required Description Format unit See also Absolute or project relative path to a CIC CCSDS event file in MEM EventFilePath Yes formiat Character string 7 3 3 3 3 3 UnloadFile command The UnloadFile command instructs the Broker to unload and detach an already loaded CIC CCSDS event file from all project satellites Events from this file are no longer attached to any satellite This command has the following syntax CMD EVENT UnloadFile lt EventFilePath gt Parameter Required Description Format unit See also Absolute or project relative path to a CIC CCSDS event file in MEM EventFilePath Yes formiat Character string Note that the specified file must have been loaded previously via a LoadFile command Event files configured in the VTS configuration utility may not be removed via the UnloadFile command they can only be removed from the VTS configuration utility itself 7 3 3 4 FWD messages FWD messages provide inter client communication by forwarding messages from one client to another These messages have the following syntax FWD lt RecipientId gt lt Message gt Parameter Required Description Format unit See also ALL character string m Recipientld Yes Application ID of the recipient Application IDs in VTS Positive or null integer Message Yes Message to forward to the recipient Character string may contain spaces The recipient ID must be an existing client
168. ile Relative txt Auto Connect 4 true Specific Args port 8889 Configuration of an application 6 1 5 Configuring event types Event types can be configured in the Event Type Editor tab of the VTS configuration utility The appearance of the event types in the Timeline and 2D views can be specified for all events of the project The GUI is composed of the following e An action toolbar e Ahierarchical view of all event types e An editing pane for the currently selected event type wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 File Project Help ARB OO B 9 o cnes Structure ScenarioEditor Event Editor Appearance Wa i Click an item to edit Type Default ALARM MISSION lt gt OEF PASS Event type editor 6 1 5 1 Loading event files The event types displayed in the tree view are loaded from the event files attached to the project s satellites Clicking the Reload Events button in the toolbar reads all event files and displays the event types available in these files This should be done manually each time an event file is added to or removed from the project or if existing event files are modified Decorations of existing event types are not affected by a reload 6 1 5 2 Configu
169. ile formats e g CIC CCSDS files into xyz or q files for Celestia and much more 7 1 4 3 Building the client application s command line The launcher must provide the command line arguments for its client application These will be appended to the application command line by the Broker To return the command line arguments to the Broker the launcher must print them on its standard output Only the command line arguments may be printed to standard output However informational messages may be printed to standard error and will be logged by the Broker The first command line argument is mandatory and must be the client application ID passed by the Broker as input parameter This ID allows the Broker to identify the client application for which the command line arguments are provided This first field will not be passed on to the client application Only arguments from the second field onwards will be passed 7 1 4 4 Sample command line arguments The launcher for the Celestia client application may print the following line to standard output 0 dir C users VTS Apps Celestia bin conf celestia cfg url C users VTS Apps Celestia bin extras 0 VTS CubeSat celx extrasdir C users VTS Apps Celestia bin extras 0 e The first field is mandatory and is the ID for the Celestia instance given as input to the launcher e The following fields are the actual command line arguments for Celestia and are standard arguments handled by th
170. ines the value of the Euler angles data Refer to the documentation of the lt Value gt generic tag in the lt Value gt Data value section for further information For fixed Euler angles values the Fixed tag must contain a character string of three real numbers defining the three rotations around the Z X and Z axes The angles are expressed in degrees Sample Value tag Value Fixed Data 90 0 45 123 lt Value gt 7 5 3 4 2 3 lt AxisAngle gt Orientation as an axis and angle The AxisAngle tag defines the orientation of an object as an angle of rotation around an axis This tag has no attributes It must contain both the Axis and Angle tags Refer to the Orientation of objects in VTS chapter for more information Sample AxisAngle tag lt AxisAngle gt lt Axis gt Rotation axis The Axis tag defines the axis of rotation for an axis and angle orientation This tag has no attributes It must contain a Value tag Sample Axis tag lt Axis gt lt Value gt Rotation axis value The Value tag defines the value of the rotation axis data Refer to the documentation of the lt Value gt generic tag in the lt Value gt Data value section for further information For a fixed rotation axis value the Fixed tag must contain a character string of three real numbers defining the three X Y and Z components of the rotation axis Sample Value tag lt Value gt lt Fixed Data 0 0 707 0 707 g
171. ing is a sample CIC CCSDS MEM script file CIC MEM VERS de CREATION DATE 2014 027215T16 19 57 ORIGINATOR VTS META START OBJECT NAME OBJECT ID SCRIPT SCREENSHOT SCROO1 USER_DEFINED_PROTOCOL NONE USER_DEFINED_CONTENT SCRIPT USER_DEFINED_SIZE 2 USER_DEFINED_TYPE STRING USER DEFINED UNIT n a TIME SYSTEM UTC META STOP 55276 3000 celestia PROP equatorialgrid true E527 G SOO OS SERVICE TakeScreenshot PROJECT DATE APPNAMES COUNT 55276 3002 celestia PROP equatorialgrid false DZ SOS S SERVICE TakeScreenshot PROJECT DATE _ APPNAME _ SCOUNTS 55276 3004 2dwin 0 STRUCT OrbitVisible Sol Earth CubeSat false BOAIE SOO OS SERVICE TakeScreenshot PROJECT DATE _ APPNAME _ COUNTS wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 3 16 5 Sample macro file The following is a sample CIC CCSDS MPM macro file CIC MPM VERS TO CREATION_DATE 2014 06 12T16 54 12 ORIGINATOR VTS META START OBJECT NAME OBJECT ID MACRO A4SPLIT MACOO1 USER DEFINED PROTOCOL NONE USER DEFINED CONTENT MACRO USER DEFINED SIZE 2 USER DEFINED TYPE STRING USER DEFINED UNIT n a META STOP CMD PROP WindowGeometry 0 0 640 480 CMD PROP WindowGeometry 640 0 640 480 CMD PROP WindowGeometry 0 480 640 480
172. ing the project file The project file contains the description in standard XML format of all the objects in the project This description refers to data files as paths relative to the project folder Portability concerns of project folders dictate that data files must reside within sub folders of the project folder Should the user select data files outside of the project folder VTS will automatically offer to copy these files inside the project folder Remarks e Itis recommended to create one folder per VTS project so that modifying a data file for a given project will not silently affect other projects e The project folder can be stored on any device hard disk drive USB stick CD and must not necessarily be located in a sub folder of the main VTS folder e Some client applications require the availability of data located in folders following a strict nomenclature The README files for these applications describe their requirements 4 1 2 2D icons and textures Objects projected on the main surface in 2D views are displayed as icons These icons may be in any of the following formats bmp gif ico jpg mng pbm pgm png ppm svg svoz tga tif tiff xbm xpm Icon files are also used for event decorations The same formats are supported Custom textures for central bodies may also be in any of the above formats 4 1 3 3D models and textures The description of a satellite refers to 3D model files Refer to t
173. ings menu item wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 r Settings Project Use auto compute project dates by default Broker Allow multiple instances Port range begin 8888 s Port range end 8888 Stream buffer length 0 50hours Log message max length 13 T Timeline Auto oad file size limit 500 00 gt B Le Auto oad item count limit 300 items gt Launcher Client application data caches Clear all c ewe Settings menu 6 1 6 1 Project options 6 1 6 1 1 Use auto compute dates by default By default this option is unchecked the compute dates button must be pressed to take in consideration all data files in use for determining the start and end dates of the project Check this option to automatically compute date on each visualization run but it might take a while on large data files 6 1 6 2 Broker options 6 1 6 2 1 Allow multiple instances By default the broker server runs on port 8888 If a visualization is run on a second instance of VTS on the same computer the Broker will fail Check this option to fill a range of ports and when the Broker starts it will scan the range for an open port Let this option unchecked but change the port range begin value to fo
174. ion i z0 22wi eos A significant threshold of 5 of novelty is ideal for an agile satellite maneuver wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Date 14 11 2014 Reference VTS MU 69 IR 20 2200 ieri m A high threshold gives good results for long coverage missions with good performance e Sensor coverage fusion threshold The sensor residual trace is composed by many polygons Its length is maintained by deleting polygons at the end of the tail For better performance polygons are merged together when two polygons have at least a certain percentage of area in common The SensorCoverageFusionThreshold parameter sets the percentage of novelty This is a minimum threshold Choose a small value when the length of the sensor residual trace must be accurate 0 of fusion will keep all wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 polygons separated Choose a high value for better performance 99 of fusion will merge huge blocks of polygons which will be removed one by one making the residual trace length vary a lot Choose th
175. ition of an object This tag has no attributes It must contain a Value tag Refer to the Position of objects in VTS chapter for more information Sample Position tag wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 lt Position gt 7 5 3 4 1 1 lt Value gt Position value The Value tag defines the value of the position data Refer to the documentation of the lt Value gt generic tag in the lt Value gt Data value section for further information For a fixed position value the Fixed tag must contain a character string of three real numbers defining the values for the X Y and Z components of the position vector The unit for a position value depends on the context kilometers for a body or a satellite meters for a satellite component or sensor Sample Value tag lt Value gt lt Fixed Data 6755 24486 1224 32145 3652 32185 gt lt Value gt 7 5 3 4 2 Orientation Orientation of an object The Orientation tag defines the orientation of an object This tag has no attributes It must contain one of the available orientation type tags described below Quaternion EulerAngle AxisAngle Direction AltAzCoordinate Refer to the Orientation of objects in VTS chapter for more information Sample Orientation tag
176. ization time for all client applications This is the playback visualization mode visualization data is read from CIC CCSDS data files and time flow can be fully controlled play pause time ratio flow direction etc The real time visualization mode allows VTS to synchronize with an external time source Upon connection to the Broker a client wishing to control the visualization time may declare itself as REGULATING as described in the INIT message connection to the Broker section above The Broker then switches to real time mode e time control buttons and commands are disabled e visualization date is received from the regulating client Note that several regulating clients may not connect to the Broker simultaneously The regulating client must send TIME messages to the Broker to set the visualization date as described in the TIME messages section above e g TIME 22105 5468754 To ensure good quality of synchronization for the visualization date a TIME message should be sent every second of wall clock time Increasing the rate will not necessarily increase the quality of synchronization due to communication delays and congestion which are better smoothed out by interpolation at a synchronization rate of 1Hz Decreasing the rate is discouraged as it may lead to misleadingly inaccurate interpolation in client applications The VTS Broker estimates the current visualization date based on the TIME messages received from the regulating
177. l body and the target of its antenna General properties Station name Toulouse Longitude deg 1 22 Latitude deg 43 38 Altitude m 0 Antenna Target Altitude km 1000 Satellite Sol Earth CubeSat General properties of a ground station e The name of a ground station must be unique on its parent body e The geographical coordinates longitude and latitude in degrees of a ground station must be defined Its altitude in meters is optional e The target of a ground station s antenna can be either a fixed altitude or the altitude of one of the project s satellites 6 1 4 7 2 2D properties of a ground station The 2D properties of a ground station define its appearance in the 2D views and in the project hierarchy 2D properties Symbol File Browse Default icon for a ground station e If the Symbol file field is empty a default icon is assigned to the ground station wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 6 1 4 7 3 Properties of a ground station sensor By convention in its canonical position a ground station sensor frame is aligned with the ground station s frame and the sensor points along the Z axis Physical properties Type Elliptical Half angle onX 10 deg Half ang
178. layed in Celestia 3 12 SCALE FACTORS IN VTS Scale factors in VTS can be applied to central bodies or satellites of a project for Celestia and client applications that support scale factors This feature allows easy visualization of both the satellite s attitude and its orbital position All satellite components are affected by the satellite s scale factor Note that when a central body s scale factor is different than 1 the computations for sensor body intersection will be erroneous in clients affected by the scale factor The scale factor for central bodies and satellites can be dynamically adjusted in the View Properties tab of the Broker using the Body scale and Satellite scale properties wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Fichier Navigation Temps Rendu Vue Signets Aide Scale factor 1 for Earth and the project s satellite wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Fichier Navigation Temps Rendu Vue Signets Aide Scale factor 0 75 for Earth and 5000 000 for the project s satellite Scale factors also allow for easy visuali
179. le on Y 10 deg Z Graphic properties Sensor contour Color BE Sensor swath Properties of a ground station sensor 6 1 4 7 3 1 Physical properties of a ground station sensor These properties are identical to those of a satellite sensor Refer to the Physical properties of a satellite sensor section for further information 6 1 4 7 3 2 Graphic properties of a ground station sensor The graphic properties of a ground station sensor define the appearance of the sensor in the 2D views Ground station sensors are not displayed in the 3D views the corresponding parameters are henced grayed out e Sensor contour o The Color button defines the color of the sensor contour wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Kourou Longitude 52 650 Latitude 5 160 Altitude 0 000m Ground station sensor in 2DWin 6 1 4 8 Configuring a Point Of Interest A Point Of Interest abbreviated POI represents one or many locations in geographical coordinates Any number of POIs can be attached to central bodies in the project Refer to the POIs and ROIs in VTS chapter for more information of the POI file format Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69
180. lication for the visualization The ID is chosen as the first available i e not already attributed application ID starting from 100 e External IDs are attributed in sequence by the Broker upon connection of a new client if it was not started by the Broker and requires automatic attribution of an ID by passing the 7 ID in the N T message sent to the Broker by the client The ID is chosen as the first available i e not already attributed application ID starting from 1000 7 3 SYNCHRONIZATION PROTOCOL FOR VTS CLIENTS Once all client application launchers have successfully terminated the Broker starts all client applications with their respective command line arguments Client applications must then connect to the Broker via TCP Once connection has been established the VTS synchronization protocol is used for communication between the Broker and its clients This chapter describes version 1 0 of the VTS synchronization protocol wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 7 3 1 Message syntax Messages must abide by the following syntax rules in order to be correctly parsed by VTS and standard client applications 1 Sent messages must be followed by a terminating newline character n 2 Message fields which contain whitespace
181. lt File gt generic tag in the lt File gt CIC CCSDS file section for further information The actual format and unit of the file data attribute depend on the context in which the parent Value tag is used 7 5 3 6 2 1 ColorFile Color file for a sampled data file The ColorFile tag defines a CIC CCSDS file to provide the color associated with some sampled data Refer to the documentation of the lt ColorFile gt generic tag in the lt ColorFile gt CIC CCSDS color file section for further information This tag is optional 7 5 3 6 3 lt Stream gt Streamed values The Stream tag defines a visualization stream for the values of some data Attribute Description Format unit See also Id Stream identifier Character string Data sources in VTS Mode Stream mode Character string INTERPOL or DIRECT Synchronization protocol for VTS clients The actual format and unit of the streamed values depend on the context in which the parent Value tag is used Sample Stream tag Stream Id satl Mode INTERPOL gt 7 5 3 7 lt File gt CIC CCSDS file The File tag defines a CIC CCSDS file Attribute Description Format unit See also Data sources in VTS Name Name of the CIC CCSDS file Character string CIC CCSDS data files in VTS The file path must be relative to the project folder If this tag is used to define a sampled file for a Value tag it may contain an optional ColorFile tag Sample File tag File
182. mand instructs the Broker that all StoreCommand commands see above in reply to a SaveState or SaveWindow context save request have been sent by the client application This command has the following syntax CMD SERVICE SaveStateFinished Synchronized command The Synchronized command is sent by clients in reply to a SynchroRequested request to indicate that the client is synchronized and ready for screen capture This command has the following syntax CMD SERVICE Synchronized The recording of high quality movies in VTS requires client applications to ensure that once a Synchronized command has been issued the visualized scene in the sender will remain frozen until the next TIME or CMD TIME PLAY message received from the Broker Refer to the Recording movies section in the Broker user manual chapter for more information on movies in VTS 7 3 3 3 2 3 StartApplication command The StartApplication command instructs the Broker to start a new instance of the specified client application This command has the following syntax CMD SERVICE StartApplication ApplicationName ApplicationId Parameter Required Description Format unit See also ApplicationName Yes Application name Character string Applicationld Optional default 1 Application ID Positive or null integer Application IDs in VTS The provided application name must match that of a client application available to VTS If the provided application ID is already used amongst alr
183. mmands set new values for structural properties of a client application These properties are declared in the entity sections of the application s INI file Refer to the Description of application properties chapter for more information on application properties These commands have the following syntax CMD STRUCT lt PropertyName gt lt EntityFullName gt lt PropertyValue gt Parameter Description Format unit See also PropertyName Property name Character string wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Parameter Description Format unit See also Full name of a target entity for EntityFullName the property Character string Object paths in VTS Messages received by Property specific may be composed of several Celestia PropertyValue Property value mM remy space separated fields Messages received by 2DWin Below are some sample CMD STRUCT commands e Set the scale factor for Earth in Celestia CMD STRUCT BodyScale Sol Earth 0 8 e Disable the sensor footprint in 2DWin CMD STRUCT AimContourVisible Sol Earth CubeSat Sensor false 7 3 5 Messages received by Celestia Apart from the common messages described above Celestia handles the commands corresponding to properties declared in its INI configuration f
184. mple events of the OEF EARTH IN SENSOR END 2 event type are orbit events at the dates when the Earth leaves the field of view of the second star tracker Event types in VTS are organized hierarchically An event type full name includes the names of all its parent types separated with slashes e g PASS KRU TC EMISSION END 3 14 2 CIC CCSDS event files Events are described in CIC CCSDS files in MEM format For more information on the CIC CCSDS file format refer to the CIC CCSDS data files in VTS chapter A CIC CCSDS event file must have the following characteristics e The USER DEFINED PROTOCOL must be NONE wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 e The USER_DEFINED_CONTENT is the top level event type name for all events in the file It will be implicitly prepended to the event type names found in the file e The USER_DEFINED_SIZE must be 1 or more The first column after the date must be the event type full name not including the top level type USER_DEFINED_CONTENT All other columns will be used as text description metadata for the event e The USER_DEFINED_TYPE must be STRING e The USER_DEFINED_UNIT must be n a The following is a sample CIC CCSDS event file CIC_MEM_VERS 1 0 CREATION DATE 2013 07 L8T1 6 19 51
185. mport satellite event decorations import event decorations for the imported satellites only available when at least one satellite has been selected for import Once the import has been configured it can be applied by clicking the OK button or canceled by clicking the Cancel button Once the import has been applied it can still be undone thanks to the Undo feature of VTS Beware that file operations will not be undone 6 1 4 Configuring a project and its entities 6 1 4 1 General parameters of a project The general parameters of a project are its start and end dates and the initial properties of the visualization used by the Broker Time Configuration Standalone Compute dates Auto compute Start date 3D1950 21994 MID 55276 0 000000 fe ISO 2010 03 21 00 00 00 UTC End date 301950 21995 940511 MID 55277 81260 150400 E3 ISO 2010 03 22 22 34 20 UTC Synchronize with system time Start Options Initial time ratio 1 0 Pause visualization Loop visualization Minimize broker Auto dose at end date Configuration of the project dates and initial properties of the visualization 6 1 4 1 1 Configuring the project dates e The Compute dates button automatically computes the date range of the project based on the widest common time interval of all ephemerides files used in the project Note dates are not updated when a data file or entity is added removed from the project wiki kiwi Documents
186. n Use the default ephemeris of a predefined body in dient applications Use the catalog ephemeris to provide external data to dient applications Use custom ephemeris for an additional body or to overload ephemeris of a predefined body in dient applications Position Constant File 9 Stream 0 0 Z 0 Orientation Quaternion Euler angle Axis and angle Dire Azimuth and eleva Quaternion Constant File Stream Configuring the ephemeris mode The Ephemeris Definition radio buttons select the position and orientation to use for the body e Default ephemeris mode client applications choose their preferred ephemeris origin e Catalog ephemeris mode client applications use VTS catalog ephemeris files e Custom ephemeris mode the user provides ephemeris to the body as described in the Position and orientation of an entity section See the Central bodies in VTS section for more details 6 1 4 4 Configuring a satellite A satellite is composed of a main component and sub components General 3D and geometric properties are configured at the component level Common and 2D properties are configured only for the main component 6 1 4 4 1 General properties of a satellite The general properties of a satellite are its name central body and parameters of its orbit path wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS
187. n specific messages are described further below Messages received by client applications are categorized as follows e TIME messages concern time synchronization e CMD messages control various aspects of the visualization e DATA messages provide values for streamed data Some commands have similar syntax as commands received by the Broker described in the above section 7 3 4 1 TIME messages Time messages synchronize client applications with the current visualization date Client applications must handle these messages in order to properly synchronize with VTS When no REGULATING client is connected the Broker broadcasts the current visualization date to all clients at a rate of 2 Hertz These messages have the following syntax TIME TimeJD1950 lt TimeRatio gt Parameters are the same as those described in the TIME messages paragraph of the Messages received by the Broker section above except that the time ratio is always provided Client applications which interpolate date between time ticks sent by the Broker may use the date provided in TIME messages to synchronize their interpolation loop Note that when the visualization is paused the time ratio is set to O 7 3 4 2 CMD messages Command messages control various aspects of the visualization for clients They are divided in several categories e CMD TIME commands inform about alterations to the flow of time but do not provide the visualization date or time ratio
188. nging from 0 to 1 for the RGB components and transparency e MEM format with 3 or 4 integer fields ranging from 0 to 255 for the RGB components and transparency e MEM format with 1 string field in HTML color format RRGGBB in hexadecimal for the RGB components no transparency 6 1 4 2 1 3 Position as a stream Position 9 Constant 9 File Stream Stream ID pos Mode INTERPOL M wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Position defined by a stream e The radio button in the Stream tab allows specifying the ID of a data stream e The stream mode can be selected as INTERPOL or DIRECT In INTERPOL mode data will be interpolated while in DIRECT mode data will be used as is without interpolation Note that the INTERPOL mode induces a delay in the visualisation Refer to the Real time VTS section in the Synchronization protocol for VTS clients chapter for further information 6 1 4 2 2 Orientation modes Orientation Q9 Quaternion Euler angles Axis and angle Direction Azimut and elevation Quaternion 9 Constant File Stream CIC file Data CUBESAT AEM ATTITUDE TXT Lx Browse BP Orientation defined by an ephemerides file e Five radio buttons allow selecting the orientation mode of an entity Q
189. ning the camera on all axes of the QSW frame e TNW frame cameras The camera is positioned in the TNW local orbital frame pointed at the satellite Expanding this action allows positioning the camera on all axes of the TNW frame e Miscellaneous cameras o Orbit The camera is positioned at a distance of the satellite s central body pointed towards the body in a direction normal to the satellite s velocity so that the orbit of the satellite can be observed The UP vector of the camera is aligned on the Z axis of the central body s local frame Hold the CTRL key while clicking to observe the scene from the opposite side of the body o Goto The camera is pointed at the satellite travelled so that it occupies as much space as possible in the 3D window and attached to the satellite s local frame The UP vector of the camera is undefined o Center The camera is simply pointed at the satellite Its reference frame remains unchanged The UP vector of the camera is undefined e Sensors These cameras are only available when sensors are attached to the satellite The camera is positioned at the location of the sensor plus an offset which can be set in the application parameters pointed in the direction of its aim vector Expanding the action allows selecting each sensor of the satellite The UP vector of the camera is the X axis of the sensor Hold the CTRL key while clicking to use the Y axis as the UP vector 6 2 12 Applications tab The
190. nt project file vts This folder also contains data referenced by the project A VTS project file is an XML file describing the entities of the visualization the start and end dates of the visualization the client applications for the visualization and the states of the visualization scenario While editing a project if the user selects some data or 3D file outside the project folder a popup will offer to copy the file under the project folder Several project files may reside in a common folder However caution must be taken when altering a shared data file as this will impact all projects using it A new project can be created by doing the following e In the toolbar click the New project button or in the File menu click the New project entry e The Create a new project dialog opens asking for a location to save the project Select a folder which will contain all files related to the project fill in the project s name and click Save 6 1 3 2 Opening a project An existing project can be opened by doing one of the following e Select the project file on disk o Inthe toolbar click the Open project button or in the File menu click the Open project entry o The Open project file dialog opens Select a project file vts and click Open e Select the project file in the list of the last 15 project files available in the File menu e Drag and drop the project file from a file browser onto the window of the VTS configuration utility
191. nterval end entry sets the visualization date to the date start date end date of the selected diamond rectangle Broker only wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 e The Select state for event Select state for interval start Select state for interval end entry marks as active the first enabled state to the left of the selected diamond rectangle start end e The Create state at event Create state at interval start Create state at interval end entry creates a new scenario state at the date of the selected diamond rectangle start end 3 13 1 6 Timeline toolbar The timeline s toolbar offers the following actions e The Add files button opens a browser to add one or several files data files or scripts to the timeline These files will have to be saved in the project folder if they are located outside of it Files not part of the structure added this way will be saved and opened on future loads of the project Files may also be added by drag and dropping them onto the timeline e The Refresh timeline button updates the timeline The project dates files events and data and the contents of these files are updated The timeline may only be updated if the project is in a valid state e The Center cursor button centers the timeline s view on th
192. o ceccccccscccsssccccssscccceeeeccsssescceuseceseusscceeseseseeesaeesusscasasuesuueseveuasacauseseausesuseseeaeausseeseueas 7537s lt File Ss CIC CESDS File e 7 5 3 8 Colorkile CIC CCSDS color file oerte riter a A GEES wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date Rev 01 Date Reference VTS MU 69 1 OVERVIEW 1 1 REFERENCE DOCUMENTS These files are referenced in this user manual RD1 D finition du protocole d change CIC V1 0 LEGAL Jean Luc 09 06 2010 Issue 1 Rev 0 DCT DA PA 2009 0021267 1 2 APPLICABLE DOCUMENTS There is no applicable document wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 06 03 2014 14 11 2014 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 2 INTRODUCTION 2 1 OVERVIEW OF VTS VTS is a visualization toolkit for space data Its primary goal is to animate satellites in both 2D and 3D environments Its
193. o the object around the rotation axis in the counterclockwise direction A positive angle implies a counterclockwise rotation around the axis convention dictates that this corresponds to screwing along the direction of the axis i e in clockwise direction while looking along the direction of the axis 3 5 3 4 Direction A direction defines a rotation so that the X axis of the object points in the specified direction It should be noted that this kind of orientation leaves a degree of freedom 3rd rotation of the Euler angles and should thus only be used for solids of revolution around the X axis e g a vector along the X axis 3 5 3 5 Azimuth and elevation Azimuth and elevation define a sequence of two rotations first around axis Z then around axis Y resulting of the previous rotation If both rotations are null the object points towards X As for the direction orientation this kind of orientation leaves a degree of freedom around the aim axis Notice that in this orientation mode conventions for sensor orientations pointing toward Z is changed for pointing towards X 3 5 4 Validity domains The different kinds of orientations are not relevant for all object types The table below lists the valid orientation kinds for all object types It should be noted that combinations marked as not relevant are still available in VTS so that they may be used should the need arise Combinations marked with a dash are however not possible to us
194. ocuments_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 In case of forceful close of Celestia when visualizing sensor swath see the section on Hardware requirements for VTS 3 11 2 2 Ground station sensor In the 2D view a ground station sensor is represented by the projection of the base of its conical aim volume at a given altitude back on the surface of its central body The altitude can also be set to the altitude of one of the project s satellites and will then vary with time A ground station sensor has the same parameters as a satellite sensor with its aim axis directed right above its ground station The angles define the half angles of the sensor s cone around the X and Y axes In order to obtain the visibility circle at minimum elevation the half angles should be set to the complementary angles of the half angles 90 half angle around X or Y Projection of a ground station sensor in 2DWin wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Kourou Longitude 52 650 Latitude 5 160 Altitude 0 000m Ground station sensor in 2DWin Ground station sensors are not disp
195. of the currently selected entity in the project hierarchy 3 wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 e A text area for notifications warnings errors etc 4 The Scenario Editor tab features all the tools required to edit the project s scenario These tools are detailed in the chapter about concepts specific to VTS in the Scenario in VTS section The Event Type Editor tab allows customizing the appearance of mission events attached to the project s satellites 6 1 2 Toolbar actions The actions below are available in the toolbar of the VTS configuration utility e New Project button Ctrl N create a new project e Open Project button Ctrl O load an existing project e Save Project button Cir S save the current project e Run button Ctrl R start the visualization e Stop button stop the current visualization e Check project button check that the project is valid e Check project and data files button check that the project and its data files are valid e Clear Logger button clear all messages in the notification pane 4 e Undo button Ctr Z undo the previous modification of the project e Redo button Cir Y redo the next modification of the project only available with a previously undone modification e Start Propa
196. oject tree Initial States Property name Value 4 Application parameters Antialiasing Samples 1 Sensor view camera offset m 1 Sensor geometry section count 128 Sensor swath resolution s 1 Celestia application parameters e Antialiasing samples Set the level of multisample antialiasing Not all 3D graphics hardware support antialiasing through most newer graphics chipsets do Larger values will result in smoother edges with a cost in rendering speed 4 is a sensible setting for recent higher end graphics hardware 2 is probably better mid range graphics The default value is 1 which disables antialiasing e Sensor view camera offset The sensor camera view accessible through 3D Camera tab in the Broker sets the camera position at the sensor position plus an offset in meters to avoid some artifacts or obstructions of sight This offset moves the camera along the Z axis e Sensor geometry section count Number of points making up the outline polygon of the aiming sensor surface Performance and display accuracy depend on this parameter One the one hand performance may be affected by a too high setting and a long residual trace On the other hand accuracy is better with a high setting when the satellite attitude has a large angle with the nadir wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03
197. olor button defines the color of the sensor contour e Sensor swath 2D and 3D views o The Mode list defines the display mode of the sensor swath The Instantaneous mode only displays the instant sensor swath for the current location of the sensor this corresponds to a trace of null duration The Duration mode allows defining the residual length of the sensor swath expressed in hours or days o The Opacity field defines the opacity of the sensor swath 0 transparent 100 opaque o The Color list allows defining the sensor swath color using one of the following 3 methods The Orbit path color mode uses the same color as the one used for the satellite s orbit path either defined in the general properties of the satellite or by the CIC CCSDS color file attached to the position file of the satellite The Fixed color mode uses a fixed user defined color The Fixed file mode uses the colors specified in a user defined CIC CCSDS color file Color files format must meet the following requirements e MEM format with 3 or 4 real fields ranging from 0 to 1 for the RGB components and transparency e MEM format with 3 or 4 integer fields ranging from 0 to 255 for the RGB components and transparency e MEM format with 1 string field in HTML color format RRGGBB in hexadecimal for the RGB components no transparency Note When using a color file the black color 0 0 0 is used to disable rendering of the sensor swath while it is in
198. ometry gt Geometric properties section for further information Position data for a satellite component is expressed in kilometers for the top level component and meters for its sub components lt SensorSatellite gt Satellite sensor The SensorSatellite tag defines a satellite sensor This tag has no attributes Sample SensorSatellite tag lt SensorSatellite gt lt Sensor gt Satellite sensor properties The Sensor tag defines the properties of a satellite sensor used for displaying the sensor s footprint on its central body in 2DWin and its volume in Celestia Refer to the documentation of the lt Sensor gt generic tag in the lt Sensor gt Sensor section for further information 7 5 2 7 2 4 lt Events gt Mission events of a satellite The Events tag defines the mission events for a satellite i e the CIC CCSDS event files and the custom event decorations for the satellite Refer to the documentation of the lt Events gt generic tag in the Events Events section for further information This tag may contain both File and Decoration tags 7 5 2 8 lt Events gt Event decorations for all entities The Events tag defines the default event decorations for all entities of the project These decorations may be overridden on a per entity basis e g through the Events tag as described in the lt Events gt Mission events of a satellite section above Refer to the documentation of the lt E
199. on See also Property label format unit value mode Camera description CameraDesc Character string target reference l Defauit MANUAL CMD CAMERA Camera parameters frame position field commands of view Selected object in the SelectObject D vi l Character string 3D view Sol Earth MANUAL Object paths in VTS Selected object Celestia full name SatelliteLabelsVisible Boolean icibili ard of all satellite inus MANUAL Satellite labels false or true aoe s SolarSystemScale iti y Positive real Scale factor for the 1 MANUAL Scale factors in VTS Solar system scale number solar system WindowMenus Boolean i Display of the menu false MANUAL Window menu false or true bar WindowText Boolean Display of text information on the true MANUAL Window text false or true current object AmbientLight 9 Real number Amount of articifial 0 3 MANUAL Ambient Light within 0 1 ambient light AllPoiVisible Boolean i i 1 i dd of all Points of i MANUAL e and ROls in All POI visibility false or true teres AllRoiVisible Boolean i i mil Wed pl ttug MANUAL and ROls in All ROI visibility false or true egionsor interes 7 3 5 2 CMD STRUCT commands 7 3 5 2 1 Central body properties Property name i ie Description suns Propagation See also Property label ormat unit value mode BodyScale Positive real Scale factor for the central 1 MANUAL Scale factors Body scale number body in VTS Eme2000Axes Visible Boolean Display of the EME2000 figs MA
200. op Processor 3rd gen Intel Core i7 3610M 3 30GHz 6MB 3rd gen Intel Core i7 3770 3 40GHz 8MB Memory Dual channel SDRAM DDR3 4 GB 1600 MHz Dual channel SDRAM DDR3 8 GB 1600 MHz Video NVIDIA GeForce GT 650M 2 GB NVIDIA GeForce GT 640 1 GB Hard drive SATA 1TB 5400 rd min SATA 1TB 7200 rd min 2 4 2 Minimal system requirements e 1GHz processor e Dedicated video card with 128 MB memory nVidia GeForce 5000 or equivalent embedded video card for modern processors Intel HD Graphics 3000 e 512 MB memory e 500 MB free disk space Such a system will run VTS but won t handle the more realistic rendering options in Celestia wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 2 4 3 Video card drivers In order to get the best performance from a machine video card drivers should be kept up to date This will solve the majority of display problems encountered while using Celestia Driver updates are available on the website of the card s chipset maker nVidia ATI or Intel or on the website of the system maker for some laptops Issues with Celestia and sensor swath if Celestia closes forcefully while running a visualization with sensor swath enabled it may be due to outdated graphics card drivers If drivers are up to date and
201. or contour false or true contour AimVolumeVisible Boolean Display of the sensor volume true MANUAL Sensor volume false or true AimAxisVisible Boolean Display of the sensor aim axis false MANUAL Sensor axis false or true AimTraceVisible Boolean Display of the sensor swath trace false MANUAL Sensor swath false or true 7 3 5 2 5 ROI properties Property name parameters format Default Description Propagation mode See also Property label unit value RoiVisible Boolean Display the region of POIs and ROIs in ss apf true MANUAL ROI visibility false or true interest VTS 7 3 5 3 Scriptable CMD CAMERA commands Scriptable CMD CAMERA commands are not used by the Broker but they can be used inside VTS scripts refer to the Scripts and macros in VTS chapter for more information These commands have the following syntax CMD CAMERA lt CameraName gt lt CameraParameters gt The table below describes available cameras See Camera name Parameters unit Description alee X Y where X is the number of views horizontaly and Y Creates multi viewports each viewport has CreateMultiview the number of views verticaly a scriptable camera X Y coordinates of the viewport to control in MultiView Select a viewport the next command will SelectView mode only affct this viewpot SetFov angle Field Of View angle in randians Changes the current camera field of view wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G
202. or meters 3D file format in VTS If attached to a central body the radius is expressed in kilometers If attached to a satellite or component the radius is expressed in meters Refer to the 3D file format in VTS chapter and to the 3D properties of a satellite section of the VTS configuration utility user manual chapter for more information Sample Radius tag Radius Value 2 79382 7 5 3 3 3 lt LightSensitive gt Light sensitivity of an object The LightSensitive tag defines whether or not to shade an object in 3D views Attribute Description Format unit See also Value Object light sensitivity Boolean A value of 1 enables object shading A value of 0 disables object shading Refer to the 3D properties of a satellite section of the VTS configuration utility user manual chapter for more information Sample LightSensitive tag lt LightSensitive Value 1 gt 7 5 3 3 4 lt Use3dsCoords gt Usage of an object s 3DS coordinates The Use3dsCoords tag defines whether or not to use the coordinates system from the 3DS file of an object in 3D wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 views Attribute Description Format unit See also Value Usage of 3DS coordinates Boolean 3D file format in VTS MeshScale Scaling factor
203. oration layer Attribute Description Format unit See also Name Name of the icon file Character string The File tag may only be used for Custom icon decoration layers The name of the icon file must be relative to the project folder Sample File tag File Name Models sun png gt 7 5 3 6 lt Value gt Data value The Value tag defines the values for some project data This tag has no attributes It must contain one of the tags described below according to the data source Fixed File or Stream Refer to the Data sources in VTS chapter for more information Sample Value tag lt Value gt 7 5 3 6 1 lt Fixed gt Fixed value The Fixed tag defines a fixed value for some data The fixed value is stored as an attribute to the Fixed tag wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Attribute Description Format unit See also Data Fixed value for the data Character string for the fixed value Data sources in VTS The actual format and unit of the Data attribute depend on the context in which the parent Value tag is used Sample Fixed tag Fixed Data 1 0 0 0 7 5 3 6 2 lt File gt Sampled values file The File tag defines a CIC CCSDS file containing sampled values for some data Refer to the documentation of the
204. ormation on these messages can be found in the Synchronization protocol for VTS clients section The TIME CMD and DATA checkboxes allow enabling or disabling the display of these classes of messages in the list 6 2 14 Recording movies Movies can be recorded by the Broker during visualization When recording a movie client applications are synchronized frame by frame and an image is captured at each frame The output movie is set at a framerate of 25 images per second Note that recording a movie is not possible when the Broker is in real time mode For more information on real time mode refer to the Real time VTS section of the Synchronization protocol for VTS clients chapter To start recording a movie click the Record movie entry in the Broker s action menu wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 ji 3 4 21 03 2010 22 03 2010 suc PESEE Broker VTS CubeSat vts Dock on top of screen Dock on bottom of screen Lj e El Disable always on top Lgj Save Broker position Record movie M Add application gt Run macro gt c Quit Recording a movie A configuration dialog pops up and visualization is paused Interaction with the Broker is disabled while the dialog is opened wh
205. osing a body name amongst the planets of the solar system The planet s radius is automatically filled in in the 3D properties of the body e A body not known to Celestia can be defined However it will then be necessary to provide user defined 3D properties and ephemerides 6 1 4 3 1 2 Texture of a body The texture of a body defines its appearance in the 2D and 3D views It can be defined in 3 ways selected by a radio button Built in Fixed Timed The Preview area displays the currently selected texture for the current body Notes e User defined textures must correspond to a plate carr e projection i e with a 1 2 ratio and centered on longitude 0 e Due to limitations in Celestia only one central body may used the Fixed or Timed texture types in the project Built in texture Texture properties Q Built in texture _ Fixed texture file C Timed texture file Built in textures are only available for bodies for which a texture exists in Celestia Preview Built in texture wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 The texture is provided by Celestia if available Celestia has built in textures for all planets of the solar system and some of their natural satellites Fixed texture Texture properties Built in
206. pacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Target entity Camera name Corresponding Broker cameras Sun and Body cameras e View from Body Satellite QswFrame e View toward Body QSW frame cameras Satellite TnwFrame TNW frame cameras Miscellaneous cameras Satellite Orbit e Orbit Miscellaneous cameras Satellite Goto e Goto Miscellaneous cameras Satellite Center e Center Sensor Sensor SensorView Sensors Refer to the CMD CAMERA commands section in the Synchronization protocol for VTS clients chapter for more information on the corresponding camera messages sent to client applications 7 4 7 Usage in the VTS synchronization protocol Properties and cameras declared in the INI file are used by the VTS synchronization protocol to generate commands for client applications Properties in the INITIAL and SPECIFIC sections are translated into PROP commands while those in entity specific sections IBODY COMPONENT SATELLITE and SENSOR are translated into STRUCT commands Cameras in the CAMERAS section result in corresponding CAMERA commands being sent Specific properties MD PROP lt PropertyName gt lt PropertyValue gt or example D PROP WindowGeometry 0 1 640 480 tructural properties nana Z CMD STRUCT lt PropertyName gt lt EntityFullName gt lt PropertyValue gt For example CMD STRUCT
207. parameters for the project s timeline nnne 7 5 2 5 1 TimelineScenario Scenario display parameters in the timeline 7 5 2 5 2 TimelineEvents Events for a satellite display parameters in the timeline 7 5 2 5 3 TimelineFile Display parameters of a file in the timeline 7 5 2 5 4 TimelineScript Display parameters of a script file in the timeline 7 5 2 5 5 TimelineStream Stream display parameters in the timeline 7 5 2 6 ToBeUsedApps Client applications for the visualization 7 5 2 6 1 Application Project client application 2s E m 7 5 2 6 1 1 SpecificArgs Additional parameters for an application 75 27 Entities Entities of the visualization riti er tp ee E De EI FERE SERE den es rm ex Eee teme aes VE 27 5 EE 4 To To ROCA To des HO dy PERRO 75 27 11 Texture Body texture iier ere dx EEEE pa Rua aHa EEEE ha Uns aue ERR RAS EXE XN SPAN NEUE RAS ERR VN Nu FE ese TES wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 14 11 2014 Reference VTS MU 69 7 5 2 411 2 lt Prop2d gt 2D properties of a body uice easet ires Ee Er do aede a Ree ERR eg 166 7 5 2 7 1 3 Graphics3d 3D graphic properties of a body 166 7 5 2 7 1 4
208. path before and after the 22 MANUAL Orbit time window duration after event in satellite hours Eme2000Axes Visible M Boolean Display of the EME2000 fide MANUAL EME2000 inertial frame v io or true inertial reference frame axes QswAxesVisible Boolean Display of the QSW local false MANUAL QSW local frame axes false or true orbital frame TnwAxesVisible Boolean Display of the TNW local tales MANUAL TNW local frame axes false or true orbital frame FrameAxes Visible Boolean Display of the local satellite inda MANUAL Satellite frame axes false or true frame SunDirectionVisible Boolean Display of the Sun direction false MANUAL Sun direction false or true vector BodyDirectionVisible Boolean Display of the satellite body MANUAL Body direction false or true direction vector wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Property name i Parameters format unit Description Default Propagation See also Property label value mode VelocityVectorVisible Boolean Display of the satellite false MANUAL Velocity vector false or true velocity vector 7 3 5 2 4 Sensor properties Property name Parameters torma Description Default value Propagation mode ce Property label unit also AimContourVisible Boolean Display of the sensor base true MANUAL Sens
209. pen source software developed amongst others by Chris Laurel VTS relies on the latest source version of Celestia http www shatters net celestia It is interfaced with VTS through LUA scripts wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 6 4 4 Integration with VTS Celestia is fully integrated with VTS All of Celestia s features related to the visualization of satellites within the perimeter of VTS are available directly from the Broker These features are described in detail in the Messages received by Celestia section of the Synchronization protocol for VTS clients chapter and in the 3D Cameras tab section of the Broker user manual chapter 6 4 2 Navigating in Celestia The main navigation controls in Celestia are e Left click mouse move camera pointing e Right click mouse move rotation around the selected object e Mouse wheel zoom in out on the selected object e Shift left click mouse move change field of view e Left right arrow keys camera roll All controls are described in Celestia s Help menu the menu bar must be enabled in the Broker 6 4 3 Specific application parameters in VTS When adding Celestia as a VTS client application some parameters can be set by clicking on the Celestia entry in the VTS pr
210. ption Format unit See also Name Timed texture file name Character string Texture of a body in the VTS configuration utility user manual Sample TextureTimedFile tag TextureTimedFile Name Data EARTH TEXTURE TXT The file name must point to a CIC CCSDS file in MEM format defining the textures to use and its path must be relative to the project folder lt TextureTimedFileCyclic gt Timed cyclic body texture file The TextureTimedFileCyclic tag defines the timed cyclic texture file of a central body Attribute Description Format unit See also Name Timed cyclic texture file name Character string Texture of a body in the VTS configuration utility user manual Epoch Texture cycle epoch Real number JD1950 wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Attribute Description Format unit See also Period Texture cycle period Real number days Sample TextureTimedFileCyclic tag TextureTimedFileCyclic Name Data EARTH TEXTURE CYCLIC TXT Epoch 18262 Period 2 gt The file name must point to a CIC CCSDS file in MEM format defining the textures to use and its path must be relative to the project folder 7 5 2 7 1 2 lt Prop2d gt 2D properties of a body The Prop2d tag defines the 2D properties of a central body i
211. r ca a 7 Sensor swath Mode Duration 2 hours Color Colonflemmmx Data CUBESAT_SENSOR_COLOR TXT L2 Browse Properties of a satellite sensor 6 1 4 6 2 1 Physical properties of a satellite sensor A sensor is described by the following physical properties e The sensor s shape the Type drop down list defines either an Elliptical conical or Rectangular pyramidal base for the sensor e The sensor s aperture the Half angle on X and Half angle on Y fields define the half angles of aperture around the X axis in the YZ plane and around the Y axis in the XZ plane These angles are expressed either in degrees or radians 6 1 4 6 2 2 Graphic properties of a satellite sensor The graphical properties of a sensor define its appearance in the 2D and 3D views wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 e The Range field defines the maximum length of the sensor volume in the 3D views expressed in kilometers e Sensor volume 3D views only o The Color button defines the color of the sensor volume This color is also used in the graphical interfaces to identify the sensor o The Opacity field defines the opacity of the sensor volume 0 transparent 100 opaque e Sensor contour 2D and 3D views o The C
212. r Decreases the time ratio Two clicks on this button result in a 5 times slower time flow The current time ratio is displayed next to this button e Faster Increases the time ratio Two clicks on this button result in a 5 times faster time flow e Revert Every click on this button inverts the time flow direction The time ratio remains unchanged 2 2 5 3 2 Timeline The timeline 2 displays the visualization s time range Dragging the cursor controls the visualization s current time While moving the cursor the current time is kept updated in all client applications synchronously For finer or coarser grained time control the timeline can be zoomed in out using the mouse wheel 2 2 5 3 3 Current time A text area 3 displays the current visualization time The default format is the ISO time format date and time in UTC The arrow button circles through other available time formats CNES julian day JD1950 fractional days with reference date January 1st 1950 and modified julian day MJD days and seconds reference date November 17th 1858 The Edit date button pops up a dialog in which the current visualization time can be accurately defined in all of the above time formats 2 3 SOFTWARE REQUIREMENTS FOR VTS This page describes the software requirements for proper operation of the VTS toolkit 2 3 1 Write access permission VTS needs write access permission in its whole folder hierarchy Many tools create temporary fil
213. r file for the sensor swath The ColorFile tag defines a CIC CCSDS color file for the color of the sensor swath in client applications Refer to the documentation of the lt ColorFile gt generic tag in the lt ColorFile gt CIC CCSDS color file section for further information If present this tag selects the Color file sensor swath color mode in the VTS configuration utility Refer to the Graphic properties of a satellite sensor section in the VTS configuration utility user manual chapter for more information 7 5 3 1 2 lt Geometry gt Geometric properties of a sensor The Geometry tag defines the position and orientation of a sensor Ground station sensors define this tag but do not use it Refer to the documentation of the lt Geometry gt tag in the lt Geometry gt Geometric properties section for further information Position data for a sensor is expressed in meters 7 5 3 2 lt Prop2d gt 2D properties The Prop2d tag contains all tags related to the 2D properties of a visualization object This tag has no attributes Sample Prop2d tag lt Prop2d gt 7 5 3 2 1 lt SymbolFile gt 2D symbol file The SymbolFile defines the image file to use as the icon of an object in 2D views VTS usually provides a default icon for its various visualization entities which can be overridden by this tag Attribute Description Format unit See also Name 2D symbol file name Character string 2dWin user manual
214. r more information The appearance of mission events can be defined in the Event Type Editor tab of the VTS configuration utility Refer to the Configuring event types section in the VTS configuration utility user manual chapter for more information 6 3 4 5 Interacting with events Events at the exact same date or at dates close enough that they appear to be at the same date at the current 2DWin zoom level will animate and split when the mouse is hovered above them Hovering above a single event will display a tooltip containing the name of the satellite the event is attached to the name of the event as well as additional data provided by the CIC CCSDS event file The line segment linking the icon of an event to its actual position on the satellite ground track is the same color only a bit lighter as that of the satellite ground track Double clicking an event will set the current visualization time to the date of the event The satellite then appears located at the position of the event The visualization is also paused The visibility of all event types can be controlled from the Events tab of the Broker Refer to the Events tab section of the Broker user manual chapter for more information wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Date 14 11 2014 Reference VTS MU 69 SUN IN SEN
215. rCoverageMergingThreshold Positive real 90 percentage for INITIAL Specific Sensor coverage merging threshold number 96 merging application polygons parameters in VTS wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 7 3 6 2 CMD STRUCT commands 7 3 6 2 1 Central body properties Property name perty Parameters format Description viden Propagation mode in Property label unit value also TerminatorVisible Boolean Display of the day night inis MANUAL Terminator false or true terminator SubsolarPointVisible Boolean Display of the Sun zenith true MANUAL Subsolar point false or true position 7 3 6 2 2 Satellite properties Property name i aed Parameters format unit Description ai i SO a See also Property label value mode OrbitVisible Boolean Display of the satellite orbit MANUAL Orbit path false or true path OrbitWindow Two Positive real numbers Duration of the satellite s orbit Orbit time Duration before event path before and after the 22 MANUAL window duration after event in hours Satellite VisibleEvents Events tab in the Character string list List of visible event types Pee MANUAL Broker user Visible events manual 7 3 6 2 3 Sensor properties Property name Parameters format Des ristion Default Propagation See Property label unit p val
216. race CO LAL SPACEBEL SAS VTS Equipe VTS VTS MU G 69 SPB Change 05 Date 06 03 2014 Issue 01 Date 14 11 2014 Ref VTS MU 69 Distribution Code SE USER MANUAL VTS2 Written by Date 14 11 2014 Equipe VTS SPACEBEL SAS Approved by For application wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS Technoparc 8 Rue Jean Bart 31670 LABEGE France T l 33 5 32 09 09 09 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 INDEX SHEET CONFIDENTIALITY KEYWORDS VTS User Manual DLP TITLE User Manual VTS 2 AUTHOR S Equipe VTS SPACEBEL SAS SUMMARY This document is the user manual of VTS LOCALIZATION VTS MU VOLUME 1 TOTAL NUMBER OF PAGES 185 COMPOSITE DOCUMENT N LANGUAGE EN INCLUDING PRELIMINARY PAGES 0 NUMBER OF SUPPL PAGES 0 CONFIGURATION MANAGEMENT NG CM RESP REASONS FOR EVOLUTION Release of VTS 2 6 Rosetta CONTRACT March sous accord cadre n 116754 HOST SYSTEM Microsoft Word 11 0 11 0 5604 C Documents and Settings Administrateur Application Data Microsoft Templates Normal dot Version GDOC v4 2 2 2 Base projet wiki spacebel fr kiwi Outils Gdoc vts mdb RELATED DOCUMENTS Stand alone document wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual V
217. rce a single value different from 8888 Important If the server port is different from 8888 the launchers will be started with a serverport lt portNum gt option in command line 6 1 6 2 2 Stream buffer length Configure the length of the DATA buffer which is used to display streamed values in the Timeline wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 6 1 6 2 3 Log message max length Configure the message max width displayed in the Server Received packets or Server Sent packets Wider messages are truncated 6 1 6 3 Timeline 6 1 6 3 1 Auto load file size limit Configure the maximum size for files displayed in the project timeline The data for files above this size will not be loaded the file will appear as a gray box without tooltips Note that the dates and file type are still loaded Tuning this setting allows to speed up the loading time of the timeline for projects with large files 6 1 6 3 2 Auto load item count limit Configure the maximum number of data lines for files displayed in any mode other than Block mode in the project timeline Files containing more lines will have their data loaded but displayed in colored Block mode with tooltips showing the data Tuning this setting allows to improve the responsiveness of t
218. refer to the T ME messages above for this e CMD SERVICE commands control various aspects of the visualization unrelated to time wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 e CMD EVENT commands deal with CIC CCSDS mission event files for the visualization e CMD CAMERA commands define the camera position and target for client applications handling camera commands e CMD PROP commands set new values for specific view properties of client applications e CMD STRUCT commands set new values for structural view properties of client applications 7 3 4 2 1 CMD TIME messages 7 3 4 2 1 1 PAUSE command The PAUSE command informs client applications that visualization is paused Clients may then stop all animation of the visualization scene while still letting the user interact with their GUI This command has the following syntax CMD TIME PAUSE Visualization date is still sent by the Broker when the visualization is paused However it remains constant and the time ratio is set to 0 7 3 4 2 1 2 PLAY command The PLAY command informs client applications that visualization has resumed from pause This command has the following syntax CMD TIME PLAY 7 3 4 2 2 CMD SERVICE messages 7 3 4 2 2 1 Initialization commands Upon connection after re
219. request see below SaveWindow request The SaveWindow request informs client applications that a window position and geometry context save is ongoing and instructs them to send back to the Broker the corresponding StoreCommand command This request has the following syntax CMD SERVICE SaveWindow Client applications should reply with a single StoreCommand command for the specific WindowGeometry property command The value for this property is application specific e g CMD SERVICE StoreCommand CMD PROP WindowGeometry 0 480 640 480 Note Once the SaveWindow request has been issued by the Broker client applications are expected to send back a StoreCommand command for the WindowGeometry property within 1 second Beyond this time frame the context save will time out for clients which have not responded Refer to the Timeline toolbar section of the Scenario in VTS chapter for more information on window position and geometry context save actions SynchroRequested request The SynchroRequested request instructs client applications that they should freeze the visualization at the last transmitted visualization date This request is transmitted when a movie recording is ongoing in the Broker Refer to the Recording movies section in the Broker user manual chapter for more information on movies in VTS This request has the following syntax CMD SERVICE SynchroRequested Client applications should reply with the Synchronized command
220. ring default event type decorations When the Toggle Edit Entity Decorations Mode button is untoggled the event type editor is in basic mode and only the All satellites column is visible Decorations configured in this mode will apply to all satellites in the project The default decoration displayed in the tree for all types is a gray diamond Clicking the decoration on the line of an event type selects it for edition in the editing pane The Customized option can then be enabled to customize the event type s decoration e The and buttons add or remove decoration layers e The arrow buttons move the selected layer up or down The preview area displays the event type decoration as it will appear in client applications that handle events Stars in the hierarchical view indicate event types with custom decorations Decorations are inherited by all descendant types of a decorated event type unless one of these descendants itself has its decoration customized 6 1 5 2 1 Shape layers Shape decoration layers have the following properties e the shape of the layer Circle Circular target Cross Diamond or Square e the color of the layer e whether or not to fill the shape 6 1 5 2 2 Icon layers Icon decoration layers allow the user to select one of the following appearances wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Iss
221. roker VTS Ar amp K i S Real time ES ISO 2016 07 09 07 30 59 UTC Pw ge gs ep Oo 09 07 16 00 00 RE oO CIC Sat POSITION VELOCITY TXT CIC Sat SATELLITE ECLIPSE TXT CIC Sat SATELLITE MODES bt CIC Sat SATELLITE CONSUMED POWER b CIC Sat SOLAR ARRAY CURRENT TXT CIC Sat BATTERY DOD TXT D Uu BR WN oH NON NN NN LLC en Timeline View Properties Events 3DCameras Applications Server Project timeline The contents of the timeline are described in the Timeline section of the Scenario in VTS chapter 6 2 9 View Properties tab The View Properties tab allows interacting with client applications and defining the properties of all project scenario states wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Broker vts IE amp qui S Real time eee 0 600 A UTC 2016 07 09 07 26 53 Label ere Acquisition Application Property name Value E 0 Celestia 4 Application parameters Window geometry 600 0 680x480 1 2dWin Equatorial grid C false Camera parameters lt Double click to view gt Selec
222. roperties editor of the VTS configuration toolkit or of the Broker Initial properties sent to clients upon connection may also be described 3D client applications may also declare compatible cameras available in the 3D Cameras tab of the Broker It is the client application s responsibility to ensure it is compatible with the cameras it declares to have available 7 4 4 Application properties file format The applications properties file must be located in the doc subfolder of the application folder with the following name application name VtsConf ini This file is in standard INI format It must be composed of sections with uppercase names Properties in each section are stored in associative arrays with keys prefixed by a number in order to preserve the order of declarations when displaying the properties in VTS Array keys must be written in lowercase Important array keys in a single section are numbered from 1 to N The section must hold the size N statement 7 4 2 Section list e INITIAL Initial properties for the application These properties are configured in the application s pane in the Structure tab of the VTS configuration utility The propagation mode must be set to NITIAL for all properties in this section e SPECIFIC Specific properties for the application wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB
223. s line number Lines can be reordered by drag and dropping their headers line numbers 3 13 1 3 2 Interacting with events Right clicking on an event displays a context menu with the following actions e The Go to event entry sets the visualization date to the date of the selected event Broker only e The Select state for event entry marks as active the first enabled state to the left of the selected event e The Create state at event entry creates a new scenario state at the date of the selected event 3 13 1 4 Project scripts VTS scripts used by the project are displayed in the timeline Each script has its own line Refer to the Scripts and macros in VTS chapter for more information on script files 3 13 1 4 1 Graphical representation of scripts The header of each line shows the name of the script Script commands are displayed as red diamonds at the date at which they occur Each line can be resized by resizing its header s line number Lines can be reordered by drag and dropping their headers line numbers wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 3 13 1 4 2 Interacting with scripts The following actions are available for script headers e Double clicking the header sets the zoom level and pans the timeline so that the line s
224. s the time system UTC both for display and internal calculations 3 2 2 Entering a date When a date needs to be specified anywhere in VTS the same user interface is used The date can be entered in the JD1950 MJD and ISO formats wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 16717 999291871 49999 86338 817654 1995 10 09 T 23 58 58 UTC Lo cancel jJ Date dialog in VTS 3 3 DATA SOURCES IN VTS There are three types of data sources in VTS e Fixed a fixed value e File a time dependent value read from a file e Stream a value provided by a network stream 3 3 1 Fixed data source This data source provides a constant user defined value The actual value is defined by the user upon selection of the source This source can be used eg for the position and orientation of fixed satellite components and sensors 3 3 2 File data source This data source is based on a file specified by the user upon selection of the source The values are read from the file which must follow the standard CIC CCSDS format This source can be used for the ephemerides of celestial bodies satellites as well as for the position and orientation of mobile parts on satellites It is most adequate for offline visualization once the position
225. s to use an acyclic timed texture with texture changes adjusted for the project Dates in the MEM file are interpreted as durations from the start of the cycle This means that a timed texture MEM file must contain dates in the MJD date format For example the following lines 0 0 Textures plankton_00 jpg 0 7200 Textures plankton 01 jpg specify that the image file Textures plankton 00 jpg is to be used as texture at the start of a cycle and that the image file Textures plankton 01 jpg is to be used as texture two hours after the start of a cycle Beware if MJD date 0 0 is not present in the MEM file no texture will be displayed at the start of a cycle 6 1 4 3 2 2D properties of a body The 2D properties of a body allow configuring its appearance in the project hierarchy 2D properties Symbol File Browse Default icon for a body e f the Symbol file field is empty a default icon is assigned to the body 6 1 4 3 3 3D properties of a body The 3D properties of a body define its appearance in 3D views wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Graphics definition Use the default graphics of a predefined body in client applications O Use custom graphics for an additional body or to overload graphics of a predefin
226. s used by components exist f applicable all data files used by components are valid shallow check Sub components check o Sensors check All sensors on a given satellite have unique names f applicable all data files used by sensors are valid shallow check e Dates check o Project start date is before its end date o All data files used by the project cover the time range of the project o Catalog ephemerides for default bodies used in the project cover the time range of the project e Additional checks o All additional files displayed in the timeline are valid shallow check o All script files used by the project are valid shallow check Checks on data files are shallow i e only the header and file metadata are checked e No errors in the header e Data type described in the metadata matches what VTS expects o Data type o Data dimension o Data unit wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 6 1 2 2 Validity of the project and its data files The Check project and data files action covers the perimeter of the Check project action and also ensures the contents of all data files can be loaded without errors 6 1 3 Managing a project 6 1 3 1 Creating a project By definition the project folder is the folder containing the curre
227. s will be saved in the project scenario 6 2 13 Server tab The Server tab displays information on the connection and communication of client applications with the Broker 6 2 13 1 Log tab The Log tab displays the log of all messages emitted by the Broker or client applications during visualization Since messages are collected from applications executed in different processes the order in which the messages are displayed should not be taken as an accurate representation of the order in which the messages have actually been emitted wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 E Broker VTS 21 03 2010 22 03 2010 23 03 20 g v KK ii 9 Real time v G ur awos2 oon gt BO Log Clients Receivedpackets Sent packets Launcher 2dWin is ready LauncherCelestia is ready Start D users jee vts Release VTS 2 3 Beta Vts WindowsNT 3172M Apps Celestia bin celestia exe Parameters title 1 Celestia dir D users jee vts Release VTS 2 3 Beta Vts WindowsNT 3172M Apps Celestia bin cor Start D users jee vts Release VTS 2 3 Beta Vts WindowsNT 3172M Apps 2dWin bin 2dwin exe Parameters D users jee vts Data CubeSat CubeSat vts 0 QGLShader link Vertex shader s linked fragment shader s
228. set of entities to visualize and in the client applications launched to visualize them Applications can be configured in the VTS configuration utility each instance of an application separate from the others WY contigurateur w Celestia launcherCelestia Fichier projet Description Mission 5celestia celestiaVtsConf ini Vu w MyApp 4 launcherMyApp Config Applications Data Fichiers CIC Mod le 3D LC pmyapp uy idian Project configuration Upon startup of the visualization the Broker starts the launchers for each instance of its client applications configured in the project file Each launcher is passed the path to the project file and its application ID It handles the pre processing required to start its client application such as data conversion script generation file copy etc It then returns to the Broker the command line arguments to use when starting its client application The Broker in turn starts each client applications with its provided arguments wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Lj Z Configurateur i i Pr paration de Hum tc launcherCelestia sn Io l application H J u parati Se launcherMyApp ies 6 5celestia Ww
229. so WindowMode Window mode for the Broker Undocked DockedOnTop or Character Display modes in the Broker DockedOnBottom string user manual Collapsed Compact mode for the Broker window when undocked Boolean Display moaes in the Broker user manual AlwaysOnTop Broker window always on top of other windows Boolean Eee moaesiin ME Br ker user manual XPos X coordinate of the Broker screen position Integer YPos Y coordinate of the Broker screen position Integer wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Attribute Description Format unit See also Width Width of the Broker window Integer Height Height of the Broker window in full display mode Integer ActiveTab Tab number of the default Broker tab in full display mode Integer Sample BrokerOptions tag lt BrokerOptions WindowMode Undocked Collapsed 1 AlwaysOnTop 1 XPos 0 YPos 480 Width 640 Height 80 ActiveTab 0 gt 7 5 2 5 lt TimelineOptions gt Display parameters for the project s timeline The TimelineOptions tag defines the display parameters for the project s timeline i e the display modes for data files loaded in the timeline in the VTS configuration utility or Broker This tag has no attributes Refer to the Timeline section in the Scenario in VTS chapter for more in
230. spaces tabs must be quoted using double quotes e g field with whitespace 3 Literal quotes in message fields must be escaped with a backslash e g field with literal quotes 4 Literal backslashes in message fields must be escaped with an additional backslash e g C path to lfile 7 3 2 Connecting to the Broker In order to engage communication with the Broker client applications must connect to a socket server setup by the Broker e By default the Broker server port is 8888 In this case the launchers are started with no specific port option e If VTS is configured for open ports scanning the launchers are started with a serverport lt portNum gt option in command line 7 3 3 Messages received by the Broker This section describes the commands client applications may send to the Broker 7 3 3 1 INIT message connection to the Broker Once connected to the server client applications must sent the following initialization command to engage communication INIT lt Name gt lt ClientType gt ProtocolVersion Clientld The parameters for this command are described below Parameter Required Description Format unit See also Name Yes Name of the client Character string Time behavior of the CONSTRAINT or ClientType Yes client REGULATING Real time VTS Optional Synchronization protocol ProtocolVersion ync H Integer Integer default 1 0 version Optional Application IDs in Clientld auto attr
231. splay in the project timeline These files should not be referenced by the project inside lt Value gt tags since files referenced by the project are automatically displayed in the project timeline unless ignored Refer to the documentation of the lt File gt generic tag in the lt File gt CIC CCSDS file section for further information 7 5 2 41 States Project scenario The States tag contains a list of visualization states which compose the project scenario This tag has no attributes If present the States tag must contain at least one Instant tag see below at date 0 Refer to the Scenario in VTS chapter for more information Sample States tag lt States gt 7 5 2 11 1 Instant Scenario visualization state The Instant tag defines a visualization state from the project scenario It aggregates view properties for all client applications of the visualization Attribute Description Format unit See also Time Date of the visualization state Real number JD1950 Date formats in VTS Label Visualization state label in the project timeline Character string All projects using the project scenario must define at least one visualization state at date 0 This state holds the values for all client application initial properties and view properties at the start of the visualization Refer to the Client applications in VTS chapter for more information on initial and view properties of a client application Sample In
232. sssssssceseseessseses 6 3 4 1 Context menu 6 3 4 2 Cursor coordinates 6 3 4 3 Interacting with a satellite a 6 34 31 SatelliteloGk 3 initio eret rede she deer hod ed AERE Eee easdasictesds eaa pe varie desee sksteacaneceeseachedechaates 6 3 4 3 2 Geographical coordinates ss 6 3 4 3 3 Moving IET TITIO es cete Recte Re i Decet excede de dec tinea ates eee turco dt a sedebit recent one see eae 6 344 UI cen ccmeee P wPQ M 6 3 4 5 Interacting With events iie ek ERREUR DUREE LEER ere GRE einen EU Ie Ra EEEa YD Fue ue FIL de PH a EA XY RS AX RENTEN SR CER ERR RR GER NEUE 6 3 5 T CRNICAI c wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 14 11 2014 Reference VTS MU 69 635 1 Rotation model ssie e E a E NE EE en eS 6 3 5 2 Central body texture 6 4 CELESTIA USER MANUAL 6 4 1 Integration with VTS 6 4 2 Navigating in Celestia tte e e PY YR REE ETE EX E EYE RAE RE Ree dE RAE KE e FE PEE ET TRE EE EET o VR RR TE YRXR EPA FEET TR ERE 129 6 4 3 Specific application parameters in VTS n es 129 7 PLUGIN DEVELOPMENT
233. stant tag Instant Time 21994 513 Label Start of apogee thrust 7 5 2 11 1 1 lt AppState gt State properties for a client application The AppState tag contains a list of properties for a specific client application Each Instant tag must contain as many AppState tags as there are client applications in the project wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Attribute Description Format unit See also Id Client application ID Positive integer Application IDs in VTS The application ID must match the one defined in corresponding Application tag see above Sample AppState tag AppState Id 1 gt lt Command s Application property The Command tag defines a property command for a client application This command sets the value of an application property Attribute Description Format unit See also Str Property command Character string Synchronization protocol for VTS clients The actual value of the command depends on the client application it is intended for and on the property to be set Refer to the Client applications in VTS and Synchronization protocol for VTS clients chapters for more information Sample Command tag lt Command Str CMD PROP equatorialgrid false gt 7 5 3 Generic tags 7 5 3 1 lt Sensor
234. t lt Value gt lt Angle gt Rotation angle wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 The Angle tag defines the angle of rotation for an axis and angle orientation This tag has no attributes It must contain a Value tag Sample Angle tag Angle lt Value gt Rotation angle value The Value tag defines the value of the rotation angle data Refer to the documentation of the lt Value gt generic tag in the lt Value gt Data value section for further information For a fixed rotation angle value the Fixed tag must contain a character string of one real number defining the rotation angle The rotation angle is expressed in degrees Sample Value tag lt Value gt lt Fixed Data 45 00 gt lt Value gt 7 5 3 4 2 4 lt Direction gt Orientation as a direction The Direction tag defines the orientation of an object along a direction vector This tag has no attributes It must contain a Value tag Refer to the Orientation of objects in VTS chapter for more information Sample Direction tag lt Direction gt Value Direction vector value The Value tag defines the value of the direction data Refer to the documentation of the lt Value gt generic tag in the lt Value gt Data value section
235. t Geometry gt Geometric properties section for further information Position data for a body is expressed in kilometers 7 5 2 7 1 6 GroupGroundStations Ground stations of a body The GroupGroundStations tag contains the list of all ground stations on a central body This tag has no attributes Sample GroupGroundStations tag GroupGroundStations wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 lt GroundStation gt Ground station The GroundStation tag defines a ground station of a central body Attribute Description Format unit See also Name Ground station name Character string Sample GroundStation tag lt GroundStation Name Toulouse gt lt Prop2d gt 2D properties of a station The Prop2d tag defines the 2D properties of a ground station i e its icon 2D views Refer to the documentation of the lt Prop2d gt generic tag in the lt Prop2d gt 2D properties section for further information lt LatLongAlt gt Coordinates of a station The LatLongAlt tag defines the geographical coordinates of a ground station latitude longitude and altitude on its central body This tag has no attributes Sample LatLongAlt tag lt LatLongAlt gt lt Value gt Coordinates value of a station The Value ta
236. t e g for solar arrays The coordinates of the center of rotation are 1 0 0 The object is rotated 30 around an axis located at the end of the red X axis and directed along the green Y axis Note that this rotation axis is not displayed on the diagram hence the object appearing as if translated and not only rotated due to the rotation center being offset 3 6 4 6 Case 6 translation and offset rotation e Position X21 Y 0 Z 0 e Center of rotation X21 Y 0 Z0 e Axis of rotation X20 Y21 Z 0 e Angle of rotation 30 This example adds a translation of 1 meter along the X axis on top of the transformations of case 5 The diagram confirms that rotation occurs before translation 3 7 BACKWARDS COMPATIBILITY IN VTS 3 7 1 Backwards compatibility of project files cS Principle VTS features backwards compatibility of its project files This means that project files from an earlier version of VTS will still be read correctly by newer versions of the toolkit However they will always be saved in the most recent file format if they are modified This mechanism is available from VTS 1 1 onwards 3 7 1 2 Compatibility table From revision Toolkit version Revision tag From r3829 onwards 2 6 project wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS
237. t application e Apps o Celestia bin Ccelestia exe JauncherCelestia exe CleanerCelestia bat README cCelestiaVtsConf ini icon png 7 1 4 Application launchers A client application launcher in VTS is in charge of preparing the visualization for a client application To this end it may pre process visualization data generate scripts copy files etc and lastly return the command line arguments for the client application The only mandatory output of a launcher is the command line arguments to be passed to its client application 7 1 4 1 Input parameters for a launcher Launchers are all started by the Broker in a similar way i e with the following command line arguments e Absolute path to the project file e Client application ID which may be used to identify the application in the project file useful when several instances of the same application take part in the visualization wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 7 1 4 2 Preparing the client application This phase may not be required The launcher may need to do some processing to setup the environment for its client application This may include altering configuration files for the application converting project data files into application specific f
238. t file and attach it to a project satellite This command has the same syntax and parameters as the LoadFile command received by the Broker Refer to it for details LoadFile commands may be sent upon connection of a new client to instruct it to load mission event files which were loaded by other client applications before it joined the visualization 7 3 4 2 3 2 ReloadFile command The ReloadFile command instructs client applications to reload an already loaded CIC CCSDS event file This command has the same syntax and parameters as the ReloadFile command received by the Broker Refer to it for details 7 3 4 2 3 3 UnloadFile command The UnloadFile command instructs client applications to unload and detach an already loaded CIC CCSDS event file from all project satellites Events from this file should no longer be attached to any satellite This command has the same syntax and parameters as the UnloadFile command received by the Broker Refer to it for details 7 3 4 2 4 CMD CAMERA commands CMD CAMERA messages instruct client applications to change the visualization camera Only messages corresponding to cameras declared in the client application s INI file may be received These commands have the following syntax CMD CAMERA CameraName lt CameraParameters gt The table below describes available cameras wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 1
239. taData tag shows meta information about the project in a description field Attribute Description Format unit See also Description Project description Character string Sample MetaData tag MetaData Description Sample project 7 5 2 3 lt StartOptions gt Initial parameters for the visualization The StartOptions tag defines the initial parameters for the Broker at the start of the visualization Attribute Description Format unit See also TimeRatio Time ratio at the start of the visualization Positive real Time management in the Broker number user manual SysTimeSynced Synchronization of visualization time with system time Boolean Time management in the Broker Paused Pause time at the start of the visualization Boolean user manual Looped Loop playback for the visualization Boolean Time managementin the Broker user manual oe Minimize the Broker window at the start of the Minimized visualization Boolean R Hide the Broker window at the start of the Hidden visualization Boolean AutoClosed Automatically close the Broker once visualization has Boolean reached its end date Sample StartOptions tag lt StartOptions TimeRatio 100 SysTimeSynced 0 Paused 0 Looped 1 Minimized 0 Hidden 0 AutoClosed 0 gt 7 5 2 4 lt BrokerOptions gt Parameters for the Broker window The BrokerOptions tag defines the display mode of the Broker and some of its window parameters Attribute Description Format unit See al
240. tc wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 o If no number is specified then the given arguments will be passed on to all clients with the given name i e all instances of Celestia 2dWin etc o If an additional number is specified Celestia 1 PrestoPlot 3 etc then the given arguments will only be passed on to the n th instance of the application Examples broker project C Project CubeSat vts specificArgs 1 someOption broker project C Project CubeSat vts specificArgs Celestia url exampleUrl broker project C Project CubeSat vts specificArgs 2dWin 2 colorLayer The specificArgs arguments must be specified after the project argument on the command line 6 2 2 Start of a visualization When a visualization is started from the VTS configuration utility the Broker starts all the client applications defined in the VTS project During this initialization phase the Broker displays the Initializing message in the text fields of the time control area Time does not start flowing until all client applications have signaled they are ready Upon connection of the various client applications the Broker s tabs are populated with commands and information regarding these applications Visualization automatic
241. te properties The Label field displays the label of the current scenario state It can be modified The Date button opens a dialog to view and edit the date of the current scenario date However it is not possible to modify the date of the fictional initial scenario state The Application list displays a list of all client applications Selecting a client application in the list displays its view properties in the tree hierarchy to the right There are two types of view properties application parameters which describe global properties specific to the application and objects parameters which describe display properties of project entities central bodies satellites sensors etc for the application Each property has a label describing its purpose Clicking or double clicking a property s value to the right of its label opens an editor to modify the value e Properties with bold labels have had their values modified but not saved Scenario states for which at least one of their properties has had its value modified appear with an orange star in the timeline e Properties with italic labels have a unique value for the whole scenario Modifying their value automatically affects all scenario states Each property can be reset to default by right click In the Broker this action can lead to a message to the concerned application The table below describes the wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manu
242. ted object Sol Earth CIC SAT_ref CIC SAT Satellite labels 4 true Solar system scale x1 o Window menu false Window text 4 true Ambient Light 30 4 Objects parameters 4 Earth Body scale x0 9 EME2000 inertial frame axes false Body frame axes false P Planetographic grid false Terminator false 4 CIC SAT Component visibility 4 true Satellite scale x 2e 06 Orbit path 4 true 7 maroon A imul orci GG lum ie Fi lei Timeline View Properties 3D Cameras Applications Server Client application view properties The contents of this tab are described in the View properties editor section of the Scenario in VTS chapter 6 2 10 Events tab The Events tab allows controlling the visibility of mission events in client applications that support them wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 r Broker VTS amp K li 9 Real time P B 2 o E A UTC 2012 12 12 09 44 55 Applications All satellites CubeSat CubeSat 1 pum V X ALARM MX u MX a loris 4 E MISSION 0 FO 9 ll lt gt COME MO HOM Inst T 44 0 m lt gt ModeAoCS MOM HOO m SModeAOCS WI 23 HO 0 z otF ive e iv 6 0 M PASS 9
243. texture Fixed texture file Timed texture file OMERE TrappedElectrons_AE8 Max Diff 0 1MeV_IGRF 2012 1000km 0 1 x0 1 png Browse Preview Fixed texture The texture is defined by an image file in the project folder wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Timed texture Texture properties Built in texture Fixed texture file Q Timed texture file Data EARTH TEXTURE CYCLIC TXT D Browse j v Cyclic texture Epoch 3p1osp 0 MID 33282 0 000 e UTC 1950 01 01 00 00 00 Period 2 000000 days 4 Preview Textures plancton 04 jpg JD1950 21994 356 MJD 55276 30758 400 cal UTC 2010 03 21 08 32 38 Timed texture The texture is defined through a CIC CCSDS file in the MEM format This file contains the relative path in the project folder to the texture to use with regards to the current visualization date Several parameters must be defined for a timed texture e The MEM timed texture file containing STRING data of dimension 1 e The cyclic acyclic property of the texture Notes e The Preview area allows navigating through the textures of the MEM files either with the navigation buttons or by directly specifying a date wiki kiwi Documents Documents_CNES V
244. the Server tab of the Broker wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Date 14 11 2014 Reference VTS MU 69 Bitrate 1680 Kbps Movie length 00 00 19 Recording FPS 17 1 Recording information e Bitrate the current movie bitrate e Movie length the current length of the recorded movie e Recording FPS the current record framerate this does not affect the output framerate 6 2 15 Other interactions The Ctrl Shift C keyboard shortcut copies to the clipboard the full path to the VTS project file 6 3 2DWIN USER MANUAL The 2DWin client application displays a planisphere of the project s main central body in plate carr e projection 6 3 1 Configuration in the VTS configuration utility The main central body displayed in 2DWin is the first central body defined in the project hierarchy in the VTS configuration utility Refer to the Configuring a central body section in the VTS configuration utility user manual chapter for more information Only satellites attached to this main body will appear in the 2D view 6 3 2 Specific application parameters in VTS When adding 2dWin as a VTS client application some parameters can be set by clicking on the 2dWin entry in the VTS project tree wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Publi
245. the problem persists with an Intel chipset it may be because the chipset is incompatible with the rendering of sensor swath items Sensor swath must then be disabled for the project see http www opengl org wiki FAQZWhy is my GL version only 1 4 or lower 3F wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 3 GENERAL CONCEPTS 3 1 CONVENTIONS IN VTS As in every software VTS sets up conventions for some of its elements This page lists those conventions 3 1 1 Frames In VTS frame axes form an orthonormal direct basis 3 1 2 Quaternions The first element of a quaternion corresponds to its scalar part 3 2 DATE FORMATS IN VTS 3 2 1 Formats list Date format Abbreviation Example ao 2011 Bonn Usage in VTS e Synchronization protocol CNES Julian day JD1950 22416 6819444444 0 Yes e Display e Project file CIC CCSDS files m julian jp 55698 58920 000000 33282 Yes e Display e Project file Calendar date ISO 2011 05 17 16 22 00 NA Yes e Display forced UTC ont 17116 22 00 0007 NA yes e Project file Celestia Julian SL 2455699 181944 2433282 5 No e Celestia data files day The internal date representation in VTS uses the reference date of JD1950 and is expressed with two fields for days and seconds like MJD VTS use
246. tion states e g momentarily switching to sensor view when an acquisition occurs on some instrument VTS offers two tools to edit a project scenario the timeline and the view properties editor In the VTS configuration utility these tools are available in the Scenario Editor tab wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 01 Date 14 11 2014 Reference VTS MU 69 Event Type Editor 8899 9 09 07 06 30 09 07 07 00 09 07 07 30 09 07 08 00 1 Scenario m 2 CIC Sat POSITION VELOCITY TXT Pm 3 CIC Sat SATELLITE ECLIPSE TXT Fa 4 CIC Sat SATELLITE MODES bt FE RB 5 CIC Sat SATELLITE CONSUMED POWERbt 4 6 CIC Sat SOLAR ARRAY CURRENT TXT Aa 7 CIC Sat BATTERY DOD TXT Aa 4 r l lt D State editor Label D but simulation Application Property name Value i 0 Celestia Equatorial grid V true _ e Camera parameters Double click to view edit ne 1 2dWin Selected object Sol Earth CIC SAT ref CIC SAT Satellite labels F true i 2 PrestoPlot Solar system scale x1 iei Ambient Light 30 4 Objects parameters 4 Earth Body saie on os EME2000 inertial frame axes raise Body frame axes false Planetographic grid false a 2 IE kalan Scenario editor in the VTS config
247. to all previous scenario states e The Propagate selection to previous state button copies the selected view properties to the previous scenario state e The Propagate selection to next state button copies the selected view properties to the next scenario state e The Propagate selection to all next states button copies the selected view properties to all next scenario states e The Propagate selection to all states button copies the selected view properties to all scenario states These actions allow easily setting a property value for multiple scenario states Several properties can be selected by holding down the Ctrl or Shift keys while selecting the properties to propagate If a tree node is selected all properties beneath it will be propagated In the Broker the view properties editor also offers the same buttons as those available to save states in the timeline 3 14 MISSION EVENTS IN VTS Mission events in VTS are timestampped punctual events attached to visualization entities Currently events may only be attached to satellites Events are displayed in the project timeline and in compatible client applications Currently the only standard VTS client application with events capability is 2DWin An event is defined by its event type and timestamp Text metadata may also be attached to an event 3 14 1 Event type The event type is a category describing the event that occurs at the dates of instances of this type For exa
248. to start minimized in the taskbar e The Auto close at end date option allows the Broker to automatically close once the visualization reaches the end of the time range 6 1 4 2 Configuring an entity Several entities in the project rely on some common parameters which are described in the current section Parameters specific to an entity are described in the sections concerning their respective entities 6 1 4 2 1 Position and orientation of an entity This section describes the common mechanisms used for defining the position and orientation of an entity Details specific to the various entities such as the units used are described in their respective sections For further information on how position and orientation are defined refer to the Position of objects in VTS and Orientation of objects in VTS sections For further information on the available data sources refer to the Data sources in VTS section 6 1 4 2 1 1 Fixed position Position Stream Constant 9 File 9 X km 0 Y km 0 Z km 10000 Fixed position wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 e The radio button in the Constant tab selects a fixed position for the current entity Note that in the EME2000 reference frame a fixed position is usually meaningl
249. toolkit can by started by double clicking the startVTS exe file under Windows or by executing the startVTS command under Linux This displays the main window of the VTS configuration utility It allows creating a project by setting up the entities to be visualized satellites sensors ground stations and client applications If the launcher is executed from the command line with the project lt ProjectFile vts gt argument the VTS configuration utility automatically loads the given project on startup 5 1 2 Starting the visualization from the command line The visualization can be started automatically from the command line via the launcher The Broker then opens and starts the visualization without going through the VTS configuration utility In batch mode the following arguments are mandatory e batch instructs the launcher to start the Broker directly e project ProjectFile vts specifies the project file to load The path can be either relative or absolute Other command line arguments for the Broker can also be given in batch mode Sample command line startVTS exe batch project C Project CubeSat vts On Linux only the version of VTS can be obtained with the command startVTS version wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Re
250. top a client click the red Stop button o To restart a stopped client click the green Play button A checkbox allows specifying whether or not to execute the client application s launcher before restarting the application in order to update the client s data o To remove a dynamic application from the list click the red cross button The client will be stopped if it is currently running wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Broker VIS OO GG M n S nam y ioo 20325 G wei 2010 03 21 000 QE Project Applications 2dWin cetestia 1 v m 2 Celestia oo Z Cosmographia PrestoPlot s Drop an application icon here Timeline View Properties 3D Cameras Applications Server Starting a client by drag and drop 6 2 12 2 Promoting a dynamic application into a project application Dynamic applications can be promoted to project applications by drag and dropping their icons into the Project Applications list When closing the Broker a pop up dialog will offer to save the changes made to the VTS project If changes are saved the promoted client will appear in the list of project applications in the VTS configuration utility and its view propertie
251. tructs the Broker to close the visualization session All client applications are disconnected clients started by the Broker are terminated and the Broker itself exits This command has the following syntax CMD SERVICE AUTOCLOSE 7 3 3 3 2 2 Request replies These commands are sent in reply of requests from the Broker Refer to the Requests paragraph below for more information on the various Broker requests StoreCommand command The StoreCommand command is sent in reply to a SaveState or SaveWindow context save request It instructs the Broker to store a view property command for the application into the current scenario state This command has the following syntax CMD SERVICE StoreCommand ViewPropertyCommand wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Parameter Required Description Format unit See also di a Le CMD PROP commands ommand for setting a view property of the aracter ViewPropertyCommand Yes application string CMD STRUCT commands Commands stored through a StoreCommand command will be sent back to the client application when the scenario state they are stored in becomes active For more information on the project scenario refer to the Scenario in VTS chapter SaveStateFinished command The SaveStateFinished com
252. uaternion Euler angles Axis and angle Direction Azimuth and elevation Each of these orientation modes can be configured to use a fixed value a sampled value in a CIC CCSDS data file or a value stream as described above for the configuration of the position 6 1 4 2 2 1 Orientation by quaternion Orientation Quaternion Euler angles Axis and angle Direction Quaternion Constant File Stream 9 Q0 1 000000000 Q1 0 000000000 Q2 0 000000000 Q3 0 000000000 Orientation by constant quaternion e An orientation by quaternion is defined by its four components Q0 Q1 Q2 and Q3 wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 6 1 4 2 2 2 Orientation by Euler angles Orientation Quaternion Euler angles Axis and angle Direction Euler angles Constant 9 File 9 Stream 9 Z first rotation 0 000000000 X second rotation 0 000000000 Z third rotation 0 000000000 Orientation by Euler angles e Anorientation by Euler angles is defined by a sequence of three rotations as follows Z X Z 6 1 4 2 2 3 Orientation by axis and angle Orientation D Quaternion Euler angles 9 Axis and angle Direction Axis a Constant 9 Fie Stream X 0 000000000 Y 1 000000000 Z
253. ue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 e the entity s icon configured in the project e animage icon file located inside the project folder preferred dimensions are 32x32 see the 2D icons and textures section of the Data description for VTS projects chapter for supported file formats 6 1 5 3 Configuring satellite specific event type decorations When the Toggle Edit Entity Decorations Mode button is toggled the event type editor switches to advanced mode In this mode event type decorations specified the All satellites column are applied by default unless satellite specific decorations are set in the per satellite columns of the hierarchical view Appearance u j Editing PASS KRU TC EMISSION END 2l Type Default CubeSat 1 CubeSat2 t1 ALARM Ee MISSION 7 Customized OEF Shape layer 1 4 PASS vu KER TM 4 KRU O PASS TC_EMISSION_BEG n TC_EMISSION_END e 5 Parameters TMTC_AOS TMTC_LOS Shape Circular target M ZERO_DEG_AOS ZERO_DEG_LOS E mma NPL E Fil shape SAS STH TCLOG Entity based event type decorations Note All custom satellite specific decorations will be lost when switching from advanced to basic mode When loading a VTS project with satellite specific decorations the advanced mode is automatically selected 6 1 6 Settings dialog General options independent from the project can be set in the File Sett
254. ue mode also AimContourVisible Boolean Display of the sensor footprint intersection mie MANUAL Sensor footprint false or true with the central body AimTraceVisible Boolean Display of the sensor swath trace true MANUAL Sensor swath false or true 7 3 6 2 4 POI properties Property name i perty Parameters format Description rst oe a Ges also Property label unit value mode PoiVisible Boolean i Display the point of interest true MANUAL s SRE POI visibility false or true wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Property name i Parameters format Description pun Propagation See also Property label unit value mode PoiTextVisible Boolean i Display the label of the point of inia MANUAL ns and ROls in Text visibility false or true interest 7 3 6 2 5 ROI properties Property name i Parameters format Description pics m Gas leo Property label unit value mode RoiVisible Boolean i ou Display the region of interest true MANUAL e angels ROI visibility false or true RoiTextVisible Boolean Display the label of the region of MANUAL POIs and ROIs in Text visibility false or true interest VTS T 3 7 Real time VTS 7 3 7 1 Time synchronization with an external time source By default the VTS Broker regulates the flow of visual
255. ult iei eta tee ear pan erasa aai ER esee Phat e eua Eo ta ERA Eo Eee e Nena ERR esa ao Rea e Ra Trad EE aE Raat e SE aa 28 3 6 4 1 Case 1 no modification nennen nenne nnne nnne nennen enne nnne nnn ennt sies enn senes nennen inner nnn sinn rennen nnns 28 3 642 Case 2 single translation uec eim ELE eR nent sienne dd chansevacceuuced otii RC RR RR X REUS NER Fe REN QUERN Reste 28 3 643 Case 3 single fotatiOh oi eroi eret ia e ert exceeds reisen cad Ege a ven none aten genres ne Ans EVER uer ers aide si gei da 29 3 6 4 4 Case translation and rOtatiori uicsc rrt ro tenter rra eei rer ure ER NT e PEE LY e EN EYEESEERAR PEE LE RE eV Le Coe esse eL E see UE 29 3645 Case offset rotations eee iei te o iicet pee te aU o a pe Ee WEN ERR fur este docete dea sated eats Ps aep E OES gute se ade vi 29 3 6 4 6 Case 6 translation and offset rotation sise 29 3 735 BACKWARDS COMPATIBILITY IN VTS 35 iiic e to se ertet eau a seg e a repu ee ee ua PN VRIR cantar disseuaencassacdeudesosiasne Ren un e alt eae 30 3 7 1 Backwards compatibility of project files 30 cw L1 PNGP Esnie 30 34 12 Combpatibility table netter iere teen rites recede iste EAE n bc petet sera ri tetas egi 30 3 7 2 Upgrading AERE 30 cp Leider 30 3 8 1 DEFINITIONS CERTITUDINEM 31 3 8 2 Central body of n Object eei Te ad FED n RET RR YET ere use eI xo ER ee Ve
256. uncher Lua e Interface scripting language in Celestia Used by the VTS plugin for Celestia Java e Language of the Orekit library used by the orbit propagation tool e Compilation and deployment scripts Bash e Some basic client application launchers DOS Batch e Some basic client application launchers wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11
257. uration utility In the Broker they are available in the Timeline and View Properties tab Parts of the timeline displaying dates and the project scenario are always visible in the Broker no matter which tab is currently selected 3 13 1 Timeline The timeline displays and allows selecting creating and removing visualization states in the project scenario It also displays the contents of the project s data files and event files E Broker VTS e less laMi S ram 1 09 07 16 00 00 03 07 16 0 amp 0 09 GI 1s0 2016 07 09 orsoseurc j9 ON A P 9 CIC Sat POSITION VELOCITY TXT p CIC Sat SATELLITE ECLIPSE TXT CIC Sat_SATELLITE_MODES brt p CIC Sat SATELLITE CONSUMED POWER bt CIC Sat SOLAR ARRAY CURRENT TXT Fi CIC Sat_BATTERY_DOD TXT PE D ui BB Uu hh WM ie g9 g9 9 9 O rile m r LC su PPR Timeline View Properties Events 3DCameras Applications Server Timeline in the Broker wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 The timeline can be zoomed in out using the mouse wheel and panned by drag and dropping when the mouse cursor has the shape of a hand This allows for great flexibility during visualization of a project since the timeline can
258. vents gt generic tag in the lt Events gt Events section for further information This tag may only contain Decoration tags It may not contain File tags since events must be attached to an entity 7 5 2 9 lt IgnoredFiles gt Ignored files in the project timeline The IgnoredFiles tag contains a list of CIC CCSDS project files which should not be displayed in the project timeline This tag has no attributes Sample IgnoredFiles tag lt IgnoredFiles gt 7 5 2 9 1 lt File gt Ignored project file in the timeline The File tag defines a CIC CCSDS project file which should not be displayed in the project timeline Only files referenced by the project inside lt Value gt tags may be specified here wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Refer to the documentation of the lt File gt generic tag in the lt File gt CIC CCSDS file section for further information 7 5 2 10 AdditionalFiles Additional files in the project timeline The AdditionalFiles tag contains a list of CIC CCSDS files to display in the project timeline This tag has no attributes Sample AdditionalFiles tag lt AdditionalFiles gt 7 5 2 10 1 lt File gt Additional file in the timeline The File tag defines a CIC CCSDS file to di
259. ying the 3D mesh using specialized 3D software 6 1 4 4 5 Position and orientation of a satellite The position and orientation of a satellite can be configured as described in the Position and orientation of an entity section They are expressed in the EME2000 reference frame inertial equatorial earth centered The unit for position values is the kilometer 6 1 4 5 Configuring a sub component A sub component is a part of a satellite detached from the main component A satellite is composed of a main component and may be composed of any number of sub components A sub component itself may be composed of any number of sub components Sub components can be animated in the local frame of their parent component The definition of a sub component is quite similar to the definition of the main component of a satellite 6 1 4 5 1 General properties of a sub component The general properties of a component define its name in the project hierarchy This name will be used as a unique identifier during visualization by commands interacting with entities 6 1 4 5 2 3D properties of a sub component The SD properties of a sub component define its appearance in 3D views They are similar to the 3D properties of a satellite Refer to the 3D properties of a satellite for further information e The coordinates of the rotation center are expressed in the satellite s frame in meters 6 1 4 5 3 Position and orientation of a sub component The position
260. zation of motion for the whole solar system The Solar system scale property in the View Properties tab of the Broker allows dynamically setting the scale factor of the whole solar system Note that the Sun is not affected by this scale factor Scale factors can be set for the whole solar system and for independent central bodies within in e g to decrease the size of the gas giants wiki kiwi Documents Documents_CNES VTS MU 69 VTS MU G 69 SPB 5 1 User Manual VTS 2 Public doc 24 11 14 14 11 Spacebel SAS VTS MU G 69 SPB VTS Issue 05 Date 06 03 2014 Rev 01 Date 14 11 2014 Reference VTS MU 69 Fichier Navigation Temps Rendu Vue Signets Aide Scaled solar system The scale factor editor in the view properties editor allows editing the scale factor as follows e by directly entering a numerical value in the text field e by moving the slider left right to increase decrease the factor e by setting the factor to 1 using the x1 button e by setting the factor to 10011000 using the x1e5 button satellites only 3 13 SCENARIO IN VTS The VTS project scenario consists of a set of visualization states applied at precise instants of the visualization These states hold visualization properties specific to each client such as position and orientation of the camera visibility of satellite components visibility of the equatorial grid etc Special behavior can then be triggered at precise dates through visualiza

SPACEBEL SAS VTS USER MANUAL VTS 2

Contents

Download Pdf Manuals

Related Search

Related Contents