IGo "hogs" the GPS receiver

So I recently got iGo primo running on my Eonon D5151, a Chinese nav unit with 128mb ram running win CE 6, and noticed something funny. Whenever I have igo open, it seems to hog the GPS antenna.

The head unit has an option to sync time from GPS, which works great until I open up iGo. Then, the time gets stuck on whatever time it was when I opened up iGo and it lock it's signal.

Is there a setting I can add to the sys.txt to fix this? I'm running 2.4, but am considering going down to 2.0, so an answer for either version would be perfect.

I was originally running Kudos nav, which came with the unit, but I like igo way better. I would just like to be able to maintain th clock functionality on the head into as it doesn't seem to save the time correctly unless I have the GPS sync enabled.

Any help is appreciated.

sefeing wrote:So I recently got iGo primo running on my Eonon D5151, a Chinese nav unit with 128mb ram running win CE 6, and noticed something funny. Whenever I have igo open, it seems to hog the GPS antenna.

The head unit has an option to sync time from GPS, which works great until I open up iGo. Then, the time gets stuck on whatever time it was when I opened up iGo and it lock it's signal.

Is there a setting I can add to the sys.txt to fix this? I'm running 2.4, but am considering going down to 2.0, so an answer for either version would be perfect.

I was originally running Kudos nav, which came with the unit, but I like igo way better. I would just like to be able to maintain th clock functionality on the head into as it doesn't seem to save the time correctly unless I have the GPS sync enabled.

Any help is appreciated.

OK firstly, this doesn't make any sense and is a terrible design by Eonon. You only need to sync GPS time once, which most WinCE ROM's do. Minutes aren't going to be redefined any time soon, so there is absolutely no need to repeatedly local sync the time with the atomic time. Usually, when the time is 00:00, WinCE will sync the time within roughly 20 seconds with GPS time, but from then on, the local internal clock will takeover. I've not seen it done differently on any device. With regards to your GPS being hogged. You could consider the Port Splitter app which is quite readily available, or perhaps lower your baud rate to 4800 which is the speed at which GPS works. Anything higher is simply used to clear the backlog of GPS events by the CPU.

Hah. This is true. Any tutorials for the port splitter app? Do I need to be able to access it from WINce or do I just place it on the sd with igo and it auto launches somehow?

It seemed to work alright with Kudos, which seemed to have a lower refresh rate so maybe I'll try the baud rate?

What do I enter into the sys.txt?

sefeing wrote:Hah. This is true. Any tutorials for the port splitter app? Do I need to be able to access it from WINce or do I just place it on the sd with igo and it auto launches somehow?

It seemed to work alright with Kudos, which seemed to have a lower refresh rate so maybe I'll try the baud rate?

What do I enter into the sys.txt?

[gps]
baud="4800"

This is the lowest the baud rate should ever be for GPS. You can go lower, but GPS instructions are received at this speed, so having it lower would result in a massive lagg. The higher your baud rate, the quicker the GPS instructions can be computed so it's just good for dealing with CPU laggs + processing lagg.

Ah I see. Is there any way to figure out my current rate? Would port splitter or assigning a certain port fix it as well?

Potentially using port 1 instead of 2 would fix it. I can't remember if there is a way. There used to be an app that could check it but it was very unreliable.

For a port splitter, do you need to be able to open it from wince? Or do you put it on the sd and it automatically works with igo?

Does this app. help you? 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.

sefeing wrote:For a port splitter, do you need to be able to open it from wince? Or do you put it on the sd and it automatically works with igo?

You'll need to open it. One way you could do it is by writing a mortscript that opens both the portsplitter and igo

Hmm I'll give that a shot. No clue about a mortscript though. Hopefully the baud rate will fix it.

according to the Eonon site, I should be using port 2, BAUD 9600/4800.

Would setting it to port 2 free up port 1 for the HU's Time-setting function to read? Or would it just potentiall cause more problems?
Basically, is it possible iGo reads off port 2, and the HU off 1?

Sorry for the double post. my work computer is having trouble with edits :/

Is it possible to run two ports at once? I.E.- iGo on port 2 and the HU's time management on port 1?

Most of them do this as standard. They usually reserve both port 1 and port 2 and they can run simultaneously yes. However, in practice what you might find is the port splitter works better as it provides 2 virtual ports so Windows won't be threadblocked.

Great. Just to double check- is it a possibility that iGo is running on port 1, when that's the one that's supposed to be for the time management?

So theoretically, if I were to designate iGo to run on port 2, port 1 would be open for the HU's time management, correct? By adding the correct port into sys.txt?

Sorry again for the double post. Work comp...

So, i'm just going to stick with 2.4 because of memory problems im running into on 2.0.

Do i need to change anything besides the sys.txt to change either the baud or the port?

I've read i need to either change system.ini or delete the saves folder to get everything refreshed?

sorry for all the questions and double posts. im real new when it comes to GPS modding ha.

If you post your sys.txt in the other thread I'm sure we can fix it. With regards to changing anything else... no. You just need to change the sys.txt file and you will be sorted.

You don't always have to delete your save folder, however it just rebuilds a profile so it's up to you.