My bad, I had a typo, it works now. Thanks. Good job.
Ok good news.
Several things here:
The message is not dependent of the GPS. The GPS just displays it. Itās problem in the aircraft design maybe. They use the GNS430 to display engine messages. Iām not sure that there is such a possibility in the real life. The GPS messages should be related to GPS only (as described in the documentation). Maybe a true pilot can confirm that ?
The small issue with startup screen when setting master on. I will correct that. Same issue in the M20R. Now itās strange that the master switch gives power to the GPS. Maybe a problem in the aircraft design again? In any case, I will make a workaround. This is not a blocking issue.
The GNS430 Mod takes more than 30 seconds to switch on when used alone. This is because it must check if there is a GNS530 in the cockpit in order to invalide its own maps if this is the case (MSFS bug that limits the total number of maps to 4 in the same aircraft with CTD if more than 4).
2 Likes
If this was a reply to my comment, all of the options i mentioned are settable in the mod as well as the real unit. I believe the real one has an internal battery that remembers the settings from one usage to the next. This could be simulated through a config file.
yep, that was my question. Iām very new to the 530, to gps for that matter. When I was flying before, the only GPS I had was a small Garmin unit I bought that you had to enter the locations by hand, it didnāt have a database, haha. I just started flying again a few weeks ago, and one of the planes Iām renting has a 530 in it, and Iām still learning how to use it. Iāve got the basic functions down, but Iāve got a long way to go.
1 Like
Added in the todo list if faisable. But need to verify the real unit behavior.
Now the MOD is possibly used by several aircraft but there is only one MOD so there should be a config for each aircraft using it.
Not sure how the javascript is running here, havenāt had time to experiment with mods, but in node for example:
const fs = require(āfsā)
fs.writeFileSync(āsettings.configā, ā{ āsetting1ā: āvalue 1ā, āsetting2ā: āvalue2ā }ā);
Thank you, appreciate it.
I have never used a real one, but assuming battery saves the data based on this in the manual, page 16-5. When I used to fly, i had a portable Garmin, think it was a GPS 95 maybe, and iām pretty sure it saved all of its settings. Been a long time through.
The Real Garmin can save things (like Flight Plans) ā¦ but in MSFS, everything is run in a Sandbox, and from the sandbox, I donāt think there is any way to write anything back to the PCās file systemā¦ (that Asobo allows you to do)
Another function Missing from the SDK !!!
After a fast analysis, I think this is a bug in the sim.
There is a fmissing file in the panel directory of some aircrafts: panel.xml.
This file defines some alert messages. Since itās missing, I think that the sim is using one of another aircraft from the virtual file system. Probably the voltage value for the alert is not correct (24V instead of 12V). Same issue with some other piston engine aircrafts.
This could be corrected in 2 ways: writting a mod for these aircrafts and adding the missing file with correct values (which ones?).
I could also disable these messages in the MOD since there shouldnāt be displayed in the 530 or 430. In the Garmin documentation, there are no messages about engines. Maybe this is the best solution.
1 Like
If its a Vote, I vote for removing it, and keeping the GNS530 Mod as real as possible ā especially then the issue is caused by a MSFS bug, in a plane whose files that need to be modded, are hidden/encoded in .fsarchive
3 Likes
big thanks for all your amazing work with the GNS530
3 Likes
So there will be a new version today.
Thanks for having reported these bugs to me. Difficult to test every situation.
3 Likes
Thatās okay, thatās what we are here for! 
1 Like
Maybe what could help here, especially long term, is a āTest Scriptā.
A sequence of functions to run through, with check boxes for each.
Yes, it will be long, and take some time to do (and add to as more features are added), but the benefit is that any user can then run through these tests and
(1) learn all the features
(2) test all the features
(3) Report in a consistent way, what features fail for them.
Quite a lot of initial work, but in the long term, it would enable almost anyone to test the GNS530 is a consistent and thorough way, and reduce a lot routine testing time for the developer, especially when Asobo do their regular āUpdates / Mod Bustersā
Sure; at least he does not make us pay to find bugs in software like Microsoft does with FS. 
Test script would be nice, but Iām happy just using it. No test script ever gets it all 
I love what youāve done here and use it all the time, thank you. Let us know if youāve got a donation page.
1 Like
A good script will get most, but no script just results in random reports,many of which are just operator error.
A good script would server 2 functions.
(a) A test procedure that anyone can go through and provide consistent bug reports.
(b) By it nature, good documentation, and a run through of all the operation of the GPS.
In the long term, its far more efficient, than random reports of perceived errors.
As promised, here is a new release
Available at: https://pms50.com/fs2020/gns530/pms50-gns530.zip
Changelog
v1.0.19
- Bug in init screen fixed
- Added flight plan load in GNS430
- Engine alert messages no more displayed (the GPS is not the place to display them)
9 Likes
Amazing, thanks for the quick fix. 