Overspeed and Stall Reading

[cellular55]

Hi Pete,

 

I'm trying to read the offsets 36D and 36C to track an overspeed or stall event, but it seems, also reading your documentation,  that these offsets could not provide the right values (and effectively this is what happens to my program unable to intercept these kinds of event).

 

Is it possible to have a sort of workaround for this?

 

I think to use the offset 2c4 for the Overspeed (if the IAS is higher of the value red in this offset), but I do not have any idea about how to track a stall.

 

Thanks and best regards

 

Joe

 

 

[Pete Dowson]

I'm trying to read the offsets 36D and 36C to track an overspeed or stall event, but it seems, also reading your documentation,  that these offsets could not provide the right values (and effectively this is what happens to my program unable to intercept these kinds of event).

Is it possible to have a sort of workaround for this?

 

Sorry, but there's not enough information here for me to even guess. What simulator is this with, and what version of FSUIPC? What documentation says these offsets don't provide the right values? What does it say they provide if not right?

 

I can check things here, but I need a little bit more information, please.

 

Pete

[Pete Dowson]

I can check things here, but I need a little bit more information, please.

 

I had a little time to spare so I checked those offsets both in FS9 and in FSX with the current versions of FSUIPC3 and FSUIPC4, and they both work perfectly.

 

Regards

Pete

[cellular55]

Hi Pete,

 

sorry to have forgot the details useful for your support.

 

I use FSX/SP2 and FSUIPC 4.92.

 

I was referring to the following content of the offset documentation:

 

036C 1 Stall warning (0=no, 1=stall) ?-SimC No

036D 1 Overspeed warning (0=no, 1=overspeed) ?-SimC No

 

where in the legend of the documentation is stated that for the offsets marked with ?-SimC those are 'Mapped to SimConnect variables, but validity unknown. Needs checking and

feedback please'.

 

So I assumed that the result I was obtaining was wrong. After your test I will check again my code and will let you know about the result.

 

Thanks

 

Joe

[Pete Dowson]

where in the legend of the documentation is stated that for the offsets marked with ?-SimC those are 'Mapped to SimConnect variables, but validity unknown. Needs checking and

feedback please'.

 

Ah, I see. Yes, there are a lot of those, mainly because I've never had time to go through checking them all myself, and not enough folks actually provide feedback. They are gradually being filled in as "OK" instead --- I've just done so here for those two after checking them.

 

 

So I assumed that the result I was obtaining was wrong. After your test I will check again my code and will let you know about the result.

 

Okay. You know there are two easy ways to check offsets yourself?

 

1. Use the logging "monitor" feature on the right side of the FSUIPC  logging tab. Just enter the offsets and their type (UB in this case) and have them displayed on screen, or just in the Log. If you put FSX into Windowed mode and enable the Console Log you can see the offsets being read and changed in real time.

 

2. Use the FSInterrograte utility. This is more useful when there are a lot of things to be checked, or you need some of them converting into normal units.

 

Regards

Pete