BACARS 10.7.11 — PSX reconnect
Router restarts no longer reset flight or CDU state on every connection attempt. BACARS disposes dead sockets, retries at five-second intervals, sends its name once per connection and waits for the initial PSX snapshot before resuming operational actions.
The same flight retains its loadsheet scheduling, fuel session/receipt identity, turnaround timestamps, stored messages and pending company INIT. Snapshot replay establishes door, engine, fuel and circuit-breaker baselines without replaying live actions. Confirmed aircraft/callsign changes and explicit resets retain their reset behaviour.
Printer delivery runs independently of Hoppie connectivity. Queued messages wait for PSX readiness. If a send fails before any attempt, the original message is queued again; if delivery is uncertain, its stored copy remains available for manual reprint rather than automatic duplication. PSX provides no printer acknowledgement.
Fuel settlement waits for fresh samples after reconnect. Repeated disconnected fuel-truck updates no longer overwrite the recorded end time. Events that occur while BACARS is disconnected cannot be precisely timestamped.