OpenIPC Build part 3: Connecting up a Flight controller and configuring telemetry for the OSD
Vložit
- čas přidán 7. 03. 2024
- Welcome to part 3 of my OpenIPC project. In this video, I'll be covering the essential (but easy - well, much easier than the flashing parts) task of connecting and configuring your flight controller and setting up telemetry so you can see the state of your model on the OSD.
Thanks to the sponsor of this video, PCBWay. Don't forget to check out www.pcbway.com/ for PCB prototyping, 3D printing, and more!
Some of what's going on refers to the step-by-step setup documentation I originally wrote (and people have been updating and enhancing - yay!) you can see it here github.com/OpenIPC/wiki/blob/...
The store for OpenIPC is here store.openipc.org/ Quick disclaimer: I'm not involved/affiliated in any of this, and haven't seen any of these boards in person, but from my personal view - it looks a lot better than having to flash things yourself!!
If you liked this video and want to show your support please feel free to join my Patreon supporters here / currykitten or if you decide to shop at Banggood, here's a general affiliate link which helps me out if you use it www.banggood.com/?p=E81211714...
If you want to look at other ways of supporting my channel, then check out all the ways you could help out here www.currykitten.co.uk/support-me/
I love projects like this. Clearly I’m not the normal person.
If you enjoy a tinker and you have the time, projects like this are perfect. So either you are normal, or we both have issues :)
Commenting mostly for your engagement stats - this is all well beyond my limited comprehension skills. I'll wait for a PnP option.
Thanks - it's most appreciated :)
Have you looked at Ruby lately?
Petru has added support for Open IPC hardware and once flashed, it works with existing Ruby Ground units so any OpenHD Ground unit you may already have will work with it if you flash Ruby to an SD card and add buttons to the GPIO for menu navigation, Ruby menu buttons do not use any GPIO pins that OpenHD uses so adding them does not affect switching SD cards between OpenHD and Ruby to go back and forth between ecosystems but I dont think you would look back after trying Ruby anyway!
He is adding more and more features into the Ruby Open IPC camera firmware, the most recent being shutter speed control via ruby and added a second UART to the Sigmastar SSC338Q
Once flashed with the firmware, all you need to do is power it up and it will start on a default frequency and doing a search with the ruby ground station will find and connect to it.
I've not done it myself yet but have the Sigmastar SSC338Q on order which will get flashed with Ruby when it arrives in few days.
I've no really looked at Ruby generally - mostly because it's a one-man project and is closed source. I don't have an issue with people doing things on their own, or keeping the source closed, but it represents a far higher risk if he decides not to/can't continue with the project for any reason. One guy in a lead position in OpenHD almost tanked the entire projeet when he left! With that said I'll try and give it a look when I get to the flying part. At the moment OpenIPC keeps changing so often that it makes me want to pause and let it settle for a while
@@CurryKittenRuby has been open source for a while now.
❤ thanks for your effort getting us to start this too. How do you connect Android phone for FPV? Do we get Streaming ?
Awesome, Wayne! Looking forward to the tests! 😃
And yeah, I'd definitely try it with a rc car first!
Stay safe there with your family! 🖖😊
Let's see how easily I can stick this on the car (probably easier than on a plane) :D
@CurryKitten About that, when you can take a look at the Suchiyu models. Their only "defect" is that they don't come with oil shocks, but they're pretty cheap.
I bought the Scy 16302 (that looks like a 1930s Ford) and I'm going to get the Scy 16103 Pro, the "Gantry Pro"... To rip around in the beach. 😃
Your guide in the wiki seems yo be broken right now. Just shows a blank page when i try to view it. They one on your github fork still works, but doesn't have the updates about the serial.
I noted that they did change the title, so my original URL didn't work - but I just checked the one I listed in the description github.com/OpenIPC/wiki/blob/master/en/A-step-by-step-guide-for-an-FPV-setup.md and that was fine
Thanks for part 3. I managed to get this all working on the bench. However, I gave up when my second ground segment (NVR) quite working. Was I just unlucky to get two bad units, or hooked up something incorrectly, or are the NVRs plain unreliable?
I guess it's a question of how confident you are that you didn't hook something up incorrectly? I can't really speak to their reliability - the one I have has been fine, but I've only used it for 2 or 3 hours in total, so a little early to say
Good that yours is reliable. Maybe I will give it a try again. Thanks@@CurryKitten
I like to see the latency on the bench
open ipc latency is kinda dependant on your screens refresh rate , from what i remember the "VRx module" that you build gives you at best a latency of 70 to 90 ms but if you have HDzero's goggles or i think skyzone 4's (both have 100Hz refresh rate) you can get a latency of about 50 ms , so your cheapest ground station setup for the lowest latency possible rn is lugging a laptop as your ground station or hooking up an orange pi with wifi to a 100hz screen all running of a battery bank or something , open ipc has made alot of progress on the air side of things but the ground side is slightly lacking , i think they have said they can get the latency down to 30 ms - so in line with DJI but that was with optimal hardware and conditions , so i guess most of us will still have to wait until they start building some fpv goggles that we can buy . But do go and ask the guys on telegram for a direct reply , im just a dude that follows the news on it closly so my info can be out of date
If you watch this video that Mario posted, another guy did a bench latency test czcams.com/video/i_Wz9oAK5z4/video.htmlsi=P0mwFMd2otum344_&t=212 I'm less interested in this and more interested in the latency when you fly it. Not that I have the know-how to measure this accurately
How about connect QGroundControl/Ardupilot Mission Planner to the groundstation to show telemetry and video?
Yes - nice idea. I'm told this runs slower than just using the stuff from the NVR, but certainly worth checking out what the pros/cons are
Hi, succeeded with OSD. Question. Is there a way to configure the OSD e.g. to display more information from the FC or turn down the artificial horizon. Thank you.
There probably is - but if its documented, then it's very well hidden. Bet bet is to post in the FPV telegram group. I'm sure I saw a file somewhere that defines what the OSD would show, but I maybe wrong
Hello ! Why does my NVR use the latest firmware, the OSD in the video will freeze? The old version of the firmware will not.
Don't know - I may not be on the latest version now. Have you tried pinging the telegram groups about this one?
Wayne, do you know what pins/pads each /dev/ttySx belongs to? There's ttyS0, ttyS1, ttyS2, ttyS3 in my /dev directory. I stupidly sent +9v into my ttyS2 and my telemetry does not work. Never even got to see it work. I have connected up to the tiny pins now and tried setting it to all of the above, with no luck. I don't wanna fry a lipo! Need that batt voltage
I found the same thing when I was trying to work out which tty the second UART belonged to, and it was just through trial and error I found it was S2. I couldn't see any connectors that could be another tty, unless they share pins with something else, and that's very undocumented. Those tiny pins should work as a tty though. Is getting still running on the console in inittab, if there's already a process that's using ttyS0, then the telemetry won't be able to use it