Pages: 1 ... 14 15 [16] 17 18 ... 34
Author Topic: Logging ME7 fast and flexible => ME7Logger  (Read 472560 times)
vagenwerk
Full Member
***

Karma: +2/-0
Offline Offline

Posts: 182


« Reply #225 on: January 26, 2013, 04:23:07 AM »

anyone ?
Logged
prj
Hero Member
*****

Karma: +915/-426
Offline Offline

Posts: 5833


« Reply #226 on: January 26, 2013, 06:34:00 AM »

Your install is probably corrupted due to a virus or similar, re-install it.
Logged

PM's will not be answered, so don't even try.
Log your car properly.
vagenwerk
Full Member
***

Karma: +2/-0
Offline Offline

Posts: 182


« Reply #227 on: January 26, 2013, 04:13:11 PM »

i re-download gui + logger re-install it there is still error

'Logged data size is 2 bytes.
can't locate function FT_GetLibraryVersion in dll
Initialization failed, exiting ...
exiting (cause=0x1)..."


i try many options but without succes

work like a charm and suddenly stopped after few days ?  any hints ?
Logged
phila_dot
Hero Member
*****

Karma: +171/-11
Offline Offline

Posts: 1709


« Reply #228 on: January 26, 2013, 04:43:25 PM »

That's an FTDI function.

Try reinstalling the driver.
Logged
sweegie
Full Member
***

Karma: +10/-2
Offline Offline

Posts: 137


« Reply #229 on: January 26, 2013, 05:27:59 PM »

Pull new FTDI drivers down and put ftd2xx.dll from the driver package into the me7logger bin directory. This should fix your issue.
Logged
nyet
Administrator
Hero Member
*****

Karma: +604/-166
Offline Offline

Posts: 12233


WWW
« Reply #230 on: January 26, 2013, 07:55:55 PM »

Pull new FTDI drivers down and put ftd2xx.dll from the driver package into the me7logger bin directory. This should fix your issue.

I wouldn't do this unless you really know what you are doing (i.e remember to delete the dll the next time you reinstall the drivers). Windows is really dumb with .dlls. You only need one wayward dll in yoru system and eveything can get screwed up.

Hell, i bet the poster's problem is due to something similar (a usb/serial dll floating around where it shouldnt).
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.
sweegie
Full Member
***

Karma: +10/-2
Offline Offline

Posts: 137


« Reply #231 on: January 27, 2013, 11:52:16 AM »

Hell, i bet the poster's problem is due to something similar (a usb/serial dll floating around where it shouldnt).

Yep, I agree it sounds like it. Windows *should* pick up a library dll in the same directory as the executable first, before attempting to locate it in system32 etc etc, but i dont trust it too much to behave like it's supposed to either....
Logged
nyet
Administrator
Hero Member
*****

Karma: +604/-166
Offline Offline

Posts: 12233


WWW
« Reply #232 on: January 27, 2013, 12:38:07 PM »

Its worse than that. Once that DLL is loaded in memory it *STAYS THERE * until the system is rebooted - and every app is forced to use it unless it deliberately tries to load a different dll. Absolutely retarded behavior, but thats windows for you.
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.
lsalt100
Newbie
*

Karma: +1/-0
Offline Offline

Posts: 12



« Reply #233 on: January 28, 2013, 04:53:07 PM »

Thanx for great tool!!

I've got some problems to connect, but reading this forum help much.
Now I use KKL pass through cable (blue one-china made-some ch340 chip inside).
"SLOW-0x00" in ecu settings file, and starting LOGGER before starting engine.
Everything works fine.

so once again thanx for very useful tool!!!



now is time to analyze logs ;-)
Logged

ford galaxy 2,8 V6 LPG (2004)
temanuele
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 7


« Reply #234 on: March 05, 2013, 08:52:58 PM »

Been having some issues connecting lately, so I'm wondering if I am doing something obviously wrong. I have used this same computer, cable and car for all my previous logging, so I'm not sure what happened. I have also tried both M-box 001 and 001 bin files. I have also tried different computers, cables and cars and get the same error so I'm guessing it is user error. If anyone could help me out, it would be greatly appreciated. I keep getting this error message:

-> Reading log config file C:\Users\Chuck\Desktop\ME7Logger_DIST_02042012_v1.17\
logs\2001.5 Audi S4 8D0907551M 0261207143_template.cfg .... done
-> Reading ecu characteristics file C:\Users\Chuck\Desktop\ME7Logger_DIST_020420
12_v1.17\ecus\2001.5 Audi S4 8D0907551M 0261207143.ecu .... done
Used Ecu definition is:
[Communication]
Connect      = SLOW-0x11
Communicate  = HM0
LogSpeed     = 56000

[Identification]
HWNumber           = "0261207143"
SWNumber           = "1037360857"
PartNumber         = "8D0907551M"
SWVersion          = "0002"
EngineId           = "2.7l V6/5VT"

Logged variables are:
#no.: name                , alias                           , addr  ,sz, bitm, S
, I,  A         ,   B, unit
#-------------------------------------------------------------------------------
-----------------------------
#001: dwkrz_0             , IgnitionRetardCyl1              , 380C2B, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#002: dwkrz_1             , IgnitionRetardCyl5              , 380C2C, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#003: dwkrz_2             , IgnitionRetardCyl3              , 380C2D, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#004: dwkrz_3             , IgnitionRetardCyl2              , 380C2E, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#005: dwkrz_4             , IgnitionRetardCyl6              , 380C2F, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#006: dwkrz_5             , IgnitionRetardCyl4              , 380C30, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#007: fr2_w               , LambdaControlBank2              , 382E1C, 2, 0000, 0
, 0, 3.05176e-005,   0, '-'
#008: fr_w                , LambdaControl                   , 382E3A, 2, 0000, 0
, 0, 3.05176e-005,   0, '-'
#009: frm2_w              , LambdaControlAvgBank2           , 382E2A, 2, 0000, 0
, 0, 3.05176e-005,   0, '-'
#010: frm_w               , LambdaControlAvg                , 382E34, 2, 0000, 0
, 0, 3.05176e-005,   0, '-'
#011: gangi               , SelectedGear                    , 380AF8, 1, 0000, 0
, 0,           1,   0, 'gear'
#012: ldtvm               , WastegateDutyCycle              , 380C76, 1, 0000, 0
, 0,    0.390625,   0, '%'
#013: mshfm_w             , MassAirFlow                     , 00F97C, 2, 0000, 0
, 0,   0.0277778,   0, 'g/s'
#014: nmot_w              , EngineSpeed                     , 00F87A, 2, 0000, 0
, 0,        0.25,   0, 'rpm'
#015: plsol_w             , BoostPressureDesired            , 382284, 2, 0000, 0
, 0,   0.0390625,   0, 'mbar'
#016: pvdkds_w            , BoostPressureActual             , 382216, 2, 0000, 0
, 0,   0.0390625,   0, 'mbar'
#017: tabgm               , EGTModelBeforeCat               , 380A81, 1, 0000, 0
, 0,           5,  50, '░C'
#018: tabgm2              , EGTModelBeforeCatBank2          , 380A82, 1, 0000, 0
, 0,           5,  50, '░C'
#019: tans                , IntakeAirTemperature            , 380BBF, 1, 0000, 0
, 0,        0.75,  48, '░C'
#020: tats2_w             , EGTSensorBank2                  , 3824EE, 2, 0000, 0
, 0,   0.0195312,  50, '░C'
#021: tats_w              , EGTSensor                       , 3824F0, 2, 0000, 0
, 0,   0.0195312,  50, '░C'
#022: ti_b1               , FuelInjectorOnTime              , 38238E, 2, 0000, 0
, 0,  0.00266667,   0, 'ms'
#023: zwout               , IgnitionTimingAngleOverall      , 00F9FC, 1, 0000, 1
, 0,        0.75,   0, '░KW'
Logged data size is 34 bytes.
Start connecting to ECU at 05.03.2013 19:47:04.823
try connect slow(11)
try connect slow(11)
Could not connect
try connect slow(11)
19:47:10.339-685,5 os_setspeed(speed=10400)
19:47:10.343-260,4 os_receiver_off()
19:47:10.645-914,5 os_setbreak()
19:47:10.846-457,4 os_clrbreak()
19:47:11.047-789,0 os_setbreak()
19:47:11.249-928,6 os_setbreak()
19:47:11.451-221,1 os_setbreak()
19:47:11.652-221,4 os_clrbreak()
19:47:11.854-187,9 os_setbreak()
19:47:12.055-344,1 os_setbreak()
19:47:12.256-471,5 os_setbreak()
19:47:12.459-360,7 os_clrbreak()
19:47:12.460-347,4 os_receiver_on()
19:47:12.963-062,5 os_rcvbyte(timeout=500) -> TIMEOUT
try connect slow(11)
19:47:12.964-320,5 os_setspeed(speed=10400)
19:47:12.966-048,6 os_receiver_off()
19:47:13.266-327,5 os_setbreak()
19:47:13.468-035,0 os_clrbreak()
19:47:13.669-590,0 os_setbreak()
19:47:13.870-260,9 os_setbreak()
19:47:14.070-736,3 os_setbreak()
19:47:14.271-852,4 os_clrbreak()
19:47:14.472-500,9 os_setbreak()
19:47:14.673-677,6 os_setbreak()
19:47:14.875-164,2 os_setbreak()
19:47:15.075-872,2 os_clrbreak()
19:47:15.077-718,1 os_receiver_on()
19:47:15.580-403,9 os_rcvbyte(timeout=500) -> TIMEOUT
Could not connect
=> Could not connect to ECU, exiting ...
=> Logging failed
exiting (cause=0x4)...

C:\Users\Chuck\Desktop\ME7Logger_DIST_02042012_v1.17>
Logged
phila_dot
Hero Member
*****

Karma: +171/-11
Offline Offline

Posts: 1709


« Reply #235 on: March 05, 2013, 09:53:39 PM »

If you are who I think you are, shouldn't you have access to some proprietary logging software?

And aren't you part of that anti-Nefmoto tribe?

All that aside, there is nothing obvious there.

Does VCDS and/or ECUx function as expected?

The only time that I've seen that is when the file on the ECU is bad and connection isn't possible.
Logged
nyet
Administrator
Hero Member
*****

Karma: +604/-166
Offline Offline

Posts: 12233


WWW
« Reply #236 on: March 05, 2013, 10:33:43 PM »

i've seen that on occasion.

rebooting the ECU seems to help sometimes, or unplugging the usb port on my cable and plugging it back in
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.
temanuele
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 7


« Reply #237 on: March 06, 2013, 12:20:35 AM »

If you are who I think you are, shouldn't you have access to some proprietary logging software?

And aren't you part of that anti-Nefmoto tribe?

All that aside, there is nothing obvious there.

Does VCDS and/or ECUx function as expected?

The only time that I've seen that is when the file on the ECU is bad and connection isn't possible.

Anti-Nefmoto tribe? I've never said a bad thing about this forum or its users so I'm not sure where this is coming from.
Logged
temanuele
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 7


« Reply #238 on: March 06, 2013, 12:25:08 AM »

Thanks for the answers.
Logged
CoupedUp
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 59


« Reply #239 on: March 13, 2013, 12:46:24 PM »

No, there exists currently no linux variant of the logger. A port is on the todo list,
but this will not be done in short time, sorry.

Any word on this? Would be sweet to get a raspberry pi in a car to start logging based off of a switch and not need a computer in the car.
Logged
Pages: 1 ... 14 15 [16] 17 18 ... 34
  Print  
 
Jump to:  

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