|
s5fourdoor
|
 |
« Reply #30 on: August 01, 2011, 10:22:17 AM »
|
|
|
just a quick suggestion / thought.
is there anyway you can add an option to do "synched timing".
this means if i enable / config the logger to use "synched timing", it will start the log exactly on the computer's clock second: aka 11:05:10.0000 AM like that?
this would greatly assist users to fuse multiple logging sources... just a thought!
Is the timestamp really used to sync logs from different sources? From what I read here, a synchronization would be made by comparing rpm data. But yes, I could implement something like this. Also an option to get absolute timestamps instead of relative time since start would be possible. Have to make some tests .... Ha - I have to totally honest. I don't know... but it seemed like a decent-enough idea. I suppose RPM would be better, but it might all be relative depending on the frequency of data-update. |
|
|
|
|
Logged
|
|
|
|
|
s5fourdoor
|
|
« Reply #31 on: August 01, 2011, 10:23:29 AM »
|
|
|
That is the problem with the innovate stuff... no RPM unless you add another box.
yea i landed up getting the ot2 to log the rpm with the innovate wideband, i figured that was easier than getting their other input box where you have to configure the rpm signal. What do you think about it? Have you had the chance to use the Wideband AFR matrix that does averaging? I thought that looked really powerful. Also, how are you going to log using this tool while using the OT-2? Just wondering... |
|
|
|
|
Logged
|
|
|
|
Jason
Hero Member
Karma: +38/-0
 Offline
Posts: 500
Breaks everything!
|
|
« Reply #32 on: August 01, 2011, 10:55:35 AM »
|
|
|
For me, I just thought about reading the data as it's being dumped out of the ME7Logger, and appending the wideband data from the Innovate SDK. The max sample rate I could achieve with the MarkP layout was 33hz, so I think the results would be better than the current "educated guess" method of aligning the log based on throttle lift.
|
|
|
|
|
Logged
|
|
|
|
|
|
|
RaraK
|
|
« Reply #34 on: August 02, 2011, 07:50:46 AM »
|
|
|
good stuff nyet, going to test it out tonight  |
|
|
|
|
Logged
|
|
|
|
s4rmm
Jr. Member
Karma: +4/-1
Offline
Posts: 28
|
|
« Reply #35 on: August 02, 2011, 08:51:09 AM »
|
|
|
It works with NefMoto and with VCDS, it is in dumb mode. I created virtual comport (usb to serial), configured as COM2 or COM7, but did not manage to connect.
What is the output? Just telling it can't connect or something more? Are you referencing the right ecu characteristics file in your trace config? If a wrong characteristics file is used, the logger could try to connect to a wrong address. I'm referencing the characteristics file I created from my ECUs binary. Used Ecu definition is: [Communication] Connect = SLOW-0x11 Communicate = HM0 LogSpeed = 57600 [Identification] HWNumber = "0261206776" SWNumber = "1037354123" PartNumber = "8D0907551G" SWVersion = "0001" EngineId = "2.7l V6/5VT" Here's the output: Logged data size is 101 bytes. Start connecting to ECU at 02.08.2011 17:17:17.515 try connect slow(11) try connect slow(11) Could not connect => Could not connect to ECU, exiting ... => Logging failed exiting (cause=0x4)... |
|
|
|
|
Logged
|
|
|
|
|
jibberjive
|
|
« Reply #36 on: August 05, 2011, 11:55:07 PM »
|
|
|
I just found this. Awesome work Setzi!
|
|
|
|
|
Logged
|
|
|
|
|
ThomasRS4
Guest
|
|
« Reply #37 on: August 06, 2011, 03:14:54 PM »
|
|
|
Great work, thanks to share this awesome tool...
But I have a connecting problem with my RS4 8D0907551K.
My USB-Adapter works with Nefmoto, VAGCom and other diagnostic tools without problems.
The original 551K image is stored and the .ecu file is successfull generatet by ME7Info.exe.
A config file is also written.
Logged data size is 101 bytes.
Start connecting to ECU at 05.08.2011 20:01.22.111
try connect slow(11)
try connect slow(11)
Could not connect
=> Could not connect to ECU, exiting ...
=> Logging failed
exiting (cause=0x4)...
At the beginning of a connection with VAGCom, you can here a short clicking in the instrumentcluster.
When I try to connect with ME7Logger there is no clicking.
Can anybody help?
Thanks
Tom
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #38 on: August 09, 2011, 05:51:10 PM »
|
|
|
I love this tool. Simply amazing. thanks setzi!
one small bug complaint: you MUST use spaces to separate fields, you can't use tabs.
|
|
|
|
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
dirtyr32
Newbie
Karma: +0/-0
Offline
Posts: 1
|
|
« Reply #39 on: August 09, 2011, 07:46:22 PM »
|
|
|
First off, thank you for getting this tool out there, it's going to help a lot of people see whats going on under the hood. I have an '08 R32, and while I can log fairly quickly in vcds (getting ~10-12 samples/sec) I'd really like to open up my logging options with this tool. Not that I need to change much right now, but I love the data, and really want to verify some upcoming mods I'd like to do with some good information. Nothing else I've found supports these later ME7.1.1 ECU's, so I was hoping some small tweaks to yours would be all that is needed to work with these later ME7 ecu images properly. Right now it's not detecting any ram locations/variables at all: C:\ME7Logger\bin>ME7Info.exe "..\images\VW Golf MK5 R32 0261201807 022906032KR 1037387913.bin"
read 1300 map entries
mapped 186 aliases
written 0 definitions
written output to file C:\ME7Logger\ecus\VW Golf MK5 R32 0261201807 022906032KR 1037387913.ecu
C:\ME7Logger\bin> I've attached a bin from the same ECU. |
|
|
|
|
Logged
|
|
|
|
|
matchew
|
|
« Reply #40 on: August 10, 2011, 02:54:19 AM »
|
|
|
MK5 R32 is a completely different structure of code...
|
|
|
|
|
Logged
|
|
|
|
setzi62
Full Member
Karma: +142/-0
Offline
Posts: 249
|
|
« Reply #41 on: August 10, 2011, 04:03:37 AM »
|
|
|
Yes, this MK5 R32 image looks completely different to older R32 images (which can be processed by ME7Info). I think this ECU is based on ST10 which is C167 compatible, but the bootrom must be completely different. So, no chance to get the info tool working for this MK5 R32 image  and also the logger will not run (hopefully it will detect this is a non-supported ecu). Next update will allow TABs in config files, support sync to full second at logging start, and optional absolute timestamps (for easier synchronization with other logs). I will prepare this within the next days. |
|
|
|
|
Logged
|
|
|
|
setzi62
Full Member
Karma: +142/-0
Offline
Posts: 249
|
|
« Reply #42 on: August 10, 2011, 04:09:39 AM »
|
|
|
And, I am looking into the connection problems reported by
s4rmm and ThomasRS4. Would be good to find out what is blocking there,
but currently I don't have a concrete hint what to change to get it connecting.
|
|
|
|
|
Logged
|
|
|
|
tobz
Full Member
Karma: +3/-1
Offline
Posts: 60
|
|
« Reply #43 on: August 11, 2011, 06:16:42 PM »
|
|
|
First off, I want to say: thank the fucking lord. VCDS logging is god awful slow and I'm glad someone finally created a program so we don't have to pay for / deal with the bugginess of ECU Explorer. I plan on creating a small .NET app that wraps ME7Info/ME7Logger to make it dead simple to generate your ECU definitions and then run the logger.
Anyways, having some issues... I'm getting "Got error -8" while logging. Lowering the baud rate/sample rate helped a little bit, but it always happens. It'll say it about 8 - 10 times then the logger will exit with code 0x4. Not sure what's going on, but VCDS works no problem and I'm using a blue KKL cable.
Any thoughts?
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #44 on: August 11, 2011, 11:36:12 PM »
|
|
|
One more minor thing: 2.7t mbox was missing zwbasar_4 and zwbasar_5
|
|
|
|
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
|
