The source code, jar files, property files, as well as the diagrams are available on the Developer Software page.
If you make any improvments please
send them to FCA so we can provide a better tool for everyone to use. You can send improved source code to mark.schweiger@external.fcagroup.com or andrew.hoin@fcagroup.com.
The CAN Simulator runs as a stand-alone process and sends CAN data through a socket when an app connects. CAN simulation is accomplished through either a Java CAN Panel with sliders or a Vehicle Spy script. The CAN signals available for simulation are found in a Sensor Properties file. The Sensor Properties file should be the same Sensor Properties file used by the Sensor Container.
The CAN Simulator uses a CANSimulator properties file to configure the simulator. The properties file contains the location of the Sensor Properties file, a list of CAN signals in the Vehicle Spy script to be made available to an app, as well as a count for the number of iterations through the Vehicle Spy script.
The Sensor Container was designed to communicate with the CAN Simulator over a socket. It is responsible for collecting the changed CAN data, mapping it to a java sensor, and notifying any app listening to the sensor that the data has changed. The Sensor Container has been integrated into the sensor package for the Kona Emulator.
The Kona Emulator contains a basic implementation of the current Kona interface. In it's current state the implementation emulates the radio implementation by providing API return values fed from a properties file. The implementation contains a full sensor implementation that is integrated with the Sensor Container package thus able to retrieve signal values from the CAN Simulator.
The SRT Gauge App is an xlet that uses the sensor package provided by the Kona Emulation and the CAN Simulator to simulate changing CAN data and display it with the JaimacaCAR emulator.
Updated: 03/29/2019