Getting closer, now stuck on RuntimeError: No PROTECTED permissions to override protected EEPROM fields so something else on the EEPROM isn't quite right, or is locked in some way?

  • erik replied to this.

    Hi kneave ,
    If you set environmental variable to DEPTHAI_ALLOW_FACTORY_FLASHING=235539980 (so on linux you can do DEPTHAI_ALLOW_FACTORY_FLASHING=235539980 python3 flash_eeprom.py) it will allow you to do so. Note that usually you wouldn't want to override factory calibration.
    Thanks, Erik

      Thanks Erik, I was able to use that to update the calibration but getting other errors permissions errors now 😅
      Also, it doesn't have a factory calibration apparently. Is this supposed to be the case with the 3P? It doesn't have cameras included so I can see why it wouldn't, but also it seems like not having a calibration at all may be the cause of a bunch of other issues.

      Thanks for all your help so far Erik, and colleagues, I think I'm going to have to spend some time properly getting my head around calibration and how to get it to work with my setup. I was previously using a StereoPi with two fisheye lenses and using the ROS calibration method without issue so I think I got complacent. With the extra power of the 3P it seems it needs more attention to get working. That said, it's tempting just to publish the images from each cameras to ROS and see if I can use the same method to generate the calibration. A bit hacky but I'm willing to try anything at this point! 🤣

      For Windows users seeing the previous post regarding the environmental variable, the equivalent is:
      in command prompt:
      set DEPTHAI_ALLOW_FACTORY_FLASHING="235539980"

      in powershell:
      $env:DEPTHAI_ALLOW_FACTORY_FLASHING="235539980"

      Then run the python script. This will persist until the cmd/powershell session is closed.

        kneave Good point, not sure why depthai complains about eeprom, even if there's no calibration present.. Will bring it up internally with the team. What kind of other permission erros are you getting?

          One I got the calibration done and uploaded to the 3P using the calibration_flash script (it failed to upload via calbration) I then tried to run the depthai_demo.py script and got these when I tried to switch to depth preview:

          I'm on Windows so no udev rules to set which confused me

          2 months later

          Hey folks, other projects have been wrapped up and I'll be able to look at this again next week. It looks like a lot of work has happened in the interim, could I ask which branch I should be using please?

          There are also a few PRs pending that involve calibration, are they worth waiting for them being merged?

          • erik replied to this.

            Hi kneave ,
            You should used latest main branch when calibrating, we have updated the script 2 times since then🙂

              3 months later

              It's been a very long fight getting this far but it looks like the work done to improve the calibration process has paid off so thank you Luxonis and friends for that! My IMX378 isn't being detected any more, hopefully just a dodgy ribbon cable, but I'm at least able to generate a depth map from the two AR0234 cameras.

              Now the hard work of tuning everything to reduce noise and get some usable data out of it 🙂

              erik Hi Erik, sadly it seems the fix didn't work and I can no longer detect the camera. I managed to get some images once but it hasn't worked again since. I've tried replacing the ribbon cable too, and tried another camera on that port to confirm it works (it does) so the sensor is likely broken. I'll email support as per the errata to get a replacement. 🙁

              • erik replied to this.

                  kneave What kind of errata? If it worked once, I don't understand how it could be errata.
                  What doesn't work - could you share terminal output of eg. cam_test.py?

                    Hi Erik, this one. I may not have cut the trace correctly I guess but trying the fix was worth a try, sadly it didn't work out for some reason. Regarding terminal output, it's simply not detected.

                    • erik replied to this.

                      Hi kneave , I see, I think it would be best to send an email to support@luxonis.com (with the link to this discussion) and we will replace the faulty HW asap.

                        7 days later

                        Replacement camera arrived, I just need to figure out how to calibrate the centre along with the sides. I'm going to try to calibrating the sides first then, the centre, then all three together and hoping for the best!

                        Success! I have all three camera's calibrated! I had to mess around with the calibration script quite a bit to override the error bounds for the projection errors between narrow FOV centre and very wide left and right, seems to work though!

                        Also, I love how our black cat, Toby, is literally a void in the depth map! 😅

                        Thank you to everyone for your help, I'll post my code up once I've got it all checked in.

                        13 days later

                        Another update, I've got the depth alignment example working! 😃