its already simplified, flash it with ruby, ruby is the best system out there and supports OpenIPC cams and also supports H265 and 2k, 3k, and 4k resolutions when using a Radxa 3E or 3W for the ground unit. Ruby has a proper on screen menu system for making any changes and is packed to the rafters with features.
@@stevefox3763 It's simple if you're a nerd (no criticism, I'm a nerd too lol), there's still a way to go until they deliver an end user experience suitable for the average user.
@@stevefox3763 ruby will have msp support too, and I agree user interface is more end to end user friendly. like walksnail. latency is not as stable as wfg ng but petru continue to dev it. fpvue is diiscontinued
Things will get easier, and if more vendors start getting involved (which they are) I expect they'll want to make things more straighforward as well. Massive improvement from where it was though
Excellent overview. For me, it is a bit technical, but with the newer changes incorporated I know I could have one working fairly quickly. I do remember watching the other Open IPC post you produced about a year ago and it was very technical to say the least. However, I see this system is becoming much easier to use and I am sure the development to far more simplicity is forthcoming. I'd like to know the real latency at various distances. Very Cool Stuff isn't it!
For the real latency - as i'm not someone who goes out and tries to measure it accurately - it will probably be more a case of me doing it by feel. Can i fly something, does it feel sloppy, or unresponsive... do I keep hitting trees - that sort of thing
Great video, problem is, not many people know how to set up a drone, upload firmware etc, this I know from my Linux, root history , 90% of pilots will look and turn off straight away! I've walked people through the simplest flashing of elrs and many many people just fly! Thanks for showing us mate, reminds me of the kali days, but like someone has already said, leave it 6 months and see! Your a clever guy and well explained
It's true - even now with ELRS being a doddle to flash vs what it was like a few years ago - people get very nervous at the thought of doing something. Those guys, I guess, won't be going near it until it features in a RTF package with goggles
@@CurryKitten totally true! I used to have so many ideas for videoes, so i loved editing and the music etc, but its hard to even think of something now! It seems like iflight ,AOS with Chriss as their man and Speedybee is all i see, o and Dji. Its a shame, but its also good that people are working on open source projects like this. I brought an AOS 3.5v5 and it seems like they have used the same frame body for all and just changed the arms???
Fantastic overview, Wayne! Thanks for all the info! 😃 About flying looking at a big screen, bonafidepirate does exactly that, but with Walksnail. And it sounds like fun! Anyway, stay safe there with your family! 🖖😊
Just to clarify, those milisecond numbers on screen, are the hardware (tablet) decoding time, not the actual "glass to glass" latency. For ex. On my s23 ultra i have a hardware decod time of 19 ms. Real glass to glass latency around 38 to 50 ms at 120 fps. 720p
@@CurryKitten sure, thanks to you, some months ago i was able to flash openipc thanks to your video! If you can, i think you can help us more with the install of rtl 8812eu driver for air side, msp display for native inav/betaflight osd
Got back from being away a couple of days ago and got my paws on my shiny new Runcam, got straight to putting the Ruby flavour of OpenIPC on it and very happy with the cam, may well buy more of them :)
@@CurryKitten You wont regret It, It absolutely spanks everything else, packed to the rafters with features, has a proper menu based UI for day to day use and config, all done on screen on the ground unit itself either by a menu navigation stick like cameras come with for OSD setup or individual buttons you wire in or you can use a USB keyboard. Supports all Pi hardware as well as OpenIPC cameras and also supports the Radxa 3E/3W on the ground side and if a Radxa is use in combination with an OpenIPC camera, It brings H265 support and 2k, 3k, and 4k video streaming was also just added! The new RTL8812EU 700mw WiFi adaptor also has support on the air side if using an OpenIPC camera and on the ground if using a Radxa.
@@stevefox3763I checked the repo and there is one contributor with very little activity. I was surprised to learn how fully featured it was because development over the last year seems minimal. Or maybe I am missing something?
Hey you could totally hook up this to a VR google (meta quest 2/3 and others ...) connecting the wifi adapter directly to the USB-C port ! These headsets are made for gaming, so you should have pretty good HW decoding for h264/h265. ^^
You've inadvertantly provided a decent latency test with the blinking LED on the FC... Bit more precise than moving your hand in front of the cam 😊 Thanks for the videos on this system, as a nerd who's just getting into FPV quadcopters this system is very interesting and I look forward to playing with it when it's slightly more mature... The price of video systems for FPV is mind boggling when you understand component costs and this solution looks like it will solve a lot of those cost issues.
I could film something showing a counter or something, but I'm more interested in how it feels that the raw numbers. You'll learn pretty quickly how flyable something in a few minutes... minaly because you've crashed into a tree if the latency is too high :) I suppose the high cost of digital FPV systems in FPV is due to the costs of developing your own hardware.. maybe. This is certainly a cheaper way of getting into it - and I like the way it's developping
@@CurryKitten There's a reason a lot of the digital boards arrive with the chip identification ground off, it's off the shelf hardware, the only company developing their own chips are DJI. Granted there is work in coding for the SoC and transmission system, but the current players are keeping prices artificially high due to a lack of competition, not because of those dev costs. I guess there's also a small amount of work in packaging the system onto a suitable board with power delivery etc, but there's nothing fancy going on there either, it's all pretty standardised. I'll keep an eye out for your flight tests, as you said bench tests are sub par compared to actually flying the system :-)
No - I was it, but the problem was, as I mentioned in the video, that the camera unit just wasn't working, so any gs/drone.key I was using wouldn't work. It just seemingly randomly started working after I'd dissasembled and was reassembling it
Thanks for the video! I followed your original with your recommended components to get a hands on feel for openIPC . Got the video working after increasing the grooves in my brain a bit... Is it worth continuing with that project (printing housing, getting the telemetry working) or is it significantly outdated already? Would you recommend hanging on a bit and then going for a runcam AIO and a radxa? The configurator already looks 10x easier to use than the original method. Cheers!
It will certainly still do the job, and you can use the new configurator tool with it as well, and also upgrade the software to the latest (take a look at the sysupgrade command) So the camera/wifi hasn't changed as such - the runcam just bundles it up in a much more friendly package. As for the receiving HW, the NVR will still work fine (I'll be using it) but the radxa is the best in terms of latency. I would personally experiment with what you've got and see what happens in the next few months as it seems some other vendors will be doing some stuff as well
Take a look at my flight tests. I didn't go beyond 500m in the initial testing as I didn't have an OSD or any sort of RTH in case of a problem, but there was no degradation of signal in that sort of range. If I can stick a GPS on one of the quads, I'll test it to a further distance
OpenIPC is coming along nicely. Great overview, with some nice troubleshooting tips. Expect after another winter, with feedback and community assistance, things will be that much more refined. One shame is the ground station software requires Windows. It would be nice if ran on Raspberry Pi (these can be had for ~$45), which runs open source software and OS (Linux/Android). A R-Pi can also be configured as a WiFi hotspot, and has hardware video decoders. Which might improve latency vs. a tablet. (opens other additional possibilities) BTW: Just to verify, the WiFi to USB (in kit with antennas) is just a network connection and not outputting USB video feed?
Only the desktop version requires Windows - presumably because whoever made it only has a windows machine :) If you are running on a NVR or Radxa 3W, then you are running the Open Source OpenIPC software for receiving - and both the cameras/groundstations basically run a stripped down version of Linux. I'm told Ruby is also compatible with OpenIPC and that runs on a Pi as well, although I don't think it's Open Source. Yes the USB wifi adapter is just for a network connection, and doesn't do the decoding itself. The reason for this is that OpenIPC (and others) are reliant on certain types of hardware in the network adapters for their streaming conenction. So you couldn't just use a regular wifi hotspot
You can run on an RPI no problem, so you don't need windows. I run Linux and have an RPI running Ruby Digital HD so is a staight forward connection to the OpenIPC camera's.
No - not as it stands. You can build your own VRX which you can then connect to your goggles with an HDMI lead - or wait some more months for someone to bring out a more easy solution
I know it was definately working before. The quad I've got picked out was feeding mavlink into an OpenHD setup, so pretty sure that will work, but i can't remember which version of Betaflight it was on
That's interesting... although Mavlink telemetry is definitely broken on Betaflight. I had a quad picked out that I know does send Mavlink ok, so I'll be testing it out on that one as well. So if there's a problem I'll see if I can figure out a fix.
My fpvue or pixol pilot doesnt work. I think it has to do with app permission of reading files( the gs.key) the app doesnt request permission, so i cant grant it
Hi CurryKitten, seeing that you're using both, it would be great if you could do a non-partisan, non-controversial comparison between OpenHD and OpenIPC? I don't want you to get into any politics that may exist, just a little guidance on which of those two is best for which user & use dase!
I'll try to get there. I've had the new Ochin 2 board in my wing and had two failures (not with OpenHD, but with iNav) so 3rd times lucky and then I'll be able to compare to an extent between the 2. Right now, because OpenIPC if getting some manufactorers taking interest, this is probably going to propel forward. I know Emax is looking at a goggle module and I think this would really make things a lot more consumer friendly.
Did you notice the usb hub added 10-15ms latency? Now I'm wondering how powerful your tablet is and how low the latency would be on the fastest hardware available. 🤔
I didn't really - I saw that the latency had jumped about a bit, but I hadn't put it down to a single thing.... that'll be it! My tablet isn't particularly good. I bought it some years ago to develop my sim on, but it ran at about half the speed of my iPhone XR (in 3d graphics performance) It would be good to see what it could do on decent hardware, and I'll be interested to see if there's a hub (or something less fussy than a hub) that can stop the latency jumping so much
I was able to get the runcam wifilink-g to work with my Samsung 9+ with no problem codec h-265 and channel 173. .Where can I get that hdmi adapter i would like to try my skyzone goggles for fpv. Great content big fan.
If you search for "usb-c hub hdmi" on amazon. You'll find a lot of similar products. Its probably worth dropping by the OpenIPC telegram group to see if there's any particular ones they've found are better/recommend.
Do you know if RunCam has gotten the VTX certified by the FCC to legally be sold in the USA? Some might say this is picky, but in reality, it is NOT. It is valid. There are regulations that should be followed. Besides connecting the receiver to a Phone (not really viable for FPV), how would one connect it to an HD viewing device such as monitor or goggles...HDMI ??? Yes, goggles would be nice. Wonder at what price...$500 USD? More?
No idea - you should ask RunCam that one. As to how to connect to HD, as I demo'd in the video - you can either use a USB-C hub with an HDMI out in order to use the Wifi adapter into your phone and then out via HDMI to your goggles, or use a standalone groundstation like a Radxa 3w. Which is cheap, but will take some setup.
Hello, I also purchased this product and encountered an issue. The FC data is almost impossible to display on the OSD. Why do I say "almost"? Because after many attempts, only twice did the OSD show real-time FC data after powering on. I’m using an Android phone, FPVue, and Ardupilot. I’ve tried both MAVLINK1 and MAVLINK2 protocol, but neither could display the FC data.
I say give it another 3 to 6 months for the community to simplify this. Looks promising. Thanks for the video!
its already simplified, flash it with ruby, ruby is the best system out there and supports OpenIPC cams and also supports H265 and 2k, 3k, and 4k resolutions when using a Radxa 3E or 3W for the ground unit.
Ruby has a proper on screen menu system for making any changes and is packed to the rafters with features.
@@stevefox3763 It's simple if you're a nerd (no criticism, I'm a nerd too lol), there's still a way to go until they deliver an end user experience suitable for the average user.
@@stevefox3763 ruby will have msp support too, and I agree user interface is more end to end user friendly. like walksnail. latency is not as stable as wfg ng but petru continue to dev it. fpvue is diiscontinued
fpvvue is dead, but the code has forked into OpenIPC and is being developed as Pixel Pilot github.com/OpenIPC/PixelPilot
Things will get easier, and if more vendors start getting involved (which they are) I expect they'll want to make things more straighforward as well. Massive improvement from where it was though
Thanks a lot for explicitly trying out several setups and showing how to get it to run! Super interesting
No worries - Useful for me as well to work out how I'd like to set myself up when I go and fly it
Excellent overview. For me, it is a bit technical, but with the newer changes incorporated I know I could have one working fairly quickly. I do remember watching the other Open IPC post you produced about a year ago and it was very technical to say the least. However, I see this system is becoming much easier to use and I am sure the development to far more simplicity is forthcoming. I'd like to know the real latency at various distances. Very Cool Stuff isn't it!
For the real latency - as i'm not someone who goes out and tries to measure it accurately - it will probably be more a case of me doing it by feel. Can i fly something, does it feel sloppy, or unresponsive... do I keep hitting trees - that sort of thing
Great video, problem is, not many people know how to set up a drone, upload firmware etc, this I know from my Linux, root history , 90% of pilots will look and turn off straight away!
I've walked people through the simplest flashing of elrs and many many people just fly!
Thanks for showing us mate, reminds me of the kali days, but like someone has already said, leave it 6 months and see!
Your a clever guy and well explained
It's true - even now with ELRS being a doddle to flash vs what it was like a few years ago - people get very nervous at the thought of doing something. Those guys, I guess, won't be going near it until it features in a RTF package with goggles
@@CurryKitten totally true! I used to have so many ideas for videoes, so i loved editing and the music etc, but its hard to even think of something now!
It seems like iflight ,AOS with Chriss as their man and Speedybee is all i see, o and Dji.
Its a shame, but its also good that people are working on open source projects like this.
I brought an AOS 3.5v5 and it seems like they have used the same frame body for all and just changed the arms???
Fantastic overview, Wayne! Thanks for all the info! 😃
About flying looking at a big screen, bonafidepirate does exactly that, but with Walksnail. And it sounds like fun!
Anyway, stay safe there with your family! 🖖😊
Cheers MC. Yes I've seen him in his shed with his big TV. But then again he kind of has his own little airport. Lucky thing :D
Just to clarify, those milisecond numbers on screen, are the hardware (tablet) decoding time, not the actual "glass to glass" latency.
For ex. On my s23 ultra i have a hardware decod time of 19 ms. Real glass to glass latency around 38 to 50 ms at 120 fps. 720p
Ah - good to know, thanks for this
@@CurryKitten sure, thanks to you, some months ago i was able to flash openipc thanks to your video!
If you can, i think you can help us more with the install of rtl 8812eu driver for air side, msp display for native inav/betaflight osd
Got back from being away a couple of days ago and got my paws on my shiny new Runcam, got straight to putting the Ruby flavour of OpenIPC on it and very happy with the cam, may well buy more of them :)
I seem to be getting endless messagea about Ruby - so I'll have to give it a try at some point
@@CurryKitten You wont regret It, It absolutely spanks everything else, packed to the rafters with features, has a proper menu based UI for day to day use and config, all done on screen on the ground unit itself either by a menu navigation stick like cameras come with for OSD setup or individual buttons you wire in or you can use a USB keyboard.
Supports all Pi hardware as well as OpenIPC cameras and also supports the Radxa 3E/3W on the ground side and if a Radxa is use in combination with an OpenIPC camera, It brings H265 support and 2k, 3k, and 4k video streaming was also just added!
The new RTL8812EU 700mw WiFi adaptor also has support on the air side if using an OpenIPC camera and on the ground if using a Radxa.
@@stevefox3763I checked the repo and there is one contributor with very little activity. I was surprised to learn how fully featured it was because development over the last year seems minimal. Or maybe I am missing something?
Hey you could totally hook up this to a VR google (meta quest 2/3 and others ...) connecting the wifi adapter directly to the USB-C port ! These headsets are made for gaming, so you should have pretty good HW decoding for h264/h265. ^^
You've inadvertantly provided a decent latency test with the blinking LED on the FC... Bit more precise than moving your hand in front of the cam 😊
Thanks for the videos on this system, as a nerd who's just getting into FPV quadcopters this system is very interesting and I look forward to playing with it when it's slightly more mature... The price of video systems for FPV is mind boggling when you understand component costs and this solution looks like it will solve a lot of those cost issues.
I could film something showing a counter or something, but I'm more interested in how it feels that the raw numbers. You'll learn pretty quickly how flyable something in a few minutes... minaly because you've crashed into a tree if the latency is too high :) I suppose the high cost of digital FPV systems in FPV is due to the costs of developing your own hardware.. maybe. This is certainly a cheaper way of getting into it - and I like the way it's developping
@@CurryKitten There's a reason a lot of the digital boards arrive with the chip identification ground off, it's off the shelf hardware, the only company developing their own chips are DJI. Granted there is work in coding for the SoC and transmission system, but the current players are keeping prices artificially high due to a lack of competition, not because of those dev costs. I guess there's also a small amount of work in packaging the system onto a suitable board with power delivery etc, but there's nothing fancy going on there either, it's all pretty standardised.
I'll keep an eye out for your flight tests, as you said bench tests are sub par compared to actually flying the system :-)
@@krazed0451 HDZ & DJI
I still use the diy security camera with rtl8812eu.
i think you missed it in the runcam page where you download the manual, there is also a gs.key
No - I was it, but the problem was, as I mentioned in the video, that the camera unit just wasn't working, so any gs/drone.key I was using wouldn't work. It just seemingly randomly started working after I'd dissasembled and was reassembling it
@CurryKitten weird no idea why it could have done that
Thanks for the video! I followed your original with your recommended components to get a hands on feel for openIPC . Got the video working after increasing the grooves in my brain a bit... Is it worth continuing with that project (printing housing, getting the telemetry working) or is it significantly outdated already? Would you recommend hanging on a bit and then going for a runcam AIO and a radxa? The configurator already looks 10x easier to use than the original method. Cheers!
It will certainly still do the job, and you can use the new configurator tool with it as well, and also upgrade the software to the latest (take a look at the sysupgrade command) So the camera/wifi hasn't changed as such - the runcam just bundles it up in a much more friendly package. As for the receiving HW, the NVR will still work fine (I'll be using it) but the radxa is the best in terms of latency. I would personally experiment with what you've got and see what happens in the next few months as it seems some other vendors will be doing some stuff as well
This RunCam unit is a big step forward. What sort of range does that setup get?
Take a look at my flight tests. I didn't go beyond 500m in the initial testing as I didn't have an OSD or any sort of RTH in case of a problem, but there was no degradation of signal in that sort of range. If I can stick a GPS on one of the quads, I'll test it to a further distance
OpenIPC is coming along nicely. Great overview, with some nice troubleshooting tips. Expect after another winter, with feedback and community assistance, things will be that much more refined. One shame is the ground station software requires Windows. It would be nice if ran on Raspberry Pi (these can be had for ~$45), which runs open source software and OS (Linux/Android). A R-Pi can also be configured as a WiFi hotspot, and has hardware video decoders. Which might improve latency vs. a tablet. (opens other additional possibilities)
BTW: Just to verify, the WiFi to USB (in kit with antennas) is just a network connection and not outputting USB video feed?
Only the desktop version requires Windows - presumably because whoever made it only has a windows machine :) If you are running on a NVR or Radxa 3W, then you are running the Open Source OpenIPC software for receiving - and both the cameras/groundstations basically run a stripped down version of Linux. I'm told Ruby is also compatible with OpenIPC and that runs on a Pi as well, although I don't think it's Open Source. Yes the USB wifi adapter is just for a network connection, and doesn't do the decoding itself. The reason for this is that OpenIPC (and others) are reliant on certain types of hardware in the network adapters for their streaming conenction. So you couldn't just use a regular wifi hotspot
@@CurryKitten Ruby is open source too and fully compatible with OpenIPC hardware, Raspberry and Radxa hardware
You can run on an RPI no problem, so you don't need windows.
I run Linux and have an RPI running Ruby Digital HD so is a staight forward connection to the OpenIPC camera's.
Excellent. Have you tried the maximum distance yet? How far is it? And I have a TP-Link T4U Plus, can I replace its Wi-Fi card with that? Thanks!
is there anyway to run the footage from the runcam straight to USB or to ETH and get a picture from either without the wifi in the middle?
will this work with walksnail or hdzero goggels as i dont have a tablet will it not directly connect to goggels
No - not as it stands. You can build your own VRX which you can then connect to your goggles with an HDMI lead - or wait some more months for someone to bring out a more easy solution
How do I change settings, I can't seem to connect to the configurator
Which setting? If the configurators not working for you, then you can use ssh - but odds on you might have the wrong ip address or something similar
@CurryKitten settings like power levels, resolution, ect , I did the scan and tried every ip address, I keep getting messages like Majestic not found
@CurryKitten can you do a video on how to get the radxa Zero up and running, seen couple of videos but no narration just music
Cool project to play with
I think so :)
Dose the BF 4.4.x work with the Mavlink? I'm encontering same issue by using the BF 4.5.0
I know it was definately working before. The quad I've got picked out was feeding mavlink into an OpenHD setup, so pretty sure that will work, but i can't remember which version of Betaflight it was on
@@CurryKitten Got it, thanks!
Mavlink telemetry did not work on ardupilot for me. So it might be a problem with the IPC board.
That's interesting... although Mavlink telemetry is definitely broken on Betaflight. I had a quad picked out that I know does send Mavlink ok, so I'll be testing it out on that one as well. So if there's a problem I'll see if I can figure out a fix.
My fpvue or pixol pilot doesnt work. I think it has to do with app permission of reading files( the gs.key) the app doesnt request permission, so i cant grant it
Whats the difference between wifilink and wifilink-G?
Thw WiFiLink is the camera/VTX, the WiFiLink-G also includes the receiving stuff to plug it into an Android phone/tablet
Hi CurryKitten,
seeing that you're using both, it would be great if you could do a non-partisan, non-controversial comparison between OpenHD and OpenIPC?
I don't want you to get into any politics that may exist, just a little guidance on which of those two is best for which user & use dase!
I'll try to get there. I've had the new Ochin 2 board in my wing and had two failures (not with OpenHD, but with iNav) so 3rd times lucky and then I'll be able to compare to an extent between the 2. Right now, because OpenIPC if getting some manufactorers taking interest, this is probably going to propel forward. I know Emax is looking at a goggle module and I think this would really make things a lot more consumer friendly.
Did you notice the usb hub added 10-15ms latency? Now I'm wondering how powerful your tablet is and how low the latency would be on the fastest hardware available. 🤔
I didn't really - I saw that the latency had jumped about a bit, but I hadn't put it down to a single thing.... that'll be it! My tablet isn't particularly good. I bought it some years ago to develop my sim on, but it ran at about half the speed of my iPhone XR (in 3d graphics performance) It would be good to see what it could do on decent hardware, and I'll be interested to see if there's a hub (or something less fussy than a hub) that can stop the latency jumping so much
I'll wait for OpenIPC googles before trying this system. I'm currently using analog with low resolution screen goggles with no HDMI input...
Yes - you certainly won't benefit from the increase in resolution without the equipment to watch it with
Max video translation Distance ? 🤔
Don't know yet - we'll see when I fly with it
@@CurryKitten I'm looking for this answer as well.
i was gonna emssage you to ask you to check it out. have you ordered the Mario AIO already?
I do not. It sells out pretty quickly!
@@CurryKitten They sold out so fast, but eagerly awaiting reviews and footage from them.
I was able to get the runcam wifilink-g to work with my Samsung 9+ with no problem codec h-265 and channel 173. .Where can I get that hdmi adapter i would like to try my skyzone goggles for fpv. Great content big fan.
If you search for "usb-c hub hdmi" on amazon. You'll find a lot of similar products. Its probably worth dropping by the OpenIPC telegram group to see if there's any particular ones they've found are better/recommend.
WOW! I like new tech and think this is Kool but this might be to "Coder Bro" for me!
It's got a lot more simple than when I last looked at it! Hopefully it just gets more and more accessible and we don't even have to mention Linux
OpenIPC allows multiple RX over one TX? Does anybody knows?
Do you know if RunCam has gotten the VTX certified by the FCC to legally be sold in the USA? Some might say this is picky, but in reality, it is NOT. It is valid. There are regulations that should be followed.
Besides connecting the receiver to a Phone (not really viable for FPV), how would one connect it to an HD viewing device such as monitor or goggles...HDMI ??? Yes, goggles would be nice. Wonder at what price...$500 USD? More?
No idea - you should ask RunCam that one. As to how to connect to HD, as I demo'd in the video - you can either use a USB-C hub with an HDMI out in order to use the Wifi adapter into your phone and then out via HDMI to your goggles, or use a standalone groundstation like a Radxa 3w. Which is cheap, but will take some setup.
Hello, does this add a function: you can access USB UVC (thermal imaging), achieve visible and infrared light, so it is perfect.
Hello, I also purchased this product and encountered an issue. The FC data is almost impossible to display on the OSD. Why do I say "almost"? Because after many attempts, only twice did the OSD show real-time FC data after powering on. I’m using an Android phone, FPVue, and Ardupilot. I’ve tried both MAVLINK1 and MAVLINK2 protocol, but neither could display the FC data.
It seems like a semi finished stuff ,without a hull.And too much steps for users before using.Hoping that it could be simplified soon.