DVXplorer: calibration and other problems

76 views
Skip to first unread message

李鑫胜

unread,
Jul 29, 2024, 9:27:55 AM7/29/24
to dv-users

Hello, I encountered some issues when using dv-gui to operate my dvxplorer.

Firstly, after connecting my computer to the event camera using a data cable, I always receive the following prompt at the bottom of the gui:

“USB libusb: error [windows_submit_transfer] program assertion failed - transfer HANDLE is NULL after transfer was submitted”

What could be the reason for this error? How can it be resolved?

Secondly, regarding camera calibration, I tried to calibrate the camera using the calibration module in dv-gui. I used a standard pattern as shown in the image below.

微信截图_20240724170206.png

After attempting calibration, the module was able to detect the pattern, which closely matched the one on the calibration board. However, when I collected enough calibration patterns and tried to calibrate using the program, the following error occurred, preventing the calibration from proceeding.

微信截图_20240724102723.png

Additionally, I tried to use the "save anyway" function to save the retained patterns and current calibration results, but I only received the following error message:

微信截图_20240729164533.png

What could be the reasons for these errors? How can I resolve them?

Furthermore, concerning the E2Calib method, I want to use this method to convert the time output of the event camera into frame output. However, it seems that the official code repository does not support aedat files recorded through dv-gui. How can I convert the format so that the saved file can be used with this method?

Luca Longinotti

unread,
Aug 9, 2024, 9:00:01 AM8/9/24
to dv-u...@googlegroups.com
Hello,

the libusb error on Windows is normal, doesn't mean there's an actual issue, we just print all the messages from the low-level libusb library. You can try to see if it goes away with a DV version built against the latest libusb, our bleeding edge version:
But as I said, not really needed.

Regarding the calibration, it fails to save the file due to the non-ASCII characters in your file-name. On Windows support for international characters is flaky, please make sure that only ASCII (English) characters are present in the username and any file paths.

We currently do not support E2Calib ourselves. But I see they support loading from rosbags, so you could use a ROS integration if you're familiar with ROS and load from there:

Hope this helps, have a nice day!
-- 
Luca Longinotti (llongi)

Staff Embedded Systems and Software Engineer
iniVation AG
A SynSense Group company
Reply all
Reply to author
Forward
0 new messages