Jump to content


  • Content count

  • Joined

  • Last visited

About Stephanie

  • Rank

Profile Information

  • Location
    http://www.felesmagus.com/stuff/steph_data.zip for my current files
  • Interests
    Almost everything, one thing at a time.
  1. wiring help!

    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!
  2. Faster Button Responses!

  3. Changing the fonts/colors thread-PICS

    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.
  4. Some Safety Tips re. Hacking

    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 data-1.zip or whatever). Also, keep a pristine, untouched, original copy of it on your computer somewhere too. When it comes to backups, you can never have too many. Any other files you might be modifying (sys.txt, the colour scheme.zip files, etc) you should keep backed up. If you have the time, use a 2+ GB SD card and back up the whole nav unit, if you want to be extra safe. #2 - Back Up Your Work! Every time you edit or change a file, at the very minimum keep a copy of the last good working copy. In other words if you've eliminated the blue boxes already, but now you're editing data.zip to try and add a button or change a graphic etc, always keep a copy of the last version you were using. This way if things get messed up and your new project doesn't pan out you at least have a copy of the last known-good data.zip so you can restore to that. #3 - One Thing At A Time! I know it's a PITA to test every step, especially if you're working on a desktop then have to go out to the car, boot to testmode, copy the file, boot again, etc etc. It is very tempting to save time by doing several changes at once. The problem is that if you've made a mistake, you won't know which change has the problem. You will spend more time trying to figure out which thing blew up, than you would have by going one step at a time. The navi's error messages do not tell you which file have the error, and aren't even very good about telling you what the error was. "Expected " was the error I got once for omitting a " in one of the files. #4 - Do Not Rush - Especially working in Testmode The touch screen is very, well, touchy. It is not accurate. Even after several calibrations, it is not accurate. It is very easy, even navigating with the stylus, to slip or make a mistake. Try tapping on "APL2" and accidentally dropping it into "APL" and see what happens when you reboot. I'm kidding. Seriously do not try doing this. #5 - Don't leave something half finished. If you're a busy person, trying to squeeze in some Avic hacking between a bunch of other distractions, it's easy to forget what you're doing, or forget that you have not completed some minor step in a project. Coupled with the PITA of running out to the car to do each test, it is tempting (for me at least) to sometimes do some work on the files, copy them to the SD card, then set it aside till the end of the day or the next morning, before testing it. Now if it doesn't work, try and remember just what the hell did I change / was I testing? Couple that with trying to do 2 or 3 things at once, and it's another recipe for trouble. ------ I've come up with these 5 tips because basically I've broken all of them except #1 at one time or another, and each one has come back to bite me in the behind at least once. Other than #1, if you ignore just one of these tips, it probably won't spell disaster. Particularily if you follow #2 - that way when things go wrong, you can always revert to the last good version. Ignore a few of these tips, and sooner or later you will find yourself with a navi that doesn't boot, constantly reboots, or runs but pitches errors all the time, while you aren't sure what you've done or where to start looking for the fix. For me, it's usually after days and days of problem-free hacking, when I think I'm "almost done" and I just want to make "one last change" that I get sloppy, and I get careless. Then I make some silly little mistake, compounded with not bothering to keep my last 'good' file (after all, I never needed to revert for the last 6 changes) and then Pow! Something goes wrong and I get that sinking feeling. Anyhow, hopefully others will learn from my experiences, and avoid their own sinking feelings. Cheers!
  5. SD Cards 16gb? What works....

    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.
  6. HOW TO: Variable/Function Reference Library

    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.
  7. SD Cards 16gb? What works....

    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.
  8. Numerical Zoom Scale?

    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 data is in some format that there's no text method for - the zoom is a very 'smooth' zoom, instead of large discrete steps, so it's probably a hex or binary thing...like 8 bits or 16 bits or something along those lines. Thinking of the way the zoombar reacted, it didn't just change text headings over a fixed-width scale, but the scale indicators changed size and the text headings moved around accordingly - so perhaps the best we could have hoped for would be a hex readout, like 1A or 4F or whatever... So I'm giving up - conceding defeat on this one. Same as with the car heading in degrees - for now I think it simply doesn't exist in there in a format we can use. edited to add: If I am correct, this is something that the iGo programmers would have to add - either a textmodel_hex model, or add a full_text method to the appropriate variable. Ditto for car heading, we have navigate.car_heading but the programmers would have to add a .full_text method that would perform the (simple) maths to turn the integer into a degrees readout.
  9. SD Cards 16gb? What works....

    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 ------>Song3.mp3 ---->Album2 (folder) ------>Song1.mp3 ------>Song2.mp3 ------>Song3.mp3 In other words, if the 'top' directory of the SD Card contains music, or contains a bunch of folders which themselves contain music, then it would be fine. But if the 'top' directory had no music, and the next level of directories also had no music, then it would simply give up and stop searching -- even if there was a hundred song files in a 3rd level directory.
  10. HOW TO: Variable/Function Reference Library

    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 to the end of it. This last bit here: onrelease='run sc_FindAddress' makes the clock something you can click, and when you click it, it launches the Destination / Find By Address screen. By adding an onrelease='' to any text you can make it clickable. You can add it to sprites too (although technically I think you should turn the SPRITE into a BUTTON when you do that.) You can even add your own clickable Text and Buttons, you aren't limited to just making existing stuff clickable. What follows, are a list of things you can do with this trick. (This is not a comprehensive list - just a few things I've found useful.) Show the GPS Status Screen: onrelease='nextstate st_SettingGPS' Go to the Settings menu: onrelease='nextstate st_navisettings' Go to the Find By Address screen: onrelease='run sc_FindAddress' Go to the Find By POI screen: onrelease='run sc_FindPOI' Go to the Find Favorites screen: onrelease='run sc_FindFavorite' Go to the History screen: onrelease='run sc_FindHistory' Delete Route: onrelease='run sc_btnARM_Delete_OnRelease' Show Route Info: onrelease='run sc_btnARM_Info_OnRelease' Go Home: onrelease='run sc_btnAMM_ReturnHome_OnRelease' Go to the Manage POI screen: onrelease='run sc_btnAMDM_POI_onRelease' Go to the MSND main screen: onrelease='nextstate st_MsndMain' Speak the next navigation command: onrelease='SAYNEXTCOMMAND' For people wanting to know how to find these things, the answer is simple - just find the menu where there's a function you want to make a shortcut of, look at the related 800_480.ui file, find the button, and see what the onrelease function is. For example, if you want to make a shortcut to the MSND Weather screen, go to data.zip\ui_pioneer\800_480\ui\msnd_800_480.ui and open that in notepad. Search for 'weather', and find this code: The onrelease bit is there: onrelease='vIsWorldwideWeatherSelected.set 0, NEXTSTATE st_MsndWeatherList' So, that is the shortcut to get to the MSND weather page. That is how you find the 'shortcuts' to the various screens within the navigation software. Cheers! p.s. you may need to add USESEPARATEDSAFETYMODE=1 (or =0) in addition to the onrelease to make the buttons work - the safety mode thing is what enables / disables clickable buttons based on the parking brake or bypass. I've found mixed results where sometimes the safetymode thing is required and other times it isn't.
  11. Progress: Blue Boxes and Contacts

    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.
  12. Progress: Blue Boxes and Contacts

    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.
  13. They all seem to run the same software...

    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.
  14. AV Source on Map Screen

    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.
  15. Numerical Zoom Scale?

    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!