NORVI Controllers was created to address the lack of connectivity in industrial electronics, offering reliable hardware with modern connectivity features that achieved success through flexibility and cost-effectiveness. Their products serve as “Industrial Arduino” and “Industrial ESP32” solutions for harsh environments.
What is NORVI Controllers?
NORVI Controllers is a Sri Lankan company that designs and manufactures industrial IoT devices and controllers. They specialize in ESP32 and STM32-based industrial controllers that bridge the gap between industrial automation and modern connectivity features. Founded in 2014, the company is headquartered in Green Cliff 2, Midigama East, Weligama, with 10-20 employees.
Are NORVI Controllers certified for industrial use?
Yes. NORVI Controllers are certified for industrial use and comply with CE standards, including EMC (Electromagnetic Compatibility) testing. These certifications ensure that our devices meet the safety, reliability, and performance requirements for operation in industrial environments.
Each product undergoes rigorous testing to guarantee compliance with industry regulations and to ensure stable performance in demanding conditions.
Product Categories
What are the main product lines?
NORVI IIOT Series:
ESP32-based controllers for IoT applications
Built-in WiFi connectivity
DIN-Rail mount applications with OLED displays
Digital/analog inputs and relay/transistor outputs
NORVI Outdoor Nodes:
IP67 rated weatherproof enclosures
Solar and battery powered options
LoRa/Zigbee/NB-IoT/GSM-LTE connectivity
12V DC power output for sensors
Expansion Modules:
Analog input/output modules (0-10V, 4-20mA)
Digital input/output expanders
Relay output modules
Communication interface modules
Technical Specifications
How can I read quadrature encoders with the ESP32?
The ESP32 includes built-in support for quadrature encoder decoding, making it suitable for applications such as motor position sensing and rotational feedback.
How It Works:
The ESP32’s Pulse Counter (PCNT) peripheral allows efficient decoding of quadrature signals (A/B channels).
It can count pulses and track direction, freeing up the CPU for other tasks.
Electrical Isolation:
When connecting industrial encoders, it’s important to:
Use optical or digital isolators to protect the ESP32 from electrical noise and voltage spikes.
Ensure the isolation circuit’s switching speed can handle the encoder’s pulse frequency without distortion or missed counts.
Using NORVI for Encoder Applications:
NORVI Controllers are designed for industrial use and support:
Isolated digital inputs for direct connection of encoder signals
Compatibility with NPN and PNP outputs
Firmware examples using ESP32’s hardware pulse counter
This makes NORVI a reliable platform for motion control, speed monitoring, and industrial automation projects.
How can I read MODBUS devices over RS-485 with the ESP32?
To read MODBUS RTU devices over RS-485 using an ESP32, you’ll need both proper hardware support and MODBUS-compatible firmware.
Hardware Requirements:
An RS-485 transceiver (e.g., MAX485) or a controller with built-in RS-485 support.
Correct bus wiring with optional termination resistors.
For industrial use, NORVI Controllers feature integrated RS-485 ports, offering out-of-the-box support for MODBUS communication in harsh environments.
Software Implementation:
You can configure the ESP32 to act as either a MODBUS Master (to read/write to slave devices) or a MODBUS Slave (to be queried by a master controller).
NORVI provides step-by-step guides for both roles:
🔗 Using NORVI (ESP32) as a MODBUS Master
🔗 Using NORVI (ESP32) as a MODBUS Slave
These guides walk you through:
Wiring and hardware setup
Library installation
Code examples for reading/writing MODBUS registers
Serial configuration for RS-485
Why Choose NORVI?
Built-in RS-485 with surge protection
Supports both MODBUS RTU Master and Slave modes
DIN-rail mountable, industrial-grade enclosures
Ideal for integrating with sensors, PLCs, HMIs, and SCADA systems
How can I interface industrial 0–10 V signals with the ESP32?
The ESP32’s analog-to-digital converter (ADC) operates at a much lower input voltage (typically 0–3.3 V), so directly connecting a 0–10 V industrial signal can damage the microcontroller. To safely interface these signals, you must scale them down using a voltage divider circuit or a signal conditioning module.
Alternatively, NORVI Controllers provide a more robust and industrial-ready solution. Our ESP32-based devices with 0–10 V analog input support offer:
Built-in voltage scaling to match the ESP32’s ADC range
Input protection against overvoltage and electrical noise
High-resolution ADCs for accurate voltage measurement
Compatibility with standard industrial transducers and signal outputs
With NORVI, you can safely and reliably read 0–10 V signals from sensors such as pressure transmitters, temperature controllers, position sensors, and other industrial devices — without additional circuitry.
How can I interface industrial 4–20 mA sensors with the ESP32?
To interface industrial 4–20 mA current loop sensors with an ESP32, you need to convert the current signal into a measurable voltage range that the ESP32’s ADC can read. This is typically done by placing a precision load resistor (commonly 250 Ω or 100 Ω) across the current loop to produce a corresponding voltage (e.g., 4–20 mA → 1–5 V or 0.4–2 V).
However, using a raw ESP32 module for this requires careful protection and noise filtering.
At NORVI, our industrial ESP32-based controllers include built-in 4–20 mA analog input channels, specially designed for industrial sensor integration. These inputs provide:
High-resolution ADCs for accurate readings
Input protection against surges and transients
Industrial-grade connectors for reliable wiring
Compatibility with a wide range of analog process sensors
This allows you to directly connect pressure sensors, temperature transmitters, level sensors, and other industrial devices without additional signal conditioning.
What input/output capabilities do they offer?
Digital Inputs: 24V optically isolated inputs
Analog Inputs: 0-10V DC and 4-20mA with 16-bit ADC resolution
ESP32-WROOM32: Primary processor for IoT applications
ESP32-S3-WROOM32: For advanced applications requiring more processing power
STM32L Series: For ultra-low power battery applications
Arduino Mega compatible (AtMega) : Some models support Arduino Mega form factor
NRF52 Series: BLE
ESP32 Series
How can I interface industrial 24V sensors with the ESP32?
To safely interface 24V industrial sensors with the ESP32, it is recommended to use opto-isolators (optocouplers) to protect the microcontroller from voltage spikes and electrical noise. Additionally, current-limiting resistors should be included to prevent overcurrent damage.
At NORVI, our ESP32-based industrial controllers are designed to directly support 24V digital signals, eliminating the need for additional protection circuitry in most cases. NORVI devices feature:
Built-in isolation for enhanced protection
Flexible digital input polarity – compatible with both PNP (positive) and NPN (negative) sensor outputs
Compatibility with standard industrial automation sensors and PLCs
This makes NORVI Controllers an ideal solution for integrating ESP32 with industrial-grade sensors and equipment.
Programming & Development
What expansion capabilities exist?
MicroSD card support for data logging
I2C expansion modules for additional I/O
Address-configurable expansion modules
Custom input/output configurations available
Do NORVI controllers require special drivers?
No, NORVI controllers are designed to work like standard Arduino boards with no additional drivers required for programming.
What programming environments are supported?
Arduino IDE (primary development environment)
ESP IDF
Applications & Use Cases
What industries use NORVI controllers?
Industrial Automation & Control
Embedded & IoT Product Developers
Manufacturers & Industrial Designers
AgriTech, Energy, Sustainability
Compliance & Security Integrators
Smart Buildings & Hospitality
OEM/Device Manufacturers
What are common application scenarios?
IoT Data Collection: Sensor data gathering with cloud connectivity
Remote Monitoring: Equipment status monitoring via GSM/WiFi
Process Control: Automated control systems with HMI interfaces
Environmental Sensing: Weather stations and environmental monitoring
Asset Tracking: Location and condition monitoring for equipment
How long has NORVI been manufacturing controllers?
NORVI Controllers was founded in 2014 and has been developing controllers for harsh environments for years, with hundreds of successful retrofit installations completed.
Where can I purchase NORVI products?
Direct from NORVI website (norvi.lk)
Tindie marketplace
Through authorized distributors
Custom orders through direct contact
Technical Support & Resources
What development resources are available?
GitHub repositories with example code
Documentation for each product line
What file formats and protocols are supported for data logging?
MicroSD card storage
CSV data logging
Real-time clock (DS3231 RTC) for timestamping
Cloud data transmission via WiFi/GSM
What safety and protection features are included?
Optically isolated inputs for electrical protection
Industrial-grade components rated for harsh environments
Reverse polarity protection
Overcurrent protection on outputs
ESD protection on communication interfaces
Integration & Compatibility
Are NORVI controllers compatible with existing industrial systems?
Yes, through multiple integration methods:
Modbus RTU/TCP for SCADA systems
Standard industrial I/O signals (4-20mA, 0-10V)
Ethernet connectivity for network integration
RS-485 for industrial communication networks
What sensors and devices can be connected?
Temperature sensors
Pressure transducers (4-20mA)
Voltage sensors (0-10V)
Digital switches and contacts
Load cells and strain gauges
Any device with standard industrial outputs
Product Development at NORVI
What is the usual timeline for developing an IoT product from concept to launch?
The timeline for IoT product development typically ranges from 3 to 12 months, depending on the complexity of the solution. Early stages such as requirement analysis, prototyping, and MVP development usually take 8–12 weeks, while certification and mass production may extend the schedule.
At NORVI Controllers, our extensive R&D capabilities and in-house expertise allow us to deliver prototypes and MVPs in less than 4 weeks. By following an agile development approach, we help clients accelerate time-to-market while maintaining industrial-grade quality and compliance.
How do I create an MVP (Minimum Viable Product) for my IoT idea?
An MVP is the fastest way to validate your idea. We help you design, prototype, and test a simplified version of your IoT product with essential features only. This reduces costs and allows you to gather real-world feedback before scaling to a full solution. With our in-house R&D and manufacturing, we can deliver MVPs in weeks, not months.
What steps can I take to bring a product to market with lower initial costs?
Bringing an IoT product to market doesn’t always require heavy upfront investment. You can reduce costs by:
Starting with an MVP (Minimum Viable Product): Instead of building a full solution, validate your idea with a functional prototype first.
Using off-the-shelf hardware platforms: ESP32-based controllers speed up development and lower engineering costs.
Choosing low-volume manufacturing runs: At NORVI Controllers, we accept orders starting from as low as 10 units without additional engineering fees. We can even deliver a sample batch of 2–3 units for initial testing and validation.
Reducing enclosure costs: Instead of expensive injection molding, our in-house milling, machining, and printing facilities enable you to create a unique and professional product at a fraction of the cost.
Leveraging white-label solutions: Many NORVI products are available for white-labelling, helping you enter the market quickly under your own brand.
With our end-to-end development and manufacturing expertise, NORVI helps you minimize upfront costs while ensuring your product is scalable for future growth.
How is developing an industrial IoT product different from a consumer IoT product?
Industrial IoT products require rugged design, long lifecycle support, wide operating temperature ranges, and compliance with industrial standards (e.g., Modbus, RS-485, CAN bus). Consumer IoT products, on the other hand, focus on cost, aesthetics, and ease of use. We specialize in both, offering customized solutions that fit the exact application environment.
What are the key stages in the product development process?
Our IoT product development process includes:
Concept & Feasibility Study
Hardware & Software Design
Prototyping & Testing
Certifications & Compliance
Pilot Production
Mass Manufacturing & Market Launch
This structured approach ensures a faster time-to-market with fewer risks.
How do you ensure my IoT product meets global certifications and compliance?
We follow international standards such as CE, FCC, RoHS, and ISO from the design stage. Our engineers run pre-compliance testing for EMC/EMI, safety, and wireless performance before sending products to accredited labs. This ensures smooth certification approval and helps you avoid costly redesigns later.
Can you help with both hardware and software development for IoT products?
Yes. We provide end-to-end IoT development, including:
Electronics design & embedded firmware
Mobile app & cloud platform integration
Edge computing & AI models
This full-stack capability means you get a single partner for the entire product lifecycle, from PCB design to cloud dashboards.
What role does prototyping play in reducing risks during product development?
Prototyping allows you to validate design, test features, and identify potential issues early. By creating rapid prototypes, we help clients avoid expensive mistakes and make informed decisions. Our in-house prototyping and testing labs ensure you get functional models quickly, reducing time-to-market
Do you offer white-label or custom product development services for startups and OEMs?
Yes, we provide both:
White-label solutions for companies looking to rebrand proven IoT hardware.
Custom product development for startups, enterprises, and OEMs needing tailor-made designs.
With our flexible manufacturing and global component sourcing, we deliver scalable IoT solutions that fit your brand and market needs.
How much does IoT product development cost, and what factors affect the budget?
Costs depend on complexity, certifications, hardware choice, and production volume. A simple MVP may start from close to around a thousand dollars, while a full-scale industrial IoT product can run higher due to ruggedization and compliance testing. We work with clients to optimize budgets and provide transparent cost breakdowns before development begins.
NORVI Operational Lifetime
What is the expected operational lifetime of NORVI Controllers?
NORVI Controllers are designed for industrial-grade reliability. With proper installation and environmental conditions, they typically operate for 7–10 years or longer, ensuring a stable long-term deployment for automation and IoT applications.
Do NORVI Controllers require replacement after a certain number of usage hours?
There is no strict replacement limit based on hours. Lifespan depends more on environmental conditions such as temperature, humidity, and power quality. With proper maintenance, devices can continue to run without predefined replacement schedules.
How often do you release new models of NORVI Controllers?
We introduce hardware refreshes every 2–3 years. These updates add new capabilities while keeping the platform stable and familiar for developers.
What does End of Life (EOL) mean for NORVI products?
NORVI follows a strong long-term support policy. Each product has a minimum lifecycle commitment of 10 years from its release date, ensuring customers can rely on stable availability for industrial and IoT deployments.
When a model approaches End of Life (EOL), NORVI provides at least 18 months of advance notice. This gives customers sufficient time to plan and migrate to newer models without disruptions. Our priority is business continuity and smooth transitions, while maintaining backward compatibility wherever possible.
When was the Raspberry Pi CM4 launched, and how long will it be supported?
The Raspberry Pi Compute Module 4 (CM4) was launched in October 2020. Raspberry Pi Ltd. has committed to supporting it until January 2031, and NORVI aligns its support timeline accordingly.
Are new NORVI models backward compatible with older ones?
Yes. We prioritize pin-to-pin and software compatibility across product generations. In most cases, applications developed for older models can run on new models with minimal or no changes.
How do open-source, Arduino, or Linux-based controllers compare with traditional PLCs in safety?
With the right engineering practices and system design, open-source controllers such as Arduino, ESP32, or Linux-based platforms can achieve the same safety standards as traditional PLCs. While traditional PLCs often come with built-in, certified safety modules, the same level of safety can be implemented using:
Certified safety relays and hardware interlocks for functions like emergency stop (E-stop).
Redundant circuit design and separation of safety logic from general control logic.
Compliance with international standards such as ISO 13849 and IEC 62061.
Thorough risk assessment, validation, and testing during system integration.
By following these best practices, engineering teams can confidently design robust, safe, and reliable automation systems with open-source platforms, while also benefiting from their flexibility and scalability.
Does NORVI offer smaller or more cost-effective hardware platforms?
Yes. NORVI offers entry-level ESP32-based controllers that provide the same software environment as our high-end models. These barebone options are ideal for simpler machines where cost optimization is key.
Check NORVI IIOT Series, ENET and GSM Series for more details.
Can I maintain software compatibility across different NORVI hardware options?
Absolutely. NORVI ensures scalable hardware with cross-compatibility, meaning your software applications can run on both basic barebone models and advanced RPi/ESP32-S3 controllers without major modifications.
Cookie Consent
We use cookies to enhance your browsing experience, analyze site traffic, and personalize content. By continuing to use our site, you consent to our use of cookies. Read our cookie policy
This website uses cookies
Websites store cookies to enhance functionality and personalise your experience. You can manage your preferences, but blocking some cookies may impact site performance and services.
Essential cookies enable basic functions and are necessary for the proper function of the website.
Name
Description
Duration
Geolocation Config
This cookie is used to store the consent settings based on the visitor's location.
30 days
Cookie Preferences
This cookie is used to store the user's cookie consent preferences.
30 days
These cookies are needed for adding comments on this website.
Name
Description
Duration
comment_author
Used to track the user across multiple sessions.
Session
comment_author_email
Used to track the user across multiple sessions.
Session
comment_author_url
Used to track the user across multiple sessions.
Session
Google Tag Manager simplifies the management of marketing tags on your website without code changes.
Name
Description
Duration
cookiePreferences
Registers cookie preferences of a user
2 years
td
Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator.
session
These cookies are used for managing login functionality on this website.
Name
Description
Duration
wordpress_logged_in
Used to store logged-in users.
Persistent
wordpress_sec
Used to track the user across multiple sessions.
15 days
wordpress_test_cookie
Used to determine if cookies are enabled.
Session
WooCommerce is a customizable eCommerce platform for building online stores using WordPress.
Name
Description
Duration
wp_woocommerce_session_
Contains a unique code for each customer so that it knows where to find the cart data in the database for each customer.
2 days
woocommerce_recently_viewed
Powers the Recent Viewed Products widget
session
store_notice
Allows customers to dismiss the Store Notice.
session
woocommerce_snooze_suggestions__
Allows dashboard users to dismiss Marketplace suggestions, if enabled.
2 days
woocommerce_dismissed_suggestions__
Count of suggestion dismissals, if enabled.
1 month
woocommerce_cart_hash
Helps WooCommerce determine when cart contents/data changes.
session
woocommerce_items_in_cart
Helps WooCommerce determine when cart contents/data changes.
session
WP Consent API is a plugin that standardizes the communication of accepted consent categories between plugins.
Name
Description
Duration
wp_consent_{category}
Stores your consent preference for a specific cookie category (e.g., functional, marketing). It ensures consistent consent management across WordPress plugins supporting the WP Consent API.
30 days
WPForms is a user-friendly WordPress plugin for creating custom forms with drag-and-drop functionality.
Name
Description
Duration
wpfuuid
Used to track user interactions with forms.
11 years
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
SourceBuster is used by WooCommerce for order attribution based on user source.
Name
Description
Duration
sbjs_session
The number of page views in this session and the current page path
30 minutes
sbjs_udata
Information about the visitor’s user agent, such as IP, the browser, and the device type
session
sbjs_first
Traffic origin information for the visitor’s first visit to your store (only applicable if the visitor returns before the session expires)
session
sbjs_current
Traffic origin information for the visitor’s current visit to your store
session
sbjs_first_add
Timestamp, referring URL, and entry page for your visitor’s first visit to your store (only applicable if the visitor returns before the session expires)
session
sbjs_current_add
Timestamp, referring URL, and entry page for your visitor’s current visit to your store
session
sbjs_migrations
Technical data to help with migrations between different versions of the tracking feature
session
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
Facebook Pixel is a web analytics service that tracks and reports website traffic.