00197483-02_VD_SIPLACE-OIB-3.3_EN - 第24页

Version Descripti on SIPLAC E OI B 3.3 04/2014 E dition 24 9.6 Setup Center Interface This c hapter descr ibes res trictions c oncer ning the whole f unctiona lity of the interf ace. - The us age of SI PLACE O IB req uir…

Version Description

SIPLACE OIB 3.3 04/2014 Edition

9 Restrictions

9.1 General Restrictions

Due to the dependency of the API to the underlying SIPLACE products, the content and the functionality of

the exposed API depends on the configuration of the overall system. Please see the adapter version

description of the target adapter for details.

9.2 Restrictions for the Line Control Adapter

The SIPLACE OIB Line Control Adapter must be installed on the same computer as the Line Control

Server has been installed.

9.3 Restrictions for all SIPLACE Pro Adapter Versions

All SIPLACE OIB SIPLACE Pro Adapters require an SPI installation of the target version of SIPLACE Pro

on the same machine.

The installation can be implicitly by installing a SIPLACE Pro product like SIPLACE Pro Desk

on this computer or you can explicitly install the interface by starting the SIPLACE Pro Installer and select “SIPLACE

Pro Interface” as the installation type.

9.4 SIPLACE OIB Setup Center Adapter

When operating the SIPLACE OIB Setup Center Adapter together with the XML Import Service it might

happen that the system is not operating properly, when the event log configuration from Windows is not

setup appropriately.

Workaround: Ensure that the Application event log is setup for “Overwrite events when required”

9.5 Setup Center in General

This chapter describes restrictions concerning the whole Setup Center application.

- For all used components, “verification” has to be activated in SIPLACE Pro.

- The setting “Setup Verification System” of a used setup has to be set to “External … System” in

SIPLACE Pro.

- There has to be configured a line in Setup Center.

- Setup Center only works in unique ID mode, ICL mode is not supported by SIPLACE OIB. Therefore the

barcode definitions have to define a barcode with barcode fragment “UniqueId”.

- Table management is supported with restrictions. Table announcement is only possible at the station on

site. Therefore a table has to be announced first manually, before machine control operations may be

executed via Setup Center Interface. Events have no restrictions.

- Quantity printout for ICL mode has to be disabled.

- XML import has to be disabled.

Version Description

SIPLACE OIB 3.3 04/2014 Edition

9.6 Setup Center Interface

This chapter describes restrictions concerning the whole functionality of the interface.

- The usage of SIPLACE OIB requires online verification.

- Splice chains have to be completed to be passed into the interface. If only one packaging unit of an

existing splice chain is used, the splice association will be deleted.

- Barcode rules won’t be executed.

- The following matrix shows invalid combinations for packaging unit quantity and original quantity:

Condition

Result

Quantity==Int32.MinValue && OriginalQuantity==Int32.MinValue

Denied

Quantity != Int32.MinValue && Quantity < 0

Denied

OriginalQuantity != Int32.MinValue && OriginalQuantity < 0

Denied

Quantity > 0 && OriginalQuantity==0

Denied

Quantity > OriginalQuantity

Denied

10 Errors that have been fixed

Please see the ReadMe.txt file in the installation media for the latest list of errors that have been fixed. The

ReadMe.txt file will be updated with every build.

11 Support of Previous Versions

Beginning with the release of OIB 3.0 support of OIB 1.4 will be discontinued. To continue receiving

support it will be required to upgrade to a newer version of OIB.

12 Important terms and abbreviations

OIS

Operator Information System

SIS

Setup Information System

ICL

Identical Component Lot: When the packaging units does not have

unique id, but share the same batch id.

SPI

SIPLACE Pro Programming Interface

Version Description

SIPLACE OIB 3.3 04/2014 Edition

13 Troubleshooting

13.1 MSMQ Fails to Start

There might be situations during power failures where the MSMQ store will be corrupted or is left in an

inconsistent state. Then the MSMQ service is unable to start, which implies that the SIPLACE OIB Service

does not start as well, because they depend on MSMQ service. Please follow the instructions from the

knowledgebase article http://technet.microsoft.com/en-us/library/cc733512.aspx

Event Details

Product:

Windows Operating System

ID:

2053

Source:

MSMQ

Version:

6.0

Symbolic

Name:

EVENT_ERROR_QM_INIT_INSEQ_FILE

Message:

The incoming sequences checkpoint file failed to initialize. The file

MQInSeqs.lg1 or MQInSeqs.lg2 in the Msmq\Storage folder is corrupted or

absent. Error %1: %2

Delete incoming sequence checkpoint files

Checkpoint files must be available for Message Queuing to function properly. To resolve this issue, you

must delete the incoming sequence checkpoint files, as well as the QMLog file in the Message Queuing

storage directory. This can result in some messages being duplicated. However, this will get the service

running as soon as possible and usually without data loss.

To perform these procedures, you must have membership in Administrators, or you must have been

delegated the appropriate authority.