Kyocera

The NDD Client and Collector Kyocera modules’ installation remains a manual process, performed directly through the printer’s web interface, following the details outlined in the Kyocera NDD Print Client and Collector manual.

After this step, the ECT module takes over and applies the necessary configurations to the installed components. The steps below describe how to perform them:

Import

Allows you to send settings to multiple equipment units.

1 - Create a file (.csv format) listing the addresses of the equipment units (IP address or hostname) to be configured;

💡

EXAMPLE

ipOuHostname;ipOuHostname;ipOuHostname;ipOuHostname;...
172.31.5.55;172.31.5.190;RNP002673C57A2F;172.31.253.167;...

2 - After creating the file, import it by clicking Import File;

Single Printer

Send configurations to a single piece of equipment.

  • Address: Enter the equipment's address (IP address or hostname).

Local Server

  • Communication Mode: DCS (Port 5656) or HTTPS (Ports 56569 and 56570).

  • NDD Print Host: Enter the address (IP or hostname) of the server where the NDD Print Host module is installed;

  • NDD Print Releaser: Enter the address (IP or hostname) of the server where the NDD Print Releaser module is installed;

Enabled Modules

Select the modules you want to configure:

NDD Print Client

The NDD Print Client section contains the features that can be enabled for clients installed on Kyocera printers

  • Enable Compatible Physical Identifier: Sets the default for reading physical identifiers on the device. ON: Interprets the ID in hexadecimal format. OFF: Interprets the ID in decimal format.

  • Enable Releaser: Enable document retention on the server and configure the Releaser service address in the field below.

  • Enable Environmental Impact: Enables the display of environmental impact metrics (such as paper and energy consumption) directly on the device interface.

  • Release Copies Setting: When enabled, prevents the user from changing the quantity of copies of a document at the time of print release.

NDD Print Client Collector

Module responsible for collecting data on print jobs, meters, supplies, and printer alerts, and sending them to the server. It operates independently.

General Settings

  • Default Domain: Enter the default domain to which jobs without an identified domain will be assigned;

  • Sending time: Enter the time interval (in hours) at which the data captured by the NDD Print Client Collector module will be sent to the server (Host or Data Center).

  • Log server address: Enter the address of the server to which the application will send logs for debugging and troubleshooting.

SNMP Settings

Allows you to choose between SNMP V1/V2 or SNMP V3.

The versions can be configured as follows:

  1. SNMP v1/v2:Select the desired option and enter public or private information in the SNMP Community field.

  2. SNMPv3:

    All of the fields below must be filled in:

    • User;

    • Authentication password;

    • Privacy password;

    • Privacy algorithm: Select one of the options DES or AES-128

    • Random authentication: Select one of the options: SHA1, MD5, SHA-224, SHA-256, SHA-384, or SHA-512

    • Minimum authentication level: Select one of the options:

      • No authentication, no privacy

      • Authentication, no privacy

      • Authentication and privacy

Primary Server

  • MPS/360

    • Server Address: Enter the IP address or hostname of the MPS/360 server.

    • Enterprise Key: Enter the company identification key. If you do not have one, please contact your NDD sales representative.

    • Collect meters and supplies: Make this option active to capture and send meter and supply files (NSL) to NDD Print MPS/360.

    • Accounting Configuration: Select the options for which jobs will be billed: prints, copies, scans, and/or faxes.

  • Host

    • Server Address: Enter the IP address or host name of the server where NDD Print Host is installed.

    • Accounting Configuration:

      • Printings: Makes event logging active for direct print jobs;

      • Copies: Makes event logging active for copy jobs;

      • Scans: Makes event logging active for scan jobs;

      • Faxes: Makes event logging active for fax jobs;

Secondary Server

Allows you to select a secondary server to send data. The configuration is the same as for the Primary Server.

Agent Monitoring (Orbix)

This configuration enables data transmission from the printer to the NDD Orbix, allowing you to adjust the level of monitoring for agents, meters, supplies, and events

  • Orbix Network Address: NDD Orbix address.

  • Dealer: Provider name.

  • Company Identification Key: Company identification key.

  • Collect meters and supplies: Makes the collection and sending of device meter and supply data to the NDD Orbix active;

Multiple Devices

Configure monitoring for up to 20 pieces of equipment.

  • Import File

  1. Create a CSV file containing the addresses of the printers to be monitored

  2. Save the file

  • Only CSV files will be accepted.

  • You can monitor only 20 additional equipment items per NDD Print Collector.

  1. Click “Import File” to send the file

Here's an example:

The address printers 192.168.1.11 (HP), 192.168.1.15 (EPSON), and 192.168.1.18 (LEXMARK) will be monitored by this same NDD PrintCollector.

In this case, the file structure will be as follows:

192.168.0.11;
192.168.0.15;
192.168.0.18;

Communication Test and Error Codes

After making all the necessary configurations, click Send to Printers. A communication test will be performed on the equipment, and the result will be displayed on the ECT printer settings screen.

The communication test process is carried out as follows:

  1. The configurations are sent to the application;

  2. A communication test is performed between the equipment and the configured server (NDD Print Host or Datacenter);

  3. If accounting is enabled, the day’s jobs will be searched for on the equipment, and an NPL file will be generated containing only the last job (in the event of a reconfiguration with the Collector already functioning correctly, an NPL file will no longer be generated; only the retrieval of jobs from the equipment will be validated);

  4. If meters and supplies are enabled, an NSL file will be generated containing the equipment’s meters and supplies;

  5. The files (NPL and/or NSL) will be sent to the configured server.

If all steps are completed successfully, a success message will be returned. If an error occurs in any step, the process will be aborted and an error code will be included in the return message:

Error Code

Possible causes

Error #001

  • The data center is not operational

Error #002

  • Enterprise Key entered incorrectly

  • Data center does not match the Enterprise Key

  • Enterprise Key removed from the data center

Error #003

  • Printer is busy

  • No jobs were printed today to log

  • Incorrect printer administrator user name and/or password

  • Incorrect printer SNMP community

  • Unable to resolve the printer's hostname

Error #004

  • Printer cannot communicate with the specified server

  • Incorrect NDD Print Host address

  • DCS Server port blocked (default 5656)

  • DCS Server service stopped on the server

  • Unable to resolve the server's hostname

Error #005

  • Printer is busy

  • No jobs were printed today to log

  • Incorrect printer administrator user name and/or password

  • Unable to resolve the printer's hostname

Error #006

  • Printer cannot communicate with the specified data center

  • Printer cannot communicate with the Internet (external data center)

  • Incorrect data center address

  • Data center is offline

  • HTTPS port (443) is blocked

Error #007

  • Incorrect printer administrator user

Error #008

  • There is no communication with the printer to be configured

  • The application is not installed on the printer

  • Incorrect address entered

  • Unable to resolve the printer's hostname

Error #009

  • This error usually occurs when the equipment's access credentials are incorrect or because the network is blocked on the ports being used. Check to make sure nothing is blocking the connection (such as firewalls) on port 23.

Error #010

  • If the connection is lost or the device does not respond promptly, check to see if the equipment is still connected or if there is a network block.

Error #011

  • Unable to connect to the NDD Orbix because the Agents SDK service is offline or unavailable.

Error #012

  • We cannot connect to the NDD Orbix because the DCA service is offline or unavailable.

Error #013

  • Unable to connect to the NDD Orbix because the tenant is invalid or the service is offline.

Error #014

  • Error retrieving information from the device or network. Check the equipment's SNMP community.

If a failure occurs while importing the configurations, click Save not configured. This will save all the addresses (IP address or hostname) for these equipment units to a separate .csv file, preventing the process from being repeated on equipment where the import was performed successfully.

Last updated: