Stephanie

If the wiring kit didn't come with a diagram or anything, then have a close look at the wires themselves. The Rav4 harness kit I bought didn't come with any information, but there was very small, light (silver coloured) writing on each wire that described what it was for. Cheers!

Neat!

I'd double check that the parking brake wire is properly grounded. If the software bypass works if you engage the parking brake slightly, then it should work when the parking brake wire is grounded. Having the parking brake engaged slightly just grounds the line. When you ground the parking brake wire, tie it to the negative / black wire that grounds the nav unit. Use a continuity tester or DMM to verify that it is truly grounded.

I was going to add this to another thread, but after thinking it over, I figured that this deserves it's own spot, so hopefully more people will see it. I'm sure that experienced programmers/hackers will already be familiar with these, but for those who are just getting started, these are good rules to live/code/hack by. The following are a list of tips and cautions, that can save a lot of grief and stress when it comes to modifying your navi. #1 - Make A Backup! Most of the hacks/mods revolve around the data.zip file. Make a backup to leave on your head unit (rename it data.bak or

I haven't tried movies at all so can't help there, sorry. Re the NSEW thing, I can get it to display a 'linear compass' which basically is like one of those old floating compasses, it floats the letters along on the screen. The code is already in place in the files, just not displayed, so it's just a matter of enabling it. Oh and the compass.bmp they had was backwards (E and W were backwards) so I had to make my own graphic for that. Sadly there is no way I can find to display the heading in degrees.

If you have the three bars of info displayed on the lower left corner, speed limit is one of the functions you can opt to have put in there. It's under settings, navi settings, visual, displayed info. Otherwise if you want to add a custom bit of text for it, just use search. The speed limit code has already been posted in this forum, I believe.

A note in the manual (page 179) made me try moving my music up a directory level when I first tried it out. It's a small little thing, but it solved the problem for me at least. I took that to mean, if a folder contains no music at all (even if it has subdirectories which themselves have music), the folder's contents will not be displayed. They have an illustration on that page that shows music in various subdirectory levels, but every level does contain some music.

I'm going to give up on this one.. I've tried every variable I can think of, every combination of textmodel I can think of, and nothing comes up at all. At this stage, I don't think there is a way to access the data. I know the data is in there, of course, but there doesn't seem to be a way to display it other than the zoombar. Of all the variables I tried, I thought these had the most potential: map.zoom_level_in_map map.zoom_level_in_navigate map.zoomlevel Unfortunately none of the textmodels revealed any data for me, nor any of the text methods. I have a feeling that the

I noticed one quirk that might affect how it looks at the SD cards. Mind you this was a 2GB card, but it might affect the larger ones as well. I found that it would only search one level of directories for music. If it found no music in the first level of subdirectories, it gave up. So this works: SD Card -->Album1 (folder) ---->Song1.mp3 ---->Song2.mp3 ---->Song3.mp3 -->Album2 (folder) ---->Song1.mp3 ---->Song2.mp3 ---->Song3.mp3 But this does not work: SD Card -->Music (folder) ---->Album1 (folder) ------>Song1.mp3 ------>Song2.mp3 ----

It seems to me that there's an awful lot of button-pressing just to get anything done. It is possible to make a shortcut button to get from the map screen to virtually any other navigation / iGo screen, if you know the trick. Personally, I use the Favorites a lot, and it was annoying to have to push Menu, then Destination, then Favorites. (No wonder they want you to be in Park to do anything - you have to press so many buttons and read so many screens!) In the example below, I'm going to make a display function (specifically, the Clock) become a clickable button by adding a bit of code

x=### is the value in pixels from the left side of the screen to the left edge of the text. y=### is the value in pixels from the top of the screen to the top edge of the text. w=### is the width of the text in pixels (handy for centring or right-justifying) z=### is the 'layer' to get stuff above other stuff. Higher z = more visible. Useful for putting text ontop of background graphics. h=### is the height of the text in pixels (handy for vertical alignment) Cheers! edited to add: All of which means, to move the text up, make the Y number smaller.

The dot is your true GPS position. The arrow is the snapped-to-road position. If the snap-to-road is turned off, it would show you as being offroad somewhere. I get that going into parking lots etc, the dot would show me actually in the parking lot while the arrow would bounce around from road to road trying to lock me to something. That's why I wanted to disable the snap-to-road thing.

Sorry - I forgot there were 3 more lines to comment out: ;runif nVehicle 5 'rdkeepposon.enable, rdkeepposoff.enable' ;else_runif nVehicle 6 'rdkeepposon.enable, rdkeepposoff.enable' ;else_run 'rdkeepposon.disable, rdkeepposoff.disable' When those lines are not commented, they disable the keep gps on road unless your vehicle is a bike or pedestrian. Comment them out to enable the buttons for all vehicles.

The images are in the Images.Res file in My Flash Drive\APL The program that displays the information is not part of the iGo software. I believe this is the command that launches it: EXEC "other.pioneer.postmessage" "AV" "WM_APP_AV_IGOMAP" 1 That line is in data.zip\ui_pioneer\common\ui\navigatemap.ui As far as I have seen, there's no way to move it around, you can just suppress it by commenting out that line.

Well I tried those variables this morning, and it didn't pitch any errors, but it didn't display anything either. This means that either the variables I guessed at don't actually exist, or that the textmodel I used is incorrect for the type of data in the variables. I'll test again with different textmodels and see if anything turns up. I'm sure there must be a way to display something, it's just a matter of finding the right variable and matching textmodel. Cheers!

I've been looking through the executable and found two possibilities. I'll test them in the morning. There is a "ZOOM" command/variable, which I'm going to try accessing as map.ZOOM (based on the zoombar being map.ZOOMCONTROL). There is also a "nZoomLevel" variable. I'll see if either of them produce any output. It's possible that even if we find a variable, it won't give us a friendly output, just a relative integer (like the heading does). Although that might be good enough, if you don't need the actual scale, just a relative number. Either way I'll let you know what I find.

I would love this function too - personally I find it much easier to read and understand, than the zoom bar (which I found small and hard to read).

pancho: The XM, HD, and Sirius stuff all seems to connect through the IP Bus cable. Does the F500 have an IP Bus port? That'd be the first thing to look into, if it has the port then it might be feasable. Please note though that so far most of the success has been in the navigation software, the AV stuff remains fairly closed to us. Vorian: To gain access to that function, I had to override the route settings screen and force the unit to give the F500's setting screen. If you edit data.zip\ui_pioneer\common\ui\settings.ui do a search through it for these lines: ;---746 or 749? runif

The BMP files that you cannot open/view are compressed. You need to uncompress them in order to view or edit them. There is a tool called MioMap BMP Tool (search the forums, there's a link to it somewhere). With it, you can open and uncompress the BMP to work with it, and then recompress it when you're done. Cheers!

I 'enabled' MSND on my F700 and it came up on the screen without errors. I went into the MSND Status screen, and I got the 'Connecting to MSN Direct' box. After about 5 minutes I gave up and closed it. I've read that it can take 5 or 10 minutes for that screen to actually connect, but to be honest I don't know if it'd actually work. From what I understand, there is some hardware required in order to make MSND function and if that's the case, the F700 probably isn't capable. I can't see them adding hardware that's not going to be used. What's odd (to me) is that the thing didn't come b

Potentially, yes. If you are comfortable booting your F900 into testmode, you could have a look and confirm that the software is actually there. Look in My Flash Drive\APL2\VBT and see what all is in there. If you find all the software and related files in there, then that would support my belief that the units all share identical software. The question then becomes, how exactly do we activate or access it -- without messing up other things.

I just found something else, also in the scheme zip file, colour.ini (and colour3d.ini) In the "Label Colors" section. The pioneer_blue_night does not have an entry for "label_poi" but I've seen that entry in other places. I'm going to add that entry on mine and see if this causes the POIs to get the names to appear. I won't actually test till tomorrow morning... not running out to the car to test it tonight.

If you've got a link handy to a skin with those functions active, could you post it? I wouldn't mind downloading and having a look through it too. Places to look, aside from project_config, would be in the map colour schemes. They're not in data.zip (or maybe they are...on the Pioneer they aren't) but they do contain the map colour settings, and the text display info for street names. Edited to add: I found this in Pioneer_blue_night.zip\color.ini: [userpoi] font="tahoma" fontsize=10 color=255,255,255 But it doesn't display the text tags, so it doesn't really help...

I have the F700 and it also says 746: type="PIONEER746UC" From following the scripting code, I can see that a type 746uc does not have access to msnd whereas a 747uc or 749uc do have access to msnd. Further research shows that the 746 and 747 share the same 'route settings' screen but the 749 'route settings' screen is different. I downloaded the F500 manual and compared, and the 749 'route settings' menu matches what's in the F500 manual. Hence my belief that the 746 is the F700, 747 is the F900 & F90, and 749 is the F500. Edited for typos.

That would be very nice to have those functions activated!