• Not Answered

Delete non-existent controller

In all my years working with DeltaV, I have never needed to delete a DeltaV controller from a non-production database.  In this case, export of a live system database, the controller does not exist and I do not have access to a physical controller. 

I cannot seem to find a way to delete a controller in this scenario. 

I assume if I were to commission and decommission the controller properly, I would have that option, but at present, decommissioning the non-existent controller doesn't seem to do anything. 

I am ready to export the database, hack out the controllers from the fhx, and blow it back into a new database, but I'd like to avoid that work.  Suggestions?

Youssef.El-Bahtimy

• 13 May 2016 2:04 PM
• Cancel

8 Replies

• Matt Wicks

  

  • 13 May 2016 2:20 PM

  Youssef, I assume the import from the live system database brings the controller nodes in as showing commissioned but unconnected? I have a simulator box where I have imported several production systems, but in the test case I just ran, decommissioning the node did provide the ability to delete it. Sorry I can not offer any additional suggestions, but I will be curious to hear what responses you receive.
  Good luck.

  • Cancel
• Steve Linehan

  

  • 13 May 2016 2:33 PM

  Yosssef Have you tried downloading to the Proplus before doing this. Also setup data for the network as the database sometimes gives you strange results in a DEV environment.

  • Cancel
• AK

  

  • 13 May 2016 3:12 PM

  In reply to Steve Linehan:

  I faced this issue before, Please restart P+ if possible.. Some time this issue happens that you r not able to see some live Nodes in your Control Network.Also plz see your diagnostic results as well.

  • Cancel
• Anas Mustafa

  

  • 13 May 2016 3:21 PM

  Please try to download the changed-setup data and then download the proplus..it should work..if not, could you please attach any screenshot of the error that you are getting.

  • Cancel
• Andre Dicaire

  

  • 13 May 2016 5:07 PM

  Youssef, I assume you've logged a call with the GSC. This may be a known issue. Since we don't know what revision you are using, what controller model is involved or even any specifics as to the error message you may be seeing, it seems premature for anyone to conclude they have experienced the exact same symptom.
  
  As you noted, decommissioning a controller that is not communicating with its controller is normally possible. It is required if you were to have a failed controller that needs to be replaced (Simplex). So having had a similar experience on a normal system where decommissioning worked does not equate with your scenario.
  
  I assume this is a separate machine (non-production database), and not just a new database on the same Pro Plus. If so, that would mean the Powerup folder does not contain the node commissioning files. As you may know, when a device is commissioned, a file is created that links the controller's MAC address to the assigned IP addresses. Maybe the issue you are experiencing is related to the missing files and the decommissioning function is unable to complete successfully because these files are missing. I don't know if this is the source of your issue, but if it is, it may be known to the GSC, and if not, and turns out to be the issue, it would be good to have this logged in the CTS database.
  
  If you copy the Power Up folder from the production system to the off line system and you are then able to decommission the controller, that would be a strong indication this is the issue. Either way, please log a call.
  
  Note. You should not manipulate the files in the Power up directory of a running system as this can result in unexpected issues. Since this is an offline system, the risk is acceptable.

  Andre Dicaire

  • Cancel
• Andre Dicaire

  

  • 13 May 2016 5:22 PM

  In reply to Andre Dicaire:

  A little bird just told me that if this is an SZ controller, you cannot decommission the SZ if it has a CSLS commissioned. "doctoring the FHX is the only way around."
  
  This gets back to understanding the problem before suggesting a solution. The GSC would take you through the steps to quantify the issue before suggesting a solution. and could save you all the aggravation of reading a bunch of irrelevant "non-solutions" :-)

  Andre Dicaire

  • Cancel
• Youssef.El-Bahtimy

  

  • 13 May 2016 5:30 PM

  In reply to Andre Dicaire:

  Download of proplus and setup data, restart of database, etc. did not help.
  Andre, that was very informative. Needing to have the powerup file for the controller present in order to decommission or delete it seems to be a hindrance, but I understand business rules enforcement is important when dealing with such systems.
  I could get the powerup files if I needed to, but I have not opted to do this. I took the controllers out of the fhx and created a new db using the modified export. I will keep your suggestion in mind should I require to do this in a more restrictive environment.

  • Cancel
• Andre Dicaire

  

  • 13 May 2016 5:38 PM

  In reply to Youssef.El-Bahtimy:

  And also if the controller has an SLS1508 logic solver commissioned, it cannot be deleted. If you have a logic solver in the configuration, you'll need to use the FHX route to remove the logic solver reference.

  Andre Dicaire

  • Cancel