Question External HUD via Ethernet, possible?

[Phil Smith]

Hey guys,


As I've been building my simpit and I'm wondering whether extracting HUD data and sending it over a local Network possible or not?
The main thing is ability using raspberry pi + LCD as an external HUD

There was an old topic dated back to 2012, showing it is possible to draw a HUD in separate window using D3D11Client, but it was just one post with a screengrab with no code examples, etc.
https://www.orbiter-forum.com/threads/external-hud.24098/

Really appreciate any help.

 

[Urwumpe]

I would say "yes". If we could drop a custom Sketchpad implementation in that place, we could render the HUD of the focus vessel by calling clbkDrawHUD ourself and translating the drawing calls of the HUD into any network protocol you need.

But such a plugin doesn't exist yet, I think.

 

[Phil Smith]

I would say "yes". If we could drop a custom Sketchpad implementation in that place, we could render the HUD of the focus vessel by calling clbkDrawHUD ourself and translating the drawing calls of the HUD into any network protocol you need.

But such a plugin doesn't exist yet, I think.

Thanks Urwumpe, I'll try to go this route and see it is achievable or not.
Alternatively, all necessary variables can be passes to HUD raspberry pi via ethernet and draw it locally utilizing Pi processing power.. Just thinking out loud

 

[Urwumpe]

Thanks Urwumpe, I'll try to go this route and see it is achievable or not.
Alternatively, all necessary variables can be passes to HUD raspberry pi via ethernet and draw it locally utilizing Pi processing power.. Just thinking out loud

Well, for my approach, it might be possible to just make a prototype to export a current HUD mode (built-on or add-on) to some vector graphics format, like SVG. Theoretically, this should also work with modifications for a MFD.

I have no knowledge about that matter, but are there any industry standards to transfer drawing commandoes over a network connection? If yes, you could learn from them.

 

[Phil Smith]

Well, for my approach, it might be possible to just make a prototype to export a current HUD mode (built-on or add-on) to some vector graphics format, like SVG. Theoretically, this should also work with modifications for a MFD.

I have no knowledge about that matter, but are there any industry standards to transfer drawing commandoes over a network connection? If yes, you could learn from them.

I was thinking of passing all "raw" data displayed on the HUD from Orbiter such as heading, speed, acceleration, etc., etc. in form of variables and draw a custom HUD imagery directly on Pi (sort of a symbol generator)

 

[Urwumpe]

Yes, but that keeps customized HUDs, like in the DG out.

 

[Phil Smith]

Yes, but that keeps customized HUDs, like in the DG out.

Yep, definitely.

Anyway, I think I have to take a break from the hardware design and get deep into coding side of things asap haha
My main interface design requirements are as follows:
1) Orbiter - simpit communication - over ethernet.
2) Communications between different simpit sub-systems - over CAN. Making it more real I plan to implement 2x parallel CAN buses for redundancy with ability to simulate "data bus failures" etc. (I wish I could utilize MIL-STD-1553, but those transceivers are unobtanium!)
3) No USB

So whole bunch of stuff to learn!

 

[Urwumpe]

1) Makes sense.
2) How about you look into SpaceCAN? (Just kidding) I presume, you mean CANopen as application layer protocol?
3) Its really better that way USB is pretty bloated.

 

[Phil Smith]

1) Makes sense.
2) How about you look into SpaceCAN? (Just kidding) I presume, you mean CANopen as application layer protocol?
3) Its really better that way USB is pretty bloated.

2) Yep, CANopen it is.

SpaceCAN
Nowadays I think SpaceWire is a way to go with new designs:

SpaceWire - Wikipedia

en.wikipedia.org

No chance I can obtain a physical layer for this 1 lol

3) My first iteration of MFDs had USB interface for bezel buttons – with 1x or 2x mfd's connected - it was a o.k., but as soon as you connect 3rd or 4th one - it started behaving very erratically..