Power Vision Information Thread
Outstanding HDF Member
Joined: Jun 2014
Posts: 3,185
Likes: 189
From: 90210
Hrmm.. I'm confused when you say they don't support this log file format when it is being created by the unit natively- I did not do anything special to create this file.
I have a brand new PV-2 with latest firmware and latest WinPV software. The PV-2 ran the data logging, created this file, WinPV exported it from the PV-2 with the "get log" operation, and saved it with the pvv extension. If this log format is not supported for actual use, but logs are written to this format by default in brand new units, then I'd say DJ's software programmers or QA department are totally out to lunch..
I have a brand new PV-2 with latest firmware and latest WinPV software. The PV-2 ran the data logging, created this file, WinPV exported it from the PV-2 with the "get log" operation, and saved it with the pvv extension. If this log format is not supported for actual use, but logs are written to this format by default in brand new units, then I'd say DJ's software programmers or QA department are totally out to lunch..
Outstanding HDF Member
Joined: Jun 2014
Posts: 3,185
Likes: 189
From: 90210
LOL- yeh I know that look all too well. Have a good evening I will poke around some more in WinPV
Outstanding HDF Member
Joined: Jun 2014
Posts: 3,185
Likes: 189
From: 90210
Nope, no dice. Zero options in WinPV to import, apply, manage, view, convert or otherwise open a pvv datalog file. All WinPV will do is "get log" from the PV 2 unit and save the pvv to local file on hard drive.
Tourer
Joined: Apr 2012
Posts: 482
Likes: 30
From: Michigan/Florida
I'm having an issue with random knock count on the front cylinder ('15 stock 103 TriGlide). The other two 103's ('12 SG and a '14 Limited) showed more knock counts on the rear cylinder, which is normal due to more heat, this one shows an occasional instance of a knock event on the rear, but for some reason will show several at a time on the front. I'm running FM's "stock improved" map for the next month or so (gotta get home to Michigan before the "big" order to FM), but when I first put the PV on this bike, it was doing the same thing with a stock map.
Running MegaLogViewer on the last log file, I cannot seem to find a correlation between when the knock events happen and a change in Map, TP, or other logged parameters. I know that the ECM "thinks" it's a real event, because the front cylinder advance gets backed way down until the event is over and then advances again. I know that it seemed worse on a 100 mile run the other day, as the AAT was over 90 degrees, ET eventually moved up to 230 and head temp was running 270-290, but again, I've seen this when it was much cooler. What I am suspecting is either false ION knock sensing due to a bad plug or plug wire, but am wondering if there are other reasons for this issue..
Running MegaLogViewer on the last log file, I cannot seem to find a correlation between when the knock events happen and a change in Map, TP, or other logged parameters. I know that the ECM "thinks" it's a real event, because the front cylinder advance gets backed way down until the event is over and then advances again. I know that it seemed worse on a 100 mile run the other day, as the AAT was over 90 degrees, ET eventually moved up to 230 and head temp was running 270-290, but again, I've seen this when it was much cooler. What I am suspecting is either false ION knock sensing due to a bad plug or plug wire, but am wondering if there are other reasons for this issue..
Bottom line is that bad plugs, wires or coil problems could cause bogus random knock events. I'm going to start by checking all ignition wiring and then swapping plugs. If I can't make it go away, this'll be a tough one to sell at the dealership....
Road Warrior
Joined: Apr 2010
Posts: 1,648
Likes: 37
From: Monroe, Louisiana
I did find a good explanation of ION knock sensing - one description by Wurktruk (RIP) and then a short and a long PDF found by searching Google for "ionization-current-sensing-ignition-subsystem.pdf" and "http://www.nav200.delphi.com/pdf/techpapers/2013-01-0354.pdf" .
Bottom line is that bad plugs, wires or coil problems could cause bogus random knock events. I'm going to start by checking all ignition wiring and then swapping plugs. If I can't make it go away, this'll be a tough one to sell at the dealership....
Bottom line is that bad plugs, wires or coil problems could cause bogus random knock events. I'm going to start by checking all ignition wiring and then swapping plugs. If I can't make it go away, this'll be a tough one to sell at the dealership....
Road Warrior
Joined: May 2013
Posts: 1,430
Likes: 55
From: Florida
Hrmm.. I'm confused when you say they don't support this log file format when it is being created by the unit natively- I did not do anything special to create this file.
I have a brand new PV-2 with latest firmware and latest WinPV software. The PV-2 ran the data logging, created this file, WinPV exported it from the PV-2 with the "get log" operation, and saved it with the pvv extension. If this log format is not supported for actual use, but logs are written to this format by default in brand new units, then I'd say DJ's software programmers or QA department are totally out to lunch..
I have a brand new PV-2 with latest firmware and latest WinPV software. The PV-2 ran the data logging, created this file, WinPV exported it from the PV-2 with the "get log" operation, and saved it with the pvv extension. If this log format is not supported for actual use, but logs are written to this format by default in brand new units, then I'd say DJ's software programmers or QA department are totally out to lunch..
Edit; You have set up folders for Tune files/Log Files/Value Files/ and the other one Original or Stock right?. (I'm trying to remember but it's been a while.) My tune is awesome and I log data once in a while just to see how things going. I do keep the PV mounted on my bars showing ET/TripA mpg/B+/and MAP readings.
Last edited by Smokey Stover; Apr 12, 2015 at 08:19 AM. Reason: add on
Cruiser
Joined: Dec 2008
Posts: 225
Likes: 6
I'm having an issue with random knock count on the front cylinder ('15 stock 103 TriGlide). The other two 103's ('12 SG and a '14 Limited) showed more knock counts on the rear cylinder, which is normal due to more heat, this one shows an occasional instance of a knock event on the rear, but for some reason will show several at a time on the front. I'm running FM's "stock improved" map for the next month or so (gotta get home to Michigan before the "big" order to FM), but when I first put the PV on this bike, it was doing the same thing with a stock map.
Running MegaLogViewer on the last log file, I cannot seem to find a correlation between when the knock events happen and a change in Map, TP, or other logged parameters. I know that the ECM "thinks" it's a real event, because the front cylinder advance gets backed way down until the event is over and then advances again. I know that it seemed worse on a 100 mile run the other day, as the AAT was over 90 degrees, ET eventually moved up to 230 and head temp was running 270-290, but again, I've seen this when it was much cooler. What I am suspecting is either false ION knock sensing due to a bad plug or plug wire, but am wondering if there are other reasons for this issue..
Running MegaLogViewer on the last log file, I cannot seem to find a correlation between when the knock events happen and a change in Map, TP, or other logged parameters. I know that the ECM "thinks" it's a real event, because the front cylinder advance gets backed way down until the event is over and then advances again. I know that it seemed worse on a 100 mile run the other day, as the AAT was over 90 degrees, ET eventually moved up to 230 and head temp was running 270-290, but again, I've seen this when it was much cooler. What I am suspecting is either false ION knock sensing due to a bad plug or plug wire, but am wondering if there are other reasons for this issue..
Oh jeez I just noticed you are trying this, good luck it helped me.
HD Forum Stories
The Best of Harley-Davidson for Lifelong Riders
7 Surprising Harley-Davidson Products that Are Not Motorcycles
Verdad Gallardo
8 Best Harley-Davidson Motorcycles Ever
Pouria Savadkouei
10 Worst Harley-Davidson Motorcycles Ever
Pouria Savadkouei
Killer Custom's Jail Break Is The Breakout That Refused to Blend In
Verdad Gallardo
Crazy Bunderbike Build Looks Amazing, But Is It Impossible to Ride?
Verdad Gallardo
Harley-Davidson Reveals Super Cool Cafe Racer Concept
Verdad Gallardo
Engraved Rebellion: Inside Bundnerbike's Glam Rock II
Verdad Gallardo
10 Motorcycles You Should Never Buy
Joe Kucinski
10 Things Harley-Davidson Needs to Fix in 2026
Verdad Gallardo
Outstanding HDF Member
Joined: Aug 2009
Posts: 2,858
Likes: 217
From: Puyallup Wa.
in my opinion the more automated it got the more dumbed down it got. I really like the automation for the VEs however I still keep a eye on them because it seems like there's always some area that goes weird. I really liked having log tuner available and supported. just don't see how it would be that difficult to at least give it minimal support and let people utilize it that want to.
I haven't really had any spark issues with the Fuel Moto map for my 14 SG. and I admit I don't understand how it works it just has not sunk in how it's recorded and the CAN bus system. all I've seen is little snippets and comments that I have yet to really read a full explanation of spark knock knock on the CAN bus and how it's recorded with the Power Vision
I haven't really had any spark issues with the Fuel Moto map for my 14 SG. and I admit I don't understand how it works it just has not sunk in how it's recorded and the CAN bus system. all I've seen is little snippets and comments that I have yet to really read a full explanation of spark knock knock on the CAN bus and how it's recorded with the Power Vision
Outstanding HDF Member
Joined: Jun 2014
Posts: 3,185
Likes: 189
From: 90210
I agree- Especially considering the latest PV-2 and WinPV software will export and save the logged data, by default, in pvv file format. This is ridiculous because you cannot do anything with this logged data pvv file unless you can magically find an old copy of the Log Tuner software.