FMS - Invalid entry problem

[mraviator]

I'm in the process of taking the CRJ2 around the world, currently in Asia. So far I've had no problems at all with the FMS. Today I wanted to fly near my home in the US and proceeded to POS INIT for KAUS. But I keep getting INVALID ENTRY. I tried two other nearby airports, and some more US airports farther away, same problem.

 

The only oddity I see is the FMS POS line above the airport entry. It states S-2147483648°-2147. That looks awfully a lot like an overflow (Windows?) error code to me (I'm running Win 7).

 

Now here's the interesting thing. After trying multiple US and Canadian airports, I went back to the last airport on my around-the-world-flight (VQPR), without restarting the sim, and it took the POS INIT without issues. 

 

I'm still running the 1.4.5 (I think) version since the 1.5.1 or whatever is offered gave my problems. 

 

Any insight on this?

 

Thanks!

Edited December 25, 2012 by mraviator

[philipp]

This problem was introduced by X-Plane 10.10 and was solved in CRJ 1.5.2

[mraviator]

Thanks. I will have to wait for that version (or its update) to work for me then.

[mraviator]

This problem was introduced by X-Plane 10.10 and was solved in CRJ 1.5.2

I'm basically in a situation now that no matter where I load the CRJ2, I cannot initialize my position on the FMS. It will not accept any airport input. Because I can't do that step, I do not get the full avionics and therefore cannot fly properly.

 

Is there any way to reset the FMS for this condition? Is there any workaround for this issue? Right now the FMS is holding up my ability to fly the aircraft.

 

Thanks. 

[Cameron]

I'm basically in a situation now that no matter where I load the CRJ2, I cannot initialize my position on the FMS. It will not accept any airport input. Because I can't do that step, I do not get the full avionics and therefore cannot fly properly.

 

Is there any way to reset the FMS for this condition? Is there any workaround for this issue? Right now the FMS is holding up my ability to fly the aircraft.

 

Thanks. 

I'm not quite sure how this could be happening for you. I've just loaded 1.4.5 in the latest version of 10.2 even and I can POS INIT each and every time. You're saying you can't even get this to work on your first aircraft load? I don't even have a complaint from anyone about this until here, for that matter.

[mraviator]

That's correct. No matter if I load CRJ2 directly or come from a different airport or different airport and aircraft, I can't seem to pos init the FMS. Is this a possible Nav database issue? I did update that weeks ago, but cannot say for sure if that's when it started or not. I checked, however, to make sure the airports I try to pos init at are in the Navigraph database, and they all are there. 

[cessna729]

That's correct. No matter if I load CRJ2 directly or come from a different airport or different airport and aircraft, I can't seem to pos init the FMS. Is this a possible Nav database issue? I did update that weeks ago, but cannot say for sure if that's when it started or not. I checked, however, to make sure the airports I try to pos init at are in the Navigraph database, and they all are there. 

Check PM!

cessna729.

[Cameron]

I'll also continue to investigate this.

[mraviator]

Cessna729's advice of deleting the four files in the CRJAvionics cache folder and letting them rebuild did the trick. I have to do it almost every time I fly, however.

Sent from my Galaxy Nexus using Tapatalk 2

[philipp]

You are mixing two different issues here:

 

1. The initial position reads a nonsense value, like minus a million degrees. That is caused by a change to how X-Plane initializes values when starting, it changed in 10.10 and was subsequently solved with a CRJ update, in 1.5.x

 

2. The initial position cannot be read from the database (you enter an airport and it shows up as "INVALID ENTRY") then you have a problem with either faulty navdata, incorrect installation of navdata, or a broken navdata cache. The latter can be fixed by deleting the four files in CRJ-200/plugins/CRJAvionics/cache/. The former can be fixed by carefully reviewing the navdata installation process, comparing to how it looks when the CRJ is clean installed.

 

Philipp

[mraviator]

Thanks Philipp. I might go back to the original install and compare on next database update. Thanks for the additional insight!

Sent from my Galaxy Nexus using Tapatalk 2