Sorry, but that is the expected outcome. The Volvo ME7 is not compatible with ME7L.
A custom protocol is used for logging which depends on the bootrom in ME7 found in
VAG cars (VW,Audi,Seat,Skoda).

-> Reading log config file C:\Users\Speed51133\Downloads\me7logger\logs\my 1st.c
fg .... done
-> Reading ecu characteristics file C:\Users\Speed51133\Downloads\me7logger\ecus
\example.ecu .... done
Used Ecu definition is:
[Communication]
Connect      = SLOW-0x01
Communicate  = HM0
LogSpeed     = 56000

[Identification]
HWNumber           = "0261207931"
SWNumber           = "1037366920"
PartNumber         = "4B0906018DA"
SWVersion          = "0006"
EngineId           = "1.8L R4/5VT"

Logged variables are:
#no.: name                , alias                           , addr  ,sz, bitm, S
, I,  A         ,   B, unit
#069: tmot                , CoolantTemperature              , 380A63, 1, 0000, 0
, 0,        0.75,  48, '░C'
#070: tmotlin             , CoolantTemperature              , 3848B5, 1, 0000, 0
, 0,        0.75,  48, '░C'
#071: tmotsoll            , CoolantTemperatureRequested     , 384969, 1, 0000, 0
, 0,        0.75,  48, '░C'
#072: tmst                , EngineStartTemperature          , 3848BB, 1, 0000, 0
, 0,        0.75,  48, '░C'
#073: tnst_w              , TimeSinceStart                  , 382C14, 2, 0000, 0
, 0,        0.01,   0, 's'
Logged data size is 124 bytes.
Start connecting to ECU at 26.03.2012 22:36:07.154
try connect slow(01)
received wrong inverted address 0x0F (expected 0xFE)
try connect slow(01)
received wrong inverted address 0x0F (expected 0xFE)
Could not connect
try connect slow(01)
02:36:12.473-756,1 os_setspeed(speed=10400)
02:36:12.788-569,9 os_receiver_off()
02:36:12.789-426,2 os_setbreak()
02:36:12.993-594,5 os_clrbreak()
02:36:13.196-619,7 os_setbreak()
02:36:13.399-628,3 os_setbreak()
02:36:13.603-799,1 os_setbreak()
02:36:13.806-637,0 os_setbreak()
02:36:14.009-659,7 os_setbreak()
02:36:14.212-651,5 os_setbreak()
02:36:14.415-705,6 os_setbreak()
02:36:14.618-663,5 os_clrbreak()
02:36:14.621-645,5 os_receiver_on()
02:36:14.889-692,2 os_rcvbyte(timeout=500) -> 55
02:36:14.900-123,1 os_rcvbyte(timeout=100) -> 01
02:36:14.909-663,7 os_rcvbyte(timeout=100) -> 8A
02:36:14.935-488,9 os_sendbyte(data=75)
02:36:14.969-662,8 os_rcvbyte(timeout=100) -> 0F
received wrong inverted address 0x0F (expected 0xFE)
try connect slow(01)
02:36:14.975-568,4 os_setspeed(speed=10400)
02:36:15.291-652,3 os_receiver_off()
02:36:15.292-527,2 os_setbreak()
02:36:15.496-680,1 os_clrbreak()
02:36:15.700-667,4 os_setbreak()
02:36:15.903-716,4 os_setbreak()
02:36:16.106-733,3 os_setbreak()
02:36:16.309-709,8 os_setbreak()
02:36:16.512-710,6 os_setbreak()
02:36:16.715-735,8 os_setbreak()
02:36:16.918-766,2 os_setbreak()
02:36:17.121-733,7 os_clrbreak()
02:36:17.124-729,8 os_receiver_on()
02:36:17.393-778,4 os_rcvbyte(timeout=500) -> 55
02:36:17.403-823,2 os_rcvbyte(timeout=100) -> 01
02:36:17.413-825,0 os_rcvbyte(timeout=100) -> 8A
02:36:17.440-131,2 os_sendbyte(data=75)
02:36:17.473-754,2 os_rcvbyte(timeout=100) -> 0F
received wrong inverted address 0x0F (expected 0xFE)
Could not connect
=> Could not connect to ECU, exiting ...
=> Logging failed
exiting (cause=0x4)...

C:\Users\Speed51133\Downloads\me7logger>


the above is all i can get to happen. i can log fine with vcds and EVEN WITH ECUX! I would like to try this out, but i have seen others with the same errors, and no solutions.

using a real vcds cable set it to NOT intelligent. no com port works, have to use that other selection.

any help?

I did not even know there was a README. I found it buried in the DOC folder.

So i need my ecu's binary. It says to "get it" or find someone that has it.

So how do I get it?

Finally I was able to put together a "cleanup" build of ME7Logger
with all the small changes that have piled up over the time.
Find an updated version 1.17 of ME7Logger and ME7Info in the first post.

Roughly the changes in ME7Logger:
- Reworked general timing calculations, timestamps, sync to full second
- Fixed local time in absolute timestamps (option -a)
- Supress logfile writing when output goes to stdout (option -R)
  useful if output is piped to external evaluation tool/filter
- Added option -m: Timestamp format milliseconds
- Added option -h: supress printing header information in logfiles
- Added option -b: set logging baudrate for communication,
                   overrides baudrate from ecu file
- connection method "double slowinit" added (helps with "instrument cluster" problem)
  To use double slowinit set in the [Communication] section of the .ecu file:
    Connect      = SLOW-0x00
    DoubleDelay  = 12           ; Possible values 1 .. 100 (delay in 100ms)
  This allows to connect only while engine not yet started.

And the changes in ME7Info:
- Reverted back to zwbasar_0 .. zwbasar_3
  (Array size NOT dependent on number of cylinders)
- Some variables added:
 + zwoutar_0 .. zwoutar_3
 + zwsol
 + redist / evz_austot
 + lamfaws_w / lamfawkr_w / lamfaw_w / lamfwl_w / lamrlmn_w
 + perffilt_w / perfmax_w   => This is CPU-Load
    It helps in finding out the max. logging capabilities of your ECU.
    Around 90% CPU-Load might be a limit for the ECU.

I think it would be useful if you put perffilt_w (CPU load) into your logging profiles and
make some tests to see how you ECU performs underr different logging conditions (sample rate/#variables).
My ECU is 32MHz, so I have plenty of headroom for wildest logging. But most ECUs run at 24MHz and some
even have only 20MHz, so these could probably suffer from excessive logging.

Nice!  TY setzi!

Sorry, that was a build error, so it worked only under cygwin but not in DOS shell.
I fixed this and updated the .zip in the first post, please download this again,
it contains an updated ME7Info.exe

first test of the logger on a ME7.8:


any idea?
(more details provided in PM)

request fupsrl_w