INFO: point-cloud-projection depthAI branch information about depthai-experiments HOT 6 CLOSED

Hey, This is working in depthai 0.1.0 version and depthai 0.2.0 has changed and this file doesn't work on that as of now. (if you have depthai_demo.py it's 0.2.0).
That being said. Here is another branch which comes with pcl included
In this branch to make it work you need to have the new updated calibration. you can test if your device has new two hompgrahy calibration by checking the EEPROM version which is printed when the device starts. you can update this by recalibrating too.

In the meantime I will update this with the current main branch.

from depthai-experiments.

@VanDavv I tried twice some times back but didn't work for me. Give me a day I can test and update the same. Thanks.

from depthai-experiments.

Hi @nullbyte91, the point-cloud-projection has been migrated to the new API and merged to master in #6 . Could you give it a try and confirm if it works?

from depthai-experiments.

@VanDavv @saching13
As expected, I was getting the EEPROM error. I tried re calibration for the modular camera(BW1098FFC), then I tried writing them to EEPROM, and got the core dump when I executed the below command.

python3 depthai_demo.py --store-eeprom -brd bw1098ffc

Calibration file is outdated. Re calibration required before writing to EEPROM.
To continue using old calibration disable('-e') write to EEPROM.[1]    28342 abort (core dumped)  python3 depthai_demo.py --store-eeprom -brd bw1098ffc

FYI. I've not tried the EEPROM writing before so not sure what might be the issue. And, I'm using master branch for both depthai and depthai-experiments repo.

from depthai-experiments.

Hey @nullbyte91 could you checkout to develop branch. (it looks like you are already on develop branch) so if you want to write to EEPROM on develop branch you need to recalibrate. if you have previously calibrated and didn't delete the images captured and stored in the dataset folder you can just run python3 calibrate.py -s [sq size] -brd bw1098ffc -m process. once you have done that you should be able to overcome that error on store EEPROM.

from depthai-experiments.

@nullbyte91 can we close this issue? Did @saching13 suggestion work?

from depthai-experiments.