The ZED TOP is intermittently producing corrupted images, a behavior that occurs sporadically over the course of several days without any discernible pattern. I reached out to the manufacturer’s support team, but unfortunately, they are unable to provide any insight into the issue. They suspect that the sensor may be experiencing corruption at certain times, which could be affecting the overall depth perception. The only workaround I’ve found is to close touch, disconnect the sensor, reconnect it, and then restart the project. I’ve attached a few pictures to illustrate the problem.
Sorry you’re having this problem. Unfortunately we’ve never seen this issue before either so we’re not really sure what the problem may be.
If you’ve got the hardware, it might be useful to try the sensor on a different machine or with a different USB cable to see if the problem persists.
Have you tried the sensor with the ZED’s Depth Viewer app? I gather it takes awhile for the problem to appear, but if it also happens in ZED’s app then that what mostly confirm it is a hardware problem.
Hi, thanks for your input! Unfortunately, it’s not possible to test the depth viewer for an extended period since the installation is permanent. That said, we did encounter an issue that might indicate a hardware problem. Essentially, the image became corrupted, and restarting the PC didn’t resolve it. When we reopened the TouchDesigner project, the issue persisted. Eventually, we unplugged the sensor cable, and that seemed to fix it.
Do you have any suggestions or thoughts on what might be causing this?
Unfortunately, that does sound like an issue outside of TouchDesigner so it is hard to say for sure what could be going wrong.
I did notice that you are using an Intel i9 13xxx series processor which are known to have voltage problems that can lead to unstable behaviour. We’ve had number of users with these processors report random crashes inside TouchDesigner, but it is possible that the same issue is causing corruption in either the ZED driver or TouchDesigner without actually causing a crash.
From what we have learned, there is a BIOS update that can be installed to fix the issue, but there is also a chance the processor has been permanently damaged once issues start to appear.
I don’t know if this is your problem, but it might be worth checking out if you can.