Modify your navigation system
true, true
heared that couple pages back. Wondering if anyone else figured it out.
...
Bysin, i would love to try it out. unfortunatly i do not own a TSX nor know anyone (in 'person') with a TSX, let alone a 2006 model.
As a matter of fact i do not even own a car with navigation...the only reason i ask, is because i am interested.
heared that couple pages back. Wondering if anyone else figured it out.
...
Bysin, i would love to try it out. unfortunatly i do not own a TSX nor know anyone (in 'person') with a TSX, let alone a 2006 model.
As a matter of fact i do not even own a car with navigation...the only reason i ask, is because i am interested.
Advanced
Joined: Jan 2004
Posts: 88
Likes: 2
From: Tucson, AZ
Originally Posted by Tintin
true, true
heared that couple pages back. Wondering if anyone else figured it out.
...
Bysin, i would love to try it out. unfortunatly i do not own a TSX nor know anyone (in 'person') with a TSX, let alone a 2006 model.
As a matter of fact i do not even own a car with navigation...the only reason i ask, is because i am interested.
heared that couple pages back. Wondering if anyone else figured it out.
...
Bysin, i would love to try it out. unfortunatly i do not own a TSX nor know anyone (in 'person') with a TSX, let alone a 2006 model.
As a matter of fact i do not even own a car with navigation...the only reason i ask, is because i am interested.
What Up Peeps, So has anyone on here hacked into their 03 Navigation System? Or does anyone know if its even possible? I have an 03 TL Type S with Navi. I would love to have those bmp images on my screen.
So I've finally taken the time to read this thread in it's entirety... I wish I could come away with more useful info after reading the 47 pages of posts, but I suppose that's the price for free information.
I have read about the SH-4 that we're using from the Hardware and Programming manual from http://www.renesas.com/. Our memory is limited to 4 gigs, so we've got plenty of room to expand. The MMU allows mapping to devices which seems to tie in to how the XIP BIN files are "pre" mapped to memory. My hunch is that the nag screen is read straight off the original DVD and forgotten immediatly after you click OK, since it would do nothing but waste precious memory to do otherwise. This behavior would also explain how people have simply overwritten the nag text, updated the background, replaced the dvd and seen no change in the nag but a changed background. So if we have control of the background we may be able to control the program loading. Then our only hope to remove the nag screen and remain with the stock DVD is to write a new part of the loader in the flash that safely skips the part that brings up the nag screen... assuming the startup sequence is not entirely dictated by the hardcoded files on the original DVD. We really need to network to this system.
After trying both UDF and ISO format for my TDK CD-RW's and having my Navi DVD reader fail to read I've decided to put my entire focus onto creating a test bench setup. Whether that means ripping out my Navi and setting it up on my desk here (which will be a pain in the ass for keeping all the CAN systems happy, power, display unit, etc), or a software simulator (much preferred, anyone seen the windows CE sh-4 emulator lying around? does it even exist? I know the generic CE emulator exists... perhaps I should just test on that and have the two different hardware targets. It seems to be set up this way within WinCE 5.0 dev tools...) or something totally different altogether. There is no point to hacking the code when we don't even know what part of the memory we can edit. Also, the sooner we get a network communication setup, the sooner we can all hack away comfortably instead of filling new landfills with burnt CDs and DVDs. There is a tcpstk.dll, so maybe there is hope. I will go research some more then start the arduous process of learning M$ development software.
Cheers.
<edit, minor grammar and stuff>
I have read about the SH-4 that we're using from the Hardware and Programming manual from http://www.renesas.com/. Our memory is limited to 4 gigs, so we've got plenty of room to expand. The MMU allows mapping to devices which seems to tie in to how the XIP BIN files are "pre" mapped to memory. My hunch is that the nag screen is read straight off the original DVD and forgotten immediatly after you click OK, since it would do nothing but waste precious memory to do otherwise. This behavior would also explain how people have simply overwritten the nag text, updated the background, replaced the dvd and seen no change in the nag but a changed background. So if we have control of the background we may be able to control the program loading. Then our only hope to remove the nag screen and remain with the stock DVD is to write a new part of the loader in the flash that safely skips the part that brings up the nag screen... assuming the startup sequence is not entirely dictated by the hardcoded files on the original DVD. We really need to network to this system.
After trying both UDF and ISO format for my TDK CD-RW's and having my Navi DVD reader fail to read I've decided to put my entire focus onto creating a test bench setup. Whether that means ripping out my Navi and setting it up on my desk here (which will be a pain in the ass for keeping all the CAN systems happy, power, display unit, etc), or a software simulator (much preferred, anyone seen the windows CE sh-4 emulator lying around? does it even exist? I know the generic CE emulator exists... perhaps I should just test on that and have the two different hardware targets. It seems to be set up this way within WinCE 5.0 dev tools...) or something totally different altogether. There is no point to hacking the code when we don't even know what part of the memory we can edit. Also, the sooner we get a network communication setup, the sooner we can all hack away comfortably instead of filling new landfills with burnt CDs and DVDs. There is a tcpstk.dll, so maybe there is hope. I will go research some more then start the arduous process of learning M$ development software.
Cheers.
<edit, minor grammar and stuff>
Originally Posted by inca
So I've finally taken the time to read this thread in it's entirety... I wish I could come away with more useful info after reading the 47 pages of posts, but I suppose that's the price for free information.
I have read about the SH-4 that we're using from the Hardware and Programming manual from http://www.renesas.com/. Our memory is limited to 4 gigs, so we've got plenty of room to expand. The MMU allows mapping to devices which seems to tie in to how the XIP BIN files are "pre" mapped to memory. My hunch is that the nag screen is read straight off the original DVD and forgotten immediatly after you click OK, since it would do nothing but waste precious memory to do otherwise. This behavior would also explain how people have simply overwritten the nag text, updated the background, replaced the dvd and seen no change in the nag but a changed background. So if we have control of the background we may be able to control the program loading. Then our only hope to remove the nag screen and remain with the stock DVD is to write a new part of the loader in the flash that safely skips the part that brings up the nag screen... assuming the startup sequence is not entirely dictated by the hardcoded files on the original DVD. We really need to network to this system.
After trying both UDF and ISO format for my TDK CD-RW's and having my Navi DVD reader fail to read I've decided to put my entire focus onto creating a test bench setup. Whether that means ripping out my Navi and setting it up on my desk here (which will be a pain in the ass for keeping all the CAN systems happy, power, display unit, etc), or a software simulator (much preferred, anyone seen the windows CE sh-4 emulator lying around? does it even exist? I know the generic CE emulator exists... perhaps I should just test on that and have the two different hardware targets. It seems to be set up this way within WinCE 5.0 dev tools...) or something totally different altogether. There is no point to hacking the code when we don't even know what part of the memory we can edit. Also, the sooner we get a network communication setup, the sooner we can all hack away comfortably instead of filling new landfills with burnt CDs and DVDs. There is a tcpstk.dll, so maybe there is hope. I will go research some more then start the arduous process of learning M$ development software.
Cheers.
<edit, minor grammar and stuff>
I have read about the SH-4 that we're using from the Hardware and Programming manual from http://www.renesas.com/. Our memory is limited to 4 gigs, so we've got plenty of room to expand. The MMU allows mapping to devices which seems to tie in to how the XIP BIN files are "pre" mapped to memory. My hunch is that the nag screen is read straight off the original DVD and forgotten immediatly after you click OK, since it would do nothing but waste precious memory to do otherwise. This behavior would also explain how people have simply overwritten the nag text, updated the background, replaced the dvd and seen no change in the nag but a changed background. So if we have control of the background we may be able to control the program loading. Then our only hope to remove the nag screen and remain with the stock DVD is to write a new part of the loader in the flash that safely skips the part that brings up the nag screen... assuming the startup sequence is not entirely dictated by the hardcoded files on the original DVD. We really need to network to this system.
After trying both UDF and ISO format for my TDK CD-RW's and having my Navi DVD reader fail to read I've decided to put my entire focus onto creating a test bench setup. Whether that means ripping out my Navi and setting it up on my desk here (which will be a pain in the ass for keeping all the CAN systems happy, power, display unit, etc), or a software simulator (much preferred, anyone seen the windows CE sh-4 emulator lying around? does it even exist? I know the generic CE emulator exists... perhaps I should just test on that and have the two different hardware targets. It seems to be set up this way within WinCE 5.0 dev tools...) or something totally different altogether. There is no point to hacking the code when we don't even know what part of the memory we can edit. Also, the sooner we get a network communication setup, the sooner we can all hack away comfortably instead of filling new landfills with burnt CDs and DVDs. There is a tcpstk.dll, so maybe there is hope. I will go research some more then start the arduous process of learning M$ development software.
Cheers.
<edit, minor grammar and stuff>
Originally Posted by inca
So I've finally taken the time to read this thread in it's entirety... I wish I could come away with more useful info after reading the 47 pages of posts, but I suppose that's the price for free information.
I have read about the SH-4 that we're using from the Hardware and Programming manual from http://www.renesas.com/. Our memory is limited to 4 gigs, so we've got plenty of room to expand. The MMU allows mapping to devices which seems to tie in to how the XIP BIN files are "pre" mapped to memory. My hunch is that the nag screen is read straight off the original DVD and forgotten immediatly after you click OK, since it would do nothing but waste precious memory to do otherwise. This behavior would also explain how people have simply overwritten the nag text, updated the background, replaced the dvd and seen no change in the nag but a changed background. So if we have control of the background we may be able to control the program loading. Then our only hope to remove the nag screen and remain with the stock DVD is to write a new part of the loader in the flash that safely skips the part that brings up the nag screen... assuming the startup sequence is not entirely dictated by the hardcoded files on the original DVD. We really need to network to this system.
After trying both UDF and ISO format for my TDK CD-RW's and having my Navi DVD reader fail to read I've decided to put my entire focus onto creating a test bench setup. Whether that means ripping out my Navi and setting it up on my desk here (which will be a pain in the ass for keeping all the CAN systems happy, power, display unit, etc), or a software simulator (much preferred, anyone seen the windows CE sh-4 emulator lying around? does it even exist? I know the generic CE emulator exists... perhaps I should just test on that and have the two different hardware targets. It seems to be set up this way within WinCE 5.0 dev tools...) or something totally different altogether. There is no point to hacking the code when we don't even know what part of the memory we can edit. Also, the sooner we get a network communication setup, the sooner we can all hack away comfortably instead of filling new landfills with burnt CDs and DVDs. There is a tcpstk.dll, so maybe there is hope. I will go research some more then start the arduous process of learning M$ development software.
Cheers.
<edit, minor grammar and stuff>
I have read about the SH-4 that we're using from the Hardware and Programming manual from http://www.renesas.com/. Our memory is limited to 4 gigs, so we've got plenty of room to expand. The MMU allows mapping to devices which seems to tie in to how the XIP BIN files are "pre" mapped to memory. My hunch is that the nag screen is read straight off the original DVD and forgotten immediatly after you click OK, since it would do nothing but waste precious memory to do otherwise. This behavior would also explain how people have simply overwritten the nag text, updated the background, replaced the dvd and seen no change in the nag but a changed background. So if we have control of the background we may be able to control the program loading. Then our only hope to remove the nag screen and remain with the stock DVD is to write a new part of the loader in the flash that safely skips the part that brings up the nag screen... assuming the startup sequence is not entirely dictated by the hardcoded files on the original DVD. We really need to network to this system.
After trying both UDF and ISO format for my TDK CD-RW's and having my Navi DVD reader fail to read I've decided to put my entire focus onto creating a test bench setup. Whether that means ripping out my Navi and setting it up on my desk here (which will be a pain in the ass for keeping all the CAN systems happy, power, display unit, etc), or a software simulator (much preferred, anyone seen the windows CE sh-4 emulator lying around? does it even exist? I know the generic CE emulator exists... perhaps I should just test on that and have the two different hardware targets. It seems to be set up this way within WinCE 5.0 dev tools...) or something totally different altogether. There is no point to hacking the code when we don't even know what part of the memory we can edit. Also, the sooner we get a network communication setup, the sooner we can all hack away comfortably instead of filling new landfills with burnt CDs and DVDs. There is a tcpstk.dll, so maybe there is hope. I will go research some more then start the arduous process of learning M$ development software.
Cheers.
<edit, minor grammar and stuff>

Originally Posted by JAM
Perhaps, this may help you:




Since I won't be holding my breath on that, I'll be ordering the proper tools to remove my Navi soon.
In the mean time I will read through IDA and learn what I can.
Cheers
Originally Posted by inca
So I've finally taken the time to read this thread in it's entirety... I wish I could come away with more useful info after reading the 47 pages of posts, but I suppose that's the price for free information.
I have read about the SH-4 that we're using from the Hardware and Programming manual from http://www.renesas.com/. Our memory is limited to 4 gigs, so we've got plenty of room to expand. The MMU allows mapping to devices which seems to tie in to how the XIP BIN files are "pre" mapped to memory. My hunch is that the nag screen is read straight off the original DVD and forgotten immediatly after you click OK, since it would do nothing but waste precious memory to do otherwise. This behavior would also explain how people have simply overwritten the nag text, updated the background, replaced the dvd and seen no change in the nag but a changed background. So if we have control of the background we may be able to control the program loading. Then our only hope to remove the nag screen and remain with the stock DVD is to write a new part of the loader in the flash that safely skips the part that brings up the nag screen... assuming the startup sequence is not entirely dictated by the hardcoded files on the original DVD. We really need to network to this system.
After trying both UDF and ISO format for my TDK CD-RW's and having my Navi DVD reader fail to read I've decided to put my entire focus onto creating a test bench setup. Whether that means ripping out my Navi and setting it up on my desk here (which will be a pain in the ass for keeping all the CAN systems happy, power, display unit, etc), or a software simulator (much preferred, anyone seen the windows CE sh-4 emulator lying around? does it even exist? I know the generic CE emulator exists... perhaps I should just test on that and have the two different hardware targets. It seems to be set up this way within WinCE 5.0 dev tools...) or something totally different altogether. There is no point to hacking the code when we don't even know what part of the memory we can edit. Also, the sooner we get a network communication setup, the sooner we can all hack away comfortably instead of filling new landfills with burnt CDs and DVDs. There is a tcpstk.dll, so maybe there is hope. I will go research some more then start the arduous process of learning M$ development software.
Cheers.
<edit, minor grammar and stuff>
I have read about the SH-4 that we're using from the Hardware and Programming manual from http://www.renesas.com/. Our memory is limited to 4 gigs, so we've got plenty of room to expand. The MMU allows mapping to devices which seems to tie in to how the XIP BIN files are "pre" mapped to memory. My hunch is that the nag screen is read straight off the original DVD and forgotten immediatly after you click OK, since it would do nothing but waste precious memory to do otherwise. This behavior would also explain how people have simply overwritten the nag text, updated the background, replaced the dvd and seen no change in the nag but a changed background. So if we have control of the background we may be able to control the program loading. Then our only hope to remove the nag screen and remain with the stock DVD is to write a new part of the loader in the flash that safely skips the part that brings up the nag screen... assuming the startup sequence is not entirely dictated by the hardcoded files on the original DVD. We really need to network to this system.
After trying both UDF and ISO format for my TDK CD-RW's and having my Navi DVD reader fail to read I've decided to put my entire focus onto creating a test bench setup. Whether that means ripping out my Navi and setting it up on my desk here (which will be a pain in the ass for keeping all the CAN systems happy, power, display unit, etc), or a software simulator (much preferred, anyone seen the windows CE sh-4 emulator lying around? does it even exist? I know the generic CE emulator exists... perhaps I should just test on that and have the two different hardware targets. It seems to be set up this way within WinCE 5.0 dev tools...) or something totally different altogether. There is no point to hacking the code when we don't even know what part of the memory we can edit. Also, the sooner we get a network communication setup, the sooner we can all hack away comfortably instead of filling new landfills with burnt CDs and DVDs. There is a tcpstk.dll, so maybe there is hope. I will go research some more then start the arduous process of learning M$ development software.
Cheers.
<edit, minor grammar and stuff>
Originally Posted by bysin
There isnt a Windows CE SH-4 emulator, you can only emulate programs specificially built for the emulator in visual studio embedded. Even if somehow you made a SH-4 virtual machine to run this on, there are so many device drivers you'd have to emulate which would make it almost impossible. If you can rip your navi system out of your car and setup some type of test unit next to your computer, that would be the next step in replacing the stock executables with aftermarket one.
Man. You're a smart ass kid. I didnt understand anything that you said except for "If you can rip your navi system out of your car and setup some type of test unit next to your computer, that would be the next step in replacing the stock executables with aftermarket one." But the program you made is great. I've had like 6 backscreen since you came up with the program. Wife likes it. Thanks again.
Originally Posted by bysin
There isnt a Windows CE SH-4 emulator, you can only emulate programs specificially built for the emulator in visual studio embedded. Even if somehow you made a SH-4 virtual machine to run this on, there are so many device drivers you'd have to emulate which would make it almost impossible. If you can rip your navi system out of your car and setup some type of test unit next to your computer, that would be the next step in replacing the stock executables with aftermarket one.
As for the visual studio emulator, it seems like just an x86 Windows CE emulator. So anything you want to test on WinCE in software you have to cross compile for both your target application (SH-4) and the native x86. What a drag. Though you mentioned earlier something about taking the SH-4 dlls and such and using those to make a "platform" of some kind to develop with. Did you have any luck with this?
Most importantly, did you ever get deep enough into the loader to find out what exactly gets loaded into flash and what stuff is left to be loaded off the DVD when needed? Does the entire BIN file get conditionally loaded into flash based on version numbering/timestamping/package signing(crypto)?
I'm also curious about the people who've been trying to backup the navi discs... did anyone ever find out if it is a media problem (DL vs single layer DVD+/-R) vs protection problem? That is to say, if you remove a significant portion of the navi data and squeeze it down to 4.4 gigs for single layer, does it work now? If it doesn't, then we're in trouble until this obstacle has been overcome.
Cheers,
inca
bysin and inca,
I just got an '06 Honda Accord with Navi. I don't know about donating a unit, but if you guys post your paypal, I donate some $10. It's not much, but if everyone using it donated... well milliondollarhompage ... you guys know.
Thanks for the work you've put into it, I'll keep an eye on this thread. I've got my profile open to receiving e-mails, so I would be happy to do some testing if needed.
I just got an '06 Honda Accord with Navi. I don't know about donating a unit, but if you guys post your paypal, I donate some $10. It's not much, but if everyone using it donated... well milliondollarhompage ... you guys know.
Thanks for the work you've put into it, I'll keep an eye on this thread. I've got my profile open to receiving e-mails, so I would be happy to do some testing if needed.
Originally Posted by pheobo
bysin and inca,
I just got an '06 Honda Accord with Navi. I don't know about donating a unit, but if you guys post your paypal, I donate some $10. It's not much, but if everyone using it donated... well milliondollarhompage ... you guys know.
Thanks for the work you've put into it, I'll keep an eye on this thread. I've got my profile open to receiving e-mails, so I would be happy to do some testing if needed.
I just got an '06 Honda Accord with Navi. I don't know about donating a unit, but if you guys post your paypal, I donate some $10. It's not much, but if everyone using it donated... well milliondollarhompage ... you guys know.
Thanks for the work you've put into it, I'll keep an eye on this thread. I've got my profile open to receiving e-mails, so I would be happy to do some testing if needed.
I'm not sure how dumb this is, but do Acura Navi's ever get into junk yards? A used (but functioning) tsx navi of similar year is just as valuable as the ~$6000 worth of crap from the parts site.
I won't collect money for such a thing because I don't want to promise results and I absolutely would hate to try to refund people for failng. As much as this pains me to say, we need to be honest here. It may just turn out that our schemes are farther reaching than the individual ability of each person working on this hack. =\ Does anyone speak Japanese? We should try and get an original designer to help us out. =)
In any case, we press onward. Cheers.
I won't collect money for such a thing because I don't want to promise results and I absolutely would hate to try to refund people for failng. As much as this pains me to say, we need to be honest here. It may just turn out that our schemes are farther reaching than the individual ability of each person working on this hack. =\ Does anyone speak Japanese? We should try and get an original designer to help us out. =)
In any case, we press onward. Cheers.
If anyone is willing to do a little electronics legwork for me we may be able to make progress while my weekend freetime dwindles to new all-time lows. I just got home from work a little bit ago (yeah, it was Saturday...) and I decided to take out my pen light and check out the Alpine Navi box once more. I saw an 8 pin outlet on the unit itself, and I saw a two pin plug tapped to the wiring harness. In the XIP BIN files I saw dll's for tcp and dhcp so I got to thinking about ethernet. Our computer ethernet is also 8 pin... so maybe the unused outlet on the Navi unit is ethernet? Perhaps I missed this part of the thread earlier (or maybe it was just mentioned and never resolved), but there is no way that they'd produce a standalone WinCE hardware unit without some sort of standardized communication for development, debugging, and quickly running binaries. So here are two things I would like someone to investigate (call it out if you plan on doing it so others know):
1) Take apart the navi electronics unit and find out what chip(s) interface with the 8 pin outlet. This will at most require a multimeter to check connectivity, and at the least require just a quick look and perhaps the use of a pointer to follow traces on the circuit board.
2) Find out where the two pin plug tapped in the wire harness coming out of the navi goes. If it indeed goes into the navi unit it's probably some kind of serial interface. It could be a CAN bus tap/monitor or even gift from the gods like an RS232 connection to the shell.exe in the navi software... or something that has nothing to do with what we want.
If no one claims any of these by Sunday night I'll do'em and post what I find or don't find.
Cheers
1) Take apart the navi electronics unit and find out what chip(s) interface with the 8 pin outlet. This will at most require a multimeter to check connectivity, and at the least require just a quick look and perhaps the use of a pointer to follow traces on the circuit board.
2) Find out where the two pin plug tapped in the wire harness coming out of the navi goes. If it indeed goes into the navi unit it's probably some kind of serial interface. It could be a CAN bus tap/monitor or even gift from the gods like an RS232 connection to the shell.exe in the navi software... or something that has nothing to do with what we want.
If no one claims any of these by Sunday night I'll do'em and post what I find or don't find.
Cheers
I took some pictures, but I'm afraid they will do little to show more than the general situation with the main navi circuit board. I'm also not sure where to post them and such, so for now they'll be available on request, just PM me.
I started an excel spreadsheet of the IC's on the board but it seems I can't attach files to posts so... here goes nothin for excel to html conversion... all right, that failed miserably. No cutting and pasting for me.
...
So I started yet another phpBB just for this. Here is the excel spreadsheet:
http://www.electronicdisposition.com...wtopic.php?t=4
Executive Summary:
SH-4 7750S - 208 pin Renesas microprocessor
H8S/2238 - 100 pin 256KB ROM, 16KB RAM, 16 bit microcomputer
Marubun 144 pin PCMCIA I/F
Spansion (AMD/Fujitsu) - 48 pin Flash memory, 16Mbit (2MB).
Hynix - 54 pin DRAM, 8MB each (8 total => 64MB total)
Hynix - 86 pin 183MHz, 8MB
Some weird, unidentifiable Mitsubishi chips (IC's 102 and 501)
And lots more...
Cheers
I started an excel spreadsheet of the IC's on the board but it seems I can't attach files to posts so... here goes nothin for excel to html conversion... all right, that failed miserably. No cutting and pasting for me.
...
So I started yet another phpBB just for this. Here is the excel spreadsheet:
http://www.electronicdisposition.com...wtopic.php?t=4
Executive Summary:
SH-4 7750S - 208 pin Renesas microprocessor
H8S/2238 - 100 pin 256KB ROM, 16KB RAM, 16 bit microcomputer
Marubun 144 pin PCMCIA I/F
Spansion (AMD/Fujitsu) - 48 pin Flash memory, 16Mbit (2MB).
Hynix - 54 pin DRAM, 8MB each (8 total => 64MB total)
Hynix - 86 pin 183MHz, 8MB
Some weird, unidentifiable Mitsubishi chips (IC's 102 and 501)
And lots more...
Cheers
I wanna make a correction to a previous post. I said before that the PCMCIA slot in the back was only used to save log files to. I found out that this isnt true, It can also be used to save backups of your personal addresses and calendar. Its a hidden feature in PIM.exe that allows you to do this.
Also, I'm about to release another GUI version that lets you completely modify the colors of the map perminatly for both night and day.
Also, I'm about to release another GUI version that lets you completely modify the colors of the map perminatly for both night and day.
I thought I was keeping up, did I miss how to make the backup? I will be trading in my 2004 & 2005 accords this spring and this would be very helpful. Is there a way to upload them to my 2006 also?
Thanks,
RS
Thanks,
RS
Originally Posted by bysin
I wanna make a correction to a previous post. I said before that the PCMCIA slot in the back was only used to save log files to. I found out that this isnt true, It can also be used to save backups of your personal addresses and calendar. Its a hidden feature in PIM.exe that allows you to do this.
Also, I'm about to release another GUI version that lets you completely modify the colors of the map perminatly for both night and day.
Also, I'm about to release another GUI version that lets you completely modify the colors of the map perminatly for both night and day.
Maybe this helps if it wasn't already common knowledge here.
From:
http://www.v6performance.net/forums/...2&page=1&pp=30
P.S. And um, I can't deal with hitting "ok" everytime. I may have to break down and buy the nag removers from: http://kptechnologies.com/ I'm still watching this thread maybe Inca or Bysin will make some progress on the 06 versions. Anyone know of other options until the hacks come out?
From:
http://www.v6performance.net/forums/...2&page=1&pp=30
Originally Posted by JCIMS
2. This has to be in the manual...i just discovered it by playing around. Press the 'Map', 'Menu' and 'Cancel' buttons simultaneously for a few seconds. You get into a diagnostic mode that lets you check all sorts of stuff out. I'm sure you could hose things up if you mess around with some of the settings, but it's fun to look at the 'Trip Information', which shows fuel use, 'GPS Info', which shows how many sat's you're tracking and your coords + elevation, and the 'yaw' indicator, which is insanely sensitive.
Originally Posted by pheobo
Originally Posted by JCIMS
2. This has to be in the manual...i just discovered it by playing around. Press the 'Map', 'Menu' and 'Cancel' buttons simultaneously for a few seconds. You get into a diagnostic mode that lets you check all sorts of stuff out. I'm sure you could hose things up if you mess around with some of the settings, but it's fun to look at the 'Trip Information', which shows fuel use, 'GPS Info', which shows how many sat's you're tracking and your coords + elevation, and the 'yaw' indicator, which is insanely sensitive.
To Answer Your Question About The Hack Working On The Cl Navi. I Dont Think It Does. I Have An 03 Tl Type S With Navi, And I Think Those Two Cars Have The Same Navi System. I Have Already Tried It And It Doesnt Work. All These Hacks Only Apply To The New Navi Systems That Come With The Tsx, Tl, And Accords. I Know It Sucks Ass. Those Bmp Images Look Kool.
Originally Posted by deejayceas
To Answer Your Question About The Hack Working On The Cl Navi. I Dont Think It Does. I Have An 03 Tl Type S With Navi, And I Think Those Two Cars Have The Same Navi System. I Have Already Tried It And It Doesnt Work. All These Hacks Only Apply To The New Navi Systems That Come With The Tsx, Tl, And Accords. I Know It Sucks Ass. Those Bmp Images Look Kool.
Originally Posted by huckleberry
bysin, can you use this ?
bysin, can you use something like this for your R&D ?
someone is trying to sell the whole Navi system
http://photobucket.com/albums/b265/khyberfx/navi/
I'm guessing we can start a donation drive to get this thing for you so you can do it the right way.
he blurted $3000 but I guess it's quite negotiable
someone is trying to sell the whole Navi system
http://photobucket.com/albums/b265/khyberfx/navi/
I'm guessing we can start a donation drive to get this thing for you so you can do it the right way.

he blurted $3000 but I guess it's quite negotiable
Originally Posted by bysin
Anyone here with hardware skills think they can jimmy a converter for that socket and connect it to a vga and power outlet of an external device, such as a dvd player? On the software side, the rear view camera drivers are all there and functional.
hehe now I think about it again - I suppose if current can be detected in one or more of the pins when gear in [R] and not in [D]...then most likely it's for backup cam
(Ridgelines OEM camera does NOT require a separate power supply)
Well, we wouldn't need to use the unused 16-pin socket for a VGA screen since the navi screen is essentially VGA (RGB signal with sync) and we could quite easily convert that into a VGA signal. As for an external DVD drive... I think the only way we'd be able to do that is with a PCMCIA (PC Card) to USB converter or something like that. I looked in my electrical service manual and the extra 16-pin socket isn't even mentioned in it so no pin out.


it does not work on 2006 - lots of change to the system for 06.

