Startup screen - how to change.
- Thread starter DonFromTX
- Start date
So that's by design for displays that are acquired through Vans' RV-12 program. It can't be changed to something arbitrary. Is your display not going into an RV-12?
- Joined
- Mar 23, 2005
- Messages
- 13,226
As we say, we don't support arbitrary images, only the ones that are already built into the system. In some cases It can be changed in the field back to the standard screen, depending on a variety of things.
We're just interested how it ended up that way if you didn't get it from Vans as part of an RV-12 package. Where did you purchase it from? You've mentioned in the past that you are building an RV-12. Did your plans change?
We're just interested how it ended up that way if you didn't get it from Vans as part of an RV-12 package. Where did you purchase it from? You've mentioned in the past that you are building an RV-12. Did your plans change?
Fair questions, I will try to keep it short. I bought the Skyview from Vans for an aircraft that started to be an RV12, but then I modified with different engine etc, and out of fairness to Vans, I renamed it, it is registered with the FAA as Air Force 1 (don't laugh).
That startup screen is the only reference to an RV12, and of course I would much rather it said Air Force 1 or something else, even whatever the original Dynon screen says. I assumed that if Vans put it there, it must not be too much trouble to change it.
That startup screen is the only reference to an RV12, and of course I would much rather it said Air Force 1 or something else, even whatever the original Dynon screen says. I assumed that if Vans put it there, it must not be too much trouble to change it.
swatson999
Well-Known Member
- Joined
- Oct 6, 2010
- Messages
- 1,689
I don't think of this as a problem...it would be a nice feature if one could upload an image of the correct size and have that displayed at startup (although I get the advertising appeal of having a big splashy DYNON at startup all the time
).Still...I'd be surprised if it wasn't just a jpeg or bmp file being loaded by the software at boot time...
We normally don't get into this sort of detail, but I want to illustrate that we do think about things like this hard.
What you're seeing is the the BIOS image, and the way the system is currently architected, that image needs to be onboard SkyView already to be able to load it. When we made this customization for the RV-12, we contemplated making it more widely available, but at the time some of the downstream implications were tough enough to solve quickly that we decided against it. It's still something we have on our to-revisit list. Among the reasons that made this tough to roll out more widely:
-If the image isn't PERFECTLY to spec, you're going to corrupt the BIOS, and the display will need to come back. So you need a routing in SV that rejects non-perfect images, or some program that generates correct ones, etc
-We'd still want to preserve Dynon branding at boot, at least somewhat, so just allowing that image to be replaced entirely is problematic too. The image can't be piecemealed trivially, so there's another issue.
-There are a few more things I'm forgetting.
After that spash screen, there's the very old-computery-looking boot status stuff that whizzes by, and that's been a candidate to replace with an image, but doing away with that has - of course - some other implications.
In short: we hear you, and we'd love to, but haven't yet.
DonFromTX: Can you send an email to support at dynonavionics.com, and include a link to this thread? We'll reply with a procedure that will get you back to the "stock" boot image.
What you're seeing is the the BIOS image, and the way the system is currently architected, that image needs to be onboard SkyView already to be able to load it. When we made this customization for the RV-12, we contemplated making it more widely available, but at the time some of the downstream implications were tough enough to solve quickly that we decided against it. It's still something we have on our to-revisit list. Among the reasons that made this tough to roll out more widely:
-If the image isn't PERFECTLY to spec, you're going to corrupt the BIOS, and the display will need to come back. So you need a routing in SV that rejects non-perfect images, or some program that generates correct ones, etc
-We'd still want to preserve Dynon branding at boot, at least somewhat, so just allowing that image to be replaced entirely is problematic too. The image can't be piecemealed trivially, so there's another issue.
-There are a few more things I'm forgetting.
After that spash screen, there's the very old-computery-looking boot status stuff that whizzes by, and that's been a candidate to replace with an image, but doing away with that has - of course - some other implications.
In short: we hear you, and we'd love to, but haven't yet.
DonFromTX: Can you send an email to support at dynonavionics.com, and include a link to this thread? We'll reply with a procedure that will get you back to the "stock" boot image.
- Joined
- Mar 23, 2005
- Messages
- 13,226
And to put that in simpler terms:
Vans didn't make the RV-12 boot screen, we did. They buy enough screens from us so we did custom engineering work to make it happen. It's hours of work on our end to change that image. Buy a couple hundred SkyView systems from us and we'll put your logo on the boot screen too!
Vans didn't make the RV-12 boot screen, we did. They buy enough screens from us so we did custom engineering work to make it happen. It's hours of work on our end to change that image. Buy a couple hundred SkyView systems from us and we'll put your logo on the boot screen too!