EDDI VS EdBindings

GitHub link

Alternatively, because Elite doesn't bother to tell you why, download and use a program called EDDI. It will tell you why you aren't able to dock. If it's purely betno pads are available, just wait. It will tell you if the size requirements aren't right either.

If you are exploring in the black, mapping new systems, you would also need to run something like EDDI or EDDLite configured to send data to ESDM.net for the best experience.

It is still best to use something like EDDI or EDDLite to send data EDSM but ICARUS Terminal will blend that data with your local scan data to provide real time updates to a second screen as you explore when using a Discovery Scanner, Full Spectrum Scanner or Surface Scanner.

This. Voice Attack + EDDI integration can do it:

GitHub link for EDDI. I love this program. It's my COVAS on steroids and is customizable to the extreme. Official Forum link for EDDI

Elite Dangerous Data Interface

EDDI as a plugin for VA which gives you access to loads of variables and statuses within VA to build commands with. For example {BOOL:Status lights on} would tell you if vehicle lights are on or off. (Note it should automatically start as plugin with VA, it can be started standalone but it's very talkative by default and will conflict with VA).

One such software is the Elite Dangerous Data Interface (EDCD/EDDI). There are others too like the EDMC. Once configured. EDDI integrates data with several different 3rd-party resources such as EDDB, EDSM, EDDN, VoiceAttack and others.

Also useful is the EdBindings app that lets you search your keybinds file as it provides the bindED variables you then use in VA.

To assist with bindED I suggest using EDBindings which is a small app that will let you search your own keybinds used in Elite and easily find the variable names to use in VA.

some ideas perhaps https://github.com/RealOfficialTurf/EDRefKB and https://github.com/ghorsey/EdBindings