4 4
Gideon Yampolsky

HUD dashboard development

Recommended Posts

(edited)

About what was inconvenient with Vufine display: 
It is supposed to be located very close to eyeball and has lens designed accordingly. But you would not want to put it so close to the eye in wingsuit flight, as it may hit the eye badly. Attempt to position Vufine at reasonable distance creates "tunnel vision" effect - even a slight shift of eye from the optimal position makes the image to disappear. No practical use by any means.
As I posed the image earlier, assembling of AON2 on helmet front works much better. I already made about 200 jumps with this setup and believe it is a practical solution in terms of where and how display should be positioned. The AON2 can be replaced by any kind of custom implementation, but optimal position is as I mentioned. I'm currently designing my own custom solution with 5"  800 x 480 high-brightness LCD .

Edited by Gideon Yampolsky

Share this post


Link to post
Share on other sites

Yes, I'm perfectly are of that problem. I'm trying to overcome it by combining screen big enough so that even blurry text/numbers at close distance are readable, and putting it as far as possible for the best results.

So far sticking OLED to the visor on the outside seem to be good enough. That's why it has to be transparent - big screen obscures more view.

Also it's placed not directly in front of an eye, but at the bottom and to the side - again to get more distance and obscure less view.

 

 

LilyGo TTV has arrived about a week ago and actually I'm quite impressed with what they've managed to squeeze in such a small package - it even has WiFi! And plenty of power in the processor, so with time the functionality could be extended.

 

I've hooked up the GPS and it works, now I'm sorting out few technical challenges
* Extend wiring so that unit could be hidden in one of audible pockets

* Test with different batteries. The stock one is too small, it lasted for just about 1-2 hours working only as a display. For that I had to hook up GPS module to external battery with higher voltage

* There's 5-10 seconds delay in GPS readings - displayed speed lags behind actual speed. Likely some bug in the code. Same GPS module on Arduino had better reaction time

 

In few  days I'll post an update with link to GitHub for anyone interested

photo_2021-08-26_13-09-59.jpg

  • Like 1

Share this post


Link to post
Share on other sites
On 8/26/2021 at 12:23 PM, the.Legend said:

So far sticking OLED to the visor on the outside seem to be good enough. That's why it has to be transparent - big screen obscures more view.

Also it's placed not directly in front of an eye, but at the bottom and to the side - again to get more distance and obscure less view.

How's the visibility in sunlight?

Share this post


Link to post
Share on other sites

Prototype ready and assembled. I tested it today riding a bicycle in cloudy weather and it was readable. In bright sunlight this OLED is too weak on its own, but it could be improved by putting some tinted tape on the back of the frame, or in worst case a piece of duct tape.

Will be testing it this Saturday, hopefully, it will be able to catch up with readings. GPS module is rated up to 5 Hz (similar to FlySight) so if anything, the bottlenecks would be in the code.

 

I'm wrapping up the documentation & source code, will post it after field tests

 

photo_2021-09-03_01-27-31.jpg

Edited by the.Legend
  • Like 2

Share this post


Link to post
Share on other sites
44 minutes ago, the.Legend said:

but it could be improved by putting some tinted tape on the back of the frame

you can get tinted film for car windows quite easily, just cut it to size. There are even photochromic ones available.

Edited by olofscience

Share this post


Link to post
Share on other sites
15 hours ago, olofscience said:

you can get tinted film for car windows quite easily, just cut it to size. There are even photochromic ones available.

You can buy non-adhesive tinted window film as well in case you want to experiment without commitment. A tinted visor may also help.

Share this post


Link to post
Share on other sites

The unit has been tested through the weekend and I'm really happy that it worked! Unlike previous attempts, when proprietary GPS units couldn't handle freefall, this time GPS data was displayed during all phases of the flight.

Update was to 250ms and unit reaction time was pretty accurate. GPS unit rated up to 5Hz, with time it will be upgraded to 10Hz (same as in FlySight)

I didn't have time to order tinted tape, so I put black one on the back, and on a bright day digits were readable no problem at all.

Despite digits being blurry (the image attached is pretty close to what's in reality) it was easy to read them during the flight. Display is not distracting and could be looked at with quick eye movement. You might need some practice on the ground first just to get used to it, but then during the flight it didn't take an effort to check speed.

As promised, basic source code and hastily written assembly instructions:

https://github.com/RomanTheLegend/WingsuitGps

 

Contributions are welcome because I won't have enough time to develop this project at a good pace, and there are few quite complex functions to be implemented.

 

Next on the ToDo list:

* Make few more units for my friends for wider testing and feedback (mid-October because shipping is only from China)

* Make 3D models and wiring cleaner and leaner

* Explore the possibility of attaching some control switches - that would allow to write some kind of menu interface in the future

 

P.S. I got carried away a bit and added Bluetooth intercom made from old cheap headset while at it. This helmet gets more and more advanced

photo_2021-09-06_01-17-28.jpg

photo_2021-09-06_01-34-23.jpg

  • Like 2

Share this post


Link to post
Share on other sites

Yes, I've just ordered few more units for wider testing, one of them is LCD-based. It has ~0.2 inches smaller screen and is a bit thicker, but on the other hand everything is fixed to the board i.e. no flex cables to deal with. And it's colorful.

Primary reasons for OLED were transparency (which backfired on me, but still few tests to be done with tinted tape) and the thickness of the display

Parcel would arrive around mid October, meanwhile I'll be looking at improving casing, wiring and writing new code.

Edited by the.Legend

Share this post


Link to post
Share on other sites
5 hours ago, the.Legend said:

Yes, I've just ordered few more units for wider testing, one of them is LCD-based. It has ~0.2 inches smaller screen and is a bit thicker, but on the other hand everything is fixed to the board i.e. no flex cables to deal with. And it's colorful.

Primary reasons for OLED were transparency (which backfired on me, but still few tests to be done with tinted tape) and the thickness of the display

Parcel would arrive around mid October, meanwhile I'll be looking at improving casing, wiring and writing new code.

Are you having trouble finding a transparent LCD? I wouldn't expect it to be hard to find, as they're inherently clear anyway and they only tend to be opaque because they're packaged with an enclosure and backlight. But, I haven't really looked.

Share this post


Link to post
Share on other sites

LCDs and TFTs are passive by their nature - they require backlight, unlike OLED where pixels are light emitters themselves.

Without backlight LCDs can't be used in night jumps. Also they would be harder to read while looking at some dark background even in bright daylight (I did some basic tests and something that's not glowing is in general harder to read). Basically it needs a backlight and that backlight adds extra thickness, and in this case every millimeter counts.

 

I've ordered this one with IPS display, and the whole unit is 8mm thick compared to 1.5mm OLED display (4mm when in 3Dprinted frame):

http://www.lilygo.cn/prod_view.aspx?TypeId=50033&Id=1126&FId=t3:50033:3

Edited by the.Legend

Share this post


Link to post
Share on other sites

Project went silent, but not stalled :) There's been a lot of work behind the scenes and I'm releasing major code update tonight: https://github.com/RomanTheLegend/WingsuitGps

* Introduced support for TTGO device

* Fully redesigned architecture. Everything is modular: modes, devices, features. Each mode is a separate class so it's easy to develop new ones.

* You can switch between operation modes using menu

* Support for Bluetooth - you can stream GPS data to BASEline on your phone (friendly waving to @platypii )

 

It's still in Alpha state - code needs lots and lots of optimizations and stability improvements. I'm a novice C++ programmer, and many things done not the way they should. This will be fixed with time as I gain more experience. Meanwhile code review by someone experienced is really appreciated.

 

Next I'll be focusing on 3D models for the body, buttons for TTV and also rewiring stuff in more optimal way (pieces would be plugged to each other via JST) . First model would be tailored for Kiss helmets, other models to come later.

 

What else on the priority list:

* Flash GPS to higher baud rates (by default it does only 2 readings per second, I want 5 like in FlySight)

* Switch to UBX protocol which is faster than NMEA and more data-rich (FlySight also uses UBX)

* Refactoring

* Fonts optimization (currently font file for digits is too big, sometimes program fails to flash)

* Multi-page menu

 

Less priority:

* Settings

* Save data between device reboots

 

 

photo_2021-12-16_02-30-08.jpg

  • Like 3

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

4 4