Difference between revisions of "New features in v2.75"
Line 10: | Line 10: | ||
== Signal Reader support for J1939 DM1 messages == | == Signal Reader support for J1939 DM1 messages == | ||
Signal Reader now supports reading and logging of J1939 DM1 messages. | Signal Reader now supports reading and logging of J1939 DM1 messages. | ||
== Support for alternative means of automatic connection of a vehicle to a WCU == | |||
Historically, WCUs have had the functionality of automatically telling the portal which vehicle it is in. This has been done by reading the vehicle's VIN number and reporting this to portal which then has made a connection between the two entities. |
Revision as of 09:33, 14 April 2022
New way of handling diagnostic references for vehicle profiles
Before, one and only one diagnostic reference file (sddb-file) could be connected to a vehicle profile. This release introduces a new and more complex way of choosing which ECUs and software versions that are associated to a vehicle profile. It is possible to select single files like before, combine multiple files or manually add/remove single ECUs.
This functionality is reached through the Vehicle Profiles tab and how to manage it is described in the section Edit diagnostic reference.
New trigger expression for Loss of Signal
Signal Reader supports a new trigger expression intended for situations where a signals disappears after being present on a communication bus. The syntax is LOSS_OF_SIGNAL(SignalName, Seconds), which will become true when the named signal is gone for at least the specified number of seconds.
Signal Reader support for J1939 DM1 messages
Signal Reader now supports reading and logging of J1939 DM1 messages.
Support for alternative means of automatic connection of a vehicle to a WCU
Historically, WCUs have had the functionality of automatically telling the portal which vehicle it is in. This has been done by reading the vehicle's VIN number and reporting this to portal which then has made a connection between the two entities.