The following shows the certification steps for ECHONET Lite and ECHONET devices, as well as for AIF devices. Note that the steps to be taken for certification vary between a normal procedure “new application” and “revised/additional application” when applying only for specific items. The following gives an overview of these certification systems.
Tests to be conducted based on authentication test specification document number [C*] shall be carried out while checking actual communication
As shown below, intercept and check communication between the device to be tested and the communication counterpart device flowing into the ECHONET Lite network. As long as you can carry out the test on the items described in the authentication test specifications, you can use the actual devices or test tools for communication counterparts.
When using ECHONET Lite software, you can consider the general-purpose device (e.g. computer) installed with the software as the device to be tested and carry out the same test for full ECHONET Lite devices.
Check the waveform and timing of the communication by measuring communication with the ECHONET Lite middleware adapter (see the diagram below for details). You can check communication by either interception or verification of data received by the communication counterpart. Use development tools and the like for items to check inner operation, such as the error processing procedure.
Check the ECHONET Lite network side using a same test method as the one used for full ECHONET Lite devices. Check the ECHONET Lite middleware adapter communications interface side using the same test method as the one for ECHONET ready devices.
When a company makes an application to acquire ECHONET Lite certification, it must have the same manufacturer code as the product in question. In other words, companies without a manufacturer code cannot apply for certification.
A company that is not a member of the ECHONET CONSORTIUM cannot have products certified.
Applications for certification can be made at any time.
The eligibility of the application documents is assessed and notified by the 10th working day after receiving the application. For further details, please contact a certification body directly.
Applications may be made electronically if the applicant declares that the application documents are based on original paper.
Please contact a certification body directly.
Currently, if only requiring certification for the ECHONET Lite Specification, the certification flow is that the authorized certification body (ECHONET) only carries out documentary screening, and does not conduct certification tests. However, if certification is sought for both the ECHONET Lite Specification and SMA for the product in question, third-party certification tests must be conducted via the authorized certification body (ECHONET) for the ECHONET Lite Specification as well.
In principle, we recommend using the latest Specification version, but products can also be developed and certified using an older Specification version.
For application forms, etc., please contact a certification body directly. Certification test specifications may be obtained from the Members’ Area on the Consortium website.
Since the certification is for products to be sold to ordinary consumers, certification cannot be obtained for evaluation boards or others aimed at developers.
Software packages consisting only of software that cannot provide the user with ECHONET Lite functions on its own, such as DLL, plug-ins, libraries or middleware, are not eligible for certification. For more details, see “Outline of Application for Specification Compliance Certification of ECHONET Lite (Self-certification)”.
This refers to the range of “ECHONET Lite Middleware” specified in the “ECHONET Lite Specification” (mainly Part 2).