Emerson Exchange 365

• Not Answered

workspace application error number 5(5)

Hi everyone, I have some issues with this error, I'll try to explain the best as possible:

I'm actually working in a pharmaceutical plant in which we have two DeltaV Systems the old one is ver 11.3 and the new one is ver 13.3  which hasn't been delivery yet (emerson people are still working on batch logic control).

The DV system ver 13.3 had the workspace application error number 5(5) when the "search utility" button was pressed, I solved this problem by modifying the "MODT.SCR" cause had the next structure:

MODTI { NAME='module' DEVID=############# AREA=# CDISP='display' IDISP=

'faceplate' DDISP='detail' DESC='description' }

I modified it in the next way:

MODTI { NAME='module' DEVID=############# AREA=# CDISP='display' IDISP='faceplate' DDISP='detail' DESC='description' }

I changed that file in all the workstations of the new DV System and now we are able to use "Search Utility" button with no problems.

But this problem is presented in one operator station of the old DeltaV (11.3) the problem here is when I press the "Search Utility" button in that station appears the window with the message of the error number (5) and it doesn't matter how many times I close de windows it keeps appearing and I'm not able to use DeltaV Operate because of that window, I have to log off the station so windows force the shutdown of DeltaV Operate, I checked the MODT.SCR in this station and it looks normal with the right structure:

MODTI { NAME='module' DEVID=############# AREA=# CDISP='display' IDISP='faceplate' DDISP='detail' DESC='description' }

It's strange because in the proplus I don't have this problem and I'm able to open the "Search Utility" without any problems.

Somebody has any advice to fix this issue?.

• DeltaV Operate
• DeltaV #BulkEdit #Profibus
• DeltaV #DCS
• iFix #Operate #Graphics

Edgar Valdez

• 13 May 2020 1:31 PM
• Cancel

3 Replies

• Matt Stoner

  

  • 13 May 2020 1:59 PM

  You shouldn't be modifying this file (or any other file in that directory) as these files are generated and downloaded by the DeltaV system. Typically this issue is because there is Module Description with a single quote (') in the configuration.

  • Cancel
• Andre Dicaire

  

  • 13 May 2020 2:53 PM

  As Matt says, never, ever modify the .SCR files that are downloaded workstations or found in the Power up directory.
  
  The structure of the MODT file is very rigid but can change from revision to revision. It is up to you to ensure your program is able to deal with the syntax of the file. Error handling is the hardest part of a good program and can be more work than the core functionality. Changing these files could also cause other issues as they carry a signature that is invalidated by your edit. These files are specific to DeltaV software requirements and although you may have solved your specific parsing issue, you may cause other unintended consequences.
  
  Also, the MODT and all the .SCR files are updated automatically when there is any change in control module assignments or their display settings. The edited file would be replaced/updated, every time the Pro Plus is downloaded with an update to module data.
  
  Again, never modify these files. They should be read only. The only advice is for you to fix you program.

  Andre Dicaire

  • Cancel
• chip.burge

  

  • 15 May 2020 5:40 PM

  In reply to Andre Dicaire:

  I've seen this issue before when bulk editing faceplates, primary displays, etc. - really anything that goes into the MODT.SCR file. It looks like you have an erroneous line feed character in your module's faceplate based on your change that fixed it.
  
  The MODT.SCR is generated at each workstation when the setup data is downloaded for that workstation. The find utility in the PCSD toolbar parses this file to provide a list of all of the modules in the system to match against what you type into the search box.
  
  The best way to fix this problem would be to point the module in question that takes up multiple lines at the proper faceplate manually through the properties of the individual module in DV Explorer. Keep in mind that you won't be able to see the bad characters anywhere but the module table using notepad++ or a good quality text editor. They will not show up in the properties window of the module. You can use the browse option or type the proper faceplate name. If you've got a lot of these problems it may be easier to bulk edit. Once all this is done you can perform setup data downloads to each of your workstations to update MODT.SCR. If you've done everything right there will not be any carriage return / line feed characters in the middle of an entry and the search utility will work properly.
  
  Hope this helps
  
  Chip

  • Cancel