Downloading Assigned I/O (Version 13.3.1)

I logged into one of my plants this morning and noticed that there is a blue triangle beside Assigned I/O underneath one of the controllers. I'm not aware of any changes and there are no blue triangles on the I/O network itself. What happens if I download I/O Assignments on the Assigned I/O? Will it cause any disruptions?

  • Expand the tree, right mouse and select update download status from the tree. If it is still blue you can drill down to see which I/o is flagged for download. Then if necessary download that single I/o point if process allows. Another alternative if there are no individual I/o points flagged you can download setup data at the top level and it may clear. Sometimes if you have HART enabled a change/update to the field device will flag a need for download.
  • In reply to Jason.Brumfield:

    There's only the two options and no flags on individual points. My main concern, will downloading "I/O Assignments" disrupt the process?
  • In reply to JoshC:

    I just now had the same problem, likewise on version 13.3.1. I have nothing but CHARM I/O. I read the following in books online.

    Delete Unused Assigned I/O Reference Configuration
    When the Assigned I/O subsystem is selected, this option appears on the Download menu. It applies to CHARM I/O cards (CIOCs) and CHARMs. After you delete CHARM or CIOC assignments, select this download option to update the configuration in the database.

    I tried that, but it didn't remove the blue triangle. Next I downloaded changed setup data at the controller level as Jason suggested, but that didn't work either. So I got my buddy (hee hee) to download I/O Assignments. I have never had a problem downloading an individual I/O point, so I wasn't really expecting any trouble. There was no process disruption and the blue triangle disappeared. I'm not a DeltaV expert, but it worked for me. I'll stay tuned in case someone says I was lucky.
  • In reply to Mark Bendele:

    Downloading assigned I/O worked with no process disruption. Reading the download log, it was flagged by a couple of HART alarms that had been changed.