GeoffT

I would guess that the Shift up/down on the Sony stalk are commands 7 & 8 on the PAC. These would have done nothing up until firmware 3.

I use a Sony Stalk RMX4-S. With firmware 3.0 the ability to go up and down through radio presets has been added but not in the way most people wanted. Rather than making the normal up/down command in the radio mode go through the presets, that still scans up/down though the frequencies. To go up/down presets on the Sony Stalk you need to use the "shift" up/down commands (ie press the shift ring in while activiting up/down). In MP3/CD mode this "shift" up/down command goes up/down through the folders rather than next/previous track. This is a real shame as I think most people want the sam

OK, no problem. Can you confirm though that the Phone Status, Answer Call, and End Call functions all work when programmed to a button on your wheel. If so I will set up my variable resistor test remote again and try to find what resistance values make those commands work.

Is there any chance you could measure the resistance across the connector to the avic (between the tip and base ring) when the swi-ps is giving the answer and end call commands? Sorry I don't know how to. I didn't use any resistance on my unit. just 3 wire i install, red for ignition, black for ground. and white go to the steering control . then do the program that all, There will be a 3.5mm connector (like a headphone connector) that goes from the swi-ps into the back of the f-series. You would need to un-plug that and put an ohm-meter across the tip and base ring of that and then pre

Is there any chance you could measure the resistance across the connector to the avic (between the tip and base ring) when the swi-ps is giving the answer and end call commands?

If this really did work, this is big news! What function did you map to the CH button, and what exactly does it do on the f-series? Does the preset up/down work also? Edit - just found this review on crutchfield so I guess the preset answer is no "Nearly perfect Written By Tomas, Franklin, MA on Thursday, April 30, 2009 Just installed this in my 2008 Subaru Impreza. Simple to wire up with just three wires (white/black/red); programming took a couple of tries since you have to finish it within a few seconds. Working great immediately afterwards; button response had little to no l

Talk to PAC and ask them specifically about the f-series and telephone commands. I promise you this cannot work as I have tried every possible resistance value to the steering wheel remote connection and none of them are a telephone specific command. The only commands available to the steering wheel input are Vol+/-, Track(or Freq in Tuner mode)+/-, Mute,Source & Band. I am only trying to stop you wasting time and money.

OK I get that, but I presume that as you are posting it here, you are trying to control an F-series via the swi in your Honda? What I am saying is that even if your Honda had the steering wheel buttons (or if you created them) for phone status, answer call etc, the F-series will not action these commands in any case. Unless someone can hack the part of the F-series that processes the steering wheel commands, you are not going to be able to get this to work, no matter how many buttons you create or what the swi is capable off. Sorry, but you would be wasting your time trying to do this.

The F-series only responds to certain commands from the steering wheel remote input. I am not too sure what you mean by "It has new feature to control the bluetooth" for the swi-ps, but the bottom line is that no matter what the swi-ps is capable of, it is restricted by what the f-series is programmed to interpret. See the following thread for details of the commands that are available: viewtopic.php?f=34&t=22824

That is a good link and illustrates clearly how the Sony/Pioneer wired remote works. However,even when the sleeve and ring are connected together (which is what happens on the Sony RMX when you slide the up/down ring inwards) the preset up/down functions sadly do not work with the F series.

Yes, overall I'm happy with the RMX4. The limitations are at the Pioneer end not with the RMX4. I have always preferred a stalk to steering wheel controls as I find it easier and more intuative. Far easier to use without looking/thinking as it doesn't move about like a steering wheel!

What is the degree of diffuctly of having 2 different image.res files for day and night and somehow switching between them? Ideally triggered by the illumination power feed or failing that, when the map changes from day to night mode. I guess the system probably picks the image.res up when it boots, so it may be tricky to change dynamically, but with the ingenuity of some of the people on here, anything is possible. I thought it would be cool to have the button logos etc change from white in the day to red at night like they do on the dash in my VW.

I have done a search on this and can find plenty about changing the text colour in the maps but nothing about changing it in the AV menus for track/station info etc. Is AV screens text colour modifiable or is it hard coded into av.exe etc ?

I am not a programmer, so maybe this is a bit simplistic, but bear with me. Presumably each different part of the firmware has to interpret the commands from the remote in it's own way - eg the "next track" remote command is interpreted as "next track" by the MP3 player, but is interpreted as "up scan frequency" by the tuner. Can the tuner section firmware not just be re-programmed to interpret "next track"/"prev track" remote commands as next/prev preset instead? That would solve the problem for me as there is always the on screen buttons for tuning if required.

I am using a Sony RMX4 stalk to control my F700BT. As you know, all the Sony/Pioneer wired remotes do is put a different resistance between the tip and ground of the 3.5mm connector. The standard Sony commands are as follows: Resistance ......Sony............... AVIC (ohms)........Command.........Command 0...................Power...........Nothing 2077...............Source..........Source 4336...............Mute........... Mute 6429...............DSPL........... Next Track/ Next Frequency 8670...............Next Track.... Next Track/ Next Frequency 12000..............Prev Tr

You're welcome. I have read the explanation once, and can't say I quite understood it As far as I understand it (I could be wrong here, though), on startup, iGO will process whatever text files are there that are newer than the SPDB file (there's only one). If, later on, you put a new TXT file, it will recreate the SPDB from that file only. It does not touch the SPUD AFAI,K, so it is recommended to delete SPUD when you load new speedcam database... Thanks again. I think I get it now, even if I can't explain it very well

AFAIK if you put a speedcam.txt file the unit creates a spud file out of it, and then all other manually added speedcams are just stored in the memory, regarding the rest of your questions i'm not sure how the unit handles those TXT file is converted to SPDB file once. Manual additions and edits are stored in SPUD file. Thanks Boris. OK lets see if I've got it right, if I start with a TXT camera database, that is converted to SPDB on first boot up. This is stored on the system (in the same SPEEDCAM directory?). If I make any manual changes, that creates a SPUD file containing my

I am relatively new to this but have successfully loaded cmh928's excellent all-in-one mode. I just want to try to understand how exactly the speed cam files are stored and updated on the F series, so that when I get updated speedcam files I can add them to the system in the best way. I know that you can put either a speedcamtext.txt or a speedcam.spud file in the speedcam directory, but I am unsure as to what exactly the F series then does with those files. Does it read the txt or spud file everytime it boots, only once and then stores the information somewhere else or a combination

OK, I've now gone to Simple for the speed cam warnings, and that seems to only warn me when I'm approaching a camera above the limit as I want. But it warns me by means of a barking dog rather than a beep. I read on another thread that GTIMatt's mods had a bug that caused this to happen and that he has since fixed. Can I just download his latest version, and if so, what do I have to do with the files so as not to screw up anything else? Thanks

Thanks. I'll give that a try. On the subject of the bright red block, should that pop up on other screens (Tuner/Mp3 etc) or just when on the Map screen? Mine currently only shows when on the map screen.

I've created a speedcam.txt file based on my old tomtom file, added that and removed the SPUD file. The camera warnings now all work fine. cmh928's new files also solve the UK speedsign sticky issue, and the TMC is working great too. This now all works, and looks, much better than the original. There is still a "but" though! Unless I am missing something, it doesn't seem possible to be able to have speed cam warnings only when you are over the limit. i.e you can set the warning beeps to be active only when you are over the limit, but you still have to have a spoken warning as you app

It seems like the SPUD file must be the problem. I created a dummy camera in my road, as you suggested, and I do get warnings about that both visual and audible. I then selected the 2 cameras nearest to me from the SPUD file and edited them. They did already show a direction, but I changed them to be active in both directions in case the direction was wrong (they are on a dual carriageway). However, I still get no warnings from them at all travelling past them in either direction. It seems odd that they show on the map correctly and can be edited OK, but don't seem to be recognised by the aler

Thanks for that cmh928. I hadn't realised I needed to change the device type. I have done that now and that definitely solves the TMC problem, that is now working perfectly. There didn't appear to be any extra TMC lines in the existing sys.txt I will try out the speed camera warnings again later to see if it has solved that too. I checked my speedcam directory on the flash drive and I only have the spud file that I loaded. The speedlimit signs setting still won't stick, although, interestingly, the turn restrictions option in the same menu does stick if I change that. I had copied th

Thanks for that cmh928. I hadn't realised I needed to change the device type. I have done that now and that definitely solves the TMC problem, that is now working perfectly. There didn't appear to be any extra TMC lines in the existing sys.txt I will try out the speed camera warnings again later to see if it has solved that too. I checked my speedcam directory on the flash drive and I only have the spud file that I loaded. The speedlimit signs setting still won't stick, although, interestingly, the turn restrictions option in the same menu does stick if I change that. I had copied th

Well this post proves just how newbie friendly this mod is. I am both new to this forum and to ownership of a Eurpoean spec f700bt, and have applied this mod to it without bricking it. I used "non_MSN" unziptosdcard download and copied the EU MapDBinfo file and the UK speed cam file to the specified locations. It all loaded and ran perfectly so I want to add my thanks to those that contributed to this. But, (there is always a but isn't there?) I have a couple of issues that may well be down to my newbieness or something to do with the US/EU version differences. Firstly, although