FSUIPC 7 PayloadServices and FlyByWire A32NX Project

[Jer029]

I've been using FSUIPC and Paul Henty's Payload services for some time.  Recently it appears that FBW is making changes to their payload handling.  Here's the thread that discusses the changes they've made, and that appears to have rendered the current FSUIPC7 and PayloadServices to no longer be able to calculate the total payload weight.  Ideally, it would be nice to still access the payload data from the A32nx aircraft.

Fligt details sampling broken · Issue #5891 · flybywiresim/a32nx (github.com)

 

Thanks,

jr

[John Dowson]

I'm not sure I fully understand the issue. Reading that link, it just seems that the index numbers have changed for the various weights. FSUIPC7 holds indices 1-61 of the PAYLOAD STATION WEIGHT simvar, so all the weights you need should be in the offsets area to do the calculation. Or is this something that the PayloadService does? If so, maybe this is more of a question for @Paul Hentyand should be moved to the .Net dll Client sub-forum?

John

[Jer029]

Thanks John, perhaps I put it in the wrong forum, as I think it might be specific to Payloadservices by Paul Henty.  All I know is that the payloadservices data is not readable with the a32NX project but still works with other MSFS/fs2020 aircraft - specifically PayloadWeightLbs.  I suppose I can rewrite the code to no longer use PayloadServices, but it would be sad to have to workaround just the specific model.  It would be nice if the model could preserve the data in locations used by FSUIPC/Payloadservices and still accomplish their more complex handling of payload.

 

jr

[Paul Henty]

The PayloadServices class just uses the normal FSUIPC payload station offsets (starting at 0x1400). If FSUIPC cannot get the information then PayloadService will also not see it.

Paul

[Jer029]

This was the information from the a32NX guys.  If they're using station indexes 1-8 for all payload, should not the FSUIPC/payloadservice continue to display this data.  I'm not sure what they changed that caused the failure to read values.  Shouldn't offset 0x13FC display the count of payload stations to obtain values from?

 

That is because we have split the payload stations from Front/Rear Pax and Front/Rear Bag to a much more detailed loading model. There is also an update coming soon which will remove the Pilot and Co-pilot stations as these values should ideally be considered as a part of the operating empty weight. The simvars remain same, the indexes have changed, not sure about how that affects the offsets. For pax, the indexes are 1,2,3,4

👍1

 

 

[John Dowson]

I have just taken a look at what the offsets hold for both the stock A320 and the FBS A320 (development).
This is what I see in the offsets for the stock A320:

Quote

  440969 Monitor IPC:13FC (S32) = 6
   440985 Monitor IPC:1420 (AsciiZ) = [16]"TT:MENU.PAYLOAD."
   441016 Monitor IPC:1430 (FLT64) = 170.0000
   441063 Monitor IPC:1450 (AsciiZ) = [16]"TT:MENU.PAYLOAD."
   554985 Monitor IPC:1460 (FLT64) = 6115.0000
   554985 Monitor IPC:1480 (AsciiZ) = [16]"TT:MENU.PAYLOAD."
   555032 Monitor IPC:1490 (FLT64) = 3505.0000
   555063 Monitor IPC:14B0 (AsciiZ) = [16]"TT:MENU.PAYLOAD."
   647829 Monitor IPC:14C0 (FLT64) = 4000.0000
   647844 Monitor IPC:14E0 (AsciiZ) = [16]"TT:MENU.PAYLOAD."
   647875 Monitor IPC:14F0 (FLT64) = 6310.0000
   647922 Monitor IPC:1510 (AsciiZ) = [16]"TT:MENU.PAYLOAD."
   729110 Monitor IPC:1520 (FLT64) = 0.0000
   729125 Monitor IPC:1540 (AsciiZ) = [0]""
   729157 Monitor IPC:1550 (FLT64) = 0.0000
   729204 Monitor IPC:1570 (AsciiZ) = [0]""
...

The strings are pretty useless as they are the internationalized version which has been truncated. I will make a note and look into correcting these.
There are 6 payloads provided, although the final one is 0.

For the FBW A320 (development) I see the following:

Quote

  1593422 Monitor IPC:13FC (S32) = 10
  1593438 Monitor IPC:1420 (AsciiZ) = [5]"PILOT"
  1593438 Monitor IPC:1430 (FLT64) = 0.0000
  1593485 Monitor IPC:1450 (AsciiZ) = [13]"FIRST OFFICER"
  1665219 Monitor IPC:1460 (FLT64) = 0.0000
  1665235 Monitor IPC:1480 (AsciiZ) = [16]"ECONOMY ROWS 1-6"
  1665235 Monitor IPC:1490 (FLT64) = 0.0000
  1665282 Monitor IPC:14B0 (AsciiZ) = [16]"ECONOMY ROWS 7-1"
  1749141 Monitor IPC:14C0 (FLT64) = 0.0000
  1749141 Monitor IPC:14E0 (AsciiZ) = [16]"ECONOMY ROWS 14-"
  1749141 Monitor IPC:14F0 (FLT64) = 0.0000
  1749141 Monitor IPC:1510 (AsciiZ) = [16]"ECONOMY ROWS 22-"
  1814063 Monitor IPC:1520 (FLT64) = 0.0000
  1814063 Monitor IPC:1540 (AsciiZ) = [16]"FWD BAGGAGE/CONT"
  1814063 Monitor IPC:1550 (FLT64) = 0.0000
  1814063 Monitor IPC:1570 (AsciiZ) = [16]"AFT CONTAINER (m"
  1867500 Monitor IPC:1580 (FLT64) = 0.0000
  1867500 Monitor IPC:15A0 (AsciiZ) = [16]"AFT BAGGAGE (max"
  1867516 Monitor IPC:15B0 (FLT64) = 0.0000
  1867516 Monitor IPC:15D0 (AsciiZ) = [16]"AFT BULK/LOOSE ("
  1913782 Monitor IPC:15E0 (FLT64) = 0.0000
  1913782 Monitor IPC:1600 (AsciiZ) = [0]""
  1913782 Monitor IPC:1610 (FLT64) = 0.0000
  1913782 Monitor IPC:1630 (AsciiZ) = [0]""
...

So it is providing 10 payload weights, but they are all 0.

You really need to raise this with the FBW team.

John

Edited September 28, 2021 by John Dowson
typo corrected

[Jer029]

Thanks John,  I've noted your post on the FBW forum where this is being discussed.  I've done all I can with this on my end and had written off FBW aircraft for our Econ module where the payload data is vital - or until I could try to change the code of our ACARS program to try to pick up the missing values outside of FSUIPC and PayloadServices. 

I'll watch that thread on FBW forum for any resolution.  It would seem to me that the problem resides with the FBW team rather than FSUIPC because FSUIPC continues to work with other MSFS aircraft - and it did previously with the FBW A320 until a recent update.  Hopefully they can make their modifications without losing the data posted to the standard offsets expected by other addons.

Thanks again for looking into this with the FBW team.

 

jr

[John Dowson]

24 minutes ago, Jer029 said:

It would seem to me that the problem resides with the FBW team rather than FSUIPC because FSUIPC continues to work with other MSFS aircraft - and it did previously with the FBW A320 until a recent update.  Hopefully they can make their modifications without losing the data posted to the standard offsets expected by other addons.

Yes - it seems to me that the problem isn't that they have changed which weight is in each index, which isn't an actual issue, but that they are not actually updating the indexed simvar PAYLOAD STATION WEIGHT with the correct values/weights, which is why the FSUIPC offsets are reporting 0 for each of the offsets associated/mapped  to  this simvar.

John