User defined offsets

[bpollock]

I would like to set a user defined offset, say, 66C0 to 1 or ON when offset 02B4 (ground speed) is greater than 4711841 (135 knots). This way I can monitor 66C0 in PMSounds to play the nrotate.wav file...is this possible?

[Pete Dowson]

I would like to set a user defined offset, say, 66C0 to 1 or ON when offset 02B4 (ground speed) is greater than 4711841 (135 knots). This way I can monitor 66C0 in PMSounds to play the nrotate.wav file...is this possible?

Yes. 66C0-66FF are available for any private use, as needed. I don't allocate those to any add-on or FS function.

Regards

Pete

[bpollock]

ok...thanks for the response, but I guess the real question is how? What is the exact code to put in the fsuipc.ini file...or is it not that simple?

[Pete Dowson]

ok...thanks for the response, but I guess the real question is how? What is the exact code to put in the fsuipc.ini file...or is it not that simple?

Ah, you want to do it all in FSUIPC? It isn't designed for such programming. FSUIPC is the conduit for other programs, that is its prime purpose.

You can have conditions on button actions or keyboard actions, and you can even make "virtual" buttons operate when other buttons or keys are used.

But there is no programming facility, other than the regular one of you writing a program, to scan offsets for you and take actions.

You can easily do what you want in pmSystems logics. Do you use that? Else, isn't there an offset condition test facility in pmSounds? How were you going to test a bit in 66C0 in any case? If you can do that, can't you compare the IAS offset with a value directly?

Regards

Pete

[bpollock]

Yes, I can scan for 02b4 in the soundlist.cfg file, except the value changes so quickly that if PMSounds isin't scanning at that very millisecond, it passes right by it....it works intermitteintly, but not reliably..oh well...i guess i will try to find an alternative....thanks for your help

[Pete Dowson]

Yes, I can scan for 02b4 in the soundlist.cfg file, except the value changes so quickly that if PMSounds isin't scanning at that very millisecond, it passes right by it....it works intermitteintly, but not reliably..oh well...i guess i will try to find an alternative....thanks for your help

I wasn't really thinking of checking for equality! Even FSUIPC itself couldn't do that -- the values in FS are floating point, so you always check for "within a range" or "nearly".

Can pmSounds not simply scan for "greater than", or would that make it repeat the announcement all the time? If so can it check for a range?

Either way I've found (with my now discontinued Esounds package) that you need to check for a LOWER value than the announced value because of the time lag.

Provided you'd set and confirm your V-speeds on the CDU I thought PM did say "V1""rotate" at the right times anyway. Isn't that coming from pmSounds? I'm using the whole suite, mind, pmSounds, pmSystems, MCP, GC, CDU, RCDU. Maybe it's something else?

Try asking in the PM Forums on http://www.mycockpit.org/forums

Regards

Pete

[bpollock]

I will see if it can scan a range...thanks for the suggestion. And no, I'm not using the whole suite. From what I understand, PMSounds works perfectly with their gauges, however, i simply want to use it with defualt fsx aircraft. Thanks for all your help.