Thread: iGO Avicsync 9.35.2.227616

@Cheldron
Hi!
Here you go:

@batiskaf

Hi! You are the Master! I am just an Amateur!

[Only registered and activated users can see links. ]
Do you know me from somewhere?

The software is not fully patched. Use "Here" buildings with the corresponding licenses.
This also applies to the 64-bit versions of Basar and World.

One answer should be sufficient.

Hello everyone,

I would like to report a routing issue in iGO Nextgen AVICSYNC 9.35.2.227616 when using HERE maps with the TRUCK vehicle profile.

The problem concerns toll road avoidance for heavy goods vehicles, especially on international routes through Europe.

Problem description

When I select the TRUCK profile and disable toll roads, AVICSYNC avoids not only motorways with additional toll charges but also major roads covered by electronic distance-based truck toll systems, such as Poland's e-TOLL and Germany's Toll Collect.

As a result, the calculated routes become extremely long and impractical.

For example, when planning a route to Ghent, Belgium, AVICSYNC calculates a route exceeding 2,000 km instead of a normal route.

My intention is not to avoid electronic truck toll systems, which are mandatory and already accounted for in commercial transport operations. I only want to avoid additional toll sections, such as certain motorways or toll plazas.

Tests performed

HERE maps + TRUCK profile + toll roads disabled: incorrect route, over 2,000 km.

HERE maps + TRUCK profile + toll roads enabled: correct route.

HERE maps + BUS profile + toll roads disabled: correct route, even with vehicle weight set to 40 tonnes and length set to 16 metres.

TomTom maps + TRUCK profile + toll roads disabled: correct route.

Different HERE map releases from 2025 and 2026: same incorrect behaviour in AVICSYNC.

Different map licences: no improvement.

Replacing vehicle_selection.zip, truck.zip and Pongo skin files: no improvement.

Another iGO Nextgen version: routing works correctly.

The data.zip used in both installations is also the same.

Observations

These tests strongly suggest that the problem is related to how the AVICSYNC routing engine interprets truck-specific toll restrictions from HERE maps.

The fact that the BUS profile calculates the route correctly, even with a weight of 40 tonnes, is especially interesting.

A temporary workaround is to create an additional vehicle profile named "Truck HERE" based on the BUS vehicle type, with the correct truck dimensions, weight, trailer and ADR settings.

However, this is not a proper solution. The routing engine still treats the vehicle as a bus and may not apply truck-specific road restrictions correctly.

Questions to the community

Has anyone experienced the same issue with AVICSYNC 9.35.2.227616 and HERE maps?

Is this a known limitation or bug in the AVICSYNC routing engine?

Is there a working fix that preserves the actual TRUCK vehicle type?

Can electronic truck toll roads be distinguished from other toll roads in the routing configuration?

Is there any confirmed patch or modification that solves this issue without changing the navigation engine?

I would prefer to keep AVICSYNC because the rest of the navigation works well for my needs.

I am looking for a genuine fix, not a workaround based on the BUS profile.

Any technical information or confirmed solution would be greatly appreciated.

Thank you.

The routing method does not depend on the content, in the sense that with one map it will be routed in one way, with another it will be routed in another way, just because they are from different providers
There is only one algorithm
Routing depends exclusively on the content that is read and embedded in the files


Apart from the obvious differences between providers, HERE uses separate files for truck restrictions - ftr (and Truck POI but they are not relevant in this case). Make sure you have them all present, that they are active (covered by licenses).
The 9.35 iGO series is not fully cracked, so it is possible that some files are inactive

At one time TomTom had that content integrated into the maps themselves (!). So you don't have to think about additional licenses from that side
True, with the last editions he decided to separate them again, probably because the content has become bulky

So I would say it's a license issue. Stick to the old, proven iGO NextGen editions
I do not recommend Israel edition, because it is one of the first and knows how to mess with new devices and content. Go to Pal

Hi SlawekPiet,
There is a strong opinion within the community that the AVICSYNC (9.35.x) engine is simply not the right tool for heavy trucks (TIR), and your detailed tests actually prove it.
Here are a few technical reasons why you are facing this issue:
• Origin and Purpose: The AVICSYNC branch was originally developed by NNG specifically for Pioneer AVIC multimedia systems. Its routing core was tailored for passenger cars, light commercial vehicles, and campers. It was never intended to handle complex commercial fleet attributes like electronic distance-based tolls (e-TOLL, Toll Collect) or strict axle load boundaries.
• License and Core Limitations: Even if you load the correct .ftr files and latest maps, the cracked AVICSYNC executive file often cannot properly read or validate specific truck toll matrices without proper, deep-level licensing. When a Nextgen core encounters a license mismatch or an unhandled attribute in the HERE map data, it doesn't crash — it just silently breaks the routing logic, resulting in those ridiculous 2000 km detours you observed.
Conclusion:
Your "BUS profile" workaround is clever, but as you mentioned, it's unsafe for real commercial driving because it might ignore crucial truck-specific physical restrictions.
If you need a reliable navigation for a 40-tonne truck, it is highly recommended to switch to more "truck-friendly" and well-patched Nextgen distributions, such as iGO Nextgen Israel (9.18.27.x) or iGO Nextgen PAL. Their routing engines handle HERE truck parameters and toll avoidance flawlessly without any workarounds.