• Replies 1 reply
  • Subscribers 584 subscribers
  • Views 93 views
  • Users 0 members are here
Options
Related

Citect Historian and RSLinx

Joe

I have a rather peculiar issue with my Citect Historian 2016 running on Windows Server 2012 R2.  I've set up my historian to connect to redundant IO servers running Citect 2015(7.5). Also on the historian machine i am running software to generate reports.  This software uses RSLinx Classic OEM to connect directly to my PLC.  What i've noticed is that when RSLinx is running and properly connected to the PLC the connection test to my primary data source will fail but the secondary is successful.  If i stop the RSLinx service and retest the connection it is successful to both data sources. 

Any thoughts on why this conflict would exist?

Parents
  • Hi Joe (JoeSimon1573) ,
    I've not heard of RSLinx causing any conflict with Citect Historian before. The Historian 2016 Connector would likely use CTAPI to connect to your redundant SCADA Servers. This uses port 2073 as the destination port (from Historian to SCADA).
    I'd recommend troubleshooting this further with port monitoring tools. Also see this post on Microsoft website:
    https://docs.microsoft.com/en-us/troubleshoot/windows-server/performance/determine-which-program-use-block-tcp-ports
    Kind regards
    Olivier
Reply
  • Hi Joe (JoeSimon1573) ,
    I've not heard of RSLinx causing any conflict with Citect Historian before. The Historian 2016 Connector would likely use CTAPI to connect to your redundant SCADA Servers. This uses port 2073 as the destination port (from Historian to SCADA).
    I'd recommend troubleshooting this further with port monitoring tools. Also see this post on Microsoft website:
    https://docs.microsoft.com/en-us/troubleshoot/windows-server/performance/determine-which-program-use-block-tcp-ports
    Kind regards
    Olivier
Children
No Data
© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.