sunski34 Posted June 25, 2017 Posted June 25, 2017 (edited) Hi, yesterday I tried several tests on Nevada with radar horizontal scanning scope set to +/- 15° and 30°. Altitude more than 15k feet. I noticed those strange things: A target (already displayed on VTB with large +/-60° scope) stays on VTB when switching to smaller scope and moving TDC to put it out of scope. Target isn't locked of course (No PIC or PID, just scanning). I didn't test if a target appears when out of scope and never scanned before. When a target is out of scope and displayed on VTB you can lock it immediatly (target already scanned by the radar even if out of scope) At long range (up to 40 Nm), there's no real time difference to scan and display a target (hot, 0°, same altitude). I didn't test with smaller range. May I have explanations about that? Thanks Edited June 25, 2017 by sunski34
jojo Posted June 25, 2017 Posted June 25, 2017 May you post a track please ? I don't understand how can you lock a target out of scan zone since scan zone is centered on TDC in azimuth ? Mirage fanatic ! I7-7700K/ MSI RTX3080/ RAM 64 Go/ SSD / TM Hornet stick-Virpil WarBRD + Virpil CM3 Throttle + MFG Crosswind + Reverb G2. Flickr gallery: https://www.flickr.com/gp/71068385@N02/728Hbi
sunski34 Posted June 25, 2017 Author Posted June 25, 2017 (edited) you've right Just a precision ... The target was already on VTB and out of scope, and when moving TDC I can lock it immediatly. So it's not a bad VTB display but a real target already scanned, that what I want to say.... I think that a target out of scope cannot be displayed on VTB and when changing azimuth by moving TDC, it will take time to have a VTB displayed target. Hope my explanation more clear ;) I adjusted my first remark. Edited June 25, 2017 by sunski34
sunski34 Posted June 25, 2017 Author Posted June 25, 2017 Ok, I did new tests... What I understood : A target is in scope once (60°) and is displayed on VTB. When changing scope to put it out of scope, the displayed target seemed to be memorized for 10 seconds approximately. If you put it on scope again before this delay it's like it will never be out of scope... When this delay ellapsed and the target still out of scope, the target dispears from VTB. Is that right?
sunski34 Posted June 25, 2017 Author Posted June 25, 2017 This delay seems to be used for RWR warning too when locked by a target aircraft...
Recommended Posts