It is sometimes necessary to change the Data Origin for QoS objects, as when robots have been moved. There are two places to make changes in order to successfully change the origin 'ownership' of QoS data. The following instructions direct in how to modify your existing QoS data so it has the new origin value rather than the prior/old origin value.
Launch the controller probe configuration GUI for the robot whose origin you wish to change, navigating to the Setup/Advanced tab and supplying an override value in the Origin field of the Data Origin section (override origin set by the hub). In the image below, you can see the Origin changed from robot1 to robot1_override.
NOTE - Changing the origin in this manner will result in previous QoS data persisting the original origin, and QoS data from after the change, having the new origin.
The following instructions explain how to modify your existing QoS data so it reflects the new origin value rather than the prior/old origin value.
Change the origin of a QoS through the SLM portlet Database Status dialog.
You will see a screen such as this:
Click "Add" and add the new origin value used in the first step (the override set in the controller setup).
Choose the new origin and click "Ok".
Your origin should now appear as shown below with the newly chosen value.
Perform the same process for other QoS as needed.
NOTE - existing alarms will keep their old origin. New alarms will now have the new origin.
If SLM is not a viable option for any reason you can use Mcrosoft SQL Server Studio (SSMS) or another databse tool to run queries to change/update the origin.
Essentially, you can run queries like:
SELECT * FROM S_QOS_DATA WHERE ORIGIN = '<OLD/BAD/WRONG ORIGIN_NAME>'
UPDATE S_QOS_DATA SET origin= '<new_origin_name>' WHERE origin ='<old_or_wrong_origin>' OR nim_origin = '<old_or_wrong_origin>'