Hi there! I understand you're having trouble clearing the check engine light with your FIXD OBD2 Scanner because it's taking a long time and there's difficulty in communication. I'd like to help you get this sorted out.

To better assist you, could you please share a bit more detail? For example:
- Are you using the FIXD sensor connected via Bluetooth to your Windows device?
- Does the app or device give any error messages or fail to connect?
- Have you noticed if this happens with all vehicles or a specific one?
- When you say "slow to communicate," do you mean the scanner takes a long time to read or clear codes, or is it not connecting properly at all?

In the meantime, here's a helpful step-by-step guide to troubleshoot this kind of issue:

1. Check the OBD2 Port: Make sure the OBD2 port on your vehicle is clean and free from debris or damage. Sometimes dirt or corrosion can interfere with syncing.

2. Ensure Proper Connection: Plug in the FIXD sensor securely, and turn the vehicle ignition to the "on" position without starting the engine.

3. Bluetooth Connection: Confirm your Windows device is paired with the FIXD sensor. You can do this via your Bluetooth settings.

4. Restart Devices: Turn off the ignition and unplug the FIXD sensor. Restart your Windows device and try reconnecting to the sensor and app.

5. Update the App & Firmware: Make sure the FIXD app on your device is up to date, as well as the sensor firmware if an update is available.

6. Clear Codes via the App: Once connected, use the app feature to read error codes first, then attempt to clear them. Sometimes the clearing process can take a few moments.

7. Check for Vehicle-Specific Issues: Some check engine lights come on for persistent or ongoing issues, so clearing the light without fixing the underlying cause may result in the light returning shortly.

If the communication is still slow or fails after these steps, it might be related to compatibility issues or a faulty sensor. Let me know if you've already tried some of these or how it went, and we can dig deeper!

Are you using the FIXD app on your Windows device or a different platform? This will help me tailor the instructions better.

I have done everything that you mentioned. The FIXD device communicates with my vehicle with no problem until the "clearing the code" moment. The icon just keeps circling without doing anything. The last time I used it, it took about 20 minutes before I cancelled the communication. I think the sensor is faulty.

Thank you for the details you provided. Since your FIXD sensor communicates just fine with your vehicle until the point of clearing the code, where it then gets stuck on the loading icon for an extended time, it's possible that the sensor might be experiencing a firmware or internal issue.

Before we conclude it's faulty, let's try a couple of advanced steps:

1. App Reinstallation and Cache Clearing: If you haven't already, uninstall the FIXD app on your Windows device completely, then reinstall the latest version. This can clear any temporary app glitches interfering with the clearing process.

2. Firmware Update Check: Sometimes the clearing issue can be due to outdated sensor firmware. Connect your sensor to the app and check for any firmware update prompts in the app’s settings.

3. Try Clearing Codes on Another Vehicle (if possible): This helps determine if the problem is sensor-related or vehicle-specific.

4. Check Vehicle’s ECU Status: Some vehicles have restrictions on clearing codes if certain conditions are not met (like the engine not warmed up, or active faults that prevent reset). Make sure the car is in the proper state as indicated by the FIXD app instructions before attempting to clear codes.

If after these steps the problem still persists—especially the icon endlessly circling and never clearing—the sensor could indeed be defective.

In that case, your best next step would be to reach out directly to FIXD support for a warranty replacement or repair. You can contact them via [email protected]. They might also request logs or remote diagnostics from the sensor app to better pinpoint the issue.

If you'd like, I can guide you through a screen check to confirm no app or setup steps were missed before contacting support.

Are you comfortable trying these additional steps? Let me know how you'd like to proceed!