HI, at Lnett we experience problems if we are deleting a subnetwork (deleting from function "modify control device) and setting a new one on the same same controller, but in different tier.
It happens if a user does something wrong, and will fix it. Tis is the steps they do:
- Set a subnetwork controller
- User discover they have set wrong Tier
- Delete the subnetwork (as shown below)
-Set the same device as a subnetwork controller in correct tier (same name as the first on both Controller and subnet name)
- Trace subnetwork - looks good, traces the correct subnetwork
- Save and update subnetwork - works fine, no error
- Posting to default and then there are some problems.
- The subnetwork is not created in default, and triggering a an new update will sometimes give a subnetwork but not 100% correct.
It will sometimes show as subnetwork towards wrong tier, and from the post log below you can see it "thinks" there are two subnetworks...
[VG22F85] successfully updated subnetwork in domain Electric, tier Electric Subtransmission (Finished 7:15:30 AM took 0:00:11.240964)
[VG22F85] successfully updated subnetwork in domain Electric, tier Electric Distribution MV (Finished 7:15:32 AM took 0:00:11.241954)
This problem will continue to appear for this subnetwork, if we trigger an update in this subnetwork it will sometimes fail, sometimes work fine.
I was wondering if anyone has seen the same and if they have a good way to fix. (will it help to delete the features ? controller etc?
br
Eivind Aasland
Lnett AS