Delta V Controller unable to see in Decommissioned Nodes (Explorer) but I can in diagnostics.

I am in the process of adding a new controller to my system, I am unable to see the Controller in the decommissioned nodes using Delta V explorer (Ver. 11.3), but I am able to see it using the Diagnostics software. Is this an issue as the controller firmware seams to be Ver. 12.3.?

If this is the case how can I set the firmware to Ver. 11.3 or be able to see the controller under the Delta V Explorer. 

Thank you in advance.

  • Hi, Gary. Is this an MQ controller? You need to apply two hotfixes (CTRL_17 and WS_18) to add the definitions for the MQ to the Objectivity/DB. Once you install those, you should be able to see the controllers without issue.
  • This may be as simple as closing DeltaV Explorer and starting it again. Sometimes, re-initializing the database connection to Explorer is required.
  • Hello Gary,
    You will need to downgrade the controller to DeltaV 11.3. Use the Controller Upgrade Utility in Start>>All Program>>DeltaV>>Installation>>Controller Upgrade Utility. Select the controller for downgrade. You will need to apply some hot fix to be able to flash this MQ controller down to DeltaV 11. Other M or S-Series controller (MD, MX, SD, SX) , you can just downgrade.
    Look at this link and go to Prerequisites. http://www2.emersonprocess.com/siteadmincenter/PM%20DeltaV%20Documents/ProductDataSheets/DV_PDS_M-series_MQ_Controller.pdf.
    As Ray indicated, you will need the hot fix for the MQ Controller. This goes for SQ controller as well. You can ask your Emerson Local Business Partner or if you have Guardian support, you can get it from there as well.
  • Gents Thank you all for your reply, my controller is an MX, Tinh Phan mentions that for an MX I don't require any hotfixes I should be able to see it in my Explorer, I have since re-started explorer and I am still unable to see it is there anything else I can try?
  • In reply to GaryL:

    I don't think the Controller Upgrade Utility can be ran on a controller that hasn't first been commissioned in Explorer.

    Have you checked the network cables for installation issues?
    If the primary and secondary network cables are crossed or if the primary cable alone is bad the controller will be visible in Diagnostics but may not show up in the decommissioned nodes in Explorer.
  • Guys, Thank you all for your input, I managed to sort the issue out. For some reason I had to restart the pro+ which then allowed the system to see the new decommissioned controller. Not sure now if I have other system issues.
  • In reply to GaryL:

    Hi, it is nice to know that Pro+ restart resolved the issue. But before restarting the machine you could try restarting the DetlaV database server. I have seen similar issue getting resolved in this manner. Only make sure to restart the database server from Pro+ (locally and not through remote session/ terminal session).

    1. Server can be started/ stopped from DeltaV database administrator
    2. Second way is to run following commands from the cmd application:
    Stopping: net stop deltav
    Starting: net start deltav

    Regards,

    Purnendu Saptarshi

    Automation Engineer | Skellig Automation US LLC | Greater Boston Area, MA

  • In reply to GaryL:

    I would check your PC Primary Network card. As indicated by Lazy_Engineer, your controller would show up in Diagnostics but not DeltaV Explorer. If you reboot, this may have reset the network card and got it to work again.