Topics created by AndriiHlyvko

@Eric-Katzfey @Alex-Kushleyev not exactly what I was looking for. I already implemented it using ffmpeg library. Basically I wanted to use voxl-send-command utility to send start/stop recording commands while also have the ability to save snapshots. I didn't like the idea of using gstreamer pipes for implementing this so I chose ffmpeg. I think my solution is good enough for now. I am able to start/stop recordings do snapshots and embed xmp metadata into the snapshots. Although I might come back to using OMX library if I decide I need the hardware encoding.

@Eric-Katzfey I figured out the problem. I changed the mavlink pipe to mavlink_onboard keeping the channel number as 1. Setting the channel number as 2 seems to fix the problem. I haven't looked into the implementation of modal-pipe architecture but I thought that the channel number is just used by the client of the pipe (kind of like an open file descriptor number?). Basically it looks like having the channel number as 1 breaks the mavlink pipe somehow.

@AndriiHlyvko Thanks! We have merged in those changes.

@tom cool. I created an MR with wrong source branch by mistake so just delete that one. But this one is the right one: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-camera-server/-/merge_requests/42

@AndriiHlyvko On VOXL 2, the snapshot pipe from voxl-camera-server will use the latest gps data and update the exif data of the jpg image with the latitude and longitude

voxl-camera-server receives GPS data here

voxl-mavlink-server publishes GPS data here

You can use the voxl-inspect-gps tool to verify the GPS data is being published correctly

@AndriiHlyvko The issue is with dependencies. The emulator is built using the actual filesystem used on the VOXL platform so you get all of the correct dependencies. With voxl-cross it is sometimes very difficult to setup the dependencies properly.

@AndriiHlyvko , thank you for following up with your solution!

Hi @AndriiHlyvko
The chip is not infinity flexible. Many things are fixed/set in hardware meaning either the silicon device or the PCB. There is no internal cross-bar in the QRB5165 that allows for 100% remapping like on FPGAs.

Please see these pages:
https://docs.modalai.com/expansion-design-guide/#qups-the-key-io-groups-for-expansion
https://docs.modalai.com/voxl2-qups/

Hope that helps explain things a little.

@SMRazaRizvi @madswamp @Jgaucin @AndriiHlyvko @camharrisvayu

Hey all, apologies on this. We were finally able to recreate the issue but unable to determine what the root cause was. Regardless, we have a new SDK (1.1.0) released which isn't showing the stack smashing issue.

https://developer.modalai.com/asset/2

Please let me know if this is still an issue and sorry for the wait on this.

Thanks,
Thomas Patton

Thanks @Aidan-Dempster, that worked.

Ok. I figured out the problem. The problem was my calibration chessboard. I taped the pattern to a cardboard box which resulted in some warping of the pattern. After I glued the pattern onto a flat hard surface the calibration worked.