The manual say not much about this. I think the video link is transparent for the video signal and only limited by transfer rate. I do not believe it is good for 4K, maybe not for FHD.
Look at the data for the video output of the compatible cameras.
That thing is pretty glitchy and not suitable for fast-paced FPV frankly... hope you'll have better luck with that than I. ;-)
If I remember correctly, it won't work with ST16 even, only with the ST24 (or VLC etc). And its WiFi is even more glitchy than CGO3+'s. ;-)
I have one to transmit data from a custom camera/gimbal based on Sony's analog camera core with AlceOSD (both NTSC) driven by PX4, to ST24.
Modifying the ST16 to accept its video feed (for example using files from ST24) will be a pain. Some of the Flightmode is written in Java and it can be decompiled, but there are few binary blobs written in C/C++ too, and that's where things go south. ST16 = x86. ST24 = ARM.
Unfortunately I don't remember any more how the MK58 was used (I did play with its REST interface and shot photos and recorded videos something like five years ago), but some of these could work (please note the IP Helmut said: 192.168.110.1): Projektvorstellung: CGO Camera Library für Android - Yuneec Typhoon Q500+)
I have a lot of ST10+, one st12 and one ST24. For the first development stage this will be enough. In any case, ST16 should be improved. Not right now, but in a near future, I'll add a TRW to one ST16.
If I remember correctly, it won't work with ST16 even, only with the ST24 (or VLC etc). And its WiFi is even more glitchy than CGO3+'s. ;-)
I have one to transmit data from a custom camera/gimbal based on Sony's analog camera core with AlceOSD (both NTSC) driven by PX4, to ST24.
Modifying the ST16 to accept its video feed (for example using files from ST24) will be a pain. Some of the Flightmode is written in Java and it can be decompiled, but there are few binary blobs written in C/C++ too, and that's where things go south. ST16 = x86. ST24 = ARM.
People were speculating that the only thing keeping that MK58 from working with the ST16 is that the configuration for it is commented out in some .xml files in the flightmode.apk. That kind of makes sense if both mk58 and CGO3 view a similar rtsp video stream then there may not need to be a lot of changes to the app to enable/disable the mk58.
I tried to uncomment those lines and put the file back into the APK. I could get the modified apk to install, but it would crash when ran. As best I could tell it was because I signed the apk with a different cert than yuneec did and/or my apk couldn't use the shared user that runs other apps on the ST16.
I can't uninstall the Flight mode app with out rooting the ST16 and I can't figure out how to do that. I think it's already "rooted". Running 'adb shell' and issuing 'su' gives you root shell. Be careful not to bork it though. I have no idea how to put it in fastboot and where to get flashable...
To give a report:
1. MK58 works with any PAL camera. In my case tests are with EACHINE 1/3 CMOS FPV.
2. With ST10 works without any lag, probably time delay in milliseconds.
3. With ST24 I'm going in a Camera Type cycle. Should see from what this comes. The WiFi works, I browsed some sites.
4. ST12 hasn't GoPro ... Very sad.
5. On the phone works with a second or two seconds delay. Probably due to the cache in VLC. I have a fast player on the PC, but to arrange the WiFi and to connect to the camera is not a 1-2-3 deal on this configuration, so I'll don't try.
Tomorrow I'll do a factory reset on the ST24 to see what will happen.
In front of me are three options:
1. To use ST10 without the possibility to raise the landing gear. Shortly, If I read the ST successful, is possible to make a small change inside.
2. To use ST24 if this starts to work. Should try with CGO3+...
3. To try to prepare some changes in the ST16, which is a dead idea IMHO.
The main focus should be in UVC to PAL transcoder.
The ST24 should work with the MK58. That video is transmitted by it. They are just VERY glitchy (both the MK58 and ST24), and it may take multiple attempts to work. And you may need to connect manually via Android's settings to the camera wifi.. I could take a closer look at it if you need...
ST10+ is better and shows the picture very well. ST24 is a rare unit, so no reason to put any effort to make it work. For me is important to have something, to do some inflight tests with the thermal camera. Further has two ways if the compression from the USB device is the same as compression from the MK58. To decompress, reframe, and send as a PAL composite signal via the MK or to try to send it as is direct via the WiFi. Via composite is 100% possible, the other not so sure.
Does anybody have any tips on getting a ST24 to work with an MK58 video transmitter? I can bind to the MK58 and select the GoPro from the camera type menu but I get no video displayed and there is an error message that says "failed to initialize camera". I'm not sure what initialization it is trying to do and the MK58 works with a ST10.
Lastly, does anybody know what the "FPV+DA58" and "FPV+ADA58" menu options on the bind menu are, what they do, and why they are greyed out?
Does anybody have any tips on getting a ST24 to work with an MK58 video transmitter? I can bind to the MK58 and select the GoPro from the camera type menu but I get no video displayed and there is an error message that says "failed to initialize camera".
No. I am using the MK58 with a small FPV camera. This works with an ST10. Does the MK58 look at the video signal input to determine if it is hooked up to a gopro or not?
No. I am using the MK58 with a small FPV camera. This works with an ST10. Does the MK58 look at the video signal input to determine if it is hooked up to a gopro or not?
Pretty sure your camera has to be one of the cameras on the camera selection list, and it has to be selected. If you selected GoPro from the list and your camera is not a GoPro, I doubt the ST24 will accept it.
@Valklin might have a better chance of helping.
bitbucket.org
yuneecpilots.com
