Ave Monq
• Easy integration
• Intuitive operation
• Czech localization
• LoRaWAN gateway
• LTE or ethernet network connection
• Open standard
The control system consists of 2 primary elements – the hardware enabling communication with the luminaire and the operating software, whose task is to provide the user with information about the status of the installation as easily as possible, or to allow the entire installation to be controlled.
The following elements are needed to implement a controlled lighting project:
Due to the communication, the most common type of ballast used is. From the control point of view we divide ballasts into 2 categories – with D4i certification and without certification. D4i certification means that the ballast is adapted for use in a controlled installation. The difference from non-certified D4i ballasts is primarily in the power supply at the cap base, which is integrated in the case of the D4i ballast and does not require the use of an external 24V power supply at the cap base. And also by incorporating D4i libraries that allow the current to be read via DALI
consumption of the luminaire. In the case of using a non-certified ballast, the use of an external 24V power supply may be necessary
power supply. Source: https://www.dali-alliance.org/d4i/
TESLUX Lighting s.r.o. uses standard LoRaWAN elements in controlled lighting projects.
The advantage of the technology is its open standard, which allows us to use third-party elements if necessary, and the customer cannot get into a state of being under a “vender lock” – that is, he is not dependent on a single supplier if necessary. In projects we use our own SMARTOO getaway in specification with LTE or Ethernet network connectivity.
We use a public lighting module with a ZHAGA socket, also known as a Lumawise socket. The module requires a 24 V power supply and DALI communication with the ballast.
The control system assumes that the lighting system is constantly energized and the control of each individual luminaire is dependent on the lighting module. The default condition is that the individual modules are commanded through the control system, which sends the message via SMARTOO getaway to the lighting modules.
Within the control system it is possible to set a time schedule according to which the installation is commanded. Individual messages are sent by multicast, which means that one message is sent to several modules at the same time. This prevents the installation from lighting up one lamp at a time.
The lighting modules have 2 modes of operation – manual or automatic. Manual mode relies on communication with the control system. The automatic mode of operation controls the luminaire based on the ambient light intensity. If the ambient light intensity drops below a set level, the module will light the luminaire. If, on the other hand, the ambient light intensity rises above a certain level, the module turns off the lamp.
In case the lighting module is in manual mode and communication is lost, the module waits for a defined period of time to receive a message from the control system. If the message is not received within a certain time, the module will automatically switch to automatic mode of operation to ensure lighting within the installation.
The control system consists of 3 separate parts:
Element responsible for mediating commands to lighting modules and their registration to the network. This element retains the necessary keys to encrypt communications so that a foreign attacker cannot command the installation.
A separate element providing control logic, adding lights to groups, setting the schedule, etc. Communication with the backend is via a REST API, which allows us to integrate the entire control logic into third-party applications if necessary.
The element that the user sees as the only one. It is a graphical extension of the entire control system so that anyone can operate it.The frontend can be customized to the customer in terms of logo and color scheme.
All elements are run from Docker containers for quick and easy installation either on a VPS server or locally as an on-premise solution.
The control system consists of the following modules:
The first signpost to get a quick overview of the installation status
Main functions of the dashboard:
• Number of connected devices
• Warning of a device with a ballast or communication error
• Number of LoRa gateways
• LoRa gateway status (communicating x not communicating)
The map category is used to display installed RF nodes with the option to filter for specific groups of devices or only specific devices.
Main map features:
• Grouping points by map zoom
• Display filter for specific devices / device groups + LoRa gates
• Visualization of the status of individual lights (on/off) and LoRa gates
• Click on a luminaire to view information about:
• DevEUI equipment
• Name of device
• GPS coordinates of the point
• Group in which the device is (click to redirect to a specific group with the possibility to edit the lighting status)
• Status information – lit/unlit/regulated (how many percent)
• Communication (last message) – information when the last message came from the luminaire
The “Lighting Plan” category is used to create a lighting plan and assign it to a group/groups or to specific facilities.
The main function of the Lighting Plan:
• Graphical display of settings
• Validity of the rule (range of two dates, days of the week, always)
• Action
• Light up to XX % intensity
• Turn off
• Scheduling events from – to (by dusk or fixed time)
• Comment on the plan
• Extraordinary global settings (e.g. for fireworks, etc.)
• All lights on
• All lights off
• Easy integration into higher-level systems, if needed
• Simple and intuitive operation
• Czech localization
• The user can add or modify individual elements himself without hidden costs for adding luminaires
•We are a company that develops and manufactures LoRaWAN gateways, lighting modules and control system.
• We deliver a complete solution and there is no risk of cycling between subcontractors in case of any problems.
• After installing the luminaire, always check the power supply at the socket and the correct wiring.
• The installation must be under constant power
• The advantage of using a D4i certified ballast is the integrated power supply and the ability to read ballast consumption
• The LoRa gateway should be placed as high as possible with direct visibility to the individual elements
• The LoRa gateway antenna should not be installed contiguously with another
Ave Monq