Lynxspring JENEsys Edge 534 User manual

www.lynxspring.com
JENEsys
®
Edge™534
USER GUIDE
1210 NE Windsor Drive
Lee’s Summit, MO 64086
[email protected]m
1 [phone]
© 2019 Lynxspring, Inc.
All Rights Reserved
Revised 2/1/2019
JENE-EG534-V2
Page 1 of 31
JENE-EG534

www.lynxspring.com
JENEsys
®
Edge™534
USER GUIDE
1210 NE Windsor Drive
Lee’s Summit, MO 64086
[email protected]m
1 [phone]
© 2019 Lynxspring, Inc.
All Rights Reserved
Revised 2/1/2019
JENE-EG534-V2
Page 2 of 31
Trademarks
Onyxx® and the Onyxx logo are U.S. registered trademarks of Lynxspring, Inc.
Lynxspring™ and the Lynxspring logo are U.S. registered trademarks of Lynxspring, Inc.
JENEsys® Edge™ is a trademark of Lynxspring, Inc.
Other brands and product names mentioned in this manual may be trademarks or registered trademarks of their
respective companies and are hereby acknowledged.
Copyright Notice
© 2019 Lynxspring, Inc.
All rights reserved.
This document contains proprietary information which is protected by copyright. No part of this document may be
copied, photocopied, reproduced, translated, or converted to any electronic or machine-readable form in whole or
in part without prior written approval of Lynxspring, Inc.
Disclaimer
NO WARRANTY. This technical documentation is being delivered to you AS-IS, and Lynxspring makes no
warranty as to its accuracy or use. Any use of the technical documentation or the information contained therein is
at the risk of the user. Documentation may include technical or other inaccuracies or typographical errors.
Lynxspring reserves the right to make changes in this document without prior notice, and the reader should in all
cases consult Lynxspring to determine whether any such changes have been made. The information in this
publication does not represent a commitment on the part of Lynxspring.
Lynxspring shall not be liable for incidental or consequential damages resulting from the furnishing, performance,
or use of this material.
This guide contains links and references to third-party websites that are not under the control of Lynxspring, and
Lynxspring is not responsible for the content of any reference material or linked websites. If you access a third
party website mentioned in this guide, then you do so at your own risk. Lynxspring provides these links only as a
convenience, and the inclusion of the link does not imply that Lynxspring endorses or accepts any responsibility for
the content on those third-party sites.
Lynxspring, Inc.
1210 NE Windsor Drive
Lee’s Summit, MO 64086
P 816.347.3500 F 816.437.0780
http://www.lynxspring.com

www.lynxspring.com
JENEsys
®
Edge™534
USER GUIDE
1210 NE Windsor Drive
Lee’s Summit, MO 64086
[email protected]m
1 [phone]
© 2019 Lynxspring, Inc.
All Rights Reserved
Revised 2/1/2019
JENE-EG534-V2
Page 3 of 31
Table of Contents
Niagara Documentation Addenda 4
JACE Start Up Addendum ...................................................................................................................................................................... 4
Platform Guide Addendum...................................................................................................................................................................... 5
JENEsys Edge 534 Startup procedure 6
Onyxx Network Quick Start 6
Configure the onyxxNetwork................................................................................................................................................................... 6
Add an onyxxNetwork........................................................................................................................................................................ 6
Discover and add Onyxx Devices....................................................................................................................................................... 6
Manually adding Onyxx Devices ......................................................................................................................................................... 6
Add Onyxx Proxy points ......................................................................................................................................................................... 6
Using online Discover to add Onyxx Proxy points............................................................................................................................... 7
Manually adding Onyxx Proxy points .................................................................................................................................................. 7
Onyxx Network Concepts 8
About Onyxx Network Architecture ......................................................................................................................................................... 8
About the Onyxx Network .................................................................................................................................................................. 8
Onyxx Network status notes .............................................................................................................................................................. 9
Onyxx Network monitor notes............................................................................................................................................................ 9
Onyxx Network tuning policy notes .................................................................................................................................................. 10
Onyxx Network poll scheduler notes ................................................................................................................................................ 10
Onyxx Network views ...................................................................................................................................................................... 11
N Device Manager ................................................................................................................................................................................ 11
About the Onyxx Device ....................................................................................................................................................................... 12
Onyxx Device properties .................................................................................................................................................................. 12
Onyxx Point Manager ........................................................................................................................................................................... 13
Onyxx Driver Point Manager usage notes......................................................................................................................................... 14
About Onyxx Driver Proxy points........................................................................................................................................................... 16
Onyxx Driver point types .................................................................................................................................................................. 16
Onyxx Driver Proxy Ext common properties ..................................................................................................................................... 17
Conversion types in Onyxx Driver Proxy points................................................................................................................................. 18
Scale and offset calculation (linear)................................................................................................................................................... 19
Non-linear sensor support................................................................................................................................................................ 20
Linear Calibration Ext ....................................................................................................................................................................... 22
BooleanInputPoint ........................................................................................................................................................................... 23
BooleanOutputWritable.................................................................................................................................................................... 23
CounterInputPoint............................................................................................................................................................................ 24
ResistiveInputPoint........................................................................................................................................................................... 25
ThermistorInputPoint........................................................................................................................................................................ 26
VoltageInputPoint............................................................................................................................................................................. 29
VoltageOutputWritable ..................................................................................................................................................................... 29
About the Mini USB Port 29
Onyxx Network Driver Plugin Guides 29
Onyxx Network Driver Plugin Guides Summary ..................................................................................................................................... 29
N Device Manager ........................................................................................................................................................................... 30
Onyxx Driver Point Manager............................................................................................................................................................. 30
Onyxx Network Troubleshooting 31

www.lynxspring.com
JENEsys
®
Edge™534
USER GUIDE
1210 NE Windsor Drive
Lee’s Summit, MO 64086
[email protected]m
1 [phone]
© 2019 Lynxspring, Inc.
All Rights Reserved
Revised 2/1/2019
JENE-EG534-V2
Page 4 of 31
The following are addenda to Niagara Documentation: docJaceStartup and docPlatform
JACE Start Up Addendum
Please note the following amendments to Niagara Documentation “docJaceStartup” in regard to the operation of the
JENEsys Edge 534. Referenced Niagara documentation is included in the installation of ProBuilder™ or Niagara
Framework® and is typically located in a directory on the user’s PC, similar to: C:\JENEsys\JENEsys-3.8.111\docs
Pg. 3 - IP Address:
The JENEsys Edge 534 is shipped with a default address in the range of: 192.168.1.12n, like the JACE-3E,
JACE-6E, JACE-2/6 series.
Pg. 6 – Preparing to commission a new controller (Step 3):
Attach the cable to the primary Ethernet connector.
Pg. 14 - Starting the commissioning Wizard (Step 5):
Please refer to the screen below:
Pg. 15 - Starting the commissioning Wizard (Step 8):
Please refer to this screen below:
Pg. 46 - System Shell:
The JENEsys Edge 534 System Shell will be accessible using the Mini USB port, rather than an RS-232 port.
About the JACE System Shell Menu:
The Shell menu of the JENEsys-Edge 534 does not include the ability to enable/disable SFTP and
Telnet.
Pg. 50 - About serial shell mode - Items Needed for Serial System Shell:
An RS-232 port on your PC is not needed.
The JENEsys-Edge 534 will only require a Mini-USB to USB cable and terminal emulation software
installed on your PC.
The JENEsys-Edge 534 does not use a jumper.

www.lynxspring.com
JENEsys
®
Edge™534
USER GUIDE
1210 NE Windsor Drive
Lee’s Summit, MO 64086
[email protected]m
1 [phone]
© 2019 Lynxspring, Inc.
All Rights Reserved
Revised 2/1/2019
JENE-EG534-V2
Page 5 of 31
Pg. 50 – 51 - Connecting to a serial system shell:
Set the Bits Per Second to 115200 for the JENEsys-Edge 534. (Step 5)
Steps 6 and 7 are not applicable to the JENEsys-Edge 534.
In Step 8, the movement of a jumper is not applicable to the JENEsys-Edge 534.
Platform Guide Addendum
Please note the following amendments to Niagara Documentation “docPlatform” in regards to the operation of the
JENEsys Edge 534:
Pg. 40 - Downgrading a JACE:
While there is a clean dist file for the JENEsys Edge 534 to restore it to a factory-like default, downgrading
beyond 3.8.111 is not available.
Pg. 41
1st Note:
The clean dist file for the JENEsys Edge 534 is only available on Lynxspring’s website.
2nd Note:
The JENEsys Edge 534 – AX is only available in builds 3.8.111 and 3.8.401, as of the date this
document was published.
Pg. 43 - Upgrading a JACE:
The JENEsys Edge 534 – AX can only be upgraded from 3.8.111 to 3.8.401. Lynxspring’s custom core files
and Onyxx drivers are required.
Pg. 47 - GPRS Modem Configuration:
The JENEsys Edge 534 does not support GPRS.
Pg. 95 - Wi-Fi Configuration:
At the time of publication of this document, the JENEsys Edge 534 does not support Wi-Fi.
Pg. 145 - Driver Types:
Some drivers are not supported by the JENEsys Edge 534.

www.lynxspring.com
JENEsys
®
Edge™534
USER GUIDE
1210 NE Windsor Drive
Lee’s Summit, MO 64086
[email protected]m
1 [phone]
© 2019 Lynxspring, Inc.
All Rights Reserved
Revised 2/1/2019
JENE-EG534-V2
Page 6 of 31
JENEsys Edge 534 Startup procedure
The startup of the JENEsys Edge 534 – AX is a two-step process as follows:
1. Commissioning the controller with 3.8.111 or 3.8.401, installing the latest Onyxx Driver, and;
2. Updating the Onyxx system version
From your PC, use the Niagara Workbench 3.8.111 or 3.8.401 installed with the “installation tool” option (checkbox
“This instance of Workbench will be used as an installation tool”). This option allows you to install necessary core files onto the
controller.
Download the latest Onyxx Driver package from our website, which includes necessary Niagara core files, a cleanDist file,
onyxxDriver.jar, platOnyxx.jar, and instructions. Follow the instructions provided in the driver package to arrange the files
appropriately, then to commission the controller and update the Onyxx system version. A station with an Onyxx Network is
required to initiate the Onyxx system version update. See Onyxx Network Quick Start for details on how.
Onyxx Network Quick Start
This section provides a collection of procedures to use the onyxxDriver to make Onyxx Proxy Points, the station interface to
physical I/O points. As with other NiagaraAX drivers, you can do most configuration from special “manager” views and property
sheets using Workbench.
Configure the onyxxNetwork
To add and configure the onyxxNetwork, perform the following main tasks:
•Add an onyxxNetwork
•Discover and add Onyxx Devices
Add an onyxxNetwork
Use the following procedure to add an onyxxNetwork under the station’s Drivers container.
To add an onyxxNetwork in the station:
Step 1: Double-click the station’s Drivers container, to bring up the Driver Manager.
Step 2: Click the New button to bring up the New DeviceNetwork dialog.
Step 3: Select onyxxNetwork, ensure number to add is 1, and click OK. This brings up a dialog to name this
network.
Step 4: Click OK to add the onyxxNetwork to the station.
Discover and add Onyxx Devices
In the Onyxx Driver architecture, file directories act as “device-level” components.
To discover Onyxx Devices:
Step 1: Double-click the onyxxNetwork to access the Device Manager.
Step 2: Click the Discover button to launch an Onyxx Device Discovery job.
Step 3: When complete, discovered Onyxx Devices are displayed in the top pane in the “Discovered” table. The
bottom pane, labeled “Database,” is a table of Onyxx Devices that are currently mapped into the Niagara station.
The database will remain empty until a device is added.
Step 4: Click to highlight the discovered Onyxx Device(s) you wish to add, then click the Add button. The Add
dialog appears, in which you can accept all defaults (Figure 3-5).
Step 5: Click OK to add the Onyxx Device(s) to your station.
Manually adding Onyxx Devices
Manually add Onyxx Devices, using the New button in the Device Manager.
Add Onyxx Proxy points
As with device objects in other drivers, each Onyxx Device has a Points extension that serves as the container for Proxy
points. The onyxxDriver Point Manager is used to create Onyxx Proxy points under any Onyxx Device.
This section provides quick start procedures for both tasks, as follows:

www.lynxspring.com
JENEsys
®
Edge™534
USER GUIDE
1210 NE Windsor Drive
Lee’s Summit, MO 64086
[email protected]m
1 [phone]
© 2019 Lynxspring, Inc.
All Rights Reserved
Revised 2/1/2019
JENE-EG534-V2
Page 7 of 31
•Using online Discover to add Onyxx Proxy points
•Manually adding Onyxx Proxy points
Using online Discover to add Onyxx Proxy points
This is the recommended way to accurately add Onyxx Proxy points under an Onyxx Device. Use the following
procedures:
•To discover I/O points
•To add discovered I/O points as Onyxx Proxy points
Note: If your onyxxNetwork has multiple Onyxx Devices, repeat both procedures (discover and add) for each
Device, until you have all I/O points proxied in the station.
To discover I/O points
Step 1: In the N Device Manager, in the Exts column, double-click the Points icon in the row representing the
Onyxx Device you wish to explore. This brings up its Onyxx Driver Point Manager.
Step 2: Click the Discover button to learn what I/O points are on the Onyxx Device. When the discovery job
completes, discovered I/O points are listed in the top pane of the view in the “Discovered” table. Each I/O point
occupies one row.
To add discovered I/O points as Onyxx Proxy points
Step 1: Select the I/O point or points in the Database pane of the Onyxx Driver Point Manager.
Step 2: You can map selected points in the station in different ways:
•Drag from the Discovered pane to the Database pane.
•Double-click an item in the Discovered pane.
•Right-click, then select add.
Note: All these actions will open up an “Add” dialog box.
Step 3: When the “Add” dialog appears, you typically edit a number of fields for each I/O point. For complete
details, see “Onyxx Driver Point Manager usage notes” on page 14.
The following brief summaries explain Add dialog fields:
•Name - This is the Onyxx Proxy point name—you typically change this to describe the I/O purpose.
•Type - This is the Onyxx “type,” which is selectable for any “universal input,” but fixed for any output. See
“Universal Input selection notes” on page 14 and “Output type selection notes” on page 15.
Note: Unlike other entries in the Add dialog, you cannot edit the point’s Type later.
•Address - This is the learned I/O point’s hardware’s port address.
•Poll Frequency - This specifies the point’s poll frequency group (default is Normal).
•Conversion - This specifies the conversion type used between the Onyxx Proxy extension’s “Device Facets”
and the parent point’s facets. See “Conversion types in Onyxx Driver Proxy points” on page 18.
•Facets - These are the Onyxx Proxy point’s facets, for how the value should be displayed in Niagara.
Step 4: When you have Onyxx Proxy point(s) configured properly, click OK. The Proxy points will be added to the
station and appear in the Database pane. For more details, see “About Onyxx Driver Proxy points” on page 16.
Note: In cases where you notice a fault status for input points you have edited with “non-default” facets, it is
likely related to a mismatch of the “Units” in the point’s automatically-appended Linear Calibration Ext. To clear
this fault status, expand the point’s Linear Calibration Ext and edit Units to match the units in the point’s
facets. For more information, see “Linear Calibration Ext” on page 22.
Manually adding Onyxx Proxy points
Manually add Onyxx Proxy points, using the “New” button in the Onyxx Point Manager, or by dragging from the Onyxx
palette. However, this method is generally not recommended as the path for the point will not be automatically populated.

www.lynxspring.com
JENEsys
®
Edge™534
USER GUIDE
1210 NE Windsor Drive
Lee’s Summit, MO 64086
[email protected]m
1 [phone]
© 2019 Lynxspring, Inc.
All Rights Reserved
Revised 2/1/2019
JENE-EG534-V2
Page 8 of 31
Onyxx Network Concepts
This section provides conceptual details on the onyxxNetwork driver and its components, including views. onyxxNetwork Driver
components are the station interface to physical I/O points on JENEsys Edge 534 controllers and attachable I/O extender
modules.
About Onyxx Network Architecture
Essentially, the onyxxNetwork is similar in functionality to the NdioNetwork and uses the standard NiagaraAX network
architecture. For example, real-time data is modeled using Onyxx Proxy points, which resides under an Onyxx “device”
within an Onyxx network container in the station’s Driver Container (Drivers in Nav Tree). Hierarchically, the component
architecture is: network, device, point extension, points.
Figure 3-1 onyxxNetwork driver architecture
Similarly to Ndio, “Points” is the only extension under an Onyxx “device,” and the purpose of the onyxxDriver is to configure
(and Proxy) the actual I/O hardware points.
Note: Use “Manager” views of Onyxx container components to add all Onyxx components to your station, including
Proxy points. In these views, the driver provides online “discovery” of available devices and points and will
automatically populate path names for devices and points.
For more details see:
•About the Onyxx Network
•N Device Manager
•About the Onyxx Device
•Onyxx Driver Point Manager
•About Onyxx Driver Proxy points
About the Onyxx Network
The onyxxNetwork is the top-level container component for “everything Onyxx” in a station.
Note: Only one onyxxNetwork component is valid in a station, regardless of how many Onyxx XM 34IOs or Onyxx XM
34IO-Bs are present.
The onyxxNetwork should reside in the station’s Driver Container. Add an onyxxNetwork from the Driver Device Manager
view, using the “New” command.

www.lynxspring.com
JENEsys
®
Edge™534
USER GUIDE
1210 NE Windsor Drive
Lee’s Summit, MO 64086
[email protected]m
1 [phone]
© 2019 Lynxspring, Inc.
All Rights Reserved
Revised 2/1/2019
JENE-EG534-V2
Page 9 of 31
Figure 3-2 onyxxNetwork driver architecture
Note: The JENEsys Edge 534 must have the Onyxx module installed.
The onyxxNetwork component has the typical collection of slots and properties as most other network components. The
following sections explain further:
•Onyxx Network status notes
•Onyxx Network monitor notes
•Onyxx Network tuning policy notes
•Onyxx Network poll scheduler notes
•Onyxx Network views
Onyxx Network status notes
Unlike most “fieldbus” drivers such as BACnet and Lonworks, the status of an onyxxNetwork can be “down,” in
addition to the normal “ok” or less typical “fault”. A down status might occur in the case of external I/O where the
physical connection was removed (no communications are possible), or no Onyxx devices were added to the
database.
The Health slot contains historical timestamp properties that record the last network status transitions from “ok” to any
other status. The “Fault Cause” property further explains any fault status.
Note: As in other driver networks, the onyxxNetwork has an available “Alarm Source Info” container slot you can
use to differentiate onyxxNetwork alarms from other component alarms in the station. See “About network Alarm
Source Info” in the Drivers Guide for more details.
Onyxx Network monitor notes
The Onyxx Network monitor ( Onyxx Ping Monitor)contains the basic network monitoring properties. For general
information, see “About Monitor” in the Drivers Guide. This monitor is set to run every 10 seconds and is not editable.

www.lynxspring.com
JENEsys
®
Edge™534
USER GUIDE
1210 NE Windsor Drive
Lee’s Summit, MO 64086
[email protected]m
1 [phone]
© 2019 Lynxspring, Inc.
All Rights Reserved
Revised 2/1/2019
JENE-EG534-V2
Page 10 of 31
Figure 3-3 Monitor properties of onyxxNetwork
Onyxx Network tuning policy notes
The onyxxNetwork has the typical network-level Tuning Policy Map slot with a single default Tuning Policy. More
information for this can be found in the “About Tuning Policies” in the Drivers Guide. However, given the small number
of total Onyxx Proxy points supported under an onyxxNetwork, the importance of creating additional tuning policies (or
editing the default tuning policy) is generally lower, relative to other driver networks.
Onyxx Network poll scheduler notes
The onyxxNetwork has the typical network-level Poll Scheduler slot with standard collection of properties, as described
in “About poll components” in the Drivers Guide. The following notes apply to the Poll Scheduler of an onyxxNetwork:
•By default, discovered/added Onyxx Proxy points have a Poll Frequency setting of “Normal” at the default Normal
Rate of 5 seconds. Given the small number of total Onyxx Proxy points supported under an onyxxNetwork, you
can safely assign them to the “Fast” rate (default 1 second).
•The Poll Frequencies of Fast, Normal, and Slow can be increased or decreased as desired.
Collision Arbitration Features
The Onyxx Network relies on values to be sent regularly across the sub-network as a stream. The reciever actively
“listens” for messages that pertain to it. In case the receiver was busy when the original message was sent, two
properties were added to allow for correcting – ‘Resend Interval’ and ‘Inter Point Delay.’
Resend Interval
This property allows the time between needed repeated messages to be increased or decreased. It defaults to
10 seconds (minimum) and has no upper limit. Increasing it may help minimize collisions.
Inter Point Delay
Due to the nature of the receiver, sending multiple messages at nearly the same time can cause messages to
not be received, as the receiver will be busy. This property decreases the speed at which the re-sent
messages for the same receiver are produced. The default is set for 10 seconds and can be lowered to 1
second.
Oversample Tuning
This property allows users to specify the sampling rate for collecting values. In general, values are calculated by
taking x samples of the value across a time period. The value is then calculated by averaging all the values within
the timeperiod. The more number of samples, the less an outlier will affect the value. However, this also increases
the burden on the CPU. This property is set at its max (255) so as to calculate the best value. If performance is a
concern, users can set this value lower. Though, this can allow outliers to skew the calculated value in the outliers’
direction.

www.lynxspring.com
JENEsys
®
Edge™534
USER GUIDE
1210 NE Windsor Drive
Lee’s Summit, MO 64086
[email protected]m
1 [phone]
© 2019 Lynxspring, Inc.
All Rights Reserved
Revised 2/1/2019
JENE-EG534-V2
Page 11 of 31
Onyxx Network views
The default view of the onyxxNetwork is the ‘N Device Manager.’ This is the equivalent of the ‘Device Manager’ in most
other drivers. Use this view to discover and add Onyxx Device components to the station. For details, see
“N Device Manager” below. Other standard views are also available on the onyxxNetwork.
N Device Manager
As the default onyxxNetwork view, the ‘N Driver Device Manager’ view can be used to discover and add one or more
“device-level” Onyxx Device components to the station’s database (Figure 3-4). For general information, refer to
“About the Device Manager” in the Drivers Guide.
Figure 3-4 Adding Onyxx Device discovered using N Device Manager
Figure 3-5 Add dialog for Onyxx Device(s)
Onyxx Board Manager Usage notes
Before launching a discover job, ensure that any external I/O modules are correctly installed and connected to
the host JENEsys Edge 534 controller. When adding the device to the database, changes to any defaults
other than “Name” is not needed (Figure 3-5).

www.lynxspring.com
JENEsys
®
Edge™534
USER GUIDE
1210 NE Windsor Drive
Lee’s Summit, MO 64086
[email protected]m
1 [phone]
© 2019 Lynxspring, Inc.
All Rights Reserved
Revised 2/1/2019
JENE-EG534-V2
Page 12 of 31
About the Onyxx Device
The Onyxx Device represents an I/O-34 board and can be extended by attaching Onyxx XM modules. The JENEsys Edge
534 and Onyxx XM modules hold the processors that allow for servicing hardware I/O points.
Figure 3-6 Onyxx Device property sheet
Under an onyxxNetwork, each Onyxx Device must have a unique “Device Path.” Apart from the “Enabled” property, this is
the only writable property of an Onyxx Device. All other Onyxx properties are read-only types (Figure 3-6), reflecting the
status and I/O capabilities.
Note: The N Device Manager view of the onyxxNetwork provides online discover and add commands to ensure all
available Onyxx Devices can be created and configured properly.
Each Onyxx Device has a single important device extension named Points. This is the container for all of a device’s Proxy
points. Each Proxy point represents a specific I/O terminal address on the device (JENEsys Edge 534 or Onyxx XM 34IO),
serviced by that board’s I/O processor(s). For more details, see “Onyxx Point Manager” on page 13.
Onyxx Device properties
Onyxx Device properties can be categorized into two groups:
1. Device status properties
2. Config properties
Note: As in other driver networks, the Onyxx Device has an available “Alarm Source Info” container slot you can use to
differentiate Onyxx Device alarms from other component alarms in the station.
1. Device status properties
Onyxx Devices have typical device-level status properties:
•Status - Status of the onyxxNetwork communications to this Onyxx Device; possible status flags include:
Ok - Normal communications, no other status flags
Disabled - Enabled property is set to false, either directly or in onyxxNetwork and while status is disabled,
all child onyxxPoints have disabled status; Onyxx Device polling is suspended
Fault - Typically configuration error, e.g. Onyxx Device (duplicate or invalid IO Port number)
Down - Error communicating to one or more Onyxx I/O processors on Onyxx XM 34IO
•Enabled - Either true (default) or false; can be set directly or in the parent onyxxNetwork; see Status disabled
description above
•Fault Cause - Describes the cause of a fault
•Health - Contains properties, including timestamps of last “ok” time and last “fail” time, and a string property
describing the last fail cause

www.lynxspring.com
JENEsys
®
Edge™534
USER GUIDE
1210 NE Windsor Drive
Lee’s Summit, MO 64086
[email protected]m
1 [phone]
© 2019 Lynxspring, Inc.
All Rights Reserved
Revised 2/1/2019
JENE-EG534-V2
Page 13 of 31
2. Config properties
In addition to common device-level status properties, an Onyxx Device has the following additional properties.
•Device Path – Set automatically if the device was discovered and added; a sub-portion of the full directory path
•Led Firmware Version – Displays the current firmware version of the chip that controls the LED board
•Analog Ouput Firmware Version – Displays the current firmware version of the chip that controls the AO Ports
•Digital Output Firmware Version – Displays the current firmware version of the chip that controls the DO ports
•Univesal Input Firmware Version_Lower Ports – Displays the current firmware version of the chip that controls
the UI 1-8 ports
•Universal Input Firmware Version_Upper Ports – Displays the current firmware version of the chip that controls
the UI 9-16 ports
Onyxx Point Manager
As the default view for the Points extension under an Onyxx Device, the onyxxDriver Point Manager allows available I/O
terminal “points” to be discovered and add corresponding Onyxx Proxy points added to the station database.
Figure 3-7 Adding Onyxx Proxy points discovered using Onyxx Driver Point Manager
A Proxy point is added for each discovered I/O terminal. For more details, see “Onyxx Board Manager Usage notes” on
page 11. For procedures, see “Add Onyxx Proxy points” on page 6.

www.lynxspring.com
JENEsys
®
Edge™534
USER GUIDE
1210 NE Windsor Drive
Lee’s Summit, MO 64086
[email protected]m
1 [phone]
© 2019 Lynxspring, Inc.
All Rights Reserved
Revised 2/1/2019
JENE-EG534-V2
Page 14 of 31
Onyxx Driver Point Manager usage notes
The following notes apply when using the Onyxx Driver Point Manager:
•Add and Edit dialog fields
•Universal Input type selection notes
•Output type selection notes
Add and Edit dialog fields
When adding Onyxx Proxy points for discovered I/O points, the following items are available in the Add dialog
(Figure 3-8)
Figure 3-8 Add dialog in Onyxx Driver Point Manager
•Name - Name of the Onyxx Proxy point; can be edited from the default name to reflect the actual purpose
of the I/O point, such as “Room101T,” “AHU-1_FanStatus,” and so forth
Note: The number appended onto a default name has no association to the I/O point address.
•Type - The type of Onyxx Proxy point to create (cannot be edited after adding it to the database, see
“Universal Input selection notes” below)
•Port Address - The I/O terminal address within that general IO type; recommended to be left at defualt
value
•Poll Frequency - The assigned poll frequency group, as configured in the Onyxx Network’s poll
scheduler; see “Onyxx Network poll scheduler notes” on page 10
•Conversion - The conversion type used between units in the Proxy extension’s “Device Facets” and the
units in the parent point’s Facets; see “Onyxx Driver Proxy Ext common properties” on page 17 for more
details
•Point Type - Closely related to the “Type” field; specifies if point will be a Current, Resistance, or Voltage
point
•Facets - Facets for the Onyxx Proxy point and equivalent to accessing facets through the point’s property
sheet; automatically set during creation
Universal Input selection notes
All JENEsys Edge 534 controllers and Onyxx XM 34IO controllers external I/O modules provide 16 “universal
inputs” (UI) terminals. On the device, these terminals are labeled UI1 to UI6.
The default Point Type is VoltageInputPoint and can be changed before adding to the database, as shown in
Figure 3-9.

www.lynxspring.com
JENEsys
®
Edge™534
USER GUIDE
1210 NE Windsor Drive
Lee’s Summit, MO 64086
[email protected]m
1 [phone]
© 2019 Lynxspring, Inc.
All Rights Reserved
Revised 2/1/2019
JENE-EG534-V2
Page 15 of 31
Figure 3-9 Select Onyxx Driver input type for each universal input
For most I/O platforms, any of the following are valid universal input choices:
•VoltageInputPoint -NumericPoint that reads a 0-to-10Vdc input signal and produces either a voltage
value or linear scaled output value
•ResistiveInputPoint -NumericPoint that reads a resistive signal within a 0-to-100K ohm range and
produces either an ohms value or linear scaled output value
•ThermistorInputPoint -NumericPoint that reads a Thermistor temperature sensor (Type 3, or other) signal
and produces a scaled output value
•CurrentInputPoint -NumericPoint that reads 4mA to 20mA and produces an amperage value
•CounterInputPoint -NumericPoint that counts the number of contact closures at the input
•BooleanInputResistive -BooleanPoint that reads the resistive input as one of two boolean states
(equipment status); if the measured resistance level becomes higher than the threshold level, the point will
output false
•BooleanInputVoltage -BooleanPoint that reads the voltage input as one of two boolean states
(equipment status); if the measured resistance level becomes higher than the threshold level, the point will
output true
•BooleanInputCurrent -BooleanPoint that reads the current input as one of two boolean states
(equipment status); if the measured resistance level becomes higher than the threshold level, the point will
output true
Selecting any Type other than Boolean creates a standard NumericPoint, with a specified OnyxxInputProxy
extension. Selecting BooleanInputPoint creates selections result in a BooleanPoint with an
OnyxxBooleanInputProxy extension. For more details, see “About Onyxx Driver Proxy points” on page 16.
Note: After adding an Onyxx Proxy point, the name, port address, conversion, and facets are all editable; type
is not. To change type, the point must be deleted and added again, selecting from the Type drop-down
menu, as shown in Figure 3-9. The ResistiveInputPoint and ThermistorInputPoint are identical, except for the
conversion type used in the ProxyExt.
Output type selection notes
JENEsys Edge 534 devices and Onyxx extender modules have 10 digital outputs (DO) and 8 analog Output (AO)
terminals. For any discovered output I/O terminal, the Add dialog preselects the appropriate writable OnyxxPoint
type, as either:
•BooleanOutputWritable: A standard BooleanWritable point, with an OnyxxBooleanOutput Proxy
extension
•VoltageOutputWritable: A standard NumericWritable point, with an OnyxxVoltageOutput Proxy extension

www.lynxspring.com
JENEsys
®
Edge™534
USER GUIDE
1210 NE Windsor Drive
Lee’s Summit, MO 64086
[email protected]m
1 [phone]
© 2019 Lynxspring, Inc.
All Rights Reserved
Revised 2/1/2019
JENE-EG534-V2
Page 16 of 31
About Onyxx Driver Proxy points
Onyxx Proxy points are similar to Proxy points in other drivers. Alarm and history extensions can be added to them, and
they can be linked to other station logic.
The following sections explain further:
•Onyxx Driver point types
•Onyxx Driver Proxy Ext common properties
•Conversion types in Onyxx Driver Proxy points
•Scale and offset calculation (linear)
•Non-linear sensor support (AX-3.4 and later)
•Linear Calibration Ext
Onyxx Driver point types
As seen in the onyxxDriver palette (Figure 3-10), there are 7 different onyxxDriver point types.
Figure 3-10 Onyxx Driver components as seen in the onyxxDriver palette
These 7 different onyxxDriver point types derive from the following 4 control point types:
•BooleanPoint - For Boolean “universal input” types; can be used to create BooleanInputPoint–Resistive point
type
•NumericPoint - For Numeric “universal input” types; can be used to create CounterInputPoints,
ResistiveInputPoints, ThermistorInputPoints (using ResistiveInputPoints and modifying), VoltageInputPoints,
and CurrentInputPoints
•BooleanWritable - For Boolean output types; can be used to create BooleanOutputWritable Points
•NumericWritable - For numeric output types; can be used to create VoltageOutputWritable Points
Each onyxxDriver point type is typically unique by one or more properties in its Proxy extension. Also, the Proxy
extension in each type contains the same (common) properties. Things unique to each onyxxDriver point types are
explained in following sections, as well as common properties in each point’s Proxy extension.

www.lynxspring.com
JENEsys
®
Edge™534
USER GUIDE
1210 NE Windsor Drive
Lee’s Summit, MO 64086
[email protected]m
1 [phone]
© 2019 Lynxspring, Inc.
All Rights Reserved
Revised 2/1/2019
JENE-EG534-V2
Page 17 of 31
Onyxx Driver Proxy Ext common properties
Figure 3-11 Common properties among Onyxx Proxy extensions
As shown in the property sheet view (Figure 3-11), each onyxxDriver point has the following properties in its Proxy
extension (Proxy Ext):
•Status - (read only) Status of the Proxy extension
•Fault Cause - (read only) Provides a text description of why the point status is in fault
•Enabled - True (default) or false; when set to false, the point’s status becomes disabled and onyxxDriver
polling is suspended
•Device Facets - (read only) Native facets used in Proxy read or writes (Parent point’s facets are used in point
status display, and are available for edit in Add and Edit dialogs in Point Manager)
•Conversion – Specifies the conversion used between the “read value” (in Device Facets) and the Parent
point’s output (in selected point facets); see “Conversion types in Onyxx Driver Proxy points” on page 18 for
more
•Tuning Policy Name – The assigned tuning policy, which is typically “Default Policy”
•Read Value - (read only) The last value read, using device facets
•Write Value - (read only) For writable point, this is the last value written, using device facets
•Point Type - (read only) Such as “BooleanResistiveInput,” “ResistiveInput,” “BooleanOutput”
•Port Address - The point’s I/O terminal address for its hardware type (UI, AO, DO), automatically found during
discovery; if port address is out of range or a duplicate (within the same board), the point has a fault status
•Poll Frequency - The assigned poll frequency group -- either Slow, Normal (default), or Fast
•Raw - (read only) The integer value returned from the onyxxDriver processor
•Hysteresis (hidden) – Averages the output value to reduce signal bounces
•Hysteresis Size (hidden) – Specifies the number of samples to average into the calculated output value

www.lynxspring.com
JENEsys
®
Edge™534
USER GUIDE
1210 NE Windsor Drive
Lee’s Summit, MO 64086
[email protected]m
1 [phone]
© 2019 Lynxspring, Inc.
All Rights Reserved
Revised 2/1/2019
JENE-EG534-V2
Page 18 of 31
Conversion types in Onyxx Driver Proxy points
In any onyxxDriver Proxy point. a Conversion property is available with the following selections:
Note: Currently, Workbench provides no filtering of Conversion types based on the Onyxx Proxy point being
configured. You will see the same Conversion drop-down selection list for a VoltageInputPoint as you do for a
BooleanOutputWritable. However, only a few combinations are typically useful. In addition, there may be
conversion types included that are not applicable, such as “Sm2 Flow Conversion,” which can be ignored.
500 Ohm Shunt
Applies only to a VoltageInputPoint used to read a 4-to-20mA sensor, where the UI input requires a 500 ohm
resistor wired across (shunting) the input terminals. The input signal is 2V to 10V. If this conversion type is not
available, select Linear conversion instead.
As compared to a Linear or Generic Tabular conversion, this selection provides better resolution near the upper
(20mA/10V) range of the input, compensating for input clamping protection the circuitry automatically applies
when input voltage rises above 3.9V.
Note: Currently, selection of 500 Ohm Shunt produces a “secondary” selection for conversion type, with all
conversion types shown again. Typically, only the Linear type is valid, providing the 4-20mA sensor has a
linear response. In the Scale and Offset fields for this Linear conversion, you enter whatever calculated values
are needed to display in the appropriate units of measurement for that sensor. Figure 3-12 shows an example
configuration of such a point.
Figure 3-12 Example VoltageInputPoint used for 4-to-20mA input (Edit dialog from Point Manager)
For background on this example configuration, see “Scale and offset calculation example 2”.
In the unusual case of a non-linear 4-20mA sensor, the secondary conversion type “Generic Tabular” can be used.
Default
(The default selection)
Conversion between “similar units” is automatically performed within the Proxy point. For example, if the “units”
facets of a ThermistorInputPoint is set to degrees F, the point output automatically converts to the appropriate
value, from degrees C.
If you set the Parent point’s facets to dissimilar units (often the case with a VoltageInputPoint), the parent point
has a fault status to indicate a configuration error. In this case, you must select Linear conversion, and also set
“Units” in the point’s “LinearCalibrationExt” to match the point’s facets. See “Scale and offset calculation (linear)”
on page 19 and “Linear Calibration Ext” on page 22.
Generic Tabular
This Conversion type allows nonlinear support for devices other than for thermistor temperature sensors with units
in temperature. Generic Tabular uses a “lookup table” method similar to the “Thermistor Tabular” conversion, but
without predefined output units. Selection provides a popup Tabular Conversion Dialog in which a custom
“source-to-result” non-linear curve is entered, including the ability to import and export response curve files. For
more details, see “Non-linear sensor support” on page 20 and “Curve File Import/Export notes” on page 28.

www.lynxspring.com
JENEsys
®
Edge™534
USER GUIDE
1210 NE Windsor Drive
Lee’s Summit, MO 64086
[email protected]m
1 [phone]
© 2019 Lynxspring, Inc.
All Rights Reserved
Revised 2/1/2019
JENE-EG534-V2
Page 19 of 31
Linear
Applies to VoltageInputPoint, ResistiveInputPoint, and VoltageOutputWritable points. Typically, the point’s
output value is set to a unit of measurement other than Device Facets (voltage or resistance). The Linear selection
provides two fields to make the transition:
•Scale: Determines linear response slope.
•Offset: Offset used in output calculation.
For related details, see “Scale and offset calculation (linear)” on page 19.
Note: For a VoltageInputPoint used for a 4-to-20mA sensor (shunt resistor on UI input), another primary
conversion type should be used, if available: 500 Ohm Shunt, with Linear typically selected as the “secondary”
conversion. See more about that other conversion type above.
Reverse Polarity
Useful in a BooleanInputPoint or BooleanOutputWritable to reverse the logic of the hardware binary input or
output.
Note: Be careful in the use of the reverse polarity conversion, as it may lead to later confusion when
troubleshooting logic or communications problems.
Thermistor Type 3
Applies to a ThermistorInputPoint, where this selection provides a “built-in” input resistance-to-temperature value
response curve for Type 3 Thermistor temperature sensors.
Tabular Thermistor
Applies to a ThermistorInputPoint, where this selection provides a control for a popup dialog for a custom
resistance-to-temperature value response curve, including ability to import and export curve response files. For
more details, see “Tabular Thermistor notes” on page 26 and “Curve File Import/Export notes” on page 28.
Scale and offset calculation (linear)
Unless you want a VoltageInputPoint or VoltageOutputWritable to operate with facets (units) of volts, you must set
the point’s facets to the desired units, and set the ProxyExt Conversion property to Linear.
You must then enter your calculated scale and offset values in the Linear fields. Also, you must set the
“Units” in its Linear Calibration Ext to match an input point’s facets—otherwise a fault status occurs.
Note: This also applies to any linearly-responding ResistiveInputPoint using point facets other than ohms.
Use the following formulas to calculate the Linear scale and offset values:
Where: x1 and x2 are the values (e.g. voltage), and y1 and y2 are the corresponding desired units.
•Scale
Scale = (y2 - y1) / (x2 - x1)
•Offset
Offset = y1 - (Scale * x1)
See example 1 and example 2.
Scale and off set calculation… Example 1
You have a 6-to-9Vdc actuator to control with a VoltageOutputWritable, in terms of 0-to-100% input.
Configure this point’s facets to have units: “misc,” “percent” (%).
Set the ProxyExt’s Conversion property to Linear, and enter these calculated scale and offset values:
•Scale
Scale = (y2 - y1) / (x2 - x1)
Scale = (100% - 0%) / (9V - 6V) = 100/3 = 33.3333333
•Offset
Offset = y1 - (Scale * x1)
Offset = 0% - (33.3333333 * 6V) = 0 - 200 = -200

www.lynxspring.com
JENEsys
®
Edge™534
USER GUIDE
1210 NE Windsor Drive
Lee’s Summit, MO 64086
[email protected]m
1 [phone]
© 2019 Lynxspring, Inc.
All Rights Reserved
Revised 2/1/2019
JENE-EG534-V2
Page 20 of 31
Scale and offset calculation… Example 2
You have a linear 4-to-20mA differential pressure sensor to read with a VoltageInputPoint (using an external 500
ohm resistor wired across the input), reading effectively 2V to 10V. The range of this sensor is from -10in.wc. to
+10in.wc. Configure this point’s facets to have units: “pressure,” “in/wc”.
Set the ProxyExt’s Conversion property to use “500 Ohm Shunt” (if available), then “Linear” as secondary, and in
the Linear fields enter these calculated scale and offset values:
•Scale
Scale = (y2 - y1) / (x2 - x1)
Scale = (+10in.wc - -10in.wc) / (10V - 2V) = 20/8 = 2.5
•Offset
Offset = y1 - (Scale * x1)
Offset = -10in.wc - (2.5 * 2V) = -10 - 5 = -15
Figure 3-12 shows this point’s configuration in a Workbench dialog. Note that the Linear Calibration Ext for this
point will require its “Units” property to be configured to match the facets for this point - otherwise, the point will
have a fault status. See the “Linear Calibration Ext” section for related details.
Non-linear sensor support
The conversion selection Generic Tabular provides a way for a VoltageInputPoint or ResistiveInputPoint to support a
nonlinear signal on a universal input (using point Facets other than temperature). Note that the ThermistorInputPoint
also provides non-linear support for resistance-based temperature sensors, but point Facets are limited to
temperature.
If you select Conversion type of “Generic Tabular” an edit control (note pad icon) appears in the property sheet beside
it. Click the icon to see the Tabular Conversion Dialog, as shown in Figure 3-13.
Figure 3-13 Tabular Conversion Dialog from edit control