The rear is doing the random 1-2 thing. The front may be hitting a burst of them, but you are right, it's still not continuous. The ride the other day in +90 degree temp resulted in 3 or 4 on the rear and 95 or so on the front, in a 100 mile ride that included some stop and go and a fair amount of 50-70 Mph cruising. I'm not going to get paranoid over this, but do want to eliminate it before doing the stage 1 mods.

BTW - when I asked about this at the dealership, a tech who I think is pretty sharp stated that the front cylinder on the new ones ran hotter than the back, due to the lowers and the fender blocking airflow (huh - none of that stuff is new on the 14-15's ?).. I didn't argue, but thought he was either pulling my leg.....now I'm not so sure.

Crazy Legs - I got lazy today - had to take SO to a flea market and too hot and humid when we got back. I'll grab a socket and swap 'em later.

Thanks for the replies - Ill post the outcome.

Edit - another question - when marrying the PV to a new ECM, does it remove any files from previous bikes it has been used on ( I'm talking the log and .pvv files..) And if it doesn't, what files are safe to clean off the PV - I know that my original map and the tunes in the 8 slots are all OK, but some of the log files have more data elements logged than others (i.e. some have "ionQ", others don't).

 

I always pull and delete all log and .pvv files. I will do house cleaning on the custom tunes also. I may keep the previous one just incase or if I have one that is set up to run cooler I may run it long as not doing long rides. On the 3 and 4 degrees spark knock I would take a look at the corresponding VE cell or cells it came from by rpm and map or TP depending on map format and see if it doesn't need richening up there 2 or 3 points. I find that richening the VE's above 20% throttle position or above 60Kpa by 3 to 5 points higher than I think they need to be will cure the spark knock up high. The Autotune will lean it back out if you use it. I also richen the rpm area above 3500 the same way. Helps with the shift popping and decel popping and really doesn't affect the performance. Matter of fact it can actually improve the performance if you have enough timing in the acceleration area below 3000. don't add too much timing above 3000 as it seems to have plenty there. Some may disagree, but that works for me.

 

A .pvv file is not a log file, it is a value file which is an individual table or tables within a Power Vision calibration, .pvv files can be imported in the WinPv software.

PV logs are saved in .csv format, logs can be viewed in the Dynojet Power Core software which can be downloaded here

http://www.powercommander.com/downlo...5449.19123.exe

A .csv is a very general format, it can also be opened in most spreadsheet programs including MS excel

 

Some knock activity is absolutely normal, especially on 14-15 CANbus models as knock retard is slightly different. Remember knock retard is based on sudden increases in cylinder pressure, not actual detonation and the number of knock counts is relative to the duration of the log or run cycle, you really need to look at overall knock retard activity. Also note on 14-15 bikes the knock retard channel is not individual knock events, it is adaptive knock retard that is learned. That is why your logs look funky in megalogviewer, they are the adaptive values not the knock events themselves

 

None of the maps are the same, I would make sure you are loading and comparing the maps correctly

 

If you changed from the Monster Ovals (chambered) mufflers to the V&H Hi Output muffler you are going to need to do some pretty significant retuning. With your 107/TW-888 combination these extremely larged baffle mufflers will create low RPM performance and tuning issues due to their design (as would other mufflers of similar design) Assuming you had the bike tuned with your previous setup, at a minimum you will need to run a full series of runs with AT Basic, we will need to see copies of the tune you are starting with and the maps AT is populating. Once the VE is straightened out we can get a look at some logs. I would generally suggest using your Monster ovals with your combination, the Hi Outputs are going to put a hole in the lower RPMs and will be difficult to tune with your combo.

 

WinPv is actually more powerful than Log Tuner, AT Basic/Pro populates the same corrections as Log Tuner did however you no longer have to export & import the logs and value files; all the heavy lifting is already done. You can open your base map and AT derived maps together in WinPv, the corrections are right there like log tuner, but you can edit the entire map right there with the individual tables or if you want to accept or clear Auto Tune corrections right in the delta screens. I will try to put together some screenshots this week with some helpful info, tricks, and things to look for in WinPv as well as using the Power Core software for logs. Some really cool stuff in there

 

Jaimie - thanks for taking the time to respond.. This only came up because I keep seeing the knock counter for the front cylinder register a much higher ratio of events when compared to the rear. I interpreted this as "somethings not normal". It is giving me a great opportunity to learn how to analyze the logs. I'm not sure as I understand the value assigned to "Spark Knock F" by megalogviewer, as it's expressed in degrees, but on a strip chart view it steps up staircase fashion. I've assumed that it's degrees of rotation, probably wrong. Note that when looking at spark advance on the chart it is always backing down for the duration of the knock event and then returning to the previous level.

 

This may be correct for your PV units and accompanying software, but is incorrect for the new PV-2 unit I bought, updated with latest firmware and running latest WinPV software from DJ's site. I have no doubt there is a way to change the logging file to csv for export, and I already understand that pvv is referenced as a value file.

Running though DJ's instructions on starting logging, the default process I encountered with the PV-2 when I exported the captured logged data through WinPV's "get log" operation, WinPV saved it with a pvv file extension. The DJ guide shows it being exported as a csv. I can't tell why my unit, by default, chose to save it as a pvv. The log settings in the PV2 were set to simple and not "pro-xy"

I eventually figured out how to open the pvv in WinPV using the "load values" menu option, but again, I have no idea why the PV-2 would export logged data in a pvv format. I was data logging and not auto tuning.

You may want to grab a new default unit with the latest firmware to see this oddity.

 

You are correct and that was my mistake for not being familiar with the software- the VE's are different between all of them, and I'm understanding now that having VE correct is key. Everything else though is 100% the same among these map files. None of these maps are for my specific set of pipes, yet I have different DJ techs saying use different files such as the one for Rinehart, Big Shots, and telling me 'oh they are all similar and do the same thing'- which tells me, they don't think VE matters all that much and neither does accurate tuning. Very disappointing from my side, is all I'm saying.