Yurbuh Tuggly wrote:If you contact WayTeq, you may want to be careful what you say if you have replaced/installed your own navigation software other than what came with it. They may be unlikely to offer 'support' for any versions of anything that they did not provide.

This is the reason I have not contacted them so far. And I got the device anyway from a friend, who had gotten it as a gift, ...

mpourdas wrote:I got some .dll's from another "popular" igo primo 2 version, but no success. I do not know if I should put the dll in the main or the tmc folder, but I tried both anyway. In the sys.txt file I have no entry related to tmc, in the tmc folder I have left only one .tmc file (infoblu for Italy),

The *.dll would go in the root of your Primo folder (on the same level as the EXE, sys.txt, content folder, etc)
Yes, you would probably have to tell Primo the TMC settings in sys.txt (assuming the hardware would not be auto-detected...which you would not know for sure unless the proper DLL was present)...something (but NOT EXACTLY!) like this:

[tmc]
show_tmc=1
port="COM,1"
baud=38400
source="gns"

The most significant thing. The external USB/TMC will probably emulate a com port...you just have to know which one.
Anything in the "TMC" folder, at this point is irrelevant. Those would only be special premium licenses which should not affect the ability of Primo to auto-scan for stations.
I have just about every *.dll known, but it would be hit and miss, and some renaming back and forth. I have about 20 files.
If you get nowhere with Waytec, I can upload them for you if you want to try 'the hard way'.

mpourdas wrote:click on it, all buttons are fade

That means no TMC receiver has been detected. Never will be without a proper DLL, probably.
EDIT: Here they all are:
4632

Unzip the attachment on your PC, and you can try each dll (one at a time) to see if the process of elimination could possibly work...if the "TMC" buttons within Primo become un-grayed out, that's the one. Note that all the DLLs with numbers in their names will probably have to be renamed without the numbers...such as gpstmc v4.0.0.7.dll to just gpstmc.dll.

Good luck!
Report back.

First you could check that the receiver is actually working, by using, e.g. mixsertester (google it), with it you can open a com port and see if is there a tmc receiver attached.
Once you found it, you could try putting in sys.txt something like this (instead of 8 put the number of your port and instead of 9660 the speed that works for you):

Code: Select all

[tmc]
show_tmc=1
port="COM,8"
baud=9600
source="royaltek"
saved_config_available="1"
saved_config_classname="NMEA_GPSTMC_ROYALTEK"
seved_config_portname="COM"
saved_config_port="8"


Thanks a lot, I will play with the dll's and the sys.txt file tomorrow and let you know. I hope to solve the problem here since I cannot find the email for support in the wayteq website. It seems I have to through a registration form, where I should give more data than I am willing to. And the box to receive their newsletter by email cannot be unchecked! I do not like these strategies in general, but I am really very satisfied with the GPS device so far.

It is 2 days since I emailed Wayteq and as yet no reply.Hope we can get this going without them!

mpourdas wrote:Thanks a lot, I will play with the dll's and the sys.txt file tomorrow and let you know. I hope to solve the problem here since I cannot find the email for support in the wayteq website. It seems I have to through a registration form, where I should give more data than I am willing to. And the box to receive their newsletter by email cannot be unchecked! I do not like these strategies in general, but I am really very satisfied with the GPS device so far.

I agree.The device I have,the 960 BT is IMHO as good if not better than any Tom Tom or Garmin I have had.It is also a great deal cheaper.Once the TMC is working it will be perfect.

No success and in fact it seems difficult since I have no constraints so far to proceed.

I tried all the dlls without putting any tmc entry in the sys.txt.

I also found another, rather recent, dll from the fixmygps forum which was supposed to work for a royaltek 3000 and I tried playing with the sys.txt by varying the com port (1 to 4) and the source (royaltek or NMEA_GPSTMC_ROYALTEK). The appropriate dll depends on the receiver, the GPS or both? I guess the receiver, right?

The mixsertester does not run neither on my mac (clearly) nor on my old Pc, it says not valid win32 application. Actually I do not know where I am suppose to run it, and how exactly to use it.

Now in the settings I have two boxes to tick (apart from history): traffic receiver and online traffic. If I check only the first I never see the little corresponding icon close to the top right of the map. If I click also the online traffic (even though I have no internet connection) then I do see it, but if I click on it to see the traffic summary no button seems "active".

Ovalball, how did you contact wayteq, and what did you ask?

mixsertester is a windows ce program that have to be used on your device in order to find the right port and speed (which, IIRC, should be 9600bps), because you aren't going to connect the TMC receiver to your pc or your mac.

Edit: once you manage to run mixsertester, it will show you 2 panes (it doesn't matter which one you use), each with a port selection, speed selection, an "open" and "close" button (don't remember if it's the same one or two buttons) and a memo.

Set the speed to 9600 and try to open every port.

If the port doesn't exist, it will say "open failed". If it can open it but you see nothing, it's not your port, click "close" and try the next one.
If you see text scrolling, it could either be the gps or the tmc receiver.
You should recognize the messages from the tmc receiver because they start with "$RTRDS" or "$RDTMC".
If you don't find the port this way, it could either because the speed is wrong (so repeat the process with another speed, though my receiver, also based on a royaltek chipset, uses 9600) or because your device usb doesn't work as a serial port when connected to the TMC receiver.
It's also possible that in fact is a real usb device (which I doubt) in which case you'll need drivers, though I don't know how that works on windows ce.

Or this http://www.navitotal.com/showthread.php?8650-i-need-%28gps.exe%29-for-check-my-gps-and-com.please-give-download-link-tq-so-much. Post #3.

mpourdas wrote:No success and in fact it seems difficult since I have no constraints so far to proceed.

I tried all the dlls without putting any tmc entry in the sys.txt.

I also found another, rather recent, dll from the fixmygps forum which was supposed to work for a royaltek 3000 and I tried playing with the sys.txt by varying the com port (1 to 4) and the source (royaltek or NMEA_GPSTMC_ROYALTEK). The appropriate dll depends on the receiver, the GPS or both? I guess the receiver, right?

The mixsertester does not run neither on my mac (clearly) nor on my old Pc, it says not valid win32 application. Actually I do not know where I am suppose to run it, and how exactly to use it.

Now in the settings I have two boxes to tick (apart from history): traffic receiver and online traffic. If I check only the first I never see the little corresponding icon close to the top right of the map. If I click also the online traffic (even though I have no internet connection) then I do see it, but if I click on it to see the traffic summary no button seems "active".

Ovalball, how did you contact wayteq, and what did you ask?

I used the contact us link on their website.I told them I had a 960 BT and a TMC 300 which I bought directly from them.I asked how I could get it to work.As yet still no reply!

pippolippi wrote:If the port doesn't exist, it will say "open failed". If it can open it but you see nothing, it's not your port, click "close" and try the next one.
If you see text scrolling, it could either be the gps or the tmc receiver.

Unfortunately I see text scrolling in only one port, COM1, which is the GPS. (Also I can open COM4 and COM7 but nothing shows up). Results are independent of the baudrate.

chas521 wrote:Or this http://www.navitotal.com/showthread....ink-tq-so-much. Post #3.

The scandebug shows only that COM1 is the GPS port, in agreement with the mixsertester. The other program, looks a bit "scary" for me. I tried, but I do not know what is doing.

Ovalball, since we have the same GPS and receiver could you try to see if you get anything with the mixsertester?

mpourdas wrote:Unfortunately I see text scrolling in only one port, COM1, which is the GPS. (Also I can open COM4 and COM7 but nothing shows up).

That's not good. In mixsertester there's also a button to test for a TMC receiver, but the royaltek should be sending messages all by itself.

pippolippi wrote:That's not good. In mixsertester there's also a button to test for a TMC receiver, but the royaltek should be sending messages all by itself.

I guess now I have to fine another WinCE device to test the receiver...

mpourdas wrote:I guess now I have to fine another WinCE device to test the receiver...

The usb port on a wince device (edit: or any device with a mini or micro usb connector) can be

• A plain usb port that can only work in "device" mode (you can connect that only to a computer which will see the device as an hard disk or can use it for active sync).
• An usb OTG port, which can be either device or host, depending on what you connect (usually by shorting by 4 and 5 it will set itself to host mode instead of device mode). Edit: note that this mode is only "standard" for a micro usb connector, but many devices with a mini usb connector work this way even if it's not standard.
• An usb port that transforms into a serial port with TTL levels when pins 4 and 5 are shorted. Edit: this isn't standard at all, but there are several PNAs that work this way.

If you look at

[Please Register or Login to download file]

on the "Specification" tab it says "Baud rate: 9600 TTL". The "TTL" part leads me to think that, just like other royaltek receivers, the usb connector isn't really usb but is a serial port with TTL levels. This will work if your device has a port of the third type.
It could also be that royaltek's documentation is bad or incomplete, and it's actually a real usb device, in that case it will only work if your wince device is of the second type, and you have the necessary driver.
If your device has a port of the first type this will never work. This shouldn't be the case of the wayteq (after all they list it as compatible) but it could be the case with any other random device.
Good luck.