Jump to content

Intermittent No sensor found error


---
 Share

Recommended Posts

---

Hello,

I upgraded the laptop the ATOS Q camera is using to windows 11. Since then, every so often when I turn on the camera it does not initialize and when I go to help > System Analysis > Sensor and after it doesn't find it I have to click on Correct System and restart the computer. After that it works. The Camera is attached through the thunderbolt connection straight to the laptop. Below is the error I get when it looks for the camera. Any help would be great.

image.thumb.png.acf6f36d40d0a6e728b3e499382e74bd.png

Link to comment
Share on other sites

---

Hi Austin,

 

it seems that the ethernet device is not set up correctly. Have you tried to use the correct system button? That should fix your issue.

Link to comment
Share on other sites

---

Yes I have to use the correct system button every time this comes up. it fixes it for a few days but then it comes back again.

Link to comment
Share on other sites

  • 2 weeks later...
---

Hi Austin,

Hardware issues are hard to fix via the forum. Please contact you local partner/SSC to get help.

Link to comment
Share on other sites

---

I havent used win 11 with atos systems , but as a guess iit sounds like the ip addresses for your card are being reset every time you turn on your pc.  This could be that the settings in the card arnt set to havs a fixed ip adress , an external it policy thing or perhaps windows itself.

Agree hardware issues are extremely difficult to resolve without physically diagnosing.

Link to comment
Share on other sites

---

Please sign in to view this quote.

Please sign in to view this username.

 I am not sure if this will fix your problem, but when I upgraded to Windows 11 I kept having ZQS X-ray Pro 2023 revert to Viewer Only mode (like the free version). I did some investigating, and something in Windows 11 constantly scans processes for potential malware etc. For whatever reason, it saw CODEMETER RUNTIME processes as malware and would shutdown the service. Try this fix, worked for me and I haven't had an issue since.

 

To ensure that a service, such as the CodeMeter Runtime, refires immediately after it is canceled (stopped) in Windows Services (services.msc), you can configure the recovery options for the service. Here's how to do it:

Open Services Management Console:

Press Win + R to open the Run dialog.

Type services.msc and press Enter.

Locate the CodeMeter Runtime Service:

In the Services window, scroll down to find the "CodeMeter Runtime" service or whatever it's named in your installation.

Open Service Properties:

Right-click on the CodeMeter Runtime service and select Properties.

Configure Recovery Options:

Go to the Recovery tab.

You will see options for First failure, Second failure, and Subsequent failures.

For each of these options, you can select Restart the Service from the dropdown menu.

You can also specify a time delay in the Reset fail count after and Restart service after fields (for example, set these to 1 minute).

Apply Changes:

Click OK to save your changes.

 

I set mine to 1 sec or immediately, so when Windows 11 randomly decides CodeMeter Runtime is malicious, it refires immediately, never dropping the license.

 

 

Link to comment
Share on other sites

 Share

×
×
  • Create New...