OrionLXm

User Manual

February 10, 2015 Document Revision B © 2015 by NovaTech, LLC

OrionLXm

ii

NovaTech, LLC 13555 West 107

th Street

Lenexa, KS 66215 Phone (913) 451-1880 www.novatechweb.com

orion.support@novatechweb.com orion.sales@novatechweb.com

© Copyright 2009, 2015 by NovaTech, LLC

All Rights Reserved. All NovaTech trademarks are owned by NovaTech, LLC. All other trademarks are the property of their respective owners.

The NovaTech Configuration Director (NCD) software may be installed on multiple computers as needed under the following conditions:

The computers must be owned by the end user or its subsidiary. The NCD installation must be used for an Orion-related project.

All files installed by NCD are protected by copyright and may not be shared with any third party. By installing NCD on a computer, you agree to these terms and conditions.

Disclaimer

This manual contains information that is correct to the best of NovaTech's knowledge. It is intended to be a guide and should be used as such. It should not be considered a sole source of technical instruction, replacing good technical judgment, since all possible situations cannot be anticipated. If there is any question as to the installation, configuration, or use of this product, contact NovaTech, LLC at (913) 451-1880. To ensure that the equipment described in this User's Manual, as well as all equipment connected to and used with it, operates in a satisfactory and safe manner, all applicable local and national codes that apply to installing and operating the equipment must be followed. Since these codes can vary geographically and can change with time, it is the user's responsibility to determine which codes and standards apply, and to comply with them.

Failure to follow the instructions provided in this manual, and/or failure to comply with applicable codes and safety standards can result in damage to this equipment, damage to connected devices, and/or serious injury to personnel.

All links to external websites have been verified as correct and appropriate at the time of the publication of this document. However, these links and websites, being outside of NovaTech LLC’s control, are subject to change and may no longer be correct. In this case, please contact:

orion.support@novatechweb.com

Authorized Representation – European Union

NovaTech Europe BVBA Kontichsesteenweg 71

2630 Aartselaar, Belgium Phone +32 (3) 458-0807

Fax +32 (3) 458-1817 General information: info.europe@novatechweb.com Technical support: orion.support@novatechweb.com

The CE version of this product is not available for purchase in Switzerland.

OrionLXm

iii

The documentation for the OrionLX, OrionLXm, Orion5r, and Orion5 is structured as follows. OrionLX and OrionLXm

Manual name (see cover page of each manual)

Purpose

Quick Startup Guide Describes out-of-the-box setup for quick installation.

Orion LX User Manual or

OrionLXm User Manual

Description of OrionLX/OrionLXm hardware.

Setup of configuration using NCD (NovaTech Configuration Director)

OrionLX/OrionLXm: o Configuration of OrionLX/OrionLXm features o Runtime features

Functions of Orion MMI console

Setup and operation of the video option (-MMB) (OrionLX only)

OrionLX/OrionLXm Applications Manual

Specific setup and operation of OrionLX features, such as firewall, SFTP access, installation of SSL certificate, access to OrionLX’s SQL database with Microsoft Access® and Excel®, and others.

Software Manuals Software manuals explain all aspects of setup and operation of protocols such as DNP3 master and software options (Archive, Logic, DA Logic, etc.)

Tech Notes Tech Notes provide solutions for general integration, such as scaling or setup of RS-485 networks.

Field Instructions Field Instructions provide step-by-step instructions for installation of new hardware or software in the field.

Orion5r and Orion5

Manual name (see cover page of each manual)

Purpose

Orion5 Hardware Manual Description of Orion5 hardware.

NCD User Manual Setup of configuration using NCD (NovaTech Configuration Director).

Orion MMI User Manual Functions of Orion MMI console.

Software Manuals Software manuals explain all aspects of setup and operation of protocols such as DNP3 master and software options (Archive, Logic, DA Logic, etc.)

Tech Notes Tech Notes provide solutions for general integration, such as scaling or setup of RS485 networks.

Field Instructions Field Instructions provide step-by-step instructions for installation of new hardware or software in the field.

See also Additional Documentation for a list and locations of the recommended reference manuals.

OrionLXm

iv

Styles and Symbols In this document, fonts, text styles and symbols are used to distinguish standard text from keyboard input, program text, GUI messages, and hyperlinks as follows. Warnings and safety notices are indicated with ANSI symbols.

Displayed text or symbol Description

This is normal text. Standard text.

See OrionLX Setup Hyperlink to text in same document.

www.novatechweb.com Hyperlink to website.

orion.support@novatechweb.com Clicking this link starts email client on the PC.

See OrionLX User Manual Document name.

Minimum value Menu item or text displayed by software.

Name of the data point Text to be entered in input field or window.

Save GUI button to be clicked.

if frequency < 60.0 then Program code.

<Enter>, <Ctrl>+<G>, <G> Key to be pressed.

This yellow triangle indicates a warning that

must be observed by the users in order to

avoid possible equipment damage or

personal injury.

This yellow triangle indicates an electrical

hazard.

Electrostatic sensitive device requires proper

handling and grounding procedures to avoid

equipment damage.

DANGER indicates a hazardous situation

which, if not avoided, will result in death or

serious injury.

WARNING indicates a hazardous situation

which, if not avoided, could result in death or

serious injury.

CAUTION indicates a hazardous situation

which, if not avoided, may result in minor or

moderate injury.

Note that depending on the Windows® display settings on the computer running NCD, some of the screen shot details may appear differently than shown in this manual. The screen shots in this manual have been taken using the setting “Windows Classic” which is available on Windows XP®, Windows Vista® and Windows 7®.

OrionLXm

v

Table of Contents

A. Introduction ....................................................................................................................................... A-1

I. Introduction to OrionLX............................................................................................................. A-2

II. Overview of the OrionLXm User Manual ................................................................................. A-3

III. Location of Documentation ...................................................................................................... A-4

IV. Setup of OrionLXm .................................................................................................................... A-5 1. Setup of OrionLXm IP Address .......................................................................................... A-5 2. Setup using NCD ................................................................................................................. A-5 3. Setup using OrionLXm Webpage ...................................................................................... A-6 4. Setup Worksheet ................................................................................................................. A-7 5. Change of Passwords ......................................................................................................... A-7

V. Operation of OrionLXm ........................................................................................................... A-12

B. OrionLXm Hardware ......................................................................................................................... B-1

I. Physical Specifications ............................................................................................................. B-2

II. OrionLXm Options List .............................................................................................................. B-4 Part Number Examples .............................................................................................................. B-6

III. OrionLXm Front Panel ............................................................................................................... B-7 1. Diagnostic LED Description ............................................................................................... B-7 2. Port A Configuration and Diagnostic .............................................................................. B-10 3. Power Connections ........................................................................................................... B-11 4. Digital Input ........................................................................................................................ B-12 5. Alarm Output ...................................................................................................................... B-13 6. Ethernet Ports .................................................................................................................... B-13 7. IRIG-B Port ......................................................................................................................... B-14 8. OrionLXm Optional Cards ................................................................................................ B-15

Type S4 Communication Card ...................................................................................... B-16 Type F4 Communication Card ...................................................................................... B-18 Type IL and IH I/O Cards ................................................................................................ B-18

Inputs ...................................................................................................................... B-19 Outputs ................................................................................................................... B-20

IV. Mounting Instructions ............................................................................................................. B-22

C. NovaTech Configuration Director (NCD) ........................................................................................ C-1

I. Introduction to NovaTech Configuration Director (NCD) ....................................................... C-2 1. Purpose of NCD ................................................................................................................... C-2 2. System Requirements ......................................................................................................... C-3 3. Copyright Information ......................................................................................................... C-3 4. Outline of NCD Chapters .................................................................................................... C-3

II. Installation of NCD ..................................................................................................................... C-5

III. Running NCD .............................................................................................................................. C-9 1. Main Menu ............................................................................................................................ C-9 2. File Menu ............................................................................................................................ C-10 3. Edit Menu ............................................................................................................................ C-14

Updates Tab .................................................................................................................... C-15 General Tab ..................................................................................................................... C-16 Capture Tab .................................................................................................................... C-17

OrionLXm

vi

4. Configure Menu ................................................................................................................. C-18 Standard Software Features ......................................................................................... C-18 Operations in the Port Setup Windows ........................................................................ C-19 General ............................................................................................................................ C-20 Hardware Model Information ......................................................................................... C-21 Serial Ports ..................................................................................................................... C-22 Network ........................................................................................................................... C-24 NKI – Time Interface ....................................................................................................... C-25 Add Ons........................................................................................................................... C-28

Accumulator Freeze .............................................................................................. C-28 Alarm/Archive/Retentive ....................................................................................... C-29 Alias ........................................................................................................................ C-29 Configuration Manager Agent .............................................................................. C-30 Connection Manager Agent .................................................................................. C-31 Data Logger ............................................................................................................ C-31 Orion LEDs ............................................................................................................. C-31 Points Blocking ...................................................................................................... C-32 Pseudo .................................................................................................................... C-32 Pusher ..................................................................................................................... C-32 Sensor ..................................................................................................................... C-32 System Logger ....................................................................................................... C-38 Text Module ............................................................................................................ C-38

Hardware I/O ................................................................................................................... C-39 Built-In Optional I/O ............................................................................................... C-40

Logic ................................................................................................................................ C-47 Math and Logic ....................................................................................................... C-47 Advanced Math and Logic .................................................................................... C-48 LogicPak ................................................................................................................. C-48 Distribution Automation (DA) ............................................................................... C-48 IEC 61131-3 ............................................................................................................. C-48

5. Communications Menu ..................................................................................................... C-49 Communication Window ............................................................................................... C-55

6. Window Menu..................................................................................................................... C-56 7. Help Menu ........................................................................................................................... C-57

Protocol Information ...................................................................................................... C-57 About ............................................................................................................................... C-58

D. OrionLXm Webpage ......................................................................................................................... D-1

I. Introduction ................................................................................................................................ D-2

II. Home Tab .................................................................................................................................... D-6

III. DataValues Tab .......................................................................................................................... D-8 1. View Input Values ................................................................................................................ D-9

Toggle Options ............................................................................................................... D-10 2. Force Input Value .............................................................................................................. D-12 3. Viewing Output Values ...................................................................................................... D-14 4. Force Output Values ......................................................................................................... D-16 5. View Tagging Archive ....................................................................................................... D-18

IV. Devices Tab .............................................................................................................................. D-20

V. Alarms Tab ................................................................................................................................ D-21

VI. Archive Tab ............................................................................................................................... D-23

VII. System Tab ............................................................................................................................... D-26

VIII. Logs Tab ................................................................................................................................... D-31

OrionLXm

vii

IX. Files Tab .................................................................................................................................... D-32 User Files .................................................................................................................................. D-32 Selecting the Active Configuration ........................................................................................ D-34 System Files ............................................................................................................................. D-35

X. Settings Tab .............................................................................................................................. D-36 1. Users ................................................................................................................................... D-38

Password Change .......................................................................................................... D-38 Account Management .................................................................................................... D-38

2. Authentication Rules ......................................................................................................... D-44 User Lockout Rules ........................................................................................................ D-44 Password Rules .............................................................................................................. D-45 Remote Root Login ........................................................................................................ D-46

3. Remote Accounts .............................................................................................................. D-47 4. Firewall ............................................................................................................................... D-51 5. OpenVPN ............................................................................................................................ D-55 6. Key Management ............................................................................................................... D-58

Create Key ....................................................................................................................... D-60 7. System Log ........................................................................................................................ D-61 8. Networking ......................................................................................................................... D-63

Common .......................................................................................................................... D-64 eth0 and eth1 .................................................................................................................. D-65 Advanced Networking .................................................................................................... D-66

9. Modem ................................................................................................................................ D-67 10. System ................................................................................................................................ D-70 11. Serial ................................................................................................................................... D-72 12. WebUI .................................................................................................................................. D-73

Login Message ............................................................................................................... D-74 HMI ................................................................................................................................... D-74 Web Files ......................................................................................................................... D-75 Link Bar ........................................................................................................................... D-76 Sections........................................................................................................................... D-77

13. Alarms ................................................................................................................................. D-79 Notifications .................................................................................................................... D-81 Colors .............................................................................................................................. D-81 Alarm Archive ................................................................................................................. D-81

14. Database ............................................................................................................................. D-82 15. Tagging ............................................................................................................................... D-84 16. Cascading Slave ................................................................................................................ D-88 17. Services .............................................................................................................................. D-89 18. Scheduler ........................................................................................................................... D-90

Scheduling Tasks ........................................................................................................... D-91 Add CSV Task ................................................................................................................. D-94 Add FileMover Task ....................................................................................................... D-95

E. OrionLXm MMI .................................................................................................................................. E-1

I. Introduction ................................................................................................................................ E-2

II. Connecting to the Orion MMI .................................................................................................... E-3 1. OrionLXm Port A ................................................................................................................. E-3 2. Connecting to the OrionLXm with NCD ............................................................................ E-3 3. Unlocking a User Account .................................................................................................. E-3

III. MMI Menus .................................................................................................................................. E-4 1. File Menu .............................................................................................................................. E-5

File Transfer (PC -> ORION) ............................................................................................ E-5 File Transfer (ORION -> PC) ............................................................................................ E-7

OrionLXm

viii

Make Config File Active ................................................................................................... E-8 Delete a File ...................................................................................................................... E-9 View a File ....................................................................................................................... E-10 Install Downloaded Packages ....................................................................................... E-11

2. Data Menu ........................................................................................................................... E-12 View Input Values ........................................................................................................... E-13 View Output Values ........................................................................................................ E-17 Override Input Values .................................................................................................... E-18 Clear Input Override ....................................................................................................... E-21 Send Output Values ....................................................................................................... E-22

3. View Communications ...................................................................................................... E-25 Master Port Troubleshooting ........................................................................................ E-28 Slave Port Troubleshooting .......................................................................................... E-29

4. Device Statistics ................................................................................................................ E-30 5. System Menu...................................................................................................................... E-31

Clock Configuration ....................................................................................................... E-32 View System Info ............................................................................................................ E-33 View Event Log ............................................................................................................... E-34 Clear Event Log .............................................................................................................. E-34 View Version Info ........................................................................................................... E-35 Passthrough Menu ......................................................................................................... E-36 Thread Info ...................................................................................................................... E-38 Restart ............................................................................................................................. E-40

6. Disconnect ......................................................................................................................... E-40 7. Session Timeouts .............................................................................................................. E-41 8. Network Menu .................................................................................................................... E-42

View/Change Network Configuration ........................................................................... E-43 Start/Stop Firewall .......................................................................................................... E-46

F. Glossary ............................................................................................................................................ F-1

G. Additional Documentation ............................................................................................................... G-3

List of Figures

Figure A-1: Documentation in Windows XP ......................................................................................... A-4 Figure A-2: Documentation in Windows Vista and Windows 7 (classic view) ................................. A-4 Figure B-1: OrionLXm Front Panel with Two Serial Communication Cards (Option S4S4) ............ B-7 Figure B-2: Port A Location ................................................................................................................. B-10 Figure B-3: OrionLXm Power Connection .......................................................................................... B-11 Figure B-4: Ground Lug ........................................................................................................................ B-11 Figure B-5: OrionLXm Digital Input Connection ................................................................................ B-12 Figure B-6: OrionLXm Digital Output Connection ............................................................................. B-13 Figure B-7: Dual Ethernet Ports .......................................................................................................... B-13 Figure B-8: IRIG-B Port ......................................................................................................................... B-14 Figure B-9: Card Jumpers for Slot Addressing ................................................................................. B-15 Figure B-10: OrionLXm with ST Fiber Serial Ports ............................................................................ B-18 Figure B-11: OrionLXm with I/O Card ................................................................................................. B-18 Figure B-12: Input Circuit ..................................................................................................................... B-19 Figure B-13: IL and IH Circuit Board ................................................................................................... B-20 Figure B-14: 19" Rack Mount Options ................................................................................................ B-22

OrionLXm

ix

Figure B-15: Dual Mount Option .......................................................................................................... B-22 Figure B-16: Conventional Horizontal Panel Mount .......................................................................... B-22 Figure B-17: Horizontal Mount - Top of Panel and Bottom of Panel Options ................................. B-23 Figure B-18: Vertical Panel Mount Options ........................................................................................ B-23 Figure B-19: Vertical DIN Rail Mount .................................................................................................. B-23 Figure C-1: Access to NCD and OrionLXm Documentation in Windows

® XP .................................. C-4

Figure C-2: Access to NCD and OrionLXm Documentation in Windows Vista® or Windows 7.0

® . C-4

Figure C-3: NCD Installation .................................................................................................................. C-5 Figure C-4: Starting NCD Windows Vista

® or Windows 7.0

® .............................................................. C-5

Figure C-5: Starting NCD in Windows® XP ........................................................................................... C-6

Figure C-6: NCD Program Directory Structure..................................................................................... C-6 Figure C-7: NCD Data Directory Structure ............................................................................................ C-7 Figure C-8: NCD Main Menu ................................................................................................................... C-9 Figure C-9: File Menu ............................................................................................................................ C-10 Figure C-10: Selecting Configuration for Save, Save As, Close ...................................................... C-10 Figure C-11: Convert Operations ........................................................................................................ C-10 Figure C-12: Reorder Network Ports ................................................................................................... C-12 Figure C-13: Selection of Standard / Cascaded Configuration ........................................................ C-12 Figure C-14: NCD Prompt for Logic File ............................................................................................. C-13 Figure C-15: Edit Menu ......................................................................................................................... C-14 Figure C-16: User Settings – Updates Tab ......................................................................................... C-14 Figure C-17: User Settings – General Tab .......................................................................................... C-16 Figure C-18: User Settings – Capture Tab .......................................................................................... C-17 Figure C-19: Configure Menu ............................................................................................................... C-18 Figure C-20: Port Operations ............................................................................................................... C-19 Figure C-21: Choose port for protocol ................................................................................................ C-19 Figure C-22: General Settings.............................................................................................................. C-20 Figure C-23: OrionLXm Hardware Configuration .............................................................................. C-21 Figure C-24: Port Selection .................................................................................................................. C-22 Figure C-25: Serial Protocol Selection Menu ..................................................................................... C-23 Figure C-26: Network Parameter and Port Configuration ................................................................. C-24 Figure C-27: Network Protocol Selection Menu ................................................................................. C-24 Figure C-28: NKI – Time Interface Setup ............................................................................................ C-25 Figure C-29: NKI – Port Setup .............................................................................................................. C-27 Figure C-30: Add On Options............................................................................................................... C-28 Figure C-31: Alias Assignment ............................................................................................................ C-29 Figure C-32: Orion LED Module ........................................................................................................... C-31 Figure C-33: Sensor Setup - Port Tab ................................................................................................. C-33 Figure C-34: Sensor Setup - Inputs Tab ............................................................................................. C-33 Figure C-35: Hardware I/O .................................................................................................................... C-39 Figure C-36: Optional I/O Configuration ............................................................................................. C-40 Figure C-37: IIO Port Setup .................................................................................................................. C-40 Figure C-38: IIO Device Setup .............................................................................................................. C-41 Figure C-39: IIO Inputs Setup .............................................................................................................. C-42 Figure C-40: Configured IIO Input Points ........................................................................................... C-43 Figure C-41: IIO Outputs Setup ........................................................................................................... C-44 Figure C-42: Output Point Type Setup ................................................................................................ C-46 Figure C-43: Logic Options .................................................................................................................. C-47 Figure C-44: NCD Communications .................................................................................................... C-49 Figure C-45: Manage Connections ...................................................................................................... C-50 Figure C-46: Creating/Saving/Loading Connection Files ................................................................. C-52 Figure C-47: Connection Information ................................................................................................. C-53 Figure C-48: NCD Comm Window ....................................................................................................... C-55 Figure C-49: Window Menu .................................................................................................................. C-56 Figure C-50: Help Menu ........................................................................................................................ C-57

OrionLXm

x

Figure C-51: Protocol Information ....................................................................................................... C-57 Figure C-52: NCD Version Information ............................................................................................... C-58 Figure D-1: Connect with OrionLXm ..................................................................................................... D-2 Figure D-2: Internet Explorer Security Warning .................................................................................. D-2 Figure D-3: Firefox Security Warning ................................................................................................... D-3 Figure D-4: Confirm Firefox Certificate ................................................................................................. D-3 Figure D-5: OrionLXm Login .................................................................................................................. D-4 Figure D-6: OrionLXm Homepage ......................................................................................................... D-4 Figure D-7: OrionLXm Unlock Prompt .................................................................................................. D-5 Figure D-8: OrionLXm Home Tab .......................................................................................................... D-6 Figure D-9: DataValues – Main Page ..................................................................................................... D-8 Figure D-10: DataValues – View Input Values ...................................................................................... D-9 Figure D-11: DataValues – Toggle Options ........................................................................................ D-10 Figure D-12: DataValues – Force Input Value .................................................................................... D-12 Figure D-13: DataValues – Select Output Values .............................................................................. D-14 Figure D-14: DataValues – View Output Values ................................................................................. D-15 Figure D-15: DataValues – Force Output Value ................................................................................. D-16 Figure D-16: DataValues - View Tagging Archive .............................................................................. D-18 Figure D-17: DataValues - Applied Tags ............................................................................................. D-19 Figure D-18: Devices Page ................................................................................................................... D-20 Figure D-19: Alarms Tab ....................................................................................................................... D-21 Figure D-20: Alarm Archive with Filter ................................................................................................ D-21 Figure D-21: Alarm Archive without Filter .......................................................................................... D-22 Figure D-22: Archive - 1000 Most Recent Records ............................................................................ D-23 Figure D-23: Archive with Custom Filter ............................................................................................ D-24 Figure D-24: Archive – View Trending ................................................................................................ D-25 Figure D-25: Archive – Trend for Multiple Data Points ..................................................................... D-25 Figure D-26: System Page .................................................................................................................... D-26 Figure D-27: System Page .................................................................................................................... D-27 Figure D-28: System Page .................................................................................................................... D-28 Figure D-29: System Page .................................................................................................................... D-29 Figure D-30: System Page .................................................................................................................... D-29 Figure D-31: Logs Page ........................................................................................................................ D-31 Figure D-32: Files Page ........................................................................................................................ D-32 Figure D-33: Send Files to OrionLXm ................................................................................................. D-33 Figure D-34: Select Active Configuration ........................................................................................... D-34 Figure D-35: Confirmation Prompt ...................................................................................................... D-34 Figure D-36: System Files .................................................................................................................... D-35 Figure D-37: Settings Page .................................................................................................................. D-36 Figure D-38: Change User Password .................................................................................................. D-38 Figure D-39: Settings/Users ................................................................................................................. D-39 Figure D-40: User Account Management ............................................................................................ D-41 Figure D-41: Authentication Rules – User Lockout Rules ................................................................ D-44 Figure D-42: Authentication Rules – Password Rules ...................................................................... D-45 Figure D-43: Authentication Rules – Remote Root Login ................................................................. D-46 Figure D-44: SSSD Package is Installed ............................................................................................. D-47 Figure D-45: Verification of Available File System Space ................................................................ D-47 Figure D-46: Remote Accounts ........................................................................................................... D-48 Figure D-47: Remote Accounts ........................................................................................................... D-49 Figure D-48: sysfiles.zip ....................................................................................................................... D-50 Figure D-49: Firewall Settings.............................................................................................................. D-51 Figure D-50: Firewall Filter Options .................................................................................................... D-52 Figure D-51: OpenVPN Settings .......................................................................................................... D-55 Figure D-52: Key Management Settings ............................................................................................. D-58 Figure D-53: Default Key Values .......................................................................................................... D-59

OrionLXm

xi

Figure D-54: Create New Key ............................................................................................................... D-60 Figure D-55: System Log Setup ........................................................................................................... D-61 Figure D-56: Networking Settings ....................................................................................................... D-63 Figure D-57: Static Route Configuration ............................................................................................ D-66 Figure D-58: Modem Settings .............................................................................................................. D-67 Figure D-59: System Settings .............................................................................................................. D-70 Figure D-60: Serial Ports Setup ........................................................................................................... D-72 Figure D-61: WebUI Setup .................................................................................................................... D-73 Figure D-62: Custom Login Message .................................................................................................. D-74 Figure D-63: Small Text in Header and Link Bar ................................................................................ D-74 Figure D-64: Large Text in Header and Link Bar ............................................................................... D-74 Figure D-65: Control Dialog with Tag Information ............................................................................. D-75 Figure D-66: Control Dialog without Tag Information ....................................................................... D-75 Figure D-67: Set Link to User-defined .svg File ................................................................................. D-75 Figure D-68: Link to User-defined .svg File ........................................................................................ D-76 Figure D-69: Link Bar Example ............................................................................................................ D-76 Figure D-70: Link Bar Setup ................................................................................................................. D-76 Figure D-71: Webpage Access Security and Display Options ......................................................... D-77 Figure D-72: Link Bar and Header Settings ........................................................................................ D-78 Figure D-73: Alarm Archive Settings .................................................................................................. D-80 Figure D-74: Database Settings ........................................................................................................... D-82 Figure D-75: Add Database User ......................................................................................................... D-83 Figure D-76: Tag List ............................................................................................................................ D-84 Figure D-77: Add New Tag ................................................................................................................... D-85 Figure D-78: Tagging Button in Graphics ........................................................................................... D-86 Figure D-79: Setting a Standard Tag ................................................................................................... D-87 Figure D-80: Setting a Custom Tag ..................................................................................................... D-87 Figure D-81: Cascading Slave ............................................................................................................. D-88 Figure D-82: Services Settings ............................................................................................................ D-89 Figure D-83: Scheduler – Task List ..................................................................................................... D-90 Figure D-84: Task Scheduling.............................................................................................................. D-91 Figure D-85: Task Example – Daily at 00:05 ....................................................................................... D-93 Figure D-86: Task Example – Every Three Hours .............................................................................. D-93 Figure D-87: Task List Example ........................................................................................................... D-93 Figure D-88: CSV Task Parameters ..................................................................................................... D-94 Figure D-89: FileMover Task Parameters ........................................................................................... D-95 Figure E-1: OrionLXm MMI Main Menu ................................................................................................. E-4 Figure E-2: OrionLXm File Menu ........................................................................................................... E-5 Figure E-3: File Transfer to OrionLXm Using NCD .............................................................................. E-6 Figure E-4: File Transfer to OrionLXm Using Terminal Software ...................................................... E-6 Figure E-5: File Transfer OrionLXm to PC ............................................................................................ E-7 Figure E-6: File Transfer to PC Using Terminal Software ................................................................... E-8 Figure E-7: Configuration File Selection .............................................................................................. E-8 Figure E-8: Make Selected Configuration File Active .......................................................................... E-9 Figure E-9: Delete File from Flash Memory .......................................................................................... E-9 Figure E-10: Select File for Viewing .................................................................................................... E-10 Figure E-11: View File ........................................................................................................................... E-11 Figure E-12: Package Menu ................................................................................................................. E-11 Figure E-13: Data Menu ........................................................................................................................ E-12 Figure E-14: Select Port for Input Point Monitoring .......................................................................... E-13 Figure E-15: Input Point Monitoring .................................................................................................... E-14 Figure E-16: Data View Column Editor ............................................................................................... E-15 Figure E-17: Data View Sort Editor ...................................................................................................... E-16 Figure E-18: Select Port for Output Monitoring ................................................................................. E-17 Figure E-19: Output Point Monitoring ................................................................................................. E-17

OrionLXm

xii

Figure E-20: Select Port for Forcing Input Values ............................................................................. E-18 Figure E-21: Select Input Point ............................................................................................................ E-19 Figure E-22: Force Input Point ............................................................................................................. E-19 Figure E-23: Enter Input Point Value ................................................................................................... E-20 Figure E-24: Remove Forced Input Value ........................................................................................... E-21 Figure E-25: Clear Input Override ........................................................................................................ E-21 Figure E-26: Select Port for Forcing Output Values .......................................................................... E-22 Figure E-27: Select Point for Forcing Output Value .......................................................................... E-23 Figure E-28: Forcing Output Value ...................................................................................................... E-23 Figure E-29: Entering Forced Output Value ....................................................................................... E-24 Figure E-30: Communications Menu ................................................................................................... E-25 Figure E-31: Viewing Communications .............................................................................................. E-26 Figure E-32: Communications Display Options................................................................................. E-27 Figure E-33: Device Statistics .............................................................................................................. E-30 Figure E-34: System Menu ................................................................................................................... E-31 Figure E-35: Clock Configuration ........................................................................................................ E-32 Figure E-36: System Information ......................................................................................................... E-33 Figure E-37: View Event Log ................................................................................................................ E-34 Figure E-38: Version Information ........................................................................................................ E-35 Figure E-39: Passthrough Menu .......................................................................................................... E-36 Figure E-40: Passthrough Window to Relay ...................................................................................... E-37 Figure E-41: Thread Info ....................................................................................................................... E-39 Figure E-42: Restart Menu.................................................................................................................... E-40 Figure E-43: Session Timeouts ........................................................................................................... E-41 Figure E-44: Network Menu .................................................................................................................. E-42 Figure E-45: View/Change Network Configuration ............................................................................ E-43 Figure E-46: Edit Common Parameters .............................................................................................. E-44 Figure E-47: Edit Port-Specific Parameters ........................................................................................ E-45 Figure E-48: Start/Stop Firewall ........................................................................................................... E-46

List of Tables Table A-1: Manual Overview .................................................................................................................. A-3 Table A-2: Feature Configuration Overview ....................................................................................... A-11 Table A-3: OrionLXm – Webpage and MMI Overview ....................................................................... A-12 Table B-1: OrionLXm Front Panel Diagnostic LEDs ............................................................................ B-9 Table B-2: Port A USB Communications Parameters ....................................................................... B-10 Table B-3: Digital Input Terminal Header ............................................................................................ B-12 Table B-4: Digital Input Turn-On Voltages and Current Draw .......................................................... B-12 Table B-5: Digital Output Connection ................................................................................................. B-13 Table B-6: OrionLXm Optional Cards ................................................................................................. B-15 Table B-7: Card Jumpers for Slot Addressing ................................................................................... B-16 Table B-8: RS-232 Pinout ..................................................................................................................... B-16 Table B-9: RS-485 Half Duplex Pinout ................................................................................................ B-17 Table B-10: RS-485/422 Full Duplex Pinout ........................................................................................ B-17 Table B-11: Input Terminal Numbering for I/O Card in Upper Slot .................................................. B-19 Table B-12: Input Terminal Numbering for I/O Card in Lower Slot .................................................. B-19 Table B-13: Input Voltage Range Jumpers ......................................................................................... B-19 Table B-14: Output Terminal Numbering for I/O Card in Upper Slot ............................................... B-20 Table B-15: Output Terminal Numbering for I/O Card in Lower Slot ............................................... B-20

OrionLXm

xiii

Table B-16: Contact Monitoring Jumpers and Leakage Current...................................................... B-21 Table C-1: NCD Program Directory Structure ...................................................................................... C-7 Table C-2: NCD Data Directory Structure ............................................................................................. C-8 Table C-3: NCD Main Menu .................................................................................................................... C-9 Table C-4: NCD File Menu .................................................................................................................... C-12 Table C-5: Port Operations ................................................................................................................... C-19 Table C-6: General Settings ................................................................................................................. C-20 Table C-7: Orion Ports .......................................................................................................................... C-23 Table C-8: NKI – Time Interface Data Points ...................................................................................... C-26 Table C-9: NKI – Time Interface Parameters ...................................................................................... C-27 Table C-10: NKI – Port Setup ............................................................................................................... C-27 Table C-11: Alias File Format ............................................................................................................... C-30 Table C-12: Sensor Setup..................................................................................................................... C-37 Table C-13: IIO Port Setup .................................................................................................................... C-41 Table C-14: IIO Device Setup ............................................................................................................... C-42 Table C-15: Configured IIO Input Points ............................................................................................. C-44 Table C-16: Outputs Setup ................................................................................................................... C-45 Table C-17: Manage Connections ....................................................................................................... C-51 Table C-18: Connection Information ................................................................................................... C-54 Table C-19: NCD Comm Window ......................................................................................................... C-55 Table D-1: OrionLXm Homepage Menu Items ...................................................................................... D-5 Table D-2: OrionLXm Home Tab ............................................................................................................ D-7 Table D-3: DataValue – Browsing Pages .............................................................................................. D-9 Table D-4: DataValues – Input Point Display Options ....................................................................... D-11 Table D-5: Data Values – Force Input Values ..................................................................................... D-13 Table D-6: Data Values – Force Output Values .................................................................................. D-17 Table D-7: Data Values - Tagging Archive .......................................................................................... D-19 Table D-8: System Page Information .................................................................................................. D-30 Table D-9: OrionLXm File Types .......................................................................................................... D-33 Table D-10: Settings Page .................................................................................................................... D-37 Table D-11: User Account Management ............................................................................................. D-40 Table D-12: User Groups ...................................................................................................................... D-43 Table D-13: User Lockout Rules .......................................................................................................... D-44 Table D-14: Password Rules ................................................................................................................ D-46 Table D-15: Firewall Settings ............................................................................................................... D-54 Table D-16: Common OpenVPN Settings ........................................................................................... D-56 Table D-17: OpenVPN Client Settings ................................................................................................. D-56 Table D-18: OpenVPN Server Settings ................................................................................................ D-57 Table D-19: Key Management Settings ............................................................................................... D-59 Table D-20: System Log Setup ............................................................................................................ D-62 Table D-21: Common Network Settings .............................................................................................. D-64 Table D-22: Network Settings for eth0 and eth1 ................................................................................ D-65 Table D-23: Static Route Parameters .................................................................................................. D-66 Table D-24: Modem Settings ................................................................................................................ D-69 Table D-25: System Settings ................................................................................................................ D-71 Table D-26: Serial Port Setup ............................................................................................................... D-72 Table D-27: HMI Setup Parameters ..................................................................................................... D-74 Table D-28: Section Parameters .......................................................................................................... D-78 Table D-29: Section Parameters .......................................................................................................... D-81 Table D-30: Database Settings ............................................................................................................ D-83 Table D-31: Standard Tags ................................................................................................................... D-84 Table D-32: Tag Fields .......................................................................................................................... D-86 Table D-33: Scheduler – Task List ....................................................................................................... D-90 Table D-34: Task Scheduling ............................................................................................................... D-92

OrionLXm

xiv

Table D-35: CSV Task Parameters ...................................................................................................... D-94 Table D-36: FileMover Task Parameters ............................................................................................. D-95 Table E-1: Serial/Ethernet Cables and Software .................................................................................. E-2 Table E-2: OrionLXm File Types ............................................................................................................ E-7 Table E-3: Data Point Information ....................................................................................................... E-15 Table E-4: Force Input Point Parameters ............................................................................................ E-20 Table E-5: Force Output Point Parameters ......................................................................................... E-24 Table E-6: Master Port Troubleshooting ............................................................................................. E-28 Table E-7: Slave Port Troubleshooting ............................................................................................... E-29 Table E-8: System Information ............................................................................................................ E-33 Table E-9: Common Parameters .......................................................................................................... E-44 Table E-10: Port-Specific Parameters ................................................................................................. E-45 Table F-1: Glossary .................................................................................................................................. F-2 Table G-1: NovaTech Documentation ................................................................................................... G-4

OrionLXm

A-1

A. Introduction

OrionLXm

A-2

I. Introduction to OrionLX The OrionLX is a multi-port automation platform. It is designed to operate all ports independently of one another. Each port can support a unique communications protocol:

Master mode - connected to Intelligent Electronic Devices (IED’s) or other slave devices

Slave mode - connected to Supervisory Control and Data Acquisition Masters (SCADA), or Human Machine Interfaces (HMI’s)

Each port provides its own communication timing. All ports use a common database, which makes data from all ports available to any other port. The OrionLX also provides a logic processor and logging/archiving capabilities. For practical purposes, the capability of communications with multiple IEDs and SCADA Masters make the OrionLX a powerful RTU. The OrionLX acquires data from IEDs and stores this data for polls by SCADA. SCADA commands are routed to the target IED for appropriate action. The OrionLX automation platform is designed to interface with:

IEDs from all major relay control and meter vendors using ASCII or binary protocols

PLCs from major vendors

Other devices and meters The OrionLXm base unit comes with the following features:

Diagnostics/configuration USB Type B port (port A)

One digital input

One digital output (Alarm)

IRIG-B

Two copper Ethernet ports (ETH0, ETH1)

Up to two communication cards or I/O cards can be added in any combination as follows:

­ Communication card with four DB9 ports which can be configured for RS-232, RS-485, and RS-422

­ Communication card with three DB9 ports which can be configured for RS-232, RS-485, and RS-422, and one bit protocol port

­ Communication card with four ST fiber ports

­ I/O card with 12 input points and 4 output points

OrionLXm

A-3

II. Overview of the OrionLXm User Manual

Section Title Content

A Introduction General description of the OrionLXm device, documentation, and setup information.

B OrionLXm Hardware Description of the OrionLXm hardware, dimensions, and electrical characteristics including port information.

C NovaTech Configuration Director (NCD)

How to use NCD, the primary tool for configuring the OrionLXm. NCD requires a PC that is running the Windows® operating system.

D OrionLXm Webpage This section details how to use the OrionLXm webpage to setup the diverse advanced features of the OrionLXm.

E OrionLXm MMI Describes setup of the OrionLXm’s IP address and configuration of the MMI using the RS-232 or USB port for monitoring the runtime operations of the OrionLXm.

F Glossary Description of terminology.

G Additional Documentation Additional documentation that may be helpful in setting up and using the OrionLXm device.

Table A-1: Manual Overview

OrionLXm

A-4

III. Location of Documentation All manuals are installed as .pdf files on the PC’s hard drive during the installation process described in chapter Installation of NCD. Once the installation of NCD has been completed, the folder containing the OrionLXm manuals can be accessed through the Windows

® Start menu by using the following path:

Windows XP® - Start/Programs/NovaTech NCD3/NCD Documentation

Windows Vista® or Windows 7

® - Start/All Programs/NovaTech NCD3/NCD Documentation

Figure A-1: Documentation in Windows XP

Figure A-2: Documentation in Windows Vista and Windows 7 (classic view)

The NCD documentation files may be accessed on the NCD installation CD, or in the .zip file as downloaded from the NovaTech Support Site.

OrionLXm

A-5

IV. Setup of OrionLXm The OrionLXm provides a number of hardware and software features that are basically set up in two stages using the NovaTech Configuration Director (NCD) and OrionLXm Webpage. This chapter is intended to assist users in setting up the OrionLXm most efficiently in terms of required OrionLXm features and available engineering resources. The NCD Communications window, or any communication software such as Hyperterminal, can be used to connect to the OrionLXm. A web browser is required to access the OrionLXm Webpage. Once connected to the OrionLXm, configuration files, download archives and logs, and new firmware can be transferred to/from the OrionLXm. In addition, the firewall can be configured, data values forced, and communication on any of the communication ports can be logged. The following sections show each feature of the OrionLXm and the respective tool used for the setup of each feature. This allows planning of the most efficient setup. Each entry in the table is a hyperlink to the respective section in this manual to provide easy navigation.

1. Setup of OrionLXm IP Address As a factory setting, both Ethernet interfaces are configured to use DHCP to obtain IP addresses. In general, static IP addresses must be assigned to each of the OrionLXm’s Ethernet ports. First, connect to Port A1 (serial port) or A2 (USB port) of the OrionLXm to set up Ethernet port 0 (ETH0). Setting up this connection to the OrionLXm is described in chapter Communications Menu. Then set up the IP address for ETH0 as described in the Network Menu of the OrionLXm's MMI. Once the IP address of ETH0 has been set to a known address, the OrionLXm webpage can be used to configure all remaining network settings as described in chapter Networking.

2. Setup using NCD The full configuration for an OrionLXm can be created using NovaTech Configuration Director (NCD), even before the OrionLXm is received on site. The following features are configured with NCD:

Selection of OrionLXm hardware and port setup

General setup and debug features (forcing I/O)

Synchronous and asynchronous protocols using RS-232 ports and fiber ports, including device properties and I/O point lists

TCP protocols including setup of device properties and I/O lists

Data points for network time protocols/IRIG-B

System/Point Logger (standard software feature)

OrionLED (standard feature)

Sensor Master (standard feature)

Text Module

Orion Math and Logic/Advanced Orion Math and Logic

NCD configures the programmable elements that pertain to the applications within the OrionLXm, such as communication ports, software features, devices, points lists, logic, etc. If there are several departments

OrionLXm

A-6

involved in the OrionLXm setup, the parameters of the programmable elements are typically determined by the engineering, substation, or communications department. The configuration created by the NCD is an ASCII text file, which describes the entire OrionLXm configuration. Therefore, if a large number of OrionLXm's have to be configured, the configuration files can also be created by programming scripts, which use the point and device data already available in the customer engineering department. Once a configuration has been created, it can be loaded into an OrionLXm using either the OrionLXm’s serial MMI port, or the Ethernet port. Note: Before connecting to the OrionLXm for the first time using an Ethernet port, the

OrionLXm’s IP address must first be set by connecting to the serial MMI port (see View/Change Network Configuration).

NCD can be mailed on a CD, or it can be downloaded from the OrionLX Support website (http://www.novatech-llc.com/cgi-bin/login.pl) as soon as the customer account has been set up.

3. Setup using OrionLXm Webpage The features configured with the OrionLXm Webpage are operational features and security features that are typically set up by, or in cooperation with, an IT department.

Time Synchronization: IRIG-B, UTC/Local, Modulated/Unmodulated, NTP Time Source, Time Zone

User Management: Manage users, set rights, allowed services, allowed operations, clearances

Authentication: Lockout rules, password rules, LDAP setup, Remote Root Login

Networking: Set host name, DNS, DHCP, Gateway, IP, Subnet, Media

Firewall: Set input, output, and forwarding rules, start firewall

VPN: Start option, client/server, TCP/UDP, port, cipher, key, server IP address, clients

Key Management: Create and manage key, certificates

Services: Allow/Disallow Telnet, FTP, HTTP

OrionLXm

A-7

4. Setup Worksheet The following worksheet in Table A-2 assists in configuring an OrionLXm most efficiently. The Feature column describes the features offered by the OrionLXm. For each feature, the respective configuration tool is described in columns Offline Configuration with NCD or Online Configuration with Webpage. Steps in columns Offline Configuration with NCD and Online Configuration with Webpage can be performed one after the other by the same engineers, or in parallel. For example, the Substation Department can use NCD to set up field devices and I/O lists, while the IT Department can set up the OrionLXm’s network settings using the OrionLXm’s webpage. Before the OrionLXm’s webpage can be accessed with a web browser, the OrionLXm’s IP address must be configured. This is done as described in chapter Network Menu of the OrionLXm MMI. It requires a serial port, and the NovaTech serial cable included with OrionLXm, or a USB port and USB cable. Drivers for the USB connection may be downloaded from the OrionLXm support webpage. To use Alarm/Archive/Retentive the database must be enabled and reset from the webpage. Once the Offline Configuration with NCD is completed, the .ncd file created by NCD must be transferred to the OrionLXm. This can be done using a serial connection or an Ethernet connection between the PC and the OrionLXm.

5. Change of Passwords In the course of, or after completing the setup of the OrionLXm, the default passwords must be changed in order to establish secure operations. This is explained in chapter Password Change.

OrionLXm

A-8

Item Feature Step Offline Configuration with NCD

Step Online Configuration with Webpage

001 Hardware Configuration

Select the correct OrionLXm.

Hardware Model Information

Select OrionLXm

002 Serial Protocols

DNP3, SEL, Modbus, etc.

Serial Ports

For port 1 through 16, specify protocol, poll type (master/slave), then port parameters and list of points.

*

003 IP/Network Protocols

DNP3, SEL, Modbus, etc.

Network

Then specify protocol, poll type (master/slave), port parameters and list of points. Up to 96 ports can be configured.

*

004 Force Inputs/Outputs

Allow/Disallow forcing of I/O points through OrionLXm MMI/Webpage for Troubleshooting, etc.

General Users grants or disallows each individual user the ability to force I/O points through the OrionLXm Webpage.

005 Archive

Archive I/O points, and view archived values with web browser, and transfer .csv file to PC for further processing.

Alarm/Archive/Retentive

Refer to Alarm/Archive/ Retentive Module for OrionLX Software Manual.

006 Pseudo Master

When two master stations need to exchange data, set up two corresponding slave ports on the OrionLXm, and the Pseudo Master.

Refer to Pseudo Master for Orion Manual.

007 Data Logger

Logs long events from

SEL relays connected to the OrionLXm to the OrionLXm’s expanded memory. Files are transferred to PC with NTFTP.

Data Logger

Refer to Data Logger for Orion Manual.

008 System Logger

OrionLXm system events (e.g. startup) and point changes are logged to OrionLXm’s flash memory.

System Logger

Refer to the System & Point

Logger for Orion Manual.

* Refer to specific manual for detailed description of setup.

OrionLXm

A-9

Item Feature Step

Offline Configuration with NCD

Step Online Configuration with Webpage

010 Pusher Slave

When two slave devices (PLCs, IEDs, etc.) need to exchange data, set up two corresponding master ports on the OrionLXm, and the Pusher Slave.

Pusher

Refer to Pusher Slave for Orion Manual.

011 OrionLXm LEDs

OrionLXm’s LED on front panel can be configured for specific uses.

Orion LEDs

This feature is set up automatically.

012 Text Module

Based on user-specified I/O changes, the OrionLXm creates event-specific text messages for further processing.

Text Module

Refer to Text Module for Orion Manual.

013 Monitor OrionLXm

Hardware

Monitor essential OrionLXm Status: Firewall, Alarm, internal voltages, and temperature.

See Sensor for automatic setup of OrionLXm status points.

014 OrionLXm I/O Points

The OrionLXm provides built-in SER capable discrete I/O.

Built-In Optional I/O for setup of I/O points.

015 Logic Functions

The OrionLXm provides freely programmable logic, prepacked logic functions, and IEC 61131.

Full logic package: Math and Logic and Logic for Orion Manual

Prepackaged logic: LogicPak and LogicPak for Orion

Manual

IEC 61131: IEC 61131 for OrionLX Software Manual

015 IRIG-B/NTP

Set up time-related points (e.g. time quality), IRIG-B settings, NTP time source, and time zone.

NKI – Time Interface

Time-related points, such as

OrionLX Time Quality,

OrionLX PLL Status, etc.

are set up automatically.

System

for setting up Time Zone, IRIG-B, Modulated/ Unmodulated, NTP Time Source

016 User Accounts

Manage users, set passwords and rights, allowed services and operations, account expiration, menu or command line upon login.

Users

OrionLXm

A-10

Item Feature Step Offline Configuration with NCD

Step Online Configuration with Webpage

017 Authentication Rules

Lockout rules, password rules, enable remote login.

Authentication Rules

018 Remote Accounts

Account caching, LDAP, Kerberos setup.

Remote Accounts

019 Firewall

Set input, output, and forwarding rules; start/stop firewall.

Firewall

020 OpenVPN

Settings for start-up, client, server, port, cipher, compression, etc.

OpenVPN

021 Key Management

Create and manage keys, upload key files from computer to OrionLXm.

Key Management

022 System Log

Setup for system log host and logged events.

System Log

023 Networking

Common and per-port settings: host name, IP addresses, DHCP, etc.

Networking

024 Modem

Setup of modem port.

Modem

025 System

Setup of IRIG-B, NTP time sources, and time zone.

System

026 Serial

Setup of serial ports for RS-232 or RS-485.

Serial

027 Web User Interface

Setup of login message, links to custom pages, web by-page access control, webpage appearance, etc.

WebUI

028 Alarms

Setup of alarm displays, colors, alarm archive data.

Alarms

029 Database

Database management and remote access setup.

Database

030 Tagging

Tag setup and management.

Tagging

OrionLXm

A-11

Item Feature Step Offline Configuration with NCD

Step Online Configuration with Webpage

031 Cascading OrionLXm

IP and key parameters for cascaded slave OrionLXm.

Cascading

032 Services

Enable/disable Telnet, FTP, HTTP

Services

033 Scheduler

Schedule moving or emailing files and other tasks to run at user-specified intervals.

Scheduler

Table A-2: Feature Configuration Overview

OrionLXm

A-12

V. Operation of OrionLXm For monitoring the operation of the OrionLXm, both the OrionLXm’s webpage and serial MMI can be used individually or in combination. Each provides a different set of features. For each feature, the respective menu item to access the feature is listed. All entries in the following table are hyperlinks.

Feature OrionLXm Webpage OrionLXm MMI

View System Home Tab 5. System Menu

7. Thread Info

View Data DataValues Tab 2. Data Menu

Force I/O Points DataValues Tab 2. Data Menu

Device Statistics

(poll/responses)

Devices Tab 4. Device Statistics

View/Log Communications n/a 3. View Communications

Serial Port Statistics (bytes) System Tab n/a

Network Port Statistics (bytes) System Tab n/a

Software Versions System Tab 5. System Menu

5. View Version Info

View orionlx.ntk (license file) System Tab 1. File Menu

2. File Transfer (ORION -> PC)

System/Security Logs Files Tab, Download as tar from System

n/a

Event Logs Logs Tab: Specific logs

viewable or downloadable

5. System Menu

3. View Event Log

Configuration File Management Files Tab 1. File Menu

Manage Web Files

(.svg, .js, .css, etc.)

Files Tab and WebUI n/a

Passthrough to connected devices (IED, meters, relays, etc.)

n/a 5. System Menu

6. Passthrough Menu

OrionLXm Restart System Tab - Reboot Orion 5. System Menu

8. Restart

Table A-3: OrionLXm – Webpage and MMI Overview

OrionLXm

B-1

B. OrionLXm Hardware

OrionLXm

B-2

I. Physical Specifications

Processor

CPU Intel with hardware-accelerated cryptography, 720MHz, 512MB SDRAM

Data Points

IED/SCADA Points 20,000 maximum Refresh Rate < 2 sec typical Actual values may be higher or lower, dependent upon the type of protocols, number of ports used, and specified update cycles.

Communications

Protocols Bit or byte Serial 1200-115kbps

Ethernet 10/100BaseT, half/full-duplex

Upgrades Via File Transfer

Data Archiving & Storage

Memory 4GB

Digital Inputs/Outputs

Quantity 1 input (standard) 12 inputs (optional) 4 outputs (optional)

Input Range 9-36V dc or 36-150V dc 12-48V dc or 125V dc

Alarm Output

Type Form B

Contact Ratings 10A (max)

MOV Protected

Power Supply Options

24-250V dc ± 15% / 120-240V ac ± 15%, 50-60Hz

12V dc (10.5-14.5V dc)

Power Consumption 15W nominal, 30W/30VA max.

The operating environment of the Orion equipment must allow unobstructed access to the disconnection device (power cord) at all times.

OrionLXm

B-3

Environmental

Operating Temperature -40ºC to +70ºC

Operating Humidity 5%-90% non-condensing plus other IEEE 1613

Altitude 2000 meters max.

Indication LEDs

Power Supply Power Supply

Ethernet Link and Activity

Serial Communications TX LED for each port RX LED for each port

IRIG-B IRIG-B Present IRIG-B Quality

Built-In Input Status LED for input point

Built-In I/O card Status LED for each input point

Status and relay LED for each output point

OrionLXm Status Active Config Alarm

IRIG-B

IRIG-B Input Modulated and unmodulated, auto-detection of mode

IRIG-B Output

Output (on serial ports) Unmodulated

Drive Current 24mA (max) (sufficient to drive one SEL relay on each port)

Physical

Dimensions 2U

8.5W x 3.5H x 6D (inch)

Weight 5 lbs

Connectors

Serial ports

S4 card Four DB9 female ports for RS-232 with IRIG-B or RS-422/485 (software-selectable)

F4 card Four ST fiber serial ports, wavelength 800–850nm

Ethernet – Copper RJ45

IRIG-B Input Compression Screw Terminal, #12-24 AWG

Port A USB type B jack

I/O Terminals Compression Screw Terminals, #12-24 AWG

Power Terminals Compression Screw Terminals, #12-24 AWG

OrionLXm

B-4

II. OrionLXm Options List

Card Options

Two options must be specified so that the resulting part number has four letters, such as XXXX, S4XX, or F4F4, or S4IL.

-XX No card options.

-S4 Communication card with four RS-232 and RS-422/485 ports (software switchable).

-F4 Communication card with four ST fiber ports.

-IL I/O card with 12 digital inputs and 4 digital outputs, 12-48V dc nominal turn-on voltage

-IH I/O card with 12 digital inputs and 4 digital outputs, 125V dc nominal turn-on voltage

Ethernet Options

-2EXX Dual copper Ethernet ports

Digital Input Voltage

-ILV Nominal input voltage 12-48V dc

-IHV Nominal input voltage 125V dc

Mounting Options

-RACK 19" rack mount

-PANL Panel mount

-DINR DIN rail mount

Power Supply

-WR 24-125V dc / 120-240V ac

-12V 12V dc

Software Options (field upgradable)

-35 LogicPak Module

-80 Passthrough Interface Master Module

-81 iDial Module

-82 DA Logic Module

-83 Math and Logic Module

-93 Passthrough Interface Slave Module

-94 Logger Slave Module

-95 Alarm/Archive/Retentive Module

-96 Email Module

-97 Cascaded OrionLXm Master Module

OrionLXm

B-5

-98 Cascaded OrionLXm Slave Module

-99 Advanced Math and Logic

-101 IEC 61131-3 Module

-105 Points Blocking Module

Master Protocols (field upgradable)

-01 DNP3 Master

-03 DNP3 IP Master

-04 Modbus Master

-07 Modbus TCP Master

-08 Basler Master

-09 GE Master

-10 ABB DPU Master

-11 Optimho Master

-12 PG&E 2179 Master

-13 RFL Master

-14 SEL Master

-15 Tejas V Master

-16 Transdata DTO

-18 Kitz Master

-24 CDC-I Master

-25 L&G Master

-28 DF1 Master

-29 DQI Master

-30 SPAbus Master

-32 SEL2030 Master

-33 Generic ASCII Master

-36 IEC 60870-5-103 Master

-37 SEL TCP Master -38 Conitel Master

-201 PML Master

-202 ABB 10Byte Master

-203 Harris 5000/6000 Master

Slave Protocols (field upgradable)

-41 Conitel Slave

-42 DNP3 Slave

-44 DNP3 IP Slave

-46 L&G Slave

-47 Modbus Slave

-49 Modbus TCP Slave

-51 Harris 5000/6000

OrionLXm

B-6

-52 Pusher Slave

-55 ASCII IED Web

-57 XML Webserver

-61 CDC-I Slave

-67 IEC 60870-5-101 Slave

-68 IEC 60870-5-104 Slave

Part Number Examples The following part number examples show the structure of the part number. OrionLXm-XXXX-2EXX-IHV-WR-RACK-01-03-42-44-95-99

XXXX No serial com ports

2EXX Two Ethernet ports

IHV High Input Voltage

WR Wide Range Power Supply

RACK Rack Mount

01 DNP3 Serial Master Protocol

03 DNP3 IP Master Protocol

42 DNP3 Serial Slave Protocol

44 DNP3 IP Slave Protocol

95 Alarm/Archive/Retentive Module

99 Advanced Math and Logic

OrionLXm-S4S4-2EXX-ILV-12V-PANL-03-07-44-57-95-96-101

S4S4 Eight serial com ports with DB9 connectors

2EXX Two Ethernet ports

ILV Low Input Voltage

12V Wide Range Power Supply

PAN Panel Mount

03 DNP3 IP Master Protocol

07 Modbus TCP Master Protocol

44 DNP3 IP Slave Protocol

57 XML Webserver

95 Alarm/Archive/Retentive Module

96 Email Module

101 IEC 61131-3 Module

OrionLXm

B-7

III. OrionLXm Front Panel The OrionLXm front panel provides visual diagnostic indication and connections for advanced user diagnostics. In addition, the front panel contains a USB port (Port A) for advanced diagnostics. The OrionLXm front panel layout depends on the ordered communication or I/O cards. The front panel also provides LEDs to indicate the status of power, digital input, alarm output, Ethernet communication, serial communication, time synchronization, and I/O for I/O cards.

Figure B-1: OrionLXm Front Panel with Two Serial Communication Cards (Option S4S4)

1. Diagnostic LED Description

LED Function

Tx/Rx (DB9 and ST fiber serial ports)

Each DB9 and ST fiber serial port has a green Tx and red Rx LEDs. The

LEDs will illuminate when data are transmitted or received at the respective communication ports. This indicates only the presence of communication, without any verification as to checksum, device or register addressing, or a slave device receiving the Orion’s communication. If not DB9 or ST fiber ports are specified, these LEDs are not present.

I/O Card

For each installed I/O card, there is one block of LEDs to the left of the I/O card (see also Type IL and IH I/O Cards). For each of the 12 digital inputs, there is one LED which illuminates when the respective digital input is On. For each of the 4 digital outputs, there are two LED. The first LED indicates the status of the output. It is illuminated when the status at the output terminals is On. The second LED is illuminated when the OrionLXm has activated the internal relay.

OrionLXm

B-8

LED Function

Power (Status)

The Power (Status) LED indicates the power supply is operating at correct levels.

Active

The Active LED will illuminate when there is an active configuration file running on the OrionLXm unit.

Input

The Input LED (In1) will illuminate when voltage is detected on the input.

Alarm

The Alarm LED will illuminate and the output will be closed when the

OrionLXm detects an internal alarm.

The Alarm LED indicates an alarm condition upon restart until such

time as the unit has verified normal operating conditions. If the alarm

condition persists, the LED will remain on. Specifically, the Alarm

LED is illuminated as follows. Tithe alarm output on the OrionLXm follows the LED, i.e. when the LED is illuminated, the contact is closed, and vice versa.

Orion start/restart (full restart and quick restart) is from beginning of the start to when the diagnostics menu is displayed again.

If during the start, either a driver was not detected (i.e. the .ncd file includes a driver that is not loaded on the OrionLXm), or a port could not be opened, the LED and output remain active until the problem is corrected.

Time IRIG-B, Quality

The IRIG-B LED will illuminate when IRIG-B is connected.

The Quality LED will illuminate when time accuracy is < 1ms.

OrionLXm

B-9

LED Function

Ethernet Link/Activity

The Ethernet Link and Activity LEDs are located on the upper right and left corners of each Ethernet port.

The Ethernet Link LED will illuminate when a physical link to another device has been detected.

The Ethernet Activity LED will illuminate when the OrionLXm is transmitting or receiving on a specific port.

Table B-1: OrionLXm Front Panel Diagnostic LEDs

OrionLXm

B-10

2. Port A Configuration and Diagnostic The OrionLXm provides built-in diagnostics for viewing of data values, port communications, device statistics, system events, and system/version information. It also allows the changing of network settings and configuration file, firmware file, and log file transfers via Z-Modem (bi-directional), as well as passthrough to connected relays and meters. This allows the use of the respective manufacturer’s programming software to configure the relays and meters, the retrieval of event information, etc.

Figure B-2: Port A Location

Port A is the designated diagnostics/configuration port. As such, none of Port A’s parameters can be changed. Port A is located on the front panel and uses a USB Type B connector. A male A/B USB 2.0 cable is included with the OrionLXm shipment. The PC connecting to the OrionLXm will require a USB device driver before communications can be established. The USB driver for the PC is included on the installation CD. The PC can also obtain this driver from the Internet when it first connects to the OrionLXm. The communication parameters are as follows. These parameters are fixed and cannot be changed.

Port Parameter Value

Interface USB B Female

Baud Rate 115,200 (fixed)

Parity Bits None (fixed)

Data Bits 8 (fixed)

Stops Bits 1 (fixed)

Default Login Name novatech (case sensitive)

Default Password novatech (case sensitive)

Default Root Name root (case sensitive)

Default Root Password novatech (case sensitive)

Password Back Door None (fixed)

Table B-2: Port A USB Communications Parameters

The connections for Power, ports P1 to P8, Ethernet, Inputs, and Outputs are described below in the respective chapters.

OrionLXm

B-11

3. Power Connections The OrionLXm power input is located at the bottom left of the front panel. The power supply voltage is indicated on the label above the connection port as shown in the following figure. #12-24 AWG wire is recommended, stripping the insulation between 1/4” to 3/8”. An external 3A fast acting fuse is recommended for OrionLXm power.

Figure B-3: OrionLXm Power Connection

Figure B-4: Ground Lug

Depending on the selected mounting option, connect the ground lug to an accessible screw hole with the ground symbol shown in the above figure. A size #8/#10 ring or spade lug connector is recommended. NovaTech recommends that all grounding be performed in accordance with ANSI/IEEE C57.13.3-1983.

When the OrionLXm is connected to power, touching the power connectors on the outside of the OrionLXm enclosure, or removing the top cover of the OrionLXm enclosure and touching the power supply inside the enclosure, could result in injury or death. Proper corporate and public safety instructions must be observed at all times.

The OrionLXm uses removable screw terminal compression fittings for power connections. These connectors are keyed by voltage level so that a plug keyed for one voltage level cannot be plugged into a socket keyed for another voltage level. NCD also provides points for indicating power (see chapter Sensor). Since the OrionLXm cannot communicate without the power supply operating properly, the “Status” indication is assumed to always be on.

OrionLXm

B-12

4. Digital Input The OrionLXm has one digital input on the front panel. This input uses a compression screw terminal connector that accepts #12-24 gauge wire. The digital input is factory set to either 12-48V dc or 125 V dc input. See Table B-4 for exact voltage ranges. The input circuitry provides 1000V channel-to-channel isolation. Inputs can be time stamped to 1ms when the OrionLXm is receiving quality time synchronization.

Figure B-5: OrionLXm Digital Input Connection

Function In1 + In1 -

Terminal 11 12

Table B-3: Digital Input Terminal Header

Input Range Turn-On Voltage Max. Current Drain

12-48V 9.6-60V 2.1 mA per input

125V 93-150V 2.1 mA per input

Table B-4: Digital Input Turn-On Voltages and Current Draw

OrionLXm

B-13

5. Alarm Output The OrionLXm has one digital output on the front panel to indicate an OrionLXm alarm status. This

output utilizes a compression screw terminal connector. The Alarm contact is a dry contact, but unlike

other dry contact outputs, the alarm output is Normally Closed (NC). The alarm output is a form B relay output. The output indicates an alarm condition upon restart until such time as the unit has verified normal operating conditions. The red LED on the front panel positioned

under the In1 LED also indicates the alarm condition.

Figure B-6: OrionLXm Digital Output Connection

Function ALM ALM

Terminal 13 14

Table B-5: Digital Output Connection

6. Ethernet Ports The standard OrionLXm comes with two standard Ethernet ports.

Figure B-7: Dual Ethernet Ports

The Ethernet ports are labeled Eth0 and Eth1. Both ports are a 10/100BaseT full-duplex port with

RJ45 female connectors.

OrionLXm

B-14

7. IRIG-B Port The IRIG-B input is standard in the OrionLXm. This input allows the OrionLXm to stay synced with an IRIG-B Master (GPS clock) within 1 millisecond. The OrionLXm uses a webpage to configure modulated or demodulated IRIG-B inputs (see System). The OrionLXm accepts standard IRIG-B as well as the IEEE 1344 IRIG-B extensions that provide a two-digit year.

Figure B-8: IRIG-B Port

OrionLXm

B-15

8. OrionLXm Optional Cards The OrionLXm can be set up with a total of two optional communication and I/O cards shown in the following table. Any combination of cards is possible. If there is one I/O card and one communication card, the I/O card is always the top card.

Card Type Card Description

S4 Four DB9 female ports which can be configured in software for RS-232 and RS-4985/422.

F4 Four ST fiber serial ports.

IL I/O card with 12 digital inputs and 4 digital outputs, 12-48V dc nominal turn-on voltage.

IH I/O card with 12 digital inputs and 4 digital outputs, 125V dc nominal turn-on voltage.

Table B-6: OrionLXm Optional Cards

The P1 jumper block on each card listed in the above table sets up the card for the upper or lower card slot of the OrionLXm. When the cards are installed in the OrionLXm and shipped from the factory, changing the jumpers is not required. It is only required when cards are changed in the field. There are two jumpers on the block P1 which is marked in red in the following figure.

Figure B-9: Card Jumpers for Slot Addressing

OrionLXm

B-16

Slot Jumpered Pins

Upper 2-3 and 5-6

Lower 1-2 and 4-5

Table B-7: Card Jumpers for Slot Addressing

Type S4 Communication Card The S4 card provides four DB9 female ports which can operate both as RS-232 and RS-422/485 half/full duplex ports. The operating mode is set up in the webpage shown in chapter Serial. If operating as an RS-232 port, three jumpers are available for setting up the port to operate as standard RS-232 port or SEL®-compatible RS-232 port as follows. Pins marked with * are not implemented at this time.

DB9 Pin Number

Standard RS-232 Mode

RS-232 with SEL® Pinout

SEL® Pinout Description

JP1/4/7/10 = DCD

JP2/5/8/11 = DSR

JP3/6/9/12 = DTR

JP1/4/7/10 = DCD

JP2/5/8/11 = IRIG-B

JP3/6/9/12 = IRIG-B

1 DCD* +5V dc Fused at 100 mA

2 RxD RxD Receive Data

3 TxD TxD Transmit Data

4 DTR* IRIG-B TTL Time Signal

5 GND GND Signal Ground

6 DSR* IRIG-B GND Signal Ground for IRIG-B

7 RTS RTS Request to Send

8 CTS CTS Clear to Send

9 RI* RI* Ring Indicator

Table B-8: RS-232 Pinout

OrionLXm

B-17

If operating as RS-485 half duplex port, the pinouts are as follows.

DB9 Pin Number

Signal Description

1 NC Not connected

2 Tx/Rx+ Tx/Rx+

3 NC Not connected

4 NC Not connected

5 Ground Ground

6 NC Not connected

7 NC Not connected

8 Tx/Rx- Tx/Rx-

9 NC Not connected

Table B-9: RS-485 Half Duplex Pinout

If operating as an RS-485/422 full-duplex port, the pinout is as follows.

DB9 Pin Number

Signal Description

1 NC Not connected

2 Tx+ Transmit Data +

3 Rx+ Receive Data +

4 NC Not connected

5 Ground Ground

6 NC Not connected

7 Rx- Receive Data -

8 Tx- Transmit Data -

9 NC Not connected

Table B-10: RS-485/422 Full Duplex Pinout

OrionLXm

B-18

Type F4 Communication Card The F4 card provides four serial fiber ports with wavelength of 800-850nm. It is shown in the top slot in the following figure.

Figure B-10: OrionLXm with ST Fiber Serial Ports

Type IL and IH I/O Cards The IL and IH cards provide one or two optional built-in discrete I/O cards on the OrionLXm. Each card has 12 digital inputs and 4 digital outputs with LEDs to display I/O status. These connectors use compression screw terminal connectors that accept #12-24 gauge wire. The IL card has 12-48V dc nominal turn-on voltage and the IH card has 125V dc nominal turn-on voltage

Figure B-11: OrionLXm with I/O Card

OrionLXm

B-19

Inputs The inputs are grouped in two groups of six each (1-6 and 7-12). Each group of 6 digital inputs shares a

common input (Com). The input circuitry provides 1000V channel-to-channel isolation. Inputs can be

time stamped to 10ms when the OrionLXm is receiving quality time synchronization. LEDs provide the input status for each input and will be illuminated when the turn-on voltage is detected.

Upper Card

In1 +

In2 +

In3 +

In4 +

In5 +

In6 +

Com 1-6 -

In7 +

In8 +

In9 +

In10 +

In11 +

In12 +

Com 7-12 -

Terminal 51 52 53 54 55 56 57 58 59 60 61 62 63 64

Table B-11: Input Terminal Numbering for I/O Card in Upper Slot

Lower Card

In1 +

In2 +

In3 +

In4 +

In5 +

In6 +

Com 1-6 -

In7 +

In8 +

In9 +

In10 +

In11 +

In12 +

Com 7-12 -

Terminal 21 22 23 24 25 26 27 28 29 30 31 32 33 34

Table B-12: Input Terminal Numbering for I/O Card in Lower Slot

Figure B-12: Input Circuit

Jumpers JP3 - JP14 select the input range as shown in Table B-13. The inputs are factory-set to either 9-90 V dc (IL card) or 90-125 V dc (IH card). JP3 sets the range for input 1 and JP14 sets the range for input 12.

JP3 through JP14 Input Range Turn-On Voltage Max. Current Drain

Input Jumper Removed 12-48V 9-90V 2.1 mA per input

Input Jumper Installed 125V 90-250V 2.1 mA per input

Table B-13: Input Voltage Range Jumpers

OrionLXm

B-20

Figure B-13: IL and IH Circuit Board

Outputs The IL and IH cards each have 4 digital outputs with LEDs to display I/O status. These outputs utilize compression screw terminal connectors that accept #12-24 gauge wire. The first two contacts are Form C dry contacts and the second two contacts are Normally Open (NO) dry contacts.

There are two LEDs for each output point. The Relay LED will be illuminated when the relay is closed.

The Status LED will be illuminated when current is flowing through the closed relay and the

appropriate jumper is installed (see Table B-16).

Upper Card

Out1 NC

Out1 C

Out1 NO

Out2 NC

Out2 C

Out2 NO

Out3 C

Out3 NO

Out4 C

Out4 NO

Terminal 71 72 73 74 75 76 77 78 79 80

Table B-14: Output Terminal Numbering for I/O Card in Upper Slot

Lower Card

Out1 NC

Out1 C

Out1 NO

Out2 NC

Out2 C

Out2 NO

Out3 C

Out3 NO

Out4 C

Out4 NO

Terminal 41 42 43 44 45 46 47 48 49 50

Table B-15: Output Terminal Numbering for I/O Card in Lower Slot

OrionLXm

B-21

The contact status for each output can be obtained by monitoring voltage on the relay contacts. These inputs are enabled by installing JP15 through JP18. JP15 enables monitoring of output 1 and JP18 enables monitoring of output 4. The following table shows the voltage ranges and leakage current for the voltage monitoring.

Input Range JP15 through JP18 Max. Leakage Current

70-250 V ac or

9-250 V dc

Input Jumper Installed <1 mA per input

N/A Input Jumper Removed N/A

Table B-16: Contact Monitoring Jumpers and Leakage Current

OrionLXm

B-22

IV. Mounting Instructions The Orion can be mounted in a variety of ways:

Single OrionLXm in 19" rack Dual mount two OrionLXm's side-by-side in 19" rack Panel mount, multiple options DIN rail mount, multiple options

Ensure that the OrionLXm is mounted in compliance with all applicable safety requirements.

Figure B-14: 19" Rack Mount Options

Figure B-15: Dual Mount Option

Figure B-16: Conventional Horizontal Panel Mount

OrionLXm

B-23

Figure B-17: Horizontal Mount - Top of Panel and Bottom of Panel Options

Figure B-18: Vertical Panel Mount Options

Figure B-19: Vertical DIN Rail Mount

OrionLXm

C-1

C. NovaTech Configuration Director (NCD)

OrionLXm

C-2

I. Introduction to NovaTech Configuration Director (NCD)

1. Purpose of NCD NCD is Windows

®-based configuration software with a practical and straightforward graphical user

interface (GUI) that does not require special programming or scripting. Communications are easily set up between the OrionLXm and a protocol master, Human Machine Interface (HMI), Programmable Logic Controller (PLC), or an Intelligent Electronic Device (IED) such as a relay or a meter. For many slave devices (i.e. devices being polled by the OrionLXm), default files are available that contain the device’s standard input and output points with name, point address, and range. This further facilitates fast setup of the OrionLXm. NCD is used to set up the following features of an OrionLXm configuration. The setup of other features not listed here is described in section OrionLXm Webpage.

Serial and IP Port Setup Input/Output Point Lists for each Master and Slave Port Allow Forcing of Input/Output Points for Commissioning and Troubleshooting Add On Features:

­ Alarm/Archive/Retentive ­ Alias ­ Data Logger ­ Orion LEDs ­ Points Blocking ­ Pseudo Master ­ Pusher Slave ­ Hardware Sensor ­ System Logger

Text Module SER Input/Output Points Logic or LogicPak

Once the Orion’s configuration has been created off-line and saved to an .ncd file, the .ncd file must be transferred from the PC to the Orion in one of the following ways:

USB or ssh connection between the PC running NCD and the OrionLXm. Option File Transfer (PC -> ORION) of the Orion’s MMI transfers the .ncd configuration file to the Orion.

Ethernet connection between the PC running NCD and the Orion. Before the first time a file is transferred using the OrionLXm’s web interface, the OrionLXm’s IP address must be set through the OrionLXm’s serial port

1 as described in Network Menu. Then the web browser can access the

OrionLXm’s webpage. After logging in on the webpage, the .ncd configuration file can be transferred to the OrionLXm as described in User Files.

In addition to the configuration options, NCD provides a built-in terminal window for viewing of data values, port communications, device statistics, system events, and system/version information. It also allows firmware file and log file transfers via Z-Modem (bi-directional), as well as passthrough to connected relays and meters. This allows using the respective manufacturer’s programming software to configure the relays and meters, retrieve event information, etc. Section OrionLXm MMI provides a full explanation of these features.

1 For all Orion models, the MMI port is a female DTE port labeled Port A which is located on the front

panel. The fixed communication parameters are 115200 baud, no parity, 8 data bits, and 1 stop bit.

OrionLXm

C-3

2. System Requirements The PC running NCD must meet the following requirements:

> 100MB hard drive space

Windows XP Pro®, Vista

®, Windows 7

®, Windows 8

®

.NET 3.5

Internet Explorer 6.0 or later, or Firefox

Mouse

Graphics resolution 1024x768 or better

CD/DVD Drive

Serial port or USB port

Null-modem cable (included with Orion, NovaTech part number NT-NM9MF)

Ethernet port

3. Copyright Information NCD may be installed on multiple computers as needed under the following conditions:

The computers must be owned by the end user or its subsidiary.

The NCD installation must be used for an Orion-related project. All files installed by NCD are protected by copyright and may not be shared with any third party. By installing NCD on a computer, the installer agrees to these terms and conditions.

4. Outline of NCD Chapters Chapter II will explain the installation of NCD. Chapter III explains how the various OrionLXm options are configured from within NCD. The respective protocol and software manuals that pertain to the installed options must be available for setup. For each option ordered with the OrionLXm, the corresponding manual is included in the shipment. For example, if the DNP3 Master over TCP/IP was ordered with the OrionLXm, the corresponding DNP3 Master Software Manual explains the DNP3-specific parameters, such as RTU addresses, point types, communication parameters, etc. In addition to creating the Orion’s configuration file, NCD also connects to the Orion and displays the Orion’s MMI menu. This feature is fully explained in section OrionLXm MMI. All manuals are installed as .pdf files on the PC’s hard drive during the installation process described in the following chapter Installation of NCD. Once the installation in the next chapter has been completed, the manual can be opened as follows.

OrionLXm

C-4

Windows XP®: Start - Programs - NovaTech NCD3 - NCD Documentation

Figure C-1: Access to NCD and OrionLXm Documentation in Windows® XP

Windows Vista® or Windows 7

®: Start - All Programs - NovaTech NCD3 - NCD Documentation

Figure C-2: Access to NCD and OrionLXm Documentation in Windows Vista® or Windows 7.0

®

Windows 8®: Press the Windows key to get to the Start Menu, then go to NovaTech NCD3 and NCD

Documentation.

OrionLXm

C-5

II. Installation of NCD NCD is installed with the following steps. Step 1: The NCD installation CD must be inserted to the PC’s CD drive. Step 2: If the PC is set up to auto-run CDs, the NCD installation will start automatically. If the

installation does not start automatically, go to the Start button and select Run. Type

d:\setup.exe in the Run window that appears. If the CD drive has another drive letter,

such as E:, F:, etc., that letter must be entered instead of D:.

Figure C-3: NCD Installation

Step 3: In order to complete the installation, the PC must be restarted. Step 4: When the PC has started up again, NCD can be started.

If using Windows 8®, press the Windows key to get to the Start Menu, then go to NovaTech

NCD3, and NCD3.

In Windows 7® or Windows Vista®, start NCD3 as follows.

Figure C-4: Starting NCD Windows Vista® or Windows 7.0

®

OrionLXm

C-6

In Windows XP®, start NCD3 as follows.

Figure C-5: Starting NCD in Windows® XP

NCD and accompanying files are installed in the following directories as shown in the following figure.

C:/Program Files/NovaTech LLC/NCD3/ (Windows XP®).

C:/Program Files(x86)/NovaTech LLC/NCD3/ (Windows Vista®, Windows 7

® or 8

®).

NCD and accompanying files are installed in the following directories.

Figure C-6: NCD Program Directory Structure

OrionLXm

C-7

Directory Description

\Defaults Default files for IEDs and relays supported by the Orion. New default files can be added as needed and described by each respective protocol manual.

The default files are .csv (comma separated value) files.

\Docs All related documentation regarding the following: NCD, Orion, protocols, and Technical Notes.

\HMI Examples Examples files for setting up one-line diagrams and other webpages on the OrionLXm.

\LogicSimulator LogicSimulator.exe allows running the logic program on the PC to check

it for errors before transferring it to the Orion.

\USB Driver The USB driver for communication between the PC and the Orion via USB cable.

\ftdiDrivers

\HWDEF

\IEC61131-3

\Protocols

\HWDEF

\WIC

Internal software directories.

Table C-1: NCD Program Directory Structure

The NCD configuration files, user-defined connection settings, and user-defined default files are stored by

default under \My Documents\NCD\ as shown below. Of course, other directories can be set up as

needed for storing these files.

Figure C-7: NCD Data Directory Structure

OrionLXm

C-8

Directory Description

\Captures By default, any files with MMI captures are stored in this directory. These files can also be stored elsewhere on the PC if desired. See chapter

Capture Tab for details.

\Connections User-defined .conn files for the NCD connections with the Orion.

\NCDFiles OrionLXm .ncd configuration files and associated .bas logic files.

\UserDefaultFiles User-defined default files for IEDs and relays. New default files can be added as needed and described by each respective protocol manual. The default files must be .csv (comma separated value) files.

\UserSCLFiles Any .scl, .icd, or .cid files imported by the user in the IEC 61850 driver are stored in this directory. See the IEC 61850 Client for OrionLX Software Manual for more details.

Table C-2: NCD Data Directory Structure

OrionLXm

C-9

III. Running NCD

1. Main Menu The main menu of NCD provides the following options listed in Table C-3. A more in-depth description, including all sub-options, is found below in chapters 2 through 7.

Figure C-8: NCD Main Menu

Multiple OrionLXm configurations can be opened simultaneously; .ncd files and associated .bas files if OrionLXm Math and Logic is used, or .lua files if Advanced OrionLXm Math and Logic is used.

Menu Bar Description

File Access to .ncd file-related options, such as New, Open, Close, Save, Save As,

and recently edited files. Each .ncd file contains a single configuration for an Orion. Multiple .ncd files can be transferred to the Orion, but the Orion can run only one configuration at any given time. See File Menu for a full explanation of all file-related options.

Edit The automatic login data to the Orion Support Site and the NCD Update Options are entered under this option.

Configure The entire Orion configuration is set up from this option, including hardware configuration and options, software, port configurations, addresses, IP addresses, input/output point lists, poll rates, etc. See Configure Menu for all configuration-related options.

Communications This option connects the PC to the Orion’s MMI. The Orion’s MMI can be accessed with both NCD and standard terminal software, such as WinTerminal, CRT, etc. The Orion’s MMI is fully explained in section OrionLXm MMI.

Window If multiple windows are open in NCD, this option allows arranging the windows vertically or horizontally, or cascading of the windows.

Help This option provides the standard About information, as well as Protocol

Info which summarizes the current configuration.

Table C-3: NCD Main Menu

OrionLXm

C-10

2. File Menu This option handles the .ncd files which contain the Orion configuration.

Figure C-9: File Menu

Figure C-10: Selecting Configuration for Save, Save As, Close

Figure C-11: Convert Operations

OrionLXm

C-11

Command Description

New Starts the configuration for a new OrionLXm .ncd file. This configuration will later

be saved with Save or Save As. When creating a new configuration, the

Select Hardware window (see Figure C-23) will be displayed. Then the

following window (Figure C-13) is shown allowing selection between Standard

NCD File and Cascaded NCD File. In most cases, select Standard NCD

File. When using cascaded OrionLXm's, refer to chapter Cascading as well as

the Cascading for OrionLX Software Manual. After selecting the Orion hardware, the next step is the Configure Menu.

Open Opens an existing .ncd file. The starting directory is

C:\My Documents\NCD\NCDFiles\. Of course, .ncd (and associated .bas files)

can be stored anywhere on the PC.

Save All If multiple .ncd files are open, this option is enabled for saving all open files at the same time.

Save Saves the current OrionLXm configuration to the corresponding .ncd file (and

associated .bas file for Math and Logic, or .lua file for Advanced Math and Logic)

already on the hard drive. If this is the first time that this configuration is saved to

file, a Save As window will appear. If multiple configurations are open, the

configuration to be saved must be selected (see Figure C-10).

Save As Saves the current Orion configuration to a new .ncd file (and associated .bas

file if OrionLXm Math and Logic is used or .lua file if Advanced OrionLXm Math and Logic is used). The new file name must be entered. If multiple configurations are open, the configuration to be saved must be selected (see Figure C-10).

Close Closes the open Orion configuration without saving any new or changed parameters to an .ncd file. If multiple configurations are open, the configuration to be closed must be selected (see Figure C-10).

Convert There are several conversion operations available as shown in Figure C-11.

NCD file from Orion5r to OrionLX converts an .ncd file which has

originally been set up for an Orion5r to an OrionLXm. Specifically, the Orion5r supports Modbus Plus while the OrionLXm supports Modbus TCP. If the existing OrionLXm configuration includes Modbus Plus, this function converts all related configuration information to Modbus TCP.

NCD file from Standard to Cascaded Master converts an existing .ncd

file which has originally been set up for a stand-alone OrionLXm into a new .ncd file for the master OrionLXm of several cascaded OrionLXm's.

NCD file from Standard to Cascaded Slave converts an existing .ncd

file which has originally been set up for a stand-alone OrionLXm, and makes it part of an existing .ncd file.

Math and Logic to Advanced Math and Logic converts .bas logic to

.lua logic. The OrionLXm will support both logic types; however using Advanced Math and Logic offers more user flexibility and options. This conversion tool will convert both the .bas to .lua as well as update any references in the .ncd file from .bas to .lua.

Show

Differences This option compares two NCD files. The result of the comparison is displayed in a window, and can be copied to the clipboard or saved to a file for detailed analysis.

OrionLXm

C-12

Command Description

Relay Helper The Relay Helper supports configuration for SEL® relays and is described in

the SEL® Master for Orion Software Manual, Appendix G.

Reorder

Network Ports

in NCD File

This function opens an existing .ncd file for reordering the network ports. Then the network ports can be rearranged by clicking the Move Up and Move Down

buttons as shown in Figure C-12.

Exit Exits NCD. If the current configuration has not yet been saved to an .ncd file, an additional prompt allows saving the file before exiting.

Table C-4: NCD File Menu

Figure C-12: Reorder Network Ports

Figure C-13: Selection of Standard / Cascaded Configuration

Note: An OrionLXm configuration is stored as an .ncd file on the PC’s hard drive. If logic is

used, NCD stores the logic for an .ncd configuration file in an associated .bas or .lua file located in the same directory. The name of the .bas or .lua file is stored in the

corresponding .ncd file, such as newcfg.ncd.

OrionLXm

C-13

If the .ncd file and the .bas or .lua file have been renamed (e.g. from oldcfg.ncd to newcfg.ncd and

oldcfg.bas/oldcfg.lua to newcfg.bas/newcfg.lua), or the .ncd file has been moved without

moving the .bas or .lua file, NCD displays a prompt for the associated .bas or .lua file (see Figure C-14). This is because the .ncd file still contains the original name of the associated .bas or .lua file, but now the .bas or .lua file has a new name, or is still in one directory while the .ncd file is in another directory. If the correct logic file name is not entered, NCD will continue with an empty logic file.

Figure C-14: NCD Prompt for Logic File

OrionLXm

C-14

3. Edit Menu

The Edit menu sets up features related to the operation of NCD.

Figure C-15: Edit Menu

Once Settings is selected, the following window opens.

Figure C-16: User Settings – Updates Tab

OrionLXm

C-15

Updates Tab

Under the Updates tab, the following features can be set up.

Orion Support Site User Information

Entering the NovaTech-issued User Name and Password allows automatic login to the NovaTech Orion

Support Site. If the User Name and Password have not yet been issued, clicking Request User

Name generates an email to NovaTech using the default email client software installed on the PC, such as

Outlook, Outlook Express, or Thunderbird. NCD Update Options NCD is updated based on the option selected here. Updates can be installed automatically whenever they are available. A notification can be displayed when an update becomes available. If the update is downloaded, the update will be installed automatically when NCD is restarted. If desired, updates can be disabled altogether. The number of backup copies of the previous install to keep is designated here. This can range from 0-3 with a default value of 3. Proxy Server If the PC is connected to the Internet using a proxy server, its address and port number must be entered to allow NCD to access the NovaTech server.

OrionLXm

C-16

General Tab In the first checkbox, the splash screen on NCD startup can be enabled and disabled.

Checking the Log Program Events/Errors box logs the NCD events and errors to the log file

specified in the following field. View Log File opens the current log file for viewing, and

Delete Log File deletes the current log file.

If a specific default directory for NCD files is needed which is different from the NCD standard, it must be

entered in Default Directory for NCD file Open/Save field.

Figure C-17: User Settings – General Tab

OrionLXm

C-17

Capture Tab The live communications between the OrionLXm and other devices can be captured to a file as described

in chapter Communication Window. The settings for the capture file are configured under the Capture

tab as shown in Figure C-18.

If the Enable Capture File Limits box is not checked, the capture file can potentially occupy all

remaining free space on the hard drive.

If the Enable Capture File Limits box is checked, the size of the capture file and the number of

capture files can be set.

File Size Limit sets the upper limit for a log file. The default maximum is 10 MB.

Limit Number of Capture Files limits the number of log files. The default value is 10.

If Rollover is enabled, the oldest capture file will be deleted when the above limits are reached. If the

box is not checked, the capture will stop when the above limits are reached.

Figure C-18: User Settings – Capture Tab

OrionLXm

C-18

4. Configure Menu

The options under Configure set up all aspects of the OrionLXm with regards to master and slave

protocols, communication parameters and addresses, point lists, logic, logging, etc.

Figure C-19: Configure Menu

The configuration is stored in an .ncd file on the PC’s hard drive using the steps described in the previous chapter. If ‘logic’ is used, NCD stores the logic for an .ncd in an associated .bas or .lua file located in the same directory. Once the .ncd (and .bas/.lua) file is created, it must be transferred from the PC to the OrionLXm using either the OrionLXm Webpage (Ethernet connection) or OrionLXm MMI (serial connection or Ethernet connection).

The data protocols available in the NCD installation for Serial Ports and Network are shown in

Figure C-25 and Figure C-27.

Options under NKI – Time Interface, Add Ons, Hardware I/O, and Logic are marked with

once they are configured. Additional drivers and options can be obtained by contacting NovaTech.

Standard Software Features The following software is standard for all OrionLXm's.

NKI – Time Interface

Orion LEDs

System Logger

Sensor

Other software options must be ordered specifically as shown in OrionLXm Options List.

OrionLXm

C-19

Operations in the Port Setup Windows Most of the options described in the following chapters are configured using a port setup window with the

following Port Options displayed at the top of the window. Depending on the type of port, not all of the

options are available.

The * on the right side of the title bar text indicates that the current port setup has not yet been saved.

Figure C-20: Port Operations

Setting Description

Copy

Move

The current port configuration can be copied or moved to another port in the same OrionLXm configuration. If multiple configuration files are open, the ports in the other configuration files are listed as well as targets for the copy or move operation. The selection window for the target port is shown below. Any port-specific parameters are automatically adjusted to the target port. All other parameters are simply moved or copied.

Delete Remove the current port with all configured parameters and data points from the configuration. If other ports map points defined on this port, these ports are affected by the removal of this port.

Close After configuring all parameters and data points for this port, clicking this option closes the port setup window.

Table C-5: Port Operations

Figure C-21: Choose port for protocol

OrionLXm

C-20

General

The following window is displayed for this selection. Table C-6 provides the description for each setting

in the General Settings window.

Figure C-22: General Settings

Setting Description

Force Inputs Allows forcing of input points from the Orion’s MMI console. If the box is checked here and the input is forced in the MMI, the master station will see the input point with the value forced at the Orion MMI, as opposed to the value obtained from the end device. This feature helps debug the communication between the master station and the Orion without having to force input values in the end device. See the chapter Data Menu in the MMI section of this manual for details. Note that for a user to be able to force inputs, the user account must be set up with this option (see chapter Account Management).

Force Outputs Allows forcing of output points from the Orion’s MMI console. If the box is checked here and the output is forced in the MMI, the end device will receive a value for an output point as forced by the Orion as opposed to sending a value all the way from the master. This feature helps debug the communication between the end device and the Orion without having to send output values in from the master. See the chapter Data Menu in the MMI section of this manual for details. Note that for a user to be able to force outputs, the user account must be set up with this option (see chapter Account Management).

Comments This field allows recording of any kind of notes regarding this configuration, such as location, specific parameters, history, etc.

Table C-6: General Settings

OrionLXm

C-21

Enabling Force Inputs allows forcing of input values through the

OrionLXm’s MMI console. Then, the forced OrionLXm data point(s) will indicate an equipment state or condition to the SCADA master that is only simulated, and does not reflect the actual state or condition. This may lead the SCADA master computer or personnel to initiate operations based on the simulated state as opposed to the actual state. The necessary permissions must be obtained from the control center and other departments in accordance with your corporate safety and operating guidelines. Failure to do so could result in equipment damage, injury, and/or death.

Enabling Force Outputs allows forcing of output values through the

OrionLXm’s MMI console. This may operate a live piece of equipment on the end device, the same way it would be operated locally, or from the front end/SCADA master. The necessary permissions must be obtained from the control center and other departments in accordance with your corporate safety and operating guidelines. Failure to do so could result in equipment damage, injury, and/or death.

Hardware Model Information The various models of Orion family are available with numerous options. For the OrionLXm or the

Orion5rL, the option OrionLX/Orion5rL must be selected. If the OrionLXm or Orion5rL unit has a

modem installed, the Modem box should also be checked.

Figure C-23: OrionLXm Hardware Configuration

OrionLXm

C-22

Serial Ports With the exception of Port A, all ports can be individually configured with a specific protocol, and the related communication parameters, device lists, and point lists. All ports are independent of each other, i.e. there are no limitations on the combinations of protocols used. After selecting a port in Figure C-24, the protocol selection screen in Figure C-25 allows the selecting of the protocol for the port.

Figure C-24: Port Selection

OrionLXm

C-23

Port Description

Port A Built-in diagnostics port. The communication parameters are 115200-N-8-1 and cannot be changed.

Port B

Port C

Port D

These ports are not supported by the OrionLXm.

Port 1-8 These ports can be RS-232, RS-485, RS-422, fiber, and various bit protocols depending on the modules ordered and installed in each slot (see chapter OrionLXm Optional Cards.

Table C-7: Orion Ports

Figure C-25: Serial Protocol Selection Menu

Depending on the protocols purchased and implemented, a specific protocol may be available as a Master (the Orion acts as master, polling other devices with that protocol) and/or Slave (the Orion acts as slave, responding to polls by a remote master). After selecting the protocol, refer to the specific NovaTech protocol documentation to configure the port communication parameters, RTU/device list, input point list, output point list, poll groups, and any other related parameters.

OrionLXm

C-24

Network

Under Network, the network ports are configured. Port 23 is a default HTTP Slave port. Configure

New Port adds a new TCP/IP master or slave protocol which is selected on the screen shown in Figure

C-26 and Figure C-27.

Figure C-26: Network Parameter and Port Configuration

Figure C-27: Network Protocol Selection Menu

Depending on the network protocols purchased and installed, a specific protocol may be available as a Master (the OrionLXm acts as master, polling other devices with that protocol) and/or Slave (the OrionLXm acts as slave, responding to polls by a remote master). After selecting the protocol, refer to the specific NovaTech protocol documentation to configure the port communication parameters, RTU/device list, input point list, output point list, poll groups, and any other related parameters.

OrionLXm

C-25

NKI – Time Interface The OrionLXm time synchronization software module is a standard OrionLXm feature. It is used for obtaining and distributing time. This module samples IRIG-B and/or NTP time sources, providing highly accurate time and date in the OrionLXm. IRIG-B and NTP can be sampled concurrently for redundant time sources. The OrionLXm can, in turn, distribute time via IRIG-B and NTP. Synchronization is accomplished through constant sampling. Thousands of time samples are required before the OrionLXm adjusts its time. On power up, it can take the OrionLXm up to 30 minutes to set the Time Quality Flag, which indicates 1 ms accuracy. Under rare circumstances, it can take up to 8 hours for the flag to set when no frequency drift file is present on the OrionLXm. In the screen shown below, the following data points can be configured as explained in Table C-8. These points can be monitored by a SCADA master and used in the OrionLXm logic. The parameters for each point are explained in Table C-9.

Figure C-28: NKI – Time Interface Setup

Inputs Function

Orion PLL Offset The last applied correction to the system clock in seconds.

Source scaling: -2,147,483,648 to 2,147,483,647.

Orion PLL Freq The automatic periodic correction to the system clock in Parts Per Million (PPM). Positive values make the clock go faster while negative values slow it down.

Source scaling: -2,147,483,648 to 2,147,483,647.

OrionLXm

C-26

Inputs Function

Orion MaxErr The maximum clock error in seconds.

Source scaling: -2,147,483,648 to 2,147,483,647.

Orion EstErr The estimated collective time source error in seconds. This value will vary from OrionLXm to OrionLXm.

Source scaling: -2,147,483,648 to 2,147,483,647.

Orion PLL Status The PLL Status is represented by a numerical range. If the PLL is enabled, synchronization is occurring (synchronization is a never-ending process when connected to a time source). Entering the following command on the MMI command line displays the current status condition along with a brief description:

# ntpdc –c kern

Source scaling: -2,147,483,648 to 2,147,483,647.

Orion Time

Quality

The time quality of the OrionLXm time daemon. This value is 0 when no time sources are reachable or if estimated error is greater than or equal to 0.03 seconds…32 if estimated error is less than 0.0005 seconds…31 if estimated error is less than 0.00075 seconds.

Source scaling: 0 to 32.

Orion Time

Quality Binary

Binary point indicating time accuracy. On indicates accuracy to +/- 500 µsec.

Source scaling: 0 to 1.

Orion Time

Reachability

This is an 8-bit register with the bits corresponding to the reachability of a configured source during the last 8 poll cycles. 0 indicates no sources were reached during the last 8 polls. 255 (decimal) indicates a source was reached during all of the last 8 polls. Bit 0 (LSB) corresponds to the most recent poll issued while bit 7 (MSB) represents the poll “8 polls ago”.

Source scaling: 0 to 255.

Table C-8: NKI – Time Interface Data Points

Parameter Description

Point Name The Point Name and the Device name are combined into the Tagname

which references the point within this port, as well as all other ports/protocols where that point might be used. Using self-explanatory names facilitates online monitoring of the OrionLXm’s operation. This string can be up to 30

characters long, and can contain all printable characters except @, [, ], ', ",

=, and commas.

Alias Name Displays the Alias Name (specified in the Alias module under Add Ons).

Point Type Eight point types are used for the predefined points. The types are:

offset, freq, maxerr, ester, status, quality, qualitybin, reach

The Point Type cannot be modified by the user, since it is predefined in the OrionLXm.

OrionLXm

C-27

Parameter Description

Device The only Device available on this tab is the predefined Orion Internal

device, since each OrionLXm has only one NKI port.

Min/Max Values Each point has a minimum and maximum value. The minimum and maximum values are used by the NKI to normalize the value and make it available to other ports in the Orion. A complete discussion of scaling is provided NovaTech’s Analog/Accumulator Scaling Technical Note.

Table C-9: NKI – Time Interface Parameters

On the Port tab, the Orion driver and port information is entered. For most configurations, the default

parameters generated during creation of the configuration file are correct and need not be changed.

Figure C-29: NKI – Port Setup

Parameter Description

Port Name The default name is NTP Kernel If the name is changed, the new port

name should describe the port’s purpose, as this will provide self-explaining MMI menus when the Orion is operating. This string can be up to 30

characters long, and can contain all printable characters except @, [, ], ', ",

&, =, and commas.

Port Module Use Automatic Settings is disabled for the OrionLXm model. The

Port Module specifies which protocol driver will be utilized in the Orion.

NKI defaults to mnki, which is required for NKI.

Table C-10: NKI – Port Setup

OrionLXm

C-28

Add Ons The OrionLXm has numerous additional modules for data retrieval, storage, logging, and communications

available. These modules are configured under Add Ons (Figure C-30).

Figure C-30: Add On Options

For each option, the respective NovaTech software manual provides complete instructions regarding setup and operation. Accumulator Freeze

The Accumulator Freeze module allows the configuration of accumulator change logging, automated

freeze commands, and accumulator resets. The Accumulator Logger for OrionLX Manual provides the necessary details regarding the setup and operation of this option.

OrionLXm

C-29

Alarm/Archive/Retentive

The Alarm/Archive/Retentive option sets up archiving and retention (restoration of point values

after a power-cycle) for internal data points such as time quality, firewall status, and internal voltages. These values are then written to a file in the expanded memory. The Alarm/Archive/Retentive for Orion Manual provides the necessary details regarding the setup and operation of this option. Alias The Alias feature is a standard feature of the OrionLXm. It allows mapping the point names as

generated during the OrionLXm configuration to external point names imported from a .csv file. From

then on, the Orion data points can be referred to by their imported point names throughout the OrionLXm software, menus, and webpage. This feature is useful for importing standard point names already defined and used in the corporate setting. Thus, without any additional training, all staff are immediately familiar with all data points which are configured in the OrionLXm, because those are the names already in use.

When opening the Alias option, the following screen is displayed with all Inputs and all Outputs that

have been configured for the current configuration file. Inputs and Outputs are selected in the pane

on the left. In the center pane, all configured input/output points are displayed. In the right pane, the Open File button allows opening of a .csv or .txt file (see format in Table C-11) which contains a

simple list with all input and output aliases, i.e. existing names that are already used in the corporate environment, to describe the points currently in operation.

Figure C-31: Alias Assignment

OrionLXm

C-30

Each point can be assigned its alias by drag and drop. Aliases can also be entered manually.

The .csv file containing the alias names consists of a single column as shown in the following table.

Both the list of input aliases and the list of output aliases require a specific header ([Input Alias] and

[Output Alias]) for the alias file to be useable by NCD. The size of the .csv file depends on the

number of points configured in the OrionLXm and the number of points existing in the corporate environment. If multiple Orions are used, multiple alias files can be created, each representing a subset of the total number of existing points in the control system.

[Input Alias]

AliasName for Input1

AliasName for Input2

AliasName for Input3

AliasName for Input4

AliasName for Input5

AliasName for Input6

AliasName for Input7

AliasName for Input8

AliasName for Input9

AliasName for Input10

[Output Alias]

AliasName for Output1

AliasName for Output2

AliasName for Output3

AliasName for Output4

AliasName for Output5

AliasName for Output6

AliasName for Output7

AliasName for Output8

AliasName for Output9

AliasName for Output10

Table C-11: Alias File Format

Once all input and output aliases have been assigned, clicking Close at the top of the window closes the

Alias Interface.

Configuration Manager Agent The Configuration Manager Agent ties the Orion into the NovaTech Configuration Manager software. This software manages the configurations of the Orion and downstream devices and is available separately from NovaTech.

OrionLXm

C-31

Connection Manager Agent The Configuration Manager Agent ties the Orion into the NovaTech Configuration Manager software. This software manages secure access authorizations for multiple Orions and multiple users, and is available separately from NovaTech. Data Logger

The Data Logger option sets up data points for logging to files. Multiple files can be set up for logging.

Points related to each other can be logged to the same file. The setup and operation of this option are described in the Data Logger for Orion Manual. Orion LEDs The LED module is standard OrionLXm software and automatically configured as shown below. No further setup is required. The module controls the Time Quality LED, the Active Config LED, the Firewall LED, and LEDs L1, L2, and L3.

Figure C-32: Orion LED Module

OrionLXm

C-32

Points Blocking SCADA Points Blocking is defined as the action of temporarily not reporting changes in real-time data values to SCADA. This is sometimes referred to as “Alarm Shelving”. The Points Blocking module can be ordered for the OrionLXm (standard CPU or High Performance CPX models) to enable users to temporarily block the reporting of selected points, or groups of points, to SCADA. The Points Blocking Module requires the additional Expanded Memory option to be purchased. The additional 1GB or 4GB memory enables retention of the blocked point state through power cycles (see Points Blocking Module for OrionLX). Pseudo Typically, data is being polled from the end device by the Orion through a master port, and in turn, an Orion slave port is polled by a master station, such as a SCADA master or HMI. However, some applications specify that the Orion be connected to two master stations, and data to be exchanged between two masters. Thus, the outputs of one master become the inputs of the other master, and vice versa. This option allows setting up the data transfer between two slave ports on the Orion, i.e. data between two master stations is exchanged. The setup and operation of this option are described in the Pseudo Master for Orion Manual. Pusher Typically, the Orion is polling data from the end device using a master port. In turn, an Orion slave port is polled by a master station. However, some applications specify that the Orion be connected to two slave devices, and for data to be exchanged between those two slave devices. A typical example is two PLCs connected to the Orion, with the PLCs needing to exchange data. Thus, the Orion reads the inputs from one slave device and writes them as outputs to the other slave device, and vice versa. This option allows setting up the data transfer between two master ports on the Orion, i.e. data between two slave stations is exchanged. The setup and operation of this option are described in the Orion Pusher Software Manual. This option is an integrated part of the Modbus Master (see Modbus Master for Orion Software Manual) and SEL Master (see SEL® Master for Orion Software Manual). Sensor The Sensor Master module is a standard OrionLXm feature. It monitors the OrionLXm temperature, voltages, firewall status, and alarm status, and makes these values available as analog or discrete data points for logging, processing in logic, or masters stations. All data points shown below are available in default setup.

The Port tab of the Sensor Master module includes a Point Options checkbox setting to enable the

configuration of security points.

OrionLXm

C-33

Figure C-33: Sensor Setup - Port Tab

By default, Enable Security Points is checked which includes all security-related points such as Root

Session Status on the Inputs tab and the Outputs tab in the configuration. If the box is unchecked,

only the hardware-related sensor points are included in the Orion realtime database.

Figure C-34: Sensor Setup - Inputs Tab

OrionLXm

C-34

Inputs Function

Orion

Temperature

The current temperature inside the Orion. The temperature is made available in degrees Celsius.

Source scaling: -128 to 127.

Orion 3B Volts The current 3B voltage of the Orion. The default source scaling is 0..255. On a slave port that this point is mapped to, either 16-bit integer or floating point format should be used for setting up this point. For 16-bit integers, the range must be defined as 0..65535. In the mapped point, the voltage is then indicated as a number between 0 and 6640, representing a voltage between 0 and 6.64 Volts. If the mapped point is set up as a floating point value, the range must be defined as 0..65535. The voltage is then indicated as a number between 0 and 6.64 Volts.

Source scaling: 0 to 255.

Orion 3A Volts The current 3A voltage of the Orion. The default source scaling is 0..255. On a slave port that this point is mapped to, either 16-bit integer or floating point format should be used for setting up this point. For 16-bit integers, the range must be defined as 0..65,535. In the mapped point, the voltage is then indicated as a number between 0 and 4382, representing a voltage between 0 and 4.382 Volts. If the mapped point is set up as a floating point value, the range must be defined as 0..65.535. The voltage is then indicated as a number between 0 and 4.382 Volts.

Source scaling: 0 to 255.

Orion 5 Volts The current 5V voltage of the Orion. The default source scaling is 0..255. On a slave port that this point is mapped to, either 16-bit integer or floating point format should be used for setting up this point. For 16-bit integers, the range must be defined as 0..65,535. In the mapped point, the voltage is then indicated as a number between 0 and 6640, representing a voltage between 0 and 6.64 Volts. If the mapped point is set up as a floating point value, the range must be defined as 0..65.535. The voltage is then indicated as a number between 0 and 6.64 Volts.

Source scaling: 0 to 255.

Firewall Status Binary point indicating whether the OrionLXm firewall is turned off or turned on. When mapped, the range of the mapped point must be 0…1.

Source scaling: 0 to 1 (Off and On).

Alarm Status Binary point indicating whether an alarm is active. When mapped, the range of the mapped point must be 0…1. An active alarm is also indicated by the Alarm LED (see Alarm) and the Alarm Output (see Alarm Output).

Source scaling: 0 to 1 (Off and On).

ttyS2 off hook

ttyS20 off hook

The modem is off hook.

Source scaling: 0 to 1 (Off and On).

eth0 link

eth1 link

The respective Ethernet port has a good link to another device or switch.

eth0 activity

eth1 activity

There is communication activity on the respective Ethernet port.

OrionLXm

C-35

Inputs Function

SSHD Session

Status

Value is 1 if SSH or SFTP login is used. Value is 0 with logout, including idle timeout. The value of this point is also available as Text event.

Examples of Text event format:

host slog username login on ssh

host slog username logout on ssh

Affected application(s): SSH, SFTP

HTTP Session

Status

Value is 1 if HTTP login is used. Value is 0 with logout, including idle timeout. The value of this point is also available as Text event.

Examples of Text event format:

host slog username login on apache2_http

host slog username logout on apache2_http

Affected application(s): HTTP

HTTPS Session

Status

Value is 1 with HTTPS login. Value is 0 with logout, including idle timeout. The value of this point is also available as Text event.

Examples of Text event format:

host slog username login on apache2_https

host slog username logout on apache2_https

Affected application(s): HTTPS

Login TTY

Session Status

Value is 1 with TTY login. Value is 0 with logout, including idle timeout. The value of this point is also available as Text event.

Examples of Text event format:

host slog username login on /dev/ttyS# host slog username logout on /dev/ttyS#

Affected application(s): TTY(Serial Port)

Login Telnet

Session Status

Value is 1 if Telnet login is used. Value is 0 with logout, including idle timeout. The value of this point is also available as Text event.

Examples of Text event format:

host slog username login on /dev/pts/# host slog username logout on /dev/pts/#

Affected application(s): Telnet

Pro FTPD

Session Status

Value is 1 if FTP login is used. Value is 0 with logout, including idle timeout. The value of this point is also available as Text event.

Examples of Text event format:

host slog username login on /dev/ftpd##### host slog username logout on /dev/ftpd#####

Affected application(s): FTP (SFTP is part of SSH)

GDM Session

Status

Value is 1 if user is logged in via attached keyboard and monitor. This includes locked screens. Value is 0 if no user is logged in. The value of this point is also available as Text event.

Examples of Text event format:

host slog username login on :0 host slog username logout on :0

Affected application(s): MMB Keyboard and Monitor

OrionLXm

C-36

Inputs Function

PPP Session

Status

Value is 1 if user is connected and logged in via PPP (dial up networking); value is 0 with logout or disconnect, including idle timeout. The value of this point is also available as Text event.

Examples of Text event format:

host slog username login on /dev/ttyS# host slog username logout on /dev/ttyS#

Affected application(s): PPP (Dial-up networking)

IEC61131

Session Status

Value is 1 if IEC61131-3 login is made via NCD. Value is 0 with logout, including idle timeout. The value of this point is also available as Text event.

Examples of Text event format:

host slog username login on orion_iec61131-3 host slog username logout on orion_iec61131-3

Affected application(s): Debug connection via NCD

Secure Passthru

Session Status

Value is 1 if NCM is connected and logged into. Value is 0 with no NCM connections are used, including idle timeout. The value of this point is also available as Text event.

Examples of Text event format:

host slog username login on orion_spsec host slog username logout on orion_spsec

Affected application(s): Debug connection via NCD

Root Session

Status

Value is 1 if root login is used. Value is 0 with root logout, including idle timeout. The value of this point is also available as Text event.

Examples of Text event format:

host slog root login on app host slog root logout on app

Affected application(s): Local or Remote Root

Local Root

Session Status

Value is 1 if local root login is used. Value is 0 with local root logout, including idle timeout. The value of this point is also available as Text event.

Examples of Text event format:

host slog root login on app

host slog root logout on app

Affected application(s): GDM and TTY

Remote Root

Session Status

Value is 1 if remote root login is used. Value is 0 with remote root logout, including idle timeout. The value of this point is also available as Text event.

Examples of Text event format:

host slog root login on app

host slog root logout on app

Affected application(s): Network

OrionLXm

C-37

Inputs Function

Local Session

Status

Value is 1 if local login is used. Value is 0 with local logout, including idle timeout. The value of this point is also available as Text event.

Examples of Text event format:

host slog username login on app

host slog username logout on app

Affected application(s): GDM and TTY

Remote Session

Status

Value is 1 if remote login is used. Value is 0 with remote logout, including idle timeout. The value of this point is also available as Text event.

Examples of Text event format:

host slog username login on app

host slog username logout on app

Affected application(s): Network

User Login

Count

Increments with every login. Decrements with each logout, including idle timeout. Value is 0 on Orion process restart or reboot. The value of this point is also available as Text event.

Examples of Text event format:

host slog username login on app

host slog username logout on app

Affected application(s): Any

Note: All of the above text events will be attached to this point.

Known User

Login Failure

Count

Increments every time a known user fails to log in. Does not decrement. Value is 0 on reboot. The value of this point is also available as Text event.

Examples of Text event format:

host slog username attempted login on app

Affected application(s): Any

Unknown User

Login Failure

Count

Increments every time an unknown user tries to log in. Does not decrement. Value is 0 on Orion process restart or reboot. The value of this point is also available as Text event.

Examples of Text event format:

host slog Invalid user username attempted login on app

Affected application(s): Any

User Lockout

Count

Increments every time a user is locked out. Does not decrement when user is unlocked out. Value is 0 on Orion process restart or reboot. The value of this point is also available as Text event.

Examples of Text event format:

host slog User username is locked out

Affected application(s): Any

Table C-12: Sensor Setup

OrionLXm

C-38

System Logger The System Logger is a standard OrionLXm feature. It allows logging of system events, such as operation and communication related events, as well as point changes for all points or a specified list of points. The setup and operation of this option are described in the System & Point Logger for OrionLX Manual. Text Module The Text module monitors the current values of specified discrete or analog points. For specific values, text strings can be defined, and when the point assumes a specific value, the associated text is generated. The Email, Datalogger, and Logic modules of the Orion can subscribe to the generated text strings for various purposes, such as sending emails. The setup and operation of this option are described in the Text Module for OrionLX Manual. See also Email for OrionLX Software Manual, Data Logger or OrionLX Software Manual, and Math and Logic Software Manual.

OrionLXm

C-39

Hardware I/O The OrionLXm provides one discrete input (see Digital Input) and one discrete output (Alarm) (see Alarm

Output) on the front panel. These are configured with the menu item Built-in Standard (SER).

In addition, optional I/O cards are available as described in chapter Type IL and IH I/O Cards. These are

configured with the menu item Built-in Optional (IIO).

Figure C-35: Hardware I/O

OrionLXm

C-40

Built-In Optional I/O The OrionLXm can be ordered with one or two optional built-in discrete I/O cards. Each card has 12 digital inputs and 4 digital outputs with LEDs to display I/O status. These points are configured using the Built-in Optional I/O (IIO) module.

Figure C-36: Optional I/O Configuration

Port Setup

Click Port in the left pane for the following setup.

Figure C-37: IIO Port Setup

OrionLXm

C-41

Parameter Description

Port Name The default name is IIO Master If the name is changed, a port name that

describes the ports purpose should be used, as this will provide self-explaining MMI menus when the Orion is operating. This string can be up to 30

characters long, and can contain all printable characters except @, [, ], ', ",

=, &, and commas.

Port Module Use Automatic Settings is disabled for the OrionLXm. This parameter

defaults to mser, which is required for this I/O.

Table C-13: IIO Port Setup

Device Setup

Click Add New Device in the left pane to set up a new device. Each I/O card in the OrionLXm must be

set up as a separate device. Then configure the new device as shown below.

Figure C-38: IIO Device Setup

OrionLXm

C-42

Parameter Description

Company Select NovaTech.

Device Select OrionLXm.

Description The name entered here will be used throughout the Orion configuration. Using a name like SER or Local makes the displays self-explanatory. This string can be up to 30 characters long, and can contain all printable characters except @, [, ], ', ", =, and commas.

Bus Device The bus address of the card. Depending upon the number of I/O and communication cards, the I/O card may be Card A or Card B. Card A is the bottom card and Card B is the top card. Note: JP1 configures the I/O cards USB bus address (A or B).

Table C-14: IIO Device Setup

Input Setup

Click Inputs in the left pane to set up the input points of the I/O card. In the center pane, highlight the

discrete or accumulator input points which are desired in the OrionLXm mapping table and realtime database. Then click >> to move these points to the pane on the right as shown in Figure C-40.

Figure C-39: IIO Inputs Setup

OrionLXm

C-43

Figure C-40: Configured IIO Input Points

Parameter Description

Point Name The Point Name and the Device name are combined into the Tagname which

references the point within this port, as well as all other ports/protocols where that point might be used. Using self-explanatory names facilitates online monitoring of the Orion’s operation. This string can be up to 50 characters long, and can contain

all printable characters except @, [, ], ', ", =, and commas.

Alias Name Displays the Alias Name (as specified in the Alias module).

Channel

Number

The valid range for both Binary and Changes (counter) inputs is 0..15,

corresponding to physical inputs Input01..Input16. The Binary input with

Channel Number 0 maps the first binary input Input01, and the Counter input

with Channel Number 0 counts the changes of the first binary input Input01,

and so on. Input13 - Input16 provide the status of the four outputs. If current is flowing through the associated relay contact, a value of 1 will be reported.

Meta Type This field is not editable and is only displayed on the All Points tab. For Binary

inputs this field will be blank and for Changes (counter) points it will be Changes.

Filter Time

(msec)

The binary input must remain in the new state for at least the determined contact

Filter Time for the new state to be recorded by the OrionLXm. The time

recorded will be the initial change of state time (prior to the filter). If the input

remains in the new state for less than the contact Filter Time, no change of

state and no event will be recorded. The default setting for the contact Filter

Time is 0. The contact Filter Time does not have an upper limit.

Debounce Time

(msec)

After the contact Filter Time expires, all input state changes are disregarded

until the Debounce Time has elapsed. Then the binary input is monitored for

changes again. The default setting for Debounce Time is 0. The Debounce

Time does not have an upper limit.

Chatter Count If more input state transitions occur than are defined in the Chatter Count field,

the point is put into the Chatter State. The Chatter Time field defines the sliding

interval, When the input stabilizes and the chatter falls below the configured

Chatter Count for the current sliding window, the point is again reported

normally with its current state and events. The default setting for Chatter Count

is 1000 state changes. The Chatter Count does not have an upper limit.

OrionLXm

C-44

Parameter Description

Chatter Time

(usec)

Interval in microseconds of the sliding interval of time used with the Chatter

Count value. The default setting for Chatter Time is 60000.

Min/Max

Values

Each Changes (counter) point has a minimum and maximum value. The minimum

and maximum values are used to normalize the value from the I/O, and make it available to other ports in the Orion. For a complete discussion of scaling, refer to NovaTech’s Analog/Accumulator Scaling Technical Note.

Table C-15: Configured IIO Input Points

Output Setup

Click Outputs in the left pane to set up the output points of the I/O card. In the center pane, highlight

the discrete output points which are desired in the OrionLXm mapping table and realtime database. Then click >> to move these points to the pane on the right as shown in Figure C-41.

Figure C-41: IIO Outputs Setup

Parameter Description

Point Name The Point Name and the Device name are combined into the Tagname which

references the point within this port, as well as all other ports/protocols where that point might be used. Using self-explanatory names facilitates online monitoring of the Orion’s operation. This string can be up to 50 characters long, and can contain

all printable characters except @, [, ], ', ", =, and commas.

Alias Name Displays the Alias Name (as specified in the Alias module).

Channel

Number

The valid range for discrete outputs is 0..3, corresponding to physical outputs Output01..Output04.

OrionLXm

C-45

Parameter Description

Mode Each output point must be assigned one of the following three modes or output types (see also Figure C-42).

Output

Type

Description

TC If a point address is designated as Trip/Close, two consecutive

physical outputs are used. Trip/Close points must start on either

Channel Number 0 (Output01) or Channel Number 2

(Output03). The first output is pulsed if a Trip command is

received and the second output is pulsed if a Close command is

received. When the On Time expires, the output is set to

Off/Open again. For example, if Channel Number 0 is configured

as TC, then output Output01 is the Trip coil, and output

Output02 is the Close coil.

Command Output1 Output2

0 (Trip) Pulsed ---

1 (Close) --- Pulsed

Pulse A Pulse output is pulsed with the time specified in On Time when

a command is received. A Pulse output is mapped to a single

output coil.

Latch A Latch output stays in the commanded position after the

command is received. A 0 opens the coils, and a 1 closes the coil.

A Latch output is mapped to a single output coil.

Timer

Override

Allows overriding of On Time, Off Time and Pulses received from the slave

port. If checked, the user defined On Time, Off Time and Pulses are used

instead of values sent to the OrionLXm slave port. If unchecked, the On Time,

Off Time and Pulses will only be used if the value sent to the slave port is 0.

This applies only to TC and Pulse output types.

On Time

(msec)

Number of milliseconds to pulse an output. Only applies to TC and Pulse output

types.

Off Time

(msec)

Number of milliseconds between output pulses. Only applies to Pulse output

type.

Pulses Number of output pulses to send. Only applies to Pulse output type.

Table C-16: Outputs Setup

OrionLXm

C-46

Figure C-42: Output Point Type Setup

OrionLXm

C-47

Logic The Orion provides five logic options (Figure C-43).

Figure C-43: Logic Options

Math and Logic

Math and Logic sets up the full logic module. The logic module processes the selected input points

and output points and the programmed logic. It can set any input or output point configured in the

OrionLXm. Math and Logic also defines and sets specific logic points which can be used by external

master or slave devices. A complete description of this module is provided in the OrionLX Math and Logic Manual.

OrionLXm

C-48

Advanced Math and Logic

Advanced Math and Logic utilizes the Lua programming language (Lua 5.1.4 – Copyright © 1994-

2008 Lua.org, PUC-Rio). A complete description of this module is provided in the OrionLX Math and

Logic Manual. Advanced Math and Logic supports the following programming elements:

Variable declarations

Conditional statements

Repetitive statements (loops)

Functions For a complete reference of the Lua programming language, refer to the complete online reference manual via the following link: Hhttp://www.lua.org/manual/5.1/manual.html H. LogicPak

The LogicPak module provides two pre-packaged functions:

Automatic switchover between redundant field devices

OR’ing of status bits, such as Comm Fail flags, to combine values from multiple field devices into single bit for the master

A complete description of this module is provided in the LogicPak for Orion Manual. Distribution Automation (DA)

DA sets up the Distribution Automation module which provides control for electrical grid functions and

operations on the distribution level. Before the DA Logic can be set up, all master ports in the OrionLXm that communicate with the respective RTUs in the DA Logic must be set up. A complete description of this module is provided in the DA Logic for Orion Manual. IEC 61131-3 The full set of IEC 61131 programming languages is available for the OrionLXm:

Structured Flow Chart

Function Block Diagram

Ladder Diagram

Structured Text

Instruction Language A complete description of this module is provided in the IEC 61131 for OrionLX Software Manual.

OrionLXm

C-49

5. Communications Menu The following steps show how to connect to the OrionLXm using NCD (NovaTech Configuration Director) either by way of a serial connection or an Ethernet connection. Note: During the initial setup of the OrionLXm, its IP address must be entered using the serial

MMI as described in Network Menu. If another terminal software program is being used, consult the documentation supplied with that software for setup of a connection to the OrionLXm.

Select the Communications tab and choose Online Connections as shown in the following figure.

Figure C-44: NCD Communications

Note: When a previously configured connection does not seem to work as intended, port A

allows reloading the configuration into the Orion and/or to determine the Orion’s state. NCD supports multiple serial and Ethernet connections. The settings for each connection can be saved to a separate file.

The bottom section of the Manage Connections window allows saving and loading the connection

files from the hard drive. The display of this section can be toggled by clicking Advanced >> and

<< Simple .

OrionLXm

C-50

Figure C-45: Manage Connections

OrionLXm

C-51

Button Function

New Connection Creates a new connection, and opens the window for configuration as shown in Figure C-47. In this window, the connection name is

entered, such as Washington County Substations.

Delete Connection Deletes the highlighted connection.

Edit Connection Opens the window (Figure C-47) for editing the highlighted connection.

Connect Uses the parameters from the highlighted connection to connect to an Orion.

Close Closes the Manage Connections window.

Advanced >>

<< Simple Toggles the display of the following five options.

Group Folder Actions

Create New Creates a new folder for connections, such as Western Utah.

Under a folder, new specific connections can be created, such as

North or West. Folders can be nested. This allows easy

connection management for multiple devices or locations.

Deleted Selected Deletes the currently selected folder and all connections in it.

Rename Selected Renames the currently selected folder.

File Actions

Load File Create a new .conn file for saving all connections presently displayed in the Connections pane.

Save Configuration As Saves all current connections to a file as shown in Figure C-46.

Load File Load a previously saved connection file.

Table C-17: Manage Connections

OrionLXm

C-52

Figure C-46: Creating/Saving/Loading Connection Files

OrionLXm

C-53

Figure C-47: Connection Information

OrionLXm

C-54

Parameter Description

Connection Name The name entered here is used to display the connection in Figure C-45.

File Transfer

Packet Size

The default value is 1024 bytes. To facilitate communication on slower

connections such as radio modems, this value can be set to 128 bytes.

Serial

TCP/IP Connection

SSH

Telnet

These four buttons select the type of connection. Only one button can be selected for a connection. If a button is selected, the associated

parameter frame (Serial Connection or Settings) is enabled, while

the other frame is disabled.

Serial Connection

Comm Port Selects the COM port used to connect to the Orion. If Show All is

checked, any COM port between 1 and 256 can be selected, whether it is

installed or not on the PC. If Show All is not checked, only the COM

ports installed on the PC will be available for selection.

Parity None, Odd, or Even can be selected.

Data Bits 7 or 8 data bits can be selected.

Stop Bit 1 or 2 stop bits can be selected.

Baud Rate Baud rates between 1200 and 115200 baud can be selected from the

dropdown list.

Settings

Host Address Enter the IP address of the Orion that this connection is set for.

Port Enter the port number used in this connection.

Terminal Colors

Back Color Background color of the window used to communicate with the Orion.

Fore Color Foreground color of the window used to communicate with the Orion.

Font Font used to display text in the window used to communicate with the Orion.

Table C-18: Connection Information

Note: The communication parameters for connection to serial Port A of an OrionLXm are

115200N81. Clicking OK saves the parameters and returns to the Manage Connections window (Figure C-45).

Clicking Cancel abandons any changes and returns to the Manage Connections window (Figure

C-45).

OrionLXm

C-55

Communication Window After highlighting the desired connection and clicking Connect in Figure C-45, NCD will open the

following communications window. Refer to section OrionLXm MMI of this manual for more information regarding the OrionLXm MMI.

Figure C-48: NCD Comm Window

The toolbar at the top of the window provides the following tools.

Parameter Description

Edit Connection Clicking this button opens the Connection Information window shown

Figure C-47 for editing the connection parameters.

Start Capture/

Stop Capture

Any communication between the PC and the OrionLXm can be logged to a file for analysis or tech support purposes. This button is a toggle button, i.e. either

Start Capture or Stop Capture is displayed. After clicking Start

Capture, the log file name and location on the PC’s hard drive must be

specified. While the communication is being logged, Stop Capture is

displayed. Clicking on it will stop the logging and close the log file.

Reset

Configuration

Clicking this option disables the current configuration file of the connected Orion. The type of currently connected Orion (OrionLXm, Orion5r, etc.) must be specified. After the subsequent warm boot, the OrionLXm will operate without the configuration file. This option can be used, for example, if the current configuration file contains improper port or mapping parameters that cause operation errors.

Disconnect Closes the current connection.

Table C-19: NCD Comm Window

OrionLXm

C-56

6. Window Menu If multiple configuration and communication windows are open, this option allows

Cascading all windows

Closing all windows

Switching to one of the currently open windows

Figure C-49: Window Menu

OrionLXm

C-57

7. Help Menu The Help Menu contains both protocol information as well as version and system information regarding NCD.

Figure C-50: Help Menu

Protocol Information This option provides a point count for all currently open configurations as shown below.

Figure C-51: Protocol Information

OrionLXm

C-58

About This option displays the NCD version information.

In addition, specific driver information can be obtained by clicking Control Versions… .

General information about the PC hardware, drivers, and operating system can be obtained by clicking

System Info… . Details of all currently installed files can be seen by clicking the

Program Versions… button.

General information about the PC hardware, drivers, and operating system can be obtained by clicking

System Info… .

The information provided by these buttons may be required for technical support.

Figure C-52: NCD Version Information

OrionLXm

D-1

D. OrionLXm Webpage

OrionLXm

D-2

I. Introduction When connected to a LAN or the Internet, the OrionLXm provides a webpage for user settings and diagnostics. All current web browsers are supported, including Internet Explorer (Version 6, 7, and 8), Firefox (Versions 2 and 3), Opera, and Safari. By default, the OrionLXm does not enable unsecured

HTTP. Secure HTTPS is enabled. To start working with the OrionLXm webpage, type https:// and

the IP address of the OrionLXm in the browser URL window. Example:

Figure D-1: Connect with OrionLXm

After connecting to the OrionLXm via HTTPS, the browser may display a certificate warning. The OrionLXm ships with a self-signed key used for all encrypted communication including HTTPS. NovaTech does not include a key file issued by a Certificate Authority (CA) such as VeriSign, because the OrionLXm leaves NovaTech’s control when shipped. Since the OrionLXm key file is not certified by a Certificate Authority (CA), the browser warns that an individual could have obtained the key file and could monitor network communications between the PC and the OrionLXm. For setting up keys, see chapter Key Management. When using Internet Explorer, clicking Yes displays the OrionLXm webpage.

Figure D-2: Internet Explorer Security Warning

When using Firefox, the following warning message allows adding an exception by clicking the link - Or you can add an exception…

OrionLXm

D-3

Figure D-3: Firefox Security Warning

Firefox will respond with the following screen. First click Get Certificate , then make sure that

is checked, and finally click Confirm Security Exception .

Figure D-4: Confirm Firefox Certificate

OrionLXm

D-4

Once the OrionLXm’s certificate has been accepted, the following window is displayed for entering the OrionLXm’s user name and password.

Figure D-5: OrionLXm Login

After entering the username and password, the OrionLXm homepage is displayed (Figure D-6). The tabs under the OrionLXm logo are the various main headings for diagnostics and settings. Note: The tab headings shown may vary depending on the various protocol packages and

options installed on the Orion. The figures shown in the following figures represent the standard tab headings.

Figure D-6: OrionLXm Homepage

OrionLXm

D-5

In order to access the OrionLXm and make changes, click Unlock in the upper right corner. A window

for entering the password is displayed. After 30 minutes of user inactivity, the OrionLXm will automatically return to the “Locked” state, which limits user operation.

Figure D-7: OrionLXm Unlock Prompt

Menu Function

Home View basic OrionLXm information, including Serial Number, Orion Main Firmware Version, Uptime, Active Configuration, Hostname, and Ethernet Address.

DataValues View and force values of Input and Output points by port.

Devices View and clear Poll and Response counters for each slave device connected to the OrionLXm.

Alarms View and acknowledge alarms by point name, zone, etc.

Archive View archived values based on standard or custom filters, such as time, device, point name, etc.

System Download system information, view key file with licensed options, reboot the OrionLXm, view version information, serial and Ethernet port statistics, and more information.

Logs Set logging period and levels (critical, emergency, warning, info, etc.) for the OrionLXm software and hardware components.

Files Transfer files to and from the OrionLXm including NCD configuration files, SVG, and update packages, and system files.

Settings Configure Users, Authentication, Networking, Modem Settings, System, Firewall, OpenVPN, Key Management, Services, Scheduler, Database Settings, and SVG Settings.

Contact Provides NovaTech address, phone number, and email address.

Table D-1: OrionLXm Homepage Menu Items

The following chapters will discuss each tab on the OrionLXm homepage in detail.

OrionLXm

D-6

II. Home Tab The Home tab provides general information about the OrionLXm including serial number, Distro version, firmware information, uptime, active configuration, and hostname. If user web graphics are used, a link will also be available to these graphics from the home page under

User Links on the right side (chapter WebUI provides more information). In this example, home.svg is

available.

Figure D-8: OrionLXm Home Tab

OrionLXm

D-7

Item Description

OrionLX Serial # Each OrionLXm has a unique 5-digit serial number. This serial number is required when requesting support from NovaTech. The serial number is also found on the identification label on the rear of the OrionLXm.

OrionLX Distro

Version

Displays the version of the Distro currently running in the OrionLXm.

OrionLX Firmware

Version

OrionLX Firmware

Date

Displays the version of the firmware currently running in the OrionLXm.

More information is available under the System tab.

Linux Version Displays the version of the Linux kernel currently running in the OrionLXm.

OS Uptime Displays the time since the OrionLXm Linux operating system has been running in days, hours, minutes, and seconds. This will reset after a full restart or after a power cycle.

Orion Process Uptime Displays the time since the OrionLXm process has been running in days, hours, minutes, and seconds. This will reset after a full restart, quick restart, or power cycle.

Active Configuration The NCD configuration file that is currently running in the OrionLXm.

Date/Time Current date and time as well as time zone.

Hostname The hostname is used to identify the OrionLXm on the network. This is found on the top right corner of every page. Using the hostname requires a DNS server.

eth0 Address

eth1 Address

eth2 Address

Shows the configured IP address for each installed Ethernet port. Up to three ports can be installed. If a port is set up for DHCP instead of a static IP address, this information is omitted.

Table D-2: OrionLXm Home Tab

OrionLXm

D-8

III. DataValues Tab The DataValues page allows real-time viewing and forcing of each input/output point’s value and point information on a port-by-port basis. Each data point in the OrionLXm will typically be displayed on at least two ports:

The master port of the OrionLXm that communicates with a slave device and obtains the input point value from that slave device or sends the output point value to the slave device.

The slave port of the OrionLXm that communicates with a master station and sends the input point value to that master station or receives the output point value from that master station.

The OrionLXm maintains the value of each input point and each output point in the realtime database as a normalized value, i.e. percentage of full scale. For complete details, see NovaTech’s Analog/Accumulator Scaling Technical Note. Forcing the value of input points and output points is available only if the logged in user has permission in the Users settings. Forcing an input/output point means that the OrionLXm will use the value(s) entered on the OrionLXm webpage as described below when communicating to the SCADA master (to which the Orion is a slave) or RTUs/IEDs (to which the Orion is a master) instead of using the values from live devices the Orion communicates with. This is useful for testing, or when the Orion is installed and not all other devices or communication links are available yet.

As shown on Figure D-9, select the inputs or outputs of the port whose point values are to be

monitored or changed.

Figure D-9: DataValues – Main Page

OrionLXm

D-9

1. View Input Values

After clicking on inputs for a specific port, all the inputs on that port are displayed.

Figure D-10: DataValues – View Input Values

Up to 30 input values can be displayed on one page and sorted by Device. If more input points are

mapped to the port, pagination allows browsing of the pages. Points that are offline are highlighted in red to indicate an error. Points can be forced from the input page by clicking the desired point name. If the point does not highlight when moving the mouse over it, the login account does not have the permission to force inputs. The Users chapter provides information on setting user permissions.

The links <<first, <prev, next>, last>>, and the page numbers enable browsing of the pages as

follows.

Link Function

<<first Skip to the first page.

<prev Go to the previous page.

next> Go to the next page.

last>> Skip to the last page.

1, 2, 3, 4, … Go to the specific page.

Table D-3: DataValue – Browsing Pages

OrionLXm

D-10

Toggle Options

When viewing the above page (Figure D-10), click the Toggle options button to customize the

page by adding and removing columns. This drops down a list of columns to display as well as point

value notation (decimal, octal, hexadecimal) (Figure D-11). The Save option uses web client cookies

to retrieve these settings. When the cookies are cleared or a different machine is used, these settings will

return to their default values. These settings are universal for all ports. The Reset button returns to

the last saved settings which are saved using cookies on the PC.

Figure D-11: DataValues – Toggle Options

The displayable columns are explained in the following table.

OrionLXm

D-11

Column Description

Alias

Name

Each point has two text descriptors for user identification. A Name, also known as

Tagname, is required and usually describes the end device where the point

originates, such as Breaker424@HV Relay. An Alias is an optional descriptor

that is intended to display the SCADA master terminology, such as West Sub

Breaker 424 HV Relay.

Default: Name column is displayed, and the Alias column is not displayed.

Device Every point belongs to a device. This column displays the user defined device

name, such as HV Relay, and is convenient for sorting multi-dropped ports.

Default: Device column is displayed.

Type

Point #

Protocol-specific point number and point type. Some examples of point types are

AI for Analog Input, BI for Binary Input. Depending on the protocol and the way

it addresses points, points may be numbered in hexadecimal (17h), decimal (23),

or octal (27o). The MMI will display the point address the way the specific

protocol addresses points. If there is a bit position within a word, the point

number is displayed as 17:03, which means bit 3 in word 17. Bit numbering and

word sizes are protocol dependent, i.e. bit 1 can be LSB or MSB, and a word can be 8 bits or 16 bits. The respective protocol manual provides additional information.

Default: Type column is displayed, and Point # column is displayed.

Changes Counter that displays the number of point changes since the OrionLXm (re)start. For analog or accumulator points, every data change increments the corresponding change counter by 1. For digital points, every 0-1 or 1-0 transition increments the change counter by 1.

Default: Changes column is not displayed.

Fails Counter that displays the number of failed polls since the Orion (re)start.

Default: Fails column is not displayed.

Successes Counter that displays the number of successful polls since the Orion (re)start.

Default: Successes column is not displayed.

Value Current value of the point as per communication with an end device. If the point has been forced, the forced value will be displayed instead of the value from the end device.

Default: Value column is displayed.

Percent Full

Scale

Percent of full scale of the current value. For example, if the value is scaled from

–2048 to 2047, and the current value is 1024, this file will show 0.75 for 75%.

Default: Percent Full Scale column is displayed.

Status If the corresponding value is updated from the remote device, the field will show

Online. If there is any type of communication error with the remote device, the

field will show Offline.

Default: Status column is displayed.

Forced No or Yes, depending on whether the value is obtained from the slave device, or

overridden by a value entered at the Orion MMI.

Default: Forced column is displayed.

Table D-4: DataValues – Input Point Display Options

OrionLXm

D-12

2. Force Input Value Forcing or overriding input values allows for the testing of the correct transmission of values to the master polling the Orion, without having to generate those values in the end device in the field. The ability to force inputs depends upon the user’s permission settings. Forcing inputs can be useful under several circumstances:

The end device and/or the communication to it have not yet been installed or are temporarily not available.

Generation of test values in the end device is too complicated or not possible, depending on the end device.

In order to force a point, first select the port of the point that is to be forced (see Figure D-10). After clicking on the point, the following screen (Figure D-12) will appear. If the desired point does not highlight when moving the mouse over it, then the account used to login does not have permission to force this point.

Figure D-12: DataValues – Force Input Value

With this command, the OrionLXm data point will indicate an equipment state or condition to the SCADA master that is only simulated, and does not reflect the actual state or condition. This may lead the SCADA master computer or personnel to initiate operations based on the simulated state as opposed to the actual state. The necessary permissions must be obtained from control center and other departments in accordance with your corporate safety and operating guidelines. Failure to do so could result in equipment damage, injury, and/or death.

OrionLXm

D-13

By entering the following parameters, input data points can be forced to report those values.

Item Description

Scaled Value

Percent Full Scale

Enter either a percentage or scaled value. In the drop-down box,

select one of these two values. For digital input points, enter 0/1 or

0/100 percent, and for analog values either the scaled value, or its

percentage of full scale.

Examples:

For a digital value of 1 (On), enter either 1 and Scaled Value, or

100 and Percent Full Scale.

For an analog value of 6 with a scaling range of 0..10, enter either 6

and Scaled Value, or 60 and Percent Full Scale.

Comm Status The point can be simulated as being either Online or Offline.

Online indicates that the value is received online from the end

device. Offline indicates that there is no communication with the

end device, but rather the most recent value as of the time of the last communication.

Time to Remain Forced Determines how long (in minutes) the point will stay in the simulated state before returning to the actual value as obtained from the end device.

Table D-5: Data Values – Force Input Values

After entering the above parameters, clicking Force Value writes the entered value to the data point.

Clicking Cancel aborts the operation. Click the Clear Input Override link (Figure D-9) to clear

all forced values.

OrionLXm

D-14

3. Viewing Output Values

In order to view output values, i.e. values sent from a master station to an end device, click on outputs

of the desired port.

Figure D-13: DataValues – Select Output Values

The last output value sent to the device will be displayed (Figure D-14). This value may have been sent by a master, to which the Orion is connected as a slave, or the value may have been generated by logic running in the Orion, or the value may have been forced by user input.

OrionLXm

D-15

Figure D-14: DataValues – View Output Values

Up to 30 values can be displayed on one page. Pagination is provided to allow jumping to different pages. Table D-3 provides a listing of the pagination commands. Chapter Toggle Options provides a complete description of the Toggle options button.

OrionLXm

D-16

4. Force Output Values This function sends output values to connected slave/end devices as entered by the OrionLXm. During normal operation, any output commands sent to those devices would be issued by a front end/SCADA master, and merely passed-through by the OrionLXm. This function can be used for localized testing without involving the entire system end-to-end. The ability to force outputs depends upon the user’s permission settings. Output points can be forced by clicking on the desired point name in Figure D-14. If the output point does not highlight when moving the mouse over it, the login account does not have permission to force outputs.

This command can possibly operate live equipment on the end device,

the same way it would be operated locally, or from the front end/SCADA master. The necessary permissions must be obtained from control center and other departments in accordance with your corporate safety and operating guidelines. Failure to do so could result in equipment damage, injury, and/or death.

Clicking on the desired point displays the following screen.

Figure D-15: DataValues – Force Output Value

The window shown in Figure D-15 is a “generic” screen in that it shows all parameters possibly needed, whether the output point is a simple discrete output, a select-before-operate output, a trip/close output, a pulse output, or an analog output/setpoint. Depending on the protocols used to connect the front end/SCADA master to the end device, only a selection of the listed types will be available, as either the protocol between the front end and the Orion, and/or the protocol between the Orion and the end device

OrionLXm

D-17

may not support all point types. The only value that must be entered is the value required by the point type. The following table lists the parameters.

Item Description

Scaled Value

Percent Full Scale

Enter either a percentage or scaled value. In the drop-down box,

select one of these two values. For digital output points, enter 0/1

or 0/100 percent, and for analog output values enter either the

scaled value, or its percentage of full scale.

Examples:

For a digital value of 1 (On), enter either 1 and Scaled Value, or

100 and Percent Full Scale.

For an analog value of 6 with a scaling range of 0..10, enter either 6

and Scaled Value, or 60 and Percent Full Scale.

Duration Usually, trip/close, raise/lower, and pulse outputs require a duration. If none is entered, and a default value is used in the point configuration, the default value is used instead.

Pulses For pulse output points, the number of pulses may be required unless it is predefined by the respective protocol.

Offtime For pulse output points, the offtime between on-pulses may be required as well.

Table D-6: Data Values – Force Output Values

After entering the above parameters, click Force Value to perform the operation as set up. Clicking

Cancel aborts the operation.

OrionLXm

D-18

5. View Tagging Archive

The View tagging archive link allows a user to determine whether or not any tags which may have

been created in the OrionLXm HMI menus have been applied.

The View tagging archive link is located above the Clear Input Override link on the

DataValues WebUI tab. Click the View tagging archive link to display a summary for each tag

entered. The summary for each tag consists of the parameters described in Table D-7.

Figure D-16: DataValues - View Tagging Archive

Any tag which has been applied will result in an entry being created in the tagging archive. Once the entry appears in the tagging archive, the user can remove the tag if desired. If a tag in the tagging archive is removed, the archive will display a time stamp parameter indicating when the tag was applied and removed (Figure D-17).

OrionLXm

D-19

Figure D-17: DataValues - Applied Tags

Item Description

Point Name The Point Name and the Device name are combined into the Tagname

which references the point within the port, as well as all other ports/protocols where that point might be used. Using self-explanatory names facilitates online monitoring of the OrionLXm’s operation. This string can be up to 50 characters long, and can contain all printable

characters except @, [, ], ', ", =, and commas.

Alias Point Name Each point has two text descriptors for user identification. Name, also

known as Tagname, is required and usually describes the end device

where the point originates, such as Breaker424@HV Relay. An Alias is

an optional descriptor that is intended to display the SCADA master

terminology, such as West Sub Breaker 424 HV Relay.

Tag Type Generally tags are identified by one of three types (or by user-specified

custom tags). The three default tag types are Do Not Operate,

Information, and Out of Service.

Applied Time Stamp Time stamp alerting the user to the moment the tag went into effect.

Removed Time Stamp Time stamp alerting the user to the moment the tag was released or removed.

User Name User name required at login.

Comment Optional field. Comments can be used to alert the user to special circumstances or instructions.

Table D-7: Data Values - Tagging Archive

OrionLXm

D-20

IV. Devices Tab The Devices page displays communication statistics about all slave devices attached to the OrionLXm,

i.e. devices that are being polled by the OrionLXm. The Reset All Counters link resets the Polls and

Responses counters for all devices to 0. The counters roll over at 232

(= 4,294,967,296). Devices that are offline are displayed with red background to indicate an error. If more devices are connected to the OrionLXm than fit on one page, pagination allows browsing and jumping pages (see Table D-3 for a list of commands).

Figure D-18: Devices Page

OrionLXm

D-21

V. Alarms Tab The Alarms page shows all currently raised alarms in the Orion. The Alarms list can be sorted by clicking the respective column headers. Alarms can be acknowledged individually or collectively. Acknowledged alarms are moved to the Alarm Archive. The colors for specific alarm levels and unacknowledged/acknowledged are set up as described in chapter Alarms. Point setup for alarming is described in the Alarm-Archive-Retentive Module for OrionLX Software Manual.

Figure D-19: Alarms Tab

The list can be filtered by specifying a Pointname or Alias, and/or by specifying a date/time window in

the Filter options section (Figure D-20). Figure D-21 shows the unfiltered archive.

Figure D-20: Alarm Archive with Filter

OrionLXm

D-22

Figure D-21: Alarm Archive without Filter

OrionLXm

D-23

VI. Archive Tab The Archive page displays the archived events. The events can be viewed in their entirety, or filtered to the 1000 most recent records, or filtered by clicking Custom filters . Via Rows per page, the

records can be viewed 15, 25, 50, 75, or 100 records per page.

Figure D-22: Archive - 1000 Most Recent Records

OrionLXm

D-24

Alternatively, the archive can be filtered by entering a Point Name or Alias, and a date/time window

(Figure D-23). If multiple Point Name or Alias names are entered, they need to be separated by

commas. After clicking Update view , only the records matching the filter criteria will be displayed.

Figure D-23: Archive with Custom Filter

Trends can be viewed by clicking View Trending . In this window, the point’s Point Name or

Alias, and a date/time window must be entered (Figure D-24). After clicking Update view , the

trending curve for the specified point will be displayed (Figure D-25).

OrionLXm

D-25

Figure D-24: Archive – View Trending

Figure D-25: Archive – Trend for Multiple Data Points

OrionLXm

D-26

VII. System Tab The System page allows viewing and updating of operating system information such as versions, serial and network port statistics, and OrionLXm application versions. Table D-8 describes the information displayed on the system page.

Figure D-26: System Page

OrionLXm

D-27

Figure D-27: System Page

OrionLXm

D-28

Figure D-28: System Page

OrionLXm

D-29

Figure D-29: System Page

Figure D-30: System Page

OrionLXm

D-30

Item Description

Uptime The time the OrionLXm Linux operating system has been running, in days, hours, minutes, and seconds. This will reset after a full restart or power is reapplied.

Linux Version Version of the currently installed Linux kernel.

Update By clicking this button, software already installed on the OrionLXm can be updated. Refer to the Updating OrionLX Distro Field Instructions for a complete description of the update process.

Install By clicking this button, new software can be installed on the OrionLXm. Refer to the Adding OrionLX Protocols Field Instructions for a complete description of the installation process.

Download system info

as .tar

Compresses all system diagnostic log files into one .tar file. This

file can be transferred to the PC. NovaTech support engineers may request this file to support the OrionLXm.

View key file View all protocols that this OrionLXm is licensed for. If a protocol is listed in the key file, the corresponding driver must also be loaded in the OrionLXm for the protocol to be functional. To check for specific protocol libraries, see the Package Versions table.

Reboot Orion Force a warm start of the Orion.

Core file The core file can be transferred to the PC if needed. It is used by Technical Support to analyze the OrionLXm’s performance.

File System Display the status of the OrionLXm file system, including overall size, available space, mounting points, etc.

Module Versions Lists port, name, version, and date for all protocol drivers and the main.exe running on the OrionLXm. All OrionLXm protocol packages can be verified in this table.

Package Versions Displays the application packages and their versions which are installed on the OrionLXm.

Serial Ports Displays all serial ports, the number of bytes transmitted and received on each port since the last boot, and the status of the RS-232 lines.

Ethernet Interfaces For each Ethernet port, the port’s name, MAC address, IP address, and subnet mask is displayed.

Network Stats–Receive

Network Stats–Transmit

Displays the number of transmitted and received bytes, packets, errors, etc. for each network interface since the last reboot.

/proc/meminfo Displays memory information.

/proc/interrupts Displays interrupt information.

Table D-8: System Page Information

OrionLXm

D-31

VIII. Logs Tab The Logs page displays the desired time period and information level (alert, critical, debug, emergency, etc.) for various programs. The events meeting the selected criteria can be downloaded into a .csv (Comma Separated Values) file by clicking Download.CSV .

Figure D-31: Logs Page

OrionLXm

D-32

IX. Files Tab The Files page allows uploading, downloading, activating, and removing configuration files from the OrionLXm. This page also allows the transfer of system files and update packages. File transfers between the PC and the OrionLXm use the HTTPS/HTTP file transfer protocol.

User Files Files can be transferred to the OrionLXm by clicking the Select files... button and specifying

the file locations in the PC’s file system. Alternatively, files on the PC can simply be dragged and dropped onto the User files area of the webpage. Click the Send button to transfer the selected

files to the OrionLXm (Figure D-33).

Figure D-32: Files Page

OrionLXm

D-33

Figure D-33: Send Files to OrionLXm

If a file selected for transfer has the same name as the active configuration, a warning message is displayed. If the file is then actually transferred, the active configuration will be overwritten and the OrionLXm application process will automatically restart.

All available files are listed under User files. The following files can be transferred between the PC

and the OrionLXm using the Files page.

File Extension File Use Description

.ncd Configuration file OrionLXm configuration file.

.bas Logic file Logic in “Basic” syntax executed by the OrionLXm.

.gpg Digitally Signed Driver file Only downloaded when a new driver becomes available.

orionlx.ntk Key file They key file specifies what protocol drivers a specific OrionLXm is licensed to run. Even if a specific driver is downloaded into the OrionLXm, it will not execute without the proper license in this file. Contact NovaTech support for troubleshooting.

.svg Scalable Vector Graphics file User webpages.

.js Java Script file User webpages.

.tar Compressed file Contains system files.

Table D-9: OrionLXm File Types

OrionLXm

D-34

The listed files can be sorted by filename, size, and date by clicking the respective column headers

Filename, Size, and Date.

Clicking a file name opens the file for viewing. Files of type .ncd and .bas are displayed as ASCII text. Files of type .svg are displayed as graphics. Each of the files can be selected by clicking the checkbox to the left of the file name. Then, either the

Download or the Delete button can be clicked, and the operation is applied to all selected files.

Clicking the Download button transfers all selected files from the OrionLXm to the PC.

Clicking the Delete button deletes all selected files from the OrionLXm non-volatile memory.

Selecting the Active Configuration From all configuration files that have been transferred to the OrionLXm, the active configuration can now be selected from the drop-down box shown in Figure D-34. A separate prompt requires confirmation for switching to another configuration (Figure D-35). Note that all files belonging to a configuration must have been transferred to the OrionLXm, such as .bas, .svg, etc. for the selected configuration and .ncd file to operate correctly.

Figure D-34: Select Active Configuration

Figure D-35: Confirmation Prompt

OrionLXm

D-35

System Files The System files section includes system files parameters such as date and size (Figure D-36). The system files contain user-configured settings which have been set and saved using the OrionLXm webpage. These files can be moved from one Orion to another, assuming the logged in user has the appropriate permissions. The files can be transferred to the PC by clicking the Download all button

at the bottom of the list. System files cannot be transferred individually to the PC.

The System Files section allows sorting on Filename, Size, and Date by clicking the respective column

header. The sort will alternate between ascending and descending.

Figure D-36: System Files

OrionLXm

D-36

X. Settings Tab Configuration and system parameters such as user authorization, modem settings, alarms, or scheduling can be set up on the Settings page. All settings configured through these pages are saved on the OrionLXm and can be transferred to the PC for backup (see System Files). These settings can also be transferred to a spare OrionLXm instead of being manually configured on a spare OrionLXm.

Figure D-37: Settings Page

The following table provides a brief overview of available settings behind each link.

OrionLXm

D-37

Menu Function

Users Manage users, set passwords and rights, allow services and operations, account expiration, menu or command line upon login.

Authentication Rules Set User Lockout rules, Password rules, and Remote Root Login permission.

Remote Accounts Set Account Caching, Remote Account, LDAP, and Kerberos Authentication parameters.

Firewall Set up firewall rules for receiving, sending, and forwarding of packets.

OpenVPN VPN client, server, and network settings.

Key Management Create, manage, and transfer keys in the OrionLXm.

System Log Set system log destination and filters.

Networking IP networking, such as IP address, and connection settings.

Modem Set up internal modem on port D, and external modem or console on port B.

System Set time zone, IRIG-B Input/Output parameters, and NTP Time Sources.

Serial Set up the S4 communication cards for RS-232 or RS-485/422.

WebUI Set up webpage links, HMI tagging, and OrionLXm webpage access rules.

Alarms Alarm notifications, alarm colors, and alarm archive settings.

Database Setup of archive, retentive, and tagging database and database access management.

Tagging Setup and management of tags.

Cascading Slave Settings for cascading OrionLXm's.

Services Enable Telnet, FTP, and HTTP unsecured system protocols.

Scheduler Set up recurring tasks in the OrionLXm, such as emailing of .csv export files from the archive and alarm database, and moving files via SFTP/FTP from the OrionLXm to a host computer.

Table D-10: Settings Page

OrionLXm

D-38

1. Users

Password Change If the account used for login does not have the permission to manage users, the Change Password page is displayed at this point. This is the only available option for users without user management authorization.

Figure D-38: Change User Password

Account Management

For accounts that belong to the useradmin group (see Table D-12), the following screen (Figure D-39) is

displayed instead of the screen in Figure D-38. The Users page allows adding, modifying, and deleting users as well as the setting of user authorizations. The following account authorizations are set up as shown in Figure D-40.

OrionLXm

D-39

Figure D-39: Settings/Users

OrionLXm

D-40

Function Description

Username User name required at login.

Password

Verify Password

Sets the user password. The password rules are configured on the Authentication Rules page.

Lockout Information Provides information on the number of failed login attempts made since

the last successful login for the selected Username.

Login Type Defines the user interface provided by the OrionLXm after logging in over Telnet, SSH, and serial connection.

Menu Display of OrionLXm MMI. See OrionLXm MMI for details.

Text Command line interface. Typing ntsh will display the

OrionLXm menus from the command line.

iDial This login type is used in conjunction with the iDial software

option. After authentication, a user with this login type will enter the iDial command line interface. If the iDial software option is not configured in the active .ncd file, the user session will be terminated immediately after authentication.

Groups The groups the particular user is a member of. Each group grants certain permissions to a user as explained in Table D-12.

Table D-11: User Account Management

Under Edit Users, click any user account to modify the properties and authorizations.

For adding new users, click Add new user or Add User depending on the current screen.

Once the setup is complete, click Save Settings to save the current settings.

In order to delete a user account, click the respective account, then click Delete User at the bottom

of the page. Note: NovaTech recommends creating new accounts and deleting the default novatech

account. Setting up a second administrator account to be used only in an emergency (e.g. when the first administrator account has been locked out, or its password has been misplaced) is strongly recommended.

OrionLXm

D-41

Figure D-40: User Account Management

OrionLXm

D-42

Function Description LDAP

Group ID

alarming (1-5) The Alarming checkboxes are used with the Alarm/Archive/Retentive

option. These levels can be used to enable different users to

acknowledge different types of alarms. Up to 5 levels of

acknowledging alarms are supported.

Example: a breaker maintenance issue could be set up so only a

maintenance engineer can acknowledge, while a breaker status

change might be set up for only a relay protection engineer to

acknowledge.

The assignment of points to alarm acknowledgment groups is

described in the Alarm/Archive/Retentive Module for OrionLX

Software Manual.

116 - 120

control (1-5) The Control checkboxes are used with the user webpage options.

These levels can be used to enable different users to send different

controls from a webpage. Up to 5 levels of controls are supported.

The assignment of points to control groups is described in the

OrionLX WEBserver (XML Slave) Software Manual, chapter "NCD

Setup of XML Slave", "Outputs Tab".

121 - 125

cronconfig This group grants a user the ability to change the scheduled tasks on the Scheduler page.

128

forceinput Allows the user to force inputs in the OrionLXm through the

diagnostic port for debugging purposes (see chapter Force Input

Value and Override Input Values).

109

forceoutput Allows the user to force field outputs connected to the OrionLXm

through the diagnostic port for debugging purposes (see chapter

Force Output Values and Send Output Values).

110

ftp Allows the user access to the OrionLXm using FTP. 101

http Allows the user access to the OrionLXm using HTTP and a web

browser.

102

https Allows the user access to the OrionLXm using secure HTTP and a

web browser.

103

modem Allows the user access to the OrionLXm using the dialup modem

over PPP.

105

networkconfig Allows the user to modify and save network parameters on the

Network Settings page. This page can be viewed but not edited by

the users that do not have this box checked.

111

networksecurity Allows the user access to the Firewall page. This page cannot be

viewed by users that do not have this box checked.

114

orionconfig Allows access to the Files page. This page cannot be viewed by

users that do not have this box checked.

108

OrionLXm

D-43

Function Description LDAP

Group ID

packageinstall Allows the user to install updates on the OrionLXm. 113

passthrough Allows the user to use the passthrough option under the system

menu via Telnet/SSH. Passthrough allows users to communicate

with devices that support ASCII protocols.

115

postgres If the optional expanded memory is installed in the OrionLXm and the

Archive/Alarm/Retentive module is available, an SQL database is

provided. Checking this box will allow the user to set up the

PostgreSQL options.

502

ppp This group grants a user the ability to make a dial-in connection and

establish a PPP link using a modem.

127

ssh Allows the user access to the OrionLXm using secure shell. 104

tagging (1-5) Up to 5 levels of tagging for HMI use.

The setup of the tagging groups is described in chapter Tagging.

129 - 133

telnet Allows the user access to the OrionLXm using Telnet. 106

tty Allows the user access to the OrionLXm through the Ports A1 and

A2.

5

useradmin Allows maintenance of this page (adding, deleting, and modifying of

user accounts). This page cannot be viewed by users that do not

have this box checked.

107

viewlogs Allows the user to view system log files. This page cannot be viewed

by users that do not have this box checked.

112

webfiles This group grants a user the ability to view/add SVG pages on the

OrionLXm.

126

wheel This group grants a user who has shell access (the login type Text)

the ability to become the super user (root).

10

Table D-12: User Groups

Note that five alarm groups, five tagging groups, and five control groups are available. For each category (alarm acknowledgment, control, and tagging), the matrix of each group and the users assigned to each group must be carefully designed. The users must be able to perform their job functions, and at the same time be prevented from operations they are not authorized to perform. Each of the five groups of a category (alarm acknowledgment, control, and tagging) are disjoint groups and not supersets of each other (like the groups superuser, administrator, power user, and user are in a computer). This means that assigning a user to control groups 2 and 5 for example, grants permission for operating control groups 2 and 5 only, and not for control groups 1, 3, and 4.

OrionLXm

D-44

2. Authentication Rules The Authentication Rules page sets how user passwords are used. Note that fields marked with an * are required fields.

User Lockout Rules User Lockout rules define the number of consecutive failed password attempts before a user account is locked out or disabled. This is an important setting to prevent unauthorized users from gaining access to the OrionLXm.

Figure D-41: Authentication Rules – User Lockout Rules

Function Description

Enabled Enable/disable lockout rules. When this setting is on, the OrionLXm will use the following settings to decide when to disable a user due to failed login attempts.

Default: On

Max. Login

Attempts

Defines the number of consecutive failed password attempts before the user account is locked out or disabled.

Default: 5

Lock Out

Permanently

Instructs the OrionLXm to permanently disable a user account after a number of failed attempts.

Default: Off

Time Until

Unlock (sec)

Defines the number of seconds the OrionLXm will remain in lockout.

Default: 172800 seconds (2 days)

Temporary Lock

Time (sec)

The amount of time between failed attempts the OrionLXm will lockout.

Default: 3 seconds

Table D-13: User Lockout Rules

OrionLXm

D-45

Password Rules Password rules configure how many digits and the types of characters that are required in a password. A long password with a mixture of uppercase, lowercase, numbers, and special characters is the most secure. This password conformance check is executed when a new user is added or when a user changes the password.

Figure D-42: Authentication Rules – Password Rules

Function Description

Enabled Enable/disable password rules. When this setting is on, the OrionLXm will check user passwords to make sure they follow the rules defined below.

Default: On

Min. Length Defines the minimum number of characters a password must be to be accepted. Default: 8

Min. Digits Defines the minimum number of numeric digits (0-9) that must be used in a password.

Default: 1

OrionLXm

D-46

Function Description

Min. Uppercase Defines the minimum number of uppercase (A-Z) letters that must be used in a password.

Default: 1

Min. Lowercase Defines the minimum number of lowercase (a-z) letters that must be used in a password.

Default: 1

Min. Special

Chars

Defines the minimum number of special character digits that must be used in a password. Special characters include:

! @ # $ % ̂ & * ( ) + , - . / : ; < = > ? “ ‘ [ \ ] _ ̀ { | } ~

Default: 1

Max Repeated Defines the maximum number of times a character can be repeated.

difok Sets the minimum number of characters that must be different when changing a password.

Default: 5

difignore Defines the number of characters in a password before the difok setting is ignored.

Default: 23

Password

History

Defines the number of password changes before a previously used password can be reused.

Default: 3

Table D-14: Password Rules

Remote Root Login

If the Allow Remote Root Login box is checked, remote login will be allowed for the root user.

However, the root user will also need to be given remote login permissions as described in chapter Users.

To do this, enable required connections such as ssh as shown in Figure D-40.

Figure D-43: Authentication Rules – Remote Root Login

OrionLXm

D-47

3. Remote Accounts

The Remote Accounts page (Figure D-47) configures the Account Caching parameters and Remote

Accounts settings. Account Caching specifies where the OrionLXm will find the server in order to

obtain authentication when a password is entered. Remote Accounts configures where the OrionLXm

will find the LDAP server in order to validate user groups. Kerberos Authentication configures the

Kerberos settings. Both LDAP and Kerberos are configured offline in a text editor and saved as separate files on the PC. Once completed, the configuration files (i.e. sysfiles.zip) are uploaded to the OrionLXm through the Files Tab. Examples are shown in Figure D-47.

Before Account Caching and the Remote Accounts functions will work, the SSSD package and its

dependencies must be installed in the OrionLXm. If the SSSD package is already installed on the

OrionLXm, it is listed under the header Package Versions under the System Tab as shown in the

following figure. In this case, proceed to the setup in Figure D-47.

Figure D-44: SSSD Package is Installed

If the SSSD package is not yet installed, run the OrionLXm Updater program to install the SSSD package. For detailed instructions on adding the SSSD package, see Adding OrionLX Protocols Field Instructions. Note that no new license key is required to add the SSSD package. At least 2.6MB of file system space must be available on the OrionLXm before installing the SSSD

package. The available file system space is listed after /dev/root under the heading File System

under the System Tab. In the following example, the available space is 3.1GB.

Figure D-45: Verification of Available File System Space

Note: The Remote Accounts link is not available on the Settings Tab until the SSSD package is

installed. Select an option from the Authentication Template drop-down menu to

activate the SSSD service.

OrionLXm

D-48

Figure D-46: Remote Accounts

OrionLXm

D-49

Figure D-47: Remote Accounts

OrionLXm

D-50

In above figure, the sample sssd.conf and krb5.conf files are shown. The sample files must be

downloaded to the PC as .zip files by clicking the sysfiles.zip links in Figure D-46. The correct

parameters for each setting must be provided by the person handling the LDAP or Active Directory in the

corporate IT department and entered in sssd.conf and krb5.conf in the sysfiles.zip below.

Then the sysfiles.zip file must be uploaded to the Orion again as described in Figure D-33 on the

Files Tab. Once the file has been uploaded correctly, the new values in the sssd.conf and

krb5.conf files are displayed on the screen shown in Figure D-47. Note that the directory structure of

the downloaded .zip must remain unchanged.

Figure D-48: sysfiles.zip

OrionLXm

D-51

4. Firewall The firewall is an important cyber-security tool. The firewall is a first defense step to keep unwanted traffic from entering the OrionLXm and its applications. The firewall is only one component which must be combined with secure authentication and encryption methods as well as other security procedures in order to secure the network and the devices connected to it. The firewall configuration involves establishing a list of rules based on IP address and port numbers.

Rules can be set for Input traffic, Output traffic, and Forward traffic (for routing). Generally, a firewall

is set up to drop all incoming packets. Exceptions are defined to allow specific applications from specific machines to communicate with the OrionLXm and its applications. Adding a comment to each rule is recommended so settings can easily be identified and modified at a later date.

Figure D-49: Firewall Settings

The OrionLXm is shipped with the firewall disabled. The default setting is set to drop both input packets

and output packets. When configuring the firewall, the Input rules, the Output rules, and the Forward

rules must be modified. The tighter the rules, the safer the firewall. It is recommended to temporarily set the output default to accept packets while setting up the input rules to keep from having too many changes at once. Once the input rules function properly, change the default for the output back to drop, and then add the output rules. The order in which rules are executed is important. If the firewall is configured to accept traffic from 26.45.123.54 and the next rule drops all incoming packets, it is much different than dropping all incoming packets and then accepting packets from 26.45.123.54. To set up the firewall, rules must be added by clicking the Add Rule button (Figure D-49) for each

rule. After clicking the Add Rule button, click the Edit button. Once the Edit button is

OrionLXm

D-52

clicked, the following Filter Options webpage will be displayed. To rearrange rules, drag and drop

the rules into the desired order. After all rules have been configured, the Enabled checkbox must be checked before clicking Save .

The web browser will automatically refresh. If the browser does not refresh within one minute, the OrionLXm will turn off the firewall to enable the user to modify the firewall rules. Although every effort has been made to allow access back into the OrionLXm, it is possible to create firewall rules that lock out the user during setup. In this case, the serial interfaces (Ports A1 or A2) must be used to disable the firewall. As a general practice, firewall settings should only be configured locally so that the firewall settings can be modified using the serial interfaces. If the firewall settings are accepted, the OrionLXm will set the Firewall LED on the front panel to indicate protection. All rules that are not specified or needed should be left empty.

Figure D-50: Firewall Filter Options

OrionLXm

D-53

Function Description

Source

Interface The Interface setting specifies the Ethernet interface(s) to which this rule applies.

The available options are any (all interfaces), eth0, eth1, lo (loopback), and/or

tun0 (VPN tunnel).

The first list box allows choosing whether the selected interface is or is not

included in this rule.

Address Defines the IP source address of the incoming packet that is or is not included

in this rule.

Port Defines the source port number that is or is not included in this rule. A list of

preset port numbers is provided for convenience. Other port numbers can be manually entered. Presets include:

FTP, SSH/SFTP, Telnet, HTTP, HTTPS, DNP, Modbus, NTP, OpenVPN, Radius,

Radius Account, PostgreSQL, LDAP, and Secure LDAP.

Destination

Address Defines the IP destination address of the incoming packet that is or is not

included in this rule.

Port Defines the destination port number that is or is not included in this rule. A list

of preset port numbers is provided for convenience. Other port numbers can be manually entered. Presets include:

FTP, SSH/SFTP, Telnet, HTTP, HTTPS, DNP, Modbus, NTP, OpenVPN, Radius,

Radius Account, PostgreSQL, LDAP, and Secure LDAP.

Common

Protocol The Protocol setting specifies the IP protocol (TCP or UDP) that is or is not

included.

Default: TCP and UDP

State The OrionLXm remembers the State of the connection. This setting defines the

actions based on the current state of the connection. Stateful packet inspection is important to prevent exploitation of a device. Server (or slave) protocols will utilize

a state setting, such as Established to keep a program from accepting a

connection that met all other firewall rules. The available settings are:

New A new connection is being created.

Established A current connection is established.

Related New connections created from previous connections.

Invalid Not new, established, or related.

OrionLXm

D-54

Function Description

Action and Additional Options

Action Action to take if the packet matches the rule.

NONE No action is taken.

DROP Drop the packet and do not send a reject message.

ACCEPT Accept the packet.

REJECT Drop the packet and send an ICMP error message back to sender.

LOG Accept packets and log packet information.

Default: NONE

Additional

Options

This is a command line option that requires advanced knowledge of firewalls. If needed, this option will require assistance from NovaTech.

Comment Allows users to add a comment for the purpose of the rule.

Table D-15: Firewall Settings

OrionLXm

D-55

5. OpenVPN OpenVPN allows configuration of an encrypted tunnel for data exchange between the OrionLXm and a client or server. Protocols that do not use encryption, such as DNP3 and Modbus, have a secure SSL tunnel for exchanging information when using OpenVPN. OpenVPN is an open source VPN package that can be installed on Windows or Linux operating systems. This program can be downloaded free of charge at http://openvpn.net/.

Figure D-51: OpenVPN Settings

OrionLXm

D-56

Common OpenVPN settings are used for both client and server modes.

Field Description

Start On Boot For testing, it may be desirable to enable the VPN from the command prompt. Once the VPN is set up properly, this box should be checked. This setting applies to Client and Server.

Default: unchecked

Mode Configures the OrionLXm VPN mode; Client or Server.

Default: Client

Protocol Configures the protocol used over the VPN; UDP or TCP.

Default: UDP

Port Defines the port number. 1194 is the registered OpenVPN port number.

Default: 1194

Cipher Defines the cipher algorithm used to cipher packets. Choices are: AES 128,

Blowfish, Triple-DES.

Default: AES 128

Enable

Compression

Compresses data over the VPN tunnel.

Default: unchecked

CA Defines the Certificate Authority file (.pem). This list is populated from the CA files entered in the Remote Accounts page.

Default: default

Key Defines the Key file (.pem). This list is populated from the Key files entered in the Key Management page.

Default: default

Table D-16: Common OpenVPN Settings

Client OpenVPN settings are used when the OrionLXm is initiating a VPN tunnel with a host.

Field Description

Host IP address of the host.

Table D-17: OpenVPN Client Settings

OrionLXm

D-57

Server OpenVPN settings are used when a device is initiating a VPN tunnel with the OrionLXm.

Field Description

VPN Network Defines the IP Address this server will occupy. IP address will be assigned to clients based on this address.

Default: 10.8.0.0

VPN Netmask Defines the netmask for the VPN interface.

Default: 255.255.255.0

Redirect Gateway Automatically routes all IP traffic over this VPN.

Default: unchecked

Allow Client to

Client

Allows client-to-client connections.

Default: unchecked

Max Clients Defines the total concurrent clients that can tunnel to this OrionLXm.

Default: 100

Table D-18: OpenVPN Server Settings

Clicking Save changes saves any entered settings.

OrionLXm

D-58

6. Key Management The Key Management page allows the creation of new keys, the uploading of them, and the associating of SSL keys with system features. The OrionLXm ships with a default key that is used for SSH and HTTPS. NovaTech does not include a key file issued by a Certificate Authority (CA) such as VeriSign, because the OrionLXm leaves NovaTech’s control when shipped. The OrionLXm’s self-signed keys cause most browsers to generate a warning message. The end user can obtain a signed key from a trusted CA, upload it by clicking Browse and Upload ,

and associate SSH and HTTPS with that key. Clicking Save saves any entered settings.

Figure D-52: Key Management Settings

OrionLXm

D-59

Field Description

Keys The Keys section shows the list of all SSL keys in the OrionLXm. The key

values can be viewed by clicking the respective link under the Key Name

heading. The following figure shows the parameters associated with a key.

In order to create a new key, click Create a new key, which requires the

parameters shown in Figure D-54. See also chapter Create Key.

System Keys

Allows users to select a specific key for SSH and HTTPS (Apache). The list box will include all key files displayed in the keys section.

Key file upload Allows uploading of key files to the OrionLXm.

Table D-19: Key Management Settings

Figure D-53: Default Key Values

OrionLXm

D-60

Create Key

After selecting the Create a new key link, a prompt allows the entering of the parameters of the

Distinguished Name. All fields must be entered. Once the parameters have been entered, click

Create Key to create the key. The new key will be displayed in the key list (see Figure D-52).

Figure D-54: Create New Key

OrionLXm

D-61

7. System Log If the system log or syslog function is set up, the OrionLXm sends the system messages specified below to the specified computer for logging and analyzing. This function is used for system management and security auditing.

Figure D-55: System Log Setup

OrionLXm

D-62

Field Description

Enable Remote

Logging

This box must be checked to enable the syslog functionality.

Host Address IP address of the syslog host computer.

Destination Port Port number of the host computer which is used for syslogging.

Default: 514

Connection Type Connection type with syslog host computer.

Default: TCP

Filter Options Check all types of events for which messages shall be sent to the syslog host for logging.

Default: alert, critical, emergency, error.

Table D-20: System Log Setup

OrionLXm

D-63

8. Networking The Networking page configures the installed Ethernet ports as well as common settings such as hostname, DNS Server, and routing activation. Once the Save changes button is clicked, these

settings immediately take effect. If the IP address of the OrionLXm has been changed, the new address of the OrionLXm must be entered in the web browser for continued access to the OrionLXm’s webpages.

The OrionLXm has two Ethernet ports eth0 and eth1 of which only eth0 is shown in the following

figure. The setup of both ports is identical.

Figure D-56: Networking Settings

OrionLXm

D-64

Common

The Common settings affect all network adapters as follows.

Function Description

Hostname Optional name that identifies the OrionLXm on a network. The DNS server must be aware of this hostname and supply connecting devices with the IP address. This name is also displayed on the OrionLXm title bar for device recognition.

Default: orionlx

DNS Server 1

DNS Server 2

The Domain Name System (DNS) Server converts a hostname to an IP address. The OrionLXm supports two DNS servers. If no DNS is required for communications to and from the OrionLXm, it is recommended to leave the DNS server fields empty for faster ssh connection times.

Enable Routing The Enable Routing setting allows the OrionLXm to act as a router. When routing, the OrionLXm becomes the gateway between two networks. After selecting this option, the user must configure the OrionLXm IP address as the gateway addresses of the two networks that the OrionLXm is routing. The default gateway addresses of the OrionLXm Ethernet ports should be left blank.

Table D-21: Common Network Settings

Note: NovaTech recommends using the Firewall Settings when the Enable Routing setting

is selected.

OrionLXm

D-65

eth0 and eth1 For all network ports, the same set of parameters must be configured. All ports operate independently of each other. In most environments, the IT department or networking engineering personnel must be consulted to obtain specific addresses for the Orion’s network configuration. Note: Each port (eth0, eth1) must belong to a different network and set up with

corresponding IP addresses. If network ports are set up with IP addresses belonging to the same IP network, IP communication errors may occur.

Example 1: 192.168.x.x and 172.16.x.x are different networks. Example 2: With subnet mask 255.255.255.128, the ranges 192.168.1.1 - 192.168.1.127 and

192.168.1.129 - 192.168.1.255 are different networks.

Function Description

Configuration

Use DHCP

Dynamic Host Configuration Protocol (DHCP) allows the OrionLXm to obtain its IP address from a DHCP server. Depending on the requirements and network setup, the IP addresses can be assigned automatically through a DHCP server on the network. However, unless the DHCP server is set up to assign a specific address to the OrionLXm, this will result in varying addresses assigned by the DHCP server. In most network architectures, static IP addresses will be the preferred setup.

Default: Checked (DHCP enabled)

IP Address OrionLXm static IP address for eth0 or eth1.

Example: 172.16.123.12

Subnet Mask The Subnet Mask is used to divide networks. Devices that communicate over a network must have the same subnet mask. The corporate IT department or networking engineering personnel normally provide the specific settings.

Example: 255.255.0.0

Gateway The Gateway setting allows the OrionLXm to communicate with devices that are not on the network. Commonly, the gateway is the IP address of the router. NovaTech recommends using a gateway setting for one network interface only.

Example: 172.16.0.1

Media Settings Defines the speed at which the OrionLXm communicates over the network. auto

negotiate allows the OrionLXm to connect at the optimal available speed.

Selecting 10/half or 100/half restricts this port to the selected speed and half

duplex mode.

Default: auto negotiate

Table D-22: Network Settings for eth0 and eth1

OrionLXm

D-66

Advanced Networking

Clicking the Advanced Networking link opens a new window where static routes can be configured.

Click Add to open the following window (Figure D-57) and to configure new static routes.

Figure D-57: Static Route Configuration

Function Description

Broadcast IP

Address

Enter the IP address of the final destination.

Subnet Mask Enter the subnet mask of the final destination.

Gateway Enter the gateway IP address which must be on the same LAN segment as the OrionLXm.

Interface Select the OrionLXm Ethernet port for which this static route applies.

Table D-23: Static Route Parameters

OrionLXm

D-67

9. Modem The OrionLX offers modem support on any of the up to 8 serial ports. The port must be set up as an RS-232 port as described in chapter Serial. Refer to the external modem’s user manual for any information needed for setting up this modem, such as initialization strings. The entered settings become effective after clicking Save changes .

Figure D-58: Modem Settings

OrionLXm

D-68

Field Description

Enabled In order to enable a modem port, the Enabled checkbox must be checked.

Default: Not enabled

Comm Port Select any port that is set up as an RS-232 port (see chapter Serial).

Direct (not

dial-up)

This option must be checked only if the port is used for a leased line modem.

PPP IP Address This is the IP address that the PPP server on the OrionLXm will give to the PC that is dialing in to the OrionLXm on that particular TTY port. This must be in the

same range as the PPP Server IP Address, and cannot match the ranges of

any other network interfaces.

PPP Server IP

Address

This is the IP address that has been assigned to the PPP server that is running on the OrionLX (not the IP address of the initiating OrionLX). All PPP Server IP Addresses should be the same on every TTY port. This must be in the same

range as the PPP IP Address, and cannot match the ranges of any other

network interfaces.

Port Speed Select the speed between the selected modem port and the modem from the drop down box.

Use DTR to

reset modem

When checked, the OrionLX uses the DTR line to reset the modem.

Hold the DTR

line low

Default (milliseconds): 500

Init Chat Enter the init chat string as per the modem manufacturer manual.

Force Init

Chat

Enter the force init chat string as per the modem manufacturer manual.

Post Init Chat Enter the post init chat string as per the modem manufacturer manual.

Modem Check

Time

The OrionLXm checks with a simple AT…OK sequence to determine if the modem

is still alive and responding as specified. If not, the OrionLXm will perform a full modem reset.

Number of

Rings

Specifies the number of rings after which the OrionLXm instructs the modem to answer when being called from the outside.

Answer Chat Enter the answer chat string as per the modem manufacturer manual.

Answer Chat

Timeout

During the answer-chat, each expected string must arrive in the time specified here. This time should be at least 5 seconds longer than the time set with the |ATS7=...| modem setup command.

Autobauding Some modems switch their DTE line speed to the communication line speed after connecting, e.g., after sending CONNECT 2400, the modem switches to 2400 bps. Newer modems usually have a switch to "lock" a DTE baud rate, which is strongly recommended. If the connected modem switches the speed, checking

Autobauding will set up the OrionLXm modem driver accordingly.

OrionLXm

D-69

Field Description

Ignore Carrier If the connected modem does not assert the DCD (carrier detect) line, or the serial port, cable, or serial driver is broken, it is possible that the connection will “lock” after a successful CONNECT. In this case, there are no immediate error messages, but nothing is sent to the port anymore. Depending on the operating system used, this can happen before printing the ‘/etc/issue' file or after printing the ‘password:' prompt. To work around this, carrier detection can be ignored.

WARNING: When using this option, the system will not be able to detect when a caller just hangs up instead of cleanly logging out. This may result in hanging modems, etc.

Login Time This specifies the maximum time the user can take to log in. If no login has occurred after that time, the OrionLXm modem driver will hang up.

Table D-24: Modem Settings

OrionLXm

D-70

10. System The system settings configure system time parameters including IRIG-B Input, IRIG-B Output, and NTP settings.

Figure D-59: System Settings

OrionLXm

D-71

Field Description

Time Zone Defines the OrionLXm time zone. The OrionLXm will use this time zone setting for user interface time values, except for log files. Protocols that use time provide an offset for multi time zone systems. If daylight savings time is undesirable, use the Greenwich Mean Time (GMT) or Universal Time Coordinated (UTC) offset zones. Click Save to save the setting.

Example: Etc/GMT-6

IRIG B Input - Timezone Defines how the OrionLXm will interpret the incoming IRIG-B

signal. If UTC is selected, the OrionLXm will apply the time zone

setting to the incoming time before using it. If Local is selected,

the OrionLXm will use the exact time received.

Default: UTC

IRIG B Input - Signal

Type

Defines what type of IRIG-B signal the OrionLXm will receive.

Unmodulated is an AC signal and Modulated is a DC signal.

Default: Unmodulated

IRIG B Output – Output

Mode

Defines whether the IRIG-B output signal will be Generated by

the Orion or whether the Orion should Use input signal.

Default: Generated by the Orion

IRIG B Output - Timezone Defines how the OrionLXm will send the outgoing IRIG-B signal. If

UTC is selected, the OrionLXm will apply the time zone setting to

the signal before sending. If Local is selected, the OrionLXm will

send the exact time of the OrionLXm. Click Save to save the

setting.

Default: Local

NTP Time Sources Network Time Protocol (NTP) is a very accurate network protocol for setting the OrionLXm time. The OrionLXm can receive both IRIG-B and NTP messages. Commonly, a hostname or IP address is entered. Several hostnames are provided, but usually the NTP Server is a GPS clock or server on the network. Hosts can be added by typing the hostname or IP address and clicking Add .

After saving, the new entry will be displayed in the list box. The Delete button allows deletion of individual hosts.

Table D-25: System Settings

OrionLXm

D-72

11. Serial The ports on the S4 communication card can be set up to operate as RS-232, RS-485 2-wire, and RS-485/422 4-wire ports.

Figure D-60: Serial Ports Setup

The following port settings are available.

Port Type Description

RS-232 The port operates as an RS-232 port. The pinout is described in Table B-8.

RS-485 2-wire The port operates as an RS-485 half duplex port using two wires. The pinout is described in Table B-9.

RS-485/422 4-wire The port operates as an RS-485/422 full duplex port using four wires. The pinout is described in Table B-10.

Table D-26: Serial Port Setup

OrionLXm

D-73

12. WebUI On the WebUI page, the following settings related to the OrionLXm’s webpages are entered. All settings become effective by clicking the Save button at the bottom of the page.

Figure D-61: WebUI Setup

OrionLXm

D-74

Login Message By default, no custom text is shown on the OrionLXm’s initial login page. Custom text (Example: “Welcome to Desert Road Substation!”) can be entered as shown above (Figure D-61) which is then displayed as shown in Figure D-62.

Figure D-62: Custom Login Message

HMI In the HMI section of the setup page, the following settings are available.

Field Description

Use large text in the header

bar and link bar on HMI

If this box is unchecked, the header bar is displayed as shown in Figure D-63. If the box is checked, the header bar is displayed as shown in Figure D-64.

Display tagging button and

information in HMI control

dialog

Tags can be set up as described in chapter Tagging. When executing control operations in the HMI dialog, the respective tags can be displayed as part of the confirmation screens. If this is desired, this box must be checked (Figure D-65). Otherwise, this box must be unchecked (Figure D-66).

Table D-27: HMI Setup Parameters

Figure D-63: Small Text in Header and Link Bar

Figure D-64: Large Text in Header and Link Bar

OrionLXm

D-75

Figure D-65: Control Dialog with Tag Information

Figure D-66: Control Dialog without Tag Information

Web Files Immediate links to user-defined .svg files can be displayed on the Home page (Figure D-68). Each file that requires a link on the home page must be checked as shown below (Figure D-67).

Figure D-67: Set Link to User-defined .svg File

OrionLXm

D-76

Figure D-68: Link to User-defined .svg File

Link Bar Above the blue OrionLXm banner, links can be set up for immediate access to the linked pages (Figure

D-69). As shown in Figure D-70, the link names must be entered in the Name column, and the OrionLXm

directory of the respective .svg file must be entered in the Address column.

Figure D-69: Link Bar Example

Figure D-70: Link Bar Setup

OrionLXm

D-77

Sections Each section has three parameters that can be customized; access settings, hide header, and show link bar. If no rules or parameters are defined for a section, the default settings for each parameter will be used. After all of the parameters are set and the rules have been added for the sections, click the Save

button located on the bottom of the webpage. Note that the HMI section is available only if the XML Slave protocol is configured.

Figure D-71: Webpage Access Security and Display Options

OrionLXm

D-78

Control Box Description

Dropdown box For each section (Home, Files, System, etc.) of the OrionLXm, access rules can be added by clicking the Add rule button. For each section, multiple

rules can be specified. Each rule determines whether accessing that section of

the OrionLXm from the specified IP address or CIDR block, no_login,

login, or unlock is required. Access to that section can also be disabled

altogether by selecting deny for the specified IP address or CIDR block (see

the dropdown box in Figure D-71). To remove a rule, click the Delete

button associated with that rule.

Hide header If this box is checked, the OrionLXm webpage header which consists of the blue banner and the tabs (Figure D-72) will not be shown when the respective section page is displayed. The header will also be hidden from any pages linked from the main section page.

Show link bar If this box is checked, the link bar will be shown on the respective section page (Figure D-72). The link bar will also be shown on all pages linked from the main section page.

Table D-28: Section Parameters

Figure D-72: Link Bar and Header Settings

After all changes have been completed, click the Save button.

Show Link Bar

Hide Header

OrionLXm

D-79

13. Alarms For alarms, the visual and audio notifications, colors, and archive columns can be specified. Refer to the Alarm/Archive/Retentive Module for OrionLX Software Manual for setting up data points for alarming.

OrionLXm

D-80

Figure D-73: Alarm Archive Settings

OrionLXm

D-81

Notifications For unacknowledged alarms, the following options can be specified. Refer to Alarms Tab for acknowledging alarms.

Control Box Description

Show warning

banner

If this box is checked, a warning banner will be displayed if there are any unacknowledged alarms.

Show most recent

alarm in banner

If this box is checked, the most recent alarm will be displayed if there are any unacknowledged alarms.

Play alarm sound

every x seconds

If this box is checked, the specified alarm sound (alarm1, alarm2, alarm3,

alarm4, or alarm5) will be played at the specified interval.

Table D-29: Section Parameters

Colors The colors for normal values, alarm values, and acknowledged alarms can be defined using standard colors or custom colors. The colors can be entered either by text name as shown in Figure D-73 or by the respective six-digit hex code. For example, #FF0000 represents red.

Alarm Archive

The columns DateTime, Device DateTime, Pointname, and Alias can be included or excluded

from the Alarm Archive by setting the respective checkboxes accordingly.

OrionLXm

D-82

14. Database The following database operations work in combination with NCD configuration for archiving, retentive data, and/or alarming (see Alarm/Archive/Retentive Module for OrionLX Manual).

Note that for all database operations (such as Reset database), the database must be enabled. The

database is enabled when the link Disable database is displayed as shown below (Figure D-74).

Figure D-74: Database Settings

Function Description

Enable Database

Disable Database

Activate or deactivate the database.

Default: the database is disabled.

Reset Database Deletes and recreates all database tables. All data in the database will be lost. Resetting the database will take approximately 5-10 minutes to complete. The database must be enabled for this operation to be available.

Analyze Database Collects statistics about the contents of tables in the database. The query planner uses these statistics to help determine the most efficient execution plans for queries. Using this feature for large databases optimizes the query response time. The database must be enabled for this operation to be available.

Allow remote

database access

When this box is checked, the database server will listen on TCP/IP port 5432 (on all interfaces) for connections and provide access. Click Save

to make the setting permanent.

OrionLXm

D-83

Function Description

Add When connecting remotely to port 5432 using a client such as pgAdmin, or a driver such as psqlODBC, a username and password must be specified to connect. This option permits access for the specified database users. When clicking this button, the following window is displayed (Figure D-75). The respective user name and password must be entered. The

checkboxes for the desired access (archive, retentive, tagging)

must be set as well.

Delete Clicking on this link to the right of a database user name removes that user’s account.

Table D-30: Database Settings

Figure D-75: Add Database User

OrionLXm

D-84

15. Tagging For tagging of equipment, the OrionLXm provides the following three standard tags.

Tag Name Description Permis-sion

Disable Output Value

Display Group

Do Not Operate Place on devices to inhibit operation. 1 0 1

Information Place on devices to give information. 1 None 2

Out of Service Place on devices that are out of service.

1 Both 3

Table D-31: Standard Tags

The meaning of Permission, Disable Output Value, and Display Group is explained in Table

D-32.

Additional tags can be added by clicking Add tag type on the following page (Figure D-76). The page

shown in Figure D-77 will be displayed.

Figure D-76: Tag List

OrionLXm

D-85

Figure D-77: Add New Tag

Field Description

Name Name of the new tag.

Description Description of the purpose of the new tag.

Disable control

value This parameter sets which output values will be disabled when the tag is applied to the individual control. The options available in the drop down menu are:

Parameter Description

none This parameter would be used for Information only type tags. Neither control will be disabled with this selection.

both This is the most restrictive parameter. The control will not be able to be turned on or off.

0 An output value of 0 will be disabled if this option is selected. Depending on how the operation of the control is defined, this parameter could turn the control on or off.

1 An output value of 1 will be disabled if this option is selected. Depending on how the operation of the control is defined, this parameter could turn the control on or off.

Permission There are five permission groups set up in Account Management, called

tagging1, tagging2, etc. The operator who is setting the tag must

belong to the specified group.

OrionLXm

D-86

Field Description

Display Group The display group can be 1 through 16. This option corresponds to the

Tagging Visibility Group that is set on the Orion HMI.

Additional Fields The additional fields are optional. If left empty, no additional fields will be displayed (Figure D-79). If additional fields are needed, they can be added by clicking + and filling in the desired text labels. In the above

example, two fields called Tester Name and Tester Phone Number

have been added. When the tag is used, those additional fields are displayed as shown in Figure D-80.

Table D-32: Tag Fields

For taggable equipment, the Tagging button must be inserted in the .svg graphics next to the

equipment (Figure D-78). Clicking the button opens the tag window shown in Figure D-79.

Figure D-78: Tagging Button in Graphics

All existing tags for the associated data point are displayed below the data point’s name on the left hand side. Existing tags can be removed by clicking the respective Remove tag button.

For adding a new tag, select the desired tag type from the dropdown box, fill out the Comment field and

other fields if available (see example in Figure D-80). Then click Apply Tag for the tag to become

effective.

OrionLXm

D-87

Figure D-79: Setting a Standard Tag

Figure D-80: Setting a Custom Tag

OrionLXm

D-88

16. Cascading Slave When several OrionLXm's are cascaded, the NCD configurations for the slave OrionLXm are generated on the following screen of the master OrionLXm by clicking Save and Make Active . The master

OrionLXm in turn, has been set up accordingly in NCD (see Figure C-13). A complete description of setting up a cascaded OrionLXm is available in the Cascading for OrionLX Manual.

Figure D-81: Cascading Slave

OrionLXm

D-89

17. Services The Services page enables/disables unsecure protocols that are disabled by default. Each of these protocols has a secure equivalent that is enabled in the OrionLXm by default. SSH replaces Telnet, SFTP replaces FTP, and HTTPS replaces HTTP. After clicking the Save changes button, any

changes will immediately take effect.

Figure D-82: Services Settings

OrionLXm

D-90

18. Scheduler The Scheduler page allows the scheduling of various tasks to run at user-specified intervals. Multiple

tasks may be run concurrently. Only users who belong to the cronconfig group (see Users) can

access this function.

Figure D-83: Scheduler – Task List

Field Description

Restart Cron Daemon Click this button after adding new tasks, or editing or deleting existing tasks.

Add CSV Task Add a CSV task as described in Scheduling Tasks and Add CSV Task.

Add FileMover Task Add a FileMover task as described in Scheduling Tasks and Add FileMover Task.

remove When clicking this link next to a task, the task will be removed and will no longer be executed.

Task (such as

CSV File Generator)

When clicking the task’s link, the task is opened for editing.

Table D-33: Scheduler – Task List

OrionLXm

D-91

The hwclock task is the hardware clock task that keeps the time synchronized. This task should not be

removed and is not available for editing.

Scheduling Tasks The scheduling procedures for CSV tasks and FileMover tasks are identical as shown in the following figure. The task-specific setups are outlined in the respective chapters Add CSV Task and Add FileMover Task.

Figure D-84: Task Scheduling

OrionLXm

D-92

Field Description

Task Information

Task Description Assign a task name.

Schedule Date/Time

Designates how often the task should run. There are options for Month, Day

of Month, Day of Week, Hours, and Minutes. If all options are selected,

the task will run every minute of every hour of every week and every day of the month and every month. The intervals can be set in detail using the following controls.

If invalid parameters are selected, a notification message will appear when saving the settings.

Month Select individual months or all months in which the task is to be run.

Default: all months

Day of Month Select specific days or all days of the month for the task to run.

Default: all days of the month

Day of Week Select specific days or all days of the week for the task to run.

Default: all days of the week

Hours Select the hour of the day the task should run in military time.

Default: all hours

Minutes Select the minutes past the hour for the task to run.

Default: every minute

Repeat Value Select how often the task should be repeated, relative to month, day of month, day of week, hours, and/or minutes.

Default: No Repeat.

Table D-34: Task Scheduling

The following two examples show two tasks. The first task (Figure D-85) is run daily at 00:05, and the second task (Figure D-86) is run every three hours. Figure D-87 shows the task list with those two tasks.

OrionLXm

D-93

Figure D-85: Task Example – Daily at 00:05

Figure D-86: Task Example – Every Three Hours

Figure D-87: Task List Example

OrionLXm

D-94

Add CSV Task

With the CSV task, portions of the Archive or Alarm database can be emailed. The CSV task

parameters are set up on the following page.

Figure D-88: CSV Task Parameters

Field Description

Database Designates whether the CSV file will contain data from the Archive or

from the Alarm database.

Maximum file size Minimum file size is 10 Kbytes, and maximum file size is 500000 Kbytes.

Default: 20000

Maximum files This is the number of files that will be saved before the files begin to be deleted in order to make room for new files.

Default: 60

Use device

date/time

Uses the date and time information gathered from the specific device rather than using the OrionLXm information.

Email CSV

Email to group

To utilize the emailing function, check the Email CSV box which will

enable the Email to group field. In this field, enter the name of the

group that data should be emailed to. The email groups are configured in NCD. For instruction on how to configure an email group in NCD, see the Email for OrionLX Software Manual.

Name describing CSV

file

The content of this field will be used as the “Subject” of the email.

Table D-35: CSV Task Parameters

Any changes on this page must be saved by clicking the Save button.

OrionLXm

D-95

Add FileMover Task With the FileMover task, files in the OrionLXm can be transferred to a host computer using FTP or SFTP. The FileMover task parameters are set up on the following page. Note: The FileMover software package must be installed on the OrionLXm for this option to be

available.

Figure D-89: FileMover Task Parameters

Field Description

ftp sftp Select the protocol for the file transfer.

Path Path in the OrionLXm file system of the file to be transferred.

Private Key Path to the private key file used for encrypting the transferred file. This is only needed when using SFTP.

IP Address IP address of the host computer to which the file is transferred.

Port Port of the host computer used for file transfer.

Path Path in the host computer file system where the transferred file is stored.

Username Username for login at the host computer.

Password Password for login at the host computer.

Delete on success If this box is checked, the specified file will be deleted in the OrionLXm file system upon successful transfer to the host computer.

Table D-36: FileMover Task Parameters

Any changes on this page must be saved by clicking the Save button.

OrionLXm

E-1

E. OrionLXm MMI

OrionLXm

E-2

I. Introduction The OrionLXm provides a built-in MMI for viewing data values, port communications, device statistics, system events, and system/version information. It also allows configuration file, firmware file, and log file transfers via Z-Modem (bi-directional), as well as passthrough to connected relays and meters. This allows use of the respective manufacturer’s programming software to configure the relays and meters, retrieve event information, etc. The OrionLXm’s dedicated MMI port is port A via USB. Additional serial ports on the OrionLXm can be set up as MMI ports if needed. For example, if viewing in different locations is required, or if multiple aspects of the MMI are to be viewed at the same time. In addition, the same MMI with the same functionality (aside from file transfer) is available for access by way of SSH or PuTTY, and the OrionLXm’s Ethernet port(s). Again, multiple MMI windows can run simultaneously. Using the MMI requires NCD (NovaTech Configuration Director) software or a standard terminal or telnet software (for example, HyperTerminal, CRT, etc.) in order to make commissioning, monitoring, and troubleshooting as easy as possible.

Connection Requirements In order to connect to the OrionLXm, the following hardware and software is required.

Serial Connection Ethernet Connection

Hardware - PC with available USB port and A/B USB cable (included with OrionLXm)

- Ethernet cable

- PC with Ethernet connection

Software - NCD or

- any terminal software

(HyperTerminal, CRT, etc.)

- NCD or

- any software which allows Telnet connection (CRT, PuTTY, etc.)

Table E-1: Serial/Ethernet Cables and Software

OrionLXm

E-3

II. Connecting to the Orion MMI

1. OrionLXm Port A The configuration and MMI port of the OrionLXm is port A on the front panel. Port A is automatically set up to run the MMI, and does not require any configuration. The communication parameters are 115200 Baud, No Parity, 8 Data Bits, and 1 Stop Bit (115200N81). The terminal mode is ANSI. For port A, the parameters cannot be changed, meaning the above parameters are fixed, and the port cannot be used for a protocol. Connecting to port A requires a USB A/B cable such as the one that is included with a new OrionLXm. If custom cables are used, the OrionLXm requires only three lines to be connected; Transmit, Receive, and Ground. Loading a NCD configuration file into the OrionLXm enables the OrionLXm to operate the configured protocols on all other ports, as well as operating additional MMI ports, user-defined logic, etc.

2. Connecting to the OrionLXm with NCD The chapter Communications Menu describes how to set up a serial connection in NCD and how to connect to an OrionLXm. After connecting to the OrionLXm MMI, login to the OrionLXm with the appropriate user name and password.

3. Unlocking a User Account If a user is locked out due to too many failed login attempts, the OrionLXm MMI can be used to view the failed login attempts and unlock the user account. This must be done from an administrative or root user

account. In the terminal window, type the command faillog. Then, follow the prompts in order to reset

the locked out user account. See the OrionLX Applications Manual for a list of other shell commands that can be used in the terminal window.

OrionLXm

E-4

III. MMI Menus

The OrionLXm displays the following Main Menu on Port A.

All menu items in Figure E-1 are hyperlinks to the respective sections.

OrionLX

Automation Platform

Version 1.39.8 Date: 05/27/2009

Copyright 2000-2009 NovaTech LLC

SalesDemo.ncd

Main Menu

--------------------------------------------

1. File Menu

2. Data Menu

3. View Communications

4. Device Statistics

5. System Menu

6. Disconnect

7. Session Timeouts

8. Network Menu

Figure E-1: OrionLXm MMI Main Menu

OrionLXm

E-5

1. File Menu The File Menu allows uploading, downloading, activation, and deletion of configuration files from the OrionLXm. File transfers between the PC and the OrionLXm use the Z-Modem file transfer protocol. All menu items in Figure E-2 are hyperlinks to the respective sections.

OrionLX

Automation Platform

Version 1.39.8 Date: 05/27/2009

Copyright 2000-2009 NovaTech LLC

File Menu

--------------------------------------------

1. File Transfer (PC -> ORION)

2. File Transfer (ORION -> PC)

3. Make Config File Active

4. Delete a File

5. View a File

6. Install Downloaded Packages

Figure E-2: OrionLXm File Menu

File Transfer (PC -> ORION) This option allows the selection of and downloading of a file, such as .ncd or .bas, to the Orion. When using NCD, the following window will open in order to select the file on the PC.

OrionLXm

E-6

Figure E-3: File Transfer to OrionLXm Using NCD

When using terminal software, the following window (Figure E-4) will open. At this point, the file transfer from the PC to the OrionLXm must be initiated using the terminal software.

Begin ZModem transfer now...

Press Control-X five times consecutively to abort

Figure E-4: File Transfer to OrionLXm Using Terminal Software

OrionLXm

E-7

File Type/Extension File Use Description

.ncd OrionLXm Configuration File

Configures the OrionLXm’s ports with protocols and points.

.bas OrionLXm Logic File Basic file containing logic executed by the OrionLXm.

.dll, .exe OrionLXm Driver File Only downloaded when a new driver becomes available. Oftentimes this update is performed by the OrionLXm Updater, a stand-alone program which brings all drivers in an OrionLXm up to the most current level.

orionlx.ntk OrionLXm Key File The key file specifies what protocol drivers a specific OrionLXm is authorized to run. Even if a specific driver is downloaded into the OrionLXm, it will not execute without the proper authorization.

Table E-2: OrionLXm File Types

File Transfer (ORION -> PC) This feature uploads a specific file from the Orion to the PC. The typical reason for this would be to review a configuration that has been downloaded from another PC that is not available on the presently connected PC. First, specify the file to be uploaded by its number on the following screen. Note that files can be uploaded only one at a time.

If more than 20 files are stored in flash memory, the screen ends with ---More---. In this case, hitting

any key will scroll the screen by 20 more lines, or until the end of the file list.

1. orion16.ini

2. central.bas

3. central.ncd

4. southyard.ncd

5. southyard.bas

Please enter the number of the file to send to PC:

Figure E-5: File Transfer OrionLXm to PC

OrionLXm

E-8

After entering a file number, an NCD window (if using NCD) is displayed for specifying the name and location on the hard drive for the file that is to be transferred to the PC. When using terminal software, the following window will open. At this point, the file transfer to the PC from the OrionLXm must be initiated using the terminal software.

Begin ZModem transfer now...

Press Control-X five times consecutively to abort

Figure E-6: File Transfer to PC Using Terminal Software

Make Config File Active An OrionLXm can have several .ncd files (and associated .bas or .lua logic files) stored in its flash memory. However, only one of those files can be active at any given time. This option specifies the configuration file the OrionLXm shall load and operate. The user must verify that the configuration file loaded is actually intended for the specific OrionLXm, and that the OrionLXm has the correct hardware options installed. In the following screen, the configuration file to be loaded is specified by its number. If there is a logic file associated with a configuration file, it will be loaded automatically.

If more than 20 files are stored in flash memory, the screen ends with ---More---. In this case, hitting

any key will scroll the screen by 20 more lines, or until the end of the file list.

1. spv1_31.ncd

2. bricktn2.ncd

3. central.ncd

4. southyard.ncd

5. eastyard.ncd

Please enter the number of the file to make active:

Figure E-7: Configuration File Selection

After the new configuration file has been specified, the Orion must be restarted in order for the

configuration file to be loaded and run (Figure E-8). If Do not restart is chosen, the OrionLXm will

continue to operate with the current configuration file.

OrionLXm

E-9

A Full restart resets all hardware, all software, and all drivers; including the operating system.

However, it can take up to several minutes, depending on the OrionLXm’s configuration.

A Quick restart reloads only the protocol drivers and usually takes under 60 seconds to complete.

In order for the new configuration to take effect the

OrionLX must be restarted. Do you wish to perform a

full restart, quick restart or no restart?

1. Full restart.

2. Quick restart.

3. Do not restart.

Figure E-8: Make Selected Configuration File Active

Delete a File If multiple configuration files are downloaded to the OrionLXm for testing, commissioning, or for use as a lab unit, eventually files will have to be deleted off the flash memory of the OrionLXm. Figure E-9 shows a list of files from which the file to be deleted has to be specified by its number. Files can be deleted only one at a time by entering the number that is listed with the respective file.

If more than 20 files are stored in the flash memory, the screen ends with ---More---. In this case,

hitting any key will scroll the screen by 20 more lines, or until the end of the file list. After a file has been specified, a user prompt requires confirmation of the operation.

1. spv1_31.ncd

2. spv1_31.bas

3. orion16.ini

4. southyard.ncd

5. southyard.bas

Please enter the number of the file to delete:

Figure E-9: Delete File from Flash Memory

OrionLXm

E-10

View a File

View a file allows viewing of a configuration file. First, the file must be selected using its number as

shown in the following screen. If more than 20 files are stored in flash memory, the screen ends with

---More---. In this case, hitting any key will scroll the screen by 20 more lines, or until the end of the

file list.

After entering the file number, the actual file is displayed. The (Cursor Up) and (Cursor Down) keys

allow scrolling through the file. <Esc> returns to the menu in Figure E-2. Entering <G> prompts for a line

number to go to, and then displays that line.

1. spv1_31.ncd

2. spv1_31.bas

3. southyard.ncd

4. southyard.bas

Please enter the number of the file to view:

Figure E-10: Select File for Viewing

After entering the file number, the actual file is displayed. The (Cursor Up) and (Cursor Down) keys

allow scrolling through the file. <Esc> returns to the menu. Entering <G> prompts for a line number to go

to, and then displays that line (Figure E-11).

OrionLXm

E-11

ConfigCreation=7/20/2009 11:58:47

ConfigLastWrite=8/06/2009 9:41:05

RemoteUsername=

RemotePassword=

RemoteAttemptsBeforeLockout=0

RemoteLockoutTime=0

MMITCPPort=23

ForceInputs=1

ForceOutputs=1

[Comments]

[System]

BootDelay=0

EnableRouting=0

LoadTimeout=

[Orion Model]

Model=OrionLXm

NetworkCards=NONE

ModbusPlusCards=NONE

InternalModem=0

Figure E-11: View File

Install Downloaded Packages Update packages can be transferred to the OrionLXm using the MMI option File Transfer (PC -> ORION) (or the webpage option User Files). Once transferred, the following screen allows viewing of the transferred packages, clearing of the installation directory, and installation of the transferred packages. Note: After installing packages, a reboot (System Menu or System Tab) is required for the

installed packages to be executed.

Package Installation Menu

1. List available packages to install.

2. Install all packages in installation directory.

3. Clear package installation directory.

>

Figure E-12: Package Menu

OrionLXm

E-12

2. Data Menu

Option 2 of the main menu is Data Menu. The Data Menu allows real-time viewing of each input/output

point’s value information on a port-by-port basis. With the NCD default configuration, only options 1) and 2) are displayed on the following screen. For the purpose of this manual, an input point is a point that is obtained from a field device and reported to a master, and an output point is a point that is sent from a master to a field device. Since the OrionLXm essentially only passes through points from the front end to the end device, the notion of input point and output point is maintained the same way, whether the point is viewed as part of a master port where the Orion acts as a master to an end device, or as part of a slave port where the Orion acts as a slave to a front end/SCADA master. The following options are available only if the respective options are selected accordingly under option General in NCD.

3. Override Input Values

4. Clear Input Override

5. Send Output Values

Forcing an input/output point means that the Orion will use the value(s) as entered by the user at the MMI of the OrionLXm. These values are then transmitted when communicating to SCADA masters (to which the OrionLXm is a slave) or RTUs/IEDs (to which the OrionLXm is a master). Forced values temporarily replace values from live devices the OrionLXm communicates with. This is useful for testing, or when the OrionLXm is installed and not all other devices or communication links are available yet. All menu items in Figure E-13 are hyperlinks to the respective sections.

OrionLX

Automation Platform

Version 1.39.8 Date: 05/27/2009

Copyright 2000-2009 NovaTech LLC

Data Menu

--------------------------------------------

1. View Input Values

2. View Output Values

3. Override Input Values

4. Clear Input Override

5. Send Output Values

Figure E-13: Data Menu

OrionLXm

E-13

View Input Values After selecting this option, select the port whose point values are to be monitored from the following screen.

OrionLX

Version 1.39.8 Date: 05/27/2009

Copyright 2000-2009 NovaTech LLC

Input Values

--------------------------------------------

1. Port 1 - SEL Master

2. Port B - DDIO Port

3. Port 20 - NTP Kernel

4. Port 21 - Sensor Master

5. Port 24 - XML

6. Port 25 - SER Master

7. Port 26 - AAR Slave

8. Port 124 - Logic

Figure E-14: Select Port for Input Point Monitoring

Each data point in the OrionLXm will typically be displayed on at least two ports; the master port that obtains the point from another device, and the slave port through which another device polls the OrionLXm for the point’s value. A point can also be mapped to more than one slave port if more than one master polls the OrionLXm for that point. The OrionLXm maintains the point’s value in the realtime database as a normalized value, i.e. percentage of full scale. However, the scaled values for the same point will vary, based on the scaling entered for each port. See also NovaTech’s Analog/Accumulator Scaling Technical Note for more details. Once a port is selected, all its values are displayed as follows.

OrionLXm

E-14

Data values for Port 1 - SEL Master (p1)

Name Point Number Value Percent FS

Polls @SEL 501 Dual Relay N/A 390244.000 0.009086

Responses @SEL 501 Dual Relay N/A 390244.000 0.009086

Comm Fail @SEL 501 Dual Relay N/A 0.000 0.000000

Meter IAX @SEL 501 Dual Relay 00040 3.000 0.009156

Meter IBX @SEL 501 Dual Relay 00041 0.000 0.000000

Meter ICX @SEL 501 Dual Relay 00042 9.000 0.027467

PassThru Status @SEL 501 Dual 00998 0.000 0.000000

ESC=Back C=Column Editor S=Sort Editor H=Hex D=Dec O=Oct

Figure E-15: Input Point Monitoring

The (Cursor Up) and (Cursor Down) keys allow scrolling through all the points on the selected port.

<G> allows jumping to a specific page. After pressing <G>, Goto: appears in the lower left hand corner

for entering the specific page number, followed by <Enter>.

<Esc> returns to the screen in Figure E-13.

<H>, <D>, and <O> display the Value column in hexadecimal, decimal, or octal format, respectively. The

default display is decimal.

<C> starts the Column Editor (Figure E-16). The Orion always displays four columns, and defaults to

the columns shown initially. In the column editor, columns can be removed from and added to the display. New columns are displayed in the order in which they were added. After specifying the desired

columns, <Esc> returns to the previous screen.

OrionLXm

E-15

COLUMN EDITOR

Add/Remove: Selected Columns:

1. Remove Name Name

2. Add Device Point Number

3. Add Data Type Value

4. Remove Point Number Percent FS

5. Add Changes

6. Add Fails

7. Add Successes

8. Remove Value

9. Remove Percent FS

0. Add Comm Status

A. Add Forced

B. Add Alias

Figure E-16: Data View Column Editor

Field Description

Name Point’s tagname, such as Breaker424 @HVRelay.

Device Device from which the point originates, such as HVRelay.

Data Type AI: Analog Input, BI: Binary Input, ACC or CI: Accumulator/Counter Input.

Point

Number

Protocol-specific point number. Depending on the protocol and the way it addresses

points, points may be numbered in hexadecimal (17h), decimal (23), or octal (27o).

The MMI will display the point address the way the specific protocol addresses points. If

there is a bit position within a word, the point number is displayed as 17:03, which

means bit 3 in word 17. Bit numbering and word sizes are protocol dependent, i.e. bit 1 can be LSB or MSB, and a word can be 8 bits or 16 bits. The respective protocol manual provides detailed information.

Changes Counter that displays the number of point changes since the Orion (re)start. For analog or accumulator points, every data change increments the corresponding change counter by 1. For digital points, every 0-1 or 1-0 transition increments the change counter by 1.

Fails Failed polls for the specific point.

Successes Successful polls for the specific point.

Value Current value of the point as per communication with an end device. If the point has been forced, the forced value will be displayed instead of the value from the end device.

Percent

FS

Percent of full scale of the current value. For example, if the value is scaled from –2048

to 2047, and the current value is 1024, this file will show 0.75 for 75%.

Comm

Status

If the corresponding value is updated from the remote device, the field will show

Online. If there is any type of communication error with the remote device, the field will

show Offline.

Forced No or Yes, depending on whether the value is obtained from the slave device, or

overridden by a value entered at the Orion MMI.

Table E-3: Data Point Information

OrionLXm

E-16

The Sort Editor (Figure E-17) is started by pressing the <S> key. The editor allows sorting of the

data screen by any of the displayed columns. Table E-3 shows the available sort criteria. Up to three sort criteria can be selected, each in ascending (lowest value first) or descending order (highest value first). First, one or more of the existing sort criteria must be removed. Then the new sort criteria must be

selected. Ascending order will be indicated by ASC, and descending order will be indicated by DESC.

Once the sort order is specified, <Esc> returns to the previous screen.

SORT EDITOR

Add/Remove: Sort Order:

1. Add Name Device ASC

2. Remove Device Data Type ASC

3. Remove Data Type Point Number ASC

4. Remove Point Number

5. Add Changes

6. Add Fails

7. Add Successes

8. Add Value

9. Add Percent FS

0. Add Comm Status

A. Add Forced

B. Add Alias

Figure E-17: Data View Sort Editor

OrionLXm

E-17

View Output Values On the following screen (Figure E-18), the port whose point values are to be monitored is selected. The last output value sent to the device is displayed. Depending on the application, the output value may have been sent by a master that the OrionLXm is connected to as a slave, or it may have been generated by logic running in the OrionLXm, or it may have been forced at the MMI.

OrionLX

Version 1.39.8 Date: 05/27/2009

Copyright 2000-2009 NovaTech LLC

Output Values

--------------------------------------------

1. Port 1 - SEL Master

2. Port B - DDIO Port

3. Port 20 - NTP Kernel

4. Port 21 - Sensor Master

5. Port 24 - XML

6. Port 25 - SER Master

7. Port 26 - AAR Slave

8. Port 124 - Logic

Figure E-18: Select Port for Output Monitoring

Once a port is selected, all of its values are displayed as follows.

Output values for Port 25 - SER Master (p1)

Name Point Number Last Output Percent FS

Output1 @OrionIO 1 0 0.000000

Output2 @OrionIO 2 1 100.00000

Output3 @OrionIO 3 0 0.000000

Output4 @OrionIO 4 1 100.00000

ESC=Back C=Column Editor S=Sort Editor H=Hex D=Dec O=Oct

Figure E-19: Output Point Monitoring

The (Cursor Up) and (Cursor Down) keys allow scrolling through all the points on the selected port.

<Esc>, <C>, <S>, <H>, <D>, <O>, and <G> are identical options for viewing input values, and are

explained in the section View Input Values.

OrionLXm

E-18

Override Input Values Overriding input values allows testing of the correct transmission of values to the master that is polling the OrionLXm, without having to generate those values in the end device in the field. This can be necessary under several circumstances:

The end device and/or the communication to it, have not yet been installed, or are temporarily not available.

Generation of test values in the end device is too complicated or not possible, depending on the end device.

By default, this function is enabled when the configuration file is set up in NCD. As with the other options, first select the port of the point that is to be forced temporarily.

OrionLX

Version 1.39.8 Date: 05/27/2009

Copyright 2000-2009 NovaTech LLC

Force Input Values

--------------------------------------------

1. Port 1 - SEL Master

2. Port B - DDIO Port

3. Port 20 - NTP Kernel

4. Port 21 - Sensor Master

5. Port 24 - XML

6. Port 25 - SER Master

7. Port 26 - AAR Slave

8. Port 124 - Logic

Figure E-20: Select Port for Forcing Input Values

The (Cursor Up) and (Cursor Down) keys allow scrolling to the point which is to be forced. All points on the port are available, and are sorted in alphabetical order of the tagname. The current point is always

highlighted. Pressing <Enter> selects the point to be forced. <G> (Goto) allows jumping to a specific

point by entering the point number.

OrionLXm

E-19

Force values for Port 1 - SEL Master (p1)

Comm Fail @SEL 501 Dual Relay

Meter IAX @SEL 501 Dual Relay

Meter IBX @SEL 501 Dual Relay

Meter ICX @SEL 501 Dual Relay

PassThru Status @SEL 501 Dual Relay

Polls @SEL 501 Dual Relay

Responses @SEL 501 Dual Relay

Figure E-21: Select Input Point

FORCE INPUT VALUE

Point Name: Meter IAX @SEL 501 Dual Relay

Percent Full Scale: 0.018311

Comm Status: Online

Minimum Value: 0.000000

Maximum Value: 32767.000000

Scaled Value: 6.000000

Manually Forced: No

Force Value

Back

Figure E-22: Force Input Point

Pressing <Enter> while on Force Value in the above screen displays the following screen (Figure

E-23). By entering the following parameters, an input point can be forced to a specific value. This facilitates the testing of the Orion’s communication link with any SCADA master polling those input values without having to go through the effort of forcing the test values in the end devices in the field.

With this command, the OrionLXm data point will indicate an equipment state or condition to the SCADA master that is only simulated, and does not reflect the actual state or condition. This may lead the SCADA master computer or personnel to initiate operations based on the simulated state as opposed to the actual state. The necessary permissions must be obtained from the control center and other departments in accordance with your corporate safety and operating guidelines. Failure to do so could result in equipment damage, injury, and/or death.

OrionLXm

E-20

FORCE INPUT VALUE

Point Name: Comm Fail @SEL 501 Dual Relay

Percent Full Scale: 0.000000

Comm Status: Online

Minimum Value: 0.000000

Maximum Value: 1.000000

Scaled Value: 0.000000

Manually Forced: No

Forced Point Values

Scaled Value [ 0.000000]

Percent Full Scale [ 0.000000]

Comm Status [ Online]

Time to Remain Forced [ 5]

Force Value

Cancel

Figure E-23: Enter Input Point Value

Function Description

Scaled Value

Percent Full

Scale

One of these two values is required for all point types. For digital input points,

enter 0-1 or 0-100 percent, and for analog values enter either the scaled value,

or its percentage of full scale. Regardless of the point type, a value must be entered in either of those two fields, as this is the value that will be sent to any polling SCADA master.

Comm Status A point can be simulated as being either Online or Offline. Online

indicates that the value is received online from the end device. Offline means

that there is no communication with the end device. However, the most recent value as of the time of the last communication can still be polled.

Time to Remain

Forced

Determines how long the point will stay in the simulated state before returning to the actual value as obtained from the end device. The unit is minutes.

Offtime (ms) For pulse output points, the offtime between on-pulses is required as well.

Force Value

Cancel

After entering the above parameters, Force Value or Cancel must be

selected. Cancel immediately returns to the points list (Figure E-21). Force

Value displays a prompt to confirm the operation before sending the entered

output point value to the field device.

Table E-4: Force Input Point Parameters

OrionLXm

E-21

FORCE INPUT VALUE

Point Name: Meter IAX @SEL 501 Dual Relay

Percent Full Scale: 0.024415

Comm Status: Online

Minimum Value: 0.000000

Maximum Value: 32767.000000

Scaled Value: 8.000000

Manually Forced: Yes

Remove Forced Value

Back

Figure E-24: Remove Forced Input Value

Clear Input Override With this option, forced inputs can be cleared. This means that all forced input values are removed, and that the realtime values from the field devices are used and transmitted to the master station again.

Are you sure that you want clear the override flag

for all input values? This will cause all forced

inputs to change value on the next scan.

(Y/N)

Figure E-25: Clear Input Override

With this command, multiple value and state changes may be reported to the SCADA master. All involved personnel must be informed of this step in order to avoid wrong responses to the realtime data reported to the SCADA master. Failure to do so could result in equipment damage, injury, and/or death.

OrionLXm

E-22

Send Output Values This function sends output values to connected slave/end devices as entered by the Orion. During normal operation, any output commands sent to those devices would be issued by a front end/SCADA master, and merely passed-through by the Orion. This function can be used for localized testing without involving the entire system end-to-end. By default, this function is enabled when the configuration file is set up in NCD.

With this command, you will possibly operate a live piece of equipment on the end device, the same way it would be operated locally, or from the front end/SCADA master. The necessary permissions must be obtained from the control center and other departments in accordance with your corporate safety and operating guidelines. Failure to do so could result in equipment damage, injury, and/or death.

For the output point to be forced, first select the point’s port (Figure E-26).

OrionLX

Version 1.39.8 Date: 05/27/2009

Copyright 2000-2009 NovaTech LLC

Output Values

--------------------------------------------

1. Port 1 - SEL Master

2. Port B - DDIO Port

3. Port 20 - NTP Kernel

4. Port 21 - Sensor Master

5. Port 24 - XML

6. Port 25 - SER Master

7. Port 26 - AAR Slave

8. Port 124 - Logic

Figure E-26: Select Port for Forcing Output Values

The (Cursor Up) and (Cursor Down) keys allow scrolling to the data point to be forced (Figure E-27). All points on the port are available, and are sorted in alphabetical order of the tagname. The current point

is always highlighted. Pressing <Enter> selects the point to be forced. <G> (Goto) allows jumping to a

specific point after entering the point’s number.

OrionLXm

E-23

Force outputs for Port 25 - SER Master (p1)

Output1 @OrionIO

Output2 @OrionIO

Output3 @OrionIO

Output4 @OrionIO

Figure E-27: Select Point for Forcing Output Value

On the following screen, the two initial choices are Force Value and Back. Back will return to the point

selection screen (Figure E-27). Force Value displays the screen in Figure E-28. This screen is a

“generic” screen in that it shows all parameters possibly needed, whether the output point is a simple discrete output, a select-before-operate output, a trip/close output, a pulse output, or an analog output/setpoint. Depending on the protocols used to connect the front end/SCADA master to the end device, only a selection of the listed types will be available, as either the protocol between the front end and the Orion and/or the protocol between the Orion and the end device may not support all point types.

Point Name: Output2 @OrionIO

Percent Full Scale: 0.000000

Comm Status: Offline

Minimum Value: 0.000000

Maximum Value: 1.000000

Scaled Value: 0.000000

Force Value

Back

Figure E-28: Forcing Output Value

OrionLXm

E-24

FORCE OUTPUT

Point Name: Output2 @OrionIO

Percent Full Scale: 0.000000

Comm Status: Offline

Minimum Value: 0.000000

Maximum Value: 1.000000

Scaled Value: 0.000000

Forced Output Values

Scaled Value [ 0.000000]

Percent Full Scale [ 0.000000]

Duration (msec) [ 0]

Pulses [ 0]

Offtime (msec) [ 0]

Force Value

Cancel

Figure E-29: Entering Forced Output Value

Function Description

Scaled Value

Percent Full

Scale

One of these two values is required for all point types. For digital output points,

enter 0-1 or 0-100 percent, and for analog values enter either the scaled value,

or its percentage of full scale. Regardless of the point type, a value must be entered in either of those two fields, as this is the value that will be sent to the output point.

Note: Depending on the output point type, the following fields may be required.

Duration (ms) Usually, trip/close, raise/lower, and pulse outputs require a duration. If none is entered, and a default value is used in the point configuration, the default value is used instead.

Pulses For pulse output points, the number of pulses is required.

Offtime (ms) For pulse output points, the offtime between on-pulses is required as well.

Force Value

Cancel

After entering Scaled Value/Percent Full Scale, Duration, Pulses,

and Offtime, Force Value or Cancel must be selected. Cancel

immediately returns to the points list (Figure E-27). Force Value displays a

prompt to confirm the selection on a separate screen before sending the entered output point value to the field device.

Table E-5: Force Output Point Parameters

OrionLXm

E-25

3. View Communications The ability to view the realtime communications of all OrionLXm ports facilitates identifying and resolving communication and configuration questions. To view communications, the port to be monitored must first be selected from the screen shown in Figure E-30 by entering its number. Live communication sent and received on this port of the OrionLXm will then be displayed (Figure E-31). If the OrionLXm is a master, then an exchange typically starts with a

transmission of a poll/command (indicated by TX), and ends with a reception of the reply (RX). If the

OrionLXm is a slave, an exchange typically consists of a reception (RX) of a poll/command, to which the

OrionLXm replies with the transmission of a reply (TX). The OrionLXm displays limited verbose

explanation of the data exchanged. For a detailed explanation, refer to the standard manual of the protocol that is being monitored. Typically, the protocol manuals are not supplied by NovaTech, but by the supplier of the equipment that the OrionLXm connects to.

OrionLX

Automation Platform

Version 1.39.8 Date: 05/27/2009

Copyright 2000-2009 NovaTech LLC

Communications Menu

--------------------------------------------

1. Port 1 - SEL Master

2. Port B - DDIO Port

3. Port 20 - NTP Kernel

4. Port 21 - Sensor Master

5. Port 25 - SER Master

6. Port 26 - AAR Slave

Figure E-30: Communications Menu

OrionLXm

E-26

Viewing Communications for Port B - DDIO Port

Press 'c' to change comm display options.

SYSTEM INFORMATION DUMP:

Uptime: 20 days, 19 hrs, 10 min

(Port B)(16:54:28:043):

(Port B)(16:54:28:043): Event/Individual Point Poll - DDIO Address 1

(Port B)(16:54:28:203)TX[33]: 05 64 18 C4 01 00 05 00 (99 F2)-CRC

C1 C1 01 3C 04 06 3C 03 06 3C 02 06 01 02 01 00 (55 82)-CRC

00 07 00 (9E 78)-CRC

(Port B)(16:54:28:281)RX[34]: 05 64 19 44 05 00 01 00 (EB CD)-CRC

C1 C1 81 10 00 01 02 01 00 00 07 00 01 01 01 01 (2C 0A)-CRC

01 01 01 01 (BF B9)-CRC

(Port B)(16:54:28:282): DDIO

(Port B)(16:54:28:282): IIN: Time Sync Request

(Port B)(16:54:28:284): Parse Binary Inputs - Range 0 to 7

(Port B)(16:54:29:087):

(Port B)(16:54:29:087): Event/Individual Point Poll - DDIO Address 1

(Port B)(16:54:29:246)TX[33]: 05 64 18 C4 01 00 05 00 (99 F2)-CRC

C2 C2 01 3C 04 06 3C 03 06 3C 02 06 01 02 01 00 (E9 E6)-CRC

00 07 00 (9E 78)-CRC

(Port B)(16:54:29:326)RX[34]: 05 64 19 44 05 00 01 00 (EB CD)-CRC

C2 C2 81 10 00 01 02 01 00 00 07 00 01 01 01 01 (90 6E)-CRC

01 01 01 01 (BF B9)-CRC

Figure E-31: Viewing Communications

Additional communication information can be displayed by pressing <c> (lowercase) to change the

Communication Display Options (Figure E-32). Any of the listed display options can be turned on

or off. For most communications issues, turning on the timestamps and the sequence numbers will be most useful. In order to effectively analyze protocol communication, familiarity with the monitored protocol and the corresponding protocol documentation is required. The communication can also be logged to a file, and sent to NovaTech for analysis. This allows in-depth tracking of issues.

OrionLXm

E-27

COMM DISPLAY OPTIONS

0. Transmit Messages YES

1. Receive Messages YES

2. Transmit Errors YES

3. Receive Errors YES

4. Non Data Messages YES

5. Non Data Errors YES

6. Verbose Messages YES

7. Include Timestamp YES

8. Include Sequence Num.NO

9. Include Port Num. YES

A. Include Device Num. NO

B. Include Data Length. YES

C. Sys Info On 15min. NO

Figure E-32: Communications Display Options

The following tables (Table E-6 and Table E-7) provide an overview of the most common issues when

using the View Communications feature of the Orion. Depending on the OrionLXm’s configuration

and communication system architecture, there may be numerous additional scenarios that can only be examined on a case-by-case basis.

OrionLXm

E-28

Master Port Troubleshooting The OrionLXm communicates as a master to one or more end devices which are single-dropped (RS-232, RS422/485, optical fiber) or multi-dropped (RS422/485, optical fiber) on a single port.

Observation Issue

There are no polls for an expected device.

The device has not been configured at all.

The device has been configured, but with another device node address. (If multidropped, another end device may respond in its place.)

The poll time (in Polls Groups) has been set to an excessive time, so the polls could be much farther apart than anticipated.

There are no responses to polls sent out by the OrionLXm.

The baud rate/parity bits/data bits/stop bits are not set up correctly in the device or the OrionLXm.

The cable/connection between the OrionLXm and the device is not plugged in.

The connection between the OrionLXm and the device is not set up correctly (for example, a straight serial cable is used instead of a null-modem cable, etc.).

There are error responses to polls sent out by the OrionLXm.

The poll/command going to the end device is asking for points that are not configured in the end device. Check the point types and addresses in the end device, and verify against the points configured in the OrionLXm. This could be either an address specified in the command, or the length/number of points specified.

If an error is returned for an output command, the value specified in the command could be out of range.

Table E-6: Master Port Troubleshooting

OrionLXm

E-29

Slave Port Troubleshooting The OrionLXm communicates as a slave to a front end/SCADA master. The OrionLXm can be part of a multi-dropped network, and/or host multiple devices with different addresses. This way, the OrionLXm responds to the master for each device that it hosts, and the master cannot tell that it is communicating with a single OrionLXm in place of multiple RTUs.

Observation Issue

There are no polls for the device hosted by the Orion.

The front end/SCADA master is not set up (yet) to poll for the new device.

The baud rate/parity bits/data bits/stop bits are not set up correctly in the device or in the Orion.

The cable/connection between the Orion and the device is not plugged in.

The connection between the Orion and the device is not set up correctly (for example, a straight serial cable is used instead of null-modem cable, etc.).

There are no responses from the Orion.

There is a device address mismatch between the master and the device(s) in the Orion, so the Orion does not see any of “its” devices addressed.

There are multiple responses/ noise when the response is returned, and the master reports communication/CRC/BCH errors.

There is another device on the shared line with the same address as a device in the Orion. Thus, both devices respond to the same command, which results in overlaid simultaneous responses to the master, which in turn logs a communication error.

Table E-7: Slave Port Troubleshooting

OrionLXm

E-30

4. Device Statistics The following screen shows the statistics for each slave device connected to the OrionLXm. Slave devices are devices being polled by the Orion.

<C> resets the poll/response counters for all devices to 0. The counters roll over at 232

(= 4,294,967,296).

The (Cursor Up) and (Cursor Down) keys allow scrolling through all the points on the selected port. These options allow verifying connectivity and communication quality with slave devices.

Device Statistics (C to Clear)

Port Device Status Polls Responses Percent Successful

1 SEL 501 Relay Online 392442 392442 100.000000

B DDIO Online 1168083 1168083 100.000000

Figure E-33: Device Statistics

OrionLXm

E-31

5. System Menu

The System Menu provides the Clock Configuration, Event Log, System, and Version

Information, etc. for the OrionLXm as shown in the following menu.

All menu items in Figure E-34 are hyperlinks to the respective sections.

OrionLX

Automation Platform

Version 1.40.0 Date: 09/22/2009

Copyright 2000-2009 NovaTech LLC

System Menu

--------------------------------------------

1. Clock Configuration

2. View System Info

3. View Event Log

4. Clear Event Log

5. View Version Info

6. Passthrough Menu

7. Thread Info

8. Restart

Figure E-34: System Menu

OrionLXm

E-32

Clock Configuration The hardware clock of the OrionLXm can be set with the following menu. In order to change time or date, select the respective item by entering the associated menu number as shown below.

For the new time to take effect, option 7. Save Time must be selected after the correct time and date

have been entered with options 1. through 6.

OrionLX

Automation Platform

Version 1.40.0 Date: 09/22/2009

Copyright 2000-2009 NovaTech LLC

Clock Configuration

--------------------------------------------

Current Date/Time: 10/14/2009 16:28:10

New Date/Time: 10/14/2009 16:27:21

1. Set Seconds

2. Set Minutes

3. Set Hours

4. Set Day

5. Set Month

6. Set Year

7. Save Time

Figure E-35: Clock Configuration

OrionLXm

E-33

View System Info The System Information screen displays the following information.

OrionLX

Automation Platform

Version 1.40.0 Date: 09/22/2009

Copyright 2000-2009 NovaTech LLC

System Information

--------------------------------------------

Process Uptime: 14 days, 02 hrs, 56 min

System Uptime: 14 days, 23 hrs, 27 min

Keynum: 9000

Figure E-36: System Information

Function Description

Process Uptime Shows the time since the last configuration change or software reboot of the OrionLXm.

System Uptime Shows the time since the last power-cycle or hardware reboot of the OrionLXm.

Keynum Serial number of the OrionLXm.

Table E-8: System Information

OrionLXm

E-34

View Event Log An OrionLXm event log is displayed below. It includes all events since the last warm boot or configuration change. If needed, the log can be captured to a file as well (see chapter Communications Menu or, if using third-party software to connect to the OrionLXm, refer to that software’s documentation for details).

OrionLX

Automation Platform

Version 1.40.0 Date: 09/22/2009

Copyright 2000-2009 NovaTech LLC

View Event Log

--------------------------------------------

09/30/2009 18:31:56.500 notice: Orion Started!

09/30/2009 18:31:57.289 prtcl err: No function body found for

LogicOut1Change.

09/30/2009 18:31:57.289 prtcl err: No function body found for

OrionOut4Change.

09/30/2009 18:31:58.329 notice: LoadLibrary(mmi)

09/30/2009 18:31:59.858 notice: LoadLibrary(/usr/lib/orion/salar001.so)

09/30/2009 18:32:00.192 notice: LoadLibrary(/usr/lib/orion/msel129.so)

09/30/2009 18:32:00.409 notice: LoadLibrary(/usr/lib/orion/mdnp126.so)

09/30/2009 18:32:00.625 notice: LoadLibrary(/usr/lib/orion/mnki100.so)

09/30/2009 18:32:00.738 notice: LoadLibrary(/usr/lib/orion/msens101.so)

09/30/2009 18:32:00.853 notice: LoadLibrary(/usr/lib/orion/sled100.so)

09/30/2009 18:32:00.968 notice: LoadLibrary(/usr/lib/orion/shttp106.so)

09/30/2009 18:32:05.285 notice: Logic started.

10/13/2009 21:00:02.340 prtcl err: Archive Monitor: Connect failed.

Error: could not connect to server: No such file or directory

Is the server running locally and accepting connections on Unix domain

socket "/var/run/postgresql/.s.PGSQL.5432"?

10/13/2009 21:00:04.344 prtcl err: Archive Monitor: Connect failed.

Error: could not connect to server: No such file or directory

Is the server running locally and accepting connections on Unix domain

socket "/var/run/postgresql/.s.PGSQL.5432"?

10/13/2009 21:00:06.352 prtcl err: Archive Monitor: Connect failed.

Error: could not connect to server: No such file or directory

Is the server running locally and accepting connections on Unix domain

socket "/var/run/postgresql/.s.PGSQL.5432"?

Figure E-37: View Event Log

Clear Event Log The event log described in the previous chapter can be cleared by selecting this option. Note that when selecting this option, the event log is cleared without requiring further confirmation.

OrionLXm

E-35

View Version Info This option lists the version and date of the protocol drivers and software as configured for each port. If needed, the version information can be captured to a file (see chapter Communications Menu or, if using third-party software to connect to the OrionLXm, refer to that software’s documentation for details).

OrionLX

Automation Platform

Version 1.40.0 Date: 09/22/2009

Copyright 2000-2009 NovaTech LLC

Version Information

--------------------------------------------

Orion Core Module - main.exe Version 1.40.0 09/22/2009 13:41:01

Port 1. SEL Master - msel129.so Version 1.29.5 09/17/2009 14:47:34

Port 2. none

Port 3. none

Port 4. none

Port 5. none

Port 6. none

Port 7. none

Port 8. none

Port 9. none

Port 10. none

Port 11. none

Port 12. none

Port 13. none

Port 14. none

Port 15. none

Port 16. none

Port A. Man Machine Interface - Version 1.36.3 12/10/2008 09:09:01

Port B. DNP Master - mdnp126.so Version 1.26.19 08/4/2009 15:41:01

Port C. none

Port D. none

Port 20. ntp interface - mnki100.so Version 1.0.3 09/15/2009 15:03:01

Port 21. Sensors - msens101.so Version 1.1.1 12/17/2008 10:06:01

Port 22. Sensors - sled100.so Version 1.0.0 09/15/2008 16:07:01

Port 23. http server - shttp106.so Version 1.6.0 08/15/2008 08:18:19

Port 24. xml slave - sxml102.so Version 1.2.3 05/26/2009 11:47:00

Port 25. SER - mser100.so Version 1.0.7 07/13/2009 09:09:01

Port 26. AlarmArchiver - salar001.so Version 0.1.5 08/27/2009 10:04:00

Figure E-38: Version Information

OrionLXm

E-36

Passthrough Menu Many manufacturers of IEDs (Intelligent Electronic Devices) such as relays and meters provide special software for device configuration, event and log extraction, etc. If the end device has two ports, the second port can be directly connected to the PC running that software, bypassing the control network with the OrionLXm. However, the second port may not be available, or it may be impractical to use it. With the Passthrough option, the IED manufacturer software installed on the PC can connect through the OrionLXm to the IED. This requires the following steps. Passthrough to an IED

1. In the main menu, select 5) System Menu.

2. In this submenu, select 6) Pass-Through Menu.

3. In the Pass Through Menu (Figure E-39), select a port number for passthrough.

4. At this point, NCD (or the terminal software) is directly connected to the IED, and a screen similar to Figure E-40 will be displayed.

4a. At this point, manual commands can be entered. These commands are sent directly to the IED and executed, and the IED response is displayed in this screen.

4b. Alternatively, the IED manufacturer software can be started and connected to the IED after exiting NCD. The IED software must use the same communication parameters that NCD used (since the software will first connect with the Orion, and the Orion in turn will connect with the IED). Once the IED operations are completed, the manufacturer’s software must be closed and

NCD restarted. In the NCD communication window, entering <Ctrl>-<X> five times

terminates the passthrough of the Orion.

OrionLX

Communication Processor

Version 1.40.0 Date: 09/22/2009

Copyright 2000-2009 NovaTech LLC

Pass Through Menu

--------------------------------------------

1. Pass Through to Port 1 - SEL Master 1

2. Pass Through to Port 2 - SEL Master 2

3. Pass Through to Port 10 - SEL Master 10

Figure E-39: Passthrough Menu

OrionLXm

E-37

Entering Pass Through Mode

Press CTRL-X five times to exit

2

3I2X IRX 3I2Y IRY

I (A,pri) 4 3 8 7

=>>QUI

HP-233 Date: 10/26/09 Time: 22:17:09.603

HP-232

=

Figure E-40: Passthrough Window to Relay

OrionLXm

E-38

Thread Info This option lists the running threads in the Orion, with port number and system/user time. If needed, the thread information can be captured to a file (see chapter Communications Menu or, if using third-party software to connect to the OrionLXm, refer to that software’s documentation for details).

ORION Thread Dump

0x40377490: Logging System Monitor Thread (port=0 level=1) Priority=0

tid: 4889

System Time: 0

User Time: 0

0x403E6490: MMI Port_17_Thread (port=17 level=0) Priority=0

tid: 4890

System Time: 0

User Time: 1

0x40625490: Alarm_Archive Main Thread 30 (port=30 level=0) Priority=0

tid: 4891

System Time: 0

User Time: 1

0x40718490: SEL Master Task_p1_Thread (port=1 level=0) Priority=0

tid: 4893

System Time: 1813

User Time: 788

0x40758490: SEL Master Start_p1_Thread (port=1 level=1) Priority=0

tid: 4894

System Time: 110796

User Time: 17260

0x407BC490: DNP Master Task_p18_Thread (port=18 level=0) Priority=0

tid: 4895

System Time: 98398

User Time: 41088

0x40808490: mnki_24_Thread (port=24 level=0) Priority=0

tid: 4896

System Time: 5701

User Time: 697

0x40856490: msens_25_Thread (port=25 level=0) Priority=0

tid: 4897

System Time: 13023

User Time: 1144

0x408A1490: sled_26_Thread (port=26 level=0) Priority=0

tid: 4898

System Time: 11

User Time: 3

0x408FC490: HTTP_main_27 (port=27 level=0) Priority=0

tid: 4899

System Time: 158

User Time: 101

0x40958490: sxml_p28_Thread (port=28 level=0) Priority=0

tid: 4900

System Time: 0

OrionLXm

E-39

User Time: 0

0x409E6490: AAR Monitoring Thread 30 (port=30 level=1) Priority=0

tid: 4902

System Time: 26

User Time: 23

0x40A26490: Archive Monitoring Thread 30 (port=30 level=1) Priority=0

tid: 4903

System Time: 815

User Time: 874

0x40A66490: LogicThread (port=0 level=0) Priority=0

tid: 4904

System Time: 802

User Time: 46314

0x40AA6490: LOGICEventThread (port=128 level=1) Priority=0

tid: 4905

System Time: 0

User Time: 0

0x40AE6490: RPC Call tid 1085170832 (port=0 level=1) Priority=0

tid: 4906

System Time: 37

User Time: 10

0x40C3F490: DNP Master Monitor Thread_p18_Thread (port=18 level=1)

Priority=0

tid: 4907

System Time: 0

User Time: 0

0x40D40490: MMI UDS on /var/run/orion/mmi (port=0 level=1) Priority=0

tid: 9687

System Time: 15

User Time: 9

0x40DC1490: MMI TCP RX to (port=0 level=1) Priority=0

tid: 9688

System Time: 2

User Time: 0

0x40E01490: MMI TCP TX to (port=0 level=1) Priority=0

tid: 9689

System Time: 17

User Time: 13

Figure E-41: Thread Info

OrionLXm

E-40

Restart

A Full restart resets all hardware and restarts all software and drivers, including the operating

system. However, it can take up to several minutes for the OrionLXm to boot up, depending on the OrionLXm’s configuration.

A Quick restart reloads only the protocol drivers which usually takes under 60 seconds to complete.

Do you wish to perform a full restart, quick restart or no restart?

1. Full restart.

2. Quick restart.

3. Do not restart.

Figure E-42: Restart Menu

6. Disconnect This option closes the current session and disconnects NCD from the Orion.

OrionLXm

E-41

7. Session Timeouts The session times out, i.e. disconnects, automatically after 5 minutes. As shown below, the timeout can be based on:

whether any user key strokes were sent to the OrionLXm within those 5 minutes whether any user key strokes were sent to the OrionLXm, or any information – such as screen

updates, communication updates, etc. – was sent from the OrionLXm to the PC within those 5 minutes

The second option is useful when logging information from the OrionLXm for lengthy periods of time.

OrionLX

Automation Platform

Version 1.40.0 Date: 09/22/2009

Copyright 2000-2009 NovaTech LLC

Session Timeouts

--------------------------------------------

Current session behavior:

End session if the Orion hasn't received in 5 minutes.

Press 1 to change behavior to:

End session if the Orion has neither sent or received in 5 minutes.

Figure E-43: Session Timeouts

OrionLXm

E-42

8. Network Menu On the Network Menu, the OrionLXm network parameters such as IP address, gateway, and firewall can be set up. All menu items in Figure E-44 are hyperlinks to the respective sections.

OrionLX

Automation Platform

Version 1.40.0 Date: 09/22/2009

Copyright 2000-2009 NovaTech LLC

Network Menu

--------------------------------------------

1. View/Change Network Configuration

2. Start/Stop Firewall

Figure E-44: Network Menu

OrionLXm

E-43

View/Change Network Configuration

This menu allows changing the network parameters common to both eth0 and eth1, as well as port-

specific parameters, by selecting options 1., 2., or 3.

If any changes have been made, option 4. Save Settings must be executed before pressing <Esc>

to return to the previous menu.

OrionLX

Automation Platform

Version 1.40.0 Date: 09/22/2009

Copyright 2000-2009 NovaTech LLC

View/Change Network Configuration

--------------------------------------------

Common Hostname: orionlx

DNS Server 1: 64.126.4.189

DNS Server 2: 64.126.4.193

eth0 IP Address: 172.16.16.20

Subnet: 255.255.0.0

Gateway:

eth1 IP Address: 64.126.95.173

Subnet: 255.255.240.0

Gateway: 64.126.80.1

1. Edit Common

2. Edit eth0

3. Edit eth1

4. Save Settings

Figure E-45: View/Change Network Configuration

OrionLXm

E-44

Common Parameters

The following parameters are common to both eth0 and eth1. The specific parameters are determined

as part of the system architecture, or by the IT department.

OrionLX

Automation Platform

Version 1.40.0 Date: 09/22/2009

Copyright 2000-2009 NovaTech LLC

View/Change Network Configuration

--------------------------------------------

Common Hostname: orionlx

DNS Server 1: 64.126.4.189

DNS Server 2: 64.126.4.193

1. Edit Hostname

2. DNS Server 1

3. DNS Server 2

Figure E-46: Edit Common Parameters

Function Description

Hostname The hostname is a name assigned to the host computer, i.e. the OrionLXm. The name is often a combination of the host’s local name and the parent domain name.

DNS Server 1

DNS Server 2

For Internet communication initiated by the OrionLXm, usually a Domain Name System server is required. This server translates outgoing requests to actual IP addresses. This server can be located on the Internet, or on the corporate network. If no DNS is required for communications to and from the OrionLXm, it is recommended to leave the DNS server fields empty.

Table E-9: Common Parameters

OrionLXm

E-45

Port-Specific Parameters

The following parameters are set up individually for eth0 and eth1. Since each port can be connected

to a different network, the parameters are entered separately for each port. The specific parameters are determined as part of the system architecture, or by the IT department.

OrionLX

Automation Platform

Version 1.40.0 Date: 09/22/2009

Copyright 2000-2009 NovaTech LLC

View/Change Network Configuration

--------------------------------------------

eth0 IP Address: 172.16.16.20

Subnet: 255.255.0.0

Gateway: 172.16.16.1

1. Enable DHCP

2. Edit IP Address

3. Edit Subnet

4. Edit Gateway

Figure E-47: Edit Port-Specific Parameters

Function Description

Enable DHCP If DHCP is enabled, the IP Address, Subnet, and Gateway are assigned by a DHCP server on the network. In most cases, DHCP will be disabled and these parameters are entered manually as permanent values as described below. Generally, these parameters are determined as part of the system architecture, or by the IT department.

IP Address The IP address has the format n.n.n.n where n = 0..255, e.g. 172.16.16.20.

Subnet The Subnet mask has the format n.n.n.n where n = 0..255, e.g. 255.255.0.0.

Gateway The Gateway address is required for outbound traffic that is located on another

network. It has the format n.n.n.n where n = 0..255, e.g. 172.16.16.1.

Table E-10: Port-Specific Parameters

Note: Each port must belong to a different network and set up with corresponding IP

addresses. If network ports are set up with IP addresses belonging to the same IP network, IP communication errors may occur.

Example 1: 192.168.x.x and 172.16.x.x are different networks. Example 2: With subnet mask 255.255.255.128, the ranges 192.168.1.1 - 192.168.1.127 and

192.168.1.129 - 192.168.1.255 are different networks.

OrionLXm

E-46

Start/Stop Firewall The following menu provides the options for starting or stopping the Orion’s firewall. Additional firewall options and settings are described in chapter Firewall.

OrionLX

Automation Platform

Version 1.40.0 Date: 09/22/2009

Copyright 2000-2009 NovaTech LLC

Start/Stop Firewall

--------------------------------------------

1. Start firewall

2. Stop firewall

Figure E-48: Start/Stop Firewall

OrionLXm

F-1

F. Glossary

OrionLXm

F-2

Term Description

HMI Human Machine Interface

Input Point An input point is generally a point whose value originates at an end device

(slave device), such as a PLC, RTU, IED, relay, or meter, and is transferred

to one or more master devices, such as a SCADA master, or a HMI. During

the transfer, the information may travel over different media (such as dialup or

leased line modems, Ethernet, radio, etc.) as well as different protocols as

dictated by the master’s and end device’s capabilities and locations.

IED Intelligent Electronic Device. This general term includes relays, meters, and

other devices equipped with a microprocessor.

Master Device A master device issues polls or commands to slave devices in order to obtain

values from the slave device, or to cause specific behavior or actions by the

slave device. Typical master devices are SCADA masters and HMIs. If a

port on the Orion is set up as a master port, the OrionLXm will initiate

communication with the slave device(s) connected to that master port.

NTP Network Time Protocol

Output Point An output point is generally a point whose value originates at a master device

(such as HMI or SCADA master, etc.) and is then transferred to the end

device to control some type of action or behavior of the end device (such as

opening or closing connected switches, control computations, retrieve specific

logs, etc.). During the transfer, the information may travel over different

media (such as dialup or leased line modems, Ethernet, radio, etc.) as well as

different protocols as dictated by the master’s and end device’s capabilities

and locations.

PLC Programmable Logic Controller

RTU Remote Terminal Unit

SCADA Supervisory Control And Data Acquisition

Slave Device A slave device responds to a poll or command from a master device, but

generally does not initiate communications with another device or the master

on its own. Typical slave devices are PLCs, RTUs, IEDs, meters, and relays.

If a port on the OrionLXm is set up as a slave port, an external master must

issue a poll or command to that port of the OrionLXm for that port to issue

communication.

Table F-1: Glossary

OrionLXm

G-3

G. Additional Documentation

OrionLXm

G-4

The following additional documentation may be required for setting up and operating the OrionLXm. In addition, for each specified protocol, the respective manual is included on the installation CD.

By default, the NCD installation stores the NovaTech documentation files in C:\Program Files

(x86)\NovaTech LLC\NCD3\Docs. Third-Party documentation is not included on the NovaTech

installation CD and cannot be verified as accurate by NovaTech.

Document Title File Name

OrionLX Applications Manual OrionLX_Applications_Manual.pdf

Adding OrionLX Protocols Field Instructions FieldInstructions_Adding_OrionLX_Protocols.pdf

Analog/Accumulator Scaling Technical Note TechNote_Scaling.pdf

Alarm/Archive/Retentive for Orion Software Manual Protocol_Alarm_Archive_Retentive_Module.pdf

Archive Add-On for Orion Software Manual Protocol_Average_Archive.pdf

Cascading for OrionLX Software Manual Protocol_OrionLX_Cascading.pdf

DA Logic for Orion Software Manual Protocol_DA_Logic.pdf

Data Logger for Orion Software Manual Protocol_OrionLX_Data_Logger.pdf

DNP3 Master Software Manual Protocol_DNP3_Master.pdf

Email for OrionLX Software Manual Protocol_Email_Slave.pdf

IEC 61131 for OrionLX Software Manual Protocol_IEC61131-3.pdf

IEC 61850 Client for OrionLX Software Manual Protocol_IEC61850_Client.pdf

Logic for Orion Software Manual Protocol_Logic.pdf

LogicPak for Orion Software Manual Protocol_LogicPak.pdf

Points Blocking Module for OrionLX Protocol_Points_Blocking_Module.pdf

Pseudo Master for Orion Software Manual Protocol_Pseudo_Master.pdf

Pusher Slave for Orion Software Manual Protocol_Pusher_Slave.pdf

System & Point Logger for Orion Software Manual Protocol_Orion5r_System&Points_Logger.pdf

Text Module for Orion Software Manual Protocol_OrionLX_Text_Generator.pdf

Updating OrionLX Firmware Technical Note TechNote_Update_OrionLX_Firmware.pdf

Web Alarm Annunciator for Orion Software Manual Protocol_Orion5r_Web_Alarm_Annunciator.pdf

Table G-1: NovaTech Documentation

OrionLXm

G-5

Revision Date Changes

A 05/16/14 Initial Release for OrionLXm. MM, BM

B 02/10/15 Updated Pinout tables, updated NCD and WebUI screens. New communication and I/O cards. BM