| Overview
Now you can create custom sequences from the sequencer and push them to CCU for consumption.
With this implementation, you can add custom sequences to CCU that complement the existing operation.
The custom sequences can be cloud alerts or rules that can influence the equipment's behavior.
They can control algorithms that can be downloaded on CCU and operated locally on CCU so that in the event of a cloud connection loss, these sequences can operate continuously without a dependency on the cloud.
| Sequences for the CCU
As part of the adoption, an additional module Sequencer for the System is introduced within the Site sequencer.
| Accessing Sequencer for System
To access the sequencer for the device.
- Click Site Sequencer from the menu icon in the internal portal.
The site sequencer screen displays
- Select any site where you want to build the sequences.
The Sequence creation workspace options and canvas display.
- Click the System option to access the sequence-building workspace options and canvas for the device.
The sequencer on device opens with a default sequence in the canvas.
| Creating Sequences for System
The sequence creation happens just like the sequences for the cloud, for more information
- Create a new page for the new sequence.
- Rename the page as required.
The workspace saves successfully.
- Right-click on the newly created canvas
- Click delete all 45 blocks to clear the canvas
- Drag and drop the blocks onto the canvas and build the required sequence.
Similar to the sequence holding block in the sequencer for the cloud, the sequencer for the device has a two mandatory sequence holding block, as shown below.
- One to Run the sequence continuously for every second.
- Other to Run the sequence On Startup
All of the other blocks used for a sequence building need to be within these mandatory blocks.
| Generic Blockly Blocks
Similar to the sequencer for the device, the sequencer for system also comes with the generic blocks to support sequence building.
For more information on the Generic block refer to Site Sequencer
For more information on Sequences on Edge device refer to Sequences on Edge
| Example Sequence 1
The sequence is created to read the battery percentage, battery severity and level and display it on the device screen.
Step | Block | Actions |
Step 1 | Sequence Block (Mandatory) |
|
Step 2 |
If Logic Block |
|
| Example Sequence 2
The sequence is created for one of the most frequently used chiller sequences for lead, lag pumps in a unit. According to this sequence, the lead and lag pumps switchover (Lead becomes Lag, Lag becomes Lead) from time to time based on certain conditions.
The Table below talks about the steps and the blocks used in the sequence to achieve the use case.
First Part of the Sequence:
Step | Block | Actions |
Step 1 | Sequence Block (Mandatory) |
|
Step 2 |
String to Print |
|
Step 3 | Configure Custom Modbus Register |
To configure a custom Modbus register with
|
Step 4 | Configure Custom Modbus Register |
To configure a custom Modbus register with
|
Step 5 | Configure Custom Modbus Register |
To configure a custom Modbus register with
|
Step 6 | Configure Home Screen Input 0 |
To Configure a parameter on the home page:
|
Step 7 | Configure Home Screen Input 1 |
To Configure a parameter on the home page:
|
Step 8 | Configure Home Screen Input 2 |
To Configure a parameter on the home page:
|
Step 9 | Configure Home Screen Input 3 |
To Configure a parameter on the home page:
|
Step 10 | Configure Home Screen Input 4 |
To Configure a parameter on the home page:
|
Step 11 | Configure Home Screen Input 5 |
To Configure a parameter on the home page:
|
Step 12 | Configure Home Screen Input 6 |
To Configure a parameter on the home page:
|
Step 13 | Configure Home Screen Input 7 |
To Configure a parameter on the home page:
|
Step 14 | Set Support Counter function |
|
Step 15 | Set Lead function |
|
Step 16 | Set Lag function |
|
Step 17 | Set Reversal function |
|
Comments
0 comments
Please sign in to leave a comment.