PPP Forum

Hi all,

i use a simple example project in VB.NET with Visual Studio 2005.

I just start TomTom with

TTN.StartApplication()

and then i want to navigate to an adress:

TTN.NavigateToAddress("Krefeld", "Dieselstraße", "75", "47803")

TomTom hangs so long until I stop my application. When I stop my application, TomTom begins to routing.

Any suggestions?

Rgds,
Marcel

Hi,

please let me know the result of "InternalVersions" as well as the running TTN version.

For the running TTN version implement a call to GetApp....

Regards

Manfred

hi,


GetAppVersion: Ver: 8341, 6.031

Internalversion: Helper: 6.0.3,  Assembly: 6.0.0.1


Does this help?

By the way: When I start your TestTTN example and directly click on GetAppVersion, then TomTom starts but it hangs, too.

Device is MDA Compact III (HTC Artemis) on WM5.
Edit: No other behaviour on HTC Kaiser / TyTN II

Rgds,
Marcel

Hi,

yes this explains the problem.

Pleas contact me via email (ttncf@pp-p.net) - I'll help you.

Regards

Manfred

Hi,

I seem to be experiencing a similar situation and would very much appreciate your help.

I have taken over a PDA application written in VB.NET, using the Compact Framework, from a previous employee and I am experiencing difficulties.  Basically, the application contains two links – clicking one implements a call to start tomtom and if it’s running then call TTN.ShowCoordinatesOnMap and the other link implements a call to start tomtom and if it’s running then calls TTN.NavigateToCoordinates.  Once these calls have been made, both links implement a call to TTN.TomTomApplicationToForeground().

A customer had tomtom navigator 5 on their HP IPAQ 6915 device running Windows Mobile 5 and the calls worked fine.  Then the customer moved to HTC P6500 devices running Windows Mobile 6 with TomTom Navigator 6.010 (7720) and now the calls do not work. 

The behaviour I am seeing is that tomtom starts – TTN.StartTTN and TTN.IsApplicationRunning work fine but as soon as another call is made (e.g. to TTN.ClearRoute or TTN.NavigateToCoordinates) then tomtom hangs.

GetInternalVersions outputs:
nMajor: 6
nMinor: 0
nRelease: 1
vPPPTTCFVersion: 6.0.0.1

Calling GetApplicationVersion hangs tomtom and GetSDKVersion reveals a build of 207 and version 6.0 (The tomtom SDK folder I can find on the previous employee’s PC says TomTomPPC-SDK6.010 and PPP’s .NET wrapper is version TTNCF6).

Any ideas as to what is causing tomtom to hang?

Thanks,

Hi,

the only thing I can tell in short is that the versions of TTN and SDK must match.

This means that you must install the TTN version from the SDK otherwise it would not work.

Regards

Manfred

Hi,

Thanks for your quick reply.  The SDK version is 6.010 and the TTN version is 6.010, although the TTN installed is what the customer bought from the box, not what was supplied with the SDK – I presumed matching versions would work even if not the one supplied with the SDK – is this an incorrect presumption to make?  If they had the same version (6.010) but slightly different builds would this cause the problems of tomtom hanging?

I have been continuing my searching after my post yesterday.  After reading another post (http://forums.pp-p.com/forums/thread/1050.aspx), I investigated the \TomTom\SdkFileCalls folder and more information is supplied below in the hope that someone will be able to help me:

Scenario one:
Don’t start TomTom, run my application, execute calls e.g. TTN.ShowCoordinatesOnMap, tomtom hangs and it creates a TTNCF6.TomTomNavigationServer.3306072566.2.message file containing  “ShowCoordinatesOnMapV01|-544950|5601333|” and TTNCF6.TomTomNavigationServer.3306072566.2.finished file containing “finish” in the \TomTom\SdkFileCalls folder on the device.

Scenario two:
Start TomTom, run my application, execute calls e.g. TTN.ShowCoordinatesOnMap, TomTomNavigationServer.TTNCF6.3306072566.2.message contains “-4|”.  The Device is out of GPS signal range so sits at ‘waiting for a valid GPS signal’ screen – fair enough.  If I delete all the files in the SdkFileCalls folder first then run this test again no more files are created.

Scenario three:
Delete any SDKFileCalls files, Start TomTom let it get a GPS signal, run my application, execute calls e.g. TTN.ShowCoordinatesOnMap, TomTom activates but doesn’t actually Show Coordinates On Map – it just stays on the position it’s on even though the coordinates it should show are  469 miles  away from it’s current position!

http://forums.pp-p.com/forums/thread/1050.aspx mentions Windows Mobile 6 and checking whether tomtom is running before every call and that is what I do – a call is made to TTN.IsApplicationRunning before proceeding to another call e.g. TTN.ShowCoordinatesOnMap.

Tom Tom’s official response is that they don’t support tomtom navigator on the HTC P6500 device/Windows Mobile 6 so therefore the SDK is unsupported.  However, I can’t believe that is the root of the problem – does anyone have any ideas?

Thanks,

Hi,

I have the same problem like Marcel.

When I start my application first and then start TomTom it hangs.

My TomTom-Versioninfos are:

TomTom Application: 6.010 (BuildNo 7721)

TomTom SDK: 6.0 (BuildNo 207)

TomTom CFWrapper: 6.0.3

Can you help me please.

Thanks and regards

Nicole

First of all thanks for the precise information (versions and so on - makes support a lot easier).

TomTom has a problem when functions are called imideately after you start TTN.
This does not occure allways - and not with all devices.

Our solution for this - after Starting TTN - start a timer (for about 2 to 5 secs.).
And with this timer enable the call of further SDK functions.

I hope this litte snippet can explain what I mean:

void MyFunction()   {
if(TTT.IsApplicationRunning()!=1)   {   //not running - start
   TTN.StartTNN(this,15,15);   //at least 15 seconds to stabi
   if(TTT.IsApplicationRunning()==1)   {   //yes it runs now
      Timer1.Enabled=true;
      return;
      }
   else   {
      //could not launch TTN.... handle FATAL ERROR
      }
   //now do the geocode and such things
}

//the handler for Timer1 is very simple
void OnTimer1_Tick(....)   {
   Timer1.Enabled=false;
   MyFunction();
}

By the way - "not matching versions" (not using the SDK version of TTN) COULD work - but it also can fail.

TomTom does not care about compatibility. They (SDK devivision) ship a compatible version with the SDK - and the "Navigator Devision" does not care about SDK compatibility (looks like) when tey further enhance / fix the navigator.

Your scenario (7720 instead of 7721) would caus problems (I guess) when you use negative coords.

Last not Least - allways ensure that \\TomTom\SDKFileCalls is empty before you start a new test.
And do a softreset if something goes wrong.

Regards

Manfred