Diagnostic steps for Dejavoo Z11 'System Failure' errors. Focus on external causes & safe procedures for retail environments.
Check the warranty status with Dejavoo, as repair or replacement may be covered.
If yes, the update may have been corrupted, causing the failure.
This can point to a larger electrical problem in the store.
The "System Failure" error on a Dejavoo Z11 usually indicates a failure during the boot process or a critical runtime error. This can stem from corrupted firmware, hardware initialization failures (memory, CPU, peripherals), or power instability affecting sensitive components. EMV/NFC functionality relies on secure cryptographic modules; any interruption or corruption of their firmware can trigger a 'System Failure'. The Z11 uses flash memory to store its operating system and applications. A sudden power loss during a write cycle to this memory can corrupt the data and cause the system to fail.
Do not attempt to open the device casing. The Dejavoo Z11 contains tamper-evident seals and opening the device will void the warranty and may trigger security mechanisms rendering the device unusable. Ensure the power outlet is properly grounded. Avoid operating the device in areas with high humidity or extreme temperatures. Do not use excessive force when connecting or disconnecting cables.
Regularly inspect and maintain cables to prevent strain and damage. Ensure the device is placed in a location with adequate ventilation. Clean the touchscreen with a microfiber cloth and approved screen cleaner to prevent buildup that can interfere with touch input. Consider using a surge protector to protect against power fluctuations. Ground the device properly to minimize ESD risk, especially during dry winter months.
In some cases, a 'System Failure' message is triggered by an invalid configuration. Try pressing and holding the 'Clear' key during boot-up. This might clear the configuration and allow the device to boot. This is a non-destructive test and does not violate the PCI-PTS security. Keep detailed logs of any observed error codes or behaviours during troubleshooting.