Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem downloading EX5000 files #22

Open
paulohm2 opened this issue Nov 29, 2024 · 12 comments
Open

Problem downloading EX5000 files #22

paulohm2 opened this issue Nov 29, 2024 · 12 comments

Comments

@paulohm2
Copy link

1 Avidyne EX5000, EX600, EX500 - NavData Americas 2412 2024-11-28 2024-12-26 Y
6 Avidyne EX5000, EX600, EX500 - Electronic Charts BUNDLE - Latin & South A… 24-2024 2024-11-22 2024-12-06 Y

jdmtool transfer 1 /media/sda1
This service is not yet supported

jdmtool transfer 6 /media/sda1
Unexpected service type

@dimaryaz
Copy link
Owner

dimaryaz commented Dec 4, 2024

@paulohm2 - this one was easy. See if the latest main works for you.

(Also, does EX5000 seriously require a FAT16-formatted device?? I don't actually have a way to check for that.)

@dimaryaz dimaryaz reopened this Dec 4, 2024
@dimaryaz
Copy link
Owner

dimaryaz commented Dec 4, 2024

Oops, I fixed 1; still working on 6.

@paulohm2
Copy link
Author

paulohm2 commented Dec 4, 2024 via email

@paulohm2
Copy link
Author

paulohm2 commented Dec 5, 2024 via email

@dimaryaz
Copy link
Owner

dimaryaz commented Dec 23, 2024

Well, I got the electronic charts working! Try the avidyne_charts branch. (That is, try transferring the charts to a USB drive; I would not recommend updating the avionics just yet.)

The good news is: it's 95% the same as G1000, which I had already implemented earlier.
The bad news is: I have not yet gotten any reports of anyone successfully programming the G1000.

The resulting files are not exactly the same as what JDM produces, so it's hard for me to "prove" that they're correct. First, see this doc about G1000 Chartview; all of that applies here, too. Also, I have not implemented the coverage filtering (the "Edit Coverage" button in JDM) - but I'm assuming it's not that important.

In addition to the above: don't know if you've looked at the files JDM produces, and noticed that the update comes in the form of an AviUtility.exe file. Yes, .exe... Well, the good news is, it's actually just a copy of a file that is part of JDM, with a payload appended to it. I was reluctant to add anything from JDM to this repo, so you'll have to copy two files yourself, from wherever you have JDM installed. If you have it installed using Wine, you can do something like:

cp -r ~/.wine/drive_c/Program\ Files/Jeppesen/Jdm/oemdata/ ~/.local/share/jdmtool/

(jdmtool itself will also tell you what to do.)

Make sure to run pip install . from the avidyne_charts branch.

Transfer the service using JDM, and keep the files so you can compare them to jdmtool's files.

Transfer the service using jdmtool: jdmtool transfer 6 /media/sda1. Or, use a random directory instead: jdmtool transfer --vol-id 0000-0000 6 ./test-dir/.

If that succeeds, you can now inspect the .exe files from JDM and jdmtool, and see if you find anything that looks wrong.

List the contents of the exe: aviutil /media/sda1/AviUtility.exe
Extract all of the files in the payload into the current directory: aviutil -x /media/sda1/AviUtility.exe

You should see three directories:

  • Charts: mostly contains .dbf files, which you can open in e.g. LibreOffice. It's all info about airports, notams, subscriptions, etc.
  • Fonts: font files, straight from the downloaded .zip - except that JDM makes some of them uppercase? But I'm assuming it doesn't matter on a FAT filesystem.
  • Extractor: contains AviCharts.bin , which contains the actual charts. You can extract them by running chartview -x AviCharts.bin. jdmtool's version contains more charts than JDM's - probably due to the lack of coverage filtering (I will look into that later). But it should contain all of the files that JDM creates, and they should be identical. As long as you disabled the coverage filter in JDM, the AviCharts.bin files should be identical.

In addition to AviUtility.exe, there is AviUtil.dat - but it's copied from oemdata, so should be identical. JDM also creates AirportReport.html; jdmtool doesn't, but I'm assuming it's just for the user to look at, not for the avionics.

Let me know if you get it to work!

@dimaryaz
Copy link
Owner

I realized there's a bug in subscription guessing logic, and it will include airport metadata, notams, etc. for the whole world. Don't know if that actually causes problems, but in any case, I think I know how to fix it.

@paulohm2
Copy link
Author

paulohm2 commented Dec 23, 2024 via email

@dimaryaz
Copy link
Owner

And actually, I just fixed the subscription logic, so it should now match JDM (without the coverage filter)

@paulohm2
Copy link
Author

paulohm2 commented Dec 23, 2024 via email

@dimaryaz
Copy link
Owner

Yeah, run git pull just in case. I pushed the fix (02f1b53) literally the minute you commented :)

@paulohm2
Copy link
Author

paulohm2 commented Dec 23, 2024 via email

@dimaryaz
Copy link
Owner

Haha, have fun!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants