PPP Forum

I have had some problems when I moved a working app (from an XDA exec) onto a WM6 device (XDA Trion).

It does not seem to allow more than 2 calls to the API before blocking on the next call.

e.g I call

switchtonavigatorview

bringnavigatortoforeground

if i then call clearroute it blocks

Are there any known issues with TTN / TTNCF on WM6?

Is there any way I can

1.) set a timeout for a call to a method

2.) look at log files etc to find out what is happening.

Thanks

Craig

TTN SDK version : 6.010

TTNCF version : 6_0_3

 

Hi,

first of all we have not much experiences with WM6 since the SDK is built for WM5 (or older) and there is no clear declaration that it runs (troublefree) in WM6.
We tested with one device at the moment - and found no problems.

One important question to start: Could you please tell me the navigator version you are running???

About your questions:

No the TT-SDK is synchronous. It produces (except of some calls) two files in \TomTom\SdkFileCalls and waits for TTN to remove them an place two answer files.
And it waits infinite
An exception are asynchronous calls - see below.

One way to make this "timeout enabled" is to run SDK calls on a seperate thread and kill this thread after a certain amount of time.
Or to use async functions (available for the most calls).

The also produce the two files - but instead of waiting the return imidieatly.
You can then repetly call "ResultAvailable" and stop this checking after your "timeout".

This leads us to your second question: you can "see" haning because calls most of the time files are left in \TomTom\SdkFileCalls.
By checking those textfiles you can learn what is hanging.

Regards

Manfred

Manfred

I installed the TTN from the CAB provided by the SDK (6.010.7721)

From the sample app

Internal Version = > Helper Version = 6.0.1

Internal Version = > AssemblyVersion = 6.0.0.1

GetSDK Version => Ver = 207

GetSDK Version => StrVer = 6.0

GetAppVersion => Hangs , but checking the message files it does get the finish file.

If I restart the app but only call getappversion I get the expected result of

StrVer = 6.0.10

Ver = 7721

 

I have raised a question to Tomtom to see if they support the TTN6 SDK on WM6.

Hi,

the TTN version is correct.
But the helper should be newer (6.0.3)-- which has definitly nothing to do with your problems by the way.

And there are two finish files -- one is from the SDK (your app) and later there is one from TTN.
A function call makes:

a.) creates a "call file" (function name and params)
b.) creates a finish file (TTN triggers for it)
c.) TTN Reads the call file and deletes both files (call and finish)
d.) TTN computes the result and places it in an answer file.
e.) TTN produces a finish file
f.) the SDK triggers for the finish file
g.) the SDK reads the answer file
h.) the SDK deletes both files (answer and finish)
i.) the function returns to the caller

Regards

Manfred

I re-created the helper so it is now on 6.0.3

Using the sample app :

I get 2 message files

TTNCF6.TomTomNavigationServer.3252494018.2.message

containing "GetApplicationVersionV01| "

TTNCF6.TomTomNavigationServer.3252494018.2.finished

Does this mean that tomtom is ignoring / not completing the message call?

It seems to start tomtom in the background then freeze

If I start tomtom and make the same calls it seems to work ok

Hi,

what you get are the "Call Files".

This is a well known problem - TTN must be running to process calls.
Therefor we built StartTTN because it takes some time (after TTN runs) to initialize the SDK.
So if you call functions to early - TTN does not answer to SDK calls.

The "idea":
Start TTN - wait till it is (completely) running - make SDK calls.

Some functions seem to work (sometimes) if you simply call it.
They start TTN - and then the calls are processed.
But (starting with WM5) a lot of calls fail if the have to start TTN.

Instead you should ensure that TTN is fully running and than make your calls.

By the way - always clean up \TomTom\SdkFileCalls before you start TTN.

And the answer - yes TTN ignores your call - and the SDK waits (infinitely) for an answer.

Regards

Manfred

Thanks Manfred I now have good idea how it all works with the messaging files.

My app checks if tomtom is running before every call and starts it if not, I also start tomtom when the app starts.

I have tried making calls to

TTN.SwitchToNavigatorViewAsync

TTN.BringNavigatorToForegroundAsync

instead and it seems to work but sometimes it may take a while. (30 seconds)

The official response I got from TomTom was that they do not support WM6 or that device.

I have downgraded the device to WM5 and it seems to work just as well as the app did on the XDA Exec. (I will be testing further)

I have also tested the app on an XDA Orbit (WM 5 and WM6) and these also seem to work fine.

Seems strange that TomTom has issues with WM6 on one specific device.

Manfred what device did you use to test WM6?

Thanks

Craig

Hi,

Does anyone know if the SDK is supported/can be used with a device running windows mobile 6.1? 

The forum seems to have chopped half my post off!

Hi,

Does anyone know if the SDK is supported/can be used with a device running windows mobile 6.1?

TomTom's web site onlys seems to suggest that the SDK is supported with windows mobile 5 (http://www.tomtom.com/pro/page.php?ID=6) and TTN is supported with select windows mobile 6 devices (http://tomtom-uk.custhelp.com/cgi-bin/tomtom_uk.cfg/php/enduser/popup_adp.php?p_faqid=7219&p_created=1180622627).  If TTN is supported on selected devices do I assume that the SDK is supported on those devices?  It seems to me like tomtom aren't really pushing the sdk - anyone else get that feeling?

Am I correct in thinking that to get the functionality to work you have to have matching versions of TTN, tomtom sdk and pp-p's .NET wrapper?  So, if you have matching versions (e.g. ttn6, sdk6 and ttncf6) then it will work on the devices on their supported list (with the standard supplied operating system)?

Thanks,
Steria

First of all you are right -- the SDK division is some kind of a "fighter against the Navi division".

The problem Navi makes MUCH MORE (even if it can't give numbers it are decades) money than SDK.
Of course SDK also sells Navi - but not that much and so the situation looks like this.

SDK takes a stable Navi Build - they implemt the interfaces for the SDK and the things are done.
If there is a problem in the Navi (making SDK operations fail) it takes a bunch of time that the Navi division fixes this.
Anyhow - there will be a TTN version working with the SDK.
This is also shipped with the SDK.

Next Navi gets enhanced -- but noone there interests in compatibility with the SDK.
This is the reason why you must always ship your SDK related product with the TTN version included in the SDK.

Anyhow - nice people there with the SDK - but they are in bad situation.
Even if they are willing to help you, they sometimes are not able to do so.
SDK is a little part of TomTom - but Navi makes the money and that counts.

Anyhow this was just to explain a bit why you are right with thinking SDK is not so well supported.

 

About your question:
TTNCF is nothing more than a kind of .NET access to the SDK.
This means if the SDK run - TTNCF will also.

And so - if your device supports the SDK - TTNCF will work on it.
If there is no "declared support" - it MAY work - but it can also fail.

Regards

Manfred

Thanks Manfred that confirmed my suspicions and makes it a lot clearer! Cheers

Hi Manfred,
Is TomTom SDK now supported on WM 6 on a HTC 3300 device? I am seeing the same thing mentioned in this forum by other members. I am wondering whether i need to update my TOMTOM to get this to work?

The TOMTOM version is 6.030.