Prologger experience...
Well, i got to work on a pretty cool project the past couple days. The car is a 67 camaro, twin turbo, Motec M48, Lenco bruno trans, etc. REALLY nice car. The customer got the engine and computer setup from Duttweiler, and was supposedly tuned on an engine dyno but wasn't even close. Might have had the wrong map in it, who knows. Anyways, they had been trying to get it down the track with no success at all. They had no o2 on the car at all, and they couldn't get the MSD boost controller to work right.
I put a Prologger wideband/logger/boost controller on it and set it all up yesterday. We use the prologger to display a/f ratio, send the a/f ratio into the motec to datalog it in there as well, and to control boost. Now i use the same setup on my race car, but only for a/f ratio, i've been using the motec to control boost. This was my first time to setup the boost control on the prologger. It has a feature called "never lean" that is pretty handy. If the a/f ratio gets leaner than a preset point, it'll knock the boost back down to another preset point (usually setup for wg pressure). Well, i setup the boost controller as the instrustions say, set it to 18psi and went to the track. Wasn't really sure how well the boost controller was going to work right off the bat, the gain and overshoot settings were still zeroed out.
First hit off the trailer, car leaves and looks like it makes a decent pass all things considered. Get it back and look at the log. Boost controller did it's job perfectly, right up to 18psi, then right back down to 8psi as the a/f ratio got to 13:1! It probably saved these guys a motor! Got the a/f ratio straightened out and everything was great.
I was very impressed with how well everything worked with the prologger, and how simple it was to setup, most electronic boost controllers can be hell to setup. I think the "never lean" feature is an awesome feature that could save a lot of people a lot of money!
I put a Prologger wideband/logger/boost controller on it and set it all up yesterday. We use the prologger to display a/f ratio, send the a/f ratio into the motec to datalog it in there as well, and to control boost. Now i use the same setup on my race car, but only for a/f ratio, i've been using the motec to control boost. This was my first time to setup the boost control on the prologger. It has a feature called "never lean" that is pretty handy. If the a/f ratio gets leaner than a preset point, it'll knock the boost back down to another preset point (usually setup for wg pressure). Well, i setup the boost controller as the instrustions say, set it to 18psi and went to the track. Wasn't really sure how well the boost controller was going to work right off the bat, the gain and overshoot settings were still zeroed out.
First hit off the trailer, car leaves and looks like it makes a decent pass all things considered. Get it back and look at the log. Boost controller did it's job perfectly, right up to 18psi, then right back down to 8psi as the a/f ratio got to 13:1! It probably saved these guys a motor! Got the a/f ratio straightened out and everything was great.
I was very impressed with how well everything worked with the prologger, and how simple it was to setup, most electronic boost controllers can be hell to setup. I think the "never lean" feature is an awesome feature that could save a lot of people a lot of money!
Turbo domestics go soo fast, soo easy! lol The trans brake wasn't working right last night and it was only leaving with like 5psi and 5k rpm and running 18psi it was going 5.4 @ 130 in the 1/8th. Makes me want to build one!
We were at an 1/8th mile track 20 minutes from my shop.
We were at an 1/8th mile track 20 minutes from my shop.
Trending Topics
i set up the never lean on all the street cars it works great on the dyno you can see how fast it reacts and pulls boost...
i just set up the logger on the e-brake when it drops the timed boost starts..i think it works really good then the logger matches the time slip so you can see everything
i just set up the logger on the e-brake when it drops the timed boost starts..i think it works really good then the logger matches the time slip so you can see everything
Iam glad to here that your experience with the prologger is good. I just installed one on a customers car a few weeks ago. We will be heading to the dyno in the near future.
I'm surprised that nobody has asked Tony why he's using a prologger to record a/f on his car, when he has a Motec system?
So, I'll ask it, what gives? I know you're not one to cheap out, and I'm sure your Motec box has the wideband input enabled..
So, I'll ask it, what gives? I know you're not one to cheap out, and I'm sure your Motec box has the wideband input enabled..
Because the MoTeC sensors are stupidly expensive to replace. The Prologger sensors are cheap in comparison and last just as long. They both use a different type of Bosch sensors.
Tony, I have the Prologger, as you already know. My question is can I purchase just the solenoid and hook it up to my existing Prologger if I wanted to? It looks like everything is there to support it, just not the actual hardware.
I would love to do a back to back with my NLR vs the my Prologger. I'm curious to see how each would perform side by side.
I know the NLR does a great job, but I'm not too familiar with the Prologger yet.
Tony, I have the Prologger, as you already know. My question is can I purchase just the solenoid and hook it up to my existing Prologger if I wanted to? It looks like everything is there to support it, just not the actual hardware.
I would love to do a back to back with my NLR vs the my Prologger. I'm curious to see how each would perform side by side.
I know the NLR does a great job, but I'm not too familiar with the Prologger yet.
Chris, yes, you can, all you have to do is wire the solenoid in.
And that is correct, i've figured out a voltage output conversion to use on the prologger to mimics the signal the M4 is looking for on the lambda input. Basically you get the lambda option in the ecu w/o paying for it, you pay for the prologger instead. Everything works in the ecu as if the lambda option was enabled. By doing it this way instead of paying for the lambda option and using the internal wideband, you get a display, you get to use the bosch LSU sensor instead of the LSM sensor, and you also get all the other features of the prologger.
And that is correct, i've figured out a voltage output conversion to use on the prologger to mimics the signal the M4 is looking for on the lambda input. Basically you get the lambda option in the ecu w/o paying for it, you pay for the prologger instead. Everything works in the ecu as if the lambda option was enabled. By doing it this way instead of paying for the lambda option and using the internal wideband, you get a display, you get to use the bosch LSU sensor instead of the LSM sensor, and you also get all the other features of the prologger.
<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by tony1 »</TD></TR><TR><TD CLASS="quote">Chris, yes, you can, all you have to do is wire the solenoid in.
And that is correct, i've figured out a voltage output conversion to use on the prologger to mimics the signal the M4 is looking for on the lambda input. Basically you get the lambda option in the ecu w/o paying for it, you pay for the prologger instead. Everything works in the ecu as if the lambda option was enabled. By doing it this way instead of paying for the lambda option and using the internal wideband, you get a display, you get to use the bosch LSU sensor instead of the LSM sensor, and you also get all the other features of the prologger.</TD></TR></TABLE>
kinda off topic, how many outputs does the M4 have? I want to know if its a good tool for datalogging as far as multiple EGT sensors, shock travel sensors, etc... or would you also have to have a dashlogger or the AutoMeter data logger as well?
sorry for steering off topic
And that is correct, i've figured out a voltage output conversion to use on the prologger to mimics the signal the M4 is looking for on the lambda input. Basically you get the lambda option in the ecu w/o paying for it, you pay for the prologger instead. Everything works in the ecu as if the lambda option was enabled. By doing it this way instead of paying for the lambda option and using the internal wideband, you get a display, you get to use the bosch LSU sensor instead of the LSM sensor, and you also get all the other features of the prologger.</TD></TR></TABLE>
kinda off topic, how many outputs does the M4 have? I want to know if its a good tool for datalogging as far as multiple EGT sensors, shock travel sensors, etc... or would you also have to have a dashlogger or the AutoMeter data logger as well?
sorry for steering off topic
<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by allmotor_civic »</TD></TR><TR><TD CLASS="quote">^Brent failed to mention that we currently have a Prologger controlling a tattoo gun. </TD></TR></TABLE>
with a statement like that, we need pics
Brent really does have some crazy stuff going on out there, must be the altitude
with a statement like that, we need pics
Brent really does have some crazy stuff going on out there, must be the altitude
I would concider something other than the M4 for logging all that info Mike. The M400, 600 or even 800 would be a better option.
Look on MoTeC's website for input/output specs.
Look on MoTeC's website for input/output specs.
The M4 is not the ecu you want if you want to log a lot of extra inputs. It only has 1 voltage input, 1 temp input, and 2 digital inputs. The M400 has 8 voltage, 6 temp, and 4 digital inputs.
well thats about a $988 difference in the ECU's... vs the Dashlogger at around ~$800, the PCS unit has 2 frequency inputs and 8 analog inputs... plus it gives you the display... cost wise its not a huge difference but you also have the dig display with the Dashlogger
in your honest opinion, would the m4/pcs combo be better than bumping up to an M400?
in your honest opinion, would the m4/pcs combo be better than bumping up to an M400?
The M400 would be better IMO. It has an onboard o-scope for troubleshooting and many other features that make it very worth.
The PCS is nice, but do you really need the visuals?
The PCS is nice, but do you really need the visuals?
<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by fieldafm »</TD></TR><TR><TD CLASS="quote">
in your honest opinion, would the m4/pcs combo be better than bumping up to an M400? </TD></TR></TABLE>
All depends what you're looking for in the ecu, what all do you want it to be able to control. From strictly a logging standpoint, an external dash/logger might be a decent option, but you loose all the extra functionality of the M400. It all comes down to what you want the ecu to do. If you want it to fire the injectors and coils and turn on a fan, then the M4 will do the trick. If you want it to turn on a shift light based on ground speed so your shift light comes on perfect every time in your FWD car that spins the tires, or if you want to be able to control any output based on any input or function read in the ecu, or anything crazy/useful you can think of, then the M400 is what you want.
in your honest opinion, would the m4/pcs combo be better than bumping up to an M400? </TD></TR></TABLE>
All depends what you're looking for in the ecu, what all do you want it to be able to control. From strictly a logging standpoint, an external dash/logger might be a decent option, but you loose all the extra functionality of the M400. It all comes down to what you want the ecu to do. If you want it to fire the injectors and coils and turn on a fan, then the M4 will do the trick. If you want it to turn on a shift light based on ground speed so your shift light comes on perfect every time in your FWD car that spins the tires, or if you want to be able to control any output based on any input or function read in the ecu, or anything crazy/useful you can think of, then the M400 is what you want.



