|
bamofo
|
 |
« Reply #495 on: June 26, 2020, 07:45:42 AM »
|
|
|
Question for ME7INFO.exe
Im getting an error about illegal Range when trying to get any of the ST10 8e2910560 roms to create ECU files. IS there a force/fix/way around the illegal range? or another tool that maps out the ram locations correctly?
C:\ME7Logger120>ME7Info.exe 8E2910560A-0030-Stock.bin
read 1116 map entries
mapped 198 aliases
findfirst in illegal range 0000FEE6 - 008FFFDF
findfirst in illegal range 0000FEE6 - 00000000
findfirst in illegal range 0000FEE6 - 00000000
findfirst in illegal range 0000FEE6 - 00000000
findfirst in illegal range 0000CE1B - 008FFFDF
findfirst in illegal range 0000CE1B - 00000000
written 0 definitions
written output to file C:\ME7Logger120\logs\8E2910560A-0030-Stock_template.cfg
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #496 on: June 26, 2020, 09:18:26 AM »
|
|
|
me7info does not support st10, period. It is a totally different CPU.
Even worse, its closed source abandonware.
There are other tools sitting in the nef repo, particularly the swiss army knife tool that could be adapted to st10
|
|
|
|
|
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
|
|
|
|
bamofo
|
|
« Reply #497 on: June 29, 2020, 11:43:12 AM »
|
|
|
me7info does not support st10, period. It is a totally different CPU.
Even worse, its closed source abandonware.
There are other tools sitting in the nef repo, particularly the swiss army knife tool that could be adapted to st10
It does support some of the ST10 ECU's Ive used it on many of them already. But 8e2 is a different ST10 that it must not work with... Ill check that out. Thanks! |
|
|
|
|
Logged
|
|
|
|
chrislovevdub
Newbie
Karma: +0/-0
 Offline
Posts: 1
|
|
« Reply #498 on: April 08, 2021, 11:46:44 AM »
|
|
|
i cant get this to work on my laptop, i get as far as trying to copy my map file into the ecu folder with the command screen and it says cannot open binary file please help!!!  im a total noob and trying to learn please dont dig me out hahaha |
|
|
|
|
Logged
|
|
|
|
rdrage
Jr. Member
Karma: +13/-1
Offline
Posts: 29
|
|
« Reply #499 on: April 28, 2021, 09:15:26 AM »
|
|
|
Do you have any screenshot of the output windows in CMD ?
|
|
|
|
|
Logged
|
|
|
|
rdrage
Jr. Member
Karma: +13/-1
Offline
Posts: 29
|
|
« Reply #500 on: April 28, 2021, 09:28:52 AM »
|
|
|
Make sure you have a FDTI OBD2 cable. Not all cheap blue cables work. Have you install FDTI 2.X drivers ? Try to choose FTDI instead for com port ? Have you correct .ecu/bin file ? Have you immo off ?  |
|
|
|
|
Logged
|
|
|
|
|
golfputtputt
|
|
« Reply #501 on: July 12, 2021, 08:34:56 PM »
|
|
|
I've been trying to get my VCDS Hex-Can cable working with ME7L (through the gui visual logger) It's got the VCP installed. I've tried enabling the VCP via device manager driver properties and without. I've tried all COM ports and tried FTDI -> USB or USB1,2, serial. I keep getting: Error! Exit Code:1
Serial Open - Unable to open port (error=2)
can't open serial port COM3
exiting (cause=0x1)... Or some version of that depending on option chosen. Not sure where to proceed. Any advice? A blue KKL with the drivers installed from the boot disk was the only successful way to log. FTDI drivers from site installed on blue KKL failed. I'd like to have 1 cable to rule them all (flashing, logging, VCDS block checks, coding, etc). |
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #502 on: July 12, 2021, 09:41:14 PM »
|
|
|
If you enabled VCP it should tell you which com port it is on
|
|
|
|
|
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
|
|
|
|
golfputtputt
|
|
« Reply #503 on: July 13, 2021, 05:31:42 AM »
|
|
|
I was looking for it in device manager and serial bus interface properties where it pops up but its not shown/declared. If you enabled VCP it should tell you which com port it is on
|
|
|
|
|
Logged
|
|
|
|
|
golfputtputt
|
|
« Reply #504 on: July 13, 2021, 03:04:54 PM »
|
|
|
Got it. Forgot to install ftdiport driver on the virtual port. It also didn't pop up as a port in device manager first few times until i restarted today.
|
|
|
|
|
Logged
|
|
|
|
mikeb1223
Newbie
Karma: +1/-4
Offline
Posts: 11
|
|
« Reply #505 on: August 27, 2021, 02:24:55 AM »
|
|
|
It does support some of the ST10 ECU's Ive used it on many of them already. But 8e2 is a different ST10 that it must not work with... Ill check that out. Thanks!
I Agree it works on 551R 551T and 551S ECUs |
|
|
|
« Last Edit: August 27, 2021, 02:27:17 AM by mikeb1223 »
|
Logged
|
|
|
|
mophk
Newbie
Karma: +0/-0
Offline
Posts: 16
|
|
« Reply #506 on: April 04, 2024, 05:29:23 PM »
|
|
|
guys, is it possible that the cables break in a way that logger stops working after some time?
riddle me this:
ive been using 8d0 551g flash for the past few years on my car, the logger was working flawlessly about 6 months ago. recently ive got some more time to finish my tune but i couldnt connect using 0x11 slow method. i didnt change anything in the loom, same hw ecu, same cluster etc. ive patched the ecu tp use 0x00 slow method and it did work.
now i have a different car, same hw ecu(part of the tuning) , 98my s4 b5, patched flash and while the logger can connect it times out quickly with the info about wrong file format. the loggers log indicates timeouts, and loggers output doesnt show anything weird.
ive tried pulling the dash fuse, vcp port, bauds, sample rates, modes (0x11 and 0x00 - first one does not connext at all, second dies after 1-10 samples), tried smaller list of variables (as low as 20) and nothing helped.
i didnt try different cable but i will, and i didnt add direct kline wire, i doubt it will help as it did work 0.5y ago.
|
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #507 on: April 05, 2024, 01:10:40 AM »
|
|
|
The earlier cars there is pretty much no way to get it working stable because cluster closes connection.
Maybe there's some magic handshake to make the cluster "shut up", but ME7Logger doesn't do it, and my tool does not either.
The only way is to run a direct K-Line to the OBD II port bypassing the cluster... Or installing a cluster from 2000+.
The clusters that have immo 3 (or no immo at all) do not have this issue.
From what I have found it is only possible to have a stable connection when the engine is not running, by using the SLOW-0x00 or fast init methods and only with 124800 baud. Probably because this was meant from the factory for flashing the ECU.
As soon as you start it, the cluster starts closing the connection, even with these settings.
Even if you patch the ECU to allow SLOW-0x00 with engine running, it can connect, but not maintain a steady connection. On the Immo3 cluster it does not disconnect you when you start the engine and with the ECU patched it is also possible to make the connection when the engine is running, and it is completely stable.
This is only an issue on early EU 2.7TT, because the RS4 are all Immo3 and all 2000+ cars also use compatible clusters. The ECU's have files 8D0907551 and 8D0907551C on a 29F400 chip from the factory.
Because the issue is purely with the cluster, even if you install a newer ECU with immobilizer disabled, then it does not change anything.
When I was tuning these cars, I used a special ECU that had emulator inside and it's own OBD II port with direct K-Line, power and ground connections, and I cut the original K-Line inside the ECU.
Because the 29F800 ECU can run 29F400 software (just double stack it), then it could be used for every 2.7TT with ME7.1 (but not the newer ME7.1.1 variants).
|
|
|
|
« Last Edit: April 05, 2024, 01:24:42 AM by prj »
|
Logged
|
|
|
|
mophk
Newbie
Karma: +0/-0
Offline
Posts: 16
|
|
« Reply #508 on: April 05, 2024, 03:47:21 AM »
|
|
|
thanks prj for that, that makes sense.
how about the other car? its immo3 ecu/cluster c5 allroad, that worked few months ago. broken cable?
|
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #509 on: April 05, 2024, 04:14:48 AM »
|
|
|
thanks prj for that, that makes sense.
how about the other car? its immo3 ecu/cluster c5 allroad, that worked few months ago. broken cable? Yeah probably, that should work with SLOW-0x00 at least. Some of these cables have really bad efficiency linear voltage regulators that are not fixed to large enough cooling pads, so they overheat/crack over time. My recommendation is as always to use my logger (free for ME7) with a genuine J2534 interface like the OpenPort, but of course it's somewhat more expensive. |
|
|
|
|
Logged
|
|
|
|
|
