1. Reconfigurable Communication Link Between FASTER and RTSim Interface Matthew McCollum Mark Krause Derek Keibler

2. Problem Statement Vehicles dependent upon software systems Testing vehicle software systems as a whole is important John Deere teamed up with ISU and created a VR simulation of their tractors Currently just involves a navigation simulation Real Time Simulator (RTSim) hard coded for every tractor John Deere would now like: More advanced, flexible, and reconfigurable interface Allow for more operator controls and live operator control updates

3. System Description Current systems »John Deere FASTER test system »Iowa State University VR Tractor Simulation »Vehicle System Dynamics Modeling and Simulation Architecture Our Systems »Improved Reconfigurable Interface between the three »Real Time Simulation Communication Configuration Application (RTSim CoCoA)

4. RTSim Block Diagram

5. Full System Block Diagram

6. Operating Environment The RTSim CoCoA run on Windows The interface run on Linux machines

7. Interfaces RT Sim system already created John Deere created their own for the FASTER simulation Project is focused on interface between the two »VR Simulator though the use of Sockets »FASTER Simulator though the use of CAN over USB ports RTSim CoCoA user interface: »Likely to include two lists F one for the FASTER signals F one for the VR signals »Create connection pairs between them »Current pairs displayed neatly »Save/Open configuration files

8. Concept Sketch of GUI

9. Requirements Functional: Must have reconfigurable comm. protocol between: »CAN, VR Module, Dynamic Model Comm. protocol must be scalable to the number of variables RTSim CoCoA must allow users to manage config. files »Create, Save, Open RTSim CoCoA must keep track of units FASTER Simulator and RTSim comm. must meet real time requirements Non-functional: RTSim CoCoA shall run on Windows Interface shall run on Linux systems Interface shall conform to CAN standards (SAE J1939 and ISO 11783)

10. Deliverables F Project Plan Presentation (02/13/09) F Project Plan Report (02/27/09) F Design Presentation (04/10/09) F Design Report (4/24/09)

11. Work Plan F Project Schedule: F 01/27/09 – 02/24/09 Planning F 02/25/09 – 04/24/09 Research & Design F 04/25/09 – 08/20/09 Optional Development/Research F 08/21/09 – 09/10/09 Develop & Test RTSimCoCoA module F 09/11/09 – 11/11/09 Update existing modules F 09/11/09 – 10/11/09 Update Interface module F 10/12/09 – 10/25/09 Update VR module F 10/26/09 – 11/11/09 Update DM module F 11/12/09 - 12/15/09 Testing and Debugging

12. Risks and Resources Risks: F Loss of a second team member »Management: Keep team knowledge distributed F Hardware failure »Management: Keep backups of data (SVN) Resources (provided by client): F - Red Hat Enterprise Linux 4.0 licensed machine (64 bit preferred) with F CAN (Controller Area Network) adapter F - CAN parse (Deere internal software) F - Drivers for CAN USB or CAN cards (softing PCMCIA or Intrepid USB) F - limited data set CAN logs F - Simulation server with table definition

13. Questions?