0

  • No products in enquiry cart.

FAQs

1. I want to be notified if, between 9am and 10pm every day, motion is detected . I want to turn on a strobe light as a local alert for 10 seconds, and I want to receive a push notification at the same time. How can I do this?

The IoTPortal Events feature allows you to set multiple conditions using AND/OR logic to set the trigger condition for an event. You can also specify the actions to take which can include sending push notifications to selected users and enabling an output actuator. In this example we use the 4in1 Sensor which includes Temperature, Humidity, Ambient Light and Passive Infra-Red (PIR) Motion detection in one compact unit. We also use channel 1 of an LDSBus 2CH Relay actuator to control the strobe light.

These events can be set up via the user-friendly IoTPortal web application and the mobile apps (iOS & Android). The event is shown in the IoTPortal web application in Figure Q1a

                                                                                                    Figure Q1a

Figure Q1b shows the Event set-up. In the ‘When’ settings on the left-hand side, you can select one or more conditions using AND/OR logic. The AND condition is used so that the event triggers only when both conditions are true. Motion must be detected for at least 5 seconds, and the time must be between 9am and 10pm. Further AND/OR conditions can be added using the ‘+’ buttons shown.

In the ‘Do’ settings on the right-hand side, you can specify one or more actions to take. Here, we have specified the Notification message and entered the email addresses of the user(s) who should receive the notification. The Relay controlling the strobe light is also activated, followed by a 10 second delay, and the Relay is deactivated.  The actions can be easily re-ordered using the ‘handle’ on the right-hand side as well as edited or deleted.

                                                                                                        Figure Q1b

Figure Q1c shows the detail of the Sensor Value and Recurrence settings used, whilst Figure Q1d shows the detail of the notification, Trigger Actuator and Delay settings.

                                                                                                            Figure Q1c

                                                                                                    Figure Q1d

The IoTPortal Events feature makes it easy to do this. You can set up an event which triggers when your LDSU goes offline and you can then tell IoTPortal which actions to take in response, such as sending an email to one or more address(es) specified. Similarly, you can set a second event which triggers when the LDSU comes online and sends an email to the specified address(es). These events can be set up via the IoTPortal web application and the mobile apps (iOS & Android).

Figure Q2a shows the IoTPortal web application Events page with the two events set up. You can see all of your events listed here as well as enabling/disabling them. You can also click the arrow at the right-hand side to edit them.

 

Figure Q2a

Figure Q2b shows the 4in1 LDSU Offline event. In the ‘When’ settings on the left-hand side, you can select one or more conditions using AND/OR logic. Here, the LDSU Status condition is added and configured to trigger when the LDSU is offline for at least 10 seconds. In the ‘Do’ settings on the right-hand side, you can specify one or more actions to take. Here, the Send Email action is selected. You can specify the email addresses of one or more users as well as specifying the message to be sent.

 

Figure Q2b

For example, when the 4in1 sensor goes offline, the specified users will receive an email message as shown in Figure Q2c

 

Figure Q2c

Yes, you can use the Long Distance Sensor Bus (LDSBus) as a backbone connection, and use RJ45 splitters to form branches and sub-branches that cover the area within the 200m distance limit. This can help simplify the cabling needed compared to routing a single cable around every room in turn.

The total distance to the furthest LDSU can be up to 200m. This is the total distance (including the RJ45 cabling and the RJ11 connection from the Quad T-Junction to the furthest LDSU).

As with a linear LDSBus topology, only one LDSU on the bus should have termination enabled. Termination must be enabled on the LDSU which is furthest from the IoTPortal Gateway.

Connecting the IoTPortal Gateway via a wired Ethernet (or PoE) link offers higher throughput and is less likely to suffer from interference when compared with WiFi. Wired connections can also be more convenient, avoiding the need to reconfigure the wireless settings in the case that the access point in the premises changes. It is more difficult for bad actors to intercept data on a wired network compared to a wireless network which makes for improved security of communications over wireless networks. Having a reliable and continuous internet connection for the IoTPortal Gateway is important for ensuring responsive alerting and event condition checking and actuation control.

BRT Systems normally recommend CAT5e cabling for the LDSBus. Cat5E has been chosen to balance cost, transmission distance, power handling, EMI and crosstalk. While the CAT6 and CAT7 cables offer faster Ethernet transmission speeds of 1Gbps and 10Gbps respectively, improved EMI and crosstalk handling, they are not critical when considering the relatively much lower speed of LDSBus operations which is fixed at 230Kbps. CAT6 and CAT7 cabling can therefore be used for the LDSBus for cases where cabling is already installed or if this is preferred by the installer, but does not offer an operational benefit for LDSBus compared to CAT5e.

The IoTPortal offers two methods to alert you when application parameters are outside of defined ranges. The first is via single sensor alerts and the second is via the event service. In both cases, a choice of Push alerts, SMS messages and Emails (all with configurable messages) can be sent. These two methods allow simple set-up or comprehensive multi-condition alerts depending on the application requirement.

Single sensor alerts can be set up for each sensor, from the configuration page for the associated sensor within the IoTPortal web application or mobile app (iOS & Android). They are ideal for simpler cases where the alert is associated with a single sensor and only a notification is required (rather than taking other actions such as triggering an actuator). Single or dual thresholds (upper/lower) can be set and the resulting alert can be triggered when the alert case becomes true (activated), when it becomes false (deactivated) or both.

The Event service offers more comprehensive options which can include multiple sensors, and multiple other conditions (such as requiring the trigger condition to exist for a set time before activating, or the time of day). This is set up via the dedicated Events menu within the IoTPortal web application or mobile app (iOS & Android). In addition to sending alerts, the Events service has a wider range of actions which can be selected, such as controlling other actuators in response to the event conditions being met.

Certainly, any number of IoTPortal gateways may be deployed across a locality or region and accessed and controlled globally through the IoTPortal. Customers can connect to the IoTPortal via their favourite web browser or use the IoTPortal mobile apps available on the App Store and Play Store. The browser and mobile applications allow you to monitor and control your processes from anywhere in the world.

Yes, BRT Systems offers several models of LDSBus air quality sensors, namely, LDSBus CO2 and LDSBus CO2-Pro sensors which measure CO2, temperature, humidity and outdoor ambient light, LDSBus TrueVOC sensors that measure volatile organic gases and LDSBus Air Quality Sensor which measure air quality referenced to an international standard index.

One IoTPortal gateway can support up to 80 LDSBus devices with each LDSBus device consisting of several sensors and actuators. Additional gateways may be added to increase the coverage area and increase the number of sensors and actuators if required.

Each IoTPortal gateway supports up to three daisy-chained sensor networks, these LDSBus networks can each be up to 200m long, allowing a large area to be covered. If the aquaculture application requires more coverage than is available from a single gateway, then multiple gateways can be connected to the same system.

To ensure adequate dissolved oxygen levels, ensure that the Dissolved Oxygen (DO) probe is regularly serviced and in working condition at all times. In most farms, aerator pumps are switched on and off on a periodic schedule to ensure that DO levels always remain at a high level. However, this is wasteful from an energy conservation and equipment life point of view and ideally, we should only have to turn on the aerator when the DO level is below a safe threshold and stop when a health level is reached. This can be achieved with the IoTPortal using our Events feature which activates and deactivates the required aerator pump(s) depending on measured DO levels. Besides this, push notifications, SMS and email alerts may also be configured via our Alert feature. All the foregoing is performed via our Zero-code environment.

BRTSys provides several sensor adapters for water quality monitoring such as pH, EC, DO, ORP besides water level and thermocouple sensors. We have curated 3rd party sensor probes that are compatible with our adapters and this guide can be found at the following link: https://brtsys.com/ldsbus/wp-content/uploads/sites/8/2023/05/BRTSYS_LDSBus_Probes-Specifications.pdf

BRTSys offers a comprehensive range of sensor adapter modules tailored for various applications in the agricultural and aquaculture sectors. These include, but are not limited to, pH sensors, Oxidation Reduction Potential sensors, and thermocouples.

In addition to these, we have customers who have successfully utilized the IoTPortal system for specific applications such as Hydroponics systems and Green Houses.

  • For Hydroponics system, we incorporate a cluster of deployed sensors including pH, EC, DO, Temperature sensors, and Relay actuators for controlling water, lights, and dosing pumps.
  • For Green House solutions, we focus on soil sensors for pH, EC, Temperature, Salinity, and NPK soil measurements.

For a more detailed list of the available sensor adapters, please visit our website at https://brtsys.com/iotportal/. We are constantly expanding our range of sensors to cater to the diverse needs of our customers in the agriculture and aquaculture sectors. If you have specific requirements, feel free to contact us for customised solutions.

The IoTPortal allows users to configure event notifications based upon sensor or actuator inputs connected to the system, notifications can be pushed to an applicable email address, mobile phone or via the IoTPortal Application when event thresholds are triggered allowing users to keep track of all relevant environmental conditions.

LDSBus provides a wide range of sensor and actuator products which can be integrated into both indoor and outdoor applications, data monitoring and system automation is easily achieved through a localised host system. The IoTPortal expands the usability of the LDSBus system by enabling instant access to sensor data or actuator states anywhere in the world via the web dashboard or IoTPoral mobile Application.

Stay tuned for updates

Stay tuned for updates

I want to use PanL Smart Living to control a light based on detecting motion and ambient light levels. What hardware do I need and how do I connect it?

In this example, we have chosen the LDSBus 4in1 Sensor to detect motion and ambient light levels. This compact sensor measures both of these parameters as well as temperature and humidity. We have used the LDSBus 2CH Relay to control a connected light. The diagram below shows how to connect these to the PanLHub80 which acts as the heart of the PanL Smart Living (PSL) system.

You can daisy chain multiple Quad T-Junctions via Cat5e cables with RJ45 connectors.

  • Configure the LDSBus devices by using the LDSBus Configuration Utility before connecting them to the PanLHub80. See the LDSBus Configuration Utility guide for details. This includes an unique address for the LDSBus devices, setting a name (optional) and enabling the built-in termination for the device which is furthest away on each LDSBus (in this example it is the 2CH Relay).
  • With the system powered off, connect the first Quad T-Junction to Port 2 of the PanLHub80. Port 2 defaults to LDSBus protocol and other ports may be configured for LDSBus operation using the PanL Smart Living mobile applications.
  • Connect your LDSBus 4in1 sensor to one of the four RJ11/12 ports on the Quad T-Junction.
  • Connect your LDSBus 2CH Relay to one of the other 3 ports on the same Quad T-Junction. If the distance between the motion detector and the relay cannot be attained with a single Quad T-Junction, then the LDSBus may be extended with an additional Quad T-Junction up to 200m.
  • The PanLHub80 provides power and data through the LDSBus connection and so the only additional connection will be from your LDSBus 2CH Relay to the mains supply and to the lamps. Whilst the LDSBus operates at low voltages, the mains connections must be carried out by a qualified electrician.
  • Note that under normal operation, status LED on LDSBus devices show a steady green colour except when termination has been enabled and in which case the status LED shows a blue colour instead. Therefore, the 2CH Relay’s status LED indicates blue because its termination is enabled.

In the above example, we have used the 2CH Relay which provides basic on and off control of the light. If your lighting type has colour or dimming, then the PanL Mood Lighting Controller or LDSBus Trailing Edge Dimmer would be a good match and if using 0-10V, 1-10V technologies, the LDSBus Isolated IO Controller is an ideal match.

This type of functionality can be achieved using events within the PSL system. An event can be created to automatically trigger objects such as scenes, presets, devices, groups, rooms and zones.

Several types of events are available within the PSL system:

  • Time-based events where users can configure a particular time of data to automatically trigger an action,
  • Device-based events where users can trigger actions based on device status,
  • Sensor-based events where users can trigger actions based on sensor inputs, and
  • Advanced events where users can set multiple conditions, with AND and OR logic, in response to sensor inputs or device on/off state changes to trigger actions.

To create an event which triggers based upon motion detection and ambient light levels, we can connect an LDSBus 4in1 Sensor to the PSL system. The 4in1 Sensor consists of a PIR based motion detector, ambient light sensor besides temperature and humidity. To meet the requirements, we shall create a logic such as, “When the ambient light is below 100 Lux AND motion is detected, then turn on the smart light”.

Let’s use the PSL mobile application to create an event:

  1. Tap on ‘More’ at the bottom of the navigation bar on the app’s home screen and select ‘Events’. (Figure 2).
  2. Tap on ‘+’ icon to add a new Event.
  3. Select ‘Advanced Events’ as shown in Figure 3.
  4. The new ‘Advanced Event’ page (Figure 4) allows us to select the first WHEN condition for our event by pressing the button.
  5. Tap on ‘Add Condition’ to add the first condition and select sensor-based input (Figure 5 and Figure 6).
  6. Add an AND condition to add the second condition and select sensor-based input and select the ambient light sensor of the LDSBus 4in1 sensor (Figures 7 and 8).
  7. Finally, we can add a THEN condition to perform any desired actions when our automated event is triggered.
  8. We select ‘Save’ to save the new Event. This will be triggered by the PSL system when the conditional arguments have been satisfied.
  9. Finally, the event can be enabled via the toggle button in the events menu (Figure 9)

We have now created an event which can be used to trigger an action (scenes, presets, devices, groups, rooms and zones) when our specified conditions (motion detected and low ambient light) are detected.

Figure 1
Figure 2
Figure 3
Figure 4
Figure 5
Figure 6
Figure 7
Figure 8
Figure 9

This can be achieved in the PSL system with Scenes. A Scene allows you to set up multiple actions to achieve a desired condition. You can specify a list of actions to be executed in a sequential manner or simultaneously. Sequencing is achieved by inserting delays in between actions and when there are no delays between actions, the actions may complete out of order. A scene may be activated through touch, voice or automatically at a specific time or by a conditional event.

Actions within a scene can include the triggering of multiple preset objects (a preset being a pre-defined attribute such as on/off, colour setting or brightness for lighting). For example, you can dim lights to a deep blue colour as well as close the curtains when you want to watch a movie.

Follow these steps to create a scene using the PSL mobile apps:

  1. Tap on ‘More’ found at the bottom of the app (Figure 1), then select ‘Scenes’.
  2. Figure 2 shows the list of scenes (if any) that have been created for this PSL network. Select the ‘+’ icon to create a new scene.
  3. Give the Scene a name and you may start to build your scene by selecting ‘Add objects’ or ‘Copy an existing scene’ (Figure 3).
  4. Figure 4 shows some pre-defined preset objects that we can add to the configured scene. In this instance, we select two presets, which switch on and switch off a smart light (Philips Hue). Other objects from the devices, rooms, groups, and zones can be added to the scene.
  5. Once we have added the desired items to the scene, we can set delays between each action by tapping on the ‘Timer’. A pop-up is displayed allowing the time delay to be set. A 1-minute delay was added as shown in Figure 5.
  6. Scene actions can be re-ordered by simply dragging the actions up or down in the screen editor.
  7. Select ‘Save’ to save your new scene. From the Scenes list, tap on the newly saved Scene to activate it.

We have now created a scene which switches on a device, waits for a fixed delay of 1 minute and then switches off the light.

Figure 1
Figure 2
Figure 3
Figure 4
Figure 5

Stay tuned for updates

Stay tuned for updates

BRT Systems Pte Ltd (BRTSys) provides cutting-edge IoT solutions that drive operational excellence and deliver significant cost-value benefits with two families of solutions: IoTPortal and PanL

Our Solutions
Our Products
Partners
About Us
Copyright © 2024 BRT Systems Pte Ltd. All rights reserved.