750turbo.com

I posted this problem two years ago, but there were no replies and I still haven't solved it (maybe it doesn't have a solution since I've seen nothing on any other Power Commander forums). But I'll try again with additional info, since it is apparently unique to my E1. But I want to confirm - am I the only one having this issue?

I'm using a PC-V (for 2006-7 Suzuki GSXR750), USB interface to Windows 10 notebook running Power Commander Software Version 1.0.6.4. Stock ignition except for Bosch Mag suppression wires. Injectors fire. TPS ground properly connected, and TPS voltage stable and correct. Solid ground at cable between engine and battery. USB cable from PC5 to notebook is the one provided with PC5. Injector resistance about 10 ohms. Equipped with AutoTune, but makes no difference.

Running at speeds below about 3000 RPM, the Power Commander Control Center software RPM display either blanks out or becomes intermittent, and, to a lesser extent, some of the other displayed data jumps around also. With cell tracer on, the cell highlighed on the fuel map at idle flickers between 500 RPM and the actual idle speed, as high as 2500 RPM. Never have been able to get a really smooth idle. The PCV itself seems to work OK when this happens, but I'm not sure. The Power Commander LCD-200 display unit has similar behavior - blanks out the RPM much of the time. Tried two other notebooks - no difference. Problem seems to go away at higher engine speeds and at zero RPM when the ignition is on but engine is not running. Logically one might expect this to be related to ignition or power supply noise. Maximum voltage ripple on 12 volt buss is 0.1 volt at low speeds. Ignition has suppression wires and resistor plugs. Moving the notebook further away has no effect.

If it matters, about half the time, the PC control Center program does not connect to the PC5 unit until typically the third or fourth try, and sometimes I just have to wait a while.

Thanks for reading all of this; any experience or advice would be appreciated.

Hi Art,
Sorry you dd not get help with your PC. I won't be much help as I do not run one either. May be cause your running a -5 PC most here do not use. Usually the -3 PC. Maybe it is a matter of checking everything from the PC , TPS for proper voltage read, connections etc. Making sure you have good connections and information flowing to the PC. Hope you get this worked out. I remember when you put this on I had a lot of interest as I wanted to run the -5 with auto tune.
Keep us posted and good luck!

Sure someone will pop in with some help

I had this sort of shit for ages with with my PCV. Spoke to the guys at at Dynojet UK - see mail below.

From: Richard - Dynojet UK <richard@dynojet.co.uk>
Date: 15 August 2018 at 10:50:59 BST
To: John Woods <JohnWoods@nuview-ltd.com>
Subject: rpm filters and firmware
Hi John,

Please find attached to this e-mail the rpm filters and firmware.

Each file can be loaded in via the power commander control centre, via
the "power commander tools" menu, the "update firmware".

The software can be downloaded from the link below.

http://www.powercommander.com/downloads ... .0.6.4.zip

"PC5Moto_1.13.1.pvu" is the firmware file i would like you to upgrade to.

With regards to the rpm filters:

"RPMFilterSetZero" - This is the filter the power commander would have
originally come with before the filtering was changed. - Least filtering

"RPMFilterSetOne" - This is what the unit was changed to. - Most filtering

"RPMFilterSetFour" - This a filter in between RPMFilterSetZero and
RPMFilterSetOne.

Hope this helps.

--
Regards,

Richard Redmayne
Dynojet UK
www.dynojet.co.uk
www.dynatekuk.com
richard@dynojet.co.uk
01995 600500


after doing this all the cells appeared and as mine was happening much higher up the rev range I worked out the dyno that PCV was not doing anything when those cells didnt show - worrying.

installed the filter - "RPMFilterSetOne" - This is what the unit was changed to. - Most filtering"

Hey presto the whole bag of tricks worked like it should.

PM an email address and i will send you the filters I know I can send them as I sent them to Darrell.

I hope this works for you.

Had you feeling you would jump right in Mang!! Great help for the -5 guys!

Thanks so much! I can't wait until next weekend to do the firmware patches. I'll report back.

A -5 guy.

It's a frackin miracle! Stable RPM and it (sigh...) idles smoothly. My High-Vo chain is sooo grateful. Thanks so much!

What gets me now is that I have received (very nice) assistance from Dynojet several times over the last two years, but nothing was ever mentioned about the existence of these patches.

If it might help some other poor -5 guy, here's some other useful things I learned from Dynojet support emails. I will comment on each individually:

" The Power Commander's RPM input comes from injector pulse #1, which should be the injector pulse going through it via the ORANGE and WHITE/ORANGE wires. Anything that that changes the way that pulse "looks" on an oscilloscope can potentially change how the PC5 perceives the pulse for RPM measurement. So for the sake of testing, you might change only the #1 (left most) injector back to a stock injector (temporarily for the sake of testing) just to see if it has any effect on the PC5's RPM signal."

This made no difference, since the injectors are driven by the PC-V outputs, not at the inputs from the ECU, so they have no effect on the input signal seen by the PC-V.

"PC5's are also susceptible to receiving RFI interference from their ground source. So you might try grounding the PC5 unit directly to the engine case, to see if it has any effect on the problem."

This certainly can make a difference, but since I always complied with their grounding advice, this did not affect my issues.

"You might also try removing any electronics on the bike that aren't stock. We've seen issues like this when using the PC5 with light-weight lithium ion racing batteries. We've seen issues from LED lighting. We've seen issues with surface gap spark plugs."

I removed all of my home-made gizmos. Removed my Dynotech CD ignition system. And indeed, I have been using Shorai Lithium Batteries ever since they came out. However, the Mang-patches fixed the problem even with the Shorai battery. It can only get better once I have a good-old low-impedance lead brick. It's sitting on my bench now.

"Your unit was made in late 2011, and there have been a few changes on our circuit boards since that unit was made. If you wanted to send it in, we could offer a brand new equivalent PC5 with a year of warranty as a replacement at a reduced cost of $199 plus shipping and handling."

This after prior advise had no effect. I am indeed grateful for being offered this update option after all else failed. But it strongly suggests that they have been aware that the early PC-Vs have hardware issues that could cause the problems I experienced, and that the firmware patches are actually workarounds. But since they seem to cure my problems, I'm anxious to just get riding again. It's been two years. I'm actually on my second PC-V for this bike. In 2016, when I noticed these problems with my first unit, I tried to return it for warranty repair. But since I had cut off all the original connectors to wire it into my E1, they returned it for invalidated warranty (which is what I expected). So I bought another new one, with the same problems.

So Cheers to Mang and others that reached out to help me, when all else failed.

Glad it worked for you Art. May be we should ask Lorcan if the patches could be put somewhere on the site so anyone that needs them can get access to them.

I've made a new thread in this section with a link to the patches and a more search-friendly title. Good work Mang and Art

PC5Moto_1.13.1.pvu" is the firmware file i would like you to upgrade to.

I have just downloaded the firmware update and updated the PCV. It is now version 1.14.2
Hopefully it is going to do what I want it to do. IE Work!
I seem to be getting "not responding" more often than not for some reason.

Forgive the possible continued use of forum bandwidth. But for the benefit of anyone else who may have suffered the "early PC-V curse", I just wanted to report that the software patch provided by Mang, apparently from dynojet UK and including signal filtering, did permanently cure the problem I posted above. I did not have to buy another (my 3rd) PC-V after all, as I had been instructed by Dynojet tech support. So I guess that means I owe Mang and others who responded on the forum a PC-V worth of 805 Beer if you ever visit California. Hope to meet you some time.

One update, of possible interest, or not... The LCD-200 display I bought with my first PC-V attempt never worked correctly. Intermittent, wouldn't retain settings, couldn't even set some of the settings. Even after the PC-V patch. I hung onto this display way too long, since I liked the high resolution, color touch screen, and it wasn't cheap. It was discontinued by dynojet about a year after I bought it. Now I know why.

So I broke down and did as instructed by Dynojet Tech Support: I bought a POD-300 display. Not color. Not touch screen. More expensive. But, alas, it works fine. And the large display fonts are indeed easier to read while riding, avoiding the potential for a GPz vs tree encounter due to instrument fixation.

Opinion - Although I do admire Dynojet as a company, it seems like they are selling some products without adequate testing, an not making good on what should be product recalls when major issues are found by the buyers/product testers. I expect most of you have had only positive experiences, so consider this only a tempering comment amid the praise.

Thanks again.
Art