News:

Precision Simulator update 10.173 (24 February 2024) is now available.
Navburo update 13 (23 November 2022) is now available.
NG FMC and More is released.

Main Menu

Resync fail - single fmc

Started by GodAtum, Sat, 21 Apr 2018 12:18

GodAtum

When I load winds aloft data into the FMC, the error "Resync fail - single fmc" pops up. But the FMCs work fine and I can carry on with my flight with no issues. Not sure if I'm doing something wrong, a bit odd.

Toga

I have experienced this also though i think it's a BACARS thing. I could be wrong.

Hardy Heinlin

The most likely cause for this message is an incorrectly formatted FMC route data injection from an add-on.

Aerowinx/Logs/errors.txt may show some details.

GodAtum

Ah yes:

[Aerowinx Precision Simulator - Exceptions]

java.lang.NumberFormatException: For input string: "2900ZSPDOBBI332"
at java.lang.NumberFormatException.forInputString(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at RadioAtcBasis.readGlobBasics(RadioAtcBasis.java:483)
at RadioAtcBasis.situLoadInit(RadioAtcBasis.java:179)
at Core.unpauseLoader(Core.java:373)
at NetClientThread.run(NetClientThread.java:136)
java.lang.NumberFormatException: For input string: "294/19"
at sun.misc.FloatingDecimal.readJavaFormatString(Unknown Source)
at sun.misc.FloatingDecimal.parseFloat(Unknown Source)
at java.lang.Float.parseFloat(Unknown Source)
at Routes$RteBody.readGlob(Routes.java:4898)
at FmcRte$Rte.readGlobRteHeader(FmcRte.java:367)
at FmcRte$Rte.runModerato(FmcRte.java:554)
at FmcRte.runModerato(FmcRte.java:2043)
at FmcGlobal.runModerato(FmcGlobal.java:2364)
at Core$ModeratoThread.run(Core.java:1386)
at java.lang.Thread.run(Unknown Source)
java.lang.NumberFormatException: For input string: "2900ZSPDOBBI332"
at java.lang.NumberFormatException.forInputString(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at RadioAtcBasis.readGlobBasics(RadioAtcBasis.java:483)
at RadioAtcBasis.situLoadInit(RadioAtcBasis.java:179)
at Core.unpauseLoader(Core.java:373)
at NetClientThread.run(NetClientThread.java:136)

Gary Oliver

What version of BACARS are you using? I did have this problem however I thought it was fixed in a later version...

What flight were you trying to do? Assuming it was a dispatch centre flight plan that caused it?

I can probably grab the incorrect file and work out the problem.

Cheers
Gary

GodAtum

Quote from: Gary Oliver on Sat, 21 Apr 2018 16:30
What version of BACARS are you using? I did have this problem however I thought it was fixed in a later version...

What flight were you trying to do? Assuming it was a dispatch centre flight plan that caused it?

I can probably grab the incorrect file and work out the problem.

Cheers
Gary

I'm running v4.0.4. Flight was done via the dispatch centre BAW296 LEBl-KORD. Cheers for you help.

Jeroen Hoppenbrouwers

Wait ... so injecting an incorrect route into an unsuspecting FMC actually resets the program inside the simulated FMC?! Or is this merely a chance message that isn't intended to appear?

Hoppie

Hardy Heinlin

It doesn't reset, it just rejects the incorrect part of the injection and throws an exception. This is a momentary inconsistency in the FMS as a whole, and the message indicates this momentarily. In the real FMS world there are no add-ons, of course. So this can't happen this way in the real FMS.


|-|ardy

Hardy Heinlin

There are two different errors, independent of each other:


1.

java.lang.NumberFormatException: For input string: "2900ZSPDOBBI332"
   at RadioAtcBasis.situLoadInit(RadioAtcBasis.java:179)
   at Core.unpauseLoader(Core.java:373)
   at NetClientThread.run(NetClientThread.java:136)

This is an incorrect injection (during network triggered situation file loading) into a client PSX and refers to the Qs "VoiceAtc". The first part of this Qs string up to the first semicolon should be an integer. In this erroneous case it reads "2900ZSPDOBBI332" which is not an integer. This is strange as PSX is not able to generate such a text at this position. The Qs "VoiceAtc" stores all variables that are set on Instructor > Situation > Human > Voice-ATC.


2.

java.lang.NumberFormatException: For input string: "294/19"
   at Routes$RteBody.readGlob(Routes.java:4898)


This error is an incorrect injection of an FMC route leg data record. The record contains multiple variables separated by colons. The incorrect injection includes a slash ('294/19') where just one value is allowed. Can you show the content of the route file that has been injected?


|-|ardy

torrence

Just another data point - using BACARS (also vs4.0.4 and Dispatch I've also had this msg recently).  Winds seemed ok and I think route 'looked' ok, so I'd didn't worry about it.  Looks as if the winds are really ok, but maybe the Dispatch route may create the problem?

Cheers,
Torrence
Cheers
Torrence

Hardy Heinlin

Re error #1: "2900ZSPDOBBI332"

Just in case an add-on injected this; there should be a semicolon before the two digits that are before the ICAO codes: "29;00ZSPDOBBI332"

29 is a bitmask that stores the bits for "Talks to us", "Talks to others", LNAV DEP, LNAV CRZ, LNAV ARR.

The next digit refers to the armed Hold scenario.

The next digit refers to the armed go-around scenario.

The next characters are origin and destination: ZSPD OBBI

After that there is the initial CRZ FL.


Cheers,

|-|ardy

Jeroen Hoppenbrouwers

Quote from: Hardy Heinlin on Sun, 22 Apr 2018 00:26
So this can't happen this way in the real FMS.

Going to try that  :-)