iDefine Release Notes

for ProSafe-RS Version 4.02

iDefine 1.16.1.1215

Document No: PR12002-REL-004_01

Safety and Control Lifecycle Design and Management

December 2016
 Copyright 2016 Trinity Integrated Systems. All rights reserved.
No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or
translated into any language, in any form or by any means, electronic, mechanical, photocopying, recording, or
otherwise, without prior written permission from Trinity Integrated Systems.
All copyright, confidential information, patents, design rights and all other intellectual property rights of
whatsoever nature contained herein are and shall remain the sole and exclusive property of Trinity Integrated
Systems Limited. The information furnished herein is believed to be accurate and reliable.
However, Trinity Integrated Systems assume no responsibility for its use, or for any infringements of patents or
other rights of third parties resulting from its use.
The Trinity Integrated Systems name and Trinity Integrated Systems logo are trademarks or registered
trademarks of Trinity Integrated Systems Limited.
All other trademarks are the property of their respective owners.
 CONTENTS
CONTENTS................................................................................................................. 1

1 ABOUT THE SOFTWARE .................................................................................. 2

2 THE INSTALLATION PACKAGES ..................................................................... 3

3 KNOWN LIMITATIONS....................................................................................... 4
FILE PERMISSIONS ON IPJ FILE .............................................................................. 4
Description ......................................................................................................................... 4
Impact.................................................................................................................................. 4
Workaround ........................................................................................................................ 4
PROGRAM NAMES IN OUTPUT CONFIGURATION VALIDATION DOCUMENT..................... 4
Description ......................................................................................................................... 4
Impact.................................................................................................................................. 4
Workaround ........................................................................................................................ 5
EXCEPTION W HEN BUILDING OUTPUT CONFIGURATION ............................................ 5
Description ......................................................................................................................... 5
Impact.................................................................................................................................. 5
Workaround ........................................................................................................................ 5
IDEFINE STAYS IN MEMORY WHEN PROJECT EXPORT FAILS ....................................... 5
Description ......................................................................................................................... 5
Impact.................................................................................................................................. 6
Workaround ........................................................................................................................ 6
IDEFINE HANGS W HEN CONNECTING VIEWER .......................................................... 6
Description ......................................................................................................................... 6
Impact.................................................................................................................................. 6
Workaround ........................................................................................................................ 6

1 Contents
1 ABOUT THE SOFTWARE
iDefine for ProSafe-RS provides an engineering environment for building and
testing safety applications for Yokogawa ProSafe-RS.

Structurally and functionally, this software contains two main interconnected areas:

iDefine Core Components

This area provides common building blocks and functionalities for creating
safety applications.

Yokogawa Extensions

This area provides functionalities for interacting with Yokogawa ProSafe-

RS and AD Suite, allowing data exchanges and communication support.

Those two areas are tightly integrated, to offer a seamless engineering experience
for Yokogawa ProSafe-RS safety application engineers.

This is the first release of iDefine for ProSafe-RS. Its to be used in conjunction
with Yokogawa ProSafe-RS 4.02.

For more information about this software, please go to Yokogawa partner portal
website:

https://partner.yokogawa.com/global/.

2 About The Software

2 THE INSTALLATION PACKAGES
iDefine for ProSafe-RS software, manuals and its maintenance updates will be
provided through Yokogawa partner portal website:

https://partner.yokogawa.com/global/.

The downloadable application package contains the following files.

File Description
The launch program for installing iDefine
Setup.exe
for ProSafe-RS
iDefine_Installer.msi Installer file for iDefine for ProSafe-RS
haspdinst.exe Software license protection runtime

The downloadable manual package contains the following files.

File
iDefine for ProSafe-RS Release Notes.pdf
iDefine SQL Server- Installation Guide.pdf
iDefine - Security Manual.pdf
Description
This document
Installation instructions for iDefine for
ProSafe-RS
Security considerations and measures
for deploying iDefine for ProSafe-RS

Please read iDefine SQL Server- Installation Guide.pdf and iDefine - Security
Manual.pdf carefully before installing the software.

3 The Installation Packages

3 KNOWN LIMITATIONS
This document describes the limitations of the software. Whenever those
limitations are come across during the use of this software, those precautions
should be understood and the suggested procedures should be followed.

File Permissions on IPJ File

Description

When an iDefine project is exported to an IPJ file, the resulting IPJ file may not
be readable by other Windows users or domain users if the IPJ file is in the same
partition as where current User Temp folder exists.

This issue does not occur when the partition of the selected location for IPJ file is
different from where the current User Temp folder exists.

Impact
The IPJ file cannot be read by other Windows or domain users and they cannot
import this file.

Workaround
There are two methods to work around this limitation:

1. The user who created the IPJ file needs to copy the file to a location to which
other Windows users or domain users have read access.

2. The user who created the IPJ file changes the Security settings on that file,
through the file Properties Window through File Explorer.

Program Names in Output Configuration Validation

Document

Description
When there are errors/warnings generated in Output Configuration Validation
Document which include Program column, the text in this column may be suffixed
with an asterisk letter (*).

Impact
Appearances of this letter will not affect the application logic or the software
behaviour other than the Validation document.

4 Known Limitations
Workaround
Please note the possibility of the existence of this limitation, but there is no any
action you should take to address it.

Exception When Building Output Configuration

Description
Very rarely, an error message box may appear when an Output Configuration is
being built, which reports a NullReferenceException. The message box provides
three buttons

Details button to reveal more information about the error,

Continue button to continue use the software, and

Quit button to quit the software.

Impact
When the error occurs, the building process on current POU is interrupted and the
results of the Output Configuration build should be discarded.

There are no other impacts on other parts of the project data, except the building
results of the current Output Configuration.

Workaround
Click the Continue button on the error message box and restart the building
process again by clicking on the Build button.

iDefine Stays in Memory when Project Export Fails

Description

When a file in iDefine project folder is open and locked by another application,
exporting this project will fail. After this happens, later on when you close iDefine,
iDefine might be still in memory, visible in Windows Task Manager. Below are
the occasions this limitation occurs.

When there are connections configured in ProSafe-RS Connection

Management Window.

A document is generated and stored in iDefine project folder and the

document is opened by Microsoft Office Word or other applications.

5 Known Limitations
Impact

When this error occurs, if you start iDefine as a new process and login to the
same project using the same login credentials, iDefine will report that the current
user is already logged in. Therefore, you will not be able to login to the same
project.
When this error occurs, there is no project data loss, because this error occurs
when iDefine is closed by user deliberately.

Workaround

Note that an opened file from iDefine project folder could cause the export
process to fail. Therefore, you should make sure that all the opened project files by
other applications are closed as described below before trying to export the project.
Remove all connections in ProSafe-RS Connection Management Window.
Close Microsoft Office Word or other applications which currently have
opened documents from the current project folder.
When this error occurs, please log off the PC and login again to close iDefine.

iDefine Hangs When Connecting Viewer

Description
When an Output Configuration is connected to iDefine Test Manager and there
are logic items changing values on the active page, selecting a connection for a
Viewer may hang iDefine UI.

Impact

When this happens, iDefine UI stops responding to users inputs. However, the
iDefine application is still alive in memory. You can resolve the situation by
following the procedure described in the Workaround section below.

Workaround
In order to avoid this error, you need select connections for Viewers before
connecting Output Configuration to iDefine Test Manager.

If this error occurs, hover mouse on one of the opened iDefine Windows in
Windows Taskbar and wait for the Thumbnail Previews to appear. Right click on
Viewers Thumbnail Previews and bring up the Windows system menu and
select Close menu item. When Viewer is closed, iDefine returns to normal and
you can continue working. Alternatively, close Viewer (SiEmulate Viewer)
application using Windows Task Manager.

6 Known Limitations
 In terms of iDefine Test Manager, you can still connect to the same Logic
Simulator, SCS Simulator or SCS after the situation is resolved.

7 Known Limitations