Great video, thanks again. I recently converted to edge TX and every now and then my radio goes into emergency Mode, hopefully this new upgrade will eliminate that.
Emergency mode usually happens when the battery is pulled while powered on. If it happens outside of that, I would upgrade first and if it continues, make sure to open an issue: github.com/EdgeTX/edgetx/issues/new/choose
I tried converting from 2.5 to 2.6 and some of my models categories are missing models which didn’t get converted from opentx. Also my tx doesn’t auto open when plugged in nor does it show up on “this pc” I’m running window 10. I changed the cable to a known good one and nothing. I also updated SMT32 driver to 1.5. Under safely remove hardware it does say eject RM TX16S Mass Storage. It also is in device manager but not in my disk management. The same USB port works for other SD cards and pops up automatically. Under General information it says “currently, this hardware device is not connected to the computer. (Code 45) to fix this problem, reconnect this hardware device to the computer.“ PLEASE HELP!! I want to use edgetx but not if I lose all my models.
As far as edgetx everything seems to work fine as long as I don’t go past 2.5 but once I use edgetx buddy in dfu and update my models disappear (bin to yml) even if I go from 2.5-2.6 then 2.7
A little confuses over this whole YAML thing. so if I convert my Radoimaster TX16S from open TX to Edge TX I wont be able to coppy my models because my radio will not reconize them? I would like to do the conversion, but the idea of reprogramming all my models is just not exceptable.
Hi. i just purchased a radiomaster zorro all the edge firmware is preinstalled with black pearl and it also includes the crossfire settings, my problem is i want to put my old model bin files in my new radio models but it does not recognise bin files, is there an easy way of just converting bin files to ymal without having to flash the radio from scratch? thanks and look forward to a reply.
Companion is probably the best option. Open models from old radio and models from new radio. You can have two sets of models open side-by-side. Copy and paste from old radio to zorro then write the combined list back to radio.
@@RCVideoReviews thanks for the reply. i have backed up my old opentx sd card content onto the computer with my models folder, tried copping models bin files from there but does not work, cannot connect old x-lite to computer as the usb connector is broken, this is why i decided to purchase the zorro.
There is no yml to bin conversion. However, during the bin to yml conversion, they do not delete the original bin files. So if you didn't backup your models before you started, you may be able to find the original bin in the models directory.
I expect the mainstream use will come from developers who will be able to manipulate radio/model settings. If you're handy with text manipulation tools such as grep/awk/sed/gawk you can perform mass updates to all your yaml files. Finally, any regular text editor can open a yaml file and if you know what to look for, you can make instant changes without using tools like companion or the radio itself. So if you decide you want to add a common telemetry screen setup to all fixed wing, you can find the telemetry screen section that works, copy it, then edit all your models and paste in the setup rather quickly.
They don't really offer SD card contents for a specific version like they did on OpenTX. They just use the latest tag and it can be used on all release versions: github.com/EdgeTX/edgetx-sdcard/releases/tag/latest
Why are they using YAML on the radio itself? It takes a lot more storage space and requires parsing which is very non-trivial on these kinds of devices. I'm assuming people will be editing the YAML on a computer, so why didn't they just write a conversion utility to go from binary to text and back? On a computer this *is* trivial, and they could even support multiple text formats so people could edit the type of config file they are most comfortable with (I dislike whitespace as syntax). This strikes me as a very odd major development effort.
Q: "It takes a lot more storage space" A: Bin file is 11KB, yaml is 13KB. On a radio with 64 models on it the models directory takes 2.3MB. PS That's with BOTH the bin and yaml files. So this argument while technically true has absolutely zero practical implication. Q: "requires parsing which is very non-trivial on these kinds of devices" A: I've been using OTX for 7 years and ETX since day one. There is **ZERO** practical difference in load times between the two formats on the same radio. If you can detect a time difference you probably have an atomic clock for a brain. Again, no practical influence on the radio therefore moot. Q: "so why didn't they just write a conversion utility" A: Why bother? The way I see it, YAML provides nothing but upside. There is nothing a bin can do the YAML format cannot do, but the YAML format can do things the bin cannot. i.e. Be edited/modified easily by hand outside the radio. Q: " they could even support multiple text formats so people could edit the type of config file they are most comfortable with" A: I don't see the core dev team wasting time on this. The model format is now set and I seriously doubt will change again anytime soon. Q:"This strikes me as a very odd major development effort." A: The development effort is now in the rearview mirror and the migration to YAML sets Edge up to do more than was possible in the bin format including access to model configs from LUA and the ability for online services like buddy.edgetx.org to read model data.
@@RCVideoReviews What level of complexity did your file size comparison represent? Same question for the processing time. What happens if you make an error in your YAML config file? Are you going to have to transfer it to the radio just to see if there are issues? Or maybe you find out at the field? A conversion utility would do this for you. Or is the YAML file verified by Companion?
Molehill: Meet mountain. The filesize is governed by the radio and options. Not relevant in this context. As for the rest--try it yourself and see what happens. NONE of your concerns have legitimate practical relevance.
@@RCVideoReviews I manually edited one of my .yml files and made a small mistake, as mistakes are certainly possible when editing by hand. I loaded the .yml back onto the radio and then selected that model. No errors were reported, yet the mixer was missing entries. This would have resulted in a crash unless I had done an extremely thorough pre-flight check. To me this is an issue. To you, perhaps not.
So what? You could have just has easily made a small mistake on the radio deleting a mix line resulting in a crash unless you had done an extremely thorough pre-flight check. YOU made the mistake. YOU messed up the configuration. YOU could have just as easily made the same mistake within the radio. Own your mistakes. Look man, you're barking up the wrong tree and have yet to make a singe argument that makes any difference in any practical manner. The radio uses yaml, it's not changing back. If that doesn't work for you use OpenTX or 2.4 or 2.5. Conversation over.
it wasn't possible to bind various umx planes to edgetx 2.6 with updated and also downgraded 4-1 module firmware. it was a friggin hassle. went back to opentx and everything worked instantly. edgetx just stole me some days with this nonsense.
You could help by opening an issue and letting the developers know what you experienced. github.com/EdgeTX/edgetx/issues/new/choose FWIW I've bound Edge to DSM and DSM2 RXs:
Thank you for making this video. It worked just like you showed very seamless and all is working normal after the update.
Future upgrades should be less disruptive. Glad it worked for you.
Excellent explanation. I went from Opentx to Edgetx, very happy with the move. Very interesting and informative video. Happy flying. 🤓
Thanks for watching and commenting John. Glad EdgeTX is working well for you.
Thank You John. As always clear as a bell.
Very welcome
Great video, thanks again.
I recently converted to edge TX and every now and then my radio goes into emergency Mode, hopefully this new upgrade will eliminate that.
Emergency mode usually happens when the battery is pulled while powered on. If it happens outside of that, I would upgrade first and if it continues, make sure to open an issue: github.com/EdgeTX/edgetx/issues/new/choose
@@RCVideoReviews Awesome, thanks for the advice and I will do…
Super clear and Easy specially for the bin file
Thank you. Hope the information is useful to you.
So clear wiyh your explanations !
Glad to hear that!
Hi John, now I also know why in 2.6 my models were not fully displayed in Compagnion 2.5. Thank you for your video!
You are welcome!
John, this was a very clear and concise upgrade video, thank you.
You're very welcome. Thanks for the comment.
I tried converting from 2.5 to 2.6 and some of my models categories are missing models which didn’t get converted from opentx. Also my tx doesn’t auto open when plugged in nor does it show up on “this pc” I’m running window 10. I changed the cable to a known good one and nothing. I also updated SMT32 driver to 1.5. Under safely remove hardware it does say eject RM TX16S Mass Storage. It also is in device manager but not in my disk management. The same USB port works for other SD cards and pops up automatically. Under General information it says “currently, this hardware device is not connected to the computer. (Code 45) to fix this problem, reconnect this hardware device to the computer.“ PLEASE HELP!! I want to use edgetx but not if I lose all my models.
As far as edgetx everything seems to work fine as long as I don’t go past 2.5 but once I use edgetx buddy in dfu and update my models disappear (bin to yml) even if I go from 2.5-2.6 then 2.7
A little confuses over this whole YAML thing. so if I convert my Radoimaster TX16S from open TX to Edge TX I wont be able to coppy my models because my radio will not reconize them? I would like to do the conversion, but the idea of reprogramming all my models is just not exceptable.
The radio will convert you models for you. The only thing you lose are widgets.
Hi. i just purchased a radiomaster zorro all the edge firmware is preinstalled with black pearl and it also includes the crossfire settings, my problem is i want to put my old model bin files in my new radio models but it does not recognise bin files, is there an easy way of just converting bin files to ymal without having to flash the radio from scratch? thanks and look forward to a reply.
Companion is probably the best option. Open models from old radio and models from new radio. You can have two sets of models open side-by-side. Copy and paste from old radio to zorro then write the combined list back to radio.
@@RCVideoReviews thanks for the reply. i have backed up my old opentx sd card content onto the computer with my models folder, tried copping models bin files from there but does not work, cannot connect old x-lite to computer as the usb connector is broken, this is why i decided to purchase the zorro.
Hi, is it possible to convert yml models to bin models? I made a model on tx16 s, want it on my X10S, 😇
Thanks Matthias
There is no yml to bin conversion. However, during the bin to yml conversion, they do not delete the original bin files. So if you didn't backup your models before you started, you may be able to find the original bin in the models directory.
Thanks for the video! Can there be any benefit to edit directly in the YAML files? If so, to what use?
I expect the mainstream use will come from developers who will be able to manipulate radio/model settings. If you're handy with text manipulation tools such as grep/awk/sed/gawk you can perform mass updates to all your yaml files. Finally, any regular text editor can open a yaml file and if you know what to look for, you can make instant changes without using tools like companion or the radio itself. So if you decide you want to add a common telemetry screen setup to all fixed wing, you can find the telemetry screen section that works, copy it, then edit all your models and paste in the setup rather quickly.
@@RCVideoReviews Nice and interesting! But I think it's at the limit of my skills. Maybe I´ll try to play around with it some day.
Just updated firmware main. Now says version 2.8.0 ??? is this correct
If you see 2.8, you didn't use a release version. Even 2.7.0 RC1 still shows v2.7, so you must have used a nightly.
@@RCVideoReviews No. It was shown as a main firmware update. This was it edge tx 199206979
@@RCVideoReviews It was called. Fix: firmware compilation
@@RCVideoReviews See above reply's
Thank you very very much for the excellent video! I have a question about your radio. Where did you get the red (scroll)knobs ? Really like them!
Radiomaster sponsored me with the TX16s in this video...so Radiomaster is where I got it.
I guess this is also done if you install 2.6 as your first Edgetx install? otherwise, keep up the good work!!
Yes, I covered that scenario here: th-cam.com/video/Jlkzm5RG2L4/w-d-xo.html
You didn't show if your using SD contents for 2.5 or 2.6 or does it matter
They don't really offer SD card contents for a specific version like they did on OpenTX. They just use the latest tag and it can be used on all release versions: github.com/EdgeTX/edgetx-sdcard/releases/tag/latest
Why are they using YAML on the radio itself? It takes a lot more storage space and requires parsing which is very non-trivial on these kinds of devices. I'm assuming people will be editing the YAML on a computer, so why didn't they just write a conversion utility to go from binary to text and back? On a computer this *is* trivial, and they could even support multiple text formats so people could edit the type of config file they are most comfortable with (I dislike whitespace as syntax). This strikes me as a very odd major development effort.
Q: "It takes a lot more storage space"
A: Bin file is 11KB, yaml is 13KB. On a radio with 64 models on it the models directory takes 2.3MB. PS That's with BOTH the bin and yaml files. So this argument while technically true has absolutely zero practical implication.
Q: "requires parsing which is very non-trivial on these kinds of devices"
A: I've been using OTX for 7 years and ETX since day one. There is **ZERO** practical difference in load times between the two formats on the same radio. If you can detect a time difference you probably have an atomic clock for a brain. Again, no practical influence on the radio therefore moot.
Q: "so why didn't they just write a conversion utility"
A: Why bother? The way I see it, YAML provides nothing but upside. There is nothing a bin can do the YAML format cannot do, but the YAML format can do things the bin cannot. i.e. Be edited/modified easily by hand outside the radio.
Q: " they could even support multiple text formats so people could edit the type of config file they are most comfortable with"
A: I don't see the core dev team wasting time on this. The model format is now set and I seriously doubt will change again anytime soon.
Q:"This strikes me as a very odd major development effort."
A: The development effort is now in the rearview mirror and the migration to YAML sets Edge up to do more than was possible in the bin format including access to model configs from LUA and the ability for online services like buddy.edgetx.org to read model data.
@@RCVideoReviews What level of complexity did your file size comparison represent? Same question for the processing time. What happens if you make an error in your YAML config file? Are you going to have to transfer it to the radio just to see if there are issues? Or maybe you find out at the field? A conversion utility would do this for you. Or is the YAML file verified by Companion?
Molehill: Meet mountain.
The filesize is governed by the radio and options. Not relevant in this context. As for the rest--try it yourself and see what happens.
NONE of your concerns have legitimate practical relevance.
@@RCVideoReviews I manually edited one of my .yml files and made a small mistake, as mistakes are certainly possible when editing by hand. I loaded the .yml back onto the radio and then selected that model. No errors were reported, yet the mixer was missing entries. This would have resulted in a crash unless I had done an extremely thorough pre-flight check. To me this is an issue. To you, perhaps not.
So what? You could have just has easily made a small mistake on the radio deleting a mix line resulting in a crash unless you had done an extremely thorough pre-flight check. YOU made the mistake. YOU messed up the configuration. YOU could have just as easily made the same mistake within the radio. Own your mistakes.
Look man, you're barking up the wrong tree and have yet to make a singe argument that makes any difference in any practical manner.
The radio uses yaml, it's not changing back. If that doesn't work for you use OpenTX or 2.4 or 2.5.
Conversation over.
Уже есть 2.7 версия
Объяснение версии было предложено в самом начале видео.
it wasn't possible to bind various umx planes to edgetx 2.6 with updated and also downgraded 4-1 module firmware. it was a friggin hassle. went back to opentx and everything worked instantly. edgetx just stole me some days with this nonsense.
You could help by opening an issue and letting the developers know what you experienced. github.com/EdgeTX/edgetx/issues/new/choose
FWIW I've bound Edge to DSM and DSM2 RXs: