Old missions will need the ELPS(on) advanced command set, otherwise they don’t appear.
If in a mission a couple of tankers have TACAN set up then that seems to break the Datalink.
The IFF needs to be turned on with Hornet cold start, otherwise you won’t get Mode 4 IFF (sensor switch depress with Radar TDC over target) unknown/friendly/hostile categorization.
The E2 AWACs seems to work, but editing it to an E3 seems not always to work. Not sure why.
The AWACS doesn’t give aircraft type id, i.e. M29 etc. I’ve found boxing the NCTR and doing it myself does work, but obviously very dependent on range and aspect angle. Are people having success with this?
I can’t work out the Bulls Eye (BE) and BRA angles, or rather mine don’t seem logical yet. Probably just me.
Here’s what I’ve been able to gather with @Wes’ help:
EPLRS(on) or switch AWACS unit to a different type, then back to a E-3 or E-2. Haven’t noticed any difference between E-3 or E-2.
All my client based Bugs have EPLRS set to on by default with no changing needed. So even if you don’t have an AWACS present, you can still link with other Bugs.
TACAN beacons don’t break my datalink, but TACAN will always be set to on when the datalink is on. Always in the X and you can only change the beacon number.
Aircraft ID/NCTR is very unreliable, but IFF seems to work pretty well.
When you lock a single target, it will by default go to a diamond. With IFF on, press the interrogate (sensor switch depress) button with the radar page selected and it will determine friend/foe. This also works on the SA page for unknown contacts.
Cold starts require you to fire up both the IFF and the datalink by using the IFF and D/L UFC buttons. Tripped me up at first, so mentioning it here. As mentioned, doing so also turns on the TACAN and forces it to the X mode. So if you use TACAN for navigation, you’ll have to turn off the datalink to be able to go to the Y and A/A modes.
AWACS can also detect and report certain missiles on the SA page. Watched Wes launch HARMs and could see them show as unidentified contacts on the page.
Sorry guys - I’m snowboarding now, so I haven’t been checking.
I figure I should try to clarify things, and if anyone knows otherwise - let us know!
I think the biggest confusion from Wag’s video was the distinction between IFF mode 4 and NCTR. It key to remember, these are separate functions. I had to watch the video a few times myself, because he talks about both pretty much at the same time.
IFF is done via mode 4 IFF system, which does make use of the radar & IFF radio. IFF will tell you friend or foe, but doesn’t tell you WHAT you are looking at. For anyone familiar with civilian ATC, think of the transponder codes (“squawk”) - that is actually IFF mode 3. Now it’s too low tech (lacking encryption and complexity) for military use, hence mode 4. Let’s assume today’s IFF code is 1234. It would be like pinging the transponder, and it send back it’s code. If you get 1234, it’s friendly. Otherwise, hostile. That code doesn’t tell you what type of plane it is.
You can read up on that here, if you like:
To use IFF (Identify Friend or Foe):
As stated by @Franze, IFF must be turned on. Datalink is likely (haven’t tried without, but why not share!)
Put your radar cursor over a target.
Press Sensor Select Depress.
Results will appear on HUD and SA page.
To use NCTR (Non-Cooperative Target Recognition):
Same as above, might as well have IFF on (lest you wish to be seen as hostile to everyone) and Datalink.
Turn on NCTR via the bottom right of the Radar display. Since NCTR utilizes the radar, it must be on. I assume you can increase the chance of an ID by narrowing the scan elevation and azimuth of your radar so it gets more pulses on target & returned.
Select the SA page as active DDI or MPCD.
Hover your SA page cursor over a target. NCTR requires a head-on aspect to get radar signals into the targets intakes.
Azimuth and altitude deviation will degrade chances of this working.
Results, if available will appear in the bottom right corner of the SA page.
The results are:
Shortened callsign. For allied flights, this is the first and last letter of the callsign and it’s numbers. For example: Ford1-1 = FD11, Chevy2-3 = CY23 and so on.
After the callsign is a slash ( / ) followed by the aircraft’s fuel level, in pounds. “30” = 3000 as an example.
Below this is BRA (bearing, range, altitude) but it only seems to have the B & R. The numbers on this seem off right now, I am not sure if it’s BRA from one’s aircraft, or your Air-To-Air waypoint.
To note, I found NCTR only reliably held the ID just before hitting visual range - outside of that, it would grab and lose the identity very quickly. I may need to test more though. My initial tests still used a wide scan on the radar, so as mentioned a narrow scan zone would probably give better results.
I do not believe AWACS can perform NCTR - but if they can, they are likely too far for it to work anyway. Their radars are also not as focused, spinning 360° so the odds of it working I think would be slim.
Updated my above post with some Wikipedia links - for those so inclined, it’s interesting to see how IFF progressed in World War II. That first article gives an example. Both are relatively short. I also tidied up a couple typos and made things a bit clearer.
AWACS doesn’t have NCTR. That said, when working fleet air defense, the carrier can edit Link16 tracks to include type…done via a small intel watch. I asked about this earlier before SA came on line. I know the E-2 should be able to see the updated track info but not sure what the fighters are getting into their SA picture.
And quite frankly, we didn’t bother with that so much. What we added to the picture was primarily for use of the Strike Group commander and his warfare commanders/coordinators. At the end of the day if AW (BW in our strike group) tells a section of Hornets to engage a target, that is what they do, pretty much regardless of what they do or don’t have on their SA.
Quick clarification for future proofing since ED seems to want to update all of this IFF stuff, mode 4 can only ever give you positive friendly indications. Once they have the roe matrix, a negative mode 4 return can only ever mean the contact is neutral, not hostile.
It’s simplified to friend/hostile right now in DCS because they haven’t implemented that functionality yet.
The NCTR print will only show you the type, getting fuel and callsign number and all that is based on the contact being a friendly link participant, not NCTR. But it shows in the same place.
If you are wondering why the data drops and you have to re IFF or NCTR contacts, it’s probly because you don’t have an AWACS pumping surveillance tracks.
If your radar is the only radar out there, any time the contact disappears from your scope, that track and all associated data (IFF/NCTR) is dropped, this includes dropping the contact due to your radars refresh rate, so if you change the frame store value (air to air radar-data-pushbutton 10, which is in the upper right corner) to read 8 or 16 (remember it has a different default setting for each air to air weapon) then it will hold the contact for that many frames without getting another radar hit, which gives the radar time to hit it again and refresh the track.
Things to help this is also, having a wingman there so hopefully one of you is supporting the track at all times. Best solution is an awacs pumping out surveillance tracks, now any updates you make to the track (IFF/NCTR) will remains correlated because your system never loses the track because the surveillance track fills the gaps your own radar has.
EDIT: Also the BRA on the SA page is currently borked, it is in relative bearing to your aircraft with your nose being north. So if it shows 270/40 that means he is 40 miles away off your left wing This is incorrect (unless this version of the hornet is rather silly). Bullseye data appears to be working just fine.
Technically a negative Mode 4 return is an either neutral or hostile aircraft. However, when you apply the ROE in place for the specific operation / conflict, a negative Mode 4 by itself can mean hostile.
ROE should take into account that a defined geographic area to include the waters and airspace, are a war zone, any non-belligerent vessel or aircraft should avoid. Likewise, if the non-Mode 4 radar contact is fling in a tactical or aggressive manner–i.e. 500 knots GS, and keep making hard turns for your flight–then ROE may allow you to determine it as hostile…airliners just don’t do that.
An important caveat to US ROE is that no ROE restrictions prevents you from acting in your own self defense or collective self defense. Good ROE will provide clear definitions of Hostile Actions and Hostile Intent. Normally if you see either, fights on.
Regarding DCS MP servers that are focused on A2A. I would think that the ROE is pretty open and that a negative Mode 4 = enemy.
Yes, I am reviving this topic…“Charge to 200…CLEAR!”
Now with NEUTRAL aircraft - to include Neutral TACAIR, this becomes interesting. The HAFU symbology should retain the square symbology for known Neutral…should be?…not really.
In US doctrine you have Blue, Read and White. Blue is US/allied (Circle HAFU). Red is non-US/allied military (Diamond HAFU). White is civilian - i.e. COMAIR and Merchant ships - never saw a civilian submarine (Square HAFU, same as Unknown)
“But…”, I hear you ask, “What about a country that is not an ally but they are ‘friendly’…why they have to get the Red category?” This is actually a bigger problem than one might think. It has diplomatic ramifications. Two ways to handle it: 1- If they are on Blue side in an exercise, they are Blue/circle. If they are the adversary, they are Red/diamond. 2 - If its not an exercise but we don’t want to offend, we make them White/square but call them “Green”.
Anyway, I’m going to do some “investigating” today (No honey, I’m not just flying around for fun. This is serious investigating!).
BTW, yesterday I did some “Investigating” from the Red side of things - ground based EW and GCI tom my mighty MiG-21. It works very well. GCI will vector you to Blue and White contacts; ignore the Red as it should (and has always done). Then I shot down a White COMAIR (because they were imperialist running dog lackys) - the debrief doesn’t handle the Neutral side (yet?) so it doesn’t show, however, you don’t get points for the kill, which is fair.
Set Up: PG map. Carrier Strike Group (CSG; CVN-73, CG and DDG) steaming N towards the SOH in the GOO. E-2D airborne, just east of the CSG. FA-18 CAP to the N running E-W legs. F-15 CAP in the Southern PG off Dubai.
ROE: Everybody WEAPONS HOLD.
WHITE Countries used:
COMAIR - Algeria, Greece, Georgia, Ukraine. All have some type of transport aircraft in civilian/government non-military markings.
Military - Oman (UH-1); UAE M2000
WHITE COMAIR. (10 total; Yak40, IL-76, AN-28/30, C-130). Two flying "transit routs over the area, most other taking off from / flying To/From civilian and dual use airfields. Some activated at start; some later activated with timed triggers.
WHITE Helos (2 total; one to/from across the SOH; one along the Omani coast0
WHITE CAP (2 UAE M2000 CAP over land)
RED AIR (6; 2 x IRIAF C-130; 2 x MiG-29 CAP vic Bandar Abbas; 1 x IRIN Mi-8 coastal)
Other BLUE MILAIR (2; 1 x USAF KC-135, 1 French AF C-130)
also some RED, WHITE and BLUE shipping and a few RED EW and SAMs.
So, a lot going on in a little area. I flew an FA-18 loaded out for CAP (2 x 120C; 2 x 9M; 3 x fuel).
My mission was to take a look at how the E-2D was painting the SA picture and then go do some VID on UNK targets.
This was great fun. I need to read the updated manual a bit more and review the video at the top of this thread, but all-in-all I got the hang of things after a couple of flights.
Comms: All the WHITE Air (planes and helos) were on the same freq as my tactical channel (251 MHz); not set to silent. So I was hearing them get airborne, pass WPs. Good for my experimenting (I knew things were working). To make it realistic I will create an area ATC frequency and set all COMAIR to it- perhaps dial it into Comm 2. Keep BLUE Air on the tactical channel(s).
HAFU determination. Worked as advertised! Great fun. That said, the E-2 seemed to “know” that the IRIAF C-130 that took off from Jask, headed for Bandar Abbas, was RED/Hostile. That is actually pretty good for DCS purposes - they see it take off from Jask, a designated a RED airbase so contact = RED?. At first, the SA showed the UNK “top” (my side) and HOS “bottom” (E-2 donor side)…then went to full diamond. I also saw an UNK WHITE COMAIR An-30 that I was VIDing change to a FRD “top”. For DCS, both are good-it is what you want!, however, I need to explore more to find out why the AI did that.
SAM sites…does the E-2 have to detect the site for it to sow on the SA? Or is it a combo of E-2 donor info and own plane RWR? Sometimes the SA-6 was there…sometimes it wasn’t. I need to figure that out.
So far - the Hornet SA/DL combined with the Neutral category makes things pretty interesting. Need to check out ships and ground stuff…i.e. will a WHITE SAM engage you? Fun stuff.
I probably should share what I have now so other folks can play with it. I’ve got all the COMAIR on one frequency, RED air on another…playing around with frequency for WHITE TACAIR…probably want them to be up on something that BLUE can hear if only for deconfliction…added a WHITE SAM…
This really adds a level of realism that in RL is always an issue - a WHITE C-130 flying in the same airspace as a couple of RED C-130s…this may not have been what ED had in mind but it sure is fun.
Here is the mission I’ve been playing around with. Very Basic. Start on the deck of a carrier, take off and fly around trying to VID contacts. Once you VID - either visual or A2A FLIR then you can put in a PLID. The E-2 tends to call out a lot of stuff…yeah…
The White and Blue Bullseye are at the same spot (Your WP 2). So you can hear the White CAP (UAE M2000s) call out their posit relative to the same BE that you are using. In the future I may have them making an intercept that you will be able to “follow along”…maybe back them up, etc.
Likewise, with some triggers I can envision a CSAR mission where the hornet covers for a White SAR helo…fun stuff.