GhostRider7
New member
- Joined
- Apr 11, 2007
- Messages
- 523
cheap hotels just around the corner with bar right next door, for many it is a two day event.
To Answer the camping question....
We have had many tow their campers in for our weekend shows.Keep in mind that if the weather is bad around the time you will need to stay off the grassy hill and park the camper at the top on the paved/stoned area.We have parked them at the back of the shop also next to the car trailers there if you need a power hook up.All you need to do is check with the gang and they will fix you up and give you instructions ...........Andy
P.S.-Mike....Dangerous Placards will be brought along with me for your pot of Chili.....LOL!
The big difference with UDC and EFI is that UDC uses an established base tune, so the parameters in which we can set are already enabled. UDC is not throwing darts in the same aspect that it can be with EFI, since UDC is not using a stock tune as the starter tune.
Data logging would be great, but the premise behind UDC is if we set a value the ECM should use that value and it's not the UDC tuners ability to change that value. Data logging doesn't tell you what is safe, or effective, it just tells you if you set the limiters to match your tables. If we don't have to worry about the limiters you can do a lot of tuning without data logging. Either way the driver has to know at what rpm/load he isn't happy, data logging doesn't pick up the likes and dislikes of the driver so there is always going to be some input needed.
Data logging would help with trouble rpms/loads, but if the end user has one of several gauges you can work off of those numbers in combination with the tach to determine where in the map the tune needs tweaking. Data logging does make this easier, but it is certainly not a requirement for tuning if you know the correlation of all the maps.
Even with data logging you have the same changes of getting the first tune right with UDC as EFI, because the first tune is always just a guess of what will work the the motor/mods/use.
I am by no means saying I don't want to see data logging with UDC (quite the opposite actually), I am just pointing out that once you get used to tuning without it that it's not as big of a deal as many people make it out to be. Marco has set us up with limits to match the base tune, and that's where EFI and UDC differ.
The big difference with UDC and EFI is that UDC uses an established base tune, so the parameters in which we can set are already enabled. UDC is not throwing darts in the same aspect that it can be with EFI, since UDC is not using a stock tune as the starter tune.
Data logging would be great, but the premise behind UDC is if we set a value the ECM should use that value and it's not the UDC tuners ability to change that value.
Data logging doesn't tell you what is safe, or effective, it just tells you if you set the limiters to match your tables. If we don't have to worry about the limiters you can do a lot of tuning without data logging. Either way the driver has to know at what rpm/load he isn't happy, data logging doesn't pick up the likes and dislikes of the driver so there is always going to be some input needed.
Even with data logging you have the same changes of getting the first tune right with UDC as EFI, because the first tune is always just a guess of what will work the the motor/mods/use.
I am by no means saying I don't want to see data logging with UDC (quite the opposite actually), I am just pointing out that once you get used to tuning without it that it's not as big of a deal as many people make it out to be. Marco has set us up with limits to match the base tune, and that's where EFI and UDC differ.
How are you throwing darts with EFI when the truck is telling you what it is doing and you have real world data to see what your changes have done?.
HUH??????..Contradict yourself here a bit?...
If we set a value would you not then agree that we,the tuner,have changed the value and then the ECM will use it?
Your correct on part of this one,data logging doesn't tell you what is safe nor does UDC without it.If an owner is worried about safe tunes then he needs to keep the truck stock as even the smallest tune/tuner can break parts or cause failures.Data logging does tell you what is effective as it gives you real world info on what each change has done to the performance of the motor during the rpm runs,no matter if it is strapped or street driven for the info.Data logging will pick up driving styles and allow you to see how your changes affect the truck on the street.There are plenty of owners here using the logging capabilities to log their track runs to make adjustments to their tunes to have the truck run for the conditions it is presented with.Its no different than what any other racer does with their gassers.
I would disagree with that...
You have a much better chance with a log of what your truck is doing over any guess or canned tune to start with.You build your phantom UDC tune for a customers truck that is 3-4 states away that you have never seen and your trying tell me and everyone reading this thread that your UDC guess will be better the first time than a truck that is at a shop being logged and tuned.I do not think so.Better yet I will call BS and then say if thats the case then with a simple list of my trucks hard parts then you should be able to create a tune that should outrun the UDC tune I spent days and many strapped runs to make.I say you will not get within 100 hp of that run with your best dark territory guess you can create without seeing the truck and having hands on capabilities.
The ability to log what the truck is doing is a key ingredient that needs to be added to UDC.I like Smarty and their products and still use them on 3 of our other trucks however IMO UDC is nothing more than a larger version of the SSR guessing game without the ability to log.UDC has the ability to be a great product and with it being able to service the 03-05 owners it does have a leg up but imagine how out of the ballpark better it could be if they would give us an option to log.Until that happens any remote tuning with UDC is a dart board game being played in the dark.
The big difference with UDC and EFI is that UDC uses an established base tune, so the parameters in which we can set are already enabled. UDC is not throwing darts in the same aspect that it can be with EFI, since UDC is not using a stock tune as the starter tune.
Data logging would be great, but the premise behind UDC is if we set a value the ECM should use that value and it's not the UDC tuners ability to change that value. Data logging doesn't tell you what is safe, or effective, it just tells you if you set the limiters to match your tables. If we don't have to worry about the limiters you can do a lot of tuning without data logging. Either way the driver has to know at what rpm/load he isn't happy, data logging doesn't pick up the likes and dislikes of the driver so there is always going to be some input needed.
Data logging would help with trouble rpms/loads, but if the end user has one of several gauges you can work off of those numbers in combination with the tach to determine where in the map the tune needs tweaking. Data logging does make this easier, but it is certainly not a requirement for tuning if you know the correlation of all the maps.
Even with data logging you have the same changes of getting the first tune right with UDC as EFI, because the first tune is always just a guess of what will work the the motor/mods/use.
I am by no means saying I don't want to see data logging with UDC (quite the opposite actually), I am just pointing out that once you get used to tuning without it that it's not as big of a deal as many people make it out to be. Marco has set us up with limits to match the base tune, and that's where EFI and UDC differ.