RR - iGuidance 3.0 embedding – Solutions Consolidated.

**EricE** · 03-08-2007, 01:07 PM

This will be a FAQ of sorts. It is a list of problems and solutions that I encountered as I tried to get iGuidance 3.0 properly embedded in RR and the volume working correctly. Hopefully someone will find this post when searching and I might save you from reading this entire thread (all 24 pages of it).
Thread reference here:
Auto switch to Guidance screen for iG?

First of all, the implementation can be very easy. As the first post indicates, there is no need to download any beta version of RR. This functionality is built into the regular release of RR now. Just get the latest.

Embedding: (written for iGuidance 3.0)
You will need to use RRConfig and go to the GPS section.
Set “GPS mode” to External (this will generally mean that when you push the GPS menu button in RR the skin “External_gps” will be loaded)
Set “GPS Path” to <full path>\iGuidanceUMPC.exe
Set “GPS window name” to iGuidance
Set “GPS Port” whatever com port your GPS is on. My GPS is on com 4 and I have Xport setup to replicate that to 5,6,7,8. I setup iGuidance to read port 5 and I setup RR to read port 6.

I don’t believe any of the other settings here in the GPS section of the config are making any difference for me. Set them or not, your choice.

Now find these settings at the bottom of the Readme.txt distributed with RR. Read their descriptions. Place these settings in your RR.ini at the bottom and set them appropriately.
ignative=true|false
gpstime=true|false
gpsusadate=true|false
igautosw=true|false
gpsonvoice=true|false
pauseonvoice=true|false
lastscreenswitchtime=[0-30] in seconds.

At this point you should be able to load up RR and click GPS…it should open iGuidance in your skin and iGuidance (w/o window header [which means no menus across top]) will fill the space in that skin allocated to the application.
I am told that if you use ignative=true then you should edit that screen to remove the clipping region. If you use ignative=false then make sure there is a clipping region the same size and position as the application frame.

At this point the problem I had was that I wanted access to the menus that are found on the window header. As I mentioned this window header cannot be seen and it made no difference if I had ignative true or false or clipping region or no. I finally discovered that I can get at those menus by using Alt+f or Alt+<down arrow> to drop the first menu down. The window bar may be hidden but it is still there and accessible. Note that this doesn’t work until iGuidance has been running for about 2 mins. I am not sure why but it won’t respond to keystrokes until that time. To further complicate matters my in-car keyboard (the mini usb keyboard from the store here) doesn’t have alt keys so I had to setup a custom keystroke macro on my shuttleXpress. I did discover after all this that the two things I wanted most from the menus are available in other ways. I wanted demo mode (which is available on the destination menu after a route is active and I wanted trip calculator which will popup if you press T.

Sound:
Finally I wanted the sound to lower to around 25% when IG was giving voice directions. The setting in the RRConfig didn’t make any difference for me and just caused confusion.
I spent hrs and hrs on this. Here is what worked.

Put this in your RR ExecTBL.ini

"IGPAUSE","!PRESET;IG3;WINAMP||SETVOL;WINAMP;5 0"
"IGRESUME","PRESET;IG3;WINAMP"

The 50 at the end of that line will vary from person to person. Try different values between 0 and 200.

Set pauseonvoice=true [in RR.ini]
It’s a bit of a misnomer. Set this way pauseonvoice=true will not pause but will lower the volume.

The last thing that is needed is for the volume level in IG to be somewhat different than your winamp volume. My winamp volume is always at 100% so I set IG to be one notch below 100%. Then it started working.

Oh, btw, when I couldn’t get the sound working I read on here that the latest version of winamp that works flawlessly with RR was 5.13. I had 5.2 installed so I uninstalled it and installed 5.13. I have no idea if that made any difference as I didn’t discover the ExecTBL.ini settings until after that.

**techeros** · 03-09-2007, 02:26 AM

dude... seriously... thanks for posting this

**ehourigan** · 03-10-2007, 01:55 PM

I cant seem to get iGuidance to remember the com port, and so when it launches in RR, everything is fine, except it doesnt have the correct port. When I launch outside, I can manually choose the port no problem. How do I get iGuidance to remember which port?

-Ed

**volum3rider** · 03-11-2007, 02:03 PM

When you choose the port manually in Iguidance ouside of Roadrunner, it should remember the settings when it is used again. Try searching for the gps port automatically through Iguidance, close it when finds the right one, and then try using it in Roadrunner.

**MillerTyme** · 03-11-2007, 02:32 PM

i had a similar problem like this my solution was to change the com port to something like less than 5. For example by default, im using a usb gps, it would come in at like com port 13. If i went in iguidance and clicked autofind it wouldnt find anything but if i manually selected port 13 it worked. Well the problem was it wouldnt save the port 13. So i took someone elses advice on here and switched the port # (in device manager) to 2 or 3 i think (make sure theres no conflict first) and then i went to iG and tried autofind, viola, it found it, and when i start it up it "remembers" the port number. Definately some sort of strange bug in iG luckily i found a somewhat simple work-around. Good luck.

**ehourigan** · 03-13-2007, 01:00 PM

Hi Everyone-- Just thought I'd share an easy solution to a major prob I was hyaving with iGuidance & RR -- I could only get it to work about 20% of the time, until I realized that my port settings in the Device Manager were wrong. Default the COM PORT was set to 9600 bps, but you need to change it to 4800 bps (at least with the unit I have). Once I changed this (in the device manager), everything started working seamlessly.

**guizai** · 03-18-2007, 01:33 AM

thanks for this post but I got still got problems getting iguidance to embed. I followed the config steps as well as the RRconfig and still nothing. It's very weird. Also, when I modify the shortcut with the |nowarning, it still shows up with the warning. I don't get why nothing I do with the settings changes the operation of Iguidance. Dang ****ing.

**EricE** · 03-19-2007, 02:01 PM

Originally Posted by guizai

thanks for this post but I got still got problems getting iguidance to embed. I followed the config steps as well as the RRconfig and still nothing. It's very weird. Also, when I modify the shortcut with the |nowarning, it still shows up with the warning. I don't get why nothing I do with the settings changes the operation of Iguidance. Dang ****ing.

Are you using iGuidance 3? With 3 you don't need to add the |nowarning, RR does it for you. As far as embedding goes, check everything over once again. I have to assume you did something wrong. If it still doesn't work then you will have to describe the behavior in more detail. You really didn't tell us much.

**guizai** · 03-19-2007, 11:22 PM

Yeah, I'm using Iguidance UMPC 3.0. It's really weird, I've tried it with and without the nowarning message. In RR, it doesn't bring it up. I have to manually start it and then it retains the menu bar. I tried running it outside of RR to at least to get it to open without the warning message but when I add the nowarning to the shortcut it makes no difference. I'm using the latest version of RR and Iguidance so I don't get it. Running XP. I don't know what else to do. I will try reinstalling RR and Iguidance to see if that helps.

**2k1Toaster** · 03-20-2007, 12:10 AM

Ive been having some ig issues as well. I put it into another thread. So far I have gotten some answers, but I still don't have all my questions answered.

Instead of cluttering this up, ill just post a link: iGuidance 3.0 UMPC and RoadRunner n00b issues