Orion MMI

User Manual

July 22, 2008

Document Revision H
© 2001, 2006 by NovaTech, LLC
 Orion MMI

NovaTech, LLC
13555 West 107th Street
Lenexa, KS 66215
(913) 451-1880
www.novatechweb.com
support@novatech-llc.com

© Copyright 2001, 2006 by NovaTech, LLC

All Rights Reserved

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.

Warning: Failure to comply with applicable codes and standards can result in damage to this
equipment, damage to connected devices, and/or serious injury to personnel.

ii
 Orion MMI
Table of Content
I. Introduction and Requirements .......................................................................................................... 6

II. Orion Port A .......................................................................................................................................... 7

III. Connecting to the Orion MMI .............................................................................................................. 8

Serial Connection ................................................................................................................................. 9
Telnet Connection .............................................................................................................................. 10
Save Connection Setup ..................................................................................................................... 12
Orion Menus and Logging ................................................................................................................. 14

IV. MMI Main Menu ................................................................................................................................... 17

1. File Menu....................................................................................................................................... 18
1. File Transfer (PC -> Orion).................................................................................................... 18
2. File Transfer (Orion Æ PC) ................................................................................................... 20
3. Make Config File Active ........................................................................................................ 21
4. Delete a File............................................................................................................................ 23
5. View a File .............................................................................................................................. 24
2. Data Menu ..................................................................................................................................... 25
1. View Input Values .................................................................................................................. 27
2. View Output Values ............................................................................................................... 31
3. Override Input Values ........................................................................................................... 33
4. Clear Input Override .............................................................................................................. 37
5. Send Output Values .............................................................................................................. 38
3. View Communications................................................................................................................. 41
Troubleshooting........................................................................................................................... 44
4. Device Statistics........................................................................................................................... 46
5. System Menu ................................................................................................................................ 47
1. Clock Configuration .............................................................................................................. 47
2. View System Info ................................................................................................................... 48
3. View Event Log ...................................................................................................................... 49
4. Clear Event Log ..................................................................................................................... 49
5. View Version Info................................................................................................................... 50
6. Pass-Through Menu .............................................................................................................. 51
7. Thread Info ............................................................................................................................. 53
8. Restart .................................................................................................................................... 54

Appendix A – Recovery Menu ................................................................................................................. 55

Appendix B – TCP/IP Setup...................................................................................................................... 58

1. Test Connection to Orion ............................................................................................................ 58
2. Determine Your PC’s IP Address ............................................................................................... 60
3. Set Your PC’s IP Address ........................................................................................................... 61
4. Determine Your Orion’s IP Address and Connectivity............................................................. 63

Appendix C – Setting up additional MMI Ports ...................................................................................... 66

Index ........................................................................................................................................................... 68

iii
 Orion MMI
List of Figures

Figure 1: Online Setup .................................................................................................................................. 8

Figure 2: Select Connection to Orion............................................................................................................ 8
Figure 3: Setting up Serial Connection to Orion ........................................................................................... 9
Figure 4: Setting up Telnet to Orion............................................................................................................ 10
Figure 5: Orion IP Address.......................................................................................................................... 11
Figure 6: Orion MMI TCP Port .................................................................................................................... 12
Figure 7: Save Connection Parameters...................................................................................................... 13
Figure 8: Port Status Indication................................................................................................................... 14
Figure 9: Orion MMI Main Menu ................................................................................................................. 15
Figure 10: Log File ...................................................................................................................................... 16
Figure 11: Orion Main Menu ....................................................................................................................... 17
Figure 12: File Menu ................................................................................................................................... 18
Figure 13: File Transfer PC Æ Orion .......................................................................................................... 19
Figure 14: File Transfer Orion Æ PC .......................................................................................................... 20
Figure 15: Configuration File Selection....................................................................................................... 21
Figure 16: Restart after Configuration Change ........................................................................................... 22
Figure 17: Delete File in Orion .................................................................................................................... 23
Figure 18: View File Header........................................................................................................................ 24
Figure 19: Orion Data Menu........................................................................................................................ 25
Figure 20: Force Inputs/Outputs Setup....................................................................................................... 26
Figure 21: Select Port for Input Point Monitoring ........................................................................................ 27
Figure 22: Input Point Monitoring................................................................................................................ 28
Figure 23: Data View Column Editor........................................................................................................... 29
Figure 24: Data View Sort Editor ................................................................................................................ 30
Figure 25: Select Port for Output Point Monitoring ..................................................................................... 31
Figure 26: Output Point Monitoring ............................................................................................................. 32
Figure 27: Select Port for Forcing Input Values .......................................................................................... 33
Figure 28: Select Input Point....................................................................................................................... 34
Figure 29: Force Input Point........................................................................................................................ 34
Figure 30: Enter Input Point Value.............................................................................................................. 36
Figure 31: Forced Input Point...................................................................................................................... 36
Figure 32: Force Output Point..................................................................................................................... 38
Figure 33: Enter Output Point Value ........................................................................................................... 39
Figure 34: Confirm Forcing of Output Point ................................................................................................ 40
Figure 35: View Communications Menu ..................................................................................................... 41
Figure 36: Viewing Communications .......................................................................................................... 42
Figure 37: Communications Display Options.............................................................................................. 43
Figure 38: Device Statistics......................................................................................................................... 46
Figure 39: System Menu ............................................................................................................................. 47
Figure 40: Set Orion Time........................................................................................................................... 48
Figure 41: Orion System Information .......................................................................................................... 48
Figure 42: View Event Log .......................................................................................................................... 49
Figure 43: Orion Version Information.......................................................................................................... 50
Figure 44: Orion Pass-Through Menu ........................................................................................................ 51
Figure 45: Pass-Through to IED ................................................................................................................. 52
Figure 46: Orion Thread Information........................................................................................................... 53
Figure 47: Orion Restart Menu ................................................................................................................... 54
Figure 48: Orion Recovery Menu................................................................................................................ 55
Figure 49: Load File in Recovery Mode ...................................................................................................... 56
Figure 50: Start Command Window............................................................................................................ 58
Figure 51: Successful Ping of Orion ........................................................................................................... 59
Figure 52: Failed Ping of Orion ................................................................................................................... 59
Figure 53: ipconfig /all ................................................................................................................................. 60

iv
 Orion MMI
Figure 54: Network Connections................................................................................................................. 61
Figure 55: Local Area Connection Status ................................................................................................... 61
Figure 56: Local Area Connection Properties ............................................................................................. 62
Figure 57: Set PC’s TCP/IP Address .......................................................................................................... 62
Figure 58: Orion MMI Command Line Interface.......................................................................................... 63
Figure 59: ceipconfig................................................................................................................................... 64
Figure 60: ping ............................................................................................................................................ 65
Figure 61: Setting up additional MMI Ports................................................................................................. 66
Figure 62: Setting up additional MMI Ports................................................................................................. 67
Figure 63: MMI Port Setup for 1-16, B-D .................................................................................................... 67

List of Tables

Table 1: Serial/Ethernet Cables and Software.............................................................................................. 6

Table 2: Orion Files Types .......................................................................................................................... 19
Table 3: Data Point Information .................................................................................................................. 29
Table 4: Master Port Troubleshooting......................................................................................................... 44
Table 5: Slave Port Troubleshooting........................................................................................................... 45

v
 Orion MMI

I. Introduction and Requirements

The Orion provides a built-in MMI for viewing of 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 using the respective manufacturer’s programming software to configure the relays and meters,
retrieve event information, etc.

The Orion’s dedicated MMI port is port A over a serial RS232 connection. Additional serial ports on the
Orion can be set up as MMI port 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 Telnet and the Orion’s Ethernet port(s). Again, multiple MMI windows can run simultaneously.

Using the MMI requires NCD (NovaTech Communications 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
Serial Connection Ethernet Connection
Hardware - null-modem cable (included with - Ethernet cable
Orion, part number NT-NM9MF) - PC with Ethernet connection
- PC with available serial port (COM1,
COM2, etc.)
Software - NCD or - NCD or
- any terminal software - any software which allows Telnet
(HyperTerminal, CRT, etc) connection (CRT, etc.)
Table 1: Serial/Ethernet Cables and Software

6
 Orion MMI

II. Orion Port A

The principal configuration and MMI port of the Orion 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, 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 (and any other serial port set up as MMI port) requires a null-modem cable
(NovaTech part number NT-NM9MF) which is included with a new Orion. In case you design your own
cable, the Orion requires only three lines to be connected, Transmit, Receive, and Ground. Port A has a
standard RS232 pinout on a DB9 female connector:

Pin Usage
2 Receive
3 Transmit
5 Ground

Loading a NCD configuration file into the Orion enables the Orion to operate the configured protocols on
all other ports, as well as additional MMI ports, user-defined logic, etc.

7
 Orion MMI

III. Connecting to the Orion MMI

The following steps show how to connect to the Orion MMI using the NCD (NovaTech Communication
Director) either by way of a serial connection or a telnet connection.

Note: When connecting to the Orion for the first time, or when a previously configured connection does
not seem to work as intended, always use port A (serial connection) to load the configuration into
the Orion and/or to determine the Orion’s state.

If you are using other terminal software, consult the documentation supplied with that software regarding
the setup for a connection to the Orion.

Figure 1: Online Setup

Figure 2: Select Connection to Orion

8
 Orion MMI
In NCD, click on Communications, then Online (Figure 1). You will first see the screen in Figure 2.
Initially, there will be no connections listed in the Connections folder. If you have previously defined a
connection, such as COM1_115200, simply double-click on the connection, and the connection to the
Orion will be established.

If you click on New in Figure 2, the following window (Figure 3) allows you to define all communication
parameters for both serial and telnet connections.

The Orion and NCD provide the capability of logging the Orion MMI output (for example protocol
communications) to a file which will be stored on the PC’s hard drive. Usually the logging is limited in
time, hence the logging file will be of limited size and stored in uncompressed format. However,
sometimes logging is necessary for extended periods of time. Enable Compression is by default not
checked. However, if extended logging is needed, this option should be checked, and the resulting log file
on the PC’s hard drive will then be compressed. In this case, the file format is bzip2, and the file
extension is .bz2. www.bzip.org/downloads.html provides free utilities to decompress the log

Disable ZModem Handshaking is by default not checked, meaning that handshaking is enabled.
ZModem is the protocol used to transfer files, including the configuration files, to and from the Orion. If
Handshaking is enabled, each file block is individually acknowledged before the next block is sent. While
the handshaking increases overall file transfer time, it is recommended since it can be used in all
situations, including modem and radio connections. Disabling the handshaking is recommended only for
direct connections when the entire file can be sent with a reasonable probability of no block loss.

Terminal Back Color and Terminal Fore Color allow you to set the MMI display colors. In this
example, they are set to white background and black foreground. Depending on the computer screen and
lighting available to you, you may set those colors to your specific preference.

Serial Connection
If the connection is to port A, select Serial, 115200 baud, parity None, 8 Data Bits and 1 Stop Bit. If you
configured a MMI on ports 1-16 or B-D, the parameters entered here depend on the MMI parameters as
set up for that specific port (see Figure 63).

The standard serial port is COM1. However, if your PC has multiple serial ports, or a special configuration,
you need to select the correct serial port (COM2, COM3, etc.)

Figure 3: Setting up Serial Connection to Orion

9
 Orion MMI

Telnet Connection

For a telnet connection to the Orion, select TCP/IP (as opposed to Serial) in Figure 4.

For Host Addr and Port, enter the Orion’s IP address and MMI port as entered in the Orion’s Network
Parameters (see Figure 5) and MMI TCP Port (see Figure 6).

Figure 4: Setting up Telnet to Orion

10
 Orion MMI

Figure 5: Orion IP Address

11
 Orion MMI

Figure 6: Orion MMI TCP Port

Save Connection Setup

Once all connection parameters have been set up, you can either save the connection to a file for later
reuse, or go immediately online with the Orion.

Save allows saving changes to an existing “named” connection.

Save As saves the current parameters to a new file (Figure 7). This new file will then be available as a
“named” connection for subsequent links to the Orion MMI.

For ease of use, it is recommended to use meaningful names when naming connections, to include ports,
baud rates, IP addresses, etc.

12
 Orion MMI

Close immediately proceeds to the terminal screen with the current set of communication parameters,
without saving them to file.

Figure 7: Save Connection Parameters

13
 Orion MMI

Orion Menus and Logging

At this point, you are connected to the Orion (Figure 9). This is also indicated by the green (as opposed to
red) Port Status light in the upper right hand of the terminal window (Figure 8). If you do not see an
Orion menu, press the <Esc> key, and/or click on Connect.

User Name and Password for Telnet Connection

When you connect to the Orion with a Telnet connection, and in the Orion’s .ncd file, you configured the
Orion MMI to use a Remote User Name and Remote Password in the screen shown in Figure 6, the
first screen when connecting to the Orion is the Login screen which prompts you for the user name and
password as entered in Figure 6. Notice that both the user name and the password are case-sensitive.

Remote Attempts Before Lockout determines how many login attempts trigger a Lockout, i.e. a
period during which any remote login is disabled. The length of the period is specified in Remote
Lockout Time. Both parameters are also set in Figure 6.

If Remote User Name and Remote Password are left empty, there will be no login required. Instead,
the Orion MMI (Figure 9) will be displayed immediately.

On any MMI screen displayed by NCD, the Port Status flag in the upper right hand corner of the MMI
screen will display the connection status (Figure 8). It does not, however, indicate whether data has been
transmitted.

Serial Connection The green LED indicates that the selected serial port of your PC (typically COM1)
has been opened successfully. Even if the serial cable were not connected, the
LED would still be green. The red LED indicates that the selected serial port has
not been opened yet, or could not be opened. The latter is the case when another
program uses the same serial port.

Telnet Connection The green LED indicates that the PC has established a TCP connection with the
Orion. The red LED indicates that the selected serial port has not been opened
yet, or could not be opened.

Figure 8: Port Status Indication

Everything you enter at this screen (Figure 9) is not processed by your PC but passed to the Orion for
processing. For example, entering a 1 will select File Menu, and the Orion will display the specific
menu. Likewise, the content of the terminal windows is supplied by the Orion, while the NCD program is
running on the PC.

14
 Orion MMI

Figure 9: Orion MMI Main Menu

Regardless of the menu or screen displayed by the Orion, its content can be logged to a file on the PC for
logging and troubleshooting. Simply click on one of options on the terminal windows as marked in Figure
9.

Start Capture opens the Windows file window to specify a log file (Figure 10). This logs all menu
communication returned from Orion to a log file. This is particularly useful for troubleshooting, for example
communications (see option 3). This way, the Orion operation can be logged and examined very easily. If
needed, the file can also be emailed to NovaTech for support. If file compression was selected in (Figure
3, Figure 4), the file will be stored as a bzip2 file with extension .bz2, instead of the standard .log
format.

Reset Orion5/Reset Orion16 restarts the respective type of Orion, depending on what type of Orion
you are connected with. This may be necessary if upon power up, the Orion keeps displaying
Loading............... without actually completing the loading and displaying the MMI. This
command reboots the Orion, but instead of booting to the MMI, the Orion will boot to the recovery menu
(see Appendix A). In this menu, you can disable the current configuration and then restart the Orion.

Disconnect closes the current MMI session (Port Status goes to red). This option is available only if you
are currently connected.

Setup and Connections allow setting up a new and/or choosing an existing connection. These options
are available only if you are currently disconnected.

15
 Orion MMI

Figure 10: Log File

In case the above menu (Figure 9) does not show, use the following steps to troubleshoot the connection
to the Orion and the login.

Serial Connection
• Hit <Esc>. In addition, keep <Esc> pressed and see if the red Rx LED of the Orion lights.
• Make sure the cable between the PC and the Orion is a null-modem cable
• Make sure you use the correct communication parameters on your PC software (115200N81 for
Port A, or for any other port, the settings entered in the NCD).

Telnet Connection
• On your PC, use the Ping command to see whether the PC can “see” the Orion. Start a command
line window on a Windows PC, and enter Ping <Orion address>, for example Ping
192.168.0.100. You will either get Reply from 192.168.0.100 ... if there is a
connection between your PC and the Orion. If there is no connection, you will see Request
Timed Out. This is due to your network setup, both devices being on physically different
networks, or using different addressing.
• Verify Orion IP address vs. address used in Telnet, especially if Orion is set up not to use static
IP address but DHCP-assigned address
• Make sure PC and Orion are on the same network

Login
• Both the user name and the password (as entered in Figure 6) are case-sensitive.
• After the specified number of failed logins, no logins are possible until the specified lockout period
expires.

16
 Orion MMI

IV. MMI Main Menu

Using either serial connection or Telnet connection, the Orion displays the following main menu (Figure
11).

Orion Firmware
Version and Date

Active Configuration
File with Date/Time of
Last Change in NCD

Up/Download and View Live Data I/O

Selection of Orion Values by Port
Configurations
View Live Data View Information
Communications Regarding Device
by Orion Port Connectivity

System Functions
and Information

Figure 11: Orion Main Menu

If connected by Telnet, there will also be option 6) Disconnect. This option terminates the Telnet
session. If connected serially, Disconnect at the end of the session is not necessary.

Note: If you have several MMI windows (by way of a serial connection, and/or several Telnet
connection) open to the same Orion, each individual data screen, communication screen, or
system screen can be viewed by only one MMI window. If another windows attempts to view the
same screen, for example “View Input Data for Port 4”, it will instantly revert to the previous
menu. If this happens, it is not a malfunction of the Orion, but an indication that the screen is
already displayed in another MMI window.

17
 Orion MMI

1. File Menu
The file menu (Figure 12) allows you to upload, download, make active and remove configuration files
from the Orion. File transfers between your PC and the Orion use the Z-Modem file transfer protocol.

Command the Orion

to wait for an Select a file on the
incoming Z-Modem Orion to send to
transfer connected PC via
Z-Modem
Select which
configuration the
Orion should use

Remove a selected
configuration from View the first
the Orion page of a file

Figure 12: File Menu

1. File Transfer (PC -> Orion)

Select and download a configuration file to the Orion. First, you will see the screen in Figure 13. You can
download the currently opened .ncd file. Alternatively, you can click Browse, and the Windows file
window as in Figure 10 will allow you to select one or more files for download. This can be one or more
files as follows (Table 2):

This option is generally used for downloading .ncd files, or specific protocol files for troubleshooting. For
updating the Orion to the latest protocol driver versions, please see NovaTech’s Technical Note Updating
Orion Firmware and NCD.

18
 Orion MMI

File Type/Extension File Use Description

.ncd Orion Configuration File Configure the Orion’s ports with
protocols and points.
.bas Orion Logic File Basic file containing logic executed by
the Orion.
.dll, .exe Orion Driver File Only downloaded when a new driver
becomes available. Oftentimes this
update is performed by the Orion
Updater, a stand-alone program which
brings all drivers in an Orion up to the
most current level.
o16.key Orion Key File They key file specifies what protocol
drivers a specific Orion is authorized to
run. Even if a specific driver is
downloaded into the Orion, it will not
execute without the proper
authorization.
Table 2: Orion Files Types

Figure 13: File Transfer PC Æ Orion

19
 Orion MMI
2. File Transfer (Orion Æ PC)

This feature uploads a specific file from the Orion to your PC. The typical reason for this would be to
review a configuration that has been downloaded from another PC that is currently not available. First,
specify the file to be uploaded by its number on the following screen (Figure 14). Note that files can be
uploaded only one at a time.

If more than 20 files are listed, 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.

Figure 14: File Transfer Orion Æ PC

Then a Windows file window as shown in Figure 10 appears where you specify the name and location on
the hard drive for the file that is to be uploaded. After the upload, the menu in Figure 12 will be displayed
again.

20
 Orion MMI
3. Make Config File Active

An Orion can have several .ncd files (and associated .bas logic files) stored in its flash memory. However,
only one of those files can be active at any given time. This option allows you to specify what
configuration file the Orion shall load and operate. Of course, you need to make sure that the
configuration file loaded is actually intended for the specific Orion, and that the Orion has the correct
hardware options installed. In the following screen (Figure 15), specify the configuration file to load by its
number. If there is a logic file associated with a configuration file, it will be loaded automatically.

Figure 15: 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 16). If no restart is chosen, the Orion will continue to
operate with the current configuration file.

A Full Restart resets all hardware and restarts all software and drivers, including the operating
system. However, it can take up to several minutes, depending on your configuration.

A Quick Restart reloads only the protocol drivers and takes usually under 60 seconds to complete.
However, if the configuration changed substantially, or configured hardware that is not installed, or
hardware that requires a full restart, the Quick Restart will automatically turn into a Full Restart.

21
 Orion MMI

Figure 16: Restart after Configuration Change

22
 Orion MMI
4. Delete a File

If multiple configuration files are downloaded to the Orion for testing, commissioning, or for a lab unit,
eventually files have to be deleted off the flash drive of the Orion. Again, this option shows a list of files
(Figure 17), 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.

After a file has been specified, you will be prompted to confirm/cancel its deletion, before the menu
returns to the screen in Figure 12.

Note that the Orion’s file system supports 100 files which allows for all necessary drivers and
configurations. However, it may become necessary to delete files if that number is exceeded.

Figure 17: Delete File in Orion

23
 Orion MMI
5. View a File

View a File allows you to view a configuration file. Again, the file to be viewed is specified in a screen
as show in Figure 18. Then the actual file is displayed. You can use the ↑ (Cursor Up) and ↓ (Cursor
Down) keys to scroll through the file. <Esc> will return to the menu in Figure 12. Entering G will prompt
you for a line number to go to, and then display that line.

Figure 18: View File Header

24
 Orion MMI

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 point information on a port-by-port basis. With the NCD default configuration, you will see
only options 1) and 2) on the following screen (Figure 19).

For the purpose of this manual, an input point is a point that is obtained from an end device, and an
output point is a point that is sent to an end device. Since the Orion 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.

Options 3. Override Input Values, 4. Clear Input Override, and/or 5. Send Output
Values are available only if the configuration file is set up accordingly. Figure 20 shows the fields in
General Settings to be un/checked for dis/enabling forcing inputs and outputs. Forcing an input/output
means that the Orion will use the value(s) you insert into to Orion as described below when
communicating to 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.

Figure 19: Orion Data Menu

25
 Orion MMI

Figure 20: Force Inputs/Outputs Setup

26
 Orion MMI
1. View Input Values

On the following screen (Figure 21), select the port whose point values are to be monitored.

Figure 21: Select Port for Input Point Monitoring

Each data point in the Orion 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 Orion for the
point’s value. A point can also be mapped to more than one slave port if more than one master polls the
Orion for that point. The Orion 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 Tech Note Analog/Accumulator Scaling for more details.

27
 Orion MMI

Figure 22: Input Point Monitoring

With the ↑ (Cursor Up) and ↓ (Cursor Down) keys, you can scroll through all the points on the selected
port.

G allows you to quickly go to a specific page. Press G, and Goto: will appear in the lower left hand
corner. Enter the page number you want to go to, and press <Enter>.

<Esc> returns to the screen in Figure 19.

H/D/O allow display of the Value column in hexadecimal, decimal, or octal format. The default display is
decimal.

C starts the Column Editor (Figure 23). The Orion will always show four columns, and defaults to the
columns shown initially. In the column editor, remove the columns you do not want displayed, and add the
columns you want displayed. Add the columns in the order in which you want them displayed. The
following information can be displayed. Once you have selected the columns you want displayed, a single
<Esc> will return to the data screen (Figure 19).

28
 Orion MMI

Figure 23: Data View Column Editor

Field Description
Name Point’s tag name, 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 Protocol-specific point number. Depending on the protocol and the way it addresses
Number 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. Please consult the protocol
manual for details.
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 end device. If the point has been
forced, the forced value will be displayed instead of the value from the end device.
Percent Percent of full scale of the current value. For example, if the value is scaled from –2048
FS to 2047, and the current value is 1024, this file will show 0.75 for 75%.
Comm If the corresponding value is updated from the remote device, the field will show
Status 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 3: Data Point Information

29
 Orion MMI

S starts the Sort Editor (Figure 24). The Sort Editor allows sorting the data screen by any of the displayed
columns. In other words, first pick the columns you want displayed, and then pick the sort criteria. Table 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 remove one or more of the existing sort criteria, and
then select the new sort criteria. Then you will be prompted for the sort order. Ascending order will be
indicated by ASC, and descending order will be indicated by DESC. Once you specified the sort order you
want displayed, a single <Esc> will return to the data screen (Figure 19).

Figure 24: Data View Sort Editor

30
 Orion MMI
2. View Output Values

On the following screen (Figure 25), select the port whose point values are to be monitored. You will see
the last output value sent to the device, regardless of whether the value was sent by a master to which
the Orion is connected as a slave, whether the value was generated by logic running in the Orion, or
whether the value was forced at the MMI (see below).

Figure 25: Select Port for Output Point Monitoring

31
 Orion MMI

Figure 26: Output Point Monitoring

With the ↑ (Cursor Up) and ↓ (Cursor Down) keys, you can scroll through all the points on the selected
port.

<Esc>, C, S, H, D, O and G are identical options as for viewing input values, and are explained in the
section View Input Values.

32
 Orion MMI
3. Override Input Values

Overriding input values allows for 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. 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.

As with the other options, first select the port (Figure 27) of the point that is to be forced temporarily.

Figure 27: Select Port for Forcing Input Values

With the ↑ (Cursor Up) and ↓ (Cursor Down) keys, you can scroll to the point you want to force (Figure
28). All points on the port are available, and are sorted in alphabetical order of the tag name. The current
point is always highlighted. Press <Enter> to select the point to be forced. G (Goto) allows jumping to a
specific point by entering the point number.

33
 Orion MMI

Figure 28: Select Input Point

Figure 29: Force Input Point

34
 Orion MMI
When you press <Enter> while on Force Value (Figure 29), the following screen (Figure 30) will appear.
By entering the following parameters, you can force input values to specific values. This facilitates 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.

Warning: With this command, you will possibly 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.
Depending on your operational procedures, you may be required to get
permission, or check with either end or both ends before issuing any output
commands. Failure to do so may result in equipment damage and/or bodily harm.

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 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: You can simulate the point 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 (in minutes) determines how long the point will stay in the simulated state
before returning to the actual value as obtained from the end device.

Force Value forces the point to the simulated values just entered.

Cancel abandons the values just entered, and the point continues to be updated from the end device.

35
 Orion MMI

Figure 30: Enter Input Point Value

Then (Figure 31) you can Remove Forced Value, and/or go Back to the main point list and force
additional points.

Figure 31: Forced Input Point

36
 Orion MMI

4. Clear Input Override

Clear Input Override terminates all input overrides. Typically this is done when testing of a point or
group of points is completed.

Depending on the commissioning requirements after the successful testing, you may want to disable the
option to force values from the MMI for live operation. To do this, deselect the Force options in the NCD
file, and download the now-tested NCD file without the Force options to the Orion and restart the Orion.
This decision will have to be made based on your operational guidelines and requirements.

37
 Orion MMI
5. 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.

Warning: 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. Depending on your operational procedures, you may be required to get
permission, or check with either end or both ends before issuing any output
commands. Failure to do so may result in equipment damage and/or bodily harm.

As with forcing input values, first select the point’s port (Figure 27) and then the point itself (Figure 28)
whose value is to be forced. Then you will see the following screen (Figure 32).

Figure 32: Force Output Point

The two initial choices are Force Value and Back. Back will return to the point selection screen (like
Figure 28). Force Value displays the screen in Figure 33. 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. The only values you need to enter
are the value required by the point type.

38
 Orion MMI

Figure 33: Enter Output Point Value

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 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.

Depending on the output point type, the following fields may be required.

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 is required.

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

After entering Scaled Value/Percent Full Scale, Duration, Pulses, and Offtime, you can
choose between Force Value and Cancel. Cancel will take you back immediately to the points list (Figure
28). Force Value will prompt you to confirm your selection on a separate screen as follows (Figure 34).

39
 Orion MMI

Figure 34: Confirm Forcing of Output Point

40
 Orion MMI

3. View Communications
The ability to view the communications of your data ports facilitates identifying and resolving
communication and configuration questions.

First, select the port to monitor from the screen shown in Figure 35. Enter the menu number of the port
that you would like to view. Then live communication sent and received on this port of the Orion will be
displayed (Figure 36). If the Orion is a master, then typically an exchange starts with a transmission of a
poll/command (indicated by TX), and ends with a reception of the reply (RX). If the Orion is a slave, an
exchange typically consists of a reception (RX) of a poll/command, to which the Orion replies with the
transmission of a reply (TX). The Orion 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 Orion
connects to.

Figure 35: View Communications Menu

41
 Orion MMI

Figure 36: Viewing Communications

Depending on the issue that is being monitored, you may turn on additional logging information while
monitoring the communication. Press lowercase c to change the Communication Display Options (Figure
37). You can turn on/off any of the listed display options. For most issues, turning on the timestamps and
the sequence numbers will be most useful.

In order to effectively view communication, you will need to be familiar with the monitored protocol and
have the corresponding protocol documentation available. The communication can also be logged to file
(see Figure 9 and Figure 10), and sent to NovaTech for analysis. This allows tracking of many kinds of
issues by turning on the log for extended periods of time, and then examining the log offline.

42
 Orion MMI

Figure 37: Communications Display Options

The following tables (Table 4 and Table 5) provide an overview of using the View Communications
feature of the Orion. This is a brief list of the most basic communication issues. Depending on your
configuration and system architecture, there may be numerous additional scenarios that can only be
examined on a case-by-case basis.

43
 Orion MMI
Troubleshooting

Orion Runs Master Protocol

The Orion is communicating as a master to one or more end devices which are single-dropped (RS232,
RS422/485, optical fiber) or multi-dropped (RS422/485, optical fiber) on a single port.

Observation Issue
There are no polls for an • The device has not been configured at all.
expected device. • 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 longer apart than anticipated.
There are no responses to polls • The baud rate/parity bits/data bits/stop bits are not set up
sent out by the Orion. correctly in the device or 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 straight serial cable instead of null-
modem cable, etc.
There are error responses to • The poll/command going to the end device is asking for points
polls sent out by the Orion. 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 Orion. 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 4: Master Port Troubleshooting

44
 Orion MMI
Orion Runs Slave Protocol

The Orion is communicating as a slave to a front end/SCADA master. The Orion can be part of a multi-
dropped network, and/or host multiple devices with different address. This way, the Orion responds to the
master for each device that it hosts, and the master cannot tell that it is communicating with a single
Orion in place of multiple RTUs.

Observation Issue
There are no polls for the device • The front end/SCADA master is not set up (yet) to poll for the
hosted by the Orion. new device.
• The baud rate/parity bits/data bits/stop bits are not set up
correctly in the device or 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 straight serial cable instead of null-
modem cable, etc.
There are no responses from the • There is a device address mismatch between the master and
Orion. the device(s) in the Orion, so the Orion does not see any of
“its” devices addressed.
There are multiple • There is another device on the shared line with the same
responses/noise when the address as a device in the Orion. Thus both devices respond to
response is returned, and the the same command, which results in overlaid simultaneous
master reports responses to the master, which in turn logs a communication
communication/CRC/BCH errors. error.
Table 5: Slave Port Troubleshooting

45
 Orion MMI

4. Device Statistics

The device statistics screen (Figure 38) lets you view communication statistics about all slave devices
attached to the Orion, i.e. devices that are 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)

Figure 38: Device Statistics

46
 Orion MMI

5. System Menu

The Orion system menu provides various system and internal functions.

Figure 39: System Menu

1. Clock Configuration

The Orion has a built-in system clock. Unless the Orion is equipped with an Irig-B module and the clock
adjusted automatically, the clock will drift over time. This function (Figure 40) allows you to enter the
current date and time (options 1 through 6), and then set the Orion clock to the new time (option 7). The
date/time you enter in options 1 through 6 will take effect the moment that you select option 7.

Some protocols also provide the functionality to set time in a device, such as the Orion. Please consult
the manuals for the protocols used with the Orion to determine whether this capability is available with the
configuration available in your Orion.

47
 Orion MMI

Figure 40: Set Orion Time

2. View System Info

System Information (Figure 41) provides information about the Orion’s uptime, memory usage, and other
internal information for NovaTech Engineering. Keynum indicates the serial number of the Orion.

Figure 41: Orion System Information

48
 Orion MMI

3. View Event Log

The event log contains any information about the Orion’s start, such as what protocols were loaded or
failed to load, what points were dropped (usually because they were specified for one port, but without a
matching entry at another port), and relevant events during startup and runtime. The following screen
(Figure 42) shows what a typical log looks like. If the log extends beyond a single screen, the scroll bar
enables you to scroll through all log entries. If needed, you may turn on the logging option (Start
Capture) to capture the log to file. After rerunning the View Event Log, the entire log content will be
logged to a file on your PC for easy reviewing or emailing to technical support.

Figure 42: View Event Log

4. Clear Event Log

If the above event log gets too long, or the information first logged is outdated, Clear Event Log can be
used to delete all current entries, essentially restarting the log.

49
 Orion MMI

5. View Version Info

As the firmware and protocol drivers in the Orion can be updated with the Orion Updater and/or one driver
at a time, it is necessary to be able to review the current versions of all software in the Orion. For each
driver, you will see its name, and its version number with main version, minor version, and release
number, and the release date/time.

Figure 43: Orion Version Information

50
 Orion MMI
6. Pass-Through 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 Orion. However, the second port may not be available, or it may be impractical to use it. With the
Pass-Through option, you can use the manufacturer’s software and connect to the IED through the Orion.
This requires the following steps.

Pass-Through to an IED

1. On the main menu, select 5) System Menu

2. On this submenu, select 6) Pass-Through Menu
3. On the Pass Through Menu (Figure 44), select the number of the port that you want to pass-
through to.
4. At this point, you are directly connected to the IED, and will see a screen returned by the IED
such as in Figure 45. Now you can do one or both of the following.
4a. You can manually enter commands.
4b. If you want to run the manufacturers software, exit NCD and start the specific software for the
IED on that PC. Make sure that this software uses 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 you are done, close the manufacturer’s software, restart NCD, and enter
<Ctrl>-X five times to terminate the pass-through.

Figure 44: Orion Pass-Through Menu

The ability to pass-through to an IED depends on several communication issues. For one, going through
another device, in this case the Orion, adds to the communication delay. Depending on the software and
IEDs used, you may need to adjust timeouts, timing parameters, and other communication parameters on
a case-by-case basis. Also if the manufacturer’s software makes special use of control lines, such as
DTR, DSR, RTS, CTS, or RI, taking that signal all the way through to the IED may or may not be possible.

51
 Orion MMI

Figure 45: Pass-Through to IED

52
 Orion MMI
7. Thread Info

Thread Information (Figure 46) lists the running threads in the Orion, with port number and user time. This
information is used by NovaTech Engineering for monitoring and evaluating the Orion’s operation and
performance.

Figure 46: Orion Thread Information

53
 Orion MMI
8. 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 Orion to boot up, depending on your
configuration.

A Quick Restart reloads only the protocol drivers and takes usually under 60 seconds to complete.
However, if configured hardware is not installed, or the Orion is equipped with a hardware module that
requires a full restart, the Quick Restart will automatically turn into a Full Restart.

Figure 47: Orion Restart Menu

54
 Orion MMI

Appendix A – Recovery Menu

In order to facilitate troubleshooting of startup and runtime issues, the Orion has a recovery mode, as
opposed to normal operation. This mode can be entered by continually pressing <Ctrl>-X when the
Orion is powering up. Once this mode is entered, the Orion will display the following screen (Figure 48) as
opposed to the normal MMI menu (Figure 9). Usually NovaTech Technical Support will be working with
you at this point to address the issue at hand.

Figure 48: Orion Recovery Menu

1. Reset file system to factory contents

This option resets drivers and configuration files to the way the Orion was originally delivered. Use this
option only if the MMI does not allow you to load a new configuration or driver more. This may be the
case after a previous download did not complete, or the downloaded file was corrupted. You need to run
the Orion Updater after selecting this option, in order to run the newest firmware after the reset. Refer to
NovaTech’s Tech Note Updating Orion Firmware and NCD for a detailed description of this process.

2. Disable current configuration

If the current configuration has an error in it that prevents the Orion from running or even loading the MMI
in Figure 9, this option disables the file orion16.ini. Once rebooted, the Orion will operate without an
active .ncd configuration file. This allows loading a new configuration if the previous configuration
prevented the Orion from running. Go to File Menu (page 18) to select and possibly first load a new file.

55
 Orion MMI
3. Reboot this unit

Once you are done with all the necessary steps in the recovery mode, this option will reboot the Orion.
Unless it is forced into recovery mode, it will boot into operating mode.

4. Wait for debugging host

This option is reserved for NovaTech Engineering.

5. ZModem PC -> Orion

This option allows loading a new file while in recovery mode. You will be prompted to select the file to be
loaded as shown in Figure 49. This allows replacing a faulty file that may keep the Orion from operating,
i.e. when the Orion reboots, it will reboot with the correct file.

Figure 49: Load File in Recovery Mode

6. View exception log

If there are any operation errors, NovaTech Technical Support may ask you to email the exception log.
Before selecting this option, Start Capture as shown in Figure 9. Once the entire log has been
displayed, End Capture, which closes the file, and email the file to support@novatech-llc.com.

56
 Orion MMI

7. Clear exception log

This option clears the content of the exception log once the log has become too long.

8. Display files on the flash disk

This option lists all files on the Orion’s flash disk, including the version number and the MD5SUM
checksum.

0. Exit this program

Once you are done with all the necessary steps in the recovery mode, this option will reboot the Orion.
Unless it is forced into recovery mode, it will boot into operating mode.

57
 Orion MMI

Appendix B – TCP/IP Setup

In order to connect to the Orion by Ethernet, you may need to verify the TCP connection to the Orion.
This may require several steps on your PC, depending on your network setup and PC setup, and the way
you have configured the Orion.

1. Test Connection to Orion

You can test the connection between your PC and the Orion by using the Windows Ping command. In
Windows, click on Start, then on Run, and then enter cmd.

Figure 50: Start Command Window

At the command window, enter ping and the Orion’s address, for example ping 172.16.72.51. If the
PC can communicate with the Orion, you will the see following screen (Figure 51). If the ping fails, i.e. the
PC cannot communicate with the Orion, you will see the screen in Figure 52.

When you are done with the command windows, simply enter exit<Enter>, and it will close.

58
 Orion MMI

Figure 51: Successful Ping of Orion

Figure 52: Failed Ping of Orion

59
 Orion MMI

2. Determine Your PC’s IP Address

In order to find out your PC’s address, start a command window (Figure 50). At the command window,
enter ipconfig /all<Enter>. The PC’s Ethernet and TCP/IP information will be displayed (Figure
53). In this case, the PC’s address is 172.16.3.33

Figure 53: ipconfig /all

60
 Orion MMI

3. Set Your PC’s IP Address

You can set on your PC’s IP address in Network Connections, which is part of the Control Panel.
Double-click on Local Area Connection, which is typically the way your PC is connected to the
Ethernet. This is needed if the PC connects to the Orion on a network without automatically assigned
addresses, i.e. without a DHCP (Dynamic Host Configuration Protocol) server. In this case the Orion and
the PC must be set up with different addresses on the same network, for example 192.168.1.1 and
192.168.1.2. If there are other devices on the network, you must ensure that the addresses you are
assigning to the PC and the Orion are not yet assigned to any other device

Figure 54: Network Connections

Figure 55: Local Area Connection Status

61
 Orion MMI

Figure 56: Local Area Connection Properties

Figure 57: Set PC’s TCP/IP Address

62
 Orion MMI

4. Determine Your Orion’s IP Address and Connectivity

The Orion’s IP address is set in NCD as shown in Figure 5. Once the .ncd file has been loaded into the
Orion, this address can be verified as follows. In the Orion MMI main menu (see Figure 9), select
5. System Menu. The press <Ctrl>-P. At this point, the Orion MMI switches from a menu driven
interface to a command line interface. This is also indicated by the # prompt at the beginning of each line
(Figure 58). At this point, a number of commands can be used. These commands have to be typed
verbose, as opposed to selecting a number from a menu.

Figure 58: Orion MMI Command Line Interface

ceipconfig

When you enter this command (followed by <enter>), the Orion will display the IP information as follows
(Figure 59). In this example, the Orion’s IP address is 172.16.72.88

63
 Orion MMI

Figure 59: ceipconfig

ping

The ping command allows you to verify IP connections to other IP devices. Enter the known IP address
of the device for which you want to check connectivity to the Orion, for example ping 192.168.1.30,
followed by <enter>. The response will indicate whether the remote device can be accessed with the
current network setup, by displaying either Reply from .... or Request timed out. In the example
shown in Figure 60, the Orion can access address 172.16.72.88 but not address 172.16.3.3.

If the pinged device cannot be accessed, check the following items:

• Correct IP addresses on all devices
• Network cabling between all devices, switches, hubs, routers, and other communication devices
• Power on all end devices and communication devices

64
 Orion MMI

Figure 60: ping

exit

The exit command closes the command line interface, and returns you to the MMI menu.

65
 Orion MMI

Appendix C – Setting up additional MMI Ports

For some applications, additional MMI ports may be needed, in addition to the standard MMI port on port
A. The additional MMI ports can be set up on serial ports numbered 1 through 16 and B through D
(depending on the Orion model) on the back of the Orion. This is done as part of the Orion configuration
in NCD. First, pick the port(s) you would like to set up as additional MMI port(s) (see Figure 61, Figure 62,
and Figure 63).

Figure 61: Setting up additional MMI Ports

66
 Orion MMI

Figure 62: Setting up additional MMI Ports

The communication parameters for each of the additional MMI ports can be set up per port as needed.
The settable choices are shown in Figure 63.

Note that for the MMI port the Use Automatic Settings checkbox must be unchecked and the driver
name MMI.dll be entered in the file name box.

Figure 63: MMI Port Setup for 1-16, B-D

67
 Orion MMI

Index

Additional MMI Ports, 66

Connecting to the Orion MMI, 8
Serial Connection, 9
Telnet Connection, 10
MMI Connection Requirements, 6
MMI Main Menu, 17
Data Menu, 25
Clear Input Override, 37
Override Input Values, 33
Send Output Values, 38
View Input Values, 27
View Output Values, 31
Device Statistics, 46
File Menu, 18
Delete a File, 23
File Transfer Orion->PC, 20
File Transfer PC->Orion, 18
Make Configuration File Active, 21
View a File, 24
System Menu, 47
Clear Event Log, 49
Clock Configuration, 47
Pass-Through Menu, 51
Restart, 54
Thread Info, 53
View Event Log, 49
View System Info, 48
View Version Info, 50
View Communications, 41
MMI Port A, 7
Recovery Menu, 55
Serial/RS232 MMI Connection, 7
Standard MMI Port, 7
TCP/IP
Check PC’s IP Address, 60
Orion’s IP Settings, 63
ceipconfig, 63
ping, 64
Set PC’s IP Address, 61
Test IP Connection PC-Orion, 58
Test Orion’s IP Connectivity, 64
TCP/IP MMI Connection, 58
Troubleshooting, 44
Orion runs Master Protocol, 44
Orion runs Slave Protocol, 45

68
 Orion MMI

Revision Date Changes

E 03/29/06 Full update BM
F 04/23/06 Miscellaneous additions BM
G 10/08/06 Standard layout, several additions. BM
H 07/22/08 NovaTech address change. PN

69