Emerson Exchange 365

• Not Answered

External Reference to a module on another controller (calc block, out1) not receiving a value.

I am referencing an OUT1 (CALC output) parameter in "CTRL2" in the RELAY-MODULE from the control module DUT_TEST1 which is located in another controller "CTRL1" (but same Area).

When referencing another parameter from the CTRL1 (i.e. CTRL1/I01/C07/OINTEG) no issues are present and the status is delivered to the control module assigned to CTRL2. In the same control module I reference the CALC block without success.

Has anybody else experienced the same behavior?

Thanks for your help.

Here the referenced parameters in RELAY-MODULE:

• DeltaV Operate
• Reference
• Calc
• ControlStudio
• DeltaV

GregorP

• 18 Apr 2017 8:23 AM
• Cancel

12 Replies

• Matt Forbis

  

  • 18 Apr 2017 12:14 PM

  The first thing I would check is to make sure that setup data has been downloaded to both controllers. That does appear that it could be the case since there are no blue triangles in your screenshots, but something to check. I would also check to make sure that your parameter did get configured as an external reference and not an internal reference by accident. Also worthy of checking would be use watchit or opcwatchit to make sure they can read the parameter. That would help you narrow it down to either ctlr1 or ctlr2 as having a potential problem.
  
  Thanks,
  Matt

  • Cancel
• GregorP

  

  • 18 Apr 2017 12:29 PM

  In reply to Matt Forbis:

  Hi Matt,

  I have tried that already. Both Controllers have their setup data loaded and I am also able to read the parameter successfully with watchit.

  

  

  What bothers me the most is that this used to work without any issue.

  • Cancel
• Matt Stoner

  

  • 18 Apr 2017 12:31 PM

  What are the software revisions of the two controllers?

  • Cancel
• GregorP

  

  • 18 Apr 2017 1:06 PM

  In reply to Matt Stoner:

  Both controllers have the following SW Rev: 13.3.1.6290.xr

  • Cancel
• Andre Dicaire

  

  • 18 Apr 2017 2:04 PM

  In reply to GregorP:

  Definitely a mystery, until we solve it....
  
  Since the OINTEG reference is working we know the two controllers are communicating. And since WATCHIT shows the parameter is responding we know it is downloaded and working.
  
  The difference between these two references is one is a device level reference and the other is a module.
  
  Is this an external ref or dynamic reference?
  
  What does WATCHIT show for the following:
  'RELAY-MODULE/DEV_INT.#REF'
  'RELAY-MODULE/DEV_INT.cst'
  
  Do you have any other remote module references between the same controllers. Are the working?
  
  Try creating a module with external reference to same path and assign to Pro Plus.

  Andre Dicaire

  • Cancel
• GregorP

  

  • 18 Apr 2017 3:09 PM

  In reply to Andre Dicaire:

  Hi Andre,

  We are talking about an external ref:

  

  I tried the 'RELAY-MODULE/DEV_INT.#REF' which gave me the following result:

  

  And 'RELAY-MODULE/DEV_INT.CST' returns:

  

  According to books-online this means that the "module is not configured". Which seems odd since I have downloaded the setup data on both controllers.

  I did manage to create a module with an external reference to the same path  which was assigned to the Pro plus :

  

  I however need the parameter in the sequence function chart module that is assigned to the Controller 2.

  The last test I did was to add an external reference in the CTRL2 module pointing to an AI block on CTRL1 which also did not work:

  

  So it seems that the only control module having trouble to communicate with other control modules is the one assigned to the controller 2.

  • Cancel
• Matt Stoner

  

  • 18 Apr 2017 3:34 PM

  In reply to GregorP:

  If it worked on the Proplus but not in another controller, it is likely some sort of networking problem between the controllers.
  
  You should call the Global Service Center (GSC) and log a call on this issue to get proper support instead of trying thru an online forum.

  • Cancel
• Andre Dicaire

  

  • 18 Apr 2017 3:55 PM

  In reply to GregorP:

  First, controllers are not aware of where remote modules a located. They need to ask a workstation, typically the Pro Plus. Set up data does not send module data to the controller.
  
  The remote connection is a two step process. First the device is added to the device list. We know that is done as th diagnostic reference is seen. This reference is made using the Device Table which is sent with setup data.
  
  Second a module reference is made to a remote controller. The location of the module must be obtained using a Directory Services call. The Pro Plus typically serves this function, but if offline the next station in line will provide the data. Since your pro plus is on line, we expect this is not the issue.
  
  If the Pro Plus does not receive the request, it would not provide the location and the reference would not be resolved.
  
  Hmm. One issue we've seen is when 3rd party switches are used and IGMP is enabled. Delta V uses Multi Cast messages as broadcasts and IGMP will interfere. So have to ask. Do you have a 3rd party switch in network?
  
  If the Pro Plus does not have this module it it's setup data the request would also go unserved. However, since WATCHIT and the test modules worked we know the Pro Plus has the module in setup data.
  
  Test. If you can download a test module to CTRL2 and reference a module that is not already used in this controller we can determine if the issue is only with the module or is a broader issue.
  
  Note once a Proxy client is established for a module all future references to the module use this instead of directory services.

  Andre Dicaire

  • Cancel
• GregorP

  

  • 19 Apr 2017 8:12 AM

  In reply to Andre Dicaire:

  Hello Andre,
  
  I am using 3rd party switches in my network however I think we can exclude that being the issue because it has worked with the exact same hardware before.
  Note I am using a test system which can be commissioned/decommissioned without any problem.
  
  I added a new module to the controller 2 and referenced the same parameter. Same result, no connection.
  
  I also decommissioned the controller created a new controller placeholder and a new module with a reference. Same issue is present, no connection.

  • Cancel
• Andre Dicaire

  

  • 19 Apr 2017 1:55 PM

  In reply to GregorP:

  IGMP is a learning feature and though it worked before, it could now be blocked.
  
  I suggest you get a supported switch and connect pro plus with two controllers together. A VE6019 unmanaged switch or and DeltaV smart switch.
  
  This would eliminate a network issue. Then if issue is with the switch you will know it needs to be configured to work. If it still is not working you at least have a supported hardware set that the GSC can investigate.

  Andre Dicaire

  • Cancel
• Matt Stoner

  

  • 19 Apr 2017 1:57 PM

  In reply to GregorP:

  Is there any data that is being communicating successfully or is nothing being communicated between the two controllers?
  
  Have you logged a call with GSC yet? I highly recommend you do that for this issue if you haven't done it.

  • Cancel
• GregorP

  

  • 19 Apr 2017 2:23 PM

  In reply to Matt Stoner:

  Hello everybody,
  
  Thank you very much for your help.
  
  I will log a call with GSC and will let you know if a solution is found.

  • Cancel