POWERVISION Configuration Studio®

Version 2.8

Core Reference Manual

00-02-0966
2015-07-09
Section 78
In order to consistently bring you the highest quality, full-featured products, we reserve the right to change our
specifications and designs at any time. The latest version of this manual can be found at www.fwmurphy.com.
Table of Contents
About the PowerVision Configuration Studio® Documentation..........................................1

What’s New in this Version .......................................................................................................2

What’s New in PowerVision 2.8 ...................................................................................2

About the PowerVision Configuration Studio®......................................................................7

Installing the PowerVision Configuration Studio ..................................................................8

System Requirements ..................................................................................................8

Installation Instructions .................................................................................................8
USB to Ethernet Setup for Direct Connection to a PV450 or PV780.................................12

ECOM Device Setup for Direct Connection to a PV350/380...............................................14

PowerVision Configuration Studio Software Overview......................................................17

Launching the Application ..........................................................................................17

Building Your First Configuration................................................................................23
Button to Create a New Configuration ..................................................................................29

Open Button to Access a Configuration...............................................................................30

Murphy Standard PV450: Configuration Tab .......................................................................31

Configuration Properties ............................................................................................31

Save Button to Store a Configuration ...................................................................................36

Save As Button to Store a Configuration with a Different Name ......................................36

Close a Configuration..............................................................................................................36

Select Target Hardware for a Configuration ........................................................................36

Edit in Language ......................................................................................................................37

Murphy Standard PV450: Connections Tab .........................................................................38

Module Setup .............................................................................................................38

Free Form CAN Messages.........................................................................................40
Free Form Data Messages.........................................................................................42
J1939/NMEA 2000 Parameter Mapping .....................................................................44
Diagnostic Trouble Code Mapping .............................................................................46
Transmitting Diagnostic Messages (DM1)..................................................................47
Diagnostic Message Memory Mapping ......................................................................47
 Serial Ports.................................................................................................................50
Murphy Standard PV450: Applications Tab .........................................................................52

Murphy Standard PV450: Page Designer Tab......................................................................53

Murphy Standard PV450: Library Tab ...................................................................................56

J1939/NMEA Parameters...........................................................................................57
Diagnostic Trouble Codes (DTC) ...............................................................................61
Predefined Curves .....................................................................................................62
Unit Conversion..........................................................................................................63
IO Definitions..............................................................................................................64
Customer Extensions .................................................................................................65
Murphy Standard PV450: Programming Tab .......................................................................66

ADDENDUM A...........................................................................................................................67

How to Install a Configuration from a USB Drive........................................................67

ADDENDUM B...........................................................................................................................67

Configuring your display for a Static IP Address ........................................................67

ADDENDUM C...........................................................................................................................71

Troubleshooting Common Connection Problems .......................................................71

THIS PAGE INTENTIONALLY LEFT BLANK
About the PowerVision Configuration Studio® Documentation
The PowerVision Configuration Studio documentation is now divided into four distinct modules.
They are:
• PowerVision Configuration Studio Core Reference Manual
• PowerVision Configuration Studio Page Designer Reference Manual
• PowerVision Configuration Studio Applications Reference Manual
• PowerVision Configuration Studio Programming Reference Manual
References are made to the other documents. Therefore, if all areas of the configuration studio
are used, it will be necessary to download all four documents.
In this core document, the following is covered:
• Software installation.
• A general overview of the software.
• The buttons and navigation used throughout the program.
• Basics about building configurations using the tool.
• Basics about the Connections module.
Intended Use
The following document is intended as a reference manual only.

Section 78 00-02-0966
2015-07-09 -1-
What’s New in this Version
The following is an overview of the UI changes coming in the PowerVision 2.8 release.
PowerVision 2.8 is a major release which brings a number of bug fixes, usability improvements
and new experimental features.

What’s New in PowerVision 2.8

• New Raw CAN Logging System. This feature allows you to record a limited amount of
Raw CAN traffic for use in debugging and diagnostics.
• Find All References in Images allows you to see where images are used in a
configuration.
• New Networking Features.
• Support for Custom Lists (Also in 2.7 Patch 2).
• Ability to Scroll Text in a Text Widget.
• New Switch Statement in Activities Programming.
• Ability to Center Align Gauges in Page Designer.
• Ability to Position State and Activity Objects with the keyboard.
• Ability to Scale Free Form Variables using Resolution and Offset.
• New Graph Widget (Also in 2.7 Patch 2) and Supporting Activity Shape.
• Performance Improvements and Optimizations to Embedded Runtime.
• Ability to read a DM String in Scripting.
• Configurable Timers. Timers can be adjusted on the fly by changing the associated
variable.
• Ability to send diagnostic messages (DM1).

Connections Page

Free Form Complete Notification

• You can now specify an event to fire when the Free Form message has been received
and parameters have been written.
• Improved Free Form String Messages (now called Free Form Data Messages)
o String messages work exactly like they performed in 2.6.
o Free Form Data messages now support Standard Multi-Packet Compatibility to
allow you to capture standard multi-packet messages.
o New Binary Messages route their data to a script for processing. To manage
this, build your message as you normally would specifying the start and continue
packets. Specify an event to fire when complete. To capture this event in

Section 78 00-02-0966
2015-07-09 -2-
 scripting define a script with the following signature….

void $YourFreeFormedBinaryEvent$(CANMessageBuffer @buffer)

{ }

This will fire your script and pass you a CANMessageBuffer object. This object
contains the data in your message which can be processed in scripts. Refer to
the Scripting Function reference for more details on how to read and write data
using the new CANMessageBuffer object.

• On The Fly Analog Mode and Curve switching

o To support changing the I/O channel
configuration on the fly, you can now
specify multiple analog I/O definitions
in the library. To switch I/O
definitions, you select the definitions
that are valid on the channel UI (see
right). Changing the I/O is simply a matter of changing the selector variable.

Applications Page

• List Manager allows the system to manage lists of data that can be processed via
scripting. This release includes support for CanMessageInfo, which lists all CAN
devices on the bus and their addresses for doing complex CAN message routing.
Future releases will convert other lists to List Manager including DM1/DM2 processing.
For more information about managing lists, refer to the scripting function for
ListManagerXXX functions.

• Improvements to Monochrome menus.

o Menus no longer automatically save. Call MenuAccept to save changed values.
o You can call events on Select, Next and Previous allowing you to extend the
functionality of these buttons on specific menu items.
o Menu Styles now allow multiple widgets and properties to be bound to menu
data.
o Menu expressions now support local variables for accessing the current menu’s
temp value and last saved value allowing for more consistent/generic
expressions.

Section 78 00-02-0966
2015-07-09 -3-
Page Designer

• Property Consistency – Properties now use similar names and groups across all gauge
types to improve discovery and user experience.
• Advanced/Simple Mode – The screen designer now supports a simple (default) and
advanced view of object properties. By default, rarely used properties are hidden in the
property editor. To show them click the Show Advanced button to show more advanced
properties.

• Advanced Primitives – You can now specify your own primitives (text, rectangle, ellipse
and image) for the foreground or background of any widget. This allows you to create
complex effects with existing widgets such as custom backgrounds, day/night effects
and touch states without code.
• Smart Image Widget – You can now build a simple smart image widget to bind images
to a single object container. This performs better than using visible conditions on
separate widgets.
• Smart Rotary Gauge – You can now change the bound data value of a rotary gauge on
the fly. This is useful for configurations that have dynamic data or that receive one of
many different values in a specific UI location.
• Drop Shadows on Text – Rather than stacking multiple widgets or gauges, you can now
specify a drop shadow with color and offset properties. These perform faster and are
more consistent than multi-gauge stacking.

Library Page

• Predefined Curves – You can now specify an expression instead of a set of points for
curves on monochrome displays. This is useful for creating curves that reference
variables.
• I/O Definitions – You now build analog and resistive I/O definitions in the library. This
allows you to reuse them as well as map them to I/O channels on the fly.
• Customer Extensions – This tab allows customers to add their own files to the
configuration. Customer specific extensions (custom applications created for specific
customers) will be included in this tab and be part of the configuration install.

Programming Page

• Include ID in Programming – This checkbox on Variable and Events ensures that the
item includes its readable name for use in programming/debugging.

Section 78 00-02-0966
2015-07-09 -4-
 • Shared Enumerations. Variables can now share enumeration definitions. This is useful
when you have multiple variables that have the same values for use in Smart Gauges
and Menus.
• Enhancements to Variables
o Configurable Timeouts – Variables can now be configured to NEVER go invalid.
You can also configure the timeout of a variable from 0 to 30 seconds instead of
using the hard coded 5 second timeout.
o Save Values – You can now specify the persistence of a variable:
DoNotSave: Non-Saved variables.
SurvivesPowerCycle: Saved based on actions.
SurvivesUpgrade: Variables that are saved during upgrade.
This feature is only supported on specific hardware in this release.
• Debugging features
o Debugging Console – The debugging console allows you to see events as they
occur. In addition, you can now print messages from scripting. Scripting print
messages will show in the debug console along with events.
o Remote Diagnostics Console – This console allows you to get a semi real-time
view of variables on the display. This includes all variables that are defined in
the configuration. In addition, you can update variables, graph variables over
time and reboot the display remotely.
• Enhancements to State Machines
o State Machines now support complex actions. Complex actions take multiple
values or dynamic values (via expressions.) This allows you to do many complex
tasks (animation for example) without the need for scripting.
• Enhancements to Scripting
o Many bug fixes to script auto-complete processing.
o Better feature parity with state machines. New SendAction and
SendActionObject script functions allow you to call most actions without needing
to create an event. This improves performance and simplifies many
configurations.
o List Manager Support in Scripts and Actions. List manager is a new system
feature that lets us maintain lists in a central location similar to Strings and
Number variables. These lists can then be controlled with a single ListManager
interface using actions and/or scripting.
o New String Functions. Support for FindString, SubString, StringToDouble and
StringToInt functions.
o Support for System Objects. A number of new system objects have been
defined that you can use in scripting including:
 CANAddressInfo – Holds addresses that are on the CAN bus. Use List
functions to read this data.

Section 78 00-02-0966
2015-07-09 -5-
  CANMessageBuffer – Used to receive custom CAN data from a Free
Form CAN message. Provides the ability to read and write the data in
various data types including int, float and string.
 ScreenAlphaData – Allows you to send an animation message to the
screen. This message allows you to animate the change of Alpha
(transparency) values of screen objects.
 ScreenColorData – Allows you to send an animation message to the
screen to animate color.
 ScreenPositionData – Allows you to send an animation message to the
screen to animate the position of an object.
 ScreenRotationData – Allows you to send an animation message to the
screen to animate the rotation of an object.
 ScreenScaleData – Allows you to send an animation message to the
screen to animate the size/scale of an object.

Hardware Specific Changes

• Support for MPC-10 Added.

• Murphy Standard Configurations have been upgraded to use the latest features and are
now included in the tool.

Section 78 00-02-0966
2015-07-09 -6-
About the PowerVision Configuration Studio®
The PowerVision Configuration Studio is a PC-based software program suite for configuring
the PowerViewTM Model PV3xx, PV4xx, PV7xx, HelmView TM and MPC-xx display units. The
program is a member of the MurphyNetTM Software Suite of display configuration tools. The
software interface enables users to modify the display to their own specific needs. In addition,
the software interface allows the user to customize specific items such as:
• Display interface content look (types of inputs, rotary and bar gauges with customized
bezels and markings, uploaded logos and machine graphics, integrated video, on-
screen text and a variety of other user-defined parameters).
• Easily selectable multiple languages, day/night toggles.
• Control over the sequence of operation.
• Diagnostic codes and graphic alarms linked to bitmapped or other data. In addition,
there are active/inactive color schemes to signal inactive gauges instantly.
• Easy-to-save updates that enable the user to create and test multiple configurations.
The PowerVision Configuration Studio generates configuration updates for the display units.
These updates can be transferred to the display unit by either a direct cable connection
between the PC and the display unit or by copying a configuration from the PC to a USB flash
drive and then connecting the USB flash drive to the display unit's USB port.

Section 78 00-02-0966
2015-07-09 -7-
Installing the PowerVision Configuration Studio
System Requirements
The following are the minimum system requirements necessary for the PowerVision
Configuration Studio Software:
Processor
• Dual Core
o Intel Core Duo, 2 GHz and above
o Intel Core 2 Duo, 2 GHz and above
• Single Core
o Intel Pentium 4, 3 GHz and above
o Intel Core Solo, 1.8 GHz and above
• 2 GB System RAM and above
• USB connection on the PC and compatible USB flash drive with FAT32 file system or a
direct connect cable
Monitor Requirements
• Color monitor with resolution of 1024 x 768 pixels or higher running 100% font scaling
Minimum Required Operating System Requirements
• Windows XP Professional – SP3
o Service Pack 3 installed
o Microsoft.Net Framework 4.0
Recommended Operating System Requirements
• Windows 7

Installation Instructions
The following steps walk the user through the process of installing the PowerVision
Configuration Studio software onto their PC or laptop. The instructions are presented in a
linear fashion and should be followed accordingly.
1. Download the software from the Murphy PowerVision Forum or insert the software CD
into the CD drive of the corresponding computer.
2. Open the directory and double-click the MSI (Microsoft Installer) file.
3. The software will download the selected files to the PC.

Section 78 00-02-0966
2015-07-09 -8-
PowerVision Configuration Studio Install

1. A window displaying the Murphy PowerVision Software License Agreement is

displayed. Check the box in front of the acceptance statement (I accept the terms of the
License Agreement). The agreement can be printed by clicking [Print]. When finished
click [Next].

Section 78 00-02-0966
2015-07-09 -9-
 2. Upon completion, click [Next]. A window is displayed asking for the installation folder
location. The user can select the default settings, and click [Next]. [Change] can also
be clicked to choose another installation destination.

3. The Confirm Installation window is displayed. Click [Install] to begin the installation.

Section 78 00-02-0966
2015-07-09 - 10 -
 4. The software begins loading on the PC. When it has completed, an Installation
Complete window is displayed. Click [Finish]. This completes the installation. The
PowerVision Configuration Studio icon on their desktop is displayed on the computer
desktop.

Section 78 00-02-0966
2015-07-09 - 11 -
USB to Ethernet Setup for Direct Connection to a PV450 or PV780
The quickest way to perform configuration development is to directly connect the display to
your PC. This is completed using Murphy part number 78090048. A programmer’s
development kit (Murphy part number 78090052) is available and includes all components for
development except the display unit. The display unit must be purchased separately.
Hardware Connection

1. Insert the Monoprice USB 2.0 LAN 10/100MBps Ethernet Adapter CD into the CD drive.
2. Connect the USB to Ethernet adapter to the USB slot in your PC. Windows should
locate the correct driver automatically. Otherwise follow the bulleted step below.
• Click Open Folder to View Files on the pop-up window. Select the appropriate folder
for your operating system to install the correct driver.
3. Beginning in PowerVision 2.7, you can use Auto Discovery to connect your display.
The following steps will guide you through ensuring Auto Discovery works. If you are
unable to configure Auto Discovery, please follow the instructions in the Addendum
which describe how to manually configure your network. Please refer to the section at
the end of this document titled Advanced Ethernet Setup.
Auto Discovery is designed to simplify the connection between PowerVision and
Ethernet displays. In addition, Auto Discovery allows you to connect multiple
displays to your PC via an Ethernet Switch or Hub.
4. Open a Configuration – The first time you open a color display configuration in
PowerVision 2.8, PowerVision MAY attempt to open a connection for auto discovery.
When this occurs, you may be prompted to allow this communication with a dialog
similar to the following. Please check Public Networks and Allow Access (shown below)
to allow an exception.

Section 78 00-02-0966
2015-07-09 - 12 -
 NOTE: PowerVision does NOT send any of your data to the display or
Internet when using Auto Discovery. It only broadcasts a request to the
display to find your PC and receives the address back to allow it to
connect.

5. Once Auto Discovery has found a display to connect to, it will display the device’s
information on the Configuration tab of PowerVision. It will look similar to the following
image.

6. If Auto Discovery does not work, please refer to Addendum B for how to set up a static
IP for your display and PC. Also you may wish to turn off the Auto Discovery feature of
PowerVision. This is done by clicking the About button on the top right side of the main
toolbar and deselecting the Enable Discovery checkbox in the Application Settings tab.
NOTE: See Addendum C for help with troubleshooting common problems
connecting to displays.

Section 78 00-02-0966
2015-07-09 - 13 -
ECOM Device Setup for Direct Connection to a PV350/380

1. Install the ECOM device driver for a 32- or 64-bit Windows installation.
2. Connect the ECOM dongle.
3. Connect the display to the harness, and turn it on.
4. Open the configuration file (i.e., PV350, PV380).
5. From the Configuration Page, select Communicate over: Use ECOM Conduit.

Section 78 00-02-0966
2015-07-09 - 14 -
 6. Click on Edit Connection Settings.

NOTE: If only 0 shows in the ECOM Serial Number field, the ECOM is not
connected properly, and an error message will appear as shown above.

If the ECOM is connected properly, a serial number will appear as shown below:

7. Select the ECOM Serial Number and select OK. When the ECOM Serial Number is
selected, this line will change from Not Connected to [Type of Hardware] Connected.

Section 78 00-02-0966
2015-07-09 - 15 -
 8. Select Tools -> Create Full Install

9. Click Load Configuration. After configuration loads completely, the display will
automatically reboot with the new configuration running.
10. Save to Disk. This saves a configurationFull.gciBin file to the selected disk which can
be loaded via the PowerVision Field Programming Kit using the ECOM dongles.

Section 78 00-02-0966
2015-07-09 - 16 -
PowerVision Configuration Studio Software Overview
This section provides instructions for launching the PowerVision Configuration Studio
Software, identifies the features available and describes the general navigation available to the
user.
Launching the Application
The following steps will take the user through the steps for launching the PowerVision
Configuration Studio Software.

1. The user can either click the PowerVision Configuration Studio Software icon on their
desktop or click the Windows Start button and select the program from the All Programs
list.

NOTE: If you haven’t entered a product key, the Product Registration

screen is displayed.

Key ID
The first time the software is run after installation, the following screen is displayed.
Enter the product key on this screen.
NOTE: No key is needed to operate in Trial mode.

NOTE: To get a product key, please contact your local sales

representative, or call +1 918-317-4100 and press 1 for inside sales. Be
prepared to provide the following information:

Section 78 00-02-0966
2015-07-09 - 17 -
  Company Name
 Main Contact Name
 Phone Number
 E-mail Address
Click [Trial] if you want to evaluate the software. In trial mode, all the configuration
functionality is available with the following exceptions:
o Create – Create a package file with the currently opened configuration.
o Load – Load a package to your device.
o Full – Create full install package that includes application, configuration and
operating system ready for deployment.

2. Upon selection, the opening window is displayed.

Section 78 00-02-0966
2015-07-09 - 18 -
The Opening Window for Displays
There are several buttons positioned across the top of the opening window. When selected,
these buttons enable navigation and use of the application.

NOTE: When the window is first accessed, the only active buttons are
New and Open. Once a configuration has been created or opened, the
other buttons become active and are available on every main window of
the program.

The buttons and their individual functions are as follows:

o New – Once selected, this button enables the user to initiate the creation of a new
configuration based on the configurations included with the PowerVision Configuration
Studio or a pre-existing custom configuration.
o Open – After the configuration is created, click this to view, configure or delete the
created example.
o Save – Upon selection, this button saves all changes that have been made to a
configuration.
o Save As – This button enables saving the configuration file as another name.
o Close – When selected, this closes the configuration being worked on.
o Create – This button generates the configuration data used by the display unit. Create
acts as a compiler and prepares the user-configured changes made to the standard
examples for downloading to the device.
o Load – This button downloads a generated configuration directly to the display unit via
the direct connect, USB/Ethernet cable.
o Tools –
o Validate Configuration – When a configuration has been opened, select
Validate Configuration to check for common errors and missing data.
o Create Full Install – When this is selected from the tools menu, it generates a
full installation package (application, configuration and operating system) ready
to deploy on a production line.
NOTE: The only thing the package does not include is the loader.
The loader comes up when the display is started. The loader
included with this software is compatible with any 2.3 loader
released after July 2013 so you do not have to update the loader
on existing displays in order for them to be compatible with 2.7.
NOTE: When a color display full install package is generated, it is
named update-full.tar.gz. (See Addendum: How to Install a
Configuration from a USB Drive.)
NOTE: When a monochrome display full install package is
generated, it is named configurationFull.gciBin and can be
installed with the PowerVision Field Programming Kit 2.7 version.

Section 78 00-02-0966
2015-07-09 - 19 -
 o Load Full Install – When Load Full Install is selected from the tools menu, it
loads the complete configuration and all of its components onto the device from a
computer.

o Create Bootloader – (Monochrome display only) – When Create Bootloader is

selected from the tools menu, it generates a bootloader installation package
ready to deploy on a production line.

o Load Bootloader – (Monochrome display only) – When Load Bootloader is

selected from the tools menu, it loads the bootloader onto the device from a
computer.

o Export Configuration Components – This function is used to export specific

components of the current configuration to a file that can be imported into
another configuration file. It is discussed later in Reusing Applications.

o Import Configuration Components – This function is used to import

components from a file generated in another configuration. It is discussed later in
Reusing Applications.

o Export/Import Language Strings – The Export/Import Language Strings feature

enables the user to either export or import all of the language strings used within
the PowerVision Configuration Studio software to an Excel file or to a tab-
delimited file. It is discussed later in International Language Support.

o Global String Editor – The Global String Editor feature enables the user to
change strings on pages, menus, variables and other items.

o Select Parameters from Recording – The Select Parameters from Recording

option allows you to read a CANCapture or CANAlyzer recording to find the
device addresses and the PGNs that were recorded. These addresses and
PGNs can then be used to select J1939 parameters for the devices in the
configuration. Addresses that are selected but that are not in the configuration
will be added.

o Search Configuration – The Search Configuration opens a dialog to search for

variables while being able to filter the type of variable which is searched.

o Remote Diagnostics Console – The Remote Diagnostic Console opens a

dialog which can read and set variable from the attached remote device. This
dialog is used for debugging an active configuration.

Section 78 00-02-0966
2015-07-09 - 20 -
 o Search Unused Items – The Search Unused Items option opens a dialog which
finds all unused items. If you say no to deleting all of the items, a list of unused
items will be presented in the Console for individual inspection and deletion.

o Console – The Console button enables the user to view a list of events that have
occurred since the last configuration save. The validation system runs like a compiler.
When the system encounters an error, it stops, and the error is displayed in the Event
Log Console.
The errors give a hint about what’s wrong with the configuration. For the most part,
when you double click on the error, it will take you to the specific area of the problem so
it can be fixed before it’s loaded on the device.
o About – The About button brings up a small dialog box that displays general
information about the PowerVision Configuration Studio software. The following goes
into more detail regarding these buttons and their functionality:

o Copyright Information – Provides information about the software.

o Extensions Manager – Used to show and hide hardware.

Section 78 00-02-0966
2015-07-09 - 21 -
 o Application Settings – If there are any settings specific to portions of the
program that can be altered, they are displayed in this window.

Section 78 00-02-0966
2015-07-09 - 22 -
Field Description
Grid Size Grid size defines the size of the lines on the page designer when
the grid button is turned on.
Image Button Background The Image Background defines the color of all image buttons in the
configuration tool.

Default Data Directory Click this link to change the database address.

Set To Default Folder Click this link to set the default database folder.

Check File Associations Checking this box enables the user to open PowerVision by double
on Setup clicking on a PowerVision Configuration Database.

o Release Notes – This lists all the new features in this release.

Building Your First Configuration

The previous Overview section explained installation and identified the buttons, some of the
dialogs and the pull-down menus in PowerVision. These menus and dialogs have more details,
but it makes better sense to explain the menu details as they are being applied to a Display
Application. This section uses PowerVision to build an Engine Monitoring Display Application
from a blank configuration.

For your first introduction to PowerVision, you need to start with the most common and basic
(blank) configuration. When you want to create a Word document, you use a Word Blank
Document which has a template and defines the paper size, margins and style formats, but
otherwise is completely blank. Likewise, PowerVision has a Blank Configuration for color and
monochrome displays and other devices. The Blank Configurations are locked so they cannot
be changed, and they remain a good starting point. The locked Blank Configurations can be
opened, but they need to have a new name to save any changes.

For your first application, you want to do something simple such as create gauges on the
PV380 display, then make them work. In building the new application, you will inspect all of the
Tabs and use the necessary features from each Tab page. This build is a quick introduction to
identify what you minimally need to create a workable configuration. Later in this document, it
will discuss the deep dive into all of the menus, features and nuances. At this point a deep dive
is too much information for building a display application. Simply load it on the hardware, then
see that it works.

Start by creating a new blank monochrome configuration by clicking the [NEW] button at the
top left. It opens the following dialog. In Section A, select the blank configuration you want to
use (one for monochrome displays). You have to rename the locked configuration because it
will not be saved with that name (for example, name it PV380 TestConfig). This blank
configuration supports a particular device, and if it is not the device you are using, you will

Section 78 00-02-0966
2015-07-09 - 23 -
need to change it. Each device has a unique set of features (I/O, CAN buses, Serial Buses,
etc.) so with PowerVision to access these features, you only need to select the device. Lastly,
PowerVision can update embedded features from an older configuration, so make sure the last
saved version is older than the current version of PowerVision. This dialog can see the last
saved version, and if it is newer than the current PowerVision version, it will generate an
opening error.

The default page your configuration opens to is the Configuration page. The green circled
items are provided and should be checked. The blue items are optional items that can be
added.

Section 78 00-02-0966
2015-07-09 - 24 -
First check that you are on the Configuration Page (1) where the current selection has the blue
bar over it. Next verify that the name of the configuration is correct (PV380 TestConfig(2)) and
that the configuration is set for the PV380 display (3). PowerVision can support other
languages, but for this example English (4) will be used. A unique Windows signature is
generated for this configuration (5) so that different versions can be identified. If the PV380
hardware is connected to the ECOM device, it will show what device (6) is connected. The
Version information for this PowerVision application is shown as Available (7) while the
Installed software on the connected device is also shown. If the loaders have different version
numbers, then you should do a Full build to update the embedded loader to the version.

Optionally, you should Title (8) this configuration so you can identify it in the Open dialog. Also
add a description and the latest changes at the top of the Description and Notes Field (9). This
information shows up in the Open dialog and could provide progress information to correctly
select the latest configuration. You need to press the [Refresh] button (10) once the target
hardware is connected so you can see how much memory is available for screens, strings and
program space (11). Once the memory is gone, it will be the limit of what can be programmed.

This configuration’s purpose is to put up the Engine Speed, Engine Coolant Temperature and
Engine Oil Pressure. In this particular case, there is a Diesel engine which has an Engine
Control Unit (ECU) at Source Address 0 which broadcasts these parameters over the CAN
bus, and it is the display’s job to read these messages and display them on a monochrome
screen. You need to be on the Connections Page (1) to implement the CAN bus messages.
The PV380 has a CAN Port 1 and a RS-485 Port 1 where it receives data. On the CAN bus,
this PV380 display can transmit data as the single Transmit Device, but that is not necessary
(and if you selected the Transmit Device you would see that no messages are identified or
available to be transmitted). There are other devices on the CAN bus which are the Engine
Device and Transmission Device (plus you can add any other devices you need). The Engine
Device has the default Engine Speed message.

The Protocol of the Engine Device is J1939 (3), and it broadcasts from a static Source Address
of zero (4). This ECU also transmits Engine Coolant Temperatures and Oil Pressures. Getting

Section 78 00-02-0966
2015-07-09 - 25 -
all three of these CAN messages would provide the required gauge data. You need to press
the [+] button (5) to open a dialog where we can select the gauge data (6), then PowerVision
does the rest to identify the message (via the PGN value) and provides a parameter name
(Engine Coolant Temperature and Engine Oil Pressure) for our gauges to use.

If you go to the Application Page, you will see a list of Standard and Configurable Applications
which are already built in. You are using the J1939 Port Manager to get the ECU data, but it is
already configured correctly here. You are also using the Screen Application to provide a
display update, but it, too, is configured correctly. Nothing needs to be done on this page.

Next, go to the Page Designer Page and use the toolkit to put the gauges on the screen. First,
note that you are using the Main Layer to save your gauges. The Pop-up Layer should be used
to place Pop-up menus or Diagnostic Messages on top of the Main Layer. Also note that the
Main Layer and the Pop-up Layer can have multiple Views. On power up, a splash screen will
be shown, then the Screen Application puts up the Main Layer: Main View. If you press a bezel
button, you can switch to other Views on the Main Layer such as the User Setting View or
System Information View. These views are not being created because they are not necessary
for a simple configuration.

Like any other drawing tool, you select a drawing entity from the Toolkit Tab and place it on the
Main Layer: Main View. Use the Properties panel to update the gauge properties such as
position, ticks, angles and any other properties. The green circled drawing objects have been
added to the Main Layer: Main View.

Section 78 00-02-0966
2015-07-09 - 26 -
If you switch to the Pages Tab, you will see the Main Page, and you can rename it to Gauge
Page or copy the page (where right clicking shows the options). Opening the page will show
Folders for the Gauges and Labels which are on the screen. Folders are very useful for
collecting common drawing elements and improve the page organization.

You can press the [Create] button and then press the [Load Configuration] button on the
Output File Complete dialog after the compilation has completed. After a minute of
downloading, the PV380 will be loaded with the configuration and starts execution. Get a
device to send CAN messages at a periodic rate, or connect it to an electronic engine’s CAN
bus to make the needle and bar gauges move. From this example, it takes very little effort and
programming skill to get a PowerVision Configuration working.

To complete this example, switch to the Library Tab and the J1939/NMEA Parameters Pane.
Then highlight the PGN equal to 6144, and in the Parameter Pane, highlight the Engine Speed
as shown below. The Library Tab provides useful information that can be used to set up the
gauges. In this example, we find out that the Engine Speed in the J1939 message is from 0 to
8031.875 RPMs. Therefore the gauge should be set within this value to be useful.

Section 78 00-02-0966
2015-07-09 - 27 -
Extremely useful is the Programming Tab which has variables, events, strings, scripts, state
machines and activity diagrams. This tab is where the program logic resides. The display
contrast was too low on the initial load, so the default was increased to 165, which makes it
more readable. This is all you need to make a configuration to monitor ECU values.

Section 78 00-02-0966
2015-07-09 - 28 -
Button to Create a New Configuration

The window is divided into two sections: Base Configurations (Section A) and Base
Configuration Info (Section B).
Section A: The Base Configuration displays the available blank templates. The user selects
one of the templates, assigns it a name and then modifies it to fit their individual needs.
Section B: The Configuration Info section displays detailed information about the selected
template. The table below describes each of the fields.
Field Description
Enter a name for your new This field is where the user enters a name for the new
configuration configuration. The name can be anything the user wants. It is
suggested that the name concisely identify the configuration.
Configuration Name The name of the configuration (read-only) assigned by the creator
of the base configuration.
Configuration Description This read-only field provides the user with a description of the
configuration. If the configuration is copied from one of the Murphy
Standard templates, the field will display which template was used.
Device Name This field displays the name of the device.

Status This field enables the user to see the current status of this
configuration (editable, baseline, etc.).
Version Software version used last to save the configuration.

Section 78 00-02-0966
2015-07-09 - 29 -
Open Button to Access a Configuration
The Open a Device Configuration window provides the opportunity to open an existing
configuration. In addition, you can import a configuration from your computer where it is saved
with the *.murphyConfig extension.

There are several buttons which control this dialog.

A. Delete Configurations: When a configuration is selected and this button is clicked, a
warning is generated that this configuration file will be deleted. Pressing the [Yes] button
will delete the file, and pressing the [No] button will cancel the delete operation.
B. Import MurphyConfig File: When clicked, this button opens a Windows Open File
dialog that can be used to find a Murphy Configurations file on the current computer or
network. When the Murphy Configuration is selected, it will be imported into the DB
folder for this PowerVision version, but it will not be updated to the current PowerVision
version. To open the file the [Open] button is used, then the configuration is updated to
the current PowerVision version.
C. Open : When a configuration is selected and this button is clicked, the configuration is
loaded into PowerVision.
D. Cancel : When clicked, this dialog window will close.
NOTE: A 2.2 configuration cannot be opened by the PowerVision
Configuration Studio Software v2.5.

Section 78 00-02-0966
2015-07-09 - 30 -
Murphy Standard PV450: Configuration Tab
The Murphy Standard PV450 locked configuration was opened from the Open dialog after the
Configuration Tab page is displayed. Within this window, one controls the setup of this
configuration file.
The Configuration Properties window is divided into four main sections: Configuration General
Settings (A), Configuration Logos (B), Description and Notes (C), Event Log (hidden in
console) and Data Size (D).
NOTE: To display the event log, click the [Console] button, and it will
open a text window on the bottom with time-stamped events. Click the
[Console] button again to hide the event log.

The following defines the fields and user options when working with the configuration tool.

Configuration Properties
The Configuration Properties section enables the user to set certain parameters in the
configuration file. The fields are auto-populated with system defaults and are user-configurable
unless the field is shaded. A shaded cell indicates the parameter cannot be modified. These
fields can be edited in languages other than English. (See Device Languages for more
information on supported languages.)
Section A – Configuration General Settings. This section uniquely identifies the configuration.
This section also contains two links: Configuration Languages and Edit Font Groups. Each of
these links now provides a pop-up to select the languages and the font groups. Use this
section to edit connection settings, manage backups and set up security.

Section 78 00-02-0966
2015-07-09 - 31 -
Field Description
Title User provided description or title for the configuration that appears
in the Open dialog.
Identifier The identifier is a string name for the configuration which remains
the same with different PowerVision versions. The identifier should
only be updated on the initial creation of the configuration.
Signature This is a Windows-generated unique file identifier which is created
every time the configuration is saved.
Communicate Over Defines the way in which the program communicates with the
device. Click Edit Connection Settings to display the following
screen, and edit TCP/IP settings or ECOM Settings.

Save the Last…Backups Provides a way to save backups of the configurations. Enter the
number of backups desired. The default value is 3.
Manage Backups From here, backups can be restored or deleted.

Continued on next page

Field Description

Section 78 00-02-0966
2015-07-09 - 32 -
Field Description
Multi-Language — Edit This section is broken into two panes: Available Languages and
Languages Selected Languages. The Available Language pane contains the
languages that are stored in your configuration file and available for
use but are not loaded when generating a Load file. The Selected
Languages are the languages that have been selected by the user
and readily available languages that can be used immediately.
NOTE: The languages listed do not include
translations from English for what is seen on
the screen. However, the configuration tool
allows a user to export the English strings,
have them translated and then import them
back into the configuration file.
What the tool provides is language support for entering and
modifying information in the fields in the languages that are
displayed in the Selected Language pane. Special characters
unique to the different languages are supported so that the user
can edit the fields in a language familiar to them. Editing can be
done in the chosen languages, and those languages are displayed
on the device when the configuration is downloaded.
For more information on exporting and importing strings, see
Export/Import Strings below.
A custom language can be created and translation strings can be
imported into the language file.
Use this section to add/remove languages from the configuration.

Continued on next page

Section 78 00-02-0966
2015-07-09 - 33 -
Field Description
Multi-Language — Edit The Font Group selection enables the user to view, edit, create or
Font Group delete font groups for the various languages that are supported by
the PowerVision Configuration Studio. Each language is presented
in a particular font style that can be changed by clicking [Select
Font] within the Font Groups window. The user can then scroll
through the available fonts to select the style they want to
associate with a specific language. In addition, they can import font
styles into the list or delete a font altogether.

Given the flexibility of the display units, any font group can be
selected for each individual gauge that supports text (text that
appears on the screen). In addition, font groups can be set to
change with the language setting.
Your choices on the right side of the screen under Group
Properties are the same as your Selected Languages. Font groups
can be added or deleted, and a particular font can be managed by
clicking either [+] to add a new group or [-] to remove a font from
the list.
The Select Font link located to the right of the language provides a
list of the fonts within that group for that language. To select a font,
highlight it, and click [Ok]. This adds the font to your default fonts
for the selected language.

Section 78 00-02-0966
2015-07-09 - 34 -
Field Description

A font can be added from the Windows fonts to the configuration

fonts by clicking [Import Font]. A font file can be imported from a
computer by clicking [Import File]. Fonts can be deleted from the
list by highlighting the font to delete and clicking [Delete]; click
[Cancel] to leave the screen without making any changes to your
fonts.

Edit Culture Strings Allows the user to change the AM, PM or separator character.

Edit Security Options Allows the user to enter a password or to select a secure gciBin file
for file storage.
Provides two ways to protect the device from unwarranted
configurations being installed:
• Use GCIBIN Files. This allows you to use a secure
configuration file without requiring a password.
• Password Protect. Assign a password to the configuration.
Once a password is assigned, the file will be saved as an
encrypted file and can only be loaded on the unit using the
assigned password. No other configurations can be loaded
onto the device without the assigned password.
Murphy assigned model number. Only specific model numbered
encrypted configurations can be used on a device with this type of
security.

Section 78 00-02-0966
2015-07-09 - 35 -
Section B – Configuration Logos. This section shows the logo that will be displayed when the
unit is turned on.
Field Description
Boot Logo This editable field shows the default logo that is assigned to the
configuration. The user has the ability to change this logo to suit
their individual needs. Simply upload a logo image into the image
library (see Image Library following this section for more
information), double click on an empty slot and select the uploaded
logo image.
Section C – Description and Notes. This is a free-form text field for the user to enter important
information about the configuration. This information will only be saved when the configuration
is saved.
Section D – Data Size. This section is a visual representation that indicates the amount of
space used for each of the listed elements. The checkbox at the bottom toggles between total
space and configuration size. Click the refresh link to update the memory allocation when you
are connected to the device.

Save Button to Store a Configuration

Pressing the [Save] button saves the modified configuration to the current filename in the
PowerVision DB directory. If the configuration is a locked configuration, the [Save] button will
be shaded and inactive.

Save As Button to Store a Configuration with a Different Name

Pressing the [Save As] button opens a dialog to rename the configuration, and a new filename
is provided if the current configuration name is locked. If one presses the [Create] button, the
new filename is stored in the current PowerVision version’s DB folder. Pressing the [Cancel]
button quits the configuration Save operation.

Close a Configuration
Pressing the [Close] button opens a dialog to save any modifications. If there have not been
any modifications to the configuration, the configuration will be dumped from PowerVision.

Select Target Hardware for a Configuration

Once a configuration is open, it will specify the target display or device next to the
Configuration’s filename.

Section 78 00-02-0966
2015-07-09 - 36 -
Pressing this [Target Hardware] pull-down menu will allow the user to change the target
hardware as shown in the following figure. Since the I/O of the target hardware changes from
device to device, there is a dialog which allows the user to coerce the current I/O channels to
ones which are available for the selected target.
The available hardware can change based on the PowerVision version. For example, obsolete
hardware such as the PV750 will only be available on earlier versions of PowerVision.

Edit in Language
The configuration can be edited in different languages; English, French, German, Spanish,
Italian, Japanese, Chinese, Brazilian Portuguese, Russian and Czech. This means that only
International strings will change to the selected language. For example, if one selects
Japanese, the Diagnostic Trouble Code can be edited in Japanese. None of the Window
menus or dialogs change to another language (or Japanese).

Section 78 00-02-0966
2015-07-09 - 37 -
Murphy Standard PV450: Connections Tab
Selecting the Connections Tab goes to a screen with multiple panes for the Module Setup and
its respective devices. There are two main folders: Communication Ports and Input/Output
Channels. These Ports and Input/Output Channels change based on the target device. For
this demonstration, the PV450 Murphy Standard will be used.
Module Setup
The Connections section contains four components: CAN Ports, Input/Output Channels and
Serial Ports. The CAN Ports relate to the ports on the back of the device and their user-defined
designations. The Input/Output Channels enable the user to connect analog, digital and
frequency inputs and outputs depending upon the capabilities of the display.
CAN Ports
When a CAN Port is selected, the following set-up sections become available:
CAN Port Setup
o Free Form CAN Messages
o Message Definition
o Variable Packing
o Message Visualization
Within each of these sections, the user will have the opportunity to configure the parameters to
fit their individual needs.

Section 78 00-02-0966
2015-07-09 - 38 -
The fields are as follows:
Field Description
View Pinout Displays a pop-up diagram of the pinouts for the selected device
model.

Name The name that has been assigned to the plug. This field is not
user-configurable.
Baud Rate This menu allows the user to select the baud rate at which the plug
will communicate. Your choices are:
• 10Kbps
• 20 Kbps
• 50 Kbps
• 100 Kbps
• 125 Kbps
• 250 Kbps
• 500 Kbps
• 800 Kbps
• 1 Mbps
Edit Address Ranges This field defines the range of source addresses that the plug will
attempt to claim before going into Listen Only mode. This is useful
if the user does not want the device to attempt to claim the same
addresses as other devices on the CAN bus.
Enabled If the user elects to check this parameter, it signifies that the plug
can receive/send CAN messages.

NOTE: The respective NMEA 2000 connection meets the hardware

specifications listed by NMEA 2000 standards (isolated power bus, among
other things). It is the suggested plug to use for NMEA 2000 devices and
must be powered externally with 12 VDC.

Section 78 00-02-0966
2015-07-09 - 39 -
Free Form CAN Messages
Free Form CAN Messages is a way to specify a CAN data message that can be sent or
received by the display unit. Use could be specified as CANopen requests for data, a
Proprietary CAN command to a controller or a CAN message to an external gauge.

The Frame ID is now stored in a variable for the name chosen which allows the Frame ID to be
changed within the code while running the script.

Section A: Contains a list of the Free Form CAN messages set up for this plug.
Section B: This section allows you to define the message header. In addition, you can now
specify an event to fire when the message is received and written to the database.
Section C: This section allows you to define filters and add parameters (variables). To define
a filter or filters, select an option other than Disabled from the Enable Filters drop-down list. For
transmit messages, if a filter is specified for a number of bits, those bits will be constant in the
transmitted message.
For a received message, the filter is applied to incoming messages that match the frame ID. If
the filter matches the specified bits to be filtered, the data is read in and applied to the variable
specified; otherwise, the message is ignored.
Section D: The message visualization at the bottom of the screen will show the mapping of
the filter and the data bits to the message.

Section 78 00-02-0966
2015-07-09 - 40 -
Field Description
Name Name of the message.
Message Type This can be Standard Frame Receive/Send or Extended Frame
Receive/Send.
Frame ID (hex) This is the frame ID specified in hex. 11-bit Frame ID for standard
frame or 29-bit Frame ID for extended frame.
Data Length (bytes) Number of data bytes.
Filter Length Length in bits for the filter. If disabled, there is no filter set.
Update Device Address If checked, the claimed address of the display unit will be used for
on Outbound Messages extended frame send.
Filter (hex) Value in hex for designated filter bits. For Standard Frame Receive
and Extended Frame Receive, incoming messages will be filtered
based on the provided filter value before the message is parsed
into variables. For Standard Frame Send and Extended Frame
Send, outgoing messages will have this value in the designated
filter bits with all the selected variables packed for this CAN
message.
Filter (bin) The corresponding value, in binary, based on the input in
Filter(hex) column.
Variable Variables available from the current configuration, such as user,
J1939 and NMEA variables. For Standard Frame Send and
Extended Frame Send, the value in the selected variable(s) will be
transmitted in the designated bit location. For Standard Frame
Receive and Extended Frame Receive, the data from the incoming
CAN message in the designated bit location will be placed in the
selected variable(s).
Big Endian Set if the incoming value is in Big Endian order. By default,
incoming values are interpreted using Little Endian byte order.
Start Bit Start bit in the CAN message for this variable.
End Bit End bit in the CAN message for this variable.
Message Visualization It shows the mapping of the filter and the data bits in the CAN
message.

Free Form CAN Message Transmit and Receive

Free Form CAN Parameters allow the users to transmit and receive CAN messages that
cannot be configured through the Library J1939/NMEA 2000 Parameters using the
PowerVision Configuration Studio software.

Section 78 00-02-0966
2015-07-09 - 41 -
The specified message below is an example of a Standard Frame Receive message. The
incoming message with Frame ID 0x18F00000 and filter as 0xAC708004 should be detected
on CANport1 with 6 data bytes. Bit 32 to 47 of this incoming message will be stored into a
system variable named SFF Rx Data.

Free Form Data Messages

A free form data message allows you to easily capture strings from a CAN message into a
String Variable (reserved string). This is needed when building complex systems that need to
send strings from one device to another, such as controllers or modules that report errors or
other diagnostic data.

This feature allows you to define a message’s start and continuation patterns and then handles
the complex logic necessary to parse the CAN traffic and place the data into a string. This
eliminates the need for scripting and other parse/concatenation logic to be defined in your
configuration.

This feature currently can only handle string messages which define a length and sequence
number in their message format.

Defining a message takes place in three steps.

1. Step 1: Define the Message PGN -> String.

Section 78 00-02-0966
2015-07-09 - 42 -
 NOTE: If picking Raw instead of String, the Data will be sent using a
CANMessageBuffer object to the Complete Event to allow the user to
process the message with a script.

2. In this step, we pick a string to write our message to as well as define the PGN which
will carry our string. If you need to use only a specific section of the PGN as your
identifier, you can use the PGN Mask to mask off specific bytes of the PGN. Optionally,
you can define an event which will fire when the string is completely captured and/or
when there is an error. An error occurs when the message reaches its timeout between
data packets OR when there is a sequence error. Finally, the timeout defines how long
between each packet the system will wait before an error occurs, and the system resets
to its waiting state.

Step 2: Define the Begin Packet. This section

allows you to define the data structure that
indicates the first packet of your string. This is
done by first defining a filter. The filter can be any
byte within the packet. If you wish to only filter on
a specific packet, you can use the filter to mask
only the bytes which are used for identification.
The Length byte indicates which byte of the
message contains the length of the string we are
receiving. The sequence byte allows you to
identify a byte which is used for order. For example, entering a 3 means the third
byte will hold the sequence number of the packet (00 or 01 for example). The data
start and end byte defines where in the message the string data is contained.

Section 78 00-02-0966
2015-07-09 - 43 -
 Step 3: Define the Continue Packet. For each
packet after the first packet is received, the system
will use the Continue Packet definition to identify if
the packet is a continuation of our string. Again, the
filter allows you to use a specific byte to filter the
packet, if needed (not common), and a mask is
provided to specify the specific bytes that are
filtered. The sequence byte is used to continue the
sequence number tracking to ensure we receive all.
For example, entering a 3 means the third byte will
hold the sequence number of the packet starting at
the second packet (02, 03, 04 etc.). Finally, the
data start and end byte define where in the
message the string data is contained.

J1939/NMEA 2000 Parameter Mapping

There are two areas that detail the CAN devices: Device Setup and J1939/NMEA 2000
Parameter Mapping. Each device added to a plug will have essentially the same type of
information and options as the screen shown below for Engine Device. The parameter
selection lists will be specific to the device and protocol.

Section 78 00-02-0966
2015-07-09 - 44 -
Field Description
Variable Name The user-assigned name of the device.
Request Specific Address When checked, this sends a request with the specific address of the
device for any request-only PGNs that are mapped to the device.
Device Name The name of the device. This field is not directly editable. To edit the
name, click [Edit Name]. This provides an area to not only edit the name
but also edit the translations for the name as well.

Request Specific Address on When checked, this causes a DM2 request to be sent to the specific
Fault address of the device instead of a global request.
Protocol Choices are:
• J1939
• NMEA 2000

Route Data to PVA Gauges When checked will send data to any connected PVA gauges.
Address For PVA gauges, there are two address sets: 0 and 1. This field selects
which address range to associate with the device.
Address Type If J1939 is selected as the protocol, the choices are:
• Static Address
• Function Address
• Function Instance Address
• System Address
• System Function Address
• System Instance Address
If NMEA2000 is selected as the protocol, the choices are:
• Static Address
• Class Address
• Class Function Address
• Class Instance Address
Source Address Address of the data source.

Source Override The location for the source override.

Section 78 00-02-0966
2015-07-09 - 45 -
Field Description
J1939 Mapped Variables Click [+] to add parameters from a checklist. If you have selected J1939
as your Protocol, the list will contain J1939 Parameters. If you have
selected NMEA 2000 as your protocol, the list will contain NMEA 2000
parameters. To remove a parameter, select it and click [-].

Diagnostic Trouble Code Mapping

Diagnostic Trouble Code (DTC) Mapping is used to configure DTC messages to a variable. To
add a DTC variable, select the device and then select the DTC Mapping tab. When a DTC is
mapped to a variable, the variable will be a 1 when the DTC is active and 0 when it is inactive.
This can be used easily with a screen object’s Visible Condition to show particular faults on the
screen with simply an image widget for example.

To add a DTC variable, click [+], and select a variable from the list displayed.

Section 78 00-02-0966
2015-07-09 - 46 -
An auto-created variable is added to the DTC Mapped variables list for that device. If the auto-
create option is not selected then an existing variable can be selected.

Transmitting Diagnostic Messages (DM1)

New for PowerVision 2.8: Diagnostic Message (DM1) transmitting can now be done using the
Transmit Device of a CAN port. This feature is initially only supported on color displays.

DTC Mapping is done in the same way on the Transmit Device as shown above for other
devices with the addition of a Broadcast checkbox for each mapped variable. On the Transmit
Device’s DTC Mapping tab, add variable mappings for the desired DTCs, select the variable
and check the Broadcast checkbox for each mapped variable.

A new variable (Dm1.LampStatusForBroadcast) has been added for setting the Lamp Status
of the Diagnostic Message to be transmitted. Refer to SAE J1939-73 5.7.1.1 Malfunction
Indicator Lamp to 5.7.1.8 Flash Protect Lamp. The variable is a 2 byte value, example 04FF
hex is a warning Lamp Status.

Another new variable (Dtc.FaultConversionForBroadcast) has been added for setting the Fault
Conversion Method of the DTCs that are transmitted. Refer to SAE J1939-73 5.7.1.11 SPN
Conversion Method. 0 for Version 1, 1 for Version 2, 2 for Version 3 and 3 for Version 4.

When the values of the DTC mapped variables on the Transmit Device are non-zero, those
DTCs will be transmitted with the DM1 message on that CAN port. The value of the mapped
variable will be the Occurrence Count for its DTC.

Diagnostic Message Memory Mapping

Diagnostic Message (DM) Memory Mapping is used to configure the messages that are used
to read and write to device memory. The J1939 Memory Access messages, DM14, 15 and 16
are used to transfer memory with a device that is programmed with that support.
To create the memory mapping, select the device and select the DM Memory Mapping tab.

A B

Section 78 00-02-0966
2015-07-09 - 47 -
Section A: Add a message to map to the device memory in the area. When a message is
added, the system populates areas in sections B and C. Each area provided is editable to
specifically define the mapping.
Section B: DM14 Message Properties will be auto populated. Edit these properties. Messages
can be either read or write messages.
Section C: Add/Delete variables to associate with this plug.
Field Description
Name Name of the message.
Direction Read or Write.
Length/Number The Length/Number is limited to 32776.
Pointer (hex) Enter a pointer in this box. This number relates to the type of
pointer it is. It will either be a memory location or a spatial location.
Address Type Your choices are:
Memory
Spatial
Key/User Level This can be used to set up a password for access to the unit.
Encryption is not supported.
DM16 Variable Mappings Fields include:
• Start Byte
• End Byte
• Auto Create checkbox
• Mapped Variable

Input / Output Channels

New for 2.7:

• I/O Definitions – You now build Analog and Resistive I/O definitions in the library. This
allows you to reuse them as well as map them to I/O channels on the fly.
o To support changing the I/O channel
configuration on the fly, you can now
specify multiple analog I/O definitions
in the library. To switch I/O
definitions, you select the definitions
that are valid on the channel UI (see
right). Changing the I/O is simply a matter of changing the selector variable.

When a particular Input or Output Channel is selected by the user, a Settings section is
displayed to configure that channel. The settings available are specific to the type of channel
being defined.

Section 78 00-02-0966
2015-07-09 - 48 -
 NOTE: Each channel and the types of channels supported change per
hardware definition.

Basic Channels can be set up in this section. Basic Channels are Digital In/Out and other
single value and non-scaled channels. To enable a channel, simply map it to a variable.
Complex Channels use a Selector. This selector variable allows you to specify the channel
definition at run time by changing the variable to point to an appropriate channel from the
Library. The definition and mapped variable will be defined with the channel in the library set-
up screens.

Basic Channel Setup Section

Field Description
Name This field is non-editable and displays the name of the
corresponding input channel.
Selector Variable This is the name that will be used throughout the rest of the system
to refer to the channel. For instance, IO.Fuel Resistive will be how
Input Channel 1 will be referenced when assigning a variable to a
gauge, using the variable in a calculation, etc.

Section 78 00-02-0966
2015-07-09 - 49 -
Serial Ports
This section is used to set up and manage Modbus settings.

Field Description
Name The name of the serial port.
Protocol Your choices are:
• None (Raw Serial)
• PVA Gauge
• Modbus RTU Master
• Modbus RTU Slave
• Disabled
Enable Broadcast Enables the broadcast for the Modbus master.
Initial Values Fields include:
• Baud Rate
• Parity
• Stop Bits
Baud Rate Your choices are:
• 2400
• 4800
• 9600
• 19200
• 38400
• 57600
• 115200

Section 78 00-02-0966
2015-07-09 - 50 -
Field Description
Parity Your choices are:
• None
• Even
• Odd
Stop Bits Your choices are:
• 1
• 2

NOTE: The applications are defined in a separate document. Please see:

00-02-0965 PowerVision Studio 2.8 Application Reference Manual.

Section 78 00-02-0966
2015-07-09 - 51 -
Murphy Standard PV450: Applications Tab
Selecting the Applications Tab goes to a screen with multiple panes for the Configurable,
Standard and External Application. These applications are discussed in the Application
Reference Document and are shown here for completeness.

Section 78 00-02-0966
2015-07-09 - 52 -
Murphy Standard PV450: Page Designer Tab
Selecting the Page Designer Tab goes to a screen with multiple panes for graphics layers,
page views and widget properties. The Page Designer features are discussed in the Page
Designer’s Reference Document and are shown here for completeness.

There is an Image Library that is used primarily by the Page Designer widgets, but it can be
used in other pages to provide graphics like splash pages and backgrounds so it is included
here.

Image Library
The Image Library shows the images that are included and available to be used in a
configuration. This Image Library pop-up can be displayed anywhere in the Configuration tool
where images are selected such as boot logos, image widgets and DM2 screens. The image
library is unique to the configuration.

Section 78 00-02-0966
2015-07-09 - 53 -
Button Description
Import Import images from the computer. When pressed, a browser window is
opened from which to navigate to the desired image. Click [OPEN], and the
selected image is added to the library.
Export Export images from the library to the computer. When pressed, a browser
window is opened to navigate to the desired location for storing the image.
Replace Replace the selected image in the library with an image from the computer.
When Replace is selected, a browser window is opened from which to
select a targeted image. When an image is located, selected and opened, it
is replaced in the library and in the configuration anywhere the original
image was used.
NOTE: Be aware that this will replace every instance of
the image in the current configuration.
Restore Restores the selected image to its original state prior to any changes that
might have been made since the Image Library window was opened. When
the [OK] is pressed to close the Image Library window, all changes to the
images are saved.
Duplicate Duplicates the image in the library.
Delete Deletes the selected image from the library.
Clear Selected Clears the image from the selected item in the configuration.
Image

Section 78 00-02-0966
2015-07-09 - 54 -
Image Editing Tools

Field Description
Name The image name.

Colorize This allows the user to blend color with their image. For example, if
there is a white icon, red can be blended with it to make the icon
red.
Optimize This checkbox is used for images that have color gradients (fade
from one color to another). It optimizes the image for the 16 bits the
display uses.
Dark/Light Background Mode ̶ These buttons allow the user to view images with low or high
contrast backgrounds, which is useful for images with white-on-white or black-on-black
graphics.
NOTE: When [OK] is clicked, changes are applied to the Image Library.
However, [Save] must be clicked for the changes to be saved to the
configuration.

Section 78 00-02-0966
2015-07-09 - 55 -
Murphy Standard PV450: Library Tab
Introduced New in PowerVision 2.7:
• Curve Editor – You can now specify an expression instead of a set of points for Curves
on monochrome displays. This is useful for creating curves that reference variables.
• I/O Definitions – You now build Analog and Resistive I/O definitions in the library. This
allows you to reuse them as well as map them to I/O channels on the fly.
• Customer Extensions – This tab allows customers to add their own files to the
configuration. Customer specific extensions (custom applications created for specific
customers) will be included in this tab and be part of the configuration install.

The Library Tab has sub-tabs used to set up J1939, NMEA2000, as well as DTCs, Pre-defined
Curves and Unit Conversions.
• J1939/NMEA Parameters – Data from the J1939 or NMEA devices. Data is specified to
the J1939 and NMEA standards. These variables will have a prefix as J1939 for the
J1939 device or NMEA for the NMEA 2000 device in the Variable selection list.
• DTC Setup – Specifies DTC that will be displayed with specific text and/or excluded for
specified J1939 DTCs.
• Pre-Defined Curves – Curves are defined by a polynomial expression up to the third
order. Can also be fit based on X/Y points. Curves can be used for scaling the value
based on a non-linear expression. In addition, the Channel can use a Selector Variable
to select which curve will be used at runtime to change the selected I/O for
configurations which need to change the Channels connected device.
• Unit Conversion – Lists all the units and conversions defined in the configuration.

The Library sub-tabs are shown below.

Section 78 00-02-0966
2015-07-09 - 56 -
J1939/NMEA Parameters
The sub-tab complies with the J1939 specification (SAEJ1939).
http://www.sae.org/stadarddev/groundvehicle/j1939a.htm
The device complies with the NMEA specification (NMEA 2000): http://www.nmea.org
The parameters that come with the configuration tool are from both J1939 and NMEA 2000
standards. Configuration Tool users may add or remove standard or proprietary PGNs with
parameter information as needed. If a PGN is set up to be requested, the device will generate
the request for that PGN according to the protocol chosen only when mapped to a CAN
device.
The device supports NMEA 2000 parameters over a J1939 CAN interface, so a port can
support NMEA 2000 and J1939 data at the same time. If a parameter is marked as a fast
packet, the parameter is expected to be sent in compliance to the NMEA 2000 fast packet data
transfer method. This is required to be checked if the data is sent in compliance with the fast
packet method so that the device can parse the data from the NMEA 2000 message correctly.
If more than eight bytes of data are defined for a PGN and the Fast Packet box is not checked,
the display will assume the parameter data is being sent using J1939 multi-packet formatting
(see J1939-21 section 5.10.3).

Field Description
PGN Parameter group number for this set of parameters.
Description Description of the PGN to receive.
Rate The repetition rate of the PGN broadcast by CAN devices. It may
be defined by J1939, NMEA 2000 or the user. For PGNs that are
required to be requested, place zero for repetition rate.
Measured in ms (milliseconds, 0.001 seconds).

Section 78 00-02-0966
2015-07-09 - 57 -
Field Description
Priority The priority of the PGN to receive.
Priority may be defined by J1939, NMEA 2000 or the user. It sets
the importance value of the message from 0 to 7 (0 = highest
priority). It is used for transmit devices.
NMEA Defines if the parameter is NMEA 2000. Shorthand for NMEA
2000, a combined electrical and data specification for
communication between marine electronic devices.
Instance ID When the NMEA box is checked for a PGN, a link will be displayed
in the Instance ID column. Clicking the link presents a form
allowing configuration of the NMEA Instance ID properties
(Instance ID, Start Bit/Byte, Bit/Byte length).
Request Request defines whether the message has to be requested by the
device (e.g., Ignition Timing 6 is a request message). If this is a
requested PGN, then click on the checkbox to enable a request for
this PGN.
Fast Packet Checking this box tells the display to interpret the PGN data using
NMEA 2000 fast packet formatting. If this box not checked, the
PGN data is interpreted using J1939 multi-packet formatting.
NOTE: This property only matters if there are
more than 8 bytes of parameter data defined
for the PGN.

Parameter Mappings
The Parameter Mappings that come with the configuration tool are from either J1939 or NMEA
2000 standards. Configuration Tool users may add or remove standard or proprietary
parameters as needed.
Field Description
Parameter Type Parameter Type depends on the J1939, NMEA 2000 or user's
definition. Select an option using the drop-down menu.
Bit - Applies to NMEA 2000 standard or proprietary parameters.
Measured - Applies to J1939 standard or proprietary parameters.
Status – Applies to J1939 standard or proprietary parameters.
Signed – Applies to NMEA 2000 standard or proprietary
parameters.
Unsigned – Applies to NMEA 2000 standard or proprietary
parameters.
SPN (Suspect Parameter SPN defines the parameter within the PGN.
Number) SPN is defined by J1939.
Continued on next page

Section 78 00-02-0966
2015-07-09 - 58 -
Field Description
Start Byte The starting byte location for this parameter in its PGN as defined
by J1939, NMEA 2000 or users. J1939 multi-packet messages are
limited to 1785 bytes. NMEA 2000 fast packet messages are
limited to 223 bytes.
Start Bit The starting bit location for the parameter in the eight data bits
(1…8) of the start byte as defined by J1939, NMEA 2000 or users.
Byte Length The byte length of the parameter in its PGN message. The length
of the data is measured in bits.
For example, SPN 190 Engine Speed has a start position of the
fourth byte in its PGN with 16 bits data length. As a result, Start
Byte = 4, Start Bit = 1, Byte Length = 2 and Bit Length = 0 should
be input for this parameter, since 16 bits = 2 bytes.
Bit Length The bit length of the parameter in its PGN message. The length of
the data is measured in bits. Bit Length is limited to 7 bits. For 8
bits (1 byte) and above, Byte Length must be used.
When the data length is less than 1 byte, this field must be filled.
For example, SPN 899 Engine Torque Mode has a start position of
the first byte and first bit in its PGN with 4 bits data length. As a
result, Start Byte = 1, Start Bit = 1, Byte Length = 0 and Bit Length
= 4 should be inputted for this parameter.
If the data length is 1 byte or greater, users must fill in the data
length using the Byte Length field. For example, SPN 190 Engine
speed has a start position of the fourth byte in its PGN with a data
length of 16 bits. As a result, Start Byte = 4, Start Bit = 1, Byte
Length = 2 and Bit Length = 0 must be input for this parameter to
work correctly.
Name This is the name that is shown in the parameter list when mapping
a parameter to a CAN device. This name is also used when auto-
creating variables for parameters that are mapped to CAN devices.

Resolution Resolution of a parameter, as defined by J1939, NMEA 2000 or

users. This is the value that is multiplied times the raw data in the
message before the Offset is applied to get the value in the defined
unit.
For example, SPN 190 Engine Speed has resolution as 0.125
rpm/bit, according to SAE J1939-71. Since the unit is set to RPM
for this parameter, 0.125 is input as the resolution.
Continued on next page

Section 78 00-02-0966
2015-07-09 - 59 -
Field Description
Offset Unit refers to the base unit for the parameter based on the
provided resolution and offset, as defined by J1939, NMEA 2000 or
users.
For example: SPN 110 Engine Coolant Temperature is transmitted
with resolution 1 degree C/bit with -40 degrees C offset, according
to SAE J1939-71. Thus, unit C is selected with resolution set to 1
and offset to -40 for this parameter.
Unit Refers to the base unit for the parameter based on the provided
resolution and offset, as defined by J1939, NMEA 2000 or users.
For example: SPN 110 Engine Coolant Temperature is transmitted
with resolution 1 degree C/bit with -40 degrees C offset, according
to SAE J1939-71. Thus, unit C is selected with resolution set to 1
and offset to -40 for this parameter.
Min Value The smallest value in the selected unit for this parameter to be
shown as an active parameter. It may be defined by J1939, NMEA
2000 or users.
For example: SPN 110 Engine Coolant Temperature has a data
range of -40 to 210 degree C, according to SAE J1939-71. Thus,
-40 is entered as the Min Value.
Max Value The largest value in the selected unit for this parameter to be
shown as an active parameter. It may be defined by J1939, NMEA
2000 or users.
For example, SPN 558 Accelerator Pedal 1 Low Idle Switch has a
data range of 0 to 3 where 0 is Accelerator pedal 1 not in low idle
condition; 1 is Accelerator pedal 1 in low idle condition; 2 is Error;
and 3 is Not Available, according to SAE J1939-71. If the user
wishes to show text on gauges for all four different values, the Max
Value should be 3. If the user only wishes to show texts for 0 and 1
on gauges and inactive for other values, the Max Value should be
1.

Section 78 00-02-0966
2015-07-09 - 60 -
Diagnostic Trouble Codes (DTC)
This subtab enables the user to configure diagnostic message text, corrective action text
and/or drop for a particular Diagnostic Trouble Codes (DTC) for DM1 and DM2 only.
This area can also be configured to split the SPN and FMI strings. Please refer to the
PowerVision Configuration Studio Applications Reference Manual for details.

Field Description
SPN The Suspect Parameter Number (SPN) for the DTC.
FMI The Failure Mode Indicator (FMI) for the DTC.
Drop Check this box in order to exclude the display of the DTC and
ignore this fault. Uncheck this box to display the fault.
NOTE: Useful to ignore engine manufacturer nuisance codes. It is
used to encourage the user to use the engine manufacturer’s
instrumentation.
Light Override Override the received lamp status for this particular DTC. The user
can pick an option from the drop-down menu: default, red or
yellow. When it is set to default, the lamp status from the DM1
message will be used.
Message Diagnostic message text for this DTC. Clicking [Edit] will bring up a
Text Editor window that allows a different string for each language
in the configuration.
Corrective Action Corrective action text for this DTC. Clicking [Edit] will bring up a
Text Editor window that allows a different string for each language
in the configuration.

Section 78 00-02-0966
2015-07-09 - 61 -
Predefined Curves

• Introduced New in 2.7: Curve Editor – You can now specify an expression instead of a
set of points for Curves on monochrome displays. This is useful for creating curves that
reference variables.

This subtab allows the user to create a curve definition defined by a polynomial expression up
to the third order, which can also be fit based on X/Y points.

Curves allow the user to scale the input or output values based on a non-linear expression
rather than relying on simple linear expressions (using Variable Calculations).

Field Description
Name The defined name of the Curve.
Group The group into which the Curve belongs.
Selector ID The value that indicated this curve is in use.
Polynomial Order The highest order of the terms in the curve equation.
X Unit The Unit of the values on the X Axis (input).
Y Unit The Unit of the values on the Y Axis (output).
Coefficients The values used in the polynomial equation.
Fit Coefficients to Curve Generates an equation to fit the curve points rather than using
static coefficients.
Curve Points and Fit The points to use when auto generating the curve equation.
Curve

Section 78 00-02-0966
2015-07-09 - 62 -
Unit Conversion
The Unit Conversion subtab lists all the units and conversions defined in the configuration.
Additional units can be defined, if needed, by clicking the plus [+] button in the upper right-
hand corner of the Conversion Units panel on the left.
Some measurements can be read using different unit systems and/or multiple units of
measurement. For example, length can be measured in English units of inches, feet, yards,
miles or nautical miles as well as SI Metric units of conversion of centimeters, meters and
kilometers. For such measurements, all defined unit conversions will be displayed below the
Selected Unit section. New conversions can be added to this list by clicking the plus [+] button
in the upper right-hand corner of the Unit Conversion section.

The Conversion window will display for most of the units listed on the Units Conversion tab.
The fields for the Unit Conversion section are described as follows:
Field Description
Name The name of the selected unit.
Description This field contains the description of the unit that was selected.
To Unit Drop-down selection that enables the user to pick the selected
measurement that the displayed unit will be converted to.
Pre Addition Value Value to add to the unit before the multiplier is used.
Multiplier Multiplier to use to scale the unit.
Post Addition Value Value to add to the unit after the multiplier is used.
Comment Notes or description about this conversion.

Section 78 00-02-0966
2015-07-09 - 63 -
IO Definitions
The IO Definitions subtab lists all the sensor input curves. The Murphy Standard PV450 as a
legacy configuration does not support different sensor input curves, so this representation is
remedial. Additional units can be defined, by clicking the plus [+] button in the upper right-hand
corner of the IO Definitions.

The fields for the IO Definitions section are described as follows:

Field Description
Name The name of the selected unit.
Variable Name This field contains the name used to reference this channel data
input. The name can be auto created to correlate to the IO
descriptions.
Operation Mode The Analog inputs can be configured by software in several ways
and can even behave as digital input (0/1). The available inputs for
the PV450 are: Analog in: 0-5V; Analog in: 4-20mA; Analog in:
Resistive 400 Ohm pull-up; Digital in: 0-5V; and Digital in: 400
Ohms pull-up.
Sample Count Smoothing can be done by averaging a number of samples. This
variable specifies the number of samples which are averaged to
generate a value.
Sample Rate Multiplier to use to scale the unit.
Selected Curve A curve can be defined by samples or by an expression for a
particular sensor. Once the I/O curve is defined, it can be selected
and used to convert the I/O data into real values like temperature,
pressure, etc. This parameter identifies the I/O curve which is
used.

Section 78 00-02-0966
2015-07-09 - 64 -
Customer Extensions
The Customer Extensions subtab lists all the customer added files. The Murphy Standard
PV450 as a legacy configuration does not contain any Customer Extensions. Additional
customer extension can be added, by clicking the plus [+] button in the upper right-hand corner
of the Customer Extensions screen.

The fields for the Customer Extensions section are described as follows:
Field Description
File Data Select/Remove the file.
Type The file type of the selected file.
Name The selected File name.
Arguments (Application Only) Any argument(s) needed for the selected application.

Section 78 00-02-0966
2015-07-09 - 65 -
Murphy Standard PV450: Programming Tab
The Programming Tab has variable, event, scripts, State Machines and Activity Diagrams. The
Programming features are discussed in the Programmers’ Reference Document and are
shown here for menu completeness.

Section 78 00-02-0966
2015-07-09 - 66 -
ADDENDUM A
How to Install a Configuration from a USB Drive
For the PV450
1. READ ALL INSTRUCTIONS BEFORE CONTINUING!

2. Power OFF the display unit.

3. Insert USB drive with the configuration file into USB port.

4. Press and hold any button (continue to hold).

5. Power ON the display while continuing to hold the button a few more seconds then release.

6. Use the keys next to up/down arrows to find the desired file.

7. Use the key next to the right arrow to select and continue. (The right arrow turns green, press
again to confirm. Exit by pressing the key next to the red left arrow.)

8. When the installation is complete, a check mark is displayed in the middle of the screen.

9. The unit will reset itself automatically and boot to the new configuration.

To set up your network, follow the procedures below for Windows XP, Vista and 7 installations:
• Install PowerVision Configuration Studio software onto the computer.
• Connect the computer to the device.

ADDENDUM B
Configuring your display for a Static IP Address

Windows XP Installations:
1. Go to the computer Control Panel.
2. Go to Network and Internet Connections.
3. Go to Network Connections.
4. Install the USB-to-Ethernet driver software.

Section 78 00-02-0966
2015-07-09 - 67 -
 5. Right click [Your Local Area Connection] (the USB-to-Ethernet converters supplied will have
ASIX in the device name).
6. Select [Properties] from the right-click menu.

7. Select [Internet Protocol (TCP/IP)].

8. Click [Properties].

Section 78 00-02-0966
2015-07-09 - 68 -
 9. Select [Use the following IP address].
10. Enter the IP Address: 192.168.0.1.
11. Enter the Subnet mask: 255.255.255.0.
12. Click [OK].

Windows 7 Installations:
1. Go to the computer [Control Panel].
2. Go to [Network and Sharing Center].
3. Click on [Change adapter settings].

Section 78 00-02-0966
2015-07-09 - 69 -
 4. Right click on [Your Local Area Connection].

5. Select [Properties] from the right-click menu.

6. Select [Internet Protocol Version 4 (TCP/IPv4)].

Section 78 00-02-0966
2015-07-09 - 70 -
 7. Select [Use the following IP address].
8. Enter the IP Address: 192.168.0.1.
9. Enter the Subnet mask: 255.255.255.0.
10. Click [OK].

ADDENDUM C
Troubleshooting Common Connection Problems
A number of things can prevent being able to connect to a display. Below are some tips that may
help when connecting to a display that shows Connection Timeout or other similar errors in
PowerVision.

Switch to Auto Discovery: To use Auto Discovery, access the TCPIP settings as described in
Addendum B, and change the configuration to Obtain an IP Address Automatically. This adapter will
then auto assign itself an IP address that is compatible with the display. The correct configuration is
shown on the right.

Turn off Proxy Servers: Proxy servers can sometimes interfere with PowerVision communications.
To disable a proxy server, open the Internet Options item in Windows Control Panel. Then click Lan
Settings on the Connections tab. Here you can uncheck the Proxy Server option.

Section 78 00-02-0966
2015-07-09 - 71 -
Identify Conflicting Addresses: Sometimes other networks can conflict with PowerVision’s network
addresses. By default PowerVision uses 192.168.0.X to communicate with the display. If you have
an existing network that conflicts with this, you can either switch to Auto Discovery OR move
PowerVision to a different address by following the steps in Addendum B, substituting a different
Address (10.0.0.1 for example).
Please note that you will need to reconfigure your Configuration in PowerVision to use this address
as well. For example if you use 10.0.0.1 for adapter, you should use 10.0.0.2 for your configuration.
Changing this setting in PowerVision is done on the Configuration Tab by clicking Edit Connection
Settings.

Section 78 00-02-0966
2015-07-09 - 72 -
(THIS PAGE INTENTIONALLY LEFT BLANK)
(THIS PAGE INTENTIONALLY LEFT BLANK)