SmartRunway, SmartLanding: new addon (SRSL-PSX) v 1.0

[Avi]

Hi Hardy,

Yes, these are the longest messages.

I have no problem if you remove the messages when changing range. I guess you will do Qhnnn="". Right?

Cheers,

[Hardy Heinlin]

Hi Avi,

I think it's not necessary that PSX sends this Q to the network. I would treat this similar to a momentary action switch which self-resets after a certain time without sending the reset to the network. In our case now it would self-reset on the next ND range change. But your add-on too can reset it at any time. Here's my Q layout plan:

text semicolon number semicolon

SHORT RUNWAY;1;

ON 25C;0;

The number is the color code. 0 = green, 1 = amber.


;0;

That's an empty text string. That's the reset command.

What do you think?


Cheers,

|-|ardy

[Avi]

Looks ok.

Thanks,

[samer747]

Hi Avi,

Thanks again for this great add-on, great work. I wanted to ask you if there is a way to increase the volume for the audio callouts, make it louder?

Regards,

[Avi]

Thanks samer747,

First of all, note that some calls, mainly the routine one, are played at 6dB below normal volume level. Check appendix B to see the calls and the volume level.

You can change the normal level by up to 9.9dB by setting a value in LSK 3L on Setting 3/3 page.

Cheers,

[Hardy Heinlin]

Does the real EGPWS take the stopway into account for the length remaining during rollout? Does anybody know? Some runways have a stopway beyond the official runway length, and that's in the database as well. Avi, I can include this variable in the network output if required.


Regards,

|-|ardy


P.S.: Do you need a leading zero for runway numbers below 10?

[Avi]

Hi Hardy,

According to the (old) document I have, stopway are not included in the available runway length. not even for distance remaining calls during RTO so I don't need it.

Runway id in SRSL is 3 chars long. Even runway '12' is runway '12_' (the 3rd char is a space) so I need a leading zero but I can manipulate it myself.

Thanks,

[Hardy Heinlin]

Hi Avi,

OK, so I'll exclude the stopway, and I'll set 3 chars for every ID.


Cheers,

|-|ardy

[Matt Sheil]

Hi AVI, Amazing    What a great add-on

[Matt Sheil]

A little more free
RAAS
reading for those that like a little more information

[Avi]

Thanks Matt,

This document is SRSL-PSX

Cheers,

[Avi]

Hi all,

I have 2 questions for you:

1. Does anyone use the distance offset (to "align" the distance remaining calls to thier outside view)?
2. We all know the next PSX version will include GPS spoofing. I don't know how does it affect the EGPWS (and SRSL).
What should I do about it?
a. SRSL-PSX doesn't work if spoofing is ON (as it doesn't work if EGPWS or GPS are not powered or malfunction is active)? Even if I do it, I will add an option to override it.
b. Generates false calls (which calls? at what altitude?)?

Does anyone who know the real system knows what happens during GPS spoofing?

Thanks,

[Hardy Heinlin]

Hi Avi,

when spoofing happens, the position error is so great (many miles) that this little scenery offset will be completely irrelevant, I think.

In PSX version 10.186, when spoofing is implemented (I hope), PSX will send the erroneous GPS coords to the network. Instead of reading the true aircraft position, your add-on should then read these erroneous GPS coords and use these as its aircraft position reference. There'll be an erroneous GPS altitude as well.


Regards,

|-|ardy

[Mariano]

Hi Avi.

Please check your email.

Best regards,

Mariano

[Hardy Heinlin]

Avi, one more thought:

I just rechecked my EGPWS terrain warning code. It normally uses GPS position, even during spoofing. When GPS fails (unpowered or signal loss) it uses the left IRU position, if that fails it uses the right IRU position, and if that fails the warning system is off. I don't know if the SRSL uses the same logic. But if it does and you're interested: The IRS positions can be read from the network with this Qs:

Qs356="IrsBrgDst"; Mode=ECON; Min=11; Max=2500;

It contains each IRU's bearing and distance from the true position (which you already have).

There is another Qs that contains the passed align time of each IRU; this can be used to check which IRU is operative. Just let me know if you need more details.


Regards,

|-|ardy

[Kurt]

Hi Avi.

Thanks for this great addon - I think I have a bug report.

As soon as I start SRSL-PSX my CPU load increases dramatically and my CPU Fan spools up loud (never had that happening before). Checking the task manager on my main PSX server PC where most of all my applications run i see SRSL-PSX consuming 6% CPU time on my 16(32) core 5950X cpu - this is while the PSX instances consumes between 0.2% and 0.4% cpu time.

It is the same no matter what beta version I use and I tried it on another PC with similar very high CPU usage.

Cheers

[Avi]

Thank you guys,

Hardy,
My question about the visual offset has nothing to do with the spoofing. I wanted to know if someone uses it, or if the calculations are very precise.

Kurt,
I will look into it. From the very begining I used threads that should run for minimum time and be in wait() mode most of the time, but I'll check.

Cheers,

[Avi]

Hi All,

Version b0.4 is up. In this version:

* When working in Main mode, EICAS message "FLAPS" when entering a runway (or short runway) with flaps not in takeoff position, override the "ON XXX" message too early. Now it "waits for its turn".
* sleep() command in the Ground Advisories thread was placed in a wrong place and as a result the CPU spiked to the roof. Fixed.

Kurt, super nice catch. Please inform me it is ok now on your side.

everybody, this update is a MUST.

Download the new version and override the old one.

Cheers,

[Mariano]

Thank you, Avi (and Kurt).

Best regards,

Mariano

[Kurt]

Hi All,

Version b0.4 is up. In this version:

* When working in Main mode, EICAS message "FLAPS" when entering a runway (or short runway) with flaps not in takeoff position, override the "ON XXX" message too early. Now it "waits for its turn".
* sleep() command in the Ground Advisories thread was placed in a wrong place and as a result the CPU spiked to the roof. Fixed.

Kurt, super nice catch. Please inform me it is ok now on your side.

everybody, this upgrade is a MUST.

Download the new version and override the old one.

Cheers,

Perfect - no high CPU usage anymore

Thanks Avi