-
-
Notifications
You must be signed in to change notification settings - Fork 277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi3516ev300 cam and Hi3536dv100 nvr, can't get osd working #1589
Comments
I have tried many things : |
"Unable to decrypt packet" message come from wfb_rx and it seems it is not the problem, the message stop when a SESSION_PACKET arrive initializing the session_key. |
Ah.... I saw this. @Warfull Did you get osd on the ground (3536) working? As I saw it's working on airunit OpenIPC/msposd#18 |
No way to get the osd working. |
Now it's working. All others parameters by default. On FC: |
NVR is Hi3536DV100 , master+8d995dt, 2024-10-20
Cam is Hi3516ev300, master+874aa01, 2024-10-21
Camera module is IVG-85HG50PYA-S.
Osd is drawn but no data update.
I can see trafic on the uart port with oscillioscope, both tx and rx signal carry data.
I have tryed all possible configs in telemetry.conf,, vdec.conf
router=0,1,2
On the cam side Mavlink stream is present :
root@openipc-hi3516ev300:/usr/bin# mavfwd -m /dev/ttyAMA0 -o 0.0.0.0:14550 -v
Verbose mode!
Listening on /dev/ttyAMA0...
Detected MAVLink ver: 1.0 (254)
System_id = 1
Mavlink msg 30 no: 132
1 Pckts / 36 bytes sent
Mavlink msg 30 no: 134
1 Pckts / 68 bytes sent
Mavlink msg 30 no: 136
1 Pckts / 68 bytes sent
Mavlink msg 30 no: 138
1 Pckts / 68 bytes sent
Mavlink msg 30 no: 140
1 Pckts / 68 bytes sent
...
On nvr side :
root@openipc-hi3536dv100:/# vdec -c h265 -d stream --osd --mavlink-port 14750
[HI_VERSION=Hi3536D_MPP_V1.0.1.0 B040 Release]
The text was updated successfully, but these errors were encountered: