El strobe elevation should "roll" even when FCR is not the SOI
-
This could be an area that BMS doesnt match the real deal as much as it could, then. As I understand it, ‘extrapolation’ in BMS consists of free knowledge of exactly where the contact is.
-
I’m sure what “El strobe” is (elevation strope <shrug>don’t know what that is either).
However, I thought that HAD uses the FCR as a sensor. Thus losing some of AA settings and fuctions.</shrug>
-
Nope, HAD uses the HTS as a sensor.
-
And I guess you dont believe HAD uses the RWR or the missile seeker either.
Anyway, using HAD and FCR together has always been buggy. I assumed it was rl.
-
And I guess you dont believe HAD uses the RWR or the missile seeker either.
Anyway, using HAD and FCR together has always been buggy. I assumed it was rl.
Dont know for the RWR, didnt think so for the HARM missile seeker.
-
I’m not up for finding reffs, The HTS is a range finder. On earlier generations the HTS pod looks more optical than radome. I believe the HAD page gets slant angel from seeker or/and fcr, vector from RWR and HTS pod laser ranger finds slant range using slant angel. HAS compiles many sensors to come up with solution. Big maybe <shrug>.</shrug>
-
I’m not up for finding reffs, The HTS is a range finder. On earlier generations the HTS pod looks more optical than radome. I believe the HAD page gets slant angel from seeker or/and fcr, vector from RWR and HTS pod laser ranger finds slant range using slant angel. HAS compiles many sensors to come up with solution. Big maybe <shrug>.</shrug>
Still really off topic… but its not an optical sensor. Its not a range finder alone, either. Its a lot more complicated than that.
-
Still really off topic… but its not an optical sensor. Its not a range finder alone, either. Its a lot more complicated than that.
Off topic would depend on witch generation of HTS pod is modeled and how the system works. Generation 5+ use rf sensors and high speed data processing.
Ever wondered why the HTS designate function stops working after the last missile is fired? (Some F4 versions) Mismodeled or rl
-
Perhaps a new thread should be started to keep this one relevant to El strobe elevation implementation.
-
You’re implying that there is some type of lag between where my antenna is and where my el strobe is, and there’s not. When I roll the el strobe it immediately moves the antenna. Therefore instantaneously my search volume and where the radar is looking changes immediately. And as a pilot this is what I want. There are tactics that I can’t discuss here where every second matters because if I have to wait than it forces another tactic. I need instant results. And this is how it works in the jet.
Sidenote: don’t use TWS. RWS is pretty much the CAF standard. They call it Track While Lie for a reason. I can’t get into the whole discussion of the numbers and why it’s that way. It has to do with extrapolation with regards to a few different things.
Fair comment/observation…but I guess what I’m saying is that your “el strobe” is lying to you, if you think you are changing your FCR reporting volume “instantaneously”. My take is that it shows you where you’ve commanded the antenna, not where the antenna actually is - not until end of bar, at the shortest interval…that’s one of the short comings of a mech-scanning antenna. And just to be clear, we are talking about the FCR and not something I’ve missed, eh?..
-
Shouldnt that kind of behavior be noted in the dash, then? I cant see it in there.
-
…noted elsewhere. The Dash 1 isn’t the end-all of how systems operate.
-
…I clearly wasnt talking about the dash one, seeing as we are discussing the radar.
-
Steveie,
I understand what you’re trying to say. Yes there is some type of lag in there because it is mechanical so you definitely have a lag compared to something like an AESA radar. But that’s not what this question/answer is about. This is about being having my SOI elsewhere and it not redrawing the search volume vertical limits next to my cursor until I DMS back over to the FCR (making it my SOI again) if I have rolled my el strobe. I literally just flew the jet today and the way BMS models this is incorrect. You don’t see it here because the HAD and HSD (L16) are not very well modeled or up to date. But sometimes I need my SOI over in the right MFD yet I still can roll my el strobe and see my search volume changing without having to DMS over.
To add, I can see exactly where my antenna is looking and which bar it’s on. The little tick marks on the side and bottom that move represent your antenna. You can literally watch it scan each bar.
-
That’s why I asked about the “el strobe”…I guess it’s not something I’ve paid attention to. I’m thinking of it as the tick-marks on the side of the display that indicate the el setting/position. I’ll have to take a look myself…it makes sense to me that your controls would/could only be tied to your SOI and not split between two sensors at the same time; the two should be slaved though…I’d think. In which case there could also be some lag or error.
-
if I have rolled my el strobe
Are you saying that when changing the antenna elevation on the throttle it does not change altitude search limits on the fcr cursor when fcr is not SOI?
If that is the case, imo that would a bug when fcr and HSD is selected. HAD I’m not sure. Because as said before, the fcr could used by the HTS. Rolling el would be nulled while ccip.
BTW the HAD code looks +20 years old. The devs only code when they good documentation and it must hard to find pilots with weasel seat time.
-
Because as said before, the fcr could used by the HTS. Rolling el would be nulled while ccip.
Seeing as CCIP locks the FCR to AGR… NSS!!
-
Seeing as CCIP locks the FCR to AGR… NSS!!
-
Are you saying that when changing the antenna elevation on the throttle it does not change altitude search limits on the fcr cursor when fcr is not SOI?
If that is the case, imo that would a bug when fcr and HSD is selected. HAD I’m not sure. Because as said before, the fcr could used by the HTS. Rolling el would be nulled while ccip.
BTW the HAD code looks +20 years old. The devs only code when they good documentation and it must hard to find pilots with weasel seat time.
…I’m pretty sure that’s the way it should be. If it’s not…
-