Autonerdz forums

I simply set up my frequency channels on the desired channels.

You will see that I have frequency lines too but these are not really needed, equally you do not need to scale in the formula as I have done, you can do that in the standard scaling to get obvious resolution..

I think I read a post by Tom that the frequency formula can now have the form "freq(A)" as opposed to "Freq(A-2)", Tom will need to confirm this if he will kindly do.

Your idea of torque converter implication is a food one, you simply need to thake the crankshaft frequency converted to rpm and divide that bty the input shaft frequency in much the same way as I have done with the input and output frequencies of the transmission itself.

Naturally to can simply add this to the example capture and run it all together.

The problem that I now have with BMW's that are fitted with mechatronics is that I cannot probe the sensors as it is all inside the mechatronics unit.

The signals are transmitted on the CAN as a CAN message.

Thus my previously published desire to be able to define the bytes of a CAN message and display them in the Picoscope window.

We can already decode the CAN bus, we need to be able to define the bytes within that CAN message that represent a signal and show them in the Picoscope window.

I have posted the file as an attachment so that you may load it up.

Logic wrote on May 12^th, 2015 at 6:56pm:



That is correct.  Signals that do not cross zero no longer need the modifier to move the frequency counter threshold. 

Not sure in what build that change was made.  We were never informed and discovered it quite by accident when trying to break a frequency math channel.

Been a while now though...