Pages: 1 ... 32 33 [34]
Author Topic: Logging ME7 fast and flexible => ME7Logger  (Read 464471 times)
bamofo
Sr. Member
****

Karma: +34/-3
Offline Offline

Posts: 420


« 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
Administrator
Hero Member
*****

Karma: +604/-166
Online Online

Posts: 12232


WWW
« 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 guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

Please 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 experience.
bamofo
Sr. Member
****

Karma: +34/-3
Offline Offline

Posts: 420


« 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 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!!! Cry im a total noob and trying to learn please dont dig me out hahaha
Logged
rdrage
Jr. Member
**

Karma: +13/-1
Offline 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 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 ?


Wink
Logged
golfputtputt
Sr. Member
****

Karma: +6/-4
Offline Offline

Posts: 367


« 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:

Code:
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
Administrator
Hero Member
*****

Karma: +604/-166
Online Online

Posts: 12232


WWW
« 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 guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

Please 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 experience.
golfputtputt
Sr. Member
****

Karma: +6/-4
Offline Offline

Posts: 367


« 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
Sr. Member
****

Karma: +6/-4
Offline Offline

Posts: 367


« 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 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
Pages: 1 ... 32 33 [34]
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.02 seconds with 17 queries. (Pretty URLs adds 0s, 0q)