¶ v3.5.3 build 74
¶ List of changes:
Expanded capabilities for modifying protected imported parameters
Previously, parameters imported from protected decoding files could only be renamed. Now it is possible to modify the "Value Range" and "Timeout" properties
Added the ability to send requests to the bus during remote connection
Minor interface fixes
Fixed an issue with importing the "Total fuel consumption" parameter
¶ v3.5.3 build 70
¶ List of changes:
Added decoding file transformation feature
Now you can create your own files from multiple existing ones, including protected files from Navtelecom.
This is useful in cases where existing parameters are used as a base and additional decoded values need to be added. Or when only a few parameters need to be modified in an existing decoding file while keeping the rest unchanged
Added automatic detection and selection of OBDII parameters
Added "Flex" column to the parameter values table in the "Editor" tab
The column displays the parameter value that the monitoring server will receive after processing the device message
Added the ability to create parameter references
Previously, it was required to create multiple identical parameters for parsing in different CAN buses. Now you can simply create a reference to an existing parameter
Minor interface fixes and improvements
Fixed display of parameter presence indicators in the bus for the "Parsing by decoding file" table
Fixed sending OBDII requests to the bus
Fixed configurator crash when opening generator file
In some cases, the configurator would close when opening a message generator file if CAN scanning was running, or when attempting to start scanning after opening the file
Fixed coefficient for displaying parameter "sc3: Total fuel consumption, 0.5 L"
¶ v3.5.2 build 56
¶ List of changes:
Added graphical analysis and comparison of multiple logs
The comparison feature significantly simplifies the search for rarely or slowly changing parameters
The screenshot below shows an example of comparing logs to identify fuel level. Five logs from the same vehicle are used. The first four logs were recorded between refueling events with approximate levels of 10L, 25L, 40L, and 55L, while the last log was recorded during refueling up to a full tank (80L).
The interface shows how the comparison result looks for the byte containing fuel data
Added support for .trc and .csv log formats
In the log player you can now:
- play logs in .trc and .csv formats
- convert logs between .log, .trc, .csv formats
Available conversion paths
.log |
➜ | .trc |
.log |
➜ | .csv |
.trc |
➜ | .csv |
.csv |
➜ | .trc |
¶ v3.4.4 build 32
¶ List of Changes:
Added CAN Scripts feature
Detailed description is available in the User Manual
Completely redesigned filter for the "Decode by file" function
Now, when playing logs or scanning the bus, CAN Spy checks which decoding files contain similar messages. The animation below shows how the new filter and the matching decoding files window work.
Added indicators for the device's CAN interfaces
Detailed description is available in the User Manual
Added arbitrary value search in the "Messages" table
Added a "calculator" to compute scaling coefficients in the .caf editor
Added function to remember values on the bus for the last XXX seconds
This function allows CAN Spy to "remember" byte values occurring on the bus within an interval from 1 second to 5 minutes. After collecting the data, CAN Spy will highlight only new values.
Very useful for finding slowly changing parameters in large data sets.
Disabled block on file parsing when bus speed mismatch occurs
Previously, in the "Decode by file" function, if the bus speed and the decoding file speed didn’t match, a message appeared and decoding was not performed.
This restriction is now removed, and decoding will proceed, but the mismatch warning is now more prominent.
A new .caf file is now created when vehicle description is changed
While editing a custom decoding file, CAN Spy now monitors changes to name, model, or production years. If any of these change, it suggests saving a new .caf file with the updated name.
Minor UI adjustments
Font sizes increased where too small, spaces widened where too tight, and phrasing made clearer... 
Fixed crash when opening .caf file
Configurator crashed if scanning was started and then a .caf file was opened.
Fixed padding of empty bytes in CAN message display
If a message was shorter than 8 bytes, empty bytes were filled with random values.
¶ v3.4.3 build 12
¶ List of Changes:
Fixed display of requested parameters
Previously, the bus source of the requested parameter was incorrectly shown.
¶ v3.4.3 build 11
¶ List of Changes:
Added parameter search for FLEX in the decoding file editor
The list of parameters is quite large, so search is a helpful addition
Added parameter copy function in the Editor tab
Now it will be easier to create similar parameters (e.g., axle load)
Minor interface improvements in the Editor tab
Various small interface adjustments for the custom parameter settings area
Fixed default FLEX parameter selection on DBC import
Previously, the first parameter (Fuel level in tank) was automatically selected; now it defaults to "None"
¶ v3.4.2 build 11
¶ List of Changes:
Added Ability to Create a Custom CAN Decoding File
This function can be used in CAN Spy under the "Editor" tab.
(A detailed instruction will be prepared soon.)
¶ v3.4.1 build 9
¶ List of Changes:
Significantly Redisigned Interface
- Added a menu at the top of the application
- Changed the CAN data source selection panel (now with tooltips)
- Redesigned interface style, the Messages window now remains visible when selecting any tab
- Some interface elements are now placed in detachable windows (e.g., the Messages window) - they can be moved within the interface or placed outside the CAN Spy window (e.g., on a separate monitor)
Added Filter Function
It allows specifying constraints (filtering) for the data that will come from the CAN source to the Messages window. Accordingly, only the filtered data will be used further in the program.
Added Editor Tab
Projects for future decoding files are created and edited on this tab.
The process of creating one project is shown in the gif animation:
-
Create a Vehicle and specify the Make, Model, Years - this data will be in the name of the future decoding file
-
Create one or more CAN buses
-
Create Parameters
An example of creating a Car and adding a parameter with Engine RPM for KIA CEE'D is shown in the animation:
