00197483-02_VD_SIPLACE-OIB-3.3_EN.pdf - 第19页

Version Descripti on SIPLAC E OI B 3.3 04/2014 E dition 19 6 Functions in SIPLAC E OIB Setup Center A d apter 6.1 Caching of the PackagingUni tQuanti tyChanged Eve nts for Product ion General The SIPL ACE m achines ar e …

100%1 / 32
Version Description
SIPLACE OIB 3.3 04/2014 Edition
18
5.4 New connection check event in SIPLACE Setup Center Proxy
SIPLACE OIB 3.3 adds support for an event in the Setup Center smart proxy component.
The SIPLACE Setup Center class has a new even implemented that clients can subscribe for:
/// <summary>
/// Occurs when the proxy detects a connection state change.
/// </summary>
public event ConnectionStateChangedEvent ConnectionStateChanged;
/// <summary>
/// This event is fired whenever a connection state change is detected
/// </summary>
/// <param name="args">The <see cref="ConnectionStateDetails"/> instance containing the
event data.</param>
public delegate void ConnectionStateChangedEvent(ConnectionStateDetails args);
The event will contain information about when the connection state change was detected (in UTC time)
and what change was detected.
Changes monitored are:
Connection state SC proxy -> Setup Center Adapter
Connection state SC proxy -> OIB Core
Connection state Setup Center Adapter -> Setup Center Application / Server
Connection state Setup Center Adapter -> OIB Core
The Proxy will check periodically for state changes. This period can be configured programmatically by a
new static property in the SIPLACESetup Center class:
/// <summary>
/// Gets or sets the check alive frequency in ms.
/// This value must be greater or equal to 1 second (1000) and less or equal to 1 hour
(3600000).
/// Default value is 60000 (1 minute)
/// Can also be set in the application configuration file appSettings like so, value is in
milliseconds:
/// <add key="Asm.As.Oib.SetupCenter.Proxy.CheckConnectionStateFrequency" value="60000" />
/// </summary>
/// <value>The check alive frequency in ms.</value>
public static int CheckConnectionStateFrequency
Alternatively it can be configured in the application configuration file:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<appSettings>
<add key="Asm.As.Oib.SetupCenter.Proxy.CheckConnectionStateFrequency" value="10000" />
</appSettings>
</configuration>
Version Description
SIPLACE OIB 3.3 04/2014 Edition
19
6 Functions in SIPLACE OIB Setup Center Adapter
6.1 Caching of the PackagingUnitQuantityChanged Events for Production
General
The SIPLACE machines are sending for every board released a PackagingUnitQuantityChanged event.
This generates a lot of traffic in the network and the central OIB WS-Eventing. The Setup Center Adapter
implements a caching mechanism of the PackagingUnitQuantityChanged events with the Action = 3 and
StationQuantityChangeReason=2. These events will be cached and the QuantityCorrection will be
accumulated until a send trigger is initiated. Triggers are
Any other PackagingUnitQuantityChanged event
Any action effecting the cached component location. For example, if a feeder is removed, all cached
events correlated to that feeder location will be sent.
Setup changes
Restart of the Setup Center adapter itself
Configurable amount of time, until the first occurrence from an event on one component location. Default
is 60 minutes.
Splice Chain Split of a Packaging Unit
Configuration
By default the installation is configured to cache these events.
It can be adjusted in the OIB section under configuration->OIB in the config files in the installation
directory.
<oib>
<siplaceSetupCenter
factoryLocation="TEST.TEST.TEST"
setupCenterSCIPortOut="8001"
setupCenterPerformProductionEvents="true"
setupCenterPerformUnknownEvents="true"
setupCenterUseProductionEventCache="true"
setupCenterUseProductionEventCacheTimeSpan="60">
</siplaceSetupCenter>
</oib>
Changing the value from setupCenterUseProductionEventCache to false will disable the caching functions.
Changing the value setupCenterUseProductionEventCacheTimeSpan will change the time in minutes.
Version Description
SIPLACE OIB 3.3 04/2014 Edition
20
6.2 Email Configuration
The adapter can send emails if encountering serious problems.
There is a SIPLACE OIB configuration section to configure the email escalation in the configuration file.
The property emailNotificationAddress can be used to specify a semicolon separated list of email
addresses. The property smtpServer is used to specify the Mail server which is forwarding the emails.
<oib>
<administration emailNotificationAddress="" oibEmailAddress=""
smtpServer=""/>
<discovery discoveryMode
6.3 Checking for the MSMQ Operation
General
The SIPLACE OIB Setup Center Adapter is collecting the information from Setup Center and transferring
the event information via MSMQ to SIPLACE OIB Core. This is a reliable asynchronous communication. In
case of network malfunctions or malfunctions of the MSMQ Service on the server side the event
information is queued on the client computer in a so called outgoing queue. This check performs a periodic
check if the MSMQ queue is filled up with more than 500 messages. If so the adapter will send an
escalation email. Then user interaction is required to resolve the error situation.
Configuration
By default the installation is configured to check for collected messages.
It can be adjusted in the oib section under configuration->oib in the config files in the installation directory.
<siplaceSetupCenter factoryLocation="TEST.TEST.TEST"
setupCenterSCIPortOut="8001" setupCenterSCITimeOut="60000"
setupCenterPerformProductionEvents="true"
setupCenterPerformUnknownEvents="true"
setupCenterUseProductionEventCache="true"
setupCenterUseProductionEventCacheTimeSpan="60"
setupCenterMSMQMessageThreshold="500"
setupCenterMSMQWatchdogActivation="true"
setupCenterMSMQWatchDogCheckTimeSpan="3600000"
setupCenterDisconnectedWatchdogActivation="false"
setupCenterDisconnectedWatchDogCheckTimeSpan="300000">
Changing the value from setupCenterMSMQWatchdogActivation to false will disable the check functions.
Changing the value setupCenterMSMQWatchDogCheckTimeSpan will change the time in milliseconds,
how often the check is performed. Changing the value setupCenterMSMQMessageThreshold will change
the number of messages in the outgoing queue which triggers the escalation email.