Emerson Exchange 365

• Not Answered

Naming References in Control Module Class

Dear all,

I have a question regarding the creation of Control Module class in DeltaV.

The doubt that arises is the function of the following two fields in the "Naming References" section:

- Type
- Sub Type

What is the function of these fields?

Thank you very much.

Best Regards,

Rubén Aguilar Salamanqués

RAguilar

• 7 Mar 2022 6:32 PM
• Cancel

4 Replies

• Matt Stoner

  

  • 8 Mar 2022 8:07 PM

  The Type is just a string "parameter" that "can" be updated but really isn't typically used from what I have seen other than knowing what the "initial" type of module/module class was used to create the object from. I haven't seen a configuration that has kept this "Up to date" but I guess there might be people out there doing this.

  The Subtype is used when Bulk Editing to initially create modules. So if importing a module AI101 with a subtype defined as MY_AI_TEMP, if AI101 doesn't exist it will take a copy of module template MY_AI_TEMP (if it exists, Note module templates can be non-class based or class based) and create a module named AI101 using that module template. Then the rest of the parameters/definition for that module are updated based on what is in the data file being bulk imported.

  If AI101 already exists on the system and lets say this was created initially from MY_AI2_TEMP module template, the bulk edit will only update the subtype text to MY_AI_TEMP and then update the module based on what the data file being bulk imported. The structure and/or module class of the already existing module will still remain intact.

  It has been a very long time since I have done/seen this but If the template doesn't exist I think it generates a blank module and attempts to update and will most likely will get errors trying to update blocks/parameters that won't exist.

  • Cancel
• Andre Dicaire

  

  • 8 Mar 2022 8:33 PM

  In reply to Matt Stoner:

  I recently imported a configuration with its associated classes, however I did not import any templates. I then used a Bulk Edit of Loop_module to export the module data in order to update the Faceplate and Detail displays. When I reimportd with bulk Edit, the Sub-Type fields referenced Template names that did not exist. This caused the bulk Import to fail on every item. The error message indicated a problem with the class missing, and I checked to find the Class was there, but with an Underscore so that the name would not conflict with the template name. Changing the Sub-type to match the class name however did not work.
  
  The Bulk Edit looks for the Template name as defined in Sub-Type. So I modified my format file and removed Subtype from it and the data file and the import was successful.
  
  So, the Sub-Type links to a module template for bulk editing. Though is has not impact on subsequent imports, if it is included in the format file/data file, it must exist for the import to proceed, even after the initial module creation. Unless you delete your templates after module creation, you would never run into this, but it confirms the link to the templates during bulk edits.

  Andre Dicaire

  • Cancel
• RAguilar

  

  • 9 Mar 2022 4:52 PM

  In reply to Matt Stoner:

  Good afternoon,
  
  Thank you very much for your replies Matt Stoner and Andre Dicaire. They have been a great help.
  
  As a summary, we can say that Type "is not usually used" and subtype is used to create modules automatically in the Bulkedit Import based on that class, correct?
  
  Thanks for your help ;)

  • Cancel
• Matt Stoner

  

  • 9 Mar 2022 7:27 PM

  In reply to RAguilar:

  Yes that is correct.

  • Cancel