• Community

  • Windows Setup with Oak-D Lite has an issue

Thanks a lot Marcel-Jan! The icon issue should be resolved pretty quickly, with the windows one we don't have a solution yet, will be investigating and circle back

      6 days later

      Good day All,

      My apologies for not checking in and monitoring my thread on this. Sadly, all is still a no-go on my side. I tried to install the latest version (v.3.0.9) using the Windows Setup program and it fails to install. Below is the last few lines showing the error
      `Installing collected packages: opencv-python, opencv-contrib-python, depthai, pyqt5, depthai-sdk, argcomplete
      Message Box (Error Installing DepthAI Requirements): Couldn't install DepthAI requirements. Check internet connection and try again. Log available at: E:\Software\DepthAI\depthai\launcher\log.dat
      Install dependencies call failed with return code: 1, message: WARNING: Ignoring invalid distribution -yqt5 (e:\software\depthai\venv\lib\site-packages)
      WARNING: Ignoring invalid distribution -yqt5 (e:\software\depthai\venv\lib\site-packages)
      WARNING: Ignoring invalid distribution -yqt5 (e:\software\depthai\venv\lib\site-packages)
      WARNING: Ignoring invalid distribution -yqt5 (e:\software\depthai\venv\lib\site-packages)
      WARNING: Ignoring invalid distribution -yqt5 (e:\software\depthai\venv\lib\site-packages)
      WARNING: Ignoring invalid distribution -yqt5 (e:\software\depthai\venv\lib\site-packages)
      WARNING: Ignoring invalid distribution -yqt5 (e:\software\depthai\venv\lib\site-packages)
      WARNING: Ignoring invalid distribution -yqt5 (e:\software\depthai\venv\lib\site-packages)
      WARNING: Ignoring invalid distribution -yqt5 (e:\software\depthai\venv\lib\site-packages)
      WARNING: Ignoring invalid distribution -yqt5 (e:\software\depthai\venv\lib\site-packages)
      WARNING: Ignoring invalid distribution -yqt5 (e:\software\depthai\venv\lib\site-packages)
      WARNING: Ignoring invalid distribution -yqt5 (e:\software\depthai\venv\lib\site-packages)
      WARNING: Ignoring invalid distribution -yqt5 (e:\software\depthai\venv\lib\site-packages)
      WARNING: Ignoring invalid distribution -yqt5 (e:\software\depthai\venv\lib\site-packages)
      ERROR: Could not install packages due to an OSError: [WinError 5] Access is denied: 'E:\Software\DepthAI\venv\Lib\site-packages\PyQt5\QtCore.pyd'
      Check the permissions.

      WARNING: Ignoring invalid distribution -yqt5 (e:\software\depthai\venv\lib\site-packages)
      WARNING: Ignoring invalid distribution -yqt5 (e:\software\depthai\venv\lib\site-packages)
      Traceback (most recent call last):
      File "E:\Software\DepthAI\depthai\install_requirements.py", line 47, in <module>
      subprocess.check_call(pip_package_install + ["-r", "requirements.txt"], cwd=scriptDirectory)
      File "E:\Software\DepthAI\WPy64-3950\python-3.9.5.amd64\lib\subprocess.py", line 373, in check_call
      raise CalledProcessError(retcode, cmd)
      subprocess.CalledProcessError: Command '['E:\Software\DepthAI\venv\Scripts\python.exe', '-m', 'pip', 'install', '-U', '--prefer-binary', '-r', 'requirements.txt']' returned non-zero exit status 1.`

      I then uninstalled everything and performed the manual installation via git, etc. All installed, but when I try and run the demo script, I get the same error as before:

      E:\Software\depthai>python depthai_demo.py
      Using depthai module from: C:\Users\sam\AppData\Roaming\Python\Python39\site-packages\depthai.cp39-win_amd64.pyd
      Depthai version installed: 2.14.1.0.dev+27fa4519f289498e84768ab5229a1a45efb7e4df
      Setting up demo...
      Available devices:
      [0] 18443010F158AB1200 [X_LINK_UNBOOTED]
      USB Connection speed: UsbSpeed.HIGH
      Enabling low-bandwidth mode due to low USB speed... (speed: UsbSpeed.HIGH)
      Creating MJPEG link for MonoCamera node and left xlink stream...
      Creating MJPEG link for MonoCamera node and right xlink stream...
      Creating MJPEG link for ColorCamera node and color xlink stream...
      Error while running demo script... Command '"C:\Users\sam\AppData\Local\Programs\Python\Python39\python.exe" depthai_demo.py --noSupervisor --guiType qt' returned non-zero exit status 3221226505.
      Waiting 5s for the device to be discoverable again...
      Setting up demo...
      Available devices:
      [0] 18443010F158AB1200 [X_LINK_UNBOOTED]
      USB Connection speed: UsbSpeed.HIGH
      Enabling low-bandwidth mode due to low USB speed... (speed: UsbSpeed.HIGH)
      Creating MJPEG link for ColorCamera node and color xlink stream...
      Traceback (most recent call last):
      File "E:\Software\depthai\depthai_demo.py", line 998, in <module>
      s.runDemo(args)
      File "E:\Software\depthai\depthai_helpers\supervisor.py", line 46, in runDemo
      subprocess.check_call(' '.join([f'"{sys.executable}"', "depthai_demo.py"] + new_args), env=new_env, shell=True, cwd=repo_root)
      File "C:\Users\sam\AppData\Local\Programs\Python\Python39\lib\subprocess.py", line 373, in check_call
      raise CalledProcessError(retcode, cmd)
      subprocess.CalledProcessError: Command '"C:\Users\sam\AppData\Local\Programs\Python\Python39\python.exe" depthai_demo.py --noSupervisor --guiType cv' returned non-zero exit status 3221226505.
      Sentry is attempting to send 2 pending error messages
      Waiting up to 2 seconds
      Press Ctrl-Break to quit

      I never had a chance to try and install on another Win10 machine, but will try to do so over the next few days.

      Cheers,

      Sam

        sam512bb Thanks for reporting both of these!

        For the first issue, I'll share it internally and we'll investigate it further.

        For the second issue, could you try running the demo either with -usbs usb2 flag or connecting your DepthAI device with a USB3 cable and see if that helps?

            Luxonis-Lukasz
            Sure, I can do both. Technically I am using a USB3 cable made by Molex...but perhaps there is something not quite right with it. I will buy another USB Cable from a different manufacturer and will give it a try and will report back... in afew days time, as I am a bit swamped these days.
            Thanks again for your and everyone's assistance!
            Cheers,
            Sam

                sam512bb Sounds great, hope it works, thanks!

                Regarding the first issue - how does your E:/ partition look like, is there anything specific in its configuration? I'd like to reproduce the installation issue so this will be very helpful

                    Luxonis-Lukasz
                    My setup is nothing overly complicated. I am using Win10 Pro with an SSD for my C Drive that has the usual Windows files, etc and other folders that are used infrequently. The E Drive is a hard drive (1 TB) that I use for frequently used files. I typically install applications on my E Drive in a separate directory (E:\Software). Although I take a performance hit with using a hard drive, I find that hard drives are still far more reliable than SSD drives (I have had only 1 HD failure in 7 years as compared to 3 SSD in just 4 years). However, YMMV. That being said, the E drive has no real special setup parameters.
                    When I used the Windows Setup program, I downlaoded it and ran it with Administration privilege to ensure it had full control over file/folder creation, etc.
                    Cheers,
                    Sam

                      Thanks a lot, this will be very helpful! I'll try to recreate and circle back if I find the issue. Also, please let me know if using a different partition with installer helps in your case, will allow us to be more confident it's the partition that's causing this issue

                      3 months later

                      Looks like this is my problem also. Windows install with Oak-D Lite, USB-C.

                      • erik replied to this.

                        Hello billscom , could you provide the full terminal log, please? I suspect it's a faulty USB3 (or USB2) cable.
                        Thanks, Erik

                          erik,

                          Where is this log located? I looked but cannot find these log files.

                          • erik replied to this.

                            Hello billscom , it should be in the terminal from which you started the depthai demo app - where you executed python depthai_demo.py.
                            Thanks, Erik

                              17 days later

                              I installed DepthAI using the Windows Installer a few days ago. Today, on startup it alerted that there is a new version of depthai available and asked to perform an update. I clicked "Yes".

                              It gave a list of tasks...was not sure if it did anything.

                              From then on, the DepthAI demo was BROKEN. I ran it from the command line to see the errors and "depthai" was missing.

                              Re-installing did not solve the problem. I had to uninstall and then re-install to force all dependencies to be installed.

                              • erik replied to this.

                                SpudTheBot If the error won't get fixed, I would suggest cloning the repo from depthai and run the depthai_demo.py via terminal.
                                Thanks, Erik

                                  22 days later

                                  Hi,
                                  I just got my D Lite a couple of days ago. I installed DepthAI via the windows installer software. No errors or anything came up. When I click on the DepthAI icon. It comes up and then nothing.. No errors or anything. Any thoughts? THe hardware is plugged in.. Thank you!
                                  Sincerely,
                                  tom

                                  Same problem as above - installed 3.0.12 and will not run - nothing happens at all.. Windows 10 Pro 64 21H2 and (against my better judgement) Windows 11 Pro 64 22H2 are both doing the same thing. USB 3.0 hosts working with other devices, using supplied cable. Can look into it further but thought it was worth echoing/pointing out there appears to be a problem with the current installer.