# Request for QURT Compatibility for OSD Program Source: https://forum.modalai.com/topic/4033/request-for-qurt-compatibility-for-osd-program Category: General Questions (https://forum.modalai.com/category/2/general-questions) Posted: 2024-12-17 09:24:42 UTC by JP Drone Replies: 11 · Views: 2555 ## JP Drone · 2024-12-17 09:24:42 UTC I am currently working on configuring the OSD program (msp_dp_osd) on VOXL 2 Mini. I have successfully confirmed that the OSD works using Pins 4/5 on J10 (/dev/ttyHS0). However, Pins 4/5 on J10 (/dev/ttyHS0) are required for other critical purposes, and as a result, I would like to utilize J19 Pins 2/3 (SSC_QUP6) for OSD UART communication. As these pins are connected to the DSP (SLPI processor), the current OSD implementation cannot access SSC_QUP6 directly because it requires QURT compatibility. I kindly request that the OSD program be extended for QURT compatibility so it can function over SSC_QUP6 (J19 Pins 2/3). This modification would free up /dev/ttyHS0 for other critical tasks and allow more efficient use of the VOXL 2 Mini's available UART resources. Thank you for considering this request. I look forward to your response and any guidance on potential workarounds or a timeline for implementing QURT compatibility for the OSD program. ## Reply by Eric Katzfey (ModalAI staff) · 2024-12-17 23:04:53 UTC @JP-Drone Okay, I will try to get it running on the DSP side to use J19. I'm guessing that you don't use GPS so it's okay to use that UART port for OSD? I should be able to complete this by the end of the year. ## Reply by JP Drone · 2024-12-18 01:17:47 UTC (in reply to Eric Katzfey) @Eric-Katzfey Thank you for your response. Yes, that's correct. I don't use GPS for indoor flight, so it's fine to use that UART port on J19 for OSD. I appreciate your support and look forward to the update. ## Reply by Eric Katzfey (ModalAI staff) · 2024-12-18 17:43:11 UTC (in reply to JP Drone) @JP-Drone Can you try this voxl-px4 package and see if msp_dp_osd works for you on the GPS UART? You will need to add the driver start command in `/usr/bin/voxl-px4-start`. For example: `qshell msp_dp_osd start -d 6`. Download the package with ` wget http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/voxl-px4_1.14.0-2.0.87-202412180935_arm64.deb` or use the link http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/voxl-px4_1.14.0-2.0.87-202412180935_arm64.deb ## Reply by JP Drone · 2024-12-20 02:35:04 UTC (in reply to Eric Katzfey) @Eric-Katzfey Thank you for providing the updated package. I will test it within the next three days. I’ll get back to you with the results shortly. ## Reply by JP Drone · 2024-12-23 13:16:46 UTC (in reply to Eric Katzfey) @Eric-Katzfey Thank you for your support and the updated package. I have successfully verified that the OSD works using J19 pins for UART communication. The msp_dp_osd program is displaying the OSD as expected. However, I noticed an issue where a STATUS message or similar text is displayed in two locations. One appears correctly in the lower-left corner, as configured, but another is also visible near the center-left of the screen (please see the attached image). Could you confirm if this behavior is expected? ![IMG_3374.jpg](https://forum.modalai.com/assets/uploads/files/1734959312742-img_3374-resized.jpg) Current configurations: OSD_DIS_COL 1 OSD_DIS_ROW 11 OSD_STATUS_COL 1 OSD_STATUS_ROW 17 I would also be happy to handle long error messages. ## Reply by Eric Katzfey (ModalAI staff) · 2024-12-23 16:31:52 UTC (in reply to JP Drone) @JP-Drone No, that isn't expected. Can you send the values of all OSD parameters? What type of VTX unit are you connecting to? If you set OSD_STATUS_ROW to -1 do both messages disappear or only one of them? I see it is also showing the VIO status which is controlled by the parameters OSD_VIO_COL and OSD_VIO_ROW. ## Reply by Eric Katzfey (ModalAI staff) · 2024-12-23 17:10:50 UTC (in reply to JP Drone) @JP-Drone Does it work as expected when you try it from the J10 port (/dev/ttyHS0)? ## Reply by JP Drone · 2024-12-24 03:15:07 UTC (in reply to Eric Katzfey) @Eric-Katzfey Here is the OSD params ``` 1 1 OSD_BAND 5 6 1 1 OSD_BATT_COL 44 6 1 1 OSD_BATT_ROW 17 6 1 1 OSD_CBATT_COL 44 6 1 1 OSD_CBATT_ROW 16 6 1 1 OSD_CHANNEL 1 6 1 1 OSD_CH_COL -1 6 1 1 OSD_CH_HEIGHT 0 6 1 1 OSD_CH_ROW -1 6 1 1 OSD_CURR_COL -1 6 1 1 OSD_CURR_ROW -1 6 1 1 OSD_DIS_COL 1 6 1 1 OSD_DIS_ROW 11 6 1 1 OSD_DWELL_TIME 500 6 1 1 OSD_FM_COL 1 6 1 1 OSD_FM_ROW 9 6 1 1 OSD_HDG_COL 21 6 1 1 OSD_HDG_ROW 0 6 1 1 OSD_HOME_COL -1 6 1 1 OSD_HOME_ROW -1 6 1 1 OSD_LAT_COL -1 6 1 1 OSD_LAT_ROW -1 6 1 1 OSD_LOG_LEVEL 3 6 1 1 OSD_LONG_COL -1 6 1 1 OSD_LONG_ROW -1 6 1 1 OSD_REMOTE 0 6 1 1 OSD_RSSI_COL -1 6 1 1 OSD_RSSI_ROW -1 6 1 1 OSD_SCROLL_RATE 125 6 1 1 OSD_STATUS_COL 1 6 1 1 OSD_STATUS_ROW 17 6 1 1 OSD_SYMBOLS 16383 6 1 1 OSD_VIO_COL 38 6 1 1 OSD_VIO_ROW 0 6 ``` Thank you for the advice. Both messages are disappeared when I set OSD_STATUS_ROW to -1 ![osd.jpg](https://forum.modalai.com/assets/uploads/files/1735010023036-osd-resized.jpg) Also it was working as expected when I try it from the J10 port ## Reply by JP Drone · 2024-12-25 05:34:23 UTC (in reply to JP Drone) @Eric-Katzfey I think the messages of OSD_STATUS_ROW appear on both, OSD_STATUS and OSD_FM. Problem seems the message is appear to OSD_FM_ROW when OSD_STATUS_ROW is enabled. ## Reply by Eric Katzfey (ModalAI staff) · 2024-12-27 17:04:05 UTC (in reply to JP Drone) @JP-Drone Looks like there was an issue with the handling of strings in the DSP version of the code. I made an update, can you try it now? http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/voxl-px4_1.14.0-2.0.89-202412270902_arm64.deb ## Reply by JP Drone · 2024-12-29 05:37:07 UTC (in reply to Eric Katzfey) @Eric-Katzfey Thank you for your quick update. I was able to confirm that it is functioning properly. Really appreciate your support. Wishing you a wonderful New Year!