Unable to Recharge the prepaid meter

Solution: Connectivity Check: Confirm the meter is successfully communicating with the server. Serial Number Verification (SmartComm): Access the SmartComm Customer Master and ensure the serial number recorded matches the physical serial number of the connected meter. Duplicate Configuration Check: Verify that no two meters are incorrectly configured with the exact same serial number in the system.

Email Configuration SMTP Details Outlook

Solution: SMTP Host/Server Name: For Outlook.com: smtp-mail.outlook.com For Office 365/Microsoft 365: smtp.office365.com SMTP Port:587 (recommended) Encryption Method: STARTTLS Authentication: Your email account needs to be authenticated, so enable login or use the ""My outgoing server (SMTP) requires authentication"" option in your email client. Username: Your full Outlook email address (e.g., yourname@outlook.com or yourname@domain.com) Password: Blank

Email Configuration App Password creation for Gmail account

Reason - Gmail will work only with a secure encrypted app password Solution: Go to your Google Account settings. Navigate to the Security tab. If you don't have it enabled, turn on Two-Step Verification. Find and click on App passwords. Select an app name (like ""SMTP"" or ""Mail Client"") and click Generate. Copy the generated 16-character password and use it in your mail client's password field instead of your main Gmail password.

Email Configuration SMTP Details Gmail

Solution: Gmail SMTP Settings SMTP Server: smtp.gmail.com Port: 587: (requires STARTTLS/TLS) 465: (requires SSL) Authentication: Required Username: Your full Gmail address (e.g., user@gmail.com) Password: An App Password generated from your Google Account security settings Security/Connection: TLS or SSL, depending on the port chosen

Transfer existing sensor to a different gateway

Reason - Loss of old data stored under device id created Solution: To prevent data loss, edit the sensor and use the "Move to Gateway" option to transfer the sensor to a different gateway.

Asset list is not available in the filter

Reason - The asset is not assigned to the organization Solution: Check the asset selection settings in organization settings

Reason - Sensor/gateway limit exceeded Solution: Check license information for sensor/gateway limit

Cannot change the ip address of gateway

Reason - The ip address should is not available Solution: 1. if company network is being used check the accesibility to access 2. check if set ip is with in subnet range 3. Check if Primary and Secondary DNS is correct as per network settings 4. Set the Default Gateway IP to match the router's IP or the company network's default gateway IP.

3rd part meter not communication

Reason - 1. Memory map configuration wrong 2. (10 power -4 )Conversion factor is not available in third party memory map configuration 3. Data on modscan and software is matching but not matching with meter display readings Solution: 1. Verify data via Modscan, check wiring, confirm the meter parameter's datatype/function code in the memory map, and ensure the gateway supports that parameter datatype. 2. Can be added from conversion factor available in Master settings

Could not download certificate

Reason - All mandatory fields are not saved in organisation info settings Solution: All details should be given in mandatory field of organisation settings

Broken Conductor Protection in numrAL FDR22 Relay

Updated: Aug 27, 2026 | 6 min read

Technical Articles

Published: Mar 11, 2026 by Rajesh

Technical Articles

Click on any topic to jump to that section

Introduction

A broken conductor or open circuit fault is one of the most difficult faults to detect in power systems. It often does not cause a significant increase in current, making it hard for standard overcurrent relays to sense.

The Challenge

Standard unbalance protection (ANSI 46) uses negative-sequence current (I2) to detect faults. However, at low load levels, the negative-sequence current produced by a broken conductor can be very small — sometimes even smaller than the normal unbalance present in the system. This makes it risky to set sensitive pickup values without causing false tripping.

The Smart Solution: I2/I1 Ratio

The numrAL FDR22 relay from Lauritz Knudsen uses Broken Conductor Protection based on the I2/I1 ratio (Negative-sequence current to Positive-sequence current).

This ratio remains relatively constant even when load changes, making it a much more reliable way to detect broken conductors or open circuits.

Key Features of FDR22 Broken Conductor Protection

Uses I2/I1 ratio for accurate detection
Pickup setting adjustable from 20% to 100%
Time delay setting from 0.01 sec to 100 sec
Works effectively on both single-point and multiple-earthed systems

Why It Matters

Broken conductor faults can lead to dangerous voltage unbalance, equipment damage, and safety risks. The advanced Broken Conductor Protection in the numrAL FDR22 relay helps detect such faults quickly and reliably, enhancing system safety and protection.

Conclusion

For reliable detection of broken conductors, the Lauritz Knudsen numrAL FDR22 feeder protection relay offers a smart and sensitive solution using the I2/I1 ratio.

Takeaway: Don’t rely only on standard unbalance protection — use dedicated Broken Conductor Protection for better safety.

About the Author

Rajesh R Shirodkar,

DGM-Corporate Communication

Rajesh Shirodkar is a seasoned marketing and business leader with over 20 years of experience in the automation and electrical industry, spanning marketing communications, sales, business development, and software solution selling. He has led successful brand transformation initiatives and high-impact marketing programs, including branding and account-based marketing campaigns, as well as industry events that drive visibility, engagement, and growth. With expertise in brand building, lead generation, solution selling, and sales enablement, Rajesh is known for translating technology and business offerings into compelling value propositions and delivering sustainable growth through strong stakeholder collaboration.