Difference between revisions of "New features in v2.75"
| (2 intermediate revisions by one other user not shown) | |||
| Line 3: | Line 3: | ||
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. | 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 [[Vehicle Profiles|the Vehicle Profiles tab]] and how to manage it is described in the section [[Vehicle Profiles# | This functionality is reached through [[Vehicle Profiles|the Vehicle Profiles tab]] and how to manage it is described in the section [[Vehicle Profiles#Diagnostic templates - Manage active signals connected to the vehicle profile|Edit diagnostic reference]]. | ||
== New trigger expression for Loss of Signal == | == New trigger expression for Loss of Signal == | ||
| Line 12: | Line 12: | ||
== Support for alternative means of automatic connection of a vehicle to a WCU == | == 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. An alternative method is now available and that is by reading the vehicle chassis number. The selection on which type of method to use is available in the WCU module | 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. An alternative method is now available and that is by reading the vehicle chassis number. The selection on which type of method to use is available in the WCU module [[The Portal Administrator View#Configure the Vinreader Module|VINreader]]. The chassis number connection mechanism relies on the fact that a preconfigured label i set up before hand. Basically you designate a valued label to be used the as means to identify a vehicle in portal. Assume your preconfigured label is called 'chassis_no', then at the time the WCU will connect to a vehicle the read out chassis number from the vehicle is sent to the back-end where a vehicle having that label ('chassis_no') value set to the read out chassis number. If no vehicle having that label with that specific value set, a new vehicle is created where the label 'chassis_no' is set on the vehicle having the specific value. Read more about how to set the label to be used for chassis number identification in module [[The Portal Administrator View#Configure the Vinreader Module|VINreader]]. | ||
== The periodicity of Active Signals can be set in the Signal Reader Assignment Editor == | == The periodicity of Active Signals can be set in the Signal Reader Assignment Editor == | ||
Latest revision as of 07:27, 17 May 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. An alternative method is now available and that is by reading the vehicle chassis number. The selection on which type of method to use is available in the WCU module VINreader. The chassis number connection mechanism relies on the fact that a preconfigured label i set up before hand. Basically you designate a valued label to be used the as means to identify a vehicle in portal. Assume your preconfigured label is called 'chassis_no', then at the time the WCU will connect to a vehicle the read out chassis number from the vehicle is sent to the back-end where a vehicle having that label ('chassis_no') value set to the read out chassis number. If no vehicle having that label with that specific value set, a new vehicle is created where the label 'chassis_no' is set on the vehicle having the specific value. Read more about how to set the label to be used for chassis number identification in module VINreader.
The periodicity of Active Signals can be set in the Signal Reader Assignment Editor
The periodicity active signals can be set in the 'Modules' tab in the Signal Reader assignment editor. Click the 'Modules Settings' button to browse the Active Signals by ECU and view/edit the periodicity.
Support for M-Log firmware updates
The firmware of an M-Log unit can be updated by selecting the desired firmware version in the M-Log module settings. See M-log module for a further explanation.