PPP Forum

Hello,

every Command "SwitchMap" will crash TT ...
What is wrong ? With TT5 v5100 no Problem ...

Greetings
howi

Hi,

we have the same problem. SwitchMap will always crash TT!

So, who knows what's wrong?

Thanks a lot!

Many Greetings
bbtom

Hi Howi,

the problem (could) be that TTNCF5 is built for SDK 5.10.

Next week we will provide an update for the wrapper so that it links with SDK 5.21 - we will see in our tests if this still happends.

But there is something wrong in the SDK with SwitchMap.

We are currently testing the new TTNCF5 5.2 - SwitchMap does not crash - it simply returns -5 and does nothing!

As we know that TomTom does sometimes "strange things" with the documentation we are at the moment messing around
with different formats of the PNA path.

But till now  -5

I'll keep you informed in this thread

Manfred

Hi,

could you please tell me:

a.) TTN Version
b.) SDK Version
c.) The map path you use

And please for both versions - the running - and the crashing.

By the way - we did now try to use an older version - no crashes at all - but -5

Regards

Manfred

Hi,

we got more precise results.

The -5 was (more or less) our fault (our testdriver gave a wrong path) - we checked it against the TomTom SDK documentation:
>>Switch to the map specified by the full name and path of the .PNA file.
So \Storage Card\Great_Britain_Plus-Map\Great_Britain_Plus.pna seems to be OK.
The reality is \Storage Card\Great_Britain_Plus-Map\ -- as I said in my post above "never trust a documentation"

After fixing this we can tell:

The SDK version does not matter - also not the wrapper verion.

We gave it a try with TTNCF5, TTNCF5 V 5.1, TTNCF5 V 5.2 and the matching SDKs.

TomTom Navigator 5.100 (5160) works (with all SDKs / Wrappers).
TomTom Navigator 5.101 (5170) works (with all SDKs / Wrappers).

TomTom Navigator 5.210 (5430) CRASHES (with all SDKs / Wrappers).

So it seems to be the Navigator application which makes the troubles!

Regards

Manfred

Hi ManniT,

Thanks a lot. After additional testing, I can confirm your results.

It seems that we must wait for a new update?

Do you know, what TT says to this bug?

Many Greetings
bbtom

Hi Tom,

no - I just reported it to them.

By the way - we also tried it with the TomTom C++ smaple application "SimpleClient" to ensure that our wrapper is not involved!

This is a thing (use SimpleClient -- something like TomTom TestTTN ) we always do before reporting a but to TomTom.
And if SimpleClient does not provide the functionality we write a little app in C++.

Regards

Manfred
PS: maybe it could help if you report it too - the more customers ......

Hi,

thanx a lot ...
I am not the only one of the world with this problem ...

It is not a question of the SDK version ...
Here a low level test ...
When you write a file"SwitchMap.TomTomNavigationServer.1.1.message"
with content "SwitchMapV01|\SD Card\Benelux-Map\|"+0x00
and a file
"SwitchMap.TomTomNavigationServer.1.1.finished" whith "finish"+0x0a+0x00
to the \tomtom\sdkfilecalls\ path ...
you have the crash effect ...

Howi

Hi Howi,

jep I know - you can simply achive this by a call to "SwitchMapAsync" without TTN running.

We were also behind these things and the first thought was that the file is "misformated" with the new SDK.
But - no matter which SDK you use - the file is always the same - so TomTom did not change the SDK in this part (producing file).

So definitly the Navigator EXE is makeing the problems.

While writing I'v got this mail:

Hello Manfred,

I have tested your bug report and can confirm that the switchmap function is causing an unsuspected behavior. I will report this to our development team and we will try to get it fixed in the next update. Thanks for your report.

 Regards,

Koen Jochems
(SDK Product Specialist)

Regards

Manfred

Hi,

after a talk with Christiaan Langezaal - who was (as always) trying to help where it is possible - I have the following facts:

The bug is confirmed.
He thinks SwitchMap is rarely used (I argued 3 of my customers and me at the very moment).
Generally the Statement of Koen Jochems means "next update" and this is scheduled for Q2 2006.
After finding the bug (I argued this can't be a big thing) they will decide what to do.

MAYBE (more after bug location) we can get a "developer version" of TTN which does not have the bug.

Since the SDK has no bug we decided to ship TTNCF5 V 5.2 - a fix shall be done by simply replaceing the TTN exe.

And I hope a lot of developers contact TomTom about that bug

Regards

Manfred

What ?

TT make bullsh*t, an my 147 user must wait until Q2 2006 ?
Arghhh...

Howi

Hi Howi,

I understand your feeling - but please watch your language.
I set my hopes on Christiaan - he has a link to this thread - and from earlier contact
he really helped a lot.

There was a problem with GPS Driver performance. I told him the situation, sent a test app and he gave me over to an emloyee,
which did hard work to make this go.
Also this release was not official - but I got it and everybody with problems in this case got it also.

The TomTom problem - they have a huge number of customers.
If they start with "micro updates" be sure this will bring a lot of confusion to them.
So providing a new version means a lot of stress.

On the other hand - if there is a realy need - I think they will help as they did it with the GPS thing.

Since you have 147 Customers this would be some kind of "motivaion" for TomTom to react ASAP.
You should tell this number to Christiaan Langezaal - maybe it helps that he does even more than his best

Regards

Manfred

Hello,

Sorry for that ....

But the most of our costumers have installed the new version and
call "howi" that nothing will go one.
My nerves are a little bit crazy ...
But dit TT not test the versions before release ?

Sorry for that ....

mea culpa

howi

By the way ...

The new EnableRawGPSOutput have also a bug.. (on my system)
When  your programm  make  EnableRawGPSOutput to TT5 then
TT response with WM_GETTEXT and WM_COPYDATA with NMEA Data ...
When you make DisableRawGPSOutput TT stop this.

ok..., but
when the user terminates TT before you make the DisableRawGPSOutput TT
happens this:
a TT-rest (MunichClassWin) runs in the backround on an leaves the com port open (i can see this by a led on my syson cf gps).
There is no way to end this, because TT dit now NOT response of a DisableRawGPSOutput!
When you now restart TT, it will say "no gps device"!

Only softreset to the pda will help.

Manni, can you confim this ?
Greetings
Howi

PS: Manni: thanks for your support !

As I told you - I understand your feelings - and I think Christiaan if reading this thread will also.

I had the same with a lot of customers at the "GPS thing".
On my high-perf it worked when using the "filtered send" - but on their devices......the called Manni

But and that's the thing - it ended in a suitable solution.

And I hope it will go the same way with this....

About testing - last week (TomTom just release SDK 5.20) I got a mail from a customer asking me, why we delay.
He thought we worked with the beta - got the relase - relink and go.
That shows a lot of "testing mentality" out in the field.

From out point of view testing is most important - and it saves a lot of time - spent for support calls.
That is the reason why we gave the new wrapper 9xx kilometers of run, and a call to every function.

But even that does not ensure "bugfreenes".
By a "last time renameing" after the tests we did rename an interal function so that it became recursive -- endless loop.
By the way - we found this bug before our customers did

And in the next version - we did oversee an underscore - wich in our environment runs without problems - but did not work with customers.

We will see what 5.2 brings

At TomTom there are different divisions - or in other words the SDK is made by other employees than the Navigator.

And in this special case  it looks as if they did not check all SDK functions against the shipped Navigator.

We ourselfs did also not find that bug mean beta because we got the beta relative late and our primary goal was "dynamic testing" (on the road).
So our steps were - all new functions, dynamic functions (route, GPS, rawGPS, curpos....) and in the middle of testing the static functions
(StopApp, StartApp, GetAppVersion, .....) then the release came out.

So we stopped beta testing - and restarted the cycle at new function, dynamic functions, .....
Till yesterday where on the checklist were only a few (old!!) static functions were left we found the switch map.
First thinking of another problem (-5) your post brought us in the right direction.

We know sh*t happens - even bullsh*t

But in the end the solution counts - and I'm stll hopefull.

It is by the way a worse situation that the things came out on friday.
So we have to wait over the weekend - but let us see what the next week will bring.

Cheers

Manfred