Transcript Spyder® for Plant Control - Victor Distributing Controls Department

Momentum 2009
Spyder® for Plant Control
John Hutchey – Lou Jones
Spyder® for Plant Control – Description
• Overview
- Intended for contractors and distributors familiar with Spyder
programming
- Topics include:
 Multiple Spyders on a single piece of equipment
 Using the ZIO for local override capability
 Using auxiliary IO modules in conjunction with Spyders
 Using distributed control architecture for large plants
• Presenters
- John Hutchey
- Lou Jones
2
Multiple Spyder Approach
• Application
- Large control panel / dense IO count
- Point count exceeds that of a single Spyder
- Sequence of Operations requires more logic than is available in
a single Spyder
• Examples
- Built up AHU
- Boiler or chiller plant
3
Guidelines
• Keep IO and logic on the same Spyder
- Minimize the amount of data sent between devices
• AHU example
- Spyder #1 controls fans and dampers
- Spyder #2 controls temperature and humidity
4
Pros and Cons
• Advantages
- Significant hardware cost savings vs. typical plant controller
- Flexible IO count
 Mix and match Spyder models to match the IO required
- Single-tool engineering
 All programming performed with WEBsAXs
 Apps and macros interchangeable on small and large projects
5
Pros and Cons
• Perceived Disadvantages
- Fear of Lon bus failure
- Difficult to implement inter-controller communication
- Communication failure takes too long to detect
- No ability to override IO points
6
Lon Bus Failure Mitigation
• Use a second Lon bus for plant control
- Plant bus is electrically isolated
- Dedicated bus bandwidth available to plant Spyders
Plant Bus
7
Field Bus
Inter-Controller Communication
8
Network Variable
Network Variable
Software Output
Software Input
Source Point
Target Point
Inter-Controller Communication
• Mechanism
- Software Output – Sends data
- Software Input – Receives data
• Efficiency
- Group multiple points into a single NV
• Reusability
- Package Software Inputs/Outputs into reusable applications
9
Inter-Controller Communication
• New pre-built library of applications
- Download from the Buildings Forum Spyder Sample Apps
section
- Apps available with different point counts to fit most situations
 One digital/enum plus one analog values
 One digital/enum, one digital, and two analog values
 Five digital/enums and 3 analog values
10
How to Use
• Source Spyder
- Add ShareOut application to source Spyder’s control program
- Link points to its inputs
11
How to Use
• Target Spyder
- Add ShareIn application to target Spyder’s control program
- Link points from its outputs
12
How to Use
• Link Spyders
- Create a Lon link from source Spyder to target Spyder
13
How to Use
• Link Spyders
- Create a Lon link from source Spyder to target Spyder
- Change link type to Critical
14
How to Use
• Link Spyders
- Create a Lon link from source Spyder to target Spyder
- Change link type to Critical
- Perform a Bind
15
Communication Failure Detection
• Default failure detection time is 300 seconds
- Plant control will likely require a more timely response
• Alternative- Handle fail detection using program logic
- Use application logic to periodically update a sent value on the
source device
- Use application logic to monitor received value for changes on
the target device
16
Library Components
• Fail detect logic is already built in
• Source Spyder updates every five seconds
• Target Spyder detects failure after missing three
updates
• Timing is adjustable via NCIs
17
Library Components
• Dedicated comm fail point on each receiving app
• Also includes configurable delay for return to normal
18
How to Use
• Use COMM_FAIL in conjunction with other logic to
protect equipment on loss of communication
19
Live Demo
• Demonstration of data sharing and communication
failure detection
20
Overriding Points
• Goal: Modify programming to allow local override of IO
points via the TR70 wall module
• Method: Insert override logic between controlling block
and the IO block
21
Override Block
• This block sets its output to the highest priority input
that is not invalid.
22
TR70 Configuration
• Add a Value from Wall Module parameter.
• Be sure to configure:
- Default value NULL
- Allow null value option
23
Linking
• TR70 override is connected to a higher priority slot
than the PID.
• If TR70 value is invalid, the Override block will output
the PID value.
24
Auto Operation
• TR70 override is set to NULL
25
Auto Operation
• TR70 override is set to 90
26
Network Override
• You can also configure the application for Network and
Local override capability
- Use Network Setpoint parameter type
27
Network Override
• Override data value can be accessed by both the
Network and the Wall Module
- Last one in wins
28
Auxiliary IO Module Approach
• Application
- Project requires hardware overrides on outputs
- Logic requires status feedback when override is active
• Examples
- Central plant control
• Cautions
- Do not exceed the logic capacity of your Spyders
29
Auxiliary IO Module Approach
• XIO-4DO Capabilities
- Command NVI
- Feedback NVO
- Hand NVO
• XIO-4AO Capabilities
- Command NVI
- Feedback NVO
- Hand NVO
- Scaling NCI
30
How To – XIO4DO
• XIO-4DO command, feedback, and hand NVs are type
SNVT_switch
• This type of NV must be created using the Spyder NV
Configuration View
31
How To – XIO4DO
• Use the Add NV button to create a new NV
• Then select the type
- Network Variable Output to send a command to the XIO
32
How To – XIO4DO
• Set Guaranteed Periodic Refresh to TRUE
33
How To – XIO4DO
• Select Copy From, Standard, then SVNT_switch
34
How To – XIO4DO
• Set the Significant Event Notification to 1 for both the
state and value fields
35
How To – XIO4DO
• Click the OK button to save
36
How To – XIO4DO
• Highlight your new NV, then click the Show on
wiresheet as Points button.
37
How To – XIO4DO
• State and Value fields of the NV will now be available
for use in your application
38
How To – XIO4DO
• Switch to Wire Sheet View
- State and value software outputs are visible
39
How To – XIO4DO
• Command the state and value parts simultaneously
40
How To – XIO4DO
• Use the same process to bring feedback into your
application
41
How To – XIO4DO
• Create links and bind
42
How To – XIO4AO
• XIO-4AO command NVs are type SNVT_lev_percent
- Add a Software Output point
- Configure it for Percent
43
How To – XIO4AO
• XIO-4AO feedback, and hand NVs are type
SNVT_switch
- Must be created using NV Configuration View
44
How To – XIO4AO
• Create links and bind
45
Typical Central Plant Control
46
Typical Central Plant Control
47
Spyder Distributed Plant Control
48
Sample code
• Sample libraries for the items discussed during this
presentation are now available on the Buildings Forum
49
Questions and Answers
50
www.honeywell.com