PSXseecon version 3.23 released

[FlyItLikeYouStoleIt]

hPa and baroMode. Thanks.

[Hardy Heinlin]

Together with a logged Qs448 string possibly yes.

Here's an example:

Qs448=R-1;3530;1;101693;-1;1;1;2310110000001c

The last section "2310110000001c" is a sequence of single characters where each character indicates a specific mode. For most of them it's just "on" or "off" (1 or 0).


Regards,

|-|ardy

[kiek]

Released version 3.43

Added 4 SIOC variables (5685 .. 5688):

Qs448, EfisActLBaro        , 5686,            , Qcode value
Qs448, EfisActLhPa         , 5685,            , Qcode value
Qs449, EfisActRBaro        , 5688,            , Qcode value
Qs449, EfisActRhPa         , 5687,            , Qcode value

[FlyItLikeYouStoleIt]

Thanks but you seem to be outputting mda and minsMode (fields 2 and 3) from the Qs strings rather than hpa and Baro (fields 4 and 5).

Also I am puzzled at the lag with which the mda field changes. Watching with the IOCP console in Sioc it lags almost 2 seconds behind changes in the sim, even though the Qs is outputted by PSX "instantaneously". The minsMode field changes seem to change "instantly". Is this something you can look at for the hpa field when you implement it?

[kiek]

Sorry, my mistake. Now fixed. Re-download version 3.43 pls.

About your delay, PSXseecon runs at 20Hz. So the QS variables are written to SIOC at that pace.

Nico

[Hardy Heinlin]

If the delay is just 2 seconds I wouldn't care. Most symbols and indications on the real 744 EFIS/EICAS incorporate delays of one or more seconds. These delays in your indication hardware just add to the realism :-)

[FlyItLikeYouStoleIt]

Kiek: Thank you. I can now capture those variables.

Hardy: well the hpa reading on the PFD reacts pretty quickly to the baro knob and this is what I am trying to emulate!

Kiek: Have a look at these two videos:

The first compares Heading and Altitude performance on the MCP with hpa on the EFIS. All three variables use the same pipeline from PSX to the hardware: PSXSeeCon to SIOC to FSUIPC to Mobiflight

A.mp4

The second compares hpa on my EFIS with the PSX PFD display. The hpa on the PFD display reacts instantly.

B.mp4

I could show you a third video if necessary of the IOCP console from SIOC reacting equally sluggishly to hpa changes. This indicates that the response delay is already evident in SIOC. It is interesting that the Baro mode field from Qs448 reacts instantly in SIOC to changes, entirely consistent with PSXSeecon's 20Hz update rate. It is only the hpa field from the same Qs that reacts sluggishly, more like 0.5Hz!

Kiek - could you have a look at this, something is amiss. All you need to test it is PSX / PSXSeeCon / SIOC and monitor what is going on in SIOC.

[Hardy Heinlin]

When you simulate the 744, you could actually cover your hardware's HPA display as the 744 has no such display on its glareshield panels :-) 744 pilots look at their onside PFD when changing the onside EFIS baro.

[FlyItLikeYouStoleIt]

When you simulate the 744, you could actually cover your hardware's HPA display as the 744 has no such display on its glareshield panels :-) 744 pilots look at their onside PFD when changing the onside EFIS baro.

I know!

[kiek]

Kiek - could you have a look at this, something is amiss. All you need to test it is PSX / PSXSeeCon / SIOC and monitor what is going on in SIOC.

I'm sorry, but I no longer have any hardware and I've lost my detailed knowledge about how to size and position the PSX windows — it's been too long since I last used PSX.

However, you can test this yourself. In the PSXseecon.cfg file, you have these variables available:

MONITOR_PSX_IN_NONQ=0 
MONITOR_PSX_IN_Qh=0 
MONITOR_PSX_IN_Qi=0 
MONITOR_PSX_IN_Qs=0 
MONITOR_PSX_OUT=0 
MONITOR_SIOC_IN=1 
MONITOR_SIOC_OUT=1 

You can check the Log.txt to see the data that PSXseecon sends to and receives from SIOC.

Another point: both fields of QS448 are handled identically — they go through the same processing. Could it be that the hPa field is not updated by PSX at the same rate as the baro field in the Qs message from PSX?

Also, make sure that the rotary changes from your hardware are picked up immediately.

Finally, PSXseecon is a mature product — several cockpits have been built using it. It's not rocket science; it simply passes data back and forth. It's very unlikely that there is a problem in PSXseecon itself.

[FlyItLikeYouStoleIt]

I'm sorry, but I no longer have any hardware and I've lost my detailed knowledge about how to size and position the PSX windows — it's been too long since I last used PSX.

However, you can test this yourself. In the PSXseecon.cfg file, you have these variables available:

MONITOR_PSX_IN_NONQ=0 
MONITOR_PSX_IN_Qh=0 
MONITOR_PSX_IN_Qi=0 
MONITOR_PSX_IN_Qs=0 
MONITOR_PSX_OUT=0 
MONITOR_SIOC_IN=1 
MONITOR_SIOC_OUT=1 

You can check the Log.txt to see the data that PSXseecon sends to and receives from SIOC.

Another point: both fields of QS448 are handled identically — they go through the same processing. Could it be that the hPa field is not updated by PSX at the same rate as the baro field in the Qs message from PSX?

Also, make sure that the rotary changes from your hardware are picked up immediately.

Finally, PSXseecon is a mature product — several cockpits have been built using it. It's not rocket science; it simply passes data back and forth. It's very unlikely that there is a problem in PSXseecon itself.

I'll have a look, but in answer to your questions, the rotary changes from my hardware are picked up immediately (evidenced by instant changes on the PSX PFD) and PSX updates the hpa in the Qs instantly (as evidenced by monitoring the raw output from port 10747).

[FlyItLikeYouStoleIt]

Solved.

Entirely my fault. Apologies and thank you for your time and forbearance!

I had used 5686 "EfisActLBaro" and 5687 "EfisActRhPa" instead of both pointing to the L side, should have been 5685 "EfisActLhPa". So the variable was only updating when the virtual FO updated the R baro.

[Hardy Heinlin]

So the variable was only updating when the virtual FO updated the R baro.

Actually quite useful; so you see what your F/O is doing :-)

[AJStubbsy]

Solved.

Entirely my fault. Apologies and thank you for your time and forbearance!

I had used 5686 "EfisActLBaro" and 5687 "EfisActRhPa" instead of both pointing to the L side, should have been 5685 "EfisActLhPa". So the variable was only updating when the virtual FO updated the R baro.

@FlyItLikeYouStoleIt, did you have to do anything to get those inputs 'EfisActLBaro' and 'EfisActRhPa'. I'm trying to assign inputs to the EFIS control panel but I don't see those switches in the list.

[FlyItLikeYouStoleIt]

The Winwing EFIS? How are you going about it?

I used PSXSeecon which connects PSX to SIOC.

I then wrote a bit of SIOC code which exports the PSX variables I am after to empty FSUIPC offsets. You need a version of MSFS running for this. Then Mobiflight can read FSUIPC offsets, and can write to the EFIS.