| Overview
The Connect Module that was originally envisioned for the CPU+Economizer profile under HyperStat Split, had greater unrealized potential. The Connect module with its extensive IO capabilities in terms of Relays, Analog Outs, Sensors bus, and Universal Inputs, makes it an excellent choice for extended IO capabilities, where previously the projects depended on external controllers.
The Sequencer that was initially envisioned for creating custom sequences and running them on the cloud for a Site also had its undermined benefits.
With the already-established success stories of the Connect module and Sequencer, and as the next milestone in our vision towards scaling and greater interoperability. at 75F we have combined both these established capabilities into one.
| Low Code
Low code is the term used for this effort to run the custom sequences created over the sequencer and run over on the Connect Module. This concept of Low code (custom sequences on Edge) has its advantages.
This feature allows users to build custom application sequences on the portal and execute them directly on the edge device Connect Module. Users can create custom sequences such as PI Loop controls, lighting controls, and pump lead/lag controls based on specific site use cases, providing optimized control and management for each unique site.
The following are the advantages of bringing the concept of Low code into the 75F system, using low code can:
- Accelerate software creation
- Reducing time-to-market by simplifying complex coding tasks through a visual interface.
- Foster collaboration
- Enabling individuals with diverse technical backgrounds to contribute to agile development.
- Cost-effective and scalable, low-code platforms bridge the gap between business requirements and IT capabilities
- Drives digital transformation.
- Innovate, adapt quickly, and stay competitive in the current technological landscape.
| Sequences for the Edge
As part of the adoption towards Low code implementation, an additional module Sequencer for the Device is introduced within the Site sequencer, and a mode change to Low Code is introduced in the connect module to accept and run the low code.
| Prerequisites
Following are a few prerequisites that are mandatory for enabling the sequences on the Edge
- The Connect module version must be V 1.3 and above.
- The Sequencer application in the internal portal needs to be accessed from a browser that supports the Chromium plug-in, which supports the web USB, to transfer sequences to the Connect module.
- A USB C-type cable for connecting the connect module to the Laptop.
| Accessing Sequencer for Device
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 Device 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 Device
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 277 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
Just like the sequencer for the cloud, the sequencer for device also comes with the generic blocks to support sequence building.
For more information on the Generic block refer to Site Sequencer
| Predefined Connect Module Blocks
Similar to the predefined 75F blocks in the sequencer for the cloud to build sequences based on Haystack data, the sequencer for the device also comes with a list of predefined blocks to aid sequence building for the connect module.
The table below describes all the predefined blocks built for sequence building for the connect module.
Blocks | Description/Usage |
Use this block to print a string. | |
Use this block to set the output relay number and the corresponding relay state. | |
Use this block to set the analog output number and the corresponding analog output value. | |
Use this block to set the universal input mode, universal input number, and the corresponding universal input mode. | |
Use this block to get the universal input value and the corresponding universal input value. | |
Use this block to get the sensor bus value, sensor number, and the corresponding sensor type. | |
Use this block to get the universal input mode number. | |
Use this block to set the relay output number between 1 to 8. | |
Use this block to set the relay output state to ON or OFF. | |
Use this block to set the analog output number between 1 and 4. | |
Use this block to set the analog out value. | |
Use this block to set the universal input number between 1 to 8. | |
Use this block to select the universal input mode as analog or through thermistor. | |
Use this block to select the sensor bus type. | |
Use this block to select the sensor number between 1 and 4. | |
Use this block to run the sequence on startup. | |
Use this block to run a sequence continuously for the allotted seconds. | |
Use this block to select the standard sensor type among the given options. | |
Use this block to get the universal input mode from the selected standard sensor type | |
Use this block to convert the universal input value from the sensor type | |
Use this block to write universal input value from the modbus register value | |
Use this block to read the universal input number from the mapped modbus register | |
Use this block to read the analog output from the modbus register | |
Use this block to read the relay output from the modbus register. | |
Use this block to configure the home screen input number, input name, input units, and the input value. | |
Use this block to update home screen input number and corresponding input value. | |
Use this block to get name from standard sensor type. | |
Use this block to get units from standard sensor type | |
Use this block to imbibe PI controller process with: Controller Number Process Variable Setpoint Proportional Gain integral Gain Error Range integration Time (s) Sample Time (ms) |
|
Use this block to set the PI Controller Number between 1 to 8. | |
Use this block to set the modbus register type as input or holding register. | |
Use this block to set the modbus register address. | |
Use this block the read the modbus register type and the modbus register address. | |
Use this block the write the modbus register type, address and the corresponding value | |
Use this block to configure custom modbus register, type and address | |
Use this block to set the input value, minimum input, maximum input, minimum output and maximum output for conversion scale. | |
Use this block to enable the fail safe for the sequence. |
These predefined connect module blocks can be used along with the generic blocky blocks to build the custom sequences for the connect module.
| Setting Low Code Mode on the Connect Module
To set the connect module to a mode that accepts the Low code custom sequence and run them.
From the Connect Module home screen UI
- Press the right arrow button to navigate to the comm options screen.
- Press the down arrow button to navigate to the mode option.
- Press the right arrow button to access the mode options.
- Press the down arrow to modify the comm option to Low code.
- Press the left arrow button to confirm the mode selection.
Confirmation screen displays.
- Press the right arrow button to confirm the new mode configuration.
The device resets to the Low code mode and the new home screen for the device in low code mode displays, as below.
| Connecting and Setting Connect Module to Programmable mode.
- Connect the connect module device with a USB C cable to the Laptop.
Setting the connect module to programmable mode
- Power off the connect module, press and hold the USB BTS, power the device back ON, to set the device to the programming mode.
| Loading the Sequence to Connect Module
Once a sequence is created in the Site Sequencer application,
- Click Download on the sequencer for the device screen.
The compatible device available for loading the sequence displays in a pop-up window.
- Select the device and click Connect
The download/push successful message displays.
The sequence is pushed to the connect module and starts running on the device.
The counter and the information in the device's new home screen UI sign that the device accepted and ran the sequence successfully.
The number of runs can be tracked by a timer that starts in the connect module device home screen UI.
- Navigate further to the Low code status screen to visualize better details of the sequence running, as below.
The screen displays the following details
- Name of the sequence running on the device
- Sequence ID as signature
- Memory used by the sequence as size
- Number of times the sequence run occurred as Run count.
| Errors
Errors
In case of a miss in the above-mentioned steps, the error message for the no-compatible device connected displays.
For laptops that do not support web USB, the device gets as detected as shown below, which is not in the Device Firmware Update (DFU) mode or programmable mode.
When you face an error as shown above, this could be because the laptop used does not support web USB. For such scenarios kindly follow the following steps to resolve the error.
- Download an appropriate WinUSB/libusb driver Zaidig using the following link
Zadig - USB driver installation made easy (akeo.ie)
- Launch the installer for the application.
- Click the Options menu in Zadig and select “List All Devices.”
- Select “DFU in FS mode,” in the main drop-down.
- Select WinUSB in the target driver box & click Reinstall Driver.
The above steps would stop the error from reoccurring, and the web USB is enabled.
| Logs
For any failed scenario logs or if the user wants to visualize the logs for the connect module it can be visualized in the Terra Term application.
To access tera term.
- Download the TeraTerm using the following link.
Tera Term Open Source Project (teratermproject.github.io)
- Install the Tera Term application.
- Launch the Tera Term application.
- Select the serial port and click OK.
The logs for the connect module start to display randomly
To organize the logs display
- Click Setup and select Terminal.
- Select the LF (line feed) from the receive drop-down in the pop-up window.
The connect module logs start to display in an orderly fashion.
Comments
0 comments
Please sign in to leave a comment.