August 2025

It is now possible to configure alerts for Brother network thermal printers directly in NDD Orbix. This allows for more efficient monitoring, ensuring continuity of operations.

The following alerts already available in the system are also compatible with Brother printers:

Open printhead
Cold printhead
Invalid printhead
Printhead too hot
Cutter jammed
Printhead shutdown
Thermistor fault
Thermal printer offline
Clean printhead
Low label
Low ribbon
No label
No ribbon
Replace printhead

Information

For more information on how to issue and manage alerts, access Configure alerts.

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.1 and the NDD - Thermal Monitor (Windows) service to version 1.3.0, respectively, as instructed at Update the agent or gateway on portal.

Fixes

Service did not start searching for printers (Service: NDD - Printer Monitor)

During the remote configuration download process — both in the initial download (performed when starting the service) and in the routine download (performed at configurable intervals) — when the server was not yet fully available to respond to requests, a 404 (Not Found) error occurred, impairing communication between the agent and the portal.

To correct this, we implemented an automatic retry mechanism to handle HTTP 404 errors:

During the initial download, the agent will retry every 30 seconds, continuously, until it succeeds or encounters an error other than 404.
During the routine download, up to 6 attempts will be made. After the sixth attempt, the process will resume in the next cycle, according to the configured interval.

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.1 and the NDD - Printer Monitor (Windows) service to version 1.1.21, respectively, as instructed at Update the agent or gateway on portal.

Approvals

Approved network printers (Service: NDD - Printer Monitor)

	Meters capture	Supplies capture
Brother	HL-L5210DN	HL-L5210DN
Epson	EM-C8100 SC T3100X	EM-C8100 SC T3100X
Lexmark	XC2335 XC2326	XC2335 XC2326
Pantum	CM2100ADW	CM2100ADW
Xerox	VERSANT 4100 VERSALINK C415	VERSANT 4100 VERSALINK C415

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.1 and the NDD - Printer Monitor (Windows) service to version 1.1.21, respectively, as instructed at Update the agent or gateway on portal.

Adjusted network printers models (Service: NDD - Printer Monitor)

Xerox	ALTALINK C8035
Epson	WF-M5399 WF-M5899 WF-C878R
Konica	BIZHUB C300i

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.1 and the NDD - Printer Monitor (Windows) service to version 1.1.21, respectively, as instructed at Update the agent or gateway on portal.

Approved USB printers (Service: NDD - Printer Monitor USB)

	Meters capture	Supplies capture
Brother	MFC-L8610CDW	MFC-L8610CDW
Epson	L4260 L3110	L4260
Lexmark	CX625adhe M1242 M1342 XC2326 XC2335 XC4342	CX625adhe M1242 M1342 XC2326 XC2335 XC4342
HP	-	Laser 107w

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.1 and the NDD - Printer Monitor USB (Windows) service to version 1.1.13, respectively, as instructed at Update the agent or gateway on portal.

Adjusted USB printers models (Service: NDD - Printer Monitor USB)

Ricoh

SP 310SFNw
P502

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.1 and the NDD - Printer Monitor USB (Windows) service to version 1.1.13, respectively, as instructed at Update the agent or gateway on portal.

Approved thermal network printers (Service: NDD - Thermal Monitor)

	Odometers capture	Supplies capture
Brother	TD-4420DN TJ-4121TN	TD-4420DN TJ-4121TN

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.1 and the NDD - Thermal Monitor (Windows) service to version 1.3.0, respectively, as instructed at Update the agent or gateway on portal.

August 21, 2025

New features

New odometer report

We have implemented a new predefined and customized report: Odometers (Column display).

This report was developed to provide a detailed and accurate view of the yield of network and USB thermal printers, providing odometer data and the quantity of labels/cards printed during a selected period.

The main objective of this new report is to provide managers and administrators with a quick and clear analysis of the yield of each thermal printer, allowing:

Better monitoring of equipment usage.
More rigorous control of yield per unit of measure.
Support in decision making related to maintenance, replacement or relocation of printers.

To offer greater flexibility in data analysis, the report allows you to choose the unit of measurement used in the odometer calculation. The available options are:

Manufacturer default: uses the original unit provided by the printer, without conversion.
Centimeter, Meter or Kilometer: automatically converts all measurements according to the selected option.

The report displays the following fields, with the data organized in columns:

Customer: name of the customer where the printer is installed.
Site: location/site of the printer.
Department: department where the printer is located.
Thermal printer: name of the printer.
Serial number: unique serial number of the printer.
Asset number: asset number of the printer (if configured).
Manufacturer: manufacturer of the printer.
Model: model of the printer.
Network/USB address: connection address of the printer (IP or hostname).
Managed: indicates whether the printer is being managed by the system.
Initial reading date: date of the first reading considered for the calculation.
Final reading date: date of the last reading within the selected period.
Odometer measurement unit: unit of measurement used for the odometer.
Initial odometer: value of the odometer at the first reading.
Final odometer: value of the odometer in the last reading.
Odometer production: total produced in the period (difference between the final and initial odometer).
Number of prints initial: total number of prints in the first reading.
Number of prints final: total number of prints in the last reading.
Number of prints production: total number of prints in the period (difference between the final and initial values).

For more information on how to generate reports, access Generate predefined reports and Generate customized reports.

August 12, 2025

New features

Automatic adjustment of service startup type (Agent: DCA and Cloud Connector)

In some scenarios, certain services were installed with the Startup Type (ST) set to Automatic, or had this setting changed by the user. However, the responsibility for starting or stopping these services lies solely with the DCA and Cloud Connector agent. Therefore, only the agent should remain with the ST set to Automatic, while the services should be set to Manual.

Starting with this update, during service monitoring, the DCA and Cloud Connector agent will automatically check the ST of each service. If it identifies any services set to Automatic, it will automatically correct them to Manual.

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.0, as instructed at Update the agent or gateway on portal.

Fixes

Services running with incorrect information in memory prevented activation (Agent: DCA and Cloud Connector)

In some scenarios (likely caused when the Startup Type (ST) of a service was set to Automatic), certain services ran with incorrect information in memory, which prevented them from activating.

Example:

The DCA and Cloud Connector agent installation is started and the NDD - Printer Monitor service is installed with the ST set to Automatic. Because it is in this mode, the service starts immediately after installation, before the agent assigns the correct information in the appsettings.

The service runs and attempts to communicate with the NDD Orbix portal, but fails due to incorrect data.

Although the agent updates the service's appsettings, since it is already running, the information loaded into memory remains incorrect.

This prevents the service from activating due to incorrect information.

Now, on every monitoring, the DCA and Cloud Connector agent will validate the following essential information for each service:

Tenant (provider)
OrganizationId (customer key)
NDD Orbix URL
IsEnabled (indicates whether the service is enabled in the NDD Orbix portal)

If any discrepancies are identified, the agent will update this information in the appsettings of the respective service. If the service is running (enabled in the portal), it will be restarted so that the correct information is loaded into memory. If the service is stopped (disabled in the portal), nothing happens.

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.0, as instructed at Update the agent or gateway on portal.

August 07, 2025

Fixes

Inconsistency in the calculation of pages with savings in the EcoPrint Comparative report (Service: NDD - Supply Watch)

In the EcoPrint Comparative report, we identified that the number of pages with savings recorded in the period was higher than that indicated by the printer meter. The analysis showed that the same accounting (number of pages printed with savings) was being saved in the database several times.

The problem occurred when sending data from the NDD - Supply Watch service to the NDD Orbix portal. In situations of high usage volume, the process could not handle the level and resent the same information repeatedly, resulting in duplicate data.

To correct this, we made improvements to the NDD - Supply Watch service to support high data levels, created mechanisms to prevent duplicate data from being sent, and implemented the sending of a unique identifier for each accounting sent to the NDD Orbix portal.

In addition, we performed optimizations and performance improvements to speed up data processing, and included mechanisms to identify duplicates using the unique identifier implemented, discarding repeated readings.

The DCA and Cloud Connector (Windows) agent must be updated to version 1.1.31 and the NDD - Supply Watch (Windows) service to version 1.2.1, respectively, as instructed at Update the agent or gateway on portal.

August 04, 2025

Improvements

New fields in the response of the GET /v1/organizations/{organizationId}/printers and GET /v1/printers endpoints of the Printers API

To make the response more complete and facilitate data integration and consumption, the following field has been added to the return of the GET /v1/organizations/{organizationId}/printers and GET /v1/printers endpoints:

siteId: identifier of the site where the printer is located.

Developer Portal ➝