Categories

  • Note sure where to post? Ask questions here for direct access to the ModalAI engineering team

    Support Request Format for Best Results Feature Requests 3D Models
    1724
    Topics
    8708
    Posts

    modaltbM

    Hi @TomP ,

    The last image you have shows correct orientation, you can find "pin1" and align to that:

    804e60ec-632e-496e-a5f0-f29e4f85e9e9-image.png

    For SW configuration, you want to have /usr/lib/camera/com.qti.sensormodule.imx412_fpv_0.bin for this setup off J6. Reach back out if you get stuck here.

  • Commonly asked questions we get from the community

    54
    Topics
    268
    Posts

    Sarah McMahonS

    Hi, were you able to find a solution I ran into the same problem.

  • Questions by Product

    1735
    Topics
    9244
    Posts

    G

    Hey all,

    I'm trying to use offboard control mode to give velocity commands to a starling 2 max and need position information at higher than 10 Hz (the default rate at which mavlink position messages are published)

    Is it possible to access this information at a higher rate either by increasing the mavlink publishing rate or using MPA?

    Kind regards,
    Griffin

  • 306
    Topics
    1398
    Posts

    Samuel LehmanS

    @cegeyer when streaming from the host to the voxl using the command you suggested I get

    voxl2:~$ gst-launch-1.0 udpsrc port=8554 num-buffers=1 ! fakesink dump=true Setting pipeline to PAUSED ... Pipeline is live and does not need PREROLL ... Setting pipeline to PLAYING ... New clock: GstSystemClock 00000000 (0x7fa0004e80): 80 60 6f 28 47 41 41 80 bc 30 17 35 09 30 .`o(GAA..0.5.0 Got EOS from element "pipeline0". Execution ended after 0:00:00.034007066 Setting pipeline to PAUSED ... Setting pipeline to READY ... Setting pipeline to NULL ... Freeing pipeline ...

    I assume this means I am able to get data into the voxl. When running the second command I get this

    voxl2:~$ gst-launch-1.0 udpsrc port=8554 caps = "application/x-rtp, media=(string)video, clock-rate=(int)90000, encoding-name=(string)H264, payload=(int)96" ! rtph264depay ! h264parse ! omxh264dec ! videoconvert ! autovideosink sync=false Setting pipeline to PAUSED ... gbm_create_device(156): Info: backend name is: msm_drm Pipeline is live and does not need PREROLL ... WARNING: from element /GstPipeline:pipeline0/GstAutoVideoSink:autovideosink0: Could not initialise Xv output Additional debug info: xvimagesink.c(1773): gst_xv_image_sink_open (): /GstXvImageSink:autovideosink0-actual-sink-xvimage: Could not open display (null) Setting pipeline to PLAYING ... New clock: GstSystemClock gbm_create_device(156): Info: backend name is: msm_drm gbm_create_device(156): Info: backend name is: msm_drm gbm_create_device(156): Info: backend name is: msm_drm gbm_create_device(156): Info: backend name is: msm_drm gbm_create_device(156): Info: backend name is: msm_drm gbm_create_device(156): Info: backend name is: msm_drm gbm_create_device(156): Info: backend name is: msm_drm gbm_create_device(156): Info: backend name is: msm_drm gbm_create_device(156): Info: backend name is: msm_drm gbm_create_device(156): Info: backend name is: msm_drm gbm_create_device(156): Info: backend name is: msm_drm gbm_create_device(156): Info: backend name is: msm_drm gbm_create_device(156): Info: backend name is: msm_drm gbm_create_device(156): Info: backend name is: msm_drm gbm_create_device(156): Info: backend name is: msm_drm gbm_create_device(156): Info: backend name is: msm_drm gbm_create_device(156): Info: backend name is: msm_drm gbm_create_device(156): Info: backend name is: msm_drm gbm_create_device(156): Info: backend name is: msm_drm gbm_create_device(156): Info: backend name is: msm_drm gbm_create_device(156): Info: backend name is: msm_drm gbm_create_device(156): Info: backend name is: msm_drm gbm_create_device(156): Info: backend name is: msm_drm gbm_create_device(156): Info: backend name is: msm_drm ERROR: from element /GstPipeline:pipeline0/GstOMXH264Dec-omxh264dec:omxh264dec-omxh264dec0: GStreamer encountered a general supporting library error. Additional debug info: ../../gst-omx-1.14.4/omx/gstomxvideodec.c(1819): gst_omx_video_dec_loop (): /GstPipeline:pipeline0/GstOMXH264Dec-omxh264dec:omxh264dec-omxh264dec0: OpenMAX component in error state Hardware (0x80001009) Execution ended after 0:00:07.897981343 Setting pipeline to PAUSED ... Setting pipeline to READY ... Setting pipeline to NULL ... Freeing pipeline ...

  • Please request review from ModalAI before building your drone or custom add-on PCB

    PCB Design Reviews System Architecture Design Reviews
    4
    Topics
    10
    Posts

    ModeratorM

    @david-moro Yes, absolutely. if you are OK posting it here we can take a look or if you'd like to email the schematic to contact --at-- modalai.com we could take a look that way as well