|
TTQS
Guest
|
 |
« Reply #120 on: December 28, 2011, 02:32:42 PM »
|
|
|
Default is COM port 2 IIRC, but it is an accepted argument.
It was selected USB in VCDS when I unchecked boot in intelligent mode, but I guess I could try selecting COM2 in VCDS. I'm using the GUI and I did try typing USB into the COM port box but that didn't work either. I've just ordered a normal, cheap 409.1 KKL VAG cable from eBay to avoid any future complications with the genuine Ross Tech interface. Maybe that might help. TTQS |
|
|
|
« Last Edit: December 28, 2011, 03:09:16 PM by TTQS »
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #121 on: December 28, 2011, 06:22:47 PM »
|
|
|
Default is COM port 2 IIRC, but it is an accepted argument.
It was selected USB in VCDS when I unchecked boot in intelligent mode, but I guess I could try selecting COM2 in VCDS. I'm using the GUI and I did try typing USB into the COM port box but that didn't work either. I've just ordered a normal, cheap 409.1 KKL VAG cable from eBay to avoid any future complications with the genuine Ross Tech interface. Maybe that might help. TTQS You need to open Device Manager from the Window's Control Panel and expand the Ports tree. You should have a USB serial port with the current COM port displayed. You can assign it to a different port by double clicking it to bring up the properties window. Then, click the Port Settings tab and select the Advanced button. |
|
|
|
|
Logged
|
|
|
|
|
TTQS
Guest
|
|
« Reply #122 on: December 29, 2011, 02:37:50 AM »
|
|
|
You need to open Device Manager from the Window's Control Panel and expand the Ports tree. You should have a USB serial port with the current COM port displayed. You can assign it to a different port by double clicking it to bring up the properties window. Then, click the Port Settings tab and select the Advanced button.
Thanks. Makes sense, I'll try that. TTQS |
|
|
|
|
Logged
|
|
|
|
lezsi
Jr. Member
Karma: +1/-1
 Offline
Posts: 36
|
|
« Reply #123 on: January 04, 2012, 11:45:32 AM »
|
|
|
This logger is awesome!
Unfortunately my car (seat leon 1.8t AUQ) seems to have the busy K-line problem, it drops connection after a few seconds when ignition is on. (It's fine when ignition is off).
How others cured this problem? Do you have some details where/how to route a "dedicated" K-line from the ECU if necessary?
Thanks
|
|
|
|
|
Logged
|
|
|
|
carlossus
Sr. Member
Karma: +38/-0
Offline
Posts: 394
Leon Curpa Stg1+
|
|
« Reply #124 on: January 04, 2012, 12:24:59 PM »
|
|
|
Unfortunately my car (seat leon 1.8t AUQ) seems to have the busy K-line problem, it drops connection after a few seconds when ignition is on. (It's fine when ignition is off).
How others cured this problem? Do you have some details where/how to route a "dedicated" K-line from the ECU if necessary?
I take it you read my Leon thread http://nefariousmotorsports.com/forum/index.php?topic=1021.msg10463#msg10463 here? For me it's fine if I keep the "Log packet size: 36 bytes" or less which gives me 24 variables to log which is enough for me for most of my tinkering. I regularly log my 25minute journey to work without a timeout. You can maximise the number of vars by choosing the single byte versions where you have a choice. Out of interest, what's your ECU version? It might be better to post in the thread above to keep these issues together. |
|
|
|
« Last Edit: January 04, 2012, 12:26:39 PM by carlossus »
|
Logged
|
|
|
|
tkla
Newbie
Karma: +0/-0
Offline
Posts: 8
|
|
« Reply #125 on: January 08, 2012, 03:24:16 PM »
|
|
|
cool!
|
|
|
|
« Last Edit: January 08, 2012, 03:58:09 PM by tkla »
|
Logged
|
|
|
|
All_Euro
Newbie
Karma: +0/-0
Offline
Posts: 15
|
|
« Reply #126 on: January 09, 2012, 09:21:02 PM »
|
|
|
Finally had a chance to start using the Me7Logger - awesome stuff!
Question: has anyone else noticed their correction factors to be completely different than what VCDS logs? I'm trusting the Me7Logger values but still curious.
Thanks
|
|
|
|
|
Logged
|
|
|
|
|
TTQS
Guest
|
|
« Reply #127 on: January 10, 2012, 08:31:35 AM »
|
|
|
Finally had a chance to start using the Me7Logger - awesome stuff!
Question: has anyone else noticed their correction factors to be completely different than what VCDS logs? I'm trusting the Me7Logger values but still curious.
Thanks
Is that because of this (from the previous page on this post)? http://nefariousmotorsports.com/forum/index.php?topic=837.msg11613#msg11613TTQS |
|
|
|
|
Logged
|
|
|
|
All_Euro
Newbie
Karma: +0/-0
Offline
Posts: 15
|
|
« Reply #128 on: January 10, 2012, 12:25:36 PM »
|
|
|
I'm just realizing my question was pretty vague... in VCDS I show a fair amount of ignition timing pull in cyl#4 & with Me7Logger I rarely get any from that cylinder - I'm surprised at how much of a difference there is. |
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #129 on: January 10, 2012, 12:28:01 PM »
|
|
|
I'm just realizing my question was pretty vague... in VCDS I show a fair amount of ignition timing pull in cyl#4 & with Me7Logger I rarely get any from that cylinder - I'm surprised at how much of a difference there is.
I haven't seen that variation. |
|
|
|
|
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
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #130 on: January 10, 2012, 12:57:59 PM »
|
|
|
The one possibility I could think of, is that the ECU clears that variable each cycle, and then sets it to a new value. It is possible the ME7Logger is ready the value after it has been cleared, but before it is set. This is just a guess though.
|
|
|
|
|
Logged
|
|
|
|
Lobuziak
Newbie
Karma: +1/-0
Offline
Posts: 15
|
|
« Reply #131 on: January 15, 2012, 02:33:03 PM »
|
|
|
Hello.
I'm new to that great knowledgeable forum but have a request/question.
What would be needed to add different Motronic ECU support for ME7logger? How can I get RAM variables addresses?
My cars ECU is Me1.5.5 it has 512KB data file. The car is Opel Astra Coupe 2.0T. I have a damos for it and it looks similar to ME7.1
Tried use the tool and make some logs - "written 13 definitions" - but didn't want to make logs because of the unknown bootrom.
edit: if that helps WinOLS Demo shows processor: Siemens C167CR
Regards
Lobuziak
|
|
|
|
« Last Edit: January 15, 2012, 03:48:10 PM by Lobuziak »
|
Logged
|
|
|
|
setzi62
Full Member
Karma: +142/-0
Offline
Posts: 249
|
|
« Reply #132 on: January 20, 2012, 08:45:02 AM »
|
|
|
The ME1.5.5 might be same CPU and contain same maps as the ME7, but the basic software
is completely different. Since the ME7Logger depends definitely on the bootrom of the ME7,
it is not possible to port it easily to another ECU type. Same is true for the ME7Info tool.
|
|
|
|
|
Logged
|
|
|
|
Lobuziak
Newbie
Karma: +1/-0
Offline
Posts: 15
|
|
« Reply #133 on: January 20, 2012, 11:34:20 AM »
|
|
|
The ME1.5.5 might be same CPU and contain same maps as the ME7, but the basic software
is completely different. Since the ME7Logger depends definitely on the bootrom of the ME7,
it is not possible to port it easily to another ECU type. Same is true for the ME7Info tool.
So to get it working someone should get the bootrom with minimon, disassemble it, disassemble flash rom correlate it with damos and make some more testing... If there was a good working logger that would help with tuning of the car. There is some how working op-com but I don't get any knock control action, air mass and load is wrongly calculated... Anyway thanks. Regards Lobuziak |
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #134 on: January 22, 2012, 03:53:14 PM »
|
|
|
Has anyone with an Euro 2.7 gotten this to work? I get this: Logged data size is 72 bytes.
Start connecting to ECU at 23.01.2012 00:38:51.109
try connect slow(11)
try connect slow(11)
Could not connect
try connect slow(11)
22:38:56.656-252,0 os_setspeed(speed=10400)
22:38:56.963-321,4 os_receiver_off()
22:38:56.963-586,3 os_setbreak()
22:38:57.164-499,2 os_clrbreak()
22:38:57.365-932,4 os_setbreak()
22:38:57.566-520,4 os_setbreak()
22:38:57.767-140,4 os_setbreak()
22:38:57.968-995,3 os_clrbreak()
22:38:58.170-738,3 os_setbreak()
22:38:58.372-139,3 os_setbreak()
22:38:58.572-750,3 os_setbreak()
22:38:58.773-447,3 os_clrbreak()
22:38:58.775-066,5 os_receiver_on()
22:38:59.278-435,8 os_rcvbyte(timeout=500) -> TIMEOUT
try connect slow(11)
22:38:59.278-975,8 os_setspeed(speed=10400)
22:38:59.585-279,8 os_receiver_off()
22:38:59.585-555,8 os_setbreak()
22:38:59.787-078,9 os_clrbreak()
22:38:59.988-297,8 os_setbreak()
22:39:00.189-228,9 os_setbreak()
22:39:00.390-282,7 os_setbreak()
22:39:00.591-733,7 os_clrbreak()
22:39:00.792-797,8 os_setbreak()
22:39:00.994-333,8 os_setbreak()
22:39:01.195-425,8 os_setbreak()
22:39:01.396-525,9 os_clrbreak()
22:39:01.398-050,7 os_receiver_on()
22:39:01.901-669,2 os_rcvbyte(timeout=500) -> TIMEOUT
Could not connect
=> Could not connect to ECU, exiting ...
=> Logging failed
exiting (cause=0x4)... VCDS Lite connects just fine using the same cable... I have immo on the car, and what I notice is, a relay in the cluster makes a "click" when VCDS Lite connects, but not when ME7Logger connects. On older motronics to use fast diag, the immo had to be bypassed. Am I right in thinking, that I need to run a direct K-Line from the ECU into the diagnostic port for this to work? Otherwise the immo is blocking all communication? |
|
|
|
|
Logged
|
|
|
|
|
