Changing XNET databases and retaining mappings

[h_yong]

Hello,

I have a need to change XNET CAN databases. It appears that once I select a different database for a CAN port, all my previously imported frames get deleted which breaks all my mappings (and probably calculated channels that depend on the CAN messages...although I have not checked). Even if I assign to a very similar database that has mostly the same messages and signals, VeriStand does not automatically restore the valid messages and signals. This makes it difficult to change databases as I will need to manually redo the mappings and anything that references an XNET signal each time. Does anyone have suggestions? Thanks.

[Deborah_B]

Hello hyog,

This would take some initial up front re-mapping, but you could map a User Channel to your CAN frames and then map everything else to that User Channel, kind of like a middleman. That way, when you swap databases, you only need to remap the frame to the User Channel. It stays present in System Configuration Mappings, just looking for a source (see attachment). Aliases would work similarly for the Workspace. 

Also, if the dialog box below comes up when you are going through the database change process, be sure to select Cancel here, which will NOT delete those frames from appearing in the System Definition.

Thank you,

Deborah Y.

[h_yong]

Hi Deborah,

Thanks for the reply. Are you saying that I can map frames to user variables? I did not realize that. It would save some time compared to mapping each invididual signal to user variables if I can do it by frames. Thansk.

[h_yong]

Hi again, Deborah,

It appears I cannot map frames to user variables. That would indeed be useful as an interim solution. I have been in the habit of mapping specific signals in the past which has somewhat worked, but as the system definition and DBC's grow, I would rather not create an intermediate user variable for every single signal manually. Thank you.

[Deborah_B]

Correct, it would have to be at the signal level, I apologize for that typo!

Thank you,