Version Disagree

[J D ADAM]

Gentlemen   1. Having run PSX  over two screens/computers very successfully, i have now getting a message

"Latest version disagree 10.2 Navblue(cycle1703) "

I have copied PSX server program to the second computer and changed the ip address with no success

2. What is the reason for the standby altimeter not matching the PFD readout though baro set up is matched

3. On very odd occasions the aircraft freezes its position on the ground and will not respond with movement when throttles are advanced. (This usually happens at a holding point) Introducing reverse thrust can sometimes unfreezes this.

Any advice would be appreciated.

Derek Adam NZA

[Hardy Heinlin]

Hi Derek,

how many PSX network instances do you connect?

All instances need to have the same PSX version and the same nav database version.

You can check the versions on every PSX instance on the Instructor's About page.


Regards,

|-|ardy

[cavaricooper]

Derek-

Re. #3- I have occasionally experienced this (with earlier versions, not in the last 6 months). Using the mouse to move the throttles (in the upper EICAS) even just a little, freed them up for me.

Hardy's latest USB revision might obviate the need for this completely....

HTH- C

[Hardy Heinlin]

2. What is the reason for the standby altimeter not matching the PFD readout though baro set up is matched

The standby altimeter has instrument errors which the high-tech EFIS altimeters don't have.

The standby altimeter gets the static pressure directly from the static probe; the EFIS altimeters get filtered, error-corrected data from the air data computers.

Standby altimeter instrument errors are illustrated in some manuals by certain graphs. These errors are simulated in PSX too.

By the way, the standby airspeed indicator has instrument errors as well. Play with the pitch attitude during rollout and you will see.


Regards,

|-|ardy

[J D ADAM]

Thank you Gentlemen for your comments.

Hardy

how many PSX network instances do you connect?

Just the one

All instances need to have the same PSX version and the same nav database version.

The main server computer      Precision Simulator 10.2
The main client  computer       Precision Simulator 10.15

Aerowinx Jar files are the same  16/1/18  6880  kbs

Both computers   "Navigation data by Navblue(cycle 1703

Seems odd that the versions differ.

I have copied the base main server computer files to the main client computer.

The message reads  Latest version disagree 10.2 Navblue(cycle 1703) and obviously no connection takes place.

Your advice would be really appreciated.

Most kind regards and grateful thanks for all you contribute in such an ongoing way,

Derek

[torrence]

Derek,

I'm not expert on the networking stuff, but it's possible that the problem here relates to Hardy's second point:

"All instances need to have the same PSX version and the same nav database version."

It looks like you are running two different PSX versions on your computers. 

Hope this helps.

Cheers,
Torrence

[Hardy Heinlin]

Derek,

how many files starting with the name "Aerowinx..." are in your main server computer's Aerowinx folder?

Are there any with numbers in the file name? E.g.

Aerowinx-1.jar
Aerowinx-2.jar

Such files names may be generated by Microsoft Windows when you try to copy a file over another file of the same name, and the file you want to overwrite will never be overwritten. Windows just adds more and more copies under different, numbered file names.


Cheers,

|-|ardy

[J D ADAM]

Thank you for your rely Hardy.


It is 4am  and could not sleep thinking about my problem so did a lot of unusual investigations.

Because I keep a backup copy on both computers, I found that my shortcut on the main desktop was directing me to the backup copy (old)  duh.

Everything is sweet again.

Thank you for your ongoing support and updates.

Cheers
Derek