Problem With Sim-Avionics

[Ballwatcher]

*** Moved from FAQ sub-forum to main FSUIPC support forum ***

I have a Jetmax 777 system using Sim-Avionics software and use P3D V5.4 and V6. I have 2 PCs networked, the P3D PC and the Avionics PC.  I upgraded the Sim-Avionics 777 flight model from V2.06 to V2.10.  That's all I did.

Now stuff happens never seen before.  When I operate the fuel cut-off switch, the action is recognised in the Sim Avionics software, so fuel can be seen to flow, but nothing happens on the P3D PC and the engines won't start.  Similarly, if I operate the parking brake switch, it is seen to operate on the Avionics PC and Sim-Avionics software but not on the P3D software.  But other controls such as flaps from the same throttle hardware work on both the aeroplane and in the Sim-Avionics.

I have uninstalled an re-installed FSUIPC6 and nothing has changed.  I have uninstalled and reinstalled the sim-avionics software and no change.  I have deleted the 777 from the simobjects file in P3D and reinstalled - no change.

Can you explain the issue here and if so, what I might do to fix it ?  I don't want to do a full uninstall and reinstall of P3D as that's a last resort

Thanks in advance

Edited October 5 by John Dowson
Moved to main support forum

[John Dowson]

20 hours ago, Ballwatcher said:

Can you explain the issue here and if so, what I might do to fix it ?  I don't want to do a full uninstall and reinstall of P3D as that's a last resort

No, I cannot. What has this to do with FSUIPC? If your issue comes from an upgrade of the Sim-Avionics 777 flight model, why don't you raise this issue with them rather than here?

I know nothing about the Sim-Avionics 777. If you have an issue with FSUIPC I can help, but I do not support 3rd party products/add-ons from other developers...
If you have assignments in FSUIPC which aren't working, regardless of which aircraft you are using, then I need to see (attach not paste) your FSUIPC6.ini file (which contains your assignments), and also your FSUIPC6.log file, with appropriate logging activated (i.e. Buttons & Switches and Events (non-axis controls)) that shows what is happening.

 It could be something simple, such as an aircraft name not currently caught by a profile, or possibly a device GUID change that has made your current assignments obsolete. But I can't really comment without seeing your files.

John

[Ballwatcher]

Hi John,

Files attached.  I accept all you say about 3rd party software and I'm not asking you to fix someone else's issue / problem.  My issue is simple.

- Using my throttle quadrant, the parking brake switch is recognised on the avionics computer and in the sim-avionics software.  But in the P3D computer it has no effect and is not recognised.  The parking brake switch is recognised in FSUIPC when I assign that button to parking brake using offsets as I've always done.  So using the buttons and switches tab, I move the button, FSUIPC recognises it, and I assign it to parking brake using the offsets.  

- The same exact issue happens with the fuel cut-off switches, recognised in sim-avionics, recognised in FSUIPC but not in P3D.

Given FSUIPC6 is installed on the P3D computer and maybe clutching at straws I just wondered if there was anything in the P3D / FSUIPC interface which was causing this issue.

Thanks in advance - David

 

FSUIPC6.ini FSUIPC6.log

[John Dowson]

First, your log shows a couple of errors:

Quote

   139609 Exception 20 "DATA_ERROR", Ref 2946, Index param 1 on write SetData for "GENERAL ENG OIL LEAKED PERCENT:1"
   139609 Exception 20 "DATA_ERROR", Ref 2947, Index param 1 on write SetData for "GENERAL ENG OIL LEAKED PERCENT:2"

This type of error is usually caused by a corrupt P3D client - please re-install this component and see if they go away.

6 hours ago, Ballwatcher said:

- Using my throttle quadrant, the parking brake switch is recognised on the avionics computer and in the sim-avionics software.  But in the P3D computer it has no effect and is not recognised.  The parking brake switch is recognised in FSUIPC when I assign that button to parking brake using offsets as I've always done.  So using the buttons and switches tab, I move the button, FSUIPC recognises it, and I assign it to parking brake using the offsets.  

- The same exact issue happens with the fuel cut-off switches, recognised in sim-avionics, recognised in FSUIPC but not in P3D.

Ok, then can you please supply/ayyach a log file showing this issue. Activate logging for Buttons & Switches as well as Events. You can also monitor the offsets you are using. However, note that the offsets you are using are in an area with this description:

Quote

Reserved:   5200-527F = Ferry van Aesch (Asst CEO British Airways Virtual)   5280- 52FF: Andrew McLean: Aerosoft Hardware   5300-53FF: Mark Hastings B777 Systems Simulator   5400-5FFF: Enrico's Project Magenta

i.e. they are reserved for these systems and are handled by them, not FSUIPC. Maybe check the offsets you are using are still valid after the update.

John

[Ballwatcher]

Hi John,

Thanks again for assisting with this -much appreciated.

Regarding problem 1 - I reinstalled and repaired the P3D client file and this seems to have fixed the problem.  Log file 1 shows this.

I cannot attach the second log showing buttons and events as the file size is too big.  But what it does is repeat the following entries multiple times.  I'm hoping this gives you what you need.  Let me know.

Thanks again - David

229969 LogOptions changed, now 60000000 00000001
   230625 Button held, flags=X05, repeat set: bRef=0, Joy=0, Btn=0, (RepeatOk sets 2)
   230625 [Buttons] 20=R0,0,Cx01005418,x01
   230625 Repeating flag set: bRef=0, Joy=0, Btn=0 (RepeatDelayCtr=11)
   230625 IPC Offsets Control: Ctrl=x0100, Length=1, Offset=5418, Param=x1
   230625 Button held, flags=X05, repeat set: bRef=0, Joy=0, Btn=0, (Result 4)
   230625 [Buttons] 20=R0,0,Cx01005418,x01
   230625 Button held, flags=X05, repeat set: bRef=0, Joy=0, Btn=0, (Result 4)
   230625 [Buttons] 20=R0,0,Cx01005418,x01
   230625 Button held, flags=X05, repeat set: bRef=0, Joy=0, Btn=0, (Result 4)
   230625 [Buttons] 20=R0,0,Cx01005418,x01
   230672 Button held, flags=X05, repeat set: bRef=0, Joy=0, Btn=0, (RepeatOk sets 2)
   230672 [Buttons] 20=R0,0,Cx01005418,x01

Log File 1.log

[John Dowson]

Your press assignments are set to repeat - you shouldn't need this as the assignments are just updating an offset (no point in repeating this). So you can maybe change those assignments to a press rather than repeat, but this won't make much of a difference. Other than that, FSUIPC is behaving as expected.

As I said in my previous comment, the offsets you are writing to are NOT controlled by FSUIPC, but are reserved for use by other systems. You need to look into what is using those offsets as it is that that should be sending the appropriate controls. If its the Sim-Avionics update that provoked this issue, I would have thought that the issue lies there somewhere. But you seem to be using offsets reserved for both Mark Hastings B777 Systems Simulator (5300-53FF) and Enrico's Project Magenta (5400-5FFF).
How did you know which offsets to use - which software/document gave you this information? Maybe check that to see if its changed...

[Ballwatcher]

Hi John - once again many thanks.

Thanks for your help with this, at least I've ruled out that there is no issue with FSUIPC causing my troubles and in the process I've learned a fair bit.

Mark Hastings B777 systems simulator is Sim-Avionics.  Mark is the head guy at Sim-Avionics so he will be my next port of call.

Thanks again - David