N1 Hold write inop

[pcssundahl]

Hi Pete thanks again for the support,

 

i'm writing to 0x07f4 the logging option shows a good write of 1 but no N1 hold 

Not sure if this is a known issue or not it seems strange to me i have all other autopilot functions working well.

 

Much Gratitude!!!!

[Pete Dowson]

i'm writing to 0x07f4 the logging option shows a good write of 1 but no N1 hold 

Not sure if this is a known issue or not it seems strange to me i have all other autopilot functions working well.

 

All it will be doing is sending your request on to FS. Whether it does anything or not probably dependsupon the aircraft in use. Are you setting 07FA too (the RPM value to be held)?

 

Can you please state the version number of FSUIPC you are using? This FSX option wasn't added till 4.281.

 

Pete

[pcssundahl]

fsuipc version 4.928

I can read the offset just fine but when I write to the offset 07F4 no error returned and no change in the logging option(I was mistaken in the earlier post,sorry about that) it is like the write never happened.

 

to answer the other question no I am not setting the value at 07FA. but I set the value with the mouse in the aircraft(default 737)

I wasn't really wanting to set the value just be able to hit the n1 hold/sync. I was planning on implementing the numerical setting for the autopilot at a later time.

 

Thanks again Pete.

 

ps I am using FSUIPC4929c dll that you sent me to help implementing the pushback for a nonregistered version(thanks for that by the way) note- the version I'm referring to in these posts is registered with wideclient but Im writing to fsuipc not wideclient

[Pete Dowson]

fsuipc version 4.928

 

Version 4.928 isn't supportable I'm afraid. The current version is 4.931. Please update.

 

I can read the offset just fine but when I write to the offset 07F4 no error returned and no change in the logging option(I was mistaken in the earlier post,sorry about that) it is like the write never happened.

 

If using IPC write logging no entry appears when you think you werite to 07F4 then I'm sorry but you are not writing to 07F4.

 

Perhaps you should show me the log rather than report what you think it is telling you? Please?

 

Pete

[pcssundahl]

Ok I updated FSUIPC to ver 4.931

and still n1 hld still not working.

here is my code "minus the error checking" and log:

OffsetHex = 0x07f4

offset = [(OffsetHex, 'd'), (OffsetHex, 'd')]
Data = pyuipc.prepare_data(offset, True)

try:
        pyuipc.open(0)

 try:
        x = pyuipc.read(Data)

    pyuipc.close()
    print x

this returns [0, 0] when n1 is off " using the mouse" and [1, 1] when on

 

when write:

try:
        pyuipc.open(0)

try:
        pyuipc.write(Data, [1, 1])

    pyuipc.close()

 

nothing happens in fsx and the log file contains this:

 

  1282344 Monitor IPC:07F4 (U32) = 0

  1525766 Monitor IPC:07F4 (S32) = 0

I tried signed and unsigned both just to be sure

 

Not sure what I'm doing wrong.

 

As ALLWAYS your help and support of your product is much appreciated Pete

[Pete Dowson]

nothing happens in fsx and the log file contains this:

 

  1282344 Monitor IPC:07F4 (U32) = 0

  1525766 Monitor IPC:07F4 (S32) = 0

 

Where's the IPC write logging? If you have that enabled and no writes are logged then no writes have actually occurred! (I seem to remember I already told you this?)

 

Here, I've just tried it.  This is with the default FSX 738. I started the engines, engaged A/T and A/P, then wrote a value for the N1% hold value, and then set the RPM hold. Here are the log entries for the latter two actions:

 

  1400405 WRITE0[6204]  07FA,   2 bytes: 00 30                                            .0

  1413899 *** EVENT: Cntrl= 65900 (0x0001016c), Param= 75 (0x0000004b) AP_N1_REF_SET

  1457034 WRITE0[6204]  07F4,   4 bytes: 01 00 00 00                                      ....

  1457034 *** EVENT: Cntrl= 66711 (0x00010497), Param= 0 (0x00000000) AP_N1_HOLD

  1457158 Monitor IPC:07F4 (U32) = 1

  1457158 SimRead: 07F4="AUTOPILOT RPM HOLD"

            INT32: 1 (0x00000001)

 

Notice I wrote 12288 to 07FA to set 75% Here I'm not actually sure whether FSX wants the 0-100% value of the 0-16384 values. Perhaps you can tell me when you get it sorted. I don't know anything about RPM holding.

 

You'll see, in any case, that setting the N1/RPM hold at 07F4 is confirmed by SimConnect.

 

The logging I an using here is ipc Write and Events (non-axis), and I am monitoring offset 07F4.

 

If I try all this without starting the engines and enabling the AT and AP I may not get the hold set. I don't know -- I haven't tried all combinations, so I'm not sure, but it makes sense that you need to have everything set correctly for the Hold to take effect.

 

If you still can't figure it out, and can't use the logging I keep suggesting, I think you need "pyuipc" help. Try writing to 07F4 using a Lua plug-in or using FSInterrogate2 just to see it is okay. I think then that something may be wrong with the pyuipc code, but I'm afraid I can't help with that as I am totally unfamiliar with it.

 

Pete

[pcssundahl]

Sorry for the delay in my response.  Life sometimes slows me down a little.

Pete,

You are correct about the write not being generated that's why I couldn't find it.

but I've contacted the PYUIPC publisher and it seems to be a bug in that module.  Which he has fixed and sent a module .

I just haven't tried it yet.  Has to do with a module not converting the U32 to C correctly (if I understood correctly).

 

Thanks for the write logging example it helped me compare what I was looking at to confirm the write wasn't happening.

 I will respond with my results when I try the new module. After I respond to the pyuipc publisher with my results

 

Thanks a million Pete

 

Pete