Torque PIDs...Take 2

ShoBoat said:
SHOnUup said:
Gauge shows activity with the blinking square but no misfires to report on.

That's a good thing, did you check the other one? Misfire Trips?


Sent from my iPhone using Tapatalk
No, will put up next time. As you stated above this will start with a # then take 5 trips to reset?
 
No, 5 misfires during a drive cycle will cause it to reset. Otherwise it will keep counting. Once a series of misfires occurs it will reset to 0.


Sent from my iPhone using Tapatalk
 
SHOnUup said:
MSF Trips loaded up...reading 54 as I just started car?

Yup, so you have had 54 drive cycles since a Misfire event, reset codes or battery disconnect.


Sent from my iPhone using Tapatalk
 
It looks like I need a little help with the Misfire Gauge. I can confirm that's it's not working. The Misfire Trips gauge is working correctly, anyone?


Sent from my iPhone using Tapatalk
 
ShoBoat said:
It looks like I need a little help with the Misfire Gauge. I can confirm that's it's not working. The Misfire Trips gauge is working correctly, anyone?


Sent from my iPhone using Tapatalk
I'm willing to help once I have a few moments...What is the Forscan PID showing...total number of misfires or per cylinder?  The challenge with this is its best to capture the serial data when actual misfires occur so you can see the binary results.  This is challenging since Misfires occur so quickly...or not at all if everything is running perfect.
 
The misfire gauge is interesting to me but that might be a problem in itself. I find a lot of them interesting and so I'm running a lot of gauges. I wonder if there is an upper limit which should be avoided. I also wonder if a gauge that's on a screen that's not being displayed is still adding to the PID load. Got to stop adding gauges. I'm turning into a gauge junkie!
 
Larrylu said:
The misfire gauge is interesting to me but that might be a problem in itself. I find a lot of them interesting and so I'm running a lot of gauges. I wonder if there is an upper limit which should be avoided. I also wonder if a gauge that's on a screen that's not being displayed is still adding to the PID load. Got to stop adding gauges. I'm turning into a gauge junkie!
But they look so good, Larry!  Yeah there is a limit to the concurrent PIDs that can be polled, but I think it is about 100 with the the OBDLink, around 30 with the generic ELM adapters, at least on BlueTooth.  Not sure about wireless.
 
ecoboostsho said:
ShoBoat said:
It looks like I need a little help with the Misfire Gauge. I can confirm that's it's not working. The Misfire Trips gauge is working correctly, anyone?


Sent from my iPhone using Tapatalk
I'm willing to help once I have a few moments...What is the Forscan PID showing...total number of misfires or per cylinder?  The challenge with this is its best to capture the serial data when actual misfires occur so you can see the binary results.  This is challenging since Misfires occur so quickly...or not at all if everything is running perfect.

The gauge is a running total of misfires during the current drive cycle. It's happened once to twice that I had a few on startup. And when I started FORSCan it registered as 2 as soon as I started the log. So as long as you can get it to report one we should be able to figure it out.



The misfire gauge is more than just interesting! It gives you an insight to how the car is running. Fouled plugs? Gaping incorrect? Bad wire? Oil getting into the intake? You can tell a lot from it.


Sent from my iPhone using Tapatalk
 
Um quick dumb question, how bad would it be to start the car with one coil unplugged for a few seconds? That's one sure fire way to get the data we need.


Sent from my iPhone using Tapatalk
 
SHOdded said:
Larrylu said:
The misfire gauge is interesting to me but that might be a problem in itself. I find a lot of them interesting and so I'm running a lot of gauges. I wonder if there is an upper limit which should be avoided. I also wonder if a gauge that's on a screen that's not being displayed is still adding to the PID load. Got to stop adding gauges. I'm turning into a gauge junkie!
But they look so good, Larry!  Yeah there is a limit to the concurrent PIDs that can be polled, but I think it is about 100 with the the OBDLink, around 30 with the generic ELM adapters, at least on BlueTooth.  Not sure about wireless.
Yes this is absolutely true!  However I would just like to make sure that Larry realizes these are scanned sequentially and if you have 100 PIDS that is probably the Max rating of the MX and its a per second number.  The implication here is that you would only get a reading of a single PID every second.  More than fine for things like temperatures but if you want some degree of resolution on your Knock number then I highly recommend you use as few PIDs as possible so you don't miss events.  This car can throw massive a lot of data on the CAN bus at one time and could overwhelm Torque pretty quickly as we've already proven it isn't the fastest thing in the world.

Now what I don't know is how many it is actually reading at one time...if its just what is on the screen or scanning all of them that are in the list every time.  I do know the gauges don't update unless you are actually viewing them...I'm not positive that means they aren't still reading them in the background.  I do know that if you are actually logging with Torque (I wouldn't bother...its too slow) or you have an "alarm" set up on a PID then it reads them all the time.  So use that sparingly if you do. 

Just my 2 cents...
 
ShoBoat said:
Um quick dumb question, how bad would it be to start the car with one coil unplugged for a few seconds? That's one sure fire way to get the data we need.


Sent from my iPhone using Tapatalk
I've contemplated this but just can't bring myself to do it...It would obviously be dumping fuel in the cylinder but if you are talking idle I "doubt" it would hurt much but really don't know.  Cars obviously lose coils and plugs all the time so this happens and I doubt you will be rebuilding your motor because of it BUT I'm paranoid. :)
 
ecoboostsho said:
SHOdded said:
Larrylu said:
The misfire gauge is interesting to me but that might be a problem in itself. I find a lot of them interesting and so I'm running a lot of gauges. I wonder if there is an upper limit which should be avoided. I also wonder if a gauge that's on a screen that's not being displayed is still adding to the PID load. Got to stop adding gauges. I'm turning into a gauge junkie!
But they look so good, Larry!  Yeah there is a limit to the concurrent PIDs that can be polled, but I think it is about 100 with the the OBDLink, around 30 with the generic ELM adapters, at least on BlueTooth.  Not sure about wireless.
Yes this is absolutely true!  However I would just like to make sure that Larry realizes these are scanned sequentially and if you have 100 PIDS that is probably the Max rating of the MX and its a per second number.  The implication here is that you would only get a reading of a single PID every second.  More than fine for things like temperatures but if you want some degree of resolution on your Knock number then I highly recommend you use as few PIDs as possible so you don't miss events.  This car can throw massive a lot of data on the CAN bus at one time and could overwhelm Torque pretty quickly as we've already proven it isn't the fastest thing in the world.

Now what I don't know is how many it is actually reading at one time...if its just what is on the screen or scanning all of them that are in the list every time.  I do know the gauges don't update unless you are actually viewing them...I'm not positive that means they aren't still reading them in the background.  I do know that if you are actually logging with Torque (I wouldn't bother...its too slow) or you have an "alarm" set up on a PID then it reads them all the time.  So use that sparingly if you do. 

Just my 2 cents...

Thanks guys for the collective thoughts on my questions. Good info!  I was surprised to hear about the "alarm" priority....had no clue on that! 
 
ShoBoat said:
Um quick dumb question, how bad would it be to start the car with one coil unplugged for a few seconds? That's one sure fire way to get the data we need.


Sent from my iPhone using Tapatalk
Had this same thought yesterday. Crazy?
 
I would guess the car would set a misfire code and possibly stall, if let run long enough.  One of the scenarios the programmers should have accounted for.
 
SHOdded said:
I would guess the car would set a misfire code and possibly stall, if let run long enough.  One of the scenarios the programmers should have accounted for.

Back in the day on carbureted cars, used to happen all the time. Plug and wire failures were quite common. I could install one of the older plugs and widen the gap a little. That would also work.


Sent from my iPhone using Tapatalk
 
Back
Top