Logging data to a file
mgillam wrote: I have a re-mapped Mems 3 ECU and get a P0501 rough road detection code. I suspect that the re-map may have been done on a non-ABS car and then when uploaded to my car which has ABS. I'm concerned the ABS may have been affected and was hoping to track the live data so I could investigate further. On ABS cars I believe the rough road signal is passed from the ABS ECU on a hardwired output to pin 78 of the Mems ECU. How this works I am not sure but the signal is in the form of a square wave digital pulse train of between 0 and 5 V at 8000 pulses per mile. On non ABS cars there is a reluctor ring is fitted to the LH rear wheel and provides 48 pulses per rotation which is adapted and then sent to the same pin. I can't find this live data on pscan is this something you can add to the "wish list"? Thanks
Is this on a Rover 75 or a 25/45/MGF?
Please Log in or Create an account to join the conversation.
• how it calculates the inlet temperature as I think the later cars didn't have an inlet temperature sensor
• Why the vehicle speed always reads zero
• not sure what the "Torque conv clutch pos sens voltage" is
• or the "Adaption of throttle valve act motor"
• or the “Additive mixture correction IV error”
• Why injection time reads zero at 3 minutes 15 seconds
Thanks
Please Log in or Create an account to join the conversation.
- talkingcars
- Offline
- Moderator
- Posts: 6876
- Thanks: 1296
"• not sure what the "Torque conv clutch pos sens voltage" is"
is for the stepspeed.
Home to black Alfa Romeo 159 3.2 V6 Q4 ,green MGF VVC and red MG Maestro T16.
MG - the friendly marque.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
The old way was that the protocol would cycle through all of the selected parameters and dump the data into a big table in memory, simultaneously the graphic user interface would cycle around at a completely different rate, collecting data from the memory and rendering it onto screen.
For looking at live data on the screen that was fine, because the human eye can't really tell how often it updates, but for the tsv files it was producing multiple lines with the same data, and hence appearing to update faster than the screen was.
From version 0432 the protocol now timestamps every piece of data it collects from the ECU and also puts the timestamp in memory.
When the graphical user interface is cycling around and around it will only display, or log to file data that it hasn't seen before.
Also the timestamp in the left column of the table should now be a lot more accurate.
Please Log in or Create an account to join the conversation.
Pete
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.