Источник: Tech Note 464 Port Considerations for Wonderware Historian IDAS 135.139 TCP/UDP
Remote IDAS uses 135.139(TCP/UDP) and Port 445 (TCP and UDP)/udp Historian File and printer sharing 445/tcp Three galaxies would require ports 7500-7505 to be open For example, two galaxies would require ports 7500, 7501, 7502, and 7503 to be open. Important: If a Galaxy Repository (GR) has more than one Galaxy, two additional ports must be opened to enable a remote GR to browse to each additional galaxy. Источник: Tech Note 556 Port Configuration List for System Platform 2012 R2 Multi-Galaxy Environment Для версий WSP 2012R2 - 2014: ASBGRBrowsing Service 7500 (default, configurable)ĪSBMxDataProvider Service 3572 (default, configurable)ĪSBAuthentication Service 7779 (default, configurable) Для версий от WSP 2014R2 и старше: All PCS (ArchestrA Service Bus) communication is based on the Microsoft WCF shared port 808 Redundancy Message Channel Port (RMC) 30001 TCP The port used by the redundancy message channel to synchronize dataĪpplication Server & System Platform Multi-Galaxy Redundancy Primary Channel Port (PMC) 30000 TCP The port used by the failover service to manage heartbeats with the MxPort (NMXSVC) 5026 TCP Outbound Archestra Communication Channel. The DCOM Ports used by the Bootstrap are: 11 Schneider Electric Floating License Manager (for Citect).2.1 Application Server & System Platform Multi-Galaxy.One more thing Most of the DBs I have are optimized DBs.
#Citect floating license manager software
So DO I need to configure any middleman software to configure it. So, you have to use middleware like SImatic Net or PSDirect software to talk to S7-300 CPU.
#Citect floating license manager series
When you say basically it is same as S7-300, you mean use S7NT driver? I know with S7-300 series you can not access the it directly. So the rack/slot is probably implied for S7-1500.Īny help pages for the setup of the tags ? So even legacy software that knows nothing about S7-1500 should work as long as it did work with S7-300.Įdit: I studied the help pages, and it seems that for S7-1500 the only thing you must specify is the IP address. If the S7-1500 has enabled PUT/GET, and the tags are accessed with absolute addresses, then it is exactly as for an S7-300 - except for the rack/slot. When setting up the connection, it is basically the same as for S7-300, except that the rack/slot which was always 0/2 in S7-300 is always 0/1 in S7-1500. If I am correct, then you must setup each tag with absolute address access.Īnd, the accessed variables in S7-1500 must be set to non-optimized.Īnd, PUT/GET access must be enabled on the S7-1500 - default is not enabled. I doubt that Citect can read S7-1500 addresses symbolically (I might be wrong). If this the first time, then I can imagine a few things that you must be aware of. Has this been working before, or is it the first time for you with Citect and S7-1500 ?
0 kommentar(er)
