• Not Answered

Debug Mode in Equipment Module

Hello,

I am experiencing difficulty testing a custom equipment module using shared module blocks. 

I am trying to use debug mode to force input parameters of shared module block within the equipment module but am prompted with the error "(63) RT_WRITE_ACCESS_DENIED, Access was denied for operation. Possible reasons are the module's area is not assigned to the workstation's Alarm and Events subsystem, a disabled cascade port is in use, or you do not have parameter/field security access."

for reference:

1. The area is properly assigned to my station (I can use debug fine in other control modules within the area)
2. The shared module input parameter is a floating point with status called "EFFICIENCY".
3. Inside the shared module, "EFFICIENCY" is wired into an division block.
4. I have added "EFFICIENCY" to Parameter Security Properties with the control lock of "Control" which my account has a key for.

I am new to using equipment modules functionally, and am wondering if they inherently don't work well with Debug or I have configured my shared modules incorrectly. 

Thanks,

• EquipmentModule
• Control
• DeltaV #DCS
• configuration

Jim K

• 9 Dec 2024 7:13 PM
• Cancel

3 Replies

• Andre Dicaire

  

  • 9 Dec 2024 7:23 PM

  One thing that always gets me is that I use a Remote Client Session and I always forget to assign the area to the session. I assign it to the workstation. I know this is not your issue if you can access other modules in the same area on the same workstation. but it does bite me from time to time.

  Andre Dicaire

  • Cancel
• Matt Stoner

  

  • 9 Dec 2024 8:19 PM

  I'm not sure you can force values on module blocks because the values are from another module. You will probably have to go force/set the values in the module that the module block is assigned to.

  • Cancel
• Jim K

  

  • 9 Dec 2024 8:59 PM

  Thanks for the input (no pun intended). The only work-around I found that works as of now is to add a standard function block (ie. transfer/deadtime/etc.) inside the equipment module just upstream of the shared module parameter where debug was wanted, and to debug the standard block as means to an end.
  
  For my purpose (having the equipment module act as a reference hub to help visualize control interaction similar to SAMA drawing) this doesn't add much value. Especially due to the amount of shared blocks/parameters my equipment module has vs how often debugging would be used. As Matt suggested, debugging directly at the module seems to be the best option.
  
  Maybe for DV16, something of this nature could be added.

  • Cancel