danielhrisca
Reloading configuration (*.dspf) does not correctly remap channels (GUI)
Overview
When using the "save offline windows" option in the "Channels" Tab a *.dspf file is created, which should allow me to reopen my window in the same state as closing it. Unfortunately upon reopening the file, the channels I used for plotting don't get mapped correctly. Instead of using the Channel of the right message (f.e. VehicleSpeed.x) it uses the first appearance of x, which quickly renders the tool useless for bigger measurement projects. Furthermore, there is no information from which can-node the signal came from, meaning Can1.VehicleSpeed.x and Can2.vehicleSpeed.x would have the the same problem if only using the message name would be implemented.
Possible Solution
I noticed, that in the dspf file, there is only the name of the channel saved (which would be x in this case) but as stated above, no parent information. Including the Message and CAN information in this file and checking for it upon reopening could resolve the problem without introducing braking changes (if there then do it, else not).
A possible way to get to this information is to use the display_names attr. of the signal class. It gets available after using the extract_bus_logging method and linking the file.
A possible way to get to this information is to use the display_names attr. of the signal class. It gets available after using the extract_bus_logging method and linking the file.
If the display names are unique, then you can use them to setup the windows in the first place
If you are generating the files by extracting bus logging then the alias names (display name) will also contain the form <CANx>.<MessageName>.<SignalName>