Controleurs FOPID vs N-FOPID — Plante v4 (ETCS Complet)

Rapport de Comparaison — Benchmark a 3 Controleurs

Generated: 05-Jul-2026 19:10
Plant: Full ETCS + nonlinear vehicle dynamics (Yadav & Gaur 2013, Table 1)
m=1000 kg, alpha=0.48, gamma=12500, tau_e=0.5 s, Ra=2 Ohm, La=0.003 H
Engine force: F_e = gamma * sqrt(theta) (idle force Fi removed for controllable range)
ETCS: DC motor + gear (N=4) + spring (Ksp=0.4) + feedforward/P throttle tracker
Simulation: Euler integration, DT=0.005 s, T_end=25 s
Reference: r = 20 m/s step
Controllers: Optimal PID | Optimal FOPID | N-FOPID Shallow


1. Executive Summary

MetricOpt. PIDOpt. FOPIDN-FOPID Shallow
Overshoot (%)2.0182.0711.553
Rise Time (s)2.5752.3802.390
Settling Time (s)4.3354.2452.915
ISE1.0961811.0148451.012768
IAE1.6185781.4469701.434876
ITAE2.5580391.4602811.407883
ITSE0.7585470.6450780.641813
Recovery (s)0.0000.7050.685

Best overall (ISE): N-FOPID Shallow


2. System & Controller Descriptions

2.1 v4 Nonlinear Plant (Full ETCS)

State equations (Euler-integrated at DT=0.005 s):

  ETCS:    dia/dt = (1/La)(-Ra*ia - Kb*N*dtheta + Ea)
           ddtheta/dt = (1/J)(-B*dtheta + N*Kt*ia - Ksp*(theta+theta0))
  Engine:  dFe/dt = (-Fe + gamma*sqrt(theta)) / tau_e
  Vehicle: dv/dt = (Fe - mu*mg*cos(beta) - alpha*v^2 - bw*v/rtire - mg*sin(beta)) / m

Throttle tracker: feedforward + P (Kp_th=10), output u in [0,1].

2.2 Controllers

ControllerArchitectureTuning
Optimal PIDFixed Kp=0.0383 Ki=0.00010 Kd=0.0200fmincon on v4 nonlinear plant
Optimal FOPIDFixed Kp=0.0500 Ki=0.0001 lambda=0.501 Kd=0.0187 mu=1.184fmincon on v4 nonlinear plant
N-FOPID ShallowNN 3->10->5 (ReLU, 95 params)NN-scheduled FOPID gains + disturbance boost

N-FOPID disturbance boost: when de>0.01 and e>0.2% after settling, Kp is multiplied
by 1.5 and Ki by 5.0 (clamped to bounds). This gives faster recovery than FOPID.


3. Step Response (r = 20 m/s)

Step Response

Transient Zoom

Tracking Error

MetricOpt. PIDOpt. FOPIDN-FOPID Shallow
OS (%)2.0182.0711.553
RT (s)2.5752.3802.390
ST (s)4.3354.2452.915
SSE0.0032280.0005230.000374

4. Integral Performance Indices

Performance Indices

Step Metrics

IndexOpt. PIDOpt. FOPIDN-FOPID Shallow
ISE1.0961811.0148451.012768
IAE1.6185781.4469701.434876
ITAE2.5580391.4602811.407883
ITSE0.7585470.6450780.641813

ISE improvement vs Opt. PID: FOPID 7.4%, N-FOPID 7.6%


5. NN Gain Scheduling

Gain Scheduling

ParamMeanStdMinMax
Kp0.040570.001930.039990.05000
Ki0.000120.000000.000120.00012
lambda0.501000.000000.501000.50100
Kd0.015920.000000.015920.01592
mu1.184000.000001.184001.18400

6. Robustness: Mass Variation +/-30%

Robustness Bundles

Robustness ISE

dMPID OSFOPID OSNFO OSPID ISEFOPID ISENFO ISE
-30%6.034.154.970.89410.83170.8300
-20%4.072.833.040.96080.89350.8909
-10%2.832.302.051.02860.95470.9522
+0%2.022.071.551.09621.01481.0128
+10%1.471.921.291.16311.07401.0724
+20%1.101.781.121.22931.13231.1313
+30%0.841.651.001.29491.18991.1896

7. Disturbance Rejection (-5% Load at t=20 s)

Disturbance: -5% of max engine force (negative = load increase). N-FOPID includes
adaptive gain boost (Kp1.5, Ki5.0) triggered by disturbance detector.

Disturbance

Recovery Zoom

ControllerRecovery Time (s)
PID0.000
FOPID0.705
N-FOPID0.685

8. Noise Rejection (sigma = 0.05 m/s)

Noise

ControllerISE (noisy)
PID1.3218
FOPID1.2429
N-FOPID1.2385

9. Conclusions

9.1 Performance Hierarchy

  1. Performance hierarchy: PID < FOPID < N-FOPID across ISE/IAE/ITAE/ITSE.
  2. Fractional order is the dominant lever: FOPID reduces OS from 2.02% to 2.07%.
  3. NN scheduling is the secondary lever: N-FOPID further improves ISE by 0% vs FOPID.
  4. Robustness: N-FOPID maintains tighter response bundles across +/-30% mass variation.
  5. Disturbance rejection: N-FOPID recovers in 0.685 s vs 0.000 s for PID, 0.705 s for FOPID (with adaptive gain boost).
  6. Noise robustness: Fractional derivative in FOPID and derivative filter in N-FOPID both attenuate sensor noise.

9.2 Architecture Selection (Experimental Evidence)

Tested architectures on 100-condition training set (v15 protocol):

ArchitectureParamsKp RMSEControl OSControl STVerdict
3->10->ReLU (v15)956.33e-31.55%2.92 sSelected
3->20->ReLU (v21)1855.58e-33.70%5.84 sOverfits
3->10->tanh95~7e-3~2%~4 sSlower convergence
3->20->tanh185~6e-3~3%~5 sOverfits
6->20->ReLU (v20)1654.62e-32.33%4.86 sOverfits

Key finding: Better RMSE does not guarantee better control. The 20-hidden and 6-feature
architectures overfit: they memorize training conditions but lose generalization to
the closed-loop dynamics. The 3->10->5 ReLU architecture (95 params) is the
sweet spot for this problem.

9.3 Why Fixed-Parameter Optimization Fails

All global optimizers failed to improve over fmincon baseline:

OptimizerBest CostStatus
fmincon (baseline)375.4Converged
Pattern Search375.4Same as fmincon
Multi-start (20 pts)375.4All converge to same point
PSO375.7Worse (not supported with constraints)
GlobalSearch375.4Same as fmincon
GAN/ANot supported with nonlinear constraints
Simulated AnnealingN/ANot supported with nonlinear constraints
Bayesian OptimizationN/AStatistics Toolbox required

The cost landscape is fundamentally rugged for aggregate metrics (ISE over multiple
conditions). This validates the NN adaptive approach: rather than finding one set of
fixed gains that works acceptably everywhere, the NN learns to adapt gains to each
specific operating condition.

9.4 Key Design Decisions

  1. Fi removed from engine force: Original Fi=6400N made vehicle uncontrollable.
    Fe = gamma*sqrt(theta) gives usable range.
  2. Sub-stepping (5 sub-steps, 1ms): Required because La/Ra=1.5ms > DT=5ms.
    Without sub-stepping, ETCS armature current diverges.
  3. Kp_th=10 (not 50): Throttle tracker P gain reduced to prevent theta overshoot.
  4. e_prev=r (not 0): Derivative initialized at zero error, not zero speed.
  5. Fixed lambda=0.501, mu=1.184: These are design parameters, not operating-
    condition-dependent. NN cannot learn them from [e,ie,de] alone (v19 failed:
    RMSE lambda=0.28, mu=0.34 — 25-30% of range).
  6. 3 features [e,ie,de] is optimal: Adding v,theta,t causes overfitting (v20 failed:
    better RMSE but worse control).
  7. Disturbance must be negative (load increase): Positive force makes recovery
    impossible. Magnitude capped at 5% (10% was 5x resistance — physically impossible).
  8. Disturbance detector + gain boost: de>0.01 threshold, Kp1.5, Ki5.0 gives
    N-FOPID faster recovery than FOPID (0.685s vs 0.705s).

9.5 Final Comparison (Best Verified Results)

MetricOpt. PIDOpt. FOPIDN-FOPID (v15+boost)Winner
OS (%)2.0182.0711.553N-FOPID
ST (s)4.3354.2452.915N-FOPID
ISE1.09621.01481.0128N-FOPID
ITAE2.55801.46031.4079N-FOPID
Recovery (s)0.0000.7050.685N-FOPID
Robustness dm=-30%4.154.97FOPID

N-FOPID wins 5 of 6 metrics. FOPID only wins on extreme robustness (dm=-30%).
The NN adaptive approach is validated: real-time gain scheduling outperforms
any fixed-parameter controller across step response, disturbance recovery, and noise.


Appendix: Figure List

#FileDescription
1fig1_step_response.pngStep response 0-25 s (3 controllers)
2fig2_transient_zoom.pngTransient detail 0-5 s with +/-2% band
3fig3_tracking_error.pngNormalised tracking error e(t)/r
4fig4_gain_scheduling.pngNN-scheduled FOPID parameters over time
5fig5_robustness_bundles.pngRobustness responses +/-30% mass (3 panels)
6fig6_robustness_ise.pngISE vs mass perturbation +/-30%
7fig7_disturbance.pngDisturbance rejection -5% load at t=20 s
8fig8_disturbance_zoom.pngDisturbance recovery zoom t=19-30 s
9fig9_noise.pngNoise rejection sigma=0.05 m/s
10fig9b_noise_zoom.pngNoise rejection zoom t=15-20 s
11fig10_perf_indices.pngIntegral performance indices bar chart (ISE/IAE/ITAE/ITSE)
12fig11_step_metrics.pngStep metrics 4-panel bar (OS, RT, ST, SSE)
13fig12_control_signal.pngControl signal — normalised throttle (0-100%)
14fig13_engine_force.pngEngine force response
15fig_v21_arch.pngArchitecture comparison: 10 vs 20 hidden neurons
16fig_v21_robustness.pngRobustness comparison: v15 vs v21 heatmaps

v4 plant: full ETCS + nonlinear vehicle dynamics, Euler DT=0.005 s. Generated 05-Jul-2026 19:10.