Installation and Operations Guide

FLG-MODBUS

Novar Controls Corporation. All Rights Reserved. LTBT-TM-FLGMDBS Rev. 0002

User agreement and limited warranty
IMPORTANT - PURCHASE OF ALERTON PRODUCTS OR USE OF SOFTWARE, FIRMWARE AND / OR ACCOMPANYING DOCUMENTATION (DEFINED BELOW) IS
SUBJECT TO LICENSE RESTRICTIONS AND LIMITED WARRANTY. CAREFULLY READ THIS AGREEMENT BEFORE USING ALERTON PRODUCTS, SOFTWARE,
FIRMWARE AND/OR DOCUMENTATION.
This is a legal "Agreement," concerning the purchase of Products and use of Software, Firmware and/or Documentation, between you, the "User" (either individually or as an
authorized representative of the company that is purchasing, has purchased, or is using the Products, Software, Firmware or Documentation) and Alerton, a division of Novar
Controls Corporation, 6670 - 185th Avenue NE, Redmond, Washington 98052 USA. ("Alerton").
PURCHASE OF ALERTON PRODUCTS OR USE OF SOFTWARE, FIRMWARE AND / OR ACCOMPANYING DOCUMENTATION INDICATES USER'S COMPLETE AND
UNCONDITIONAL ACCEPTANCE OF THE TERMS AND CONDITIONS SET FORTH IN THIS AGREEMENT.
Alerton provides Alerton products ("Products"), software programs ("Software"), firmware, e.g., protocols, software program code, device drivers and related hardware ("Firm-
ware") and accompanying documentation ("Documentation") and grants a non-exclusive and non-transferable license ("License") to User to use the Software and the Firm-
ware only on the following terms and conditions. Taken together, Products, licensed Software, licensed Firmware and accompanying Documentation are collectively defined
as "Alerton Product(s)" in this Agreement.
1. Copyright. The Software, Firmware and Documentation are copyrighted and protected by United States copyright laws and international treaty provisions and laws, contain
valuable proprietary products, information and trade secrets, and shall remain the property of Alerton. User may not and shall not copy or otherwise reproduce or make avail-
able to any other party any part or all of the Software, Firmware or Documentation nor decompile, disassemble, reverse engineer, manufacture or modify any portion of the
Products, Software, Firmware, Documentation or any portion of the same for any purpose or otherwise attempt to determine the underlying source code of the Software or
Firmware or permit any such action; provided however, User may either (a) make one (1) copy of the Software solely for backup or archival purposes, or (b) transfer one (1)
image of the Software to a single hard disk, CD or other comparable media, provided User keeps the original solely for backup or archival purposes.
2. License. User is hereby licensed to use one (1) copy of the Software for User's own use in operating the Products. User may not rent, lease or otherwise assign or transfer
all or any part of the Software, Firmware or Documentation. In addition, User may not sublicense, assign or transfer this License or Agreement, or any part thereof. Any
attempt to do so shall terminate this License and User's right to use the Software and Firmware and shall subject User to liability for damages to Alerton. LICENSING TO
USER OF THE SOFTWARE AND FIRMWARE COMMENCES WHEN USER USES THE SOFTWARE, FIRMWARE AND / OR ACCOMPANYING DOCUMENTATION.
3. Copies, Modification or Merger. Except as specifically set forth in Paragraph 1, User may not copy, modify, transfer all or any portion of the Software, Firmware or Documen-
tation or merge it or them into another program, unless expressly authorized in advance in writing by Alerton. User must, as a condition of this License, reproduce and include
the identifying marks, copyright and proprietary notices on any permitted copy of the Software, Firmware and Documentation. "Copies" shall include, without limitation, any
complete or partial duplication on any media, adaptations, translations, compilations, partial copies within modifications, mergers with other material from whatever source and
updated works. User will use its best efforts to prevent any unauthorized copying or other activity with respect to the Software, Firmware and Documentation.
4. Third-Party Beneficiary. For any software or other technology under this Agreement licensed by Alerton from Microsoft( or other licensors, Microsoft or the applicable licen-
sor is a third party beneficiary of this Agreement with the right to enforce the obligations set forth in this Agreement.
5. Warranty. Alerton warrants Alerton manufactured or produced Alerton Products to be materially free from defects and to substantially conform to Alerton's published speci-
fications for a period of twenty-four (24) months from date of shipment from Alerton (the "Product Warranty Period"). This entire Section 5 is defined as the "Warranty."
Alerton also warrants Alerton Products that it has previously repaired or replaced for the greater of ninety (90) days from the date of their shipment from Alerton or the remain-
der of the Product Warranty Period of the originally shipped Alerton Product (the "Repair/Replacement Warranty Period").
During the Product Warranty or Repair/Replacement Warranty Period, Alerton will repair or replace the applicable Alerton Products without charge and will add applicable
engineering changes and upgrades.
This Warranty only applies to defective materials and workmanship of Alerton Products and excludes defects that result from misuse, neglect, improper installation, unautho-
rized repair or alteration, damage during or after shipping, accident and/or misapplication of such products. This Warranty does not apply to parts, equipment, software, firm-
ware, components, documentation or any other item that Alerton does not manufacture or produce. This Warranty is also voided by removal or alteration of Alerton Product
identification labels.
Alerton's sole responsibility with respect to Alerton Products shall be, within the applicable Product Warranty Period, to furnish a replacement Alerton Product (FOB factory) or,
at the option of Alerton, to repair and return (FOB Factory) the defective Alerton Product. ALERTON HEREBY EXCLUDES ALL IMPLIED WARRANTIES OF MERCHANT-
ABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND ALL OTHER EXPRESS OR IMPLIED WARRANTIES WHATSOEVER WITH RESPECT TO ALERTON
PRODUCTS. In no event shall Alerton be liable for personal injury, loss of profit, loss of production, loss of business or goodwill, business interruption, loss of business infor-
mation or data, loss due to delays, any other pecuniary loss, any cost or liability of Users or any other parties, to themselves or to others, increased or uncovered operating or
fixed costs, inefficiency, or any other special, exemplary, consequential, incidental, indirect or remote damages in any manner, directly or indirectly, related to design, manufac-
turing, supply, installation or use of, or inability to use, Alerton Products, or any other act or failure to act by Alerton or its agents or contractors.
ALERTON MAKES NO CLAIMS OR WARRANTIES WITH RESPECT TO THE SOFTWARE OR THE FIRMWARE AND SPECIFICALLY DISCLAIMS ANY IMPLIED WAR-
RANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE AND EXPRESS OR IMPLIED WARRANTIES THAT THE OPERATION OF THE SOFT-
WARE OR FIRMWARE OR ANY PORTION THEREOF WILL BE INTERRUPTION OR ERROR FREE. Notwithstanding anything to the contrary contained in this Warranty,
Alerton shall not be liable to Users or any other parties for any damages, including, but not limited to consequential, incidental, indirect, special, exemplary remote or pecuni-
ary damages and any stated or express warranties set forth in this warranty are in lieu of all obligations or liability for any damages arising out of or in connection with the use
or performance of, or inability to use, Alerton Products and the licensed Software and Firmware.
User's exclusive remedy and Alerton's entire liability arising from or in connection with the Alerton Products, Software, Firmware, Documentation and/or this License and
Agreement (including, without limitation, any breach of any warranty, express or implied) shall be, at Alerton's option, the repair or replacement of the Products or Software or
Firmware as applicable, as stated above. ACCORDINGLY, ALERTON AND ITS DESIGNATED DEALERS AND THEIR DESIGNATED ASSOCIATE DEALERS HAVE
EXCLUDED AND DISCLAIM ANY AND ALL IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE AND ALL OTHER WARRAN-
TIES, EXPRESS OR IMPLIED, WHATSOEVER, WITH RESPECT TO THE PRODUCTS, THE SOFTWARE, THE FIRMWARE, THE DOCUMENTATION AND/OR THE
LICENSE. USER HEREBY ACKNOWLEDGES THE SAME.
6. Remedies of Alerton. IF USER BREACHES THIS AGREEMENT, USER'S LICENSE HEREUNDER SHALL BE AUTOMATICALLY TERMINATED. Upon termination, User
shall return the Software, Firmware and all Documentation to Alerton and destroy any copies of the Software, Firmware and the Documentation or any portions thereof which
have not been returned to Alerton, including copies resident on electronic or digital media. If User breaches this Agreement, Alerton shall be entitled to all damages suffered
by Alerton resulting from such breach and Alerton shall be entitled to equitable and injunctive relief in addition to all other remedies at law. In this regard, User acknowledges
that its breach of any provision of this Agreement will cause Alerton immediate and irreparable injury for which there are inadequate remedies at law. The prevailing party in
any dispute concerning this Agreement shall be entitled to the costs of collection and enforcement, including but not limited to reasonable attorneys' fees, court costs and all
necessary expenses, regardless of whether litigation is commenced.
7. Export. Alerton Products are subject to regulation by local laws and United States government agencies, which prohibit export or diversion of certain products, information
about the products, and direct products of the products to certain countries and certain persons. User agrees that User will not export in any manner any Alerton Product or
direct product of Alerton Product, without first obtaining all necessary approval from appropriate local and United States government agencies.
8. RESTRICTED RIGHTS NOTICE. Alerton Products, Software, Firmware and Documentation have been developed entirely at private expense and are commercially pro-
vided with RESTRICTED RIGHTS. Use, duplication or disclosure by the U.S. Government or a U.S. Government subcontractor is subject to the restrictions pursuant to
DFARS 227.72013 (October 1988) and DFARS 52.227-19 (June 1987), as amended and as applicable. Manufacturer, licensor and publisher is Alerton, a division of Novar
Controls Corporation, 6670 - 185th Avenue NE, Redmond, Washington 98052 USA.
9. Statute of Limitations. No action for any breach of a warranty, if any, deemed or actual, may be commenced more than one (1) year following the expiration of such warranty.
10. Other. User further agrees that this Agreement is the complete and exclusive statement of the agreement between User and Alerton and supersedes any proposal or prior
agreement or any other communications between Alerton or any of its representatives and User relating to the use of the Software, Firmware, Documentation and purchase of
the Products. This Agreement may only be modified by a physically signed writing between User and Alerton. Waiver of terms or excuse of breach must be in writing and shall
not constitute subsequent consent, waiver or excuse. If any provision of this Agreement is finally determined to be unenforceable, the remaining provisions shall remain in
effect. The laws of the State of Washington and the United States, including U.S. copyright laws, shall govern this Agreement. Venue in the event of any suit, proceeding or
claim shall be in the courts located in King County, Washington, USA. If User has any questions regarding this Agreement, User may contact Alerton by writing Alerton at the
above address.
This Agreement shall inure to the benefit of and be binding upon the parties and their successors, administrators, heirs and permitted assigns. Notwithstanding any termina-
tion of this Agreement and not in limitation of any other provision of this Agreement, User shall specifically continue to be fully obligated to comply with all of the requirements
of paragraphs one (1) through four (4), as if the Agreement were not terminated and all remedy provisions hereunder shall apply to any breach of such obligations.

2 Novar Controls Corporation. All Rights Reserved. LTBT-TM-FLGMDBS Rev. 0002

 Installation and Operations Guide | Contents

Contents
About this guide 5
Other resources 5
Key illustrations 6
Quick start setup 9
Operational overview 10
Data storage and backup 10
Sequence of operations 10
System design and application 11
Hardware installation and setup 12
Power supply 12
Connecting to the BACnet network 12
Setting the MS/TP MAC address with Switch 2 13
Terminating MS/TP cabling 13
Connecting to a Modbus network 14
Setting Modbus protocol options 14
Mapping Modbus data to AVs and BVs 17
Assigning Modbus addresses 17
Setting up data mappings 17
Checking Modbus communications 19
Clearing Modbus object data 20
Downloading a ROC file 20
Appendix A: Syntax for description string 21
Scaling point data 24
Examples 24
Appendix B: Modbus function codes 25
Appendix C: Error indicators 26
BACnet error indications 26
Operator workstation error indications 26
Using the aler-diagnostics property 27

Novar Controls Corporation. All Rights Reserved. LTBT-TM-FLGMDBS Rev. 0002 3

Installation and Operations Guide | FLG-MODBUS

Important safety information and installation

precautions
Read all instructions
Failure to follow all instructions may result in equipment damage or a hazardous condition. Read all instructions
carefully before installing equipment.
Local codes and practices
Always install equipment in accordance with the National Electric Code and in a manner acceptable to the local
authority having jurisdiction.
Electrostatic sensitivity
This product and its components may be susceptible to electrostatic discharge (ESD). Use appropriate ESD
grounding techniques while handling the product. When possible, always handle the product by its non-electrical
components.
High voltage safety test
Experienced electricians, at first contact, always assume that hazardous voltages may exist in any wiring
system. A safety check using a known, reliable voltage measurement or detection device should be made
immediately before starting work and when work resumes.
Lightning and high-voltage danger
Most electrical injuries involving low-voltage wiring result from sudden, unexpected high voltages on normally
low-voltage wiring. Low-voltage wiring can carry hazardous high voltages under unsafe conditions. Never install
or connect wiring or equipment during electrical storms. Improperly protected wiring can carry a fatal lightning
surge for many miles. All outdoor wiring must be equipped with properly grounded and listed signal circuit
protectors, which must be installed in compliance with local, applicable codes. Never install wiring or equipment

!
while standing in water.
Wiring and equipment separations
All wiring and controllers must be installed to minimize the possibility of accidental contact with other, potentially
hazardous and disruptive power and lighting wiring. Never place 24VAC or communications wiring near other
bare power wires, lightning rods, antennas, transformers, or steam or hot water pipes. Never place wire in any
conduit, box, channel, duct or other enclosure containing power or lighting circuits of any type. Always provide
adequate separation of communications wiring and other electrical wiring according to code. Keep wiring and
controllers at least six feet from large inductive loads (power distribution panels, lighting ballasts, motors, etc.).
Failure to follow these guidelines can introduce electrical interference and cause the system to operate
erratically.
Warning
This equipment has been tested and found to comply with the limits for a class A digital device, pursuant to part
15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference
when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate
radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause
harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause
harmful interference, in which case the user will be required to correct the interference at his own expense.

2004 Novar Controls Corporation. All Rights Reserved.

6670 185th AVE NE
Redmond, WA 98052 USA
Phone: (425)869-8400 FAX: (425)869-8445
Web Site: www.alerton.com E-mail: info@alerton.com
All information in this document is provided as is without warranty of any kind. Novar Controls Corporation
reserves the right to change any information herein without prior notice. No guarantees are given as to the
accuracy of information. Trademarks and trade names may be used in this document to refer to either the entities
claiming the marks and names or their products. Alerton, BACtalk, and their logos are registered trademarks and
VisualLogic is a trademark of Novar Controls Corporation. Novar Controls Corporation disclaims any proprietary
interest in trademarks and trade names other than its own.
Questions, corrections, comments?
To improve our information products and better serve our readers, your feedback is vital. If you have any
questions, corrections, or comments about this publication or any other Alerton information products, please
send e-mail to techcomm@alerton.com.

4 Novar Controls Corporation. All Rights Reserved. LTBT-TM-FLGMDBS Rev. 0002

 Installation and Operations Guide | About this guide

About this guide

This guide provides instructions and information you need to install and
configure the FLG-MODBUS. It also provides illustrations and instructions for:

Connecting the power supply to the FLG-MODBUS

Connecting the FLG-MODBUS to the BACnet network
Connecting to the Modbus network
Mapping FLG-MODBUS data points to BACnet AVs and BVs
Checking Modbus communications

For information about setting up automated control features or designing a

BACnet internetwork, see the publications listed in Table 1.

Other resources
Table 1 Sources for more information

Document ID Contains
Product Data Sheets A summary of applications, capabilities, and
technical data.

Envision for BACtalk Installation Information needed to use Device Manager to view
and Startup Guide device information about the FLG-MODBUS or to
(LTBT-TM-ADMIN) download a ROC file. Also use to set up automated
control features for your BACtalk system.

BACtalk System Design Guide Use to design a BACnet internetwork or for specific
(LTBT-TM-SYSDSGN) integration tips for your application.

Novar Controls Corporation. All Rights Reserved. LTBT-TM-FLGMDBS Rev. 0002 5

Installation and Operations Guide | FLG-MODBUS

Key illustrations

24 VAC
terminal block
(See page 12)

Status LED
(See page 19)

Modbus status EIA-232/Serial

LED (See page 19) connection
(See page 14)

MS/TP MAC
addressSwitch 2
(See page 13) JP3
(See page 14)

MS/TP LED
(See page 19)

Modbus
OptionsSwitch 3
terminal block
(See page 14)
(See page 14)

MS/TP
MS/TP header for terminal block
(See page 13)
FST-100
connection

Figure 1 FLG-MODBUS

6 Novar Controls Corporation. All Rights Reserved. LTBT-TM-FLGMDBS Rev. 0002

 Installation and Operations Guide | Key illustrations

1 1/8" (28mm) 3 1/4" (83mm)

1 7/16" (37mm)
3/16" (5mm)

24VAC

GND

FLG-MODBUS
ASSEMBLED IN USA
POWER STATUS
POWER: 24 VAC @ 24VAC - 1
0.5A MAX GND - 2
CLASS 2 CIRCUITS
ONLY
USE COPPER
EIA-232 / 485
CONDUCTORS ONLY STATUS (DB-9)
FOR INDOOR USE ONLY

LBL-FLG-MB-A
SUITABLE FOR PLENUM MOUNTING

MODBUS STATUS
TUX/MODBUS
STATUS SW2 = MS/TP MAC ADDR JP3
VALUE EIA-232
SW2 MODBUS
ON CONFIG.
1 1
2 2 JUMPER
3 4 1 2 3
4 8
4 3/4" (120mm) 5
6
16
32
7 64 EIA-232
EIA-485
MS/TP STATUS 4 5/16" (109mm)
SW3 MODBUS SETTINGS
SWITCH NUMBER
MS/TP OFF ON
STATUS 1 RTU ASCII
2 NO PARITY PARITY
SW3 3 ODD PARITY EVEN PARITY
4 9600 BAUD 4800 BAUD
5 STANDARD 1 STOP BIT
6 (NOT USED)
+
7 (NOT USED) MODBUS
-
(B) + - 3
EIA-485
(W) - - 4
OPEN ENERGY
MANAGEMENT
EQUIPMENT 5K05 +
(B) + - 5 MS/TP
OPTION MS/TP
(W) - - 6
+ -
MS/TP
-

1/2" (12mm)

Figure 2 FLG-MODBUS mounting dimensions

Novar Controls Corporation. All Rights Reserved. LTBT-TM-FLGMDBS Rev. 0002 7

Installation and Operations Guide | FLG-MODBUS

Figure 3 Typical Modbus EIA-232 and EIA-485 architectures with the FLG-MODBUS and
BACnet networks.

8 Novar Controls Corporation. All Rights Reserved. LTBT-TM-FLGMDBS Rev. 0002

 Installation and Operations Guide | Quick start setup

Quick start setup

Use the following table to help you install and configure the FLG-MODBUS.
The key steps are listed in order.
Table 2 Quick steps

Task See
1 Connect 24 VAC power to the FLG-MODBUS page 12

2 Connect the FLG-MODBUS to the BACnet network page 12

3 Connect to the Modbus network page 14

4 Map FLG-MODBUS data points to BACnet AVs and BVs page 17

5 Save mapped data to the BACtalk server page 18

6 Check Modbus communications page 19

7 Download a new ROC file if necessary page 20

Novar Controls Corporation. All Rights Reserved. LTBT-TM-FLGMDBS Rev. 0002 9

Installation and Operations Guide | FLG-MODBUS

Operational overview
The FLG-MODBUS is a BACnet-compliant device that installs between a
BACnet MS/TP network and a Modbus EIA-232 or EIA-485 network. The FLG-
MODBUS connects Modbus devicessuch as variable speed drivesto a
BACnet system, converting data from connected Modbus devices to BACnet AV
and BV objects.

The FLG-MODBUS has a capacity for 100 AV and 100 BV objectseach AV

and BV can be assigned to one Modbus data point. These assignments are
accomplished using the BACnet description property of the AV or BV object to
be mapped. The description property is an ASCII string.

On an EIA-485 network, up to 10 Modbus devices (with a valid address between

1-247) are supported on BACnet system. On an EIA-232 network, only one
Modbus device is supported.

No te The FLG-MODBUS allows you to use the modbus reserved addresses of

248-255. You can also scale Modbus data. See Appendix A: Syntax for
description string on page 21 for more information.

Data storage and backup

The FLG-MODBUS stores description string mappings in flash memory. Flash
memory retains these mappings through power cycles. The present-values of the
mapped AVs and BVs are stored in dynamic RAM. The FLG-MODBUS
monitors its current power level and saves this data in flash memory before
shutting down for any reason. When power is returned to the FLG-MODBUS, it
reads the data from flash memory and writes it to RAM.

You can clear all mappings and data from the FLG-MODBUS. See Clearing
Modbus object data on page 20 for more information.

Sequence of operations
When the FLG-MODBUS powers up, it checks to see if the real-time operating
code (ROC) file is valid. If the ROC file is not valid, the FLG-MODBUS waits
for a valid ROC file. If the ROC file is valid, the FLG-MODBUS runs the file.

After a valid ROC file is found, the FLG-MODBUS joins the MS/TP network
and begins scanning AV and BV description properties for Modbus mappings.

See Mapping Modbus data to AVs and BVs on page 17 for more information.

10 Novar Controls Corporation. All Rights Reserved. LTBT-TM-FLGMDBS Rev. 0002

 Installation and Operations Guide | Operational overview

System design and application

Performance of the FLG-MODBUS depends on the Modbus devices to which it
is connected. In theory, remote terminal unit (RTU) mode should allow higher
throughput because it requires fewer bytes per message. In practice, Alerton has
observed several Modbus devices that have poorer performance in RTU mode
than in ASCII mode because they insert a long delay before replying to RTU
messages.

Keep in mind that Modbus networks typically run at 9600 baud in message
transmission mode. At this baud rate, theoretical bandwidth is about 39 updates
per second for RTU mode and 17 updates per second for ASCII mode.

The presence of several Modbus slaves rather than a single slave has no effect on
performance.

Novar Controls Corporation. All Rights Reserved. LTBT-TM-FLGMDBS Rev. 0002 11

Installation and Operations Guide | FLG-MODBUS

Hardware installation and setup

This section describes installation of the FLG-MODBUS, covering requirements
for connecting the unit to the power supply, BACnet network, and the Modbus
network.

When mounting in an environmental air space as defined by NEC 300-22(c), the

FLG-MODBUS must be mounted in a fully enclosed metal enclosure or in a
fully enclosed nonmetallic enclosure, listed for intended use and having
adequate fire-resistant and low-smoke-producing characteristics.

Power supply
The FLG-MODBUS requires 24VAC power @ 5VA and is a half-wave device.
Terminals for connecting power are on the right side of the unit.

24VAC

FLG-MODBUS STATUS
LED

Ground
transformer

Figure 4 Power wiring

Connecting to the BACnet network

The FLG-MODBUS connects to any BACnet MS/TP network and operates as a
BACnet MS/TP master.

The FLG-MODBUS supports communication rates of 76.8 Kbps, 38.4 Kbps,

19.2 Kbps, 9.6 Kbps, 4.8 Kbps, and 2.4 Kbps and automatically synchronizes to
the communication rate of the MS/TP trunk.

12 Novar Controls Corporation. All Rights Reserved. LTBT-TM-FLGMDBS Rev. 0002

 Installation and Operations Guide | Hardware installation and setup

Setting the MS/TP MAC address with Switch 2

Set the MS/TP MAC address using SW2 DIP Switches on the FLG-MODBUS.
The FLG-MODBUS must have a unique MAC address in the range of 0-127
(0 is normally reserved for the global controller).
Table 3 DIP switch 2 values for MS/TP MAC address

Switch Value
1 1

2 2

3 4

4 8

5 16

6 32

7 64

Terminating MS/TP cabling

MS/TP cabling terminates to screw terminals on the lower right side of the FLG-
MODBUS.

FLG-MODBUS

MS/TP
LED

+ MS/TP
-
MS/TP

Figure 5 MS/TP wiring

Novar Controls Corporation. All Rights Reserved. LTBT-TM-FLGMDBS Rev. 0002 13

Installation and Operations Guide | FLG-MODBUS

Connecting to a Modbus network

The FLG-MODBUS can connect to either a two-wire EIA-485 Modbus network
or an EIA-232 Modbus network. Only one network type can be operational.

Select the network type using jumper JP3 on the FLG-MODBUS circuit board.
Set jumper pins 1 and 2 to select EIA-485 and jumper pins 2 and 3 to select EIA-
232. See Figure 6 on page 14.

FLG-MODBUS Cable

1 1
RX RX
6 6
2 2
TX TX
7 7
3 3
8 8
4 4
GND GND
9 9
5 5
EIA-232 enlarged
EIA-232
MODBUS
LED

EIA-485

JP3 (Located under the cover)

EIA-485 EIA-232

Figure 6 Modbus wiring

Setting Modbus protocol options

The FLG-MODBUS supports multiple Modbus network options. These options
are set using the options SW3 DIP switches on the unit circuit board.

Use the following table to set the Modbus protocol options using the DIP switch
bank labeled SW3.

Switch ON OFF
1 ASCII mode RTU mode

2 Send parity bit with data No parity

3 Send EVEN parity bit Send ODD parity bit

4 Send data at 4800 baud Send data at 9600 baud

5 1 stop bit Standard stop bits

No te Only one set of protocol options can be used on the Modbus network. All
Modbus devices must have the same settings. Additionally, the Modbus standard
requires one stop bit if parity is used and two stop bits if not. However, some
devices do not follow this standard, requiring one stop bit even if parity is not
used. Therefore, the Stop option forces one stop bit even if parity is not used.

14 Novar Controls Corporation. All Rights Reserved. LTBT-TM-FLGMDBS Rev. 0002

 Installation and Operations Guide | Connecting to a Modbus network

Using the aler-gateway-setup property The aler-gateway-setup property is a

standard ASCII string that displays the Modbus protocol settings the device
currently uses. The string is an Alerton proprietary BACnet property of the
device object that can be used to view or change protocol setups. The setup
property overrides the DIP switch settings on the unit.

CA U TIO N Using the aler-gateway-setup property to set protocol options may

cause the operational protocol of the FLG-MODBUS to differ from those
displayed by the DIP switches on the unit. This can cause confusion during
troubleshooting. Using the aler-gateway-setup property is therefore not
recommended.

The string is saved to flash memory so the device will operate according to the
string even after power is cycled to the FLG-MODBUS. The displayed string
always shows the actual options in use, whether set from the DIP switches or
from the string, so there is no way to tell what the string is that is stored in flash.
If in doubt about the last string sent, resend the desired string to the FLG-
MODBUS.

To return control to the DIP switches after using the setup property, send a blank
string to the aler-gateway-setup property. To return the FLG-MODBUS to the
clean state it was in when it was shipped from Alerton, see Clearing Modbus
object data on page 20 for more information.

The aler-gateway-setup property can be a maximum of 60 characters in any

order with commas between each field. Extra spaces are ignored and characters
are not case-sensitive.

[Baud=4800 | 9600], [Parity=None | Even | Odd], [Mode=ASCII | RTU],

[Stop=Standard | One]

Example: Baud=4800, Parity=None, Mode=RTU, Stop=Standard

! To set protocol options using the aler-gateway-setup property

1. In Edit mode, open the data display where you want to place a Modbus
aler-gateway-setup property.

2. From the Place Item menu, choose Prompted Property, and then click
the display where you want to place the item.
3. Double-click the item to view the Prompted Property Setup dialog box.

4. Click the command button beside the Property box to open the Object
Specification dialog box.

5. In the Device Instance field, type the device instance of the FLG-
MODBUS.
6. Specify the Object type as either AV or BV.
N ote You can currently only select the aler-gateway-setup property
for AV and BV type objects. (You will change this object type in step 9
below.)

7. Specify the device instance where the object resides.

8. From the Property list, choose aler-gateway-setup.

Novar Controls Corporation. All Rights Reserved. LTBT-TM-FLGMDBS Rev. 0002 15

Installation and Operations Guide | FLG-MODBUS

9. Change the object type to Device.

10. Click OK, and then click Close in the Prompted Property dialog box.

11. Resize the prompted item to the size you want, save the display, and
close the Display Editor.

12. Open the display for viewing.

N ote The property will initially show current DIP switch settings.

13. Click the command button for the prompted property you created.

14. In the Edit Property dialog box, under Value, type the string to send to
the device and overwrite the DIP switch protocol option settings.
N ote Overrides are maintained in flash memory. Overrides are deleted
with the mapping assignments if you power up with all DIP switches set
to ON.

15. Click OK.

N ote The aler-gateway-setup property is not saved as part of the

device properties. Any protocol options that are changed using the
gateway property will not be backed up to the Envision server during a
Point Data or Device Property Save.

16 Novar Controls Corporation. All Rights Reserved. LTBT-TM-FLGMDBS Rev. 0002

 Installation and Operations Guide | Connecting to a Modbus network

Mapping Modbus data to AVs and BVs

The FLG-MODBUS is a BACnet device that contains 100 AV and 100 BV
objects. These AVs and BVs do not have priority arrays. The present-value of
each AV and BV is either read from or written to points on the Modbus network.
Map each AV and BV to a single Modbus point using the BACnet description
property as described in Setting up data mappings below.

Assigning Modbus addresses

Modbus data points use an addressing format that combines a reference number
and a point address. For example, 0xxxx indicates reference 0 (zero), 1xxxx
indicates reference 1, and so on. The point address range is from 1 to 9999.
Therefore, 40010 is entered as reference 4 and address 10.

No te Some manufacturers bias the Modbus addresses by 1. That is, their point
addresses range 0-9999 instead of 1-9999. In these cases you need to assign their
register address +1. For example, to read their register 45, you would assign
register 44.

When you set up a data mapping, you specify the type of object in the BACtalk
system to use to map data. You also specify whether the item is intended for a
read-only input or whether it should be commanded from the BACnet system.

The reference type of the Modbus data determines how you need to map it (see
the table below). See Appendix A: Syntax for description string on page 21 for
more information.

Reference Type BACnet Remarks

(NX reference) Object
0x BV Can be set up as Input or Output.

1x BV Modbus read-only. Must be set up as Input.

3x AV (analog) Modbus read-only. Must be set up as Input.

4x AV (analog) Can be set up as Input or Output.

6x AV (analog) Can be set up as Input or Output.

No te A BV can be mapped to a reference type 3 or 4 to monitor bitmapped

quantities.

Setting up data mappings

Use the BACnet description property to assign a Modbus data point to a BACnet
data object. Each BACnet object can be assigned to read data from or write data
to a single Modbus data point.

The description property is a standard ASCII text string. If the FLG-MODBUS

detects an error in the description string, it reports the error as a text string
appended to the front of the description when the string is read. The string will
say No String if it does not contain any mapping. See Appendix C: Error
indicators on page 26 for more information about errors.

! To map an AV or BV to a Modbus data address

1. In Edit Mode, open the data display, where you want to place Modbus
data mappings.

Novar Controls Corporation. All Rights Reserved. LTBT-TM-FLGMDBS Rev. 0002 17

Installation and Operations Guide | FLG-MODBUS

2. From the Place Item menu, choose Prompted Property, and then click
the display where you want to place the item.

3. Double-click the item to view the Prompted Property Setup dialog box.

4. Click the command button beside the Property box to open the Object
Specification dialog box.
5. In the Device Instance field, type the device instance of the FLG-
MODBUS and select the object type (AV or BV) and instance of the AV
or BV you want to use to map Modbus data.

6. From the Property list, choose description.

7. Click OK in the Object Specification dialog box, and then click Close in
the Prompted Property dialog box.

8. Repeat steps 2 through 7 for all data points you want to map.
9. Resize the prompted item to the size you want, save the display, and
close the Display Editor.

10. Open the display for viewing.

11. Click the command button for the prompted property you created.

12. In the Edit Property dialog box, under Value, type a mapping value for
the description property according to the guidelines in Appendix A:
Syntax for description string on page 21.

13. Click OK.

The data mapping is saved to the FLG-MODBUS, and the
present_value displayed in BACtalk operator workstation software for
that point now reflects the value of the Modbus point.
N ote When finished making assignments, use Device Manager to save
point data. On subsequent downloads, this data is available from the
hard disk, eliminating the need to reassign it.

! To save point data

N ote You must add the FLG-MODBUS device instance to Device
Manager to access point mapping. You may need to scan for the FLG-
MODBUS and add it to your list of devices if its not already there.
1. Open Device Manager in your BACtalk operator workstation software.

2. In the list of devices, select the FLG-MODBUS.

18 Novar Controls Corporation. All Rights Reserved. LTBT-TM-FLGMDBS Rev. 0002

 Installation and Operations Guide | Connecting to a Modbus network

3. In the Device Manager dialog box, click Save.

4. In the Save Data from Device to Disk dialog box, select Point Data, and
then click Save.
The mapped point data in the FLG-MODBUS is saved to the BACtalk
server.

! To download point data

N ote You can download backed up point data from disk only if the
device already exists.
1. Open Device Manager in your BACtalk operator workstation software.

2. In the list of devices, select the FLG-MODBUS.

N ote You may need to scan for the FLG-MODBUS and add it to your
list of devices if its not already there.

3. In the Device Manager dialog box, click Send.

4. In the Send Data from Disk to Device dialog box, select Point Data, and
then click Send.
The mapped point data previously saved on the BACtalk server is sent
to the FLG-MODBUS.

Checking Modbus communications

After you have set up BACnet network communications, Modbus
communications, and assigned mappings, you can check the status of
communications using the diagnostic and status LEDs on the FLG-MODBUS.
There are 3 LEDs on the FLG-MODBUS: Status, MS/TP, and Modbus. These
LEDs indicate the current status of communications according to the following
table.

LED Description
Status Indicates that the unit has power and is running a valid ROC file. Follows
the 2.5 second flash pattern.

MS/TP Flashes once every 2.5 seconds when power is on.

Flashes twice every 2.5 seconds while receiving valid MS/TP headers.
That is, at least one other MS/TP master device is online.
Flashes three times every 2.5 seconds when it receives a valid message.

Modbus Flashes once every 2.5 seconds when a Modbus message has been sent
but no reply received.
Flashes twice every 2.5 seconds when a Modbus message has been sent
and a valid reply has been received.

Novar Controls Corporation. All Rights Reserved. LTBT-TM-FLGMDBS Rev. 0002 19

Installation and Operations Guide | FLG-MODBUS

If you experience problems, check the following:

Wiring connections (including terminating resistors for EIA485) are

sound.
Jumper 3 is set correctly.
RTU/ASCII protocol selection is appropriate.
Parity and baud rate of FLG-MODBUS matches remote device
requirements.
The proper Modbus slave address, reference type, and register/coil
address are referenced.

Clearing Modbus object data

If you need to clear the data in the FLG-MODBUS and return it to a known
configuration state, use DIP SW2 on the unit. If all DIP switches are set to ON
when you turn the unit on, the FLG-MODBUS automatically clears all AV and
BV descriptions, sets the present-value of all AVs to 0.0, and sets the present-
value of all BVs to Inactive. The FLG-MODBUS will now respond to DIP
switch settings.

Downloading a ROC file

If a ROC file is not functioning properly, you can download a new one using
your BACtalk operator workstation software. The FLG-MODBUS ROC file
(VLC1002.BIN) must be in the System subfolder of your BACtalk installation
folder.

! To download a new ROC file

1. Open Device Manager in your BACtalk operator workstation software.

2. In the list of devices, select the FLG-MODBUS.

N ote You may need to scan for the FLG-MODBUS and add it to your
list of devices if its not already there.
3. In the Device Manager dialog box, click Send.

4. In the Send Data from Disk to Device dialog box, select ROC (OMF/
BIN), and then click Send.

20 Novar Controls Corporation. All Rights Reserved. LTBT-TM-FLGMDBS Rev. 0002

 Installation and Operations Guide | Appendix A: Syntax for description string

Appendix A: Syntax for description string

The description string is a BACnet property of each AV and BV object. It is used
to assign a Modbus data point to a BACnet data object.

Commas are required between each argument with no spaces between

items.
N ote Use a space instead of a comma between the last argument and
the descriptor.
Use uppercase or lowercase letters.
Each string can contain a maximum of 60 characters.

N ote You do not need placeholder commas for undesired options; list
only the options you want.
In most cases, this information is provided by the Modbus device manufacturer
as part of the data point assignment.

I | O | W | T | A, <Slave Address>, <Reference>, <Register or Coil Number>

[, <Extended Memory File Number>] [, F | Fb | Fl] [, L | Lb | Ll] [, BU<nn>] [,
<Real Number1>] [,<Real Number2>] <Descriptor>

Novar Controls Corporation. All Rights Reserved. LTBT-TM-FLGMDBS Rev. 0002 21

Installation and Operations Guide | FLG-MODBUS

Argument Explanation
I|O|A|W|T Message type. Determines if the value will be an input (read-only) or
output (writable). The Modbus reference type determines acceptable
entries.
I Read-only input from Modbus to BACtalk. The Modbus value is read
into BACtalk and cannot be commanded through the AV or BV present-
value property. The FLG-MODBUS performs a round-robin poll of all
input points to request values from the Modbus equipment.
O Verified output from BACtalk to Modbus using message code 6
(Preset Single Register). The Modbus value is writable through the AV or
BV present-value property. On change-of-state and during round-robin
poll, the Modbus data is read and compared against BACtalk data. A
write occurs to the Modbus point only if the compared values are
different.
Type O should be used for output points unless problems are
encountered and especially if the Modbus device stores its data in
EEPROM. This will eliminate unnecessary writes to EEPROM.
Note Use types A, T, and W when the Modbus device has problems with
type O operation.
A Verified multiple register output from BACtalk to Modbus. The Modbus
value is writable through the AV or BV present_value property. Behaves
precisely like the O point, but A values are written on the Modbus side
using the "Preset Multiple Registers" message (Modbus message code
16).
W Unverified output from BACtalk to Modbus using message code 6
(Preset Single Register). The Modbus value is writable through the AV or
BV present-value property. The value is not read from the Modbus side or
compared to the BACtalk value. A write occurs on BACtalk change-of-
state and during round-robin poll of Modbus values. Note: The W option
was added primarily for compatibility with Liebert Modbus systems, which
may flag points internally as NULL on reset. This caused an error
message to occur when the FLG-MODBUS attempted to read them for
comparison using the O point.
T Unverified multiple register output from BACtalk to Modbus. The
Modbus value is writable through the AV or BV present-value property.
Behaves precisely like the W point, but T values are written on the
Modbus side using the "Preset Multiple Registers" message (Modbus
message code 16). Developed primarily for Triatek applications.

<Slave Specifies the Modbus slave number where the data originates. Range is
Address> 1247.

<Reference> Specifies the Modbus reference type. One digit. Acceptable values are 0,
1, 3, 4, or 6.
NOTE: The number in parenthesis below is the Modbus function code.
See Appendix B: Modbus function codes on page 25 for more
information.
For operation I: 0=read coil status (binary) (1), 1=read input status
(binary) (2), 3=read input register (analog) (4), 4=read holding register
(analog) (3), 6=read general reference (analog) (20).
For operation O: 0=read coil status (1) then write (5), 4=read holding
register (3) then write (6), 6=read general reference (20) then write (21).
For operation A: 0=read coil status (1) then write (15), 4=read holding
register (3) then write (16), 6=read general reference (20) then write (21).
For operation W: 0=write coil status (5), 4=write holding register (6)
For operation T: 0=write coil status (15), 4=write holding register (16)

Register or Coil Specifies the Modbus register or coil address. Range is 19999.

22 Novar Controls Corporation. All Rights Reserved. LTBT-TM-FLGMDBS Rev. 0002

 Installation and Operations Guide | Appendix A: Syntax for description string

Argument Explanation
<Extended Omit unless Reference is set to 6. When the reference type is set to 6,
Memory File File Number must specify a file or group number in the range 09999.
Number>
(optional)

F | Fb | Fl Optional floating point designation to support the reading and writing of

(optional) floating point values when interfacing to Modbus equipment that stores
such values in two consecutive Modbus register addresses. The F
designator can only be used with AV objects.
F When F is appended to the I message-type indicator, the Modbus
register reference type must be 3 or 4 (not 6). For example, the
description string "I,1,4,206,F Sample float" requests a floating point
value from slave #1, register addresses 40206 and 40207.
When F is appended to an output message type (O,A,W,T) the FLG-
MODBUS writes the BACnet AV floating point value to two consecutive
Modbus registers, beginning with the register specified in the gateway
string.
Note: The original Modbus standard did not support floating point.
Modbus registers normally contain 2 bytes of data. Floating points
contain 4 bytes. Some manufacturers store these 4 bytes in Little
endian order, others use Big endian order. Try swapping the order If
you are not getting valid floating point data.
F= Fb = Big endian
Fl = Little endian

L | Lb | Ll Optional long integer point designation to support reading or writing of

(optional) 32-bit integers when interfacing with Modbus equipment that stores such
values in two consecutive Modbus register addresses. The L designator
can only be used with AV objects.
When L is appended to the I message-type indicator, the Modbus register
reference must be 3 or 4. For example, the description string "I,1,4,206,L
Sample long int" requests a long integer value from slave #1, register
addresses 40206 and 40207.
When L is appended to an output message type (O,A,W,T) the FLG-
MODBUS converts the BACnet AV floating point value to a long integer
and writes it to two consecutive Modbus registers, beginning with the
register specified in the gateway string.
NOTE: The original Modbus standard did not support long integers.
Modbus registers normally contain 2 bytes of data. Long integer points
contain 4 bytes. Some manufacturers store these 4 bytes in Little
endian order; others use Big endian order. Try swapping the order If
you are not getting valid point data.
L= Lb = Big endian
Ll = Little endian

BU Bit Unpack. Some Modbus devices send bit-packed data. If the BU field
is present, the bit number specified in nn (0-15) is extracted and used as
(optional)
the present-value of the BACnet object. Use only for message type I
(read-only).

<Real Number Any real number, which will be used to scale Modbus data. See Scaling
1> point data later in this section.
(optional)

<Real Number Any real number, which will be used to scale Modbus data. See Scaling
2> point data later in this section.
(optional)

<Descriptor> Optional (recommended) text description.

(optional)

Novar Controls Corporation. All Rights Reserved. LTBT-TM-FLGMDBS Rev. 0002 23

Installation and Operations Guide | FLG-MODBUS

Scaling point data

Use the two Real Number arguments in the description string to scale Modbus
data. You can scale Modbus data for AV objects only. The first Real Number
argument is applied first. Data sent to and from the Modbus device is a 16-bit
integer with a range of 1 to 65535. The manufacturer of the device should
provide the required math conversion. The format of the Real Number argument
is: * | + | - 123.456E-12 Where at least one of the symbols *, +, or - must
appear. The following table shows valid combinations and their meaning.

Symbol Meaning
* Means multiply by a positive number
*+ Means multiply by a positive number
*- Means multiply by a negative number
+ Means add a positive number
- Means subtract

E and E+ are optional and followed by a positive power to 10 exponent

E- is optional and is followed by a negative power to 10 exponent
N ote Exponent is limited to the range of +/-38

Examples
The following syntax examples show how scaling works for different situations.

Example 1) Modbus register 4 0032 reports sensed pressure 0-4095. You want
AV 15 to read as 0-300 psi. The Modbus slave address is 44.

AV 15 = ModbusValue * 300/4095
300/4095 = 0.07326.

Solution 1) The Description for AV 15 should be I, 44, 4, 32, *0.07326.

Example 2) Modbus register 44 now reports 820-4095 as gpm ranges 0-600.

The range is 600/(4095 -820) = 0.1832.
The offset = 820.

Solution 1) The Description for AV 15 should now be I, 44, 4, 32, -820.0,

*0.1832.

24 Novar Controls Corporation. All Rights Reserved. LTBT-TM-FLGMDBS Rev. 0002

 Installation and Operations Guide | Appendix B: Modbus function codes

Appendix B: Modbus function codes

The function codes used by the FLG-MODBUS are provided here as a reference
onlyyou should not need them.

Function Code Description

01 Read Coil Status. Returns the status of a number of outputs in the
slave device. The FLG-MODBUS always sets the number of coils
read as one. The data is either ON or OFF.

02 Read Input Status. Returns the status of a number of inputs in the

slave device. The FLG-MODBUS always sets the number of inputs
read as one. The data is either ON or OFF.

03 Read Holding Registers. Returns the 16-bit data value of a number

of holding registers in the slave device. The FLG-MODBUS always
sets the number of registers read as one.

04 Read Input Registers. Returns the 16-bit data value of a number of

input registers in the slave device. The FLG-MODBUS always sets
the number of inputs read as one.

05 Force Single Coil. Writes to a single coil (binary output). The data is
either ON or OFF.

06 Preset Single Register. Writes a 16-bit data value to a single data

register in the slave device.

15 Force Multiple Coils. Writes to a range of coils. The data is either ON

or OFF. The FLG-MODBUS always sets the number of coils written
to as one. Some slaves will not accept function 05, so this function is
used instead if A or T is specified as the type.

16 Preset Multiple Registers. Writes multiple 16-bit data values to a

sequence of data registers in the slave device. The FLG-MODBUS
always sets the number of register written to as one. Some slaves
will not accept function code 06 so this function is used instead if A
or T is specified as the type.

20 Read General Reference. Returns the 16-bit data values of a

number of file-group references in the slave device. The FLG-
MODBUS always sets the number of references read as one.

21 Write General Reference. Writes a number of 16-bit data values to a

group of file-group references in the slave device. The FLG-
MODBUS always sets the number of references written as one.

No te See page 22 for more explanation about the Modbus Reference type (0, 1,
3, 4, or 6).

Novar Controls Corporation. All Rights Reserved. LTBT-TM-FLGMDBS Rev. 0002 25

Installation and Operations Guide | FLG-MODBUS

Appendix C: Error indicators

The FLG-MODBUS annunciates errors through the operator workstation and
through standard BACnet properties.

BACnet error indications

The FLG-MODBUSs AV and BV objects use the standard BACnet reliability
property to reflect their current status. If an AV or BV has a valid Modbus
description string mapping and is communicating correctly with a Modbus unit,
the reliability property reads NO_FAULT_DETECTED. If the description string
is invalid or the Modbus unit is not responding for any reason, the reliability
property reads UNRELIABLE_OTHER. In this instance, the BACnet status-
flags property also reads FAULT.

No te You can use the reliability property to generate BACnet alarm

notifications. See your BACtalk operator workstation software manual for
instructions on setting up alarm notifications.

Operator workstation error indications

The FLG-MODBUS provides visual feedback of errors. As each description
string is mapped and assigned, the FLG-MODBUS verifies the validity of the
string. If the string is invalid, the FLG-MODBUS adds an error indicator to the
beginning of the description string to alert the user. These error indicators are
described in the following table.

Error Indicator Description

Error 2, Slave Address Indicates the string contains a slave address that is 0 (zero)
which is the Modbus broadcast address.

Error 3, Reference Indicates the reference number is either invalid or is incorrect

Number for the selected message type. For example, you cannot write
to a reference type 1 or 3.

Error 4, Register/Coil Indicates the register/coil number is invalid.

Number

Error 5, File/Group Indicates the file/group number is invalid.

Error 6, Floating not Indicates the floating point option is not allowed. The floating
Allowed point option is only allowed with reference types 3 or 4.

Error 7, RN1 Indicates the first optional real number does not contain a
recognizable real number.

Error 8, RN2 Indicates the second optional real number does not contain a
recognizable real number.

Error 9, Bit Unpack Indicates the bit unpack field contains an invalid bit mask.

Error 10, Long Integer Indicates the long integer option is not allowed.
not Allowed

No te If the Operation field does not begin with I, O, A, W, or T, the string is

rejected and the description string is replaced with No String.

26 Novar Controls Corporation. All Rights Reserved. LTBT-TM-FLGMDBS Rev. 0002

 Installation and Operations Guide | Appendix C: Error indicators

Using the aler-diagnostics property

Place the aler-diagnostics property on a data display to view diagnostic reports
returned by the FLG-MODBUS. The aler-diagnostics property has the following
fields:

Sent: nnnnn
Rcvd: nnnnn
Mapped: nnn

The Sent and Rcvd fields show a rolling count of Modbus messages that were
sent and received. This is useful to determine whether the FLG-MODBUS is
sending messages and whether the Modbus slave is responding.

The Mapped field is a number between 0 and 200 showing the number of valid
point mappings in the FLG-MODBUS.

Novar Controls Corporation. All Rights Reserved. LTBT-TM-FLGMDBS Rev. 0002 27

 Novar Controls Corporation. All Rights Reserved. LTBT-TM-FLGMDBS Rev. 0002