PCAN-FMS Simulator 2 Version History

17.01.2012 - Version 2.0.2.48

Bug fixes:

When recording a trace file, the data was recorded circulatory and sorted incorrectly on saving the file. The data will now be recorded linearly until the data buffer is full
In the Options dialog box, if messages were activated that are only present in FMS 02.00 and bus FMS 00.02 (e.g. DI and LFE), and the standard was only set to FMS 02.00, an error was always displayed at startup of the simulation that no messages are selected for simulation
The "Vehicle Weight" PGN was not transmitted during manual simulation of FMS standard 02.00
During manual simulation of the FMS standard 02.00, messages of PGNs "Vehicle ID" and "Driver ID" could overlap if a VID was defined with 200 characters. Now the "Driver ID" PGN is transmitted with an offset of 2 seconds to the start of the simulation. Thus the VID is transmitted 10 seconds and the DID 12 seconds after the start of the simulation and then every 10 seconds each
If a manual simulation first was started with the standard "FMS 01.00" and then anotherone was started with the standard "FMS 2.00", the signal value "Engine Per. Load" in the "Simulation" window could be changed, but the value was not updated in the "EEC2" message and not displayed in the "Monitor" window. 0xFF was always transmitted and the value 125 was always displayed in the "Monitor" window
The error conditions for the signals "Engine Percent Load", "Fuel Rate", "Instantaneous Fuel Economy", "High Resolution Engine Total Fuel Used", and "PTO Engaged" were not or not properly displayed in the "Monitor" window
On manual simulation sometimes data from a previous simulation was used if a manual simulation had been once started and stopped before. This showed up especially at recording of trace files that afterwards had many messages at the beginning with the time stamp of 0
On manual simulation the unused data bytes of all messages (except VI and DI) were not set to 0xFF. This only occurred at first transmission of the messages; afterwards the unused data bytes were transmitted correctly
The relative directory paths of trace files were faulty after saving project files. Thus, at loading of those projects and with them the trace files an error occurred

28.02.2011 - Version 2.0.1.46

Bug fixes:

When a project file was opened with a double click in Windows Explorer, an exception occurred and the program was closed again. If the program was running as trial version, the trial dialog was previously displayed; after proceeding by starting the program (Try PCAN-FMS Simulator 2) an exception occured, too
In the Bus-FMS standard, the "Parking Brake Switch" signal was placed on the wrong bit position (bits 5-6) in the CAN message. Correct according to the specification however are bits 3-4
If a CAN connection was defined in the hardware input or hardware output and if it was not active (gray), an exception occured when running the command "Change Hardware"
If the simulation was started with hardware as input and no incoming data occured on the CAN bus, the program utilized a processor core 100 % until data was received or the simulation was terminated

24.11.2010 - Version 2.0.0.43

New features:

Completely revised user interface
Graphical representation of the FMS output data with ISO-7000-compliant symbolic display of signal values and optional full-screen function
Support of the standards FMS 02.00 and Bus-FMS 00.02
Enabling and disabling the different standards in the program; FMS and Bus-FMS can be used simultaneously
Expansion of the optional switchable automatic calculation of different signal values
Playback of custom areas from a trace file
Recording the data as a CSV log file, for example for further processing in Excel
Project file version 2.0 introduced; loading and saving the whole simulation environment in project files (upward and downward compatible with version 1 of the PCAN-FMS Simulator)