Air-Flow S2 not starting after power cycle
open
Dr. Michael Chen
Dentist•Nov 28, 2024
Hello everyone,
I've been experiencing an issue with my Air-Flow S2 unit. After a power cycle (turning off and on), the device doesn't start properly. The LED indicator blinks red three times and then stays off.
I've tried the following troubleshooting steps:
- Checked all cable connections
- Verified the power outlet is working
- Waited 30 seconds before turning back on
Has anyone experienced this issue before? Any suggestions would be greatly appreciated.
Thank you!
3 Replies
EMS Support TeamEMSNov 28
Hello Dr. Chen,
Thank you for reaching out. The red LED blinking pattern you described typically indicates a firmware communication error.
Please try these steps:
1. Disconnect all handpieces from the unit
2. Unplug the power cord for 60 seconds
3. Reconnect the power and wait for the boot sequence to complete
4. Then reconnect the handpieces one by one
If the issue persists, please contact your local EMS representative for a diagnostic check.
Dr. Michael ChenNov 28
Thank you for the quick response! I'll try the 60-second power-off method. Just to clarify - should I disconnect the water line as well, or just the handpieces?
EMS Support TeamEMSNov 28
Good question! No need to disconnect the water line - just the handpieces and the power cord. The water connection doesn't affect the boot sequence.
Dr. Sarah MitchellNov 29
I had a similar issue last month. In my case, it was a loose connection on the handpiece port. Try checking if the connector pins are clean and properly aligned.
Also, make sure your firmware is up to date - there was a known bug in version 2.1 that caused boot issues.
Dr. James WilsonNov 29
Can confirm the firmware bug! I updated to v2.3 last week and the boot issues disappeared completely. You can download it from the EMS portal.
Accepted Solution
Dr. Michael ChenNov 29
Thank you both for the suggestions!
I followed the EMS Support steps and also cleaned the connector pins as Dr. Mitchell suggested. The unit is now starting properly.
It turned out to be a combination of a loose connection and needing a longer power-off time. Marking this as resolved!
