Jump to content

Recommended Posts

Posted

Hi guys. Hoping someone can help me with an issue I'm having with the EAC. I Find that I can't get it to kick on, i.e. The caution panel light goes off and autopilot functions, until I'm like 5 minutes into flight. I notice that in most tutorials and online videos people can get it to fire up right away on the ramp. Any thoughts on what I might be doing wrong? Thanks in advance. Jason

Win 10 Pro, Intel i9 9900k overclocked to 5.1 (water cooled), 64 gb Corsair Dominator platinum RAM (3444 MHz)

Titan RTX overclocked and water cooled

1.1 TB SSD 2 TB M.2 SSD

TM Warthog Stick and throttle

MFG Crosswinds

Reverb VR

Buttkicker LFE, SimShaker, Jetseat.

All DCS modules

Posted

Ok, a little more information on your situation would be nice... I've Noticed EAC wont arm if you dont wait for GPS/INS to align (4.0.0.8 on the CDU) also, you need to make sure you press the EGI switch located below your HSI.

 

Would it be possible for you to post screenshots or a track of what exactly is happening?

Posted

I can put together a track I suppose. Even with alignment and EGI set same is happening. In fact even if EAC is the last thing I turn on during startup it's the same.

Win 10 Pro, Intel i9 9900k overclocked to 5.1 (water cooled), 64 gb Corsair Dominator platinum RAM (3444 MHz)

Titan RTX overclocked and water cooled

1.1 TB SSD 2 TB M.2 SSD

TM Warthog Stick and throttle

MFG Crosswinds

Reverb VR

Buttkicker LFE, SimShaker, Jetseat.

All DCS modules

Posted

thats unusual, go ahead and put together a track, and i'll try to replicate and see if i can find anything you might be doing wrong, or if you maybe found a bug...

  • Like 1
Posted
thats unusual, go ahead and put together a track [...]

 

This!

 

Without a track, we could dance around the problem for several pages in a row. With a track, it could be as simple as "you forgot to switch on $foo and you set $bar too early. Other than that, all is good". ;)

 

On a side note, do not assume that we know anything. Please note which mission you flew in the track, provide info on the version of DCS World you used when you flew that mission, and it would also be good if you could tell us about your input peripherals (Saitek this, Thrustmaster that, just so we get an idea what you use to fly the Hog). :thumbup:

Posted
This!

 

Without a track, we could dance around the problem for several pages in a row. With a track, it could be as simple as "you forgot to switch on $foo and you set $bar too early. Other than that, all is good". ;)

 

On a side note, do not assume that we know anything. Please note which mission you flew in the track, provide info on the version of DCS World you used when you flew that mission, and it would also be good if you could tell us about your input peripherals (Saitek this, Thrustmaster that, just so we get an idea what you use to fly the Hog). :thumbup:

 

 

^ what he said :thumbup:

 

Thanks for adding more details on what we can use, i forget that not everybody knows what info to provide when asking for help :music_whistling:

Posted

I had this problem too, but I've learned that:

* Do not move your aircraft before NAV is aligned to version 4.0.0.8, otherwise alignment will stop and EAC will not function properly.

* Do not switch EAC on before you selected NAV after it have been aligned (Î'm not sure if this is required or not).

 

My steps when starting up the aircraft (concentrated on the EAC and NAV):

1) Turn on EGI and CDU switches (below the CDU screen)

2) Do not move the aircraft while NAV is aligning, the alignment takes about 4 minutes.

3) When alignment is done, it is represented by a blinking 'INS NAV READY' in the top of the CDU screen and the version T = 4.0.0.8 is represented.

4) Navigate to the NAV->ALIGN page in CDU

5) Check that T= 4.0.0.8, this tells us that NAV is fully aligned (as when INS NAV READY is flashing)

6) Select NAV by pressing R7 button on the CDU, or OSB9 on MFD (if I calculating it correctly) when in ALIGN page.

7) Press EGI button on NMSP (Navigation Mode Select Panel)

8) Turn on the RDR ALTM and EAC which is placed below the throttle.

Posted
I had this problem too, but I've learned that:

* Do not move your aircraft before NAV is aligned to version 4.0.0.8, otherwise alignment will stop and EAC will not function properly.

* Do not switch EAC on before you selected NAV after it have been aligned (Î'm not sure if this is required or not).

 

My steps when starting up the aircraft (concentrated on the EAC and NAV):

1) Turn on EGI and CDU switches (below the CDU screen)

2) Do not move the aircraft while NAV is aligning, the alignment takes about 4 minutes.

3) When alignment is done, it is represented by a blinking 'INS NAV READY' in the top of the CDU screen and the version T = 4.0.0.8 is represented.

4) Navigate to the NAV->ALIGN page in CDU

5) Check that T= 4.0.0.8, this tells us that NAV is fully aligned (as when INS NAV READY is flashing)

6) Select NAV by pressing R7 button on the CDU, or OSB9 on MFD (if I calculating it correctly) when in ALIGN page.

7) Press EGI button on NMSP (Navigation Mode Select Panel)

8) Turn on the RDR ALTM and EAC which is placed below the throttle.

 

Precisely

Very concise reply and way better than I could explain:)

i5 8600k@5.2Ghz, Asus Prime A Z370, 32Gb DDR4 3000, GTX1080 SC, Oculus Rift CV1, Modded TM Warthog Modded X52 Collective, Jetseat, W10 Pro 64

[sIGPIC][/sIGPIC]

Posted

Thanks guys...your input was all spot on. It was my own fault. I was hitting NAV once I saw INS NAV READY but not waiting for it to blink or get to 4.0.0.8.

 

Once I got my act together it works perfectly. Thanks for getting me back on point. You guys are the best.

 

Cheers Jason

Win 10 Pro, Intel i9 9900k overclocked to 5.1 (water cooled), 64 gb Corsair Dominator platinum RAM (3444 MHz)

Titan RTX overclocked and water cooled

1.1 TB SSD 2 TB M.2 SSD

TM Warthog Stick and throttle

MFG Crosswinds

Reverb VR

Buttkicker LFE, SimShaker, Jetseat.

All DCS modules

Posted

Sometimes the easiest solution is to double check what your doing, when it comes to startup, it never hurts to have one of the checklists handy if you start having issues. (If you dont have one, just hit that nice search box on here and you will get plenty of hits)

Posted

its actually T= 4.0 0.8

 

not 4.0.0.8

 

T=4.0 means 4 Minutes.

.08 is a completely different parameter value.

Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2),

ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9)

3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs

Posted

Thanks Skatezilla....I never realized that distinction.

Win 10 Pro, Intel i9 9900k overclocked to 5.1 (water cooled), 64 gb Corsair Dominator platinum RAM (3444 MHz)

Titan RTX overclocked and water cooled

1.1 TB SSD 2 TB M.2 SSD

TM Warthog Stick and throttle

MFG Crosswinds

Reverb VR

Buttkicker LFE, SimShaker, Jetseat.

All DCS modules

Posted (edited)

After I read your post Skatezilla, I was wondering what the other pair of number ( i.e. 0.8 ) mean.

 

I've googled a little and also searched in the manual.

 

So, I found a very good explanation of the alignment process:

http://www.checksix-fr.com/bibliotheque/index.php?Fichier=6119

 

There is also an explanation in the manual, though I couldn't find any detailed data about requirements for EAC to fully work.

 

So to conclude how it works from my research:

T = x.x y.y

where x.x is minutes processed while aligning

and y.y is the status of the alignment which in chronological steps shows:

- INIT

- ATTD (system knows attitude data)

- ATTD + HDG (system knows attitude and heading data)

- 8.0

- 7.2 (at this time INS NAV READY is showing, you are ready to activate NAV in scramble mode)

and down to 0.8

 

The decimal number shows the accuracy of the system (the lesser the better), and EAC needs an accuracy lesser than 1.0 to be enabled.

 

Edit:

I.e. if accuracy is 7.2, errors are 7.2 times greater than normal.

Edited by Vantskruv
  • Like 2
Posted
After I read your post Skatezilla, I was wondering what the other pair of number ( i.e. 0.8 ) mean.

 

I've googled a little and also searched in the manual.

 

So, I found a very good explanation of the alignment process:

http://www.checksix-fr.com/bibliotheque/index.php?Fichier=6119

 

There is also an explanation in the manual, though I couldn't find any detailed data about requirements for EAC to fully work.

 

So to conclude how it works from my research:

T = x.x y.y

where x.x is minutes processed while aligning

and y.y is the status of the alignment which in chronological steps shows:

- INIT

- ATTD (system knows attitude data)

- ATTD + HDG (system knows attitude and heading data)

- 8.0

- 7.2 (at this time INS NAV READY is showing, you are ready to activate NAV in scramble mode)

and down to 0.8

 

The decimal number shows the accuracy of the system (the lesser the better), and EAC needs an accuracy lesser than 1.0 to be enabled.

 

Edit:

I.e. if accuracy is 7.2, errors are 7.2 times greater than normal.

 

Thanks, useful to know!

For more information, please visit my website. If you want to reach me with a bug report, feedback or a question, it is best to do this via my Discord channel.
Details about the WinWing draw can be found here. Also, please consider following my channel on Facebook.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...