[prev in list] [next in list] [prev in thread] [next in thread] 

List:       flightgear-devel
Subject:    Re: [Flightgear-devel] FG1000 PFD errors
From:       Stuart Buchanan <stuart13 () gmail ! com>
Date:       2022-04-19 16:00:38
Message-ID: CAP3ntytGDhEo3L_UVweHZ05D5zgqY1-AT=hQ7spVO3VTUNuaJA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hi Wayne,

On Mon, 18 Apr 2022 at 23:26, Wayne Bragg wrote:

> The MFD is working correctly. I pulled new next flightgear, simgear and
> fgdata and recompiled and I still have this issue.
> 
> 
> 
> The c172p or sp haves not had any changes made to them in quite awhile as
> far as I know.
> 
> 
> 
> Do you have any idea what might be wrong?
> 

I've just checked the c182t, and it's working normally, so I suspect the
problem is in the c172sp or something specific to your configuration.

You're right about the log lines.  The 404 is just a failure to pick up one
of the tiles for the MFD map display.  I think the specific problem is
flagged by these log lines, which is causing Emesary to stop processing
messages to the PFD recipient:

   37.98 [INFO]:nasal      string index 3 out of bounds (size: 3)

   37.98 [INFO]:nasal
d:/FlightGearBuild/install/flightgear/fgdata/Aircraft/Instruments-3d/FG1000/Nasal/MFDPages/PFDInstruments/PFDInstruments.nas


   37.98 [INFO]:nasal      956

That code (PFDInstruments.nas line 956) is processing transponder codes for
display, and the problem appears to be that the transponder code ends up a
3 character string rather than a 4 character string as it should.

Could you trace out the code variable both before and after it is processed
by the sprintf() calls on lines 930-934.  My guess is that there's some
(valid) transponder
value that we've simply not captured properly.

Thanks,

-Stuart


[Attachment #5 (text/html)]

<div dir="ltr"><div dir="ltr">Hi Wayne,<br></div><div><br></div><div>On Mon, 18 Apr \
2022 at 23:26, Wayne Bragg wrote:<br><div class="gmail_quote"><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;" \
lang="EN-US"><div><p class="MsoNormal">  The MFD is working correctly. I pulled new \
next flightgear, simgear and fgdata and recompiled and I still have this issue.</p><p \
class="MsoNormal">  </p><p class="MsoNormal">The c172p or sp haves not had any \
changes made to them in quite awhile as far as I know.</p><p class="MsoNormal">  \
</p><p class="MsoNormal">Do you have any idea what might be \
wrong?</p></div></div></blockquote><div><br></div><div>I&#39;ve just checked the \
c182t, and it&#39;s working normally, so I suspect the problem is in the c172sp or \
something specific to your configuration.<br></div><div><br></div><div>You&#39;re \
right about the log lines.   The 404 is just a failure to pick up one of the tiles \
for the MFD map display.   I think the specific problem is flagged by these log \
lines, which is causing Emesary to stop processing messages to the PFD \
recipient:</div><div><br></div><div><p class="MsoNormal">     37.98 [INFO]:nasal      \
string index 3 out of bounds (size: 3)</p><p class="MsoNormal">     37.98 \
[INFO]:nasal           \
d:/FlightGearBuild/install/flightgear/fgdata/Aircraft/Instruments-3d/FG1000/Nasal/MFDPages/PFDInstruments/PFDInstruments.nas</p><p \
class="MsoNormal">     37.98 [INFO]:nasal           956</p></div><div><br></div>That \
code (PFDInstruments.nas line 956) is processing transponder codes for display, and \
the problem appears to be that the transponder code ends up a 3 character string \
rather than a 4 character string as it should.</div><div \
class="gmail_quote"><br></div><div class="gmail_quote">Could you trace out the code \
variable both before and after it is processed by the sprintf() calls on lines \
930-934.   My guess is that there&#39;s some (valid) transponder</div><div \
class="gmail_quote">value that we&#39;ve simply not captured properly.</div><div \
class="gmail_quote"><br></div><div class="gmail_quote">Thanks,<br></div><div \
class="gmail_quote"><br></div><div class="gmail_quote">-Stuart<br></div></div> </div>





_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


[prev in list] [next in list] [prev in thread] [next in thread]