browse

| Overview

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.

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 75°F, 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 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

The 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 the 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 two mandatory sequence holding blocks, as shown below.

  • One to run the sequence continuously every second.
  • Other to run the sequence On Startup

All of the other blocks used for sequence building need to be within these mandatory blocks.

| Generic Blockly Blocks

Just like the sequencer for the cloud, the sequencer for the 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 section below describes all the predefined blocks built for sequence building for the connect module.

String to Print

Screenshot 2024-07-04 135748.png

 Use this block to print a string,

You can combine the block, as shown below, with a text block to achieve a desired result.

Where a text block is used to display a text Relay Output 1 Register with the Modbus register number read from, the relay output number 1.

Set Relay Output

Use this block to set a relay output state to a relay output number to be used in the sequence.

You can combine the block, as shown above, with a Relay Output Number block and a Read Relay Output or Set Relay Output State blocks, to achieve the desired results.

Set Analog Output

Use this block to set an Analog Output Value to an Analog Output number to be used in the sequence.

You can combine the block, as shown below, with an Analog Output Number block and a Read Analog Output or Set Analog Output Value block, to achieve the desired results.

Use this block to set a Universal Input Mode to a Universal input number to be used in the sequence.

You can combine the block, as shown below, with a Universal Input Number block and a Get Universal Input Mode & Read Universal Input Number blocks, to achieve the desired results.

Get Sensor Bus Value

Use this block to Get Sensor Bus Value from a sensor bus connection to be used in the sequence.

You can combine the block, as shown above, with a Sensor Number block and a Sensor Bus Type block, to achieve the desired results.

 

Configure Home Screen Input

Use this block to configure a specific home screen input for home screen display.

You can combine the block, as shown above, with a numerical & text block to achieve the desired results.

Update Home Screen Input

Use this block to update a home screen input configured.

You can combine the block, as shown above, with a numerical & a variable to achieve the desired results.

PI Loop Block

Use this block to configure a PI Loop Output to be used in the sequence.

 

Conversion Scale Value

Use this block to configure a conversion scale value within a sequence.

You can combine the blocks, as shown above, to achieve the desired results.

Blocks Description/Usage
   
Screenshot 2024-07-04 135806.png Use this block to set the output relay number and the corresponding relay state.
Screenshot 2024-07-04 135830.png Use this block to set the analog output number and the corresponding analog output value.
Screenshot 2024-07-04 135848.png Use this block to set the universal input mode, universal input number, and the corresponding universal input mode.
Screenshot 2024-07-04 135903.png Use this block to get the universal input value and the corresponding universal input value.
Screenshot 2024-07-04 135923.png Use this block to get the sensor bus value, sensor number, and the corresponding sensor type.
Screenshot 2024-07-04 135943.png Use this block to get the universal input mode number.
Screenshot 2024-07-04 151300.png Use this block to set the relay output number between 1 to 8.
Screenshot 2024-07-04 162927.png Use this block to set the relay output state to ON or OFF.
Screenshot 2024-07-04 163921.png Use this block to set the analog output number between 1 and 4.
Screenshot 2024-07-04 164115.png Use this block to set the analog out value.
Screenshot 2024-07-04 164326.png Use this block to set the universal input number between 1 to 8.
Screenshot 2024-07-04 165153.png Use this block to select the universal input mode as analog or through thermistor.
Screenshot 2024-07-04 165324.png Use this block to select the sensor bus type.
Screenshot 2024-07-04 142415.png Use this block to select the sensor number between 1 and 4.
Screenshot 2024-07-04 142510.png Use this block to run the sequence on startup.
Screenshot 2024-07-04 142524.png Use this block to run a sequence continuously for the allotted seconds.
Screenshot 2024-07-04 142558.png Use this block to select the standard sensor type among the given options.
Screenshot 2024-07-04 142816.png Use this block to get the universal input mode from the selected standard sensor type
Screenshot 2024-07-04 142853.png Use this block to convert the universal input value from the sensor type
Screenshot 2024-07-04 142951.png Use this block to write universal input value from the modbus register value
Screenshot 2024-07-04 143107.png Use this block to read the universal input number from the mapped modbus register
Screenshot 2024-07-04 143130.png Use this block to read the analog output from the modbus register
Screenshot 2024-07-04 143331.png Use this block to read the relay output from the modbus register.
Screenshot 2024-07-04 143400.png Use this block to configure the home screen input number, input name, input units, and the input value.
Screenshot 2024-07-04 143429.png Use this block to update home screen input number and corresponding input value.
Screenshot 2024-07-04 143453.png Use this block to get name from standard sensor type.
Screenshot 2024-07-04 143635.png Use this block to get units from standard sensor type
Screenshot 2024-07-04 143709.png

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)

Screenshot 2024-07-04 143750.png Use this block to set the PI Controller Number between 1 to 8.
Screenshot 2024-07-04 144201.png Use this block to set the modbus register type as input or holding register.
Screenshot 2024-07-04 184633.png Use this block to set the modbus register address.
Screenshot 2024-07-04 143823.png Use this block the read the modbus register type and the modbus register address.
Screenshot 2024-07-04 184912.png Use this block the write the modbus register type, address and the corresponding value
Screenshot 2024-07-04 185055.png Use this block to configure custom modbus register, type and address
Screenshot 2024-07-04 143849.png Use this block to set the input value, minimum input, maximum input, minimum output and maximum output for conversion scale.
Screenshot 2024-07-04 144223.png 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.

| BACnet Blocks

With the connect module capability to act as a server in an external BMS network, the sequencer for the edge now comes with  BACnet objects and values configuration blocks, along with the read and write BACnet object blocks to read from and write to the configured objects.

Blocks Description
Use this block to configure a BACnet Analog Input Object Instance with an instance number, name, and units.
Use this block to configure a BACnet Analog value Object Instance with an instance number, name, units, min, and max value.
Use this block to configure a BACnet Binary Input Object Instance with an instance number, name, active, and inactive texts.
Use this block to configure a BACnet Binary Value Object Instance with an instance number, name, active, and inactive texts.
Use this block to configure a BACnet Multistate Input Object Instance with an instance number, name, and state text.
Use this block to configure a BACnet Multistate Value Object Instance with an instance number, name, and state text.
Use this block to write a value into the BACnet Analog Input Object Instance number.
Use this block to write a value into the BACnet Analog value Instance number.
Use this block to fetch the value from a BACnet Binary Value Object Instance number.
Use this block to write a value into the BACnet Multistate Input Object Instance number.
Use this block to write a value into the BACnet Multistate value Object Instance number.
Use this block to fetch the value from a BACnet Multistate value Object Instance number.
Use this block to define the units for the BACnet Analog Input object instance, during its configuration
Use this block to define a BACnet instance number in all the configuration blocks that require an object instance initiation.

Example Usage: 

| Modbus Blocks

Read Modbus Register

Use this block to read a value from a specific Modbus register.

You can combine the blocks, as shown above, with a Modbus register type and address blocks to achieve the desired results.

Write Modbus Register

Use this block to write a value into a specific Modbus register.

You can combine the blocks, as shown above, with a Modbus register type, address, and numerical blocks to achieve the desired results.

Configure the datatype custom Modbus register

Use this block to configure a custom datatype modbus register.

You can combine the blocks, as shown above, with a Modbus register type, address, and datatype blocks to achieve the desired results.

Read datatype Modbus register

Use this block to read a value from a custom datatype Modbus register.

You can combine the blocks, as shown above, with a Modbus register type, address, and datatype blocks to achieve the desired results.

Write datatype Modbus register

Use this block to write a value into a custom datatype Modbus register.

You can combine the blocks, as shown above, with a Modbus register type, address, datatype, and numerical blocks to achieve the desired results.

Configure Custom Modbus register

Use this block to configure a custom Modbus register.

You can combine the blocks, as shown above, with a Modbus register type and address blocks to achieve the desired results.

Blocks Description

Use this block to read the value from relay output.

You can combine the blocks as shown below to achieve the desired results.

Use this block to read an analogue output value

You can combine the blocks as shown below to achieve the desired results.

Use this block to read a universal input value.

You can combine the blocks as shown below to achieve the desired results.

 

Use this block to write to a universal input.

You can combine the blocks as shown below to achieve the desired results.

| 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 it.

From the Connect Module home screen UI

Group 1342@2x.png

  • Press the right arrow button to navigate to the Installer options screen.

Connect Installer Options 01 – 16@2x.png

  • Press the down arrow button to navigate to the connect mode option.

Connect Installer Options 01 – 17@2x.png

  • Press the right arrow button to access the mode setting screen.

Connect Installer Options 01 – 22@2x.png

By default, the connect module is set to the split mode to act as a Hyperstat split to provide the required control for the HyperStat Split CPU + Economizer profile.

  • Press the down arrow to modify the comm option to Low code.

Connect Installer Options 01 – 25@2x.png

  • Press the right arrow button to set the mode to low code.

The confirmation screen displays.

  • Press the right arrow button to confirm the new mode configuration.

Connect Installer Options 01 – 26@2x.png

The device resets to the low-code mode, and the new home screen for the device in low-code mode displays as below.

Group 1346@2x.png

| Connecting and Setting the 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.

Group 1356@2x.png

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 runs occurred as Run count.

| Errors

Errors

In case of a miss in the above-mentioned steps, the error message for the non-compatible device connected displays.

For laptops that do not support web USB, the device gets 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.

| Video Introduction References

For more information or a quick guide, refer to the following videos.

 

 

Previous
Next

Comments

0 comments

Please sign in to leave a comment.

Was this article helpful?

1 out of 1 found this helpful
Powered by Zendesk