Results 1 to 7 of 7

Thread: Suggested triggered camera controls

  1. #1
    Join Date
    Jul 2017
    Posts
    12

    Suggested triggered camera controls

    Hi,

    Im setting up a system that uses a GUI built in glade to display the camera's output. The camera while in normal operation will run in triggered mode. Its basically going to take pictures of a fast moving object that repeats itself and based on encoder and index from the controller. There will likely be a selectable free run mode. I'd also like to have it so the camera's resolution can be changed to act as a digital zoom. There will also be a high power flash.

    So I built a GUI file in glade that I'll have to send off to a Python programmer so he can add the functions I've laid out in glade. I have buttons for operator selectable camera controls. I'm wondering what functions I should leave in auto and what I should probably allow the operator to to control through the GUI. I'm thinking exposure and iris probably but I'm not sure. Obviously I have to test it in the field but I'm looking for a starting point. maybe the flash delay too?

  2. #2
    Join Date
    Jan 2003
    Location
    Bremen, Germany
    Posts
    4,862

    Re: Suggested triggered camera controls

    Hello

    If the camera runs triggered, the automatics of exposure, gain and white balance should be disabled, because you can get strange results, if the frame rate goes to low. Also a change of exposure and gain have an effect on the next image.

    The other to be exported properties depend on what you want to do. e.g. if you always use the full resolution, you do not need partial scan properties to show in your gui (if partial scan properties are available).

    At least: Show as less as possible properties, thus your user can not destroy too much.

    The last "TIS.py" I have posted as zip file in the other thread should make the property handling easier and should work in your Python / GStreamer 1.0 environment.
    Best regards
    Stefan
    IC Imaging Control Support

  3. #3
    Join Date
    Jul 2017
    Posts
    12

    Re: Suggested triggered camera controls

    Quote Originally Posted by Stefan Geissler View Post
    Hello

    If the camera runs triggered, the automatics of exposure, gain and white balance should be disabled, because you can get strange results, if the frame rate goes to low. Also a change of exposure and gain have an effect on the next image.

    The other to be exported properties depend on what you want to do. e.g. if you always use the full resolution, you do not need partial scan properties to show in your gui (if partial scan properties are available).

    At least: Show as less as possible properties, thus your user can not destroy too much.

    The last "TIS.py" I have posted as zip file in the other thread should make the property handling easier and should work in your Python / GStreamer 1.0 environment.
    What would be the preferred digital zoom method, setting the camera at different resolutions and displaying them larger or leaving it at full resolution and cropping?

    Also, I know this camera supports binning but using uvcdynctrl returned a bunch of errors:

    /program/tiscamera/data/uvc-extensions $ sudo uvcdynctrl -i usb3.xml -d /dev/video0
    [libwebcam] Unknown V4L2 user control ID encountered: 0x0098090E (V4L2_CID_USER_BASE + 14)
    [libwebcam] Unknown V4L2 user control ID encountered: 0x0098090F (V4L2_CID_USER_BASE + 15)
    etc.

    /program/tiscamera/data/uvc-extensions $ sudo uvcdynctrl -i tisEUVC.xml -d /dev/video0
    [libwebcam] Unknown V4L2 user control ID encountered: 0x0098090E (V4L2_CID_USER_BASE + 14)
    [libwebcam] Unknown V4L2 user control ID encountered: 0x0098090F (V4L2_CID_USER_BASE + 15)
    etc.

    Is this the proper usage?

  4. #4
    Join Date
    Jan 2003
    Location
    Bremen, Germany
    Posts
    4,862

    Re: Suggested triggered camera controls

    What would be the preferred digital zoom method, setting the camera at different resolutions and displaying them larger or leaving it at full resolution and cropping?
    Digital zoom is always keep the resolution and display bigger.
    /program/tiscamera/data/uvc-extensions $ sudo uvcdynctrl -i usb3.xml -d /dev/video0
    [libwebcam] Unknown V4L2 user control ID encountered: 0x0098090E (V4L2_CID_USER_BASE + 14)
    [libwebcam] Unknown V4L2 user control ID encountered: 0x0098090F (V4L2_CID_USER_BASE + 15)
    etc.

    /program/tiscamera/data/uvc-extensions $ sudo uvcdynctrl -i tisEUVC.xml -d /dev/video0
    [libwebcam] Unknown V4L2 user control ID encountered: 0x0098090E (V4L2_CID_USER_BASE + 14)
    [libwebcam] Unknown V4L2 user control ID encountered: 0x0098090F (V4L2_CID_USER_BASE + 15)
    This is proper usage and ca be ignored
    Best regards
    Stefan
    IC Imaging Control Support

  5. #5
    Join Date
    Jul 2017
    Posts
    12

    Re: Suggested triggered camera controls

    Quote Originally Posted by Stefan Geissler View Post
    Digital zoom is always keep the resolution and display bigger.


    This is proper usage and ca be ignored
    So all of the changes are still being applied? Also is there something to reference for the values being changed?

  6. #6
    Join Date
    Jan 2003
    Location
    Bremen, Germany
    Posts
    4,862

    Re: Suggested triggered camera controls

    So all of the changes are still being applied? Also is there something to reference for the values being changed?
    I do not understand which changes? "display" was meant as verb, not as substantive. That means, I wont change camera setting, but show the image bigger in your control. That would implement digital zoom.
    Best regards
    Stefan
    IC Imaging Control Support

  7. #7
    Join Date
    Jul 2017
    Posts
    12

    Re: Suggested triggered camera controls

    Quote Originally Posted by Stefan Geissler View Post
    I do not understand which changes? "display" was meant as verb, not as substantive. That means, I wont change camera setting, but show the image bigger in your control. That would implement digital zoom.
    I was referring to the errors that are present with the uvcdynctrl command pointing to the xml files. You said they can be ignored. I assume you meant the new values if I were to change them would still be applied but I just reread the readme and I believe changing the file and leaving it in the /usr/share/uvcdynctrl/data/199e directory will load new values automatically when the camera connects. Can you provide an example of how to enable the hardware trigger in the xml files?

    But I assume what you mean about the digital zoom is leave the camera at the highest resolution (2448x2048) and crop and resize the image larger?

Similar Threads

  1. UVC controls of DMK21AU04
    By CSeverijns in forum Hardware and Driver
    Replies: 7
    Last Post: August 22, 2016, 11:45:50
  2. Suggested Fireboard for new FireWire800 cameras.
    By Maximus in forum Hardware and Driver
    Replies: 1
    Last Post: September 13, 2013, 12:56:05
  3. ImageAvailable Event not triggered during AviStartCapture
    By Unregistered in forum IC Imaging Control ActiveX
    Replies: 1
    Last Post: July 22, 2003, 18:59:27
  4. ACCESSING Triggered iMAGE bUFFER
    By Unregistered in forum IC Imaging Control ActiveX
    Replies: 2
    Last Post: June 20, 2002, 17:43:43
  5. triggered grabs
    By Unregistered in forum IC Imaging Control ActiveX
    Replies: 1
    Last Post: January 25, 2002, 20:14:09

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •