Gas Pedal Delay

Originally Posted by DIGItonium

Datalogging software isn't needed as long as the voltages can be recorded over time and stored in a comma delimited text file. I use open source library, ZedGraph, to graph data with several hundred thousands of points. If you guys like, I can write a simple program that uses this library to import individual csv files and plot them as separate graphs or overlays.

Datalogging with UpRev is one thing, but we need to acquire signals at the source (I/O control signals and driver output). The ECU and VVEL module output signals to control the throttle and VVEL actuators and each has its own position sensor, but I don't know the system well enough to determine if the control signal output to the actuator goes from A to B in X milliseconds that the actuator is expected to physically change positions from A to B in X milliseconds as well.

In other words, we might have a situation where the control signal expects the actuator to move from point A to B. The actuator does move from point A to B, but there is no mention about how fast it should get there to meet the timing tolerance. It is like playing an FPS game with a wireless keyboard and mouse getting pwned from the 0.5s lag.

Originally Posted by IcedZ

Good point.
Does anyone have a scrap OBD-II cable they would be willing to mail me? I literally just need the cable to plug into the car. I will be breaking it out into a breadboard, so I preferably do not want it coming from something working. I have an NI 14 bit DAQ that will be perfect for this.

Originally Posted by DIGItonium

Oh snaps... how many channels? I guess we can start with one side (i.e., left/right actuators and sensors) with common inputs (gas pedal potentiometer, temps, etc.). Definitely create the "cool" logs where the car behaves normally, and "hot" logs where the car starts lagging. I'll try to find some time this week to write a small program using ZedGraph.