FAQ
Frequently asked questions
Answers about functions, applicability, development stage and adoption review.
What is EZIS?
A project developing transmission/reception and received-information decision functions so that signals between sensors and equipment can be used as more reliable information. The FL-1 transmitter/receiver is being developed as the first product.
Do I need to replace my existing sensors?
EZIS focuses on the delivery of correctly measured information. Whether existing sensors can be kept, and how to connect them, is decided after checking electrical characteristics, signal format and installation conditions. EZIS is not presented as a universal product that connects directly to every sensor.
Does it eliminate all noise?
No. It does not mean removing all noise or preventing all errors. EZIS is being developed to judge received information and identify uncertain results. The actual coverage must be verified for each type of disturbance and operating environment.
How does the equipment behave in the hold state?
Hold means that the received information cannot currently be confirmed. Whether to retain the previous value, re-check, or stop the equipment is defined separately according to the operational requirements of the customer's system. The EZIS decision state is kept distinct from the equipment's safety behavior.
Can I buy it now or use it in mass production?
EZIS is currently in development and verification. Price, lead time and production specifications are not confirmed on this site. The approach is to first review applicability and evaluate it in each environment.
How far has it been verified?
Verification using models/simulation and FPGA boards is in progress during development. These results do not mean customer field verification, certification or mass-production readiness. The specific scope of application must be confirmed in the relevant environment.
Can I see technical documentation?
This site provides information on functions and their use from the customer's perspective. Internal operating principles, circuits, algorithms and design values are not disclosed.
What should I prepare to review adoption?
Describe the target equipment, current signal format, link distance, situations in which problems occur, acceptable latency and required behavior in the hold state; this allows the review scope to be defined. See the Adoption page for the checklist.