Vimpacct tool v1.0 - University of California, Irvine
Contents
1. order which the messag lements appear is not important lt comment gt message opcode 001 type request size 0 reply 801 family 8 gt lt message opcode 801 type response size 2 family 8 gt message opcode 003 type request size 0 reply 803 family 8 gt lt message opcode 803 type response size 0 family 8 gt lt message opcode 010 type request size 0 reply 810 family 2 gt message opcode 810 type response size 16 gps 1 family 2 gt messages Profiles further expand to the following format profile index 100 comment The profile element contains subelements that define the messages that are in use during a waypoint leg and the timing parameters used when sending those messages Each profile element must include an index attribute with a unique integer value This attribute is referenced by the msgprofile element which is part of a waypoint The index attribute must be an integer but there is no requirement that these numbers be in order and the list of profile numbers can contain missing values Subelements in a profile can be one of two types include and msgtiming There can be any number of either type of element included The msgtiming element defines attributes that control how many of and how often messages with the given opcode are sent The interval attribute d2. User Manual Vimpacct tool v1 0 Jiwon Hahn Dexin Li Qiang Xie Dept of Electrical Engineering amp Computer Science University of California Irvine CA 92697 2625 USA jhahn dexinl qxie uci edu December 15 2003 Contents 1 Introduction 3 2 An Overview of Vimpacct 6 I User Manual 7 1 IS A RR eom IER S Rupee NECRS Nocte pe Pt ent 8 2 Input Format 3 zc dobrd amp omgcveu xau ebbe ele Stee NEUE pes 10 2 1 Application Model i s oa e se comp RR OUR RUD por RR 10 2 2 System Model 2 3 pd a A A e a SR ale a ee ae 15 3 Control Panel s 23s a ls idea A AE de a Sie MR oe eh a 19 4 Main Window so sg vede a a a as E EE 21 5 Component Editor c des BRP re Ba Pk Ends SOU OE UE OS EP ORS Reise 23 5 1 MENU functions i Siw RO UR Se Hee BAe SS RR ET 23 5 2 Editing the Component List es 23 5 3 Editing Power Modes s iodo e A A ee RU 24 5 4 Editing Mode Transiti0ns 22e 24 6 Policy Generation and Simulation o 26 6 1 Preparing the input files e e 26 6 2 Start RUDNINE 204 45 rs a ORT eee fe HP a p en oe 26 7 Power Command Dispatch eee 27 8 Interactive Simulation Playback le 28 8 1 Main Window During the Play Back o a 28 8 2 Real Time Simulation e 29 8 3 Step Simulations scudo te es Gee bye eg Eel Ge ee 31 8 4 Animation only Simulation e 33 8 5 LOMO VO gt edb tnd s mee ER
3. ai Blackpower 2 di Blackpower 3 Black Proc 3 Black Proc 4 Blackpower 4 ai Black O Main Power As Red Proc 1 v Red Proc 2 ncryption Red Proc 3 M Red Proc 4 y Red VO Redpower Time 43 200 sec Distance 37637 km PA Status PAZ PAS PAS PAI 42 339 91 958 04000 km PA Power Consumption Level dBW 0 0 0 10 0 20 0 30 0 40 0 50 0 60 0 70 0 Time Figure 4 The Main Window Display during Playback 8 Interactive Simulation Playback Interactive Simulation Playback allows the user to observe the simulation in controlled granularity The play back is controlled by the toolbar on top of the main window as shown below and the simulating wheel on the control panel Fig 1 Real Time Step Simulation Simulation Profile Zoom l l P uOoK t 64 aa4 Ht L l Animation only Exit Simulation We will first explain how to interpret the main window display during the play back then explain the usage of each group of controls 8 1 Main Window During the Play Back Fig 4 shows the main display window during the simulation playback As introduced in Section 4 it shows the mission animation mode simulation PA and mission status and system power profile frame inside the quadrant In the Mission Animation frame shown in Fig 5 the JTRS object moves during the mission and the 28 Figure 5 Mission Animation during Playback communica
4. 0000 0 00000 km PA Power Consumption Level dBW 20 0 20 0 20 0 20 0 000 X Visual IMPACCT DDES KKCON SH ARM GB Aui ime PA1 Transceiver 1 Modem 1 gy proc 1 Blackpower 1 Red Proc 1 PAZ Transceiver2 Modem 2 Blackpower 2 Black Proc 2 P Red Proc 2 PA3 Encryption Transceiver 3 Modem 3 Black Proc 3 Blackpower 3 Red Proc3 j amp 3 m mE Transceiver4 Modem 4 Blackpower 4 Black Proc 4 P Red Proc 4 BS X 3 Redpower Domain Controller GPS Unit Black O Main Power Red I O 40 200 sec Distance 37637 km PA Power Consumption Level dBW 00 00 20 00 00 00 06 99 Time Figure 9 Setting the Anchor Point 32 60006 000 X Visual IMPACCT File Tools Help PANDO KKCON SH AAE IA d PAI Transceiver 1 Modem 1 Blackpower 1 Black Proc 1 Paz Transceiver 2 Modem 2 Blackpower 2 Black Proc 2 PA3 Encryption Transceiver 3 Modem 3 Blackpower 3 Black Proc 3 PA4 Transceiver 4 Modem 4 Black Proc 4 Blackpower 4 Domain Controller GPS Unit Black YO Main Power Red O Red Proc 1 Red Proc 2 Red Proc 3 Red Proc 4 Redpower Time 43 273 sec Distance 37637 km PA Power Consumption Level dBW 00 00 00 00 00 00 00 00 Figure 10 Manual Simulation by Rolling the Simulating Wheel 8 4 Animation only Simulation Animation only simulation lets you observe the mission scenario at a glance Independent of system power m
5. As a quick Vimpacct splash disappears the Control Panel the small window on the left and the Main Display Window the large window on the right show up see Fig 14 Main Display Window consists of a simulation toolbar on the top and four frames underneath that display e Mission Animation e Mode Simulation e PA and Mission Status e System Power Profile Fig 15 shows the icons of the control panel that are used to speed up access to the tools The following subsections will reveal the functionalities of the corresponding tools 41 00OKX OOA X Visual IMPACCT Be Tois HP D DHSS KCN EEC E Amie TP 4 Control Panel rs P Mode Simulation Time 00 000 sec Distance 00000 km PA and Mission Status System Power Profile PA Power Consumption Level dBW PA Status um E poz E SS ee Paa Figure 14 GUI the Control Panel and the Main Display Window 006 File Tools Help Mission Load Component Load i 49 tj e Policy Generation Profile Simulation Profile Load E Power Profile View Energy Breakdow E ha A Y Report Generation Component Edit Program Exit System Power View Command Dispatch Simulating Wheel Speed Scaling Bar Figure 15 Control Panel 42 12 Using the tools Vimpacct offers various tools for optimizing simulating and analyzing energy consumption of a mission We will explain these tools in the sequential order which let you explore full
6. I OUI o 00 C co CO C9 CD 4 a ootoo SSonr 86 86 eE B6 eE B6 BB eE B6 86 86 BB eE B6 BB eE B6 B6 B6 RB 6 8 B eG BG B B B6 BG eG B6 06 BG 6 B6 BG B6 B6 BE B Figure 21 Executing power commands through a CORBA client 12 5 Editing Components You can simulate the system architecture with different parameters by modifying attributes of components If you are familiar with Python directly editing the component library file in a text editor may be easier and faster The Component Editor provides a graphical interface for general users see Fig 22 To open the Component Editor use the below icon or menu Icon File Menu Tools Edit A new window pops up and all the components are listed in the Component List box on the left side Double click a component and its power modes and mode transition information will show up in the middle and right frames You can then edit a mode by selecting an existing mode changing the field you want to modify and click the edit button You can also add a mode by filling in the fields and click the add button Similarly you can add and edit mode transition information see Fig 22 After editing the components you can save the component library by choosing File Save or File Save As 7 12 6 Interactively Playing Back Simulation Now let us go back to the main display window Fig 14 You will find the following toolbar on the
7. Loaded System Power Profile View By selecting the first icon menu in Table 3 a system view of power profile pops up as shown in Fig 17 a Channel Component Power Profile View The second icon menu in Table 3 will instantiate a new window entitled JTRS Power Profile Simulator as shown in Fig 17 b This is the profile view of the channels By double clicking a blue area of a channel another window will pop up showing the detail component power of the channel as shown in Fig 17 c In these window there are four icons on the top The following table shows the usage of each Icon Description a a e Export the displayed power profiles to an EPS file Close the window Zoom in the power profile within the same system component level Zoom out the power profile within the same system component level Energy Breakdown View By clicking the third icon menu of Table 3 a window showing a pie chart of system power breakdown will pop up Double click each portion in the energy pie chart to view the energy breakdown of a lower level as shown in Fig 18 44 eoe X JTRS Power Profile Simulator a System View eoe IX JTRS Power Profile Simulator Channel 1 87 0 rub LH LEL MI 417 208 do 8 ds E 2 ab 4b Channel 3 s O d annel 4 re Resources b Channel View 660 X JTRS Power Profi
8. VIMPACCT Control Panel VIMPACCT GUI Application Resource Power Power d Report Interpreter Editor Analysis Simulation 5 Generation E M er o Back end Resource ha Code Simulation Scheduler a A Library Generator Server Power 2 JL Instrumentation Policy A Resource Corba h Corba bh Handler manager Dispatcher Server g Figure 1 Block Diagram of Vimpacct Tool Flow 1 Tool Flow Fig 1 shows the tool flow of Vimpacct The top level partition of the functions is input front end and back end Here we explain these blocks following the flow of data The input to the tool consists of the Application Model and System Model Application Model captures the high level knowledge that is related to mission scenario System Model captures the architectural infor mation such as the parameters of the hardware resources and dependency among them Before starting the tool these inputs need to be captured in files in the format described in the following section Through the control panel of the front end the inputs are loaded Application Interpreter interprets the XML model into a schedulable format and the Resource Editor lets the user add delete modify parameters of the System Model Then the back end of Vimpacct performs scheduling policy handling and resource management Sched uler determines the task sequence with exact timestamp Policy Handler generates mission aware policies Resource Manager determines the power modes of eac
9. a message Power Model 7 SSS SpecC Simulation Server Terminal The system shell UCAV Unmanned Combat Airborne Vehicle 52 Bibliography
10. functionality of Vimpacct 12 1 Simulating Mission This subsection shows the sequence of using the tools related to the auto simulation of a mission By follow Step Icon File Menu Explanation 1 5 File Load Library Load the component library ie nycomplib py 2 File Load Mission Load the component library ie mission7 txt To find the library you should navigate to JTRS missionlib the mission this may take a while 3 ION Tools Policy Generation Generate power control commands Depending on the size of 4 Tools Profile Simulation Run the simulation on completion the system components and the system power profile will appear on the Main Window Fig 16 5 File Save Profile Save the simulation result as a user defined name for later use r gt 6 File Load Profile Load a pre simulated mission Table 2 Steps for Mission Simulation ing the steps shown in Table 2 you can simulate load save a mission In the meanwhile you can check the progress in the terminal window in which you started the GUI For example when the process of Step 3 is completed you will see a terminal message Mode transitions generated by DPMA Please make sure the previous process is finished before executing the next step The simulated power profile is generated after Step 4 and saved as result txt as default in JTRS temp 12 2 Viewing Results The result of simulation is
11. mission the policy generation may take a while When it shows Mode transitions generated by DPMA the process is completed Once the policy generation is completed the mission simulation can be started The power commands are sent to the SpecC simulation Server for power simulation Some text messages are printed out on both the client side and the server side Once the mission simulation is done the system power profile appears on the Main Display Window 26 7 Power Command Dispatch We can send the generated power commands to a virtual platform for execution The CORBA is used as the common interface between the power manager and the virtual platform The CORBA server is written in C with a Python wrapper that interacts with a graphic user interface as the virtual platform The server receives the power commands of individual components from the client execute the commands on the server and displays the power mode changes on the graphic user interface The CORBA client is written in Python It reads a static power schedule from a file in which each power command is associated with a time stamp The commands are dispatched at the real time through the CORBA interface to the server The CORBA client identifies the server by the means of the Interoperatable Object Reference IOR which is produced on the server side once the server is started Therefore the IOR should be sent to the client prior to its dispatch of power commands T
12. power 4 0 para time 100 more than one power mode 16 ON OFF power 4 0 para time 0 STB ON power 2 5 para time 0 1 OFF ON power 4 0 para time 50 OFF STB power 4 0 para time 50 ts STB OFF power 0 1 para time 0 ON STB power 25 0 para time 100 ON OFF power 25 0 para time 0 STB ON power 12 5 para time 0 1 OFF ON power 25 0 para time 50 OFF STB power 25 0 para time 50 Macro Macro specifies the power consumption of macro modes Each macro mode is given a name such as MAIN in the below example and have the consisting components listed with the formula for calculating the macro power consumptions Macro MAIN dc gu MAIN 0 85 dc gu MAIN O 77 s tdeo g bi BLK ts md bp BLK 0 9 ts md bp RED ri rp eu URED Z0 9 s zio xp eu PowerSupply Das real de gutbi md ts rp rd ts bp md bp 0 97 u rpteu 0 9 ri dc gu bi 0 85 de gu bi 0 7 PowerSupply specifies the formula to calculate the power consumption of the power supply components as sh
13. to exploit mission awareness in power saving in addition to the well known workload driven schemes e the capability to run in situ hardware software co simulation by sending the generated power com mands to the hardware through CORBA interface Software Installation Required Packages Vimpacct is a cross platform software written in Python it runs on Linux Unix Mac OS and Windows platforms without changing the code For running the software with full functionality the following packages are required e Python v2 2 or higher with Tkinter support e omniORB v4 0 or higher and omniPRBpy v2 0 or higher e SpecC compiler v1 2 or higher However without omniORB and SpecC packages you can still partially run the tools omniORB is used for the execution of power commands through CORBA interface while SpecC is used for re compiling the power models for mission simulation The rest of the user guide assumes the usage of full functionality and therefore you should have all packages installed Python is pre installed on most Unix Linux and Mac OS platforms To check whether your python pack age has Tkinter support first invoke a Python interpreter by opening the terminal your system shell and type python Inside the interpreter type Tkinter Note that these commands are case sensitive If no error message appears then you have the Tkinter module installed Similarly to check whether you have omniORB installed type
14. 3 bes Transceiver4 Modem 4 Domain Controller GPS Unit e Black Proc 2 PBlackpower 2 Black Proc 3 Blackpower 3 f Black Proc 4 Blackpower 4 i p Black O Main Power Ex ex ET EE Encryption E Red I O Re 2 Proc 2 Red Proc 3 Red Proc 4 2 af Redpower Time 00 000 sec Distance 00000 km Power A TO en EOS De PA Status ED latitude 0000 0 Ps recs dE E IH IE IR URL N s ce E longitude 0000 0 BENE A A esee el bene A ntn PA Power Consumption Level dBW 150 0 0 0 10 0 20 0 30 0 40 0 50 0 60 0 70 0 Figure 11 Initial State after Loading the Mission profile is zoomed in three times Then the user can click on a point 10 101 sec to exactly set the anchor Fig 13 shows the global view of the main window Now the user can see the reason why there seemed to be a power glitch 1 there are many communication activities going on at the moment with three PAs on active power states 2 more than half of the system is fully ON Without zooming in it is hard for the user to set the anchor to the exact point where this state occurs 34 Time zoom 1 0 3 83 3 33 10 08 10 19 Time Power set anchor 0 10 091 10 101 10 11 Time Figure 12 The Usage of Zoom In 35 eoe X Visual IMPACCT DINSA KCIN e AQ A 5 Vai PAI Modem 1 Modem 2 Transceiver 1 Transceiver 2 Modem 3 Modem
15. 4 Transceiver 3 PA4 Transceiver 4 Domain Controller GPS Unit Power Time 10 101 sec Distance 41271 km M Black Proc 1 Black Proc 2 Blackpower 1 Blackpower 2 Black Proc 3 Plackpower 3 M Black Proc 4 w Black O Main Power Blackpower 4 M Red Proc 1 Red Proc 2 Encryption Red Proc 3 M Red Proc 4 Redpower A Red O PA Status Location latitude 42 040 longitude 91 634 altitude 00800 Km ccoo PA Power Consumption Level dBW 16 23 25 71 00 00 06 99 Figure 13 The Result of Fig 12 36 10 11 Time 9 Power Analysis Once the mission simulation is completed the information about power break down of channels as well as that of components are available for analysis 9 1 Power profile To obtain the power profiles choose Tools Select Component Power or click 8 on the Control Panel A new window of channel level power profiles shows up each track representing the power profile of a channel The user can zoom in or zoom out the power profile by clicking the corresponding buttons at the top of the window The user can double click a track to view a lower level component level of power profiles View more details of the profiles View less details of the profiles Generate an EPS file of the window Bi AS Exit the window 9 2 Pie Chart To obtain the pie charts choose Tools Display Profile me
16. Apple machine with Mac OS X Let us name your local host Host A and the server host Host B To set up the servers on Host B you need to download and unzip the same software package on Host B as you did on Host A Run the following command on the terminal of Host B to start the SSS cd SJTRS daemon python sc daemon py 10003 where 10003 is the default port number used by the SSS The message Waiting for connection that shows on the terminal confirms that the server is correctly set Run the following command on Host B to start the CPS 9 SJTRS corba mission services server An IOR interoperatable object reference appears in the terminal window and a GUI window of system diagram pops up At the moment being the naming service has not been implemented You need to manually pass the IOR to the client side Host A To do so on Host B run the following commands to copy the IOR file securely to Host A cd SJTRS corba scp mission service ior username HostA hostname SJTRS corba Each time you restart the CPS you need to pass the new mission service ior file to Host A You may have to explicitly kill the Python processes of the previous server execution by first finding the PID process ID number of python by typing on terminal ps then killing the process by typing kill 9 PID How to Use This User Manual This user manual consists of two parts Part I pro
17. E D din das Sate Ghee ae Bes 33 9 Power Analysis cn ei ea o Roe 9 vus Red oui RU Bee Ge Ae Be bees 37 9 1 Power profile 2 4 Ed Wu ESSA Ier ead ERES 37 9 2 Pie Chart uuu doeet ge dab xe Eau beber eui da oe 37 10 Report Generation soco 448 koh m RR es ld EN Rs 38 101 Report Eeatures x v e dunes merge ue BUSY ete Bundes 38 10 2 Report Format dove E a Ses uU ru Ree SIRE Aged 39 II Quick User Guide 40 11 12 Getting Started v4 oe ee a a ee i 41 Using the tools ss 2 a nok wom Rut A E Ros 43 12 4 Simulating MISSION ocu RR e RAP Su VUE 43 12 2 Viewing Results ie a ai a a E RE Oemee s 43 12 3 Generatins Repott 9 a Bd Pho AA ts RR E S 46 12 4 Executing PowerCommands 0 0000004 46 12 5 Editing Components sor 4 2 Ba sog sem eb OR RUE ad RA 49 12 6 Interactively Playing Back Simulation o 49 12 7 Debugging the Tool at Run Time llle 51 Chapter 1 Introduction Welcome to Vimpacct v2 0 a mission level energy simulator and analyzer The name Vimpacct stands for Visual Integrated Management of Power Aware Computing and Communication Technologies Vimpacct enables system level modeling optimization and validation of complex power aware embedded systems by offering e a generic power model for both digital and analog system components and application models that capture the environmental knowledge and the application specific scenarios e the capability
18. Generate Report Sort Command Save Report _j System power profile 3 Channel level power profile 4 Component level power profile _j System level pie chart Channel level pie chart View EPS Load Report Close Figure 20 The Generated Report 48 JTRS File Tools Help black_processor_state on PA_level standby black_io_state off red power state on transceiver state on P amp level tx lowband 1 PR level rx black io state on PR level standby black_processor_state off modem_state off red_power_state off PR level standby black_io_state off red_io_state off black processor state off modem state red pouer state transceiver state transceiver state modem state black io state red io state black processor state red power state transceiver state PR level rx PR level standby black_io_state off red io state off black processor state off modem state off red power state transceiver state modem state black io state red io state black processor state T M LM S MM ae 4m mood SSpS SSSSHRAR AUS e EET EN 222292 RARAS A M Y oss aa M A 2 ao m ey n M M BRS BEG eo tot Nm eo co co eo NEN ass ooo e CERES N eo eo 60 cO C Co cO bat Ov CN CN ON BEREE P POSEN PO PO PO QOO IO PO PO PO PO QOO PO OU E OL OX OI OQ OI ES E ES IE O N OX OX OO
19. Open the component editor C12 fal File Exit Exit the Program Table 1 Control Panel Functions 20 AAA X mission7 txt preso corn ce EMS cH v e gt Sm ums 89 j Transceiver Modem Slack Proc 1 Blackpower 1 Red Proc 1 Gg a e 3g e Transceiver 2 Modem 2 Blackpower 2 Black Proc 2 PA3 Transceiver 3 Modem 3 Blackpower 3 Red Proc 3 em i a eo d M Transceiver 4 Modem 4 Black Proc 4 Blackpower 4 Red Proc 4 ob te CJ d Domain Controller GPS Unit Black YO Main Power Redwo Redpower Red Proc 2 Cm Encryption System Power Profile m E y i 40 0 50 0 Figure 3 Main Window of Vimpacct Tool 4 Main Window Fig 3 shows the main window of Vimpacct It consists of Simulation Toolbar on top and four frames that consist of Mission Animation Mode Simulation PA and Mission Status and System Power Profile These frames are tightly coupled In other words change of status in one frame applies changes in all other frames also This window is utilized for visualizing the simulation and thus is related to the interactive play back rather than back end auto simulation which will be explained thoroughly in Section 8 Here we briefly introduce their usages Simulation Toolbar that consist of 11 control icons is used for controlling the interactive simulation play back Mission Animation frame shows the high level scenario view of a mission
20. The background consists of four possible places of the communicating objects land sky water and space The communicating objects are base stations JTRS objects possibly UAVs ships and tanks and satellites During the simulation play back these objects animate to show their location distance and the communication activities Mode Simulation frame shows the layout of the system architecture In this window all the power man ageable hardware components are displayed and they change color during the simulation play back Different colors specify the power mode of the components PA and Mission Status frame consists of four sub frames top middle left middle right and bottom The top frame shows the elapsed time counted from the beginning of simulation and the current communica 21 tion distance The middle left frame shows the status of each PAs among TX RX IDLE The middle right frame shows the current location of the main JTRS object our system The bottom frame shows the power consumption level of PA in terms of dBW System Power Profile displays the entire simulation profile with Y axis as system power Watt and X axis as time sec It lets the user analyze the system status at the peak power usages 22 5 Component Editor The Component Editor is a user front end for the component library The User can use the Component Editor to create edit component models which are then compiled into simulatable SpecC models for p
21. ation You may also speed up by the usage of fast forward You can also reset the simulation The following table summarizes the functions Icon Description Play back the mission on real time Fast forward the mission Pause the real time play back Stop a real time play back OBYV Return to initial state of the mission 50 Step Simulation The step simulation allows you to observe the detailed mode transition of each component with respect to time It also provides the high level view of a mission by the time accurate animation of communicating objects and the status of time location distance and a mission aware component PA Step simulation is controlled by the following icons Icon Description K Go to the beginning state of a mission Step backward to the previous state of a mission Step forward to the next state of a mission 54 Go to the final state of a mission Alternative to these controls you can also use the simulating wheel on the Control Panel Fig 15 to manually playback the mission scenario You can tune the slowdown factor by setting the scale bar underneath where 1 represents the fastest speed and 20 the slowest speed During the simulation you can set a starting anchor anywhere inside the system power profile frame by clicking at the position you want to start the playback Animation only Simulation Animation only simulation lets you observe the mission
22. atistics Component Name Command Command Component description Number of commands for that component Percentage of the number of commands 39 Part II Quick User Guide 40 This quick user guide contains the following subsections Getting started e Using the tools Viewing the results Generating reports Executing power commands e Editing components Interactively playing back the simulation e Debugging the tool at run time 11 Getting Started To get started you first need to prepare the input files mission files mission configuration and mission profile and component library Mission profile is pre generated by passing mission configuration through MAPMgen Put the mission filesin SJTRS missionlib For the demo purpose some sample files already ex ists Refer to the sample files to get the file format Let us assume the mission to be executed is mission7 so we place mission7 xml and mission7 txt in JTRS missionlib directory Put the component library in JTRS complib The component library is a Python script Users familiar with Python can manually edit a library file Users may use the GUI Component Editor to create edit a component library without knowing Python For the demo purpose the component library mycomplib py is already in there Now we can run Vimpacct by entering the directory and run the main script as following cd SJTRS jtrsgui code python jtrsgui py
23. ck the mission on real time gt Fast forward the mission M Pause the real time play back Stop a real time play back 9 Return to initial state of the mission 8 3 Step Simulation The user can also play step simulation to observe the states in finer grain The below controls support step simulation Icon Description Go to the beginning state of a mission Step backward to the previous state of a mission Step forward to the next state of a mission gt Go to the final state of a mission Alternatively the user may use the Simulation Wheel on the control panel 20 JE The user can first set the speed of the wheel by controlling the scale bar where 1 represents the fastest speed and 20 the slowest speed Then the user manually rolls the wheel either clockwise or counter clock wise to proceed the simulation or roll back the simulation respectively see Fig 10 31 000 X Visual IMPACCT PD OOD KCN SH AQM e b Transceiver 1 Modem 1 Blackpower 1 Black Proc 1 Transceiver2 Modem 2 plack Proc 2 Blackpower 2 PAT Red Proc 1 e Red Proc 2 D Paz ala Gg GG eo d H e PAS Transceiver 3 Modem 3 Blackpower 3 Encryption Black Proc 3 Red Proc 3 b PAS Transceiver 4 Modem 4 Blackpower 4 Black Proc 4 Red Proc 4 Redpower Domain Controller GPS Unit Black VO Main Power Red I O longitude
24. de 42 039 This number must start at 0 and increment by 1 altitude 0 altitude 0 altitude 0 gt altitude 4000 altitude 0 A phase element has attributes defining the destination in latitude leas If there are more than 1 one waypoint defi waypoint has a duration attribute which de The last waypoint duration should be 0 and of the phase nes their order in the same manner as described in phase If the duration total for all ongitude altitude measured in degrees and feet and either a duration in msec or a speed in nautical mph A phase must have at th number A on sequence fines it s length in msec it will last till the end waypoints exceeds the phase length the phase will terminate according to the information in the phas lement waypoint does not have a duration of 0 the waypoint is reached Ther to the destination if this occurs lt comment gt lt waypoint sequence 0 duration 0 gt lt comment gt If the waypoint total will be an instantaneous jump in is less and the last phase will end when that location Waypoints must contain a msgprofile element and one or more waveform elements defines th the mission The msgprofile element index attribute message profile element to use for this segment of Within each phase the msgprofiles are accumulative At the beginning of a phase the list of messages
25. efines the time between requests in msec The repeat attribute is how many times this message will be sent in a given mission phase If the interval is 0 the message will not be sent at all The include element must contain two attributes sequence and index index references another profile element The sequence attribute controls the order in which the include elements are processed When a waypoint defines a profile that profile element is read in The system processes the include elements first and then the msgtiming elements The result of an include element being processed is the same as inserting the contents of the profile it references into the current profile This include process 13 is recursive so if the included profile contains include elements then those profiles are added as well Note that there is no checking for infinite loops so Care must be used when creating an include hierarchy that has several levels After the include elements are processed th system will read the msgtiming elements The result is that the msgtiming elements in the current profile will overwrite msgtiming elements contained in the included profiles his allows the mission designer to include a general profile and override particular message types in this derived profile lt comment gt include sequence 0 index 1000 gt lt msgtimi
26. energy analysis of the optimized system for the mission It could be observed in two different ways system power profile in 2D energy time graph and energy breakdown in pie charts Both ways offer multi level analysis by letting users choose to zoom into channel level view and zoom out to system level view The below table shows how to view the results _ Q o 5 File Menu Description Tools Display System Power View the system power profile Tools Display Component Power View the channel component power profile Tools Display Energy Profile View the energy breakdown Table 3 Two Ways to Observe the Optimized Energy 43 X mission7 txt STE DDNDH KCN SH z p e te gd em m a dal Transceiver 1 Modem 1 m p a M a Li s Transceiver 2 Modem 2 PES Transceiver 3 Modem 3 m ES Ll di Transceiver4 Modem 4 Domain Controller GPS Unit Power Black Proc 1 Blackpower 1 a Black Proc 2 Blackpowel 2 af Black Proc 3 Blackpower 3 Black Proc 4 Plackpower 4 E Black VO Main Power a e ala Encryption Red Proc 1 il Red Proc 2 o Red Proc 3 cl Red Proc 4 Redpower 0000 0 longitude 0000 0 altitude 00000 km PA Power Consumption Level dBW 0 0 0 10 0 20 0 30 0 40 0 50 0 60 0 70 0 Time Figure 16 Main Window with System Components and Power Profile
27. evel command 1 System level pie chart 9 Component level command Channel level pie chart Sort Eneryy Generate Report View EPS Sort Command Save Report Load Report Close a Sort Energy Generate Pp AE Sort Command Save Re By channel E ZG m By component name 4 By channel By energy usage By component name By time usage By command count b c Figure 19 Generating report a is the main text window b shows the option list of sorting the energy c shows the option list of sorting the command 47 IXI JTRS Power Profile Report JTRS Power Management Report Sat Dec 13 2003 01 58 22 General Mission Name mission Mission length 79 209 sec Total No of messages 2266 Total No of commands 3249 Total waveforms 4 Total channels 4 Total components E System peak power W 591 886 Total Energy J 4416 067 Baseline Energy J 21830 996 Energy savings 79 77 Channel level energy statistics Channel Energy J Percentage D SIUS 70 51 1 502 004 11 37 2 152 372 3 45 3 268 484 6 08 4 379 431 8 59 Component level energy statistics Component Name Energy J Energy Ontime s Ontime Black I O 35 887 0 81 HS 8 88 Domain Controller 1188 135 26 905 MOZOS 100 00 Encryption 637 375 14 43 54 290 68 54 I Statistics Figures EPS W Mission general W Channel level energy Component level energy W Channel level command W Component level command Sort Energy
28. from omniORB import CORBA If these packages are not installed you can download them at e Python http www python org e omniORB http omniorb sourceforge net e SpecC http www ics uci edu specc How to Install Vimpacct Here are the quick download links for Vimpacct package e http www ece uci edu impacct software vimpacct 1 0 tar gz for Linux Unix Mac OS e http www ece uci edu impacct software vimpacct 1 0 zip for Windows To unzip the package Linux Unix and Mac OS users can type one of the following commands in the terminal gunzip vimpacct 1 0 tar gz tar xvf 9 tar xzvf vimpacct 1 0 tar gz Windows users should use Winzip http www winzip com or other third party software to unzip the pack age A root directory named jtrs is created on your host In the rest of this user manual we will use JTRS to represent the path to the directory You do not need to additionally set this path in the shell environ ment nor build install the software since the Python scripts are interpreted rather than pre compiled If you successfully unzipped the package you are ready to go ahead to the next step Setting up the servers To fully run the tools you need to have two servers set up One is the SpecC Simulation Server SSS the other is the CORBA Power Server CPS You can set up each server either on local host on a remote host We recommend to set up the servers on remote hosts either a Unix linux machine or an
29. h resource These three functions generate energy optimal power command trace The finalized resource configuration is stored in Resource Library and passed to Code Generator where the specC simulation code is generated The generated power command trace from Resource Manager is dispatched from the CORBA Dispatcher to the CORBA Server CORBA Server sends the power control both directly to the Simulation Server and via Power Instrumentation Unit which is used for hardware co simulation The power command trace passed from Simulation Server is simulated analyzed and saved in a report format The result is visualized on Vimpacct GUI which also allows interactive simulation play back The following sections will explain each of the functions in details in the following order Policy determines the state of the system For example channel_1 ON channel_2 OFF can be a system state A policy can be thought of a macro mode of the system where a macro mode consists of one or more component mode s ie PA1 ON Modem1 ON GPS ON PA2 OFF 1 input Section 2 2 front end Section 3 4 3 back end Section 6 7 4 front end Section 8 10 2 Input Format As Vimpacct uses parameters of both the system and the environment scenario content it receives input from both the application model and the system model 2 1 Application Model The input of the application model consists of mission configuration mission profile a
30. in use is cleared Message timings are then loaded from the profile in the first waypoint is added to the message timing list any messages that are currently defin For each subsequent waypoint the given profile overwriting settings for d The waveform attribute 11 indicates which comm_manager will be used for a msgprofile and thus which waveform will be used to transmit the messages lt comment gt lt msgprofile index 100 waveform 0 gt lt waypoint gt lt phase gt Second comm_manager is defined in the following format lt comm_manager waveform 0 description Satcom gt lt comment gt Describes parameters needed by a communications manager waveform is an integer value that must start with 0 and increment by 1 for each additional comm_manager waveform is referenced by a msgprofile element in a waypoint to indicate which comm_manager is used for the profiles group of messages The description attribute is a string without spaces The string is output for each message generated by the comm_manager and describes the waveform used to transmit the message request_interval is the time differential between sending groups of request messages The round_trip_delay defines how long after a request group is sent before the associated response is received Both parameters are defined in milliseconds After a request group is sent the system will not send a
31. le Simulator Channel 1 x M 870 eee A JTRS Share Resources Power Profile aac Encryption 10 0 nnel 2 annel 3 sr SUMMIT TT c Component View Figure 17 Multi Level View of Simulated Power Profiles c is observed by double clicking on b 45 e ee X JTRS Energy Profile x JTRS Channel 1 Energy Profile adm etu El Channel 1 El Power Amplifier Bl Channel 2 Bl Modem El Channel 3 Bl Transceiver Bl Channel 4 Bl Black Processor Bl Share Resources Bl Red Processor O Black Power double click Processing Time 79 209 s Channel 1 Energy Comsumption Total Energy 4416 067 J Power Amplifier 100 354898 J Channel 1 Energy 502 003 J Modem 52 680051 J Channel 2 Energy 152 372 J Transceiver 173 4605 J Channel 3 Energy 268 484031 J Black Processor 58 640867 J Channel 4 Energy 379 43 J Red Processor 84 113766 J Share Resources Energy 3113 776 J Black Power 31 753488 J Total 502 003562 J Baseline all on 21830 J Energy Saving 79 7715734087 T T Figure 18 Pie charts Energy breakdown Double click a slice to navigate a level down 12 3 Generating Report Icon File Menu 2 Tools Generate Report Comment dexin I don t see Tools Generate Report on the Tools menu right now is it included in the latest version By the above icon or
32. menu you can generate a report of the simulation profile A new window will pop up and you can specify the items you want to generate in the report by selecting or deselecting the checkboxes see Fig 19 a You can specify the sorting criteria by selecting the pull down menu at the bottom of the window Fig 19 b c The default is set to sort by channel When the selection is done click Generate Report button to generate the report in the main text window The generated report will look like Fig 20 You can save the report by clicking the Save Report button You can load a previously stored report by clicking Load button After done close the window 12 4 Executing Power Commands Now you can run the Command Dispatcher to send the power commands to the CORBA Power Server through a CORBA interface Click on the below icon or menu to run the CORBA client Icon File Menu de Tools Run Dispatcher You will see text messages printing to the shell windows on both server side and client slide hosts as shown in Fig 21 At the same time the commands are executed on the virtual platform on Host B and power modes transitions are shown in the server side GUI 46 eoe JTRS Power Profile Report N Figures EPS 1 System power profile 3 Channel level power profile _j Component level power profile Statistics W Mission general W Channel level energy 9 Component level energy W Channel l
33. nd the mission library Mission configuration is the an XML file that contains the overall mission scenario By MAPMgen this configuration turns into a message sequence Since these mission files contain some exclusive information both of them are required as Vimpacct input Mission library also contains exclusive data those of which not clarified in either configuration nor profile XML Mission Configuration This part is extracted by mapmgen_config ppt released by Rockwell Collins on 4 14 2003 The mission configuration contains the following elements e mission e comm_manager e msgprofile The mission element defines the mission parameters such as start location and time and the sequence of mission phases The comm_manager element s defines parameters that control sending and receiving groups of messages The msgprofile element defines what messages are used and message profiles that define sets of messages and timing values used during a mission phase Unless otherwise defined all numeric parameters must be integers The mapmgen program does not verify the correctness of the configuration before beginning message simulation If an error occurs during a waypoint Mapm_gen may exit after outputing an incomplete mission Examples of errors a waypoint referencing an undefined profile a msgtiming element using an undefined message opcode or a profile include element referencing an undefined profile Below each of these elements are clearly dem
34. ng opcode 142 interval 1 repeat 1 gt lt msgtiming opcode 01f interval 1 repeat 1 gt lt profile gt Mission Profile txt Mapm gen interprets the XML configuration and generates output in the following format timestamp waveform opcode w x latitude longitude altitude y The latitude longitude and altitude information appears only with a specific opcode andw x y the parameters not utilized by Vimpacct The following is an example mission profile 0 000 Link16 2la 2 2 0 100 Link16 342 6 4 0 100 Link16 346 8 2 0 100 Link16 351 4 2 0 100 Link16 510 32 2 0 305463 0 338655 0 985097 5683 47 9507 0 100 Link16 3b7 4 1 0 100 Link16 501 6 8 Mission Library py Mission Library is currently required to be configured manually although there is a default file for the demo purpose It includes e Waveform configuration e Delay for a channel to process a message e Location of the objects base station satellite and other JTRS objects We demonstrate the format in the following sample file waveform Linkl16 freq 1000 opband hb ch 1 type p2p Satcom freq 225 opband lb ch 2 type sati f 14 ATC freq 30 opband lb ch 3 type base MilStar freq 30 opband lb ch 4 type sat2 average time to process a message thru a channel in sec IMEPERMSG 0 001 loca
35. nother until the response is received lt comment gt lt time request_interval 1500 round_trip_delay 1000 gt lt comm_manager gt Third msg profile is defined by messages and profile indices lt msgprofile gt lt comment gt The msgprofile element must include one and only one messages element and one or more profile elements lt comment gt lt messages gt lt profile index 100 gt lt profile index 101 gt lt profile index 200 gt lt profile index 201 gt lt profile index 212 gt lt msgprofile gt Messages further expand to the following format lt messages gt lt comment gt All messages are described here Required attributes for a message are 12 opcode type size and family opcode is a 3 digit hex integer with leading 0 s size is a decimal integer family is a decimal integer describing what class the message belongs in type may be one of these string values request response or broadcast A broadcast message is one that the UCAV sends to the ground without being requested All ther messages must be defined in request response pairs request essage must include a reply attribute that defines the opcode of O m the response message Response messages may include an optional gps attribute If this attribute is set to 1 then location coordinates will be included on the log line whenever the message is sent The
36. nu item or click 9 on the Control Panel The pie chart shows the power break down of the system by channels Double click each portion in the energy pie chart to view each channel s energy break down by components The user can choose to export the power profiles or pie charts to EPS files by clicking e 37 10 Report Generation The user can use the report generation tool to generate customized text reports and figures 10 1 Report Features Start the report generation tool by choosing Tools Generate Report or click 3 on the Control Panel col 3 row 3 The user can generate the following items in the text report e General mission information e Channel level energy information e Component level energy information e Channel level command information e Component level command information The user can set the sorting criteria for the energy information e by channel e by component name e by energy usage e by time usage The user can set the sorting criteria for the command information e by channel e by component name e by command count The user can generate the following figures in the encapsulate postscript EPS format e System power profile e Channel level power profile e Component level power profile e System level pie chart e Channel level pie chart The user can save the text report by clicking the Save button To load a previously stored text report click Load button The EPS figures are stored at SUTRS report eps di
37. o start the CORBA server type the following commands in a terminal on the server host cd SJTRS corba python py omission server py To send the IOR to the client side run the following commands in a separate terminal on the server host o cd SJTRS corba scp mission service ior username client host name JTRS corba where client host name is the host name on the client side and username is the user account name on the client side Jiwon is this correct name in the address To start the command dispatch on the client side choose Tools Run Dispatcher or click de on the Control Panel You will see text messages printing to the shell windows on both server side and client side At the same time the commands are executed on the virtual platform on the server side and power modes transitions are shown in the graphic window on the server side The command dispatch is completed when it reaches the end of the power schedule To shut down the CORBA server the user need to explicitly identify and kill the server process ps ef grep python kill 9 serverProcessNumber where serverProcessNumber is the process number of the server process 27 X Visual IMPACCT 8909 K C 22 c SX N 5 s ERI Transceiver1 Modem 1 y ea pne Transceiver 2 Modem 2 PAS Transceiver 3 Modem 3 tw a id Transceiver4 Modem 4 Domain Controller GPS Unit ai Black Proc 1 Blackpower 1 v Black Proc 2
38. ode it proceeds the simulation in a rapid speed faster than fast forward function of real time simulation This functionality is controlled by the following two icons Icon Description ee Run the animation of a mission only fast de Stop the animation of a mission only 8 5 Zoom I O Zoom functions let the user observe the system mode in multi granular way Since the time granularity of the mode transitions is in milliseconds and the mission length can reach longer than 10 hours the zoom in out is an important functionality It is controlled either by clicking the below icons or directly selecting an area by mouse on the power profile frame Icon Description oy Zoom in one step of the system power profile g Zoom out one step of the system power profile Here we show the usage of these functions by an example Fig 11 is an initial state after a mission load On the power profile it is observed that there is a power glitch around timestamp of 10 sec To discover the exact system state that is causing the glitch the user may click and drag the mouse to select the area to zoom in see Fig 12 The user can repeat zooming in until the desired view is reached In Fig 12 the original 33 _ IX Visual IMPACCT PD gt OOD KCON e AQ Ho andar Transceiver 1 Modem 1 Black Proc 1 Blackpower 1 Red Proc 1 b a PAZ ay Transceiver 2 Modem 2 FAS Transceiver 3 Modem
39. ogram Exit Simulating Wheel Speed Scaling Bar 1 FI Figure 2 Conrol Panel 3 Control Panel Control Panel shown in Fig 2 is used for running each function of Vimpacct Table 1 shows the mapping of icon to menu and their brief description The rows are presented in the order of the usage tool flow In the users point of view C1 C3 are used for loading the inputs C4 C5 C10 C11 are used for running the tools and C6 C9 are used for viewing the results The simulating wheel and the scaling bar are used in controlling the user interactive simulation play back which will be explained in Section 8 Complete explanation for each control functions will be presented in Section 5 10 19 Icon File Menu Descryption Cl 5 File Load Library Load the component library ie mycomplib py C2 ri File Load Mission Load the component library ie mission7 txt LS C3 File Load Profile Load a pre simulated mission optional C4 Tools Policy Generation Generate power control commands C5 HT Tools Profile Simulation Run the simulation C6 B Tools Display Component Power View the channel component power profile C7 9 Tools Display Energy Profile View the energy breakdown C8 N Tools Display System Power View the system power profile C9 B Tools Generate Report Generate the summary report C10 de Tools Run Dispatcher Run the CORBA client dispatcher Cll Tools gt Edit
40. onstrated in an XML format First mission is defined by start and phases lt mission gt lt start gt lt comment gt Define starting position and time for the mission Time is in milli seconds The ticksizemsec is the number of milliseconds the clock will advance at a time Each time the clock advances the mission controller will be notified and will pass the time event to the comm_manager s in order for them to generate messages lt comment gt lt location latitude 42 039 altitude 0 longitude 91 633 gt lt time start 0 ticksizemsec 100 gt lt start gt 10 lt comment gt Define mission phases Th number defines the order in which sequenc the p hases are played No gaps are allowed in the sequence lt comment gt lt p longi lt p Longi lt p 5000 lt p longitude 91 958 duration 313000 gt lt mission gt nce 0 name preflight 633 duration 20000 gt nce 1 latitude 625 duration 265000 gt nce 2 hase sequ tude 9 hase sequ tude 9 nase sequ name taxi e XB e 1 e name tol_theater u longitude 91 625 duration 57100 hase sequence 3 name attack Phases further expand to the following format lt phase sequence 0 name preflight longitude 91 633 lt comment gt duration 20000 gt latitude 42 039 42 039 latitude 42 539 latitude 42 539 latitu
41. ower simulation The Component Editor allows the user to e Create a component library e Add remove components to a component library Change the component ID and the component description of a component e Add remove power modes of a component Change the name and attributes of a power mode e Add remove mode transitions of a component Change the name and attributes of a mode transition Generate the SpecC model of a component library The main window of the Component Editor has three columns The left column allows the user to edit the component list of a library The middle column allows the user to edit the power modes of a component The right column allows the user to edit the mode transitions of a component We will first briefly introduce the menu functions followed by the descriptions of the functions in each column 5 1 Menu functions File New Library Create a new library Save the currently opened library if it is modified File Open a Library Open an existing library Save the currently opened library if it is modified File Save Save the current library File Save As Save the current library with a specified name File Close Close the current library Save it if modified File Exit Exit the window Tool SpecC Code Gen Code generation of the SpecC power model About Help Empty stub 5 2 Editing the Component List The left column of the main
42. own as below ow PowerSupply rw mw Dependency ON BLK 0 9 ON RED 0O 9 ON MAIN 0 85 STB MAIN 0 7 Dependency specifies the mode constraints among the components A mode dependency follows one of the following two formats cO m0 cl ml cO m0 cl ml c2 m2 r op where cj mj i 0 1 2 represents a component and a power mode respectively The mode dependency is used to check whether c0 m0 is a valid mode setting The first statement says cO is in m0 only if cl is in 17 ml In other words if cl is not in m1 c0 cannot be in m0 The second statement says c0 is in m0 only if cl ml op c2 m2 is true c m is true if the component c is in the mode m op is a logical operator among AND OR XOR See the below example The first constraint says The PA is on only if the domain controller is on and main power is on The last constraint says The domain controller is on only if the main power is on Dependency pa ON ts ON bp ON dc ON ON ON ON ON r r r mw ON amp bw ON amp bw ON amp r z 18 0006 File Tools Help Component EG a Q Profile Simulation Tagg 8 Energy Breakdow me MM ba B Command Dispat A ME B El Mission Load Policy Generation Profile Load Power Profile View System Power View Report Generation Component Edit Pr
43. ransition Click a From mode name Click the Remove button at the bottom of the column 25 6 Policy Generation and Simulation Vimpacct policy generation is based on Decoupled Power Management Architecture DOMA The main idea is to decouple system level policy making from the architectural level device control For more information on the DPMA please refer to Vimpacct mission simulation is performed using SpecC power models The advantage of using SpecC power models is the powerful support for concurrent simulation and sychronized communication between software modules 6 1 Preparing the input files To run the poligy generation the user need to prepare the mission profile files and the component library file Put the mission profiles both in the XML format and in the text format generated by MAPMgen exe in JTRS missionlib Some sample files are already in there Refer to the sample files for the file format Put the component library in SJTRS complib The component library is a Python script Users familiar with Python language can manually edit the library file Refer to JTRS complib mycomplib py as an exam ple General users can use the GUI Component Editor to create edit a component library without knowing Python 6 2 Start Running When the user starts the policy generation some text messages are printing on the terminal window showing the progress of the policy generation Depending on the size of the
44. real time The user can start fast forward pause stop and reset the mission At any time the user may either jump forward or backward onto any timestamp of a mission by clicking on a desired point on the power profile window For example if the user clicks on a point around 40 0 sec as shown on the top of Fig 9 the anchor red line will move to that point and all four frames will display the mission status at 40 0 sec 5PA for channel 1 SIDLE ACTIVE for the PA is determined by whether message is going through the PA or not ACTIVE includes RX receiving or TX transmitting mode 29 Transceiver 1 Modem 1 Black Proc 1 Blackpower 1 Red Proc 1 Transceiver 2 Modem 2 Black Proc 2 Blackpower 2 Red Proc 2 Encryption Transceiver 3 Modem 3 Black Proc 3 Blackpower 3 Red Proc 3 Ban yv e DN Transceiver 4 Modem 4 Blackpower 4 Black Proc 4 P Red Proc 4 Redpower Domain Controller GPS Unit Black O Main Power Red I O Figure 6 Mode Simulation during Playback Time 43 200 sec Distance 37637 km PA Status PAI PAZ PA3 PA4 mou PA Power Consumption Level dBW Location latitude 42 339 longitude 91 958 altitude 04000 km Figure 7 PA and Mission Status during Playback 30 0 0 0 10 0 20 0 30 0 40 0 50 0 60 0 70 0 Time Figure 8 System Power Profile during Playback The following table shows the description of the real time simulation control Icon Description D Play ba
45. rectory 38 10 2 Report Format Here is the description of the fields in the report General Mission Name Mission Length Total No of messages Total No of commands Total waveforms Total channels Total components System peak power Total energy Baseline Energy Energy savings The name of the mission The length of the mission in seconds Number of messages in the input mission profile Number of power commands generated by the tool total number of waveforms total number of channels total number of power manageable components Peak power consumption over the mission in Watt Total energy after power management in Joule Energy consumption without power management in Joule Energy savings in percentage Channel level energy statistics Channel Energy Percentage Channel number 0 is shared resources Energy consumption of the channle in Joule Energy percentage of the channel Component level energy statistics Component Name Component description Energy J Energy consumption of the component in Joule Energy Energy percentage of the component in percentage Ontime s Time in which component has non zero workload in second Ontime Time percentage of Ontime in percentage Channel level command statistics Channel Channel number 0 is shared resources Command Number of commands for that channel Command Percentage of the number of commands Component level command st
46. s an example Modes md ON metric tag idle power 4 0 para OFF metric tag idle power 0 01 para STB metric tag idle power 1 0 para ts ON metric tag idle power 25 0 para OFF metric tag idle power 0 01 para STB metric tag idle power 0 1 para pa RX metric 6 99 tag idle power 5 para 5 0 OFF metric 20 0 tag idle power 0 01 para 0 01 STB metric 0 0 tag idle power 1 0 para 1 0 TL1 metric 9 4 tag idle power 8 7 para 1 0 TL2 metric 16 23 tag idle power 42 para 10 0 TL3 metric 25 71 tag idle power 372 para 100 0 THI metric 9 4 tag idle power 8 7 para 1 0 TH2 metric 16 23 tag idle power 42 para 10 0 BYP metric 7 3 tag idle power 5 37 para 0 1 Transitions Transitions specify the mode transition overhead Similar to Modes power and para is defined and time specifies the worst case delay of the transition Below shows an example Note that para is an optional field Transitions md STB OFF power 1 0 para timens 0 ON STB
47. scenario at a glance Independent of system power mode it proceeds the simulation in a rapid speed faster than fast forward function of real time simulation This functionality is controlled by the following two icons Description Icon gt Run the animation of a mission only fast Stop the animation of a mission only Etc Zoom functions on the main window let you observe into more depth They work in the bottom right window that shows system power profile H e o9 5 Description Zoom in one step of the system power profile Zoom out one step of the system power profile DPS Exit the main display window 12 7 Debugging the Tool at Run Time The text entry box in the toolbar of the main window lets the user dynamically modify the program This box is used by the authors for the debugging purpose However if the user is familiar with Python and the Vimpacct code he she can also use it to modify the internal variables as well as the GUI itself 51 Glossary CPS CORBA Power Server dBW decibel referenced to one watt IOR Interoperatable Object Reference IMPACCT scheduler 2 MAPMgen Mission profile generator developed by Rockwell Collins Mission Configuration A mission scenario specified by start time phases waveforms message indices etc cap tured in a pre defined XML format Mission Profile A trace of messages ordered by timestamp which specifies the released time of
48. straint e g quality of service signal to noise ratio etc Add a mode Type in ALL the four attributes in the corresponding fields use hyphen if it is empty Click the Add button at the bottom of the column Edit a mode Check a mode name Type in the updated information Click the Edit button at the bottom of the column Remove a mode Click a mode name Click the Remove button at the bottom of the column 5 4 Editing Mode Transitions Double click a component name in the left column brings up the available power modes and mode transitions of the component in the middle and right columns respectively The right column allows the user to edit the mode transitions of a component There are five attributes of a mode transition e From mode e To mode e Time e Power 24 e Parameter The From mode and To mode are two power modes of a mode transition as the name suggested The Time and Power are the time delay and the power consumption of the mode transition respectively The Parameter 1s used as a variable when either or both of the Time and Power attributes are represented as a formula Add a mode transition Type in ALL the five attributes in the corresponding fields use hyphen if it is empty Click the Add button at the bottom of the column Edit a mode transition Check a From mode name Type in the updated information Click the Edit button at the bottom of the column Remove a mode t
49. tion links appears in colored lines Each color dark red red orange and yellow indicates one channel among four When the link is accomplished the communicating objects turns into red The Mode Simulation frame shown in Fig 6 shows the system architecture When the simulation is initialized each components show their original colors During the simulation they switch colors showing their mode status Gray indicates OFF mode blue indicates IDLE mode light pink indicates RX mode in PA only and red indicates FULL ON mode The PA and Mission Status during Playback frame shown in Fig 7 shows the time communicating distance PA status location and the power consumption level of PA On this example the elapsed time is 43 2 sec the distance between active link where the PA is transmitting message is 37637 km PA1 and PA3 are in IDLE mode PA2 is in TX mode and PA4 is in RX mode The current location of our JTRS system is displayed in latitude longitude in degrees and altitude in km We can see that PA2 power level bar has reached the maximum amount since it is transmitting to a far distance The System Power Profile frame shows the profile of the system through the entire mission as shown in Fig 8 This particular mission has the interval of approximately 80 sec The red anchor line proceeds to the right while the simulation plays 8 2 Real Time Simulation Real time simulation lets the user play back a mission at the speed of
50. tion of basestation in degrees km base_la 42 039 base_al 0 base_lo 91 633 location of satellites in degrees km satl_la 23 0 satl_al 35000 satl_lo 58 6 sat2_la 25 5 sat2_al 38000 sat2_lo 52 5 location of other JTRS system def object_loc time import math la 30 0 000001 time al 1000 10 math sin time math pi 720 lo 55 0 000001 time return la al lo Although we assume the location of the other JTRS system as a function over time for now a mechanism provided by the communication protocol will enable the system to track the real location 2 2 System Model System Model consists of e Components Modes Transitions e Macro PowerSupply Dependency 15 Components Components include list of the entire power manageable hardware resources in the system and their short name as shown in following example Components md Modem ts Transciever pa Power Amplifier Modes Modes specify the power mode of each components each mode having for parameters metric tag power para Metric specifies the application specific information ie transmission power of PA for required level of SNR Signal to Noise Ratio Tag specifies the active idle type of mode Power specifies the actual power consumption level of the mode considering the efficiency of the real hardware Para specifies the ideal power consumption level of the mode Below show
51. top of the window 7A code generation process needs to be executed to provide the updated power model for the simulation server To perform the code generation a SpecC compiler v1 2 or higher and a GCC compiler v2 9x are required 49 e 8 X File Tool About Component List Modes Modem Transitions Modem 1D Name mode power parameter metric rV As Param bi Black 1 0 y OFF 0 01 pus s m oy uad bp Black Processor s ON 40 a Vv z z bw Black Power STB 10 OFF STB 50 4 0 dc Domain Controller bd E B ON OFF 0 4 0 eu Encryption Unit DOZE 2 0 E y 2 v ON STB 100 4 0 gu GPS Unit md Modem STB OFF 0 1 0 mw Main Power v STB ON 0 1 25 pa Power Amplifier ri Red 1 0 m Red Processor nw Red Power ts Transciever Y Add Edit Remove Add edit remove Add Edit Remove Modem selected Figure 22 Component Editor Real Time Step Run Time Simulation Simulation Profile Zoom Debugging Tool About i EA A DDOS KKCONM SE AQAA B Amid Animation only Exit Window Simulation These tools are used for interactive play back of a simulation They are separated in groups that have different functionalities Real Time Simulation Real Time Simulation provides a way to simulate the play back at the speed of the real time Although it proceeds automatically once simulation is initiated you have the control to pause stop and restart the simu l
52. vides a comprehensive explanation of Vimpacct tool It may be used for thorough understanding of each parts of the tool Part II is a quick user guide If the user s expectation is the minimal knowledge just enough to be able to use the tool the user may directly jump to Part II The glossary of this manual is provided at the end Chapter 2 An Overview of Vimpacct Key Features Vimpacct provides tools to help you fully optimize and analyze the energy consumption of mission oriented embedded systems The following lists the key features that Vimpacct provides Interpret a high level mission profile Generate a low power schedule Simulate schedules via SpecC simulation engine Visualize optimal mission power profile Interactively play back the power mode simulation e Output a comprehensive report that includes power breakdown component utility power savings from the baseline scenario etc Dispatch power commands to a CORBA power server e Let the users edit the power model These capabilities are supported by the back end programs including IMPACCT scheduler SpecC simulator and Command dispatcher Part I User Manual Application System Model Model
53. window has a list window to show the component list Once a library is loaded the component ID s and names are listed The component ID is a short name of a component without a space The component name is an elaborated name the user defined for the component 3A SpecC compiler v1 2 or higher is required a GCC compiler v2 9x is required 23 Add a component Type in the component ID in the short empty field Type in the component name in the long empty field Click the Add button below the short empty field Edit a component Click a component name Type in the updated information Click the Edit button below the long empty field Remove a component Click a component name Click the Remove button below the long empty field 5 3 Editing Power Modes Double click a component name in the left column brings up the available power modes and mode transitions of the component in the middle and right columns respectively The middle column allows the user to edit the power modes of a component There are four attributes of a power mode e Mode name e Power Consumption e Parameter e Metric The Power Name must be in capital letters without spaces The Power Consumption can be either a number integer or floating point or a formula The Parameter is used as a variable when the Power Consumption is represented as a formula The Metric is application specific representing an application level requirement or con
Download Pdf Manuals
Related Search