TestDrive.pptVIP

* Based on our discussion with OEMs and suppliers, we defined three user profiles, each with its set of tools. Within a larger team, different engineers may take on each of the three roles (profiles), but in smaller environment one person may wear more than one hat. Example: each system includes a copy of RT-LAB run-time, TestDrive GUI, and Python. Now, when you have a lab of 10 simulators, how many copies of Matlab/Simulink/RTW do you need? Probably just one. How many copies of LabVIEW do you need? Well, between 1 and 10, it is based on the number of engineers who will be customizing GUI panels. What level of LabVIEW license do you need? Base. * We have been serving users for ECU validation (towards to the end of the V) for many years with the RT-LAB Engineering Simulator. This is the area that the computing power to run high-fidelity closed-loop plant models and the flexibility to interface with many ECUs are important. Simulators tend to be used in smaller numbers and shared by teams. In the area of software development, we see needs for a larger number of simulators, each of which is typically used by one or two engineers. They need to run the simulator in open-loop mode and closed-loop, and switch back and forth. Again, these systems have to be simple to set up and simple to use. Note: running the simulator in open-loop means that the system is quick to set up. But more importantly for software development teams, running the system in open-loop is sometimes the only viable solution. At this stage ECU software is often incomplete (for example, the ECU may contain low level I/O driver software only and no control algorithm, or it may have control algorithms implemented in software but they are not properly calibrated). As a result, the ECU may not have fully functional software to interact with a closed-loop model, or it may contain enough working software to partially close the loop. Instead, running open-loop allows the users to verify indiv