Pt1.xml to V4L2 mapping fails

bobmc-rmm commented 4 years ago

V4L2 mapping issues occur with the pt1.xml on Xubuntu 19.10 Processing statistics: 275 constants processed (0 failed, 275 successful) 134 controls processed (0 failed, 134 successful) 134 mappings processed (31 failed, 103 successful)

Loading control definition file pt1.xml for /dev/video0 Importing dynamic controls from file pt1.xml. Available meta information: File format: 3.3 Author: GetLab Contact: contact@groupgets.com Copyright: Copyright (c) GroupGets 2017 Revision: 2.0 pt1.xml: error: video0: unable to map 'LEP_CID_AGC_ROI' control. ioctl(UVCIOC_CTRL_MAP) failed with return value -1 (error 22: Invalid argument)

pt1.xml: error: video0: unable to map 'LEP_CID_AGC_STATISTICS' control. ioctl(UVCIOC_CTRL_MAP) failed with return value -1 (error 22: Invalid argument)

pt1.xml:3848: error: Invalid V4L2 control type specified: 'V4L2_CTRL_TYPE_STRING'

pt1.xml: error: video0: unable to map 'LEP_CID_OEM_SOFTWARE_VERSION' control. ioctl(UVCIOC_CTRL_MAP) failed with return value -1 (error 22: Invalid argument)

pt1.xml:3946: error: Invalid V4L2 control type specified: 'V4L2_CTRL_TYPE_STRING' pt1.xml:4184: error: Invalid V4L2 control type specified: 'V4L2_CTRL_TYPE_STRING' pt1.xml:4198: error: Invalid V4L2 control type specified: 'V4L2_CTRL_TYPE_STRING' pt1.xml:4296: error: Invalid V4L2 control type specified: 'V4L2_CTRL_TYPE_STRING' pt1.xml:4408: error: Invalid V4L2 control type specified: 'V4L2_CTRL_TYPE_STRING' pt1.xml:4450: error: Invalid V4L2 control type specified: 'V4L2_CTRL_TYPE_STRING' pt1.xml:4464: error: Invalid V4L2 control type specified: 'V4L2_CTRL_TYPE_STRING' pt1.xml:4548: error: Invalid V4L2 control type specified: 'V4L2_CTRL_TYPE_STRING'

pt1.xml: error: video0: unable to map 'LEP_CID_RAD_HOUSING_TCP' control. ioctl(UVCIOC_CTRL_MAP) failed with return value -1 (error 22: Invalid argument)

pt1.xml: error: video0: unable to map 'LEP_CID_RAD_SHUTTER_TCP' control. ioctl(UVCIOC_CTRL_MAP) failed with return value -1 (error 22: Invalid argument)

pt1.xml: error: video0: unable to map 'LEP_CID_RAD_LENS_TCP' control. ioctl(UVCIOC_CTRL_MAP) failed with return value -1 (error 22: Invalid argument)

pt1.xml:4702: error: Invalid V4L2 control type specified: 'V4L2_CTRL_TYPE_STRING' pt1.xml: error: video0: unable to map 'LEP_CID_RAD_SPOTMETER_ROI' control. ioctl(UVCIOC_CTRL_MAP) failed with return value -1 (error 22: Invalid argument)

pt1.xml:4786: error: Invalid V4L2 control type specified: 'V4L2_CTRL_TYPE_STRING' pt1.xml:4800: error: Invalid V4L2 control type specified: 'V4L2_CTRL_TYPE_STRING'

pt1.xml: error: video0: unable to map 'LEP_CID_RAD_RADIO_CAL_VALUES' control. ioctl(UVCIOC_CTRL_MAP) failed with return value -1 (error 22: Invalid argument)

pt1.xml: error: video0: unable to map 'LEP_CID_SYS_CAM_STATUS' control. ioctl(UVCIOC_CTRL_MAP) failed with return value -1 (error 22: Invalid argument)

pt1.xml: error: video0: unable to map 'LEP_CID_SYS_FLIR_SERIAL_NUMBER' control. ioctl(UVCIOC_CTRL_MAP) failed with return value -1 (error 22: Invalid argument)

pt1.xml:4996: error: Invalid V4L2 control type specified: 'V4L2_CTRL_TYPE_STRING'

pt1.xml: error: video0: unable to map 'LEP_CID_SYS_SCENE_STATISTICS' control. ioctl(UVCIOC_CTRL_MAP) failed with return value -1 (error 22: Invalid argument)

pt1.xml: error: video0: unable to map 'LEP_CID_SYS_SCENE_ROI' control. ioctl(UVCIOC_CTRL_MAP) failed with return value -1 (error 22: Invalid argument)

pt1.xml:5066: error: Invalid V4L2 control type specified: 'V4L2_CTRL_TYPE_STRING' pt1.xml:5123: error: Invalid V4L2 control type specified: 'V4L2_CTRL_TYPE_STRING' pt1.xml:5151: error: Invalid V4L2 control type specified: 'V4L2_CTRL_TYPE_STRING' pt1.xml:5193: error: Invalid V4L2 control type specified: 'V4L2_CTRL_TYPE_STRING'

pt1.xml: error: video0: unable to map 'LEP_CID_VID_FOCUS_ROI' control. ioctl(UVCIOC_CTRL_MAP) failed with return value -1 (error 22: Invalid argument)

pt1.xml:5319: error: Invalid V4L2 control type specified: 'V4L2_CTRL_TYPE_STRING' Processing statistics: 275 constants processed (0 failed, 275 successful) 134 controls processed (0 failed, 134 successful) 134 mappings processed (31 failed, 103 successful)

bobmc-rmm commented 4 years ago

The PT1.xml was generated by a python script two years ago. I suppose that the Linux libraries such as V4L2 have changed since then so the script needs to be updated such that pt1.xml is compatible with Linux today.

v4l2/uvcdynctrl/ctrl_gen.py

tuxx1112 commented 4 years ago

I'm currently also trying to use the CCI commands on my Flir Lepton 3.5 and received the same processing statistics. How should this pt1.xml file be edited such that all mappings are successful? I'm not familiar with this.

Hortiya-MWH commented 3 years ago

I am experiencing the same issue with the Purethemal2 and Lepton 3.5. Even the commands that are successful do not execute as expected. lep_cid_sys_ping 0x08030001 (button) does not return LEP_OK and lep_cid_sys_cam_uptime 0x08030004 (int) does not return the time in ms. I have the assumption that the API on the cam changed and hence the mapping has du be updated.

lucasdrandrade commented 1 year ago

Hi, I'm facing the same problem.

I actually have a PT mini and a Lepton 3.5. My main goal was to change the FFC desired period.

I thought i could make it using uvcdynctrl. But it seams like because of this issue in mappings i couldn't find the LEP_CID_SYS_FFC_SHUTTER_MODE_OBJ command after executing the command uvcdynctrl -v -d /dev/video0 -i pt1.xml

Has anyone finded out how to solve this mapping problems?

groupgets / purethermal1-uvc-capture

Pt1.xml to V4L2 mapping fails #19

V4L2 mapping issues occur with the pt1.xml on Xubuntu 19.10 Processing statistics: 275 constants processed (0 failed, 275 successful) 134 controls processed (0 failed, 134 successful) 134 mappings processed (31 failed, 103 successful)