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

Version Descripti on SIPLAC E OI B 3.3 04/2014 E dition 18 5.4 New connec tion check e vent in SIPL ACE Setup Center Proxy SIPLACE O IB 3.3 a dds sup port for an event in the Setup Ce nter sm art prox y compone nt. The S…

Version Description

SIPLACE OIB 3.3 04/2014 Edition

5.3 Discontinued Features

• The Support of the ITraceabilityOibService in the SDK will be discontinued. This means that the

SDK does not contain any interface artefacts for that interface anymore.

Caution:

Please check the support of the ITraceabilityOibService interface in the Traceability service

documentation. See the chapter Discontinued Features in the document “00197480-

02_IM_SIPLACE-OIB-3.3_EN.pdf” for migration to the new solution.

• The XML Import function in the SPI is discontinued starting in OIB version 3.0 and the usage will

throw an exception. This is due to potential wrong usage and the danger of corrupting your data.

• The WSDL Interface files for the SIPLACE Pro SPI have been removed from the SDK content. The

recommendation is to use the SPI smart proxy instead.

• The “OIB Configuration Editor” Operation Manager plug-in was removed. Please use the new

SIPLACE Studio plug-ins instead.

Version Description

SIPLACE OIB 3.3 04/2014 Edition

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"?>

</appSettings>

</configuration>

Version Description

SIPLACE OIB 3.3 04/2014 Edition

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.