Part Number: 2060-2136 (replaces 0600-0056-0015)
WATLOW®, ASPYRE®, EZ-ZONE® and INTUITION® are registered trademarks of Watlow Electric Manufacturing,
Incorporated
Modbus® is a registered trademark of Schneider Automation, Incorporated.
Using Watlow Products with SpecView 2 Addendum to SpecView Manual
Chapter 1: Introduction
2
1
SpecView is a powerful and easy-to-use Supervisory Control and Data Acquisition (SCADA) software
package. The purpose of this addendum is to quickly get you up and running using SpecView with
Watlow controllers. Chapter 2 provides a brief explanation of concepts that may not be familiar to first
time users of SpecView. Basic familiarity with these concepts is assumed in Chapter 3 which provides
procedures for getting Watlow controllers communicating with SpecView. Chapter 4 provides detailed
information regarding addressing and describes features specific to Watlow controllers.
This addendum supports SpecView version 3.
Additional Resources
In addition to this addendum the following resources are available for learning about SpecView and
other products available from Watlow:
•SpecView User Manual—available on the SpecView installation disk and at Watlow.com
navigate to Resources and Support, Technical Library: User Manuals and search on Keyword:
SpecView.
•SpecView Secrets Video Tutorials—available at Watlow.com navigate to Resources and Support,
Technical Library: Tutorials and Training and search on Keyword: SpecView.
•SpecView Frequently Asked Questions—available at Watlow.com navigate to Resources and
Support, Technical Library: Tutorials and Training and search on Keyword: SpecView.
•SpecView Software Download—the latest version of SpecView is always available at
Watlow.com navigate to Resources and Support, Technical Library: Software and Demos and
search on Keyword: SpecView.
•SpecView Software Field Upgrade Order Form—guides you through the process of adding
features to a copy of SpecView you already own. Get the form at Watlow.com navigate to
Resources and Support, Technical Library: Software and Demos and search on Keyword:
SpecView.
Chapter 2: About Setting up
Communications
The following sections provide information to help you understand how to set up communications
between SpecView and Watlow controllers.
Instrument Templates and Protocols
SpecView includes support for hundreds of different devices. The protocol drivers and instrument
templates included with SpecView tell it how to communicate with specific devices. You will need to
choose the appropriate templates whenever you want to automatically or manually set up
communications between SpecView and a device.
Using Watlow Products with SpecView 3 Addendum to SpecView Manual
There are many instrument templates grouped by communication protocol and product family that
Support for F4T and D4T
outputs in the flex modules
Support for basic operation
profiles.
Supports reads and writes to
Instruments on page 46.
Watlow EZ-ZONE
Standard Bus
EZ-ZONE PM, EZ-ZONE RM,
EZ-ZONE ST
Allows saving profiles as
Programmer ordering option.
Anafaze 16 Loop
16CLS, CLS216, 16MLS, MLS316
Anafaze 32 Loop
32MLS, MLS332
Anafaze 8 Loop
4CLS, CLS204, 8CLS, CLS208
CLS204, CLS208, CLS216,
MLS316, MLS332
Ramp/Soak Profile
programming and operation
Anafaze/AB
ANAFAZE
32MLS
Proprietary Anafaze protocol
support Watlow products. The table below lists these template groups, protocols and the Watlow models
supported by each.
Template Group Protocol(s) Supported Watlow Models Notes
Watlow F4T & D4T
Watlow Modbus
Watlow Assembly
Watlow F4
Programmer
®
Modbus
Modbus
Standard Bus
Modbus
RTU
®
TCP
®
RTU
F4T with INTUITION
D4T with INTUITION®
®
ASPYRE
EZ-ZONE
EZ-ZONE ST, SERIES 96, 97, SD
MICRODIN, POWER SERIES,
986, 987, 988, 989
SERIES F4 Ramping
F4T with INTUITION
D4T with INTUITION
EZ-ZONE PM, EZ-ZONE RM
SERIES F4 Ramping
Power Controllers
®
PM, EZ-ZONE RM,
®
functions and inputs and
parameters in EZ-ZONE
products. See
Modbus
. Limited support for
43
programming SERIES F4
16 or 32 contiguous floatingpoint values. Intended to
minimize update time for
measurements when used
with the user-configurable
communication assemblies.
Watlow Assembly
See
Recommended for EZ-ZONE.
recipes. Requires Series F4
Standard firmware option only
EZ-ZONE
®
Instruments on page
Anafaze Ramp/Soak
Using Instruments from More than one Group or Protocol
The templates in the groups listed above that support Modbus® RTU on serial communications ports are
compatible with each other. Similarly the templates that support Modbus® TCP used over Ethernet are
compatible with each other. SpecView allows protocol-compatible templates to be used on the same
port, but you will need to help SpecView by instructing it when to do so. When there are controllers
connected to the same port that require instrument templates from different groups, you will scan once
for each of those groups to automatically detect the various devices.
If your configuration requires communicating with controllers supported by different protocols via serial
communications ports, each protocol must have its own network connected to SpecView via a separate
communications port. Support for multiple communication ports is an ordering option for SpecView,
and is field upgradeable.
Automatic and Manual Configuration
SpecView can automatically detect and set up communications with controllers. However, in some cases
it may be necessary to manually configure SpecView. This method is particularly useful if you want to
create screens and configure SpecView prior to receiving your controllers. Projects that were created
automatically can be updated by testing the communications network for new controllers. It is also
Using Watlow Products with SpecView 4 Addendum to SpecView Manual
possible to manually add or remove controllers from any configuration whether it was created
automatically or manually. This addendum contains procedures for automatically and manually
configuring communications for the various networking options supporting Watlow controllers.
SpecView can automatically detect F4T and D4T data loggers controllers using Modbus® TCP or
Modbus® RTU and EZ-ZONE controllers using the Standard Bus protocol. When using Modbus® with
EZ-ZONE controllers create the configuration manually.
Naming Instruments
It is useful to name instruments such that you can easily relate what you see on the screen in SpecView
to your equipment and processes. You might want to use a name that:
• Indicates the controller’s function in the process
• Indicates the controller’s location in the panel
• Includes network information such as port and address
When you create a project or add instruments to one by automatically detecting controllers, SpecView
prompts you to name the instruments as it adds them. You must name any instruments that you add
manually. You can change an instrument’s name whenever you like. However, changing an instrument’s
name makes logged data associated with the old name inaccessible going forward; it is best to name
instruments up front.
Saving Settings in Non-Volatile Memory
Some Watlow controllers protect their non-volatile memory from being worn out prematurely due to
excessive use that may occur when communicating with devices such as a PLC that send the same
settings to a controller many times a second. In these controllers, the settings received via
communications can be held in volatile memory that is cleared when the controller is turned off. Since
SpecView will typically send parameter settings to a controller only when you edit a parameter on the
screen, for your convenience you can set the controller to routinely save the parameter settings that
come through communications in non-volatile memory. That way the values you set are saved even
when the controller is powered down. Consult the controller manual for the appropriate parameter,
typically called, “Non-Volatile Save”.
Using F4T Controllers and D4T Data Loggers
The instruments in the Watlow F4T & D4T group support standard and optional features in in F4Ts and
D4Ts as well as the flex modules those devices are set to expect. For details see F4T Instruments on
page 29.
Automatic Detection of F4Ts and D4Ts
When automatically detecting a network with the Watlow F4T & D4T group, SpecView reads the part
number of the F4T or D4T and adds the appropriate instruments for features including control loops,
cascade loops, profiles and alarms. Additionally, an instrument is added for each flex module the F4T or
D4T is configured to expect.
Additional Instruments Available with the Watlow F4T Driver
Because F4Ts and D3Ts offer many additional functions such as math, logic, timers and counters that
may not all be used in the application, other instruments may be manually added to a configuration to
gain access to the values and settings associated with these features.
Using Watlow Products with SpecView 5 Addendum to SpecView Manual
Using EZ-ZONE Controllers with Standard Bus
When automatically detecting a Standard Bus network with the Watlow EZ-ZONE Standard Bus driver,
SpecView reads each device’s part number and adds the appropriate instruments. For the details see EZ-ZONE Standard Bus Instruments on page 30.
Note! Run the 32-bit version of SpecView for compatibility with the Watlow EZ-ZONE Standard Bus
driver. This driver is not supported by the 64-bit version of SpecView.
Using EZ-ZONE Controllers with Modbus®
To configure SpecView to communicate with EZ-ZONE products via Modbus® you will select and add
appropriate instruments manually. For each instrument you must determine the correct address string.
The address string depends on the type of network and its configuration. You will add as many copies of
the instrument as needed to allow access to the desired controller features. For example, to access all
four analog inputs in an EZ-ZONE RM Control Module, you will add four EZ-ZONE Analog Input
instruments.
SpecView Instruments Supporting EZ-ZONE Devices via Modbus®
The tables in this section list the instruments that may be used with each EZ-ZONE product. Additional
tables in the EZ-ZONE Modbus® Instruments section on page 43 list each parameter included in these
instruments. Review the supported parameters carefully and determine whether they allow you to
develop a project that meets your requirements. Standard Bus communications provides access to many
more EZ-ZONE controller parameters.
Simplified Address Strings in SpecView Version 3
In previous versions of SpecView the “address string” included the controller address, number of
decimal places to display and the register offset. As of version 3 these are now entered in separate fields
in SpecView which makes setting up instruments more straight forward.
Controller or Gateway Slave Address
For Modbus® TCP each controller or gateway is identified by its TCP/IP Address. EZ-ZONE controllers
and gateways will respond to any valid setting (1 to 247) for the Slave Address. It is not necessary to set
each device to a unique Modbus® address, but each must have a unique and appropriate IP address. See
the figure below.
Using Watlow Products with SpecView 6 Addendum to SpecView Manual
For Modbus® RTU specify the controller or gateway’s Modbus® Slave Address (1 to 247). This is set in
Data Map 1 via RUI Only1
Data Map 22
First
Address
First
Address
EZ-ZONE Alarm
1 to 2
1480
50
1450
60
EZ-ZONE Analog Input
1 to 2
360
160
360
90
EZ-ZONE Control Loop
1
N/A
N/A
1750
N/A
EZ-ZONE Communications
1
2418
N/A
2060
20
EZ-ZONE Current
1
1120
N/A
1240
N/A
EZ-ZONE Digital I/O
1 to 6
880
30
940
30
EZ-ZONE Limit
1
680
N/A
720
N/A
EZ-ZONE Profile (Map 1)**
1 to 4
6070
500
N/A
N/A
EZ-ZONE Profile (Map 2)**
1 to 4
N/A
N/A
4000
1000
EZ-ZONE Profile (ST Map 1)
1 to 4
2870
800
N/A
N/A
EZ-ZONE Profile Operation
1
2720
N/A
3800
N/A
EZ-ZONE Set Points
1
2160
N/A
1890
N/A
the controller or gateway’s Setup Communications menu. Each controller or gateway on the network
must have a unique Modbus® address. See the figure below.
Decimal Places
Specify zero (0) to display whole numbers for parameters such as process variable and set point. Specify
one (1) to display these parameters with tenths precision, two (2) to display hundredths and so on. Valid
settings range from zero (0) to four (4).
Register Address Offset
The register address offset is the sum of the First Instance Address for the specific EZ-ZONE product,
any applicable Instance Offsets and the Gateway Offset, if any. The Gateway Offset is set by the user
when the RUI Gateway or RM Access Module gateway is configured. The First Instance Address and
Instance Offsets depend on the controller’s data map setting and are supplied in the tables below for
each instrument and product.
Gateway Offset
Be careful not to set up instruments that attempt to read Modbus® registers that are mapped over by the
configuration of the gateway.
Register Addresses and Offsets for EZ-ZONE ST
Instrument Instances
Instance
Instance
Offset
Instance
Instance
Offset
1
Supported only via EZ-ZONE RUI Gateway.
2
Available with firmware version 4.0 or later.
Using Watlow Products with SpecView 7 Addendum to SpecView Manual
Register Addresses and Offsets for EZ-ZONE PM
Data Map 1
Data Map 2
First
Address
First
Address
EZ-ZONE Alarm
1 to 4
1480
50
1880
60
EZ-ZONE Analog Input
1 to 2
360
80
360
90
EZ-ZONE Communications
1 or 2
2490
20
2970
20
EZ-ZONE Control Loop
1 to 2
1880
70
2360
70
EZ-ZONE Current
1
1120
N/A
1360
N/A
EZ-ZONE Digital I/O
1 to 12
880
30
1000
30
EZ-ZONE Limit
1
680
N/A
720
N/A
EZ-ZONE Profile (Map 1)
1 to 4
2570
500
N/A
N/A
EZ-ZONE Profile (Map 2)
1 to 4
N/A
N/A
4500
1000
EZ-ZONE Profile Operation
1
2520
N/A
4340
N/A
EZ-ZONE Set Points
1 to 2
2160
80
2640
80
First
Address1
EZ-ZONE Alarm
1480
EZ-ZONE Analog Input
360
EZ-ZONE Control Loop
1880
EZ-ZONE Set Points
2160
First
Address1
EZ-ZONE Alarm
1480
EZ-ZONE Analog Input
360
EZ-ZONE Limit
680
First
Address
EZ-ZONE Alarm
1 to 8
1740
60
EZ-ZONE Analog Input
1 to 4
360
90
EZ-ZONE Communications
1
2830
N/A
EZ-ZONE Control Loop
1 to 4
2220
70
EZ-ZONE Current
1 to 4
1380
50
EZ-ZONE Digital I/O
1 to 12
1020
30
EZ-ZONE Limit
1 to 4
720
30
EZ-ZONE Profile (Map 2)
1 to 25
5440
1000
EZ-ZONE Profile Operation
1
5280
N/A
EZ-ZONE Set Points
1 to 4
2500
80
EZ-ZONE Sub Routine
1 to 15
30440
860
Instrument Instances
Instance
Instance
Offset
Register Addresses for EZ-ZONE Express Controller
Instrument
1
PM Express has only one instance each.
Instance
Instance
Instance
Offset
Register Addresses for EZ-ZONE Express Limit
Instrument
1
PM Express has only one instance each.
Instance
Register Addresses and Offsets for EZ-ZONE RMC Modules
Instrument Instances
Instance
Instance
Offset
Using Watlow Products with SpecView 8 Addendum to SpecView Manual
Register Addresses and Offsets for EZ-ZONE RME Modules
First
Address
EZ-ZONE Alarms
1 to 8
1440
60
EZ-ZONE Communications
1
2170
N/A
EZ-ZONE Digital I/O
1 to 24
360
30
First
Address
EZ-ZONE Alarms
1 to 24
2660
60
EZ-ZONE Analog Input
1 to 16
380
90
EZ-ZONE Communications
1
6510
N/A
EZ-ZONE Control Loop
1 to 16
4100
70
EZ-ZONE Digital I/O
1 to 12
1820
30
EZ-ZONE Set Points
1 to 16
5220
80
First
Address
EZ-ZONE Alarms
1 to 16
2530
60
EZ-ZONE Analog Input
1 to 12
410
90
EZ-ZONE Communications
1
3500
N/A
EZ-ZONE Digital I/O
1 to 12
1850
30
EZ-ZONE Limit
1 to 12
1490
30
First
Address
EZ-ZONE Alarms
1 to 16
2500
60
EZ-ZONE Analog Input
1 to 16
380
90
EZ-ZONE Communications
1
3470
N/A
EZ-ZONE Digital I/O
1 to 12
1820
30
Instrument Instances
Instance
Instance
Offset
Register Addresses and Offsets for EZ-ZONE RMH Modules
Instrument Instances
Instance
Instance
Offset
Register Addresses and Offsets for EZ-ZONE RML Modules
Instrument Instances
Instance
Instance
Offset
Register Addresses and Offsets for EZ-ZONE RMS Modules
Instrument Instances
Instance
Instance
Offset
Address Example 1: Analog Input 1 in an EZ-ZONE ST via Modbus® RTU
For an EZ-ZONE ST communicating with SpecView directly (no gateway) via Modbus® RTU, use the
First Instance Address for the EZ-ZONE Analog Input, 360 to read analog input 1. If the controller’s
address on the 485 network is 2, set the following properties for the instrument:
• Slave Address: 2
• Offset: 360
Note that we must use data map 2 because data map 1 is not supported by SpecView for EZ-ZONE STs
without a gateway.
Address Example 2: Analog Input 2 in an EZ-ZONE ST via Modbus® RTU
For an EZ-ZONE Analog Input instrument supporting analog input 2 in the ST controller from example
1, set the following properties for the instrument:
• Slave Address: 2
• Offset: 450
Using Watlow Products with SpecView 9 Addendum to SpecView Manual
The offset is 450 because 360 is the address for the first analog input and you add the offset, 90, to reach
• EZ-ZONE PM Controller
• EZ-ZONE ST Controller
• EZ-ZONE ST Profiling
the second input.
Address Example 3: EZ-ZONE PM Controllers via an EZ-ZONE RUI Gateway with
Modbus® TCP
Consider three EZ-ZONE PM controllers configured for data map 2 and connected to an EZ-ZONE RUI
Gateway with the local/remote gateway offsets set to 0, 4000 and 8000 respectively. To determine the
register address offset for an EZ-ZONE Set Points instrument to support the second control loop in the
third EZ-ZONE PM, locate the First Instance Address and the Instance Offset. These are 2640 and 80
respectively. Add these together for second control loop and add the gateway offset for the third
controller: 2640 + 80 + 8000 = 10720. So the register address offset is 10720. Set the following
properties for this instrument:
• TCP/IP Address or Hostname: 10.3.37.105
• Slave Address: 1
• Offset: 10720
Keep in mind that with Modbus® TCP the EZ-ZONE PM will respond to any slave address.
EZ-ZONE Modbus® Profile Instruments
The instruments supporting programming profiles include 10 steps each. Therefore, the instance offsets
indicated above are ten times the instance offsets indicated for the steps in the controller manuals.
Old EZ-ZONE Modbus® Instruments
The following instruments are included in the Watlow Modbus® instrument group, but are no longer
described in this document. They are not maintained or tested for use with later versions. They are
provided for backwards compatibility only.
• EZ-ZONE PM Limit
• EZ-ZONE PM Profiling
Note: These instruments support data map 1 only.
• EZ-ZONE Gateway ST Controller
• EZ-ZONE Gateway ST Profiling
Using ASPYRE Power Controllers with Modbus®
Connect a 485 port on the PC to port 2 on the ASPYRE power controller via RS-485 Modbus RTU. To
configure SpecView to communicate with ASPYRE products via Modbus® RTU from the Watlow
Modbus group in the New Instruments list select and add one ASPYRE DT instrument manually per
power controller. Configure communications with each instrument with the information listed below.
• COM Port: the serial port to on the PC which the ASPYRE power controller is connected
• Baud Rate: per the setting of the ASPYRE RS-485 port to which the PC is connected
• EZ-ZONE PM Profiling
• Parity: Driver
• Slave Address: the address of the ASPYRE power controller on the 485 network (also known as
station address)
• Decimal Places: 0
• Modbus +1 override: not selected
• Offset: leave blank
• Extra: leave blank
Using Watlow Products with SpecView 10 Addendum to SpecView Manual
To create a configuration automatically:
1) For each F4T / D4T:
3
Chapter 3: Setup Procedures
The following sections provide procedures for establishing communications between SpecView and
Watlow controllers.
Automatically Detect an F4T or D4T
The following procedure guides you through the process of configuring SpecView to communicate with
Watlow F4T controllers and D4T data loggers via Modbus® TCP or Modbus® RTU. It is assumed that
the controllers are connected correctly via Ethernet or one or more of the computer’s serial
communications ports. To add a controller to an existing configuration, see Manually Set up or Modify a Modbus® RTU, 485 or 232 Network on page 20 or Manually Set up or Modify a Modbus® TCP Network
on page 24.
Modbus® RTU:
• Set all controllers to
the same baud rate
• Set each controller to a
unique Modbus
Modbus® TCP:
2) Launch SpecView
Address
• Set Parity to None.
• Set Modbus Word
Order to Low High
• Modbus Data Map: 1
• Set each controller to a
unique IP address.
• Make sure Modbus
TCP is enabled.
and click through
any informational
dialogs.
3) At the splash screen,
click Select/Create
Project…
Using Watlow Products with SpecView 11 Addendum to SpecView Manual
4) In the Projects
dialog click Test
5) Enter a name for the
7) For the Port to
Comms for New
Project.
project.
6) Click OK.
which the
controllers are
attached, under
Protocol choose the
Watlow F4T & D4T
template group.
8) For TCP/IP enter
Begin and End
addresses to limit
the range of
addresses scanned.
9) Click Start Scan.
Using Watlow Products with SpecView 12 Addendum to SpecView Manual
10) For each instrument
SpecView detects,
11) Once SpecView has
12) To scan another
14) To save the GDW:
enter a name and set
Decimal Places or
click OK to accept
the default settings.
scanned all the
addresses with F4T
controllers and D4T
data loggers, click
Stop or, if there are
more ports to scan,
click SkiptoNext
Port or Skip to
Next IP.
template group,
click Cancel and
repeat from step 7
above for the next
template group.
13) Click OK.
• From the File menu,
choose Save As.
• Enter a File name for
the GDW.
•Click Save.
Using Watlow Products with SpecView 13 Addendum to SpecView Manual
Automatically Detect a New Standard Bus, 485 or 232
To create a project automatically:
3) Launch SpecView.
5) In the Projects
Network
The following procedure guides you through the process of configuring SpecView to communicate with
Watlow controllers via Standard Bus, 232 and 485 serial communications. It is assumed that the
controllers are connected correctly to one or more of the computer’s serial communications ports. To
add a controller to an existing configuration, see Manually Set up or Modify an EZ-ZONE Standard Bus Network on page 17 or Manually Set up or Modify a Modbus® RTU, 485 or 232 Network on page 20.
1) Set all controllers to the same baud rate. (Not necessary for Standard Bus.)
2) Set each controller to a unique address or zone number.
Note! Use the 32-bit
version of
SpecView with the
Watlow EZ-ZONE
Standard Bus driver.
4) At the splash screen,
click Select/Create Project…
dialog click Test
Comms for New
Project.
Using Watlow Products with SpecView 14 Addendum to SpecView Manual
Loading...
+ 32 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.