Ranger's HUD Progress

What phone do you use?


  • Total voters
    29
Status
Not open for further replies.

RandomRanger

DMO, Armory, and Forum Support
Division Staff
Community Staff
Member DIN
S063
Hey all, some of you may know I'm trying to build a sort of HUD into my helmet. I'm creating this post to track it's progress I realized I should make after meeting up with NobleofDeath16 .

Desired features
Some things I want to use it for: suit cooling/fan control, comms between other 405th units (that's you guys), night vision camera, music, Alexa (name remaped), minimap (including indoors, yes google has 'indoors maps' for some locations)
I also have an online degree in AI Deep Learning... so I'm hoping to apply that in some way, but idk how yet.
I want to turn the AI chip portion of the Mk VI helmet into a usb port.

Community requested features
Nothing seems to be here yet.

HUD Input
I have a keyboard in my forearm for input
It should be possible to add buttons to the armor itself, e.g. on the side of the helmet, for specific features like comms.

HUD Output
Stereo speakers
Wearable display beneath the visor Amazon.com: Vufine Wearable Display: Gateway (I swear it was 'only' $100 when I bought it)

Current Functionality
Current functionality involves a raspberry pi built into the helmet that can play audio through the speakers and display to the screen (located by the chin, it's the black square), though everything is interacted with via the a linux gui so I've yet to make my HUD app for it. Because my USB wifi card is so old though, it doesn't have internet access (hence the pic with Ethernet plugged in)

Here's some photo's of what I've got so far
 

Attachments

  • IMG_20190127_132056.jpg
    IMG_20190127_132056.jpg
    3.7 MB · Views: 487
  • IMG_20190127_154218.jpg
    IMG_20190127_154218.jpg
    3.8 MB · Views: 464
  • IMG_20190127_180050.jpg
    IMG_20190127_180050.jpg
    3.4 MB · Views: 405
  • IMG_20190127_211437.jpg
    IMG_20190127_211437.jpg
    3.3 MB · Views: 397
  • IMG_20190127_214235.jpg
    IMG_20190127_214235.jpg
    3.4 MB · Views: 397
  • IMG_20190609_200055.jpg
    IMG_20190609_200055.jpg
    1 MB · Views: 415
  • MVIMG_20190127_164020.jpg
    MVIMG_20190127_164020.jpg
    3.7 MB · Views: 393
  • MVIMG_20190127_164027.jpg
    MVIMG_20190127_164027.jpg
    3.3 MB · Views: 386
  • MVIMG_20190609_200046.jpg
    MVIMG_20190609_200046.jpg
    3.5 MB · Views: 399
Last edited:
ABOUT TIME!

O.0 you really have your work cut out for you. If you pull this off you are going to be an absolute legend. Just wow. I cant wait!
Honestly I expect the hardest part to be the hardware, e.g. the display. But I've already got that somewhat handled (it may not be an 'in-visor' display, but it is an 'in-helmet' display) so I'm fairly optimistic about the project.
As a software engineer, writing the app itself should be relatively easy for me to be honest.
 
Last edited:
Dude this is so cool!!! If you get it working the way you want I would totally love to do the same to mine!!! :love:
Oh you can bet there'll be a tutorial at some point ;-)

The spotify client I'm running is headless, meaning I currently have to use another device to play/pause music. I'm looking at the spotify web api right now to see if I can write a super tiny client.

That 'tearing apart a laptop' turned out to be a waste of time. I wanted to gut the fan out of it for helmet circulation, but the pins are way too small to be useful.
 
Tonight I plan on reevaluating the technologies I'm using. It would be a lot easier to build in functionality if I used a smartphone to do so. Build a smartphone into the wrist as a more Carter-esque tac-pad than my current keyboard-mouse tac pad. The idea here would be to use the phone as more of an input device (think about how Carter uses it in Reach), and then use the raspi and in-helmet devices data output (e.g. music, comms, display). So I'll be balancing the engineering tradeoffs after work.
Plus having a color screen that swipes and stuff is cooler than a regular'ol qwerty board.

quick poll for y'all (top of page):
Do you use android or iPhone?
 
Last edited:
I just realized I probably shouldn’t try to do something like this to my helmet. With my luck it catch fire
Hahaha, it would be incredibly difficult to start a fire with the stuff I'm using.
Have you figured what kind of hud design you want it to have?
Right now I'm thinking about a split between a wrist-built tacpad (smartphone) with a secondary display in the helmet so you don't have to constantly look at your wrist. The trick is to keep the in-helmet display relevant and usefull... CAUSE OTHERWISE IT'S NOT A HUD
 
I think I'm gonna try avoiding smartphones for now. I don't want to alienate iPhone users (since I can only do Android dev atm) and, honestly, something about it feels less cool. If I run into too many issues though I know I can spin stuff up there pretty quickly.
 
Hurry up! Also there is an app on the app store called Zedge, it has ringtones, sounds, alerts, wallpapers, for about anything you can think up! "Cough" even Halo, like Dots' AI interface
I'm familiar with Zedge, but it hadn't occured to me to build in sound effects. I'll look into it :).
Last night I was trying to figure out the Spotify API, and I got some stuff figured out there. Security requirements always make things more difficult.
Once I get music playing, I plan on working towards an inter-suit comms system.
 
Last edited:
Wooooooo! I was able to use my app to start playback! It's useless at the moment, because it requires a terminal, but it means I finally got past the authorization issues! Time to code!

To quote Anthem: "Don't knock the little wins"
 
Also, fun fact: this isn't my first HUD. I made one freshman year of highschool.
Thats a 2" tft display plugged into a raspberry pi box that I wore clipped to my belt, with a keyboard strapped to my wrist for control.

If you're observant, you'll notice the keyboard looks similar to my suits forearm ;-)
 

Attachments

  • IMG_0030.JPG
    IMG_0030.JPG
    69.2 KB · Views: 284
  • 20140418_154005.jpg
    20140418_154005.jpg
    2.3 MB · Views: 363
  • 20140418_154014.jpg
    20140418_154014.jpg
    1.1 MB · Views: 318
  • IMG_0019.jpg
    IMG_0019.jpg
    902.3 KB · Views: 278
Last edited:
Status
Not open for further replies.
Back
Top