When DCUID of a model is changed, obscure problems crop up.
If a user naively changes a model DCUID in the model file, then builds and starts the model without manually editing the gds/param/testpoints.par file, some problems crop up that are hard to diagnose and fix:
When there are two DCUIDs defined for the same model in the testpoint.par file, awgtpman may pick up the wrong dcuid. It will then reject every channel defined with the new, correct DCUID. No testpoints can be opened.
Awg is mostly silent about this, except at startup it will report the new DCUID as 'RMID' for the channels, but report the old DCUID for itself.
To the user, it just looks like DTT can't open a test point.
Fixes:
Ideally, the installer will erase old blocks for installed models.
As workaround, awg could be changed to load DCUID from channel list. Could be changed to report DCUID as DCUID instead of RMID.
RTCDS could be involved with checking, possibly correcting the testpoint.par file.