Power Vision Information Thread
Outstanding HDF Member
Joined: Jun 2014
Posts: 3,185
Likes: 189
From: 90210
I created a quick app to take care of it for you. See the thread: https://www.hdforums.com/forum/ignit...l#post13451818
Outstanding HDF Member
Joined: Jun 2014
Posts: 3,185
Likes: 189
From: 90210
sure thing, too big for here so i posted them on my server. about 1.3mb each- these two logs are from today with testing two of my tune files.
http://www.808networks.com/download/pv2/logs/
http://www.808networks.com/download/pv2/logs/
Last edited by LA_Dog; Apr 17, 2015 at 05:40 PM.
Road Captain
Joined: Jun 2013
Posts: 743
Likes: 66
From: TX and WI
My ET engine temp is running 230 -250 F at 70's. My HeadT was calculated at 335F so was concerned. Now I will not pay attention to HeadT. I have been told by others to keep the engine temp below 270 to prevent problems. I am no expert though but have did what it took to keep temps down. Wards fans helped a lot, as well as good tune.
Last edited by Fusionfool; Apr 18, 2015 at 07:30 PM.
Road Captain
Joined: Aug 2008
Posts: 716
Likes: 10
From: Shreveport,La
I installed my decatted headpipe today and loaded the new map sent by FM for the PV. Jamie said I would need a new map when I installed that headpipe.
I loaded the new map and after it quit raining got out for a couple of short rides. I didn't have the time to do any AT runs and I forgot to run a log while riding to view tonight to see what the new map was doing.
I know they say you don't gain anything with decatting the headpipe other than less heat, but I can say between the new map and the decatting my bike loves this new setup! It really runs good and seems to make a lot more power. I had no decel popping either. The throttle seemed just a little sluggish off idle after it warmed up though.I just wish I had ran a log while I was out riding.
ET ran 199* when on the road and coolant was 167. Both went up a little in stop and go traffic, but that didn't last long enough to see where it would land.
I have been getting 40 to 42 MPG on my current map, which is way more than I have ever gotten on any of my Harleys and I wondered if it wasn't a tad lean even though the ET's have been around 200* most of the time I have been riding it since I started tuning on it. I filled it up today and after 40 miles looking at the range indicator I am looking at around 235 total miles "possible" with the new map so the mpg wasn't hurt much.
I think I will have some nice riding weather come Monday so I plan on doing my AT runs then and maybe get a couple of logs in as well. I will know more about it by Tuesday.
I only posted this in this thread because of the need for a new map after decatting the headpipe and thought it was something that should be shared.
I loaded the new map and after it quit raining got out for a couple of short rides. I didn't have the time to do any AT runs and I forgot to run a log while riding to view tonight to see what the new map was doing.
I know they say you don't gain anything with decatting the headpipe other than less heat, but I can say between the new map and the decatting my bike loves this new setup! It really runs good and seems to make a lot more power. I had no decel popping either. The throttle seemed just a little sluggish off idle after it warmed up though.I just wish I had ran a log while I was out riding.
ET ran 199* when on the road and coolant was 167. Both went up a little in stop and go traffic, but that didn't last long enough to see where it would land.
I have been getting 40 to 42 MPG on my current map, which is way more than I have ever gotten on any of my Harleys and I wondered if it wasn't a tad lean even though the ET's have been around 200* most of the time I have been riding it since I started tuning on it. I filled it up today and after 40 miles looking at the range indicator I am looking at around 235 total miles "possible" with the new map so the mpg wasn't hurt much.
I think I will have some nice riding weather come Monday so I plan on doing my AT runs then and maybe get a couple of logs in as well. I will know more about it by Tuesday.
I only posted this in this thread because of the need for a new map after decatting the headpipe and thought it was something that should be shared.
Road Captain
Joined: Aug 2008
Posts: 716
Likes: 10
From: Shreveport,La
So today I took a ride with the wife running the no cat map sent by FM. I ran two logs while out riding. The second log was after we stopped for some refreshments.
When I got home I downloaded the logs and opened them with excel. The first log showed that the bike was pulling 1.75* of timing during the whole ride except when the TP was below 17%. Then it would drop to 0% in steps.
When I opened the second log, which was made after the stop and having cycled the ignition I found no timing pulled for then next 45 minutes of data logging. Not one timing event. So it appears the ecm learned the timing setting and trimmed it to compensate for the timing pull during the first log run. I wasn't aware that the ecm would do that and I wonder if I reload the map and reset the trims if the 1.75 timing pull would show up again.
I plan on doing my AT runs tomorrow to get the VE's dialed in for this tune. I know the learned trims will be reset at that time. My question is, are the trims that we reset when loading a new map and doing AT stored on the ecm? Are we resetting the ecm learned value/trims?
I have looked at many logs from back when I was doing the 08 Ultra, but I have never seen timing pulled at a steady setting like the first data log was showing and then have it gone in a second log with no changes to the tune from the pv.
I guess I am a little confused here.
When I got home I downloaded the logs and opened them with excel. The first log showed that the bike was pulling 1.75* of timing during the whole ride except when the TP was below 17%. Then it would drop to 0% in steps.
When I opened the second log, which was made after the stop and having cycled the ignition I found no timing pulled for then next 45 minutes of data logging. Not one timing event. So it appears the ecm learned the timing setting and trimmed it to compensate for the timing pull during the first log run. I wasn't aware that the ecm would do that and I wonder if I reload the map and reset the trims if the 1.75 timing pull would show up again.
I plan on doing my AT runs tomorrow to get the VE's dialed in for this tune. I know the learned trims will be reset at that time. My question is, are the trims that we reset when loading a new map and doing AT stored on the ecm? Are we resetting the ecm learned value/trims?
I have looked at many logs from back when I was doing the 08 Ultra, but I have never seen timing pulled at a steady setting like the first data log was showing and then have it gone in a second log with no changes to the tune from the pv.
I guess I am a little confused here.
Tourer
Joined: Apr 2012
Posts: 482
Likes: 30
From: Michigan/Florida
Originally Posted by Scooterbum46
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..
HD Forum Stories
The Best of Harley-Davidson for Lifelong Riders
7 Times Harley-Davidson Chucked Tradition Out the Window
Verdad Gallardo
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
Stellar HDF Member
Joined: Jun 2007
Posts: 2,928
Likes: 117
From: Ashby, Ma
Log Tuner question:
I've run log tuner many times successfully, but not for a while. Yesterday I hit my 1K break-in mark on my new 107 build and decided to do some log tuning on the way home.
So anyway I created some logs, and ran Logtuner, but had something I've never see before happen. Logtuner shows all the hits in the 20 MAPkpa column. Although I look in the logs and hits are spread out here and there at various MAP columns and rpms.
I've reread the Logtuner directions and back tracked through my steps multiple times and can't seem to find the issue. It's logtuner is incorrectly reading, or not reading the TP or MAP data. Anyone ever had this happen? What am I doing wrong?
I've run log tuner many times successfully, but not for a while. Yesterday I hit my 1K break-in mark on my new 107 build and decided to do some log tuning on the way home.
So anyway I created some logs, and ran Logtuner, but had something I've never see before happen. Logtuner shows all the hits in the 20 MAPkpa column. Although I look in the logs and hits are spread out here and there at various MAP columns and rpms.
I've reread the Logtuner directions and back tracked through my steps multiple times and can't seem to find the issue. It's logtuner is incorrectly reading, or not reading the TP or MAP data. Anyone ever had this happen? What am I doing wrong?
Stellar HDF Member
Joined: Jun 2007
Posts: 2,928
Likes: 117
From: Ashby, Ma
Log Tuner question:
I've run log tuner many times successfully, but not for a while. Yesterday I hit my 1K break-in mark on my new 107 build and decided to do some log tuning on the way home.
So anyway I created some logs, and ran Logtuner, but had something I've never see before happen. Logtuner shows all the hits in the 20 MAPkpa column. Although I look in the logs and hits are spread out here and there at various MAP columns and rpms.
I've reread the Logtuner directions and back tracked through my steps multiple times and can't seem to find the issue. It's logtuner is incorrectly reading, or not reading the TP or MAP data. Anyone ever had this happen? What am I doing wrong?
I've run log tuner many times successfully, but not for a while. Yesterday I hit my 1K break-in mark on my new 107 build and decided to do some log tuning on the way home.
So anyway I created some logs, and ran Logtuner, but had something I've never see before happen. Logtuner shows all the hits in the 20 MAPkpa column. Although I look in the logs and hits are spread out here and there at various MAP columns and rpms.
I've reread the Logtuner directions and back tracked through my steps multiple times and can't seem to find the issue. It's logtuner is incorrectly reading, or not reading the TP or MAP data. Anyone ever had this happen? What am I doing wrong?
Did the 1K oil change to Mobil 1 15/50 syn.
Then took the PC inside and voila' normal Logtune hit maps. All is good.
I may have also just fat fingered something during the day Sunday when I was out riding. Us north easterners we got fat gloves to keep the fingers warm even here in April.
Whatever chalk it up to user error. Zen and the Art of Motorcycle Maintenance. "if you can't fix it, go relax, get a good nghts sleep and start over." Works like a charm.
