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...