Recent posts

#1

Accessories / Re: PSXseecon version 3.23 rel...

Last post by kiek - Sun, 26 May 2024 19:17

If you need Nico's software, maybe he even added Qi37 in his system already because Qi37 has been on the PSX list since the release of PSX 10.0.

Indeed it is, but at 5 Hz

#2

Accessories / Re: PSXseecon version 3.23 rel...

Last post by Jeroen Hoppenbrouwers - Sun, 26 May 2024 18:50

I actually replaced the pneumatic-mechanical parts with a servomotor, which is driven by opencockpit servomotor board and controlled by SIOC and PsxSeecon. So, is it possible to solve the lag problem caused by update rate by optimizing scripts?

As far as I can see, yes: SIOC is a programming language and you should be able to enter time-based small increments to an event, maybe even schedule the next event. I am not familiar with the internals of SIOC so somebody else probably has a better suggestion.

Hardy's suggestion to have a higher-rate variable of course also would work. I understood PSXseecon runs at 5 Hz so more than 5 Hz would be a waste.

Personally I still would prefer a SIOC smoother instead of more data per second from PSX. Move processor power use as far away from the server as possible. That lasts longer when your setup grows beyond initial imagination.

#3

Accessories / Re: PSXseecon version 3.23 rel...

Last post by Hardy Heinlin - Sun, 26 May 2024 18:16

With your way that calculator with Qi131, because the Qi131 will only show the IAS at the moment the plugin connects. It won't change with the Alt or QNH changes.

Right. In my last comment I forgot this fact too.

Anyway ... Well, I'm thinking about adding a special IAS Qi for you in the next PSX update. What update rate would be reasonable? 20 Hz, 10 Hz?

Yesterday I discovered a Qi in my code which I introduced 15 years ago:

Qi37="StbyIasError"; Mode=ECON; Min=-1000; Max=1000;

This was intended for use as a "difference" value at a low update rate, which was intended to be added to airspeed data streams that run at higher update rates. But I never implemented any write action to this Qi. Up to the latest PSX version, it always contains "0".

I could use this existing unused Qi37 now for a standby-instrument IAS output. It would include instrument errors and malfunctions. I would keep the name "StbyIasError" for compatibility reasons, but it would be the final IAS value in knots, and no further computations would be required.

If you need Nico's software, maybe he even added Qi37 in his system already because Qi37 has been on the PSX list since the release of PSX 10.0.


Regards,

|-|ardy

#4

Accessories / Re: PSXseecon version 3.23 rel...

Last post by b744erf - Sun, 26 May 2024 18:11

Thank you Hoppie
I actually replaced the pneumatic-mechanical parts with a servomotor, which is driven by opencockpit servomotor board and controlled by SIOC and PsxSeecon. So, is it possible to solve the lag problem caused by update rate by optimizing scripts?

Regards

Jack

#5

Accessories / Re: PSXseecon version 3.23 rel...

Last post by Jeroen Hoppenbrouwers - Sun, 26 May 2024 17:31

Actually no, the data that PSX sends is simply not intended to drive a display directly. Also all PSX clients themselves don't use this data directly to update their display: they interpolate, like they interpolate nearly everything else. Only this way, the data traffic over the network can be kept reasonable.

So if you want to drive something off this data, your "something" needs to interpolate smoothly over time. PSXseecon is not the right spot to do this (in my opinion) because its task is to relay, not to display or control directly (I may be wrong here).

What exactly are you driving (not the final OEM indicator but the electronics)? Does it have any brain? Does it have a microcontroller? Is SIOC the spot to do this?


Hoppie

#6

Accessories / Re: PSXseecon version 3.23 rel...

Last post by b744erf - Sun, 26 May 2024 17:24

Thank you Nico and Hardy.
Actually, before Nico released the new version, I did tried to interface the  indicator by calculating the IAS from TAS (QS121). I used a simplified formula, which may have a big difference when the QNH is far from 1013. I can't find a variable to show the current position QNH, so I can't calculate the IAS precisely. But I did find that the update rate is much better than the Qs483.

With your way that calculator with Qi131, because the Qi131 will only show the IAS at the moment the plugin connects. It won't change with the Alt or QNH changes. So I don't think I can make a good IAS with it.

Right. Seems the only way to figure out is to wait for someday PSX changing the Qs483 update rate.

Here is the link of the video showing my OEM indicator running with PSX and PSXseecon.

https://youtube.com/shorts/wZht_kfmWx4?si=xKW1WAfY7AJWnt0h

Appreciate your help, Nico and Hardy.

Regards
Jack

#7

Hangar 7 / Re: METAR Settings

Last post by B747-400 - Sun, 26 May 2024 15:35

Thanks a lot Hardy, for your important info's! 

BR
Hans

#8

Accessories / Re: PSXseecon version 3.23 rel...

Last post by Hardy Heinlin - Sun, 26 May 2024 15:00

Hello Jack,

I'm sorry, the update rate cannot be changed. The smoothing needs to be programmed on the add-on's software side.

Another option, which also needs to be programmed, would be this:

Qs121="PiBaHeAlTas"; Mode=ECON; Min=9; Max=200;

Get the TAS (the 5th variable after pitch, bank etc.) of Qs121. That is updated at 5 Hz. Whenever you receive an updated IAS from Qi131, in that moment compute the difference between the current TAS and current IAS. This difference varies very slowly with the aircraft's altitude and with the weather conditions. It varies so slowly that the 1 Hz update rate won't make any jumps. Now, for your instrument, just use the "TAS Minus Difference" at the 5 Hz rate.

Can you program this in your interface?

Edit: Please disregard. During high acceleration or deceleration, the difference will also make jumps because the difference also increases when the airspeed increases.



Regards,

|-|ardy

#9

Accessories / Re: PSXseecon version 3.23 rel...

Last post by kiek - Sun, 26 May 2024 14:48

I found that the data updated every 1 second.

FYI: PSXseecon updates information variables 5 times/sec. Hence it must be PSX that updates only once a second at the most according to the PSX documentation.

[The clients need no Internet, and you need not care about it :-)]

#10

Hangar 7 / Re: METAR Settings

Last post by Hardy Heinlin - Sun, 26 May 2024 14:36

Hi Hans,

the server will send all required weather data to the clients.

The clients need no Internet, and you need not care about it :-)

Background info: There are 2 relevant things that PSX synchronizes automatically:

1. The aerodynamic simulation needs weather data for the current aircraft position.
2. The radar simulation and the Instructor's MET map need weather data of the 7 local zones (and planet).

Data #2 get the clients from the server whenever there's a change in the 7 local zones (or planet).
Data #1 compute the clients on their own using data #2

3. Server-only stuff:
When the FMS simulation is loading weather data into the active FMC route, or when the Instructor's Corridor feature is generating a route corridor, the server has scanned the newest two METAR world files stored in the server's weather folder. These actions -- FMS or Corridor -- are only executed in the server. The server then just sends the related CDU page text or corridor text to the clients. Clients don't scan or compute this. They just display the texts (generated and sent by the server). The "sigmets.cache" works in the same way.

If you had to synchronise the weather files in your networked Aerowinx folders, you sure would find an important note in the Aerowinx manual :-) There is no such note as there's no such requirement.


Regards,

|-|ardy