Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[steveg56]

I just put on some vance and hines dresser duals with 4" Rineharts, but could not find a Map.  I contacted Fuel Moto and they do not have one either.  Nothing on Dyno Jet's downloads either. 

If it helps I have a 2012 CVO Road Glidel with the above mentioned mods.  Any help would be appreciated.   

[kiwihog]

mines a 2011 FLTRUSE with V&H power duals and 2.0 fullsac  baffles you could try mine if you want

[steveg56]

Thanks for the offer Kiwihog, but I have a similar map from Jamie over at Fuel Moto that he sent me using his Xpipe...seems to work pretty good just want to feel better that I'm not way out of tune and running super lean. 

Anybody else with a closer set up?

[Fire-Medic]

Thanks for the offer Kiwihog, but I have a similar map from Jamie over at Fuel Moto that he sent me using his Xpipe...seems to work pretty good just want to feel better that I'm not way out of tune and running super lean. 

Anybody else with a closer set up?

If you have a map that's close, you can data log and fine tune the tune you have, it's not that difficult. 

[kiwihog]

yeah instructions are on the fuel moto website on how to data log Ive just been pretty happy with how mines been running except for a high idle when cold MPG is good around 45

[steveg56]

Thanks guys...I'll try the datalog.   It's not clear with what I do with the info once I have it?  Is it pretty self explanatory on what to do with the info collected?

[glens]

Thanks guys...I'll try the datalog.   It's not clear with what I do with the info once I have it?  Is it pretty self explanatory on what to do with the info collected?

Sad to say that the data logs from the PV are fairly suspect and their usability is questionable.  What they've been doing, at any rate, is outputting data at roughly 20 millisecond intervals while the data coming from the ECM is on the order of 10 times less frequent.  What the PV does is for any "channel" of information, the unit repeatedly spits out the last-known value until it's replaced by something new from the ECM, at which point it starts repeating that value.  That anomaly could be worked-around except for the fact that the updated data doesn't occur in all of the "channels" in any given time-slice.  That's to say that the data "channels" get updated at different times.  This means that you can't merely discard the duplications by deleting every 10 or 11 lines in the log file.  It also means that any line of data in the file cannot be counted on to contain pertinent related data.

Say you got some knock retard and want to retard some timing to prevent the knock retard from occurring.  You can back up a line or two before the event and see what the operating conditions were which likely caused the spark knock.  But you find that while the MAP remains the same the throttle position changed, or while the throttle position and MAP remain the same the engine speed changed, etc!

Siimilarly, you cannot count on  any necessary information pertinent to VEs to be current in a given line of output, so how can you accurately adjust the VEs based on the logged data?

Maybe they'll fix the logging process in a future firmware upgrade.

[cvobiker]

Sad to say that the data logs from the PV are fairly suspect and their usability is questionable.  What they've been doing, at any rate, is outputting data at roughly 20 millisecond intervals while the data coming from the ECM is on the order of 10 times less frequent.  What the PV does is for any "channel" of information, the unit repeatedly spits out the last-known value until it's replaced by something new from the ECM, at which point it starts repeating that value.  That anomaly could be worked-around except for the fact that the updated data doesn't occur in all of the "channels" in any given time-slice.  That's to say that the data "channels" get updated at different times.  This means that you can't merely discard the duplications by deleting every 10 or 11 lines in the log file.  It also means that any line of data in the file cannot be counted on to contain pertinent related data.

Say you got some knock retard and want to retard some timing to prevent the knock retard from occurring.  You can back up a line or two before the event and see what the operating conditions were which likely caused the spark knock.  But you find that while the MAP remains the same the throttle position changed, or while the throttle position and MAP remain the same the engine speed changed, etc!

Siimilarly, you cannot count on  any necessary information pertinent to VEs to be current in a given line of output, so how can you accurately adjust the VEs based on the logged data?

Maybe they'll fix the logging process in a future firmware upgrade.

i was suspecting this input would eventually come.. a far cry from what the poster was asking...  So while we are off the beaten path, let me ask...  Hey glen,, can you tell us a little more about yourself??   Are you a vendor? do you support an specific vendors??   i see you are from the United States.. does that possibly mean you are in the Torrance area??   do you claim to be an expert with any specific tuning systems?  what is your 'hands on experience' with each of these systems you claim expertise with? ....  just curious cause im trying to figure out if what you say is for real or just BS    ...    Oh.. Thanks Glen    

[glens]

i was suspecting this input would eventually come.. a far cry from what the poster was asking...

Perhaps a cry from what he'd initially asked, but maybe you'd noted the thread took a direction he himself followed?  What I'd said was directly in line with that direction.

So while we are off the beaten path, let me ask...  Hey glen,, can you tell us a little more about yourself??

I like to keep my private information a little closer to my vest than plastering it on a relatively open forum.  But thanks for asking.

Are you a vendor?

No, I am not.

do you support an specific vendors??

No, I do not.

i see you are from the United States.. does that possibly mean you are in the Torrance area??

No, and I'm unfamiliar with any places called or known by "Torrance".  Perhaps you'd be so kind as to inform me where or what it or they might be.

do you claim to be an expert with any specific tuning systems?

Expert?  Hardly.  Although if you were to deliver to me just about any system I'm confident I could use it very well; within the limits of what it can do at any rate.  Do you have something in particular in mind, maybe?

what is your 'hands on experience' with each of these systems you claim expertise with? ....

Got a little bit ahead of yourself with that question?  You hadn't yet determined whether I claimed expertise with any system.  I still don't know just what it is you might have in mind so I cannot focus further in on anything for you at this point.

just curious cause im trying to figure out if what you say is for real or just BS    ...    Oh.. Thanks Glen    

What I said about the PV data logging is (at least was as of September of last year, when I spent some time with some PV data logs and dissected them) bona fide and indisputable.  As I stipulated earlier, I don't know just what the current status is in that regard.  That is if anything has changed.  I doubt it has.  Do you know one way or the other?  Do you even understand what it is I'd said?  If so, do you agree or disagree?  If you disagree, please clearly state why that is so.  If you've never looked at any data logs from any of the products, just come right out and admit it.  If you have any recent PV data logs, post one up and I'll show you with it what I'm talking about.

[captdave221]

Well I'll bite. LOL. I am attaching a recent data log from my 120 build. Take a look at it. Mostly just highway crusing.

[captdave221]

And another one.

[glens]

Open the .csv file in an editor and delete the first 31 lines, then open it in your favorite spreadsheet program (I use openoffice.org but I'd bet MS office would work too).  "Freeze" the first two rows so they always stay at the top of the grid as you scroll through the file.

You can just open the file in the spreadsheet program and then delete the first 31 rows, but this will make for some wide columns.

Either way.

Attached is a screenshot of one of those log files.  It's in an arbitrary spot in the file.  Note how the values repeat, but not with all the same transition points.  I moved the front and rear "O2 V" columns from the far(ther) right to the left and into the screen, though it's not a good place in the file since it wouldn't be closed-loop with the set lambda currently in use "here".  Still, the DJ broadband sensors are showing changes while the stock units (which presumably are still in service) do not...

I think it's a mess.

[UK1]

I just put on some vance and hines dresser duals with 4" Rineharts, but could not find a Map.  I contacted Fuel Moto and they do not have one either.  Nothing on Dyno Jet's downloads either. 

If it helps I have a 2012 CVO Road Glidel with the above mentioned mods.  Any help would be appreciated.   

Just seen your log. I couldn't tell if you had got help or not. Patrick from Dynojet sent me map 11T110000401. I have the same setup as you do. Works perfect, better than my own setup.

[UAV Pilot]

I just emailed Dynojet with my FLHTCUSE3 setup and was promptly sent a tune file for the 110 ci, stock breather and slip-ons.  Just ask, I have found Dynojet to be easy to work with and good customer service.

Glenn

[steveg56]

Just seen your log. I couldn't tell if you had got help or not. Patrick from Dynojet sent me map 11T110000401. I have the same setup as you do. Works perfect, better than my own setup.

Just checked and saw that map on their site, thank you!!   Since we have 2.25" baffles do you think the 0000402 map (extreme True duals) would work better??