Go Back  PPRuNe Forums > Other Aircrew Forums > Flight Testing
Reload this Page >

Impact of system latency upon controllability ?

Wikiposts
Search
Flight Testing A forum for test pilots, flight test engineers, observers, telemetry and instrumentation engineers and anybody else involved in the demanding and complex business of testing aeroplanes, helicopters and equipment.

Impact of system latency upon controllability ?

Thread Tools
 
Search this Thread
 
Old 8th Aug 2017, 17:00
  #1 (permalink)  
Moderator
Thread Starter
 
Join Date: Feb 2000
Location: UK
Posts: 14,216
Received 48 Likes on 24 Posts
Impact of system latency upon controllability ?

I've just been wading through a (non aviation) document on system latency that claims to be showing me some wonderful lessons about how critical system latency (input-response delay) is to controllability. No sh1t Sherlock!

However, when I went and had a rummage around the usual sources, I can't seem to find any good documentation to support what I believe I intuitively know either for aircraft, or the other obvious user of such principles - computer game design.

Can anybody point me at a good document on the topic?

G
Genghis the Engineer is offline  
Old 9th Aug 2017, 09:55
  #2 (permalink)  
 
Join Date: Jul 2007
Location: 51.50N 1W (ish)
Posts: 1,141
Received 30 Likes on 13 Posts
When I passed through NASA Dryden (Edwards AFB) in '69, they were doing some serious research on that, related to deliberate crashing an unmanned aircraft in a controlled way (they didn't wan't an uncontrolled crash, for some reason). I can't find anything from then in my library, but the first reference on the link below may be of relevance.

https://tinyurl.com/y7deuqjz
Fitter2 is offline  
Old 9th Aug 2017, 11:08
  #3 (permalink)  
Moderator
Thread Starter
 
Join Date: Feb 2000
Location: UK
Posts: 14,216
Received 48 Likes on 24 Posts
Thanks Fitter, but I suspect it isn't. I can't see drone command signal latency having much relevance to the problem of control / FBW direct input response latency?

G
Genghis the Engineer is offline  
Old 9th Aug 2017, 21:27
  #4 (permalink)  
 
Join Date: Jan 2004
Location: LIVT
Posts: 193
Received 2 Likes on 2 Posts
This looks interesting:
https://etd.ohiolink.edu/pg_10?0::NO...yton1418340523
It presents a study carried out on a flight sim F-16 Flight Control System model, so I understand that the latency limits they found between a stable and unstable behaviour are related to the flight sim model they used and do not necessarily reflect what you would find on a real F-16. On the other side, I suppose the investigation method would be applicable to a real case as well.

The relevant paragraphs are 3.12 and 6.2.

Edit: The link to the .pdf file with the full text of the thesis is at the bottom of the webpage and not very conspicuous, so I enclose it below.
https://etd.ohiolink.edu/!etd.send_f...ion=attachment

Last edited by aerolearner; 9th Aug 2017 at 21:43. Reason: Add link to pdf
aerolearner is offline  
Old 9th Aug 2017, 23:57
  #5 (permalink)  
 
Join Date: Apr 2002
Location: Nirvana South
Posts: 734
Likes: 0
Received 0 Likes on 0 Posts
Genghis,
Not my specialty as I more ensured that the overall AFCS met requirements & certification, but my recollection is that what you're asking was a fairly closely held outcome of programmes such as Bombardier's Active Control Technology (ACT) run in conjunction with Rockwell Collins' Flight Controls group. PM me if you need potential authors for a search.

A quick search on Latency on the SFTE website only brought up one paper but, again, my memory from around 10 years ago is that there were several such papers as smaller manufacturers looked at FBW. This is the link: https://www.sfte.org/component/conte...?paper_id=1264
ICT_SLB is offline  
Old 30th Aug 2017, 03:22
  #6 (permalink)  
 
Join Date: Apr 2002
Location: Nirvana South
Posts: 734
Likes: 0
Received 0 Likes on 0 Posts
Genghis,
Just got this in an e-mail from the IET Digital Library.

Execution time analysis and optimisation techniques in the model-based development of a flight control software

This case study analyses the possibilities to improve the execution time of model-based developed software by applying optimisations during code generation and compilation. The present case study is performed on flight control software, for which safety aspects are accounted throughout the development. Therefore, a formally verified compiler is used for the optimisation during the compilation. The optimisation is evaluated by execution time measurements on the target and a static worst-case execution time analysis. Based on the results, recommendations for certain model patterns are given, which impact the worst-case execution time analysis.

http://digital-library.theiet.org/do...3CD80308BCDE83
ICT_SLB is offline  
Old 30th Aug 2017, 11:59
  #7 (permalink)  
 
Join Date: Oct 1999
Location: Den Haag
Age: 57
Posts: 6,251
Received 331 Likes on 184 Posts
My main exposure to latency has been in Full Flight Simulators. Some pertinent stuff here:
https://ntrs.nasa.gov/archive/nasa/c...0050192646.pdf
http://reports.nlr.nl/xmlui/bitstrea...pdf?sequence=1
212man is offline  
Old 30th Aug 2017, 12:22
  #8 (permalink)  
 
Join Date: Nov 2015
Location: Mordor
Posts: 1,315
Received 54 Likes on 29 Posts
You may not find a specific reference because it's too basic. Any control engineering text looking at system dynamics using Laplace or similar makes this issue self-evident. Control systems implement negative feedback to achieve stability (a deviation triggers a control input in the opposite sense to the deviation). Latency is essentially phase-lag, and any phase lag in a negative-feedback system produces positive feedback (instability) resulting in either oscillation or divergence. That's the basic bit, but at deeper levels you can have nth-order phase lag (ie where the lag is in the velocity, acceleration or jerk response rather than the position response) which need to be understood mathematically for the correct fixes to be applied.

As a practical example one of the test pilot memoirs I've read talked about the Fairy Delta-II (I think) whose powered control system was rather experimental and suffered lags in the hydraulics until the oil warmed up (or something like that). So when each pilot flew it for the first time they would climb away with an apparently uncontrolable 1-2Hz pitch oscillation which would be rather alarming for the first five minutes, and then progressively disappeared.

PDR
PDR1 is offline  
Old 31st Aug 2017, 16:33
  #9 (permalink)  
Moderator
Thread Starter
 
Join Date: Feb 2000
Location: UK
Posts: 14,216
Received 48 Likes on 24 Posts
Thanks guys.

I've bounced the document (a paper sent to me to review by a "leading" academic journal) a strongly worded recommendation that they go off, talk to all or any of test pilots, simulator engineers and/or computer games designers and re-write it in the context of a chunk of real world experience. 212's documents I gave a special mention to.

PPrune at its best!

G
Genghis the Engineer is offline  
Old 1st Sep 2017, 22:09
  #10 (permalink)  
 
Join Date: Mar 2016
Location: In a happy place
Posts: 12
Likes: 0
Received 0 Likes on 0 Posts
Genghis,

Any delay in visual representation of actual (or preceived) motion greater than 100ms will make an aircraft more difficult to control. A (test) pilot will report the delay as degraded aircraft handling properties, but it is actually poor performance of the (simulator) visual system of the PFD generator. The corollary is than a delay of less than 100ms is likely to be acceptable. No reference available I'm afraid, just hard won experience.

Phil
Phil_and_Sand is offline  
Old 5th Sep 2017, 15:16
  #11 (permalink)  
Moderator
Thread Starter
 
Join Date: Feb 2000
Location: UK
Posts: 14,216
Received 48 Likes on 24 Posts
Well indeed - and I think that most flight testers (along with simulator engineers, computer game designers...) know all of that fairly intuitively - as you and I do.

The big surprise for me here was the lack of formal experimental evidence of this. After all, I'd not have to look at all hard, for example, for data relating stick force gradients to controllability, or damping to risk of divergent oscillatory modes.

G
Genghis the Engineer is offline  

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off



Contact Us - Archive - Advertising - Cookie Policy - Privacy Statement - Terms of Service

Copyright © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.