Pages: 1 ... 16 17 [18]
Author Topic: VisualME7Logger CodePlex Project  (Read 239163 times)
syntaxerror
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 11


« Reply #255 on: May 25, 2021, 07:00:28 PM »

Has anyone run into this issue?
Logged
syntaxerror
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 11


« Reply #256 on: May 25, 2021, 07:06:17 PM »

Meh ignore that, ill just debug and report back what the resolution was.
Logged
syntaxerror
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 11


« Reply #257 on: May 25, 2021, 08:34:32 PM »

That was embarrassing... incorrectly installed it. At the very least did a pull request to provide a warning if you didn't follow directions.
Logged
martin2day
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 9


« Reply #258 on: May 28, 2021, 10:35:23 AM »

Hello,

i have test to log my ME7.8 in my 996tt... :-)
But it fail... with my original bin File I can create an ECU File, but he does not find any Identifaktions....
With empty EngineID I get a error... but if I write some EnigineID to it I get the Error: Engine ID Setup '996' but is ''

Is it possible to use this great tool for logging my 996tt?

Have a nice Day
Martin
Logged
Herefortuning
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 2


« Reply #259 on: May 30, 2021, 02:43:23 AM »

Hey guys. I have passat b5 1.8t awt, FTDI cable, Windows 10 64bit. With connection everything is ok, but after starting and ~10sec it gives an error "input string was not a correct format". I have tried to start app before starting the engine. I checked my region setting in windows ( I have dot there). But still I receiving this error. Help please
Logged
Herefortuning
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 2


« Reply #260 on: May 30, 2021, 05:20:25 AM »

A bit update on my problem. Some people here wrote that try to connect via NefMoto and disconnect. After that start me7logger and it will work until you turn of the ignition. So you can have as many sessions as you want. And IT WORKED Smiley)
Logged
M.Mischler
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 32


« Reply #261 on: January 25, 2023, 01:42:53 PM »

Hey guys. I have passat b5 1.8t awt, FTDI cable, Windows 10 64bit. With connection everything is ok, but after starting and ~10sec it gives an error "input string was not a correct format". I have tried to start app before starting the engine. I checked my region setting in windows ( I have dot there). But still I receiving this error. Help please

A FormatException occurred on my system as well.

Setup:
  • - Windows 10 Home 21H2 64-Bit
  • - Cable Rosstech HEX-USB+CAN
  • - S4 B5
  • - ECU 8D0 907 551D (stock, no tuning)
  • - Logged variables:
lamfa_w         ;TargetAFRDriverRequest                ; Lambdasoll Fahrerwunsch (word)
wkr_0            ;IgnRetardKnockControlCyl1            ; zylinderindividuelle Zündwinkelspätverstellung KR
wkr_1            ;IgnRetardKnockControlCyl5            ; zylinderindividuelle Zündwinkelspätverstellung KR
wkr_2            ;IgnRetardKnockControlCyl3            ; zylinderindividuelle Zündwinkelspätverstellung KR
wkr_3            ;IgnRetardKnockControlCyl2            ; zylinderindividuelle Zündwinkelspätverstellung KR
wkr_4            ;IgnRetardKnockControlCyl6            ; zylinderindividuelle Zündwinkelspätverstellung KR
wkr_5            ;IgnRetardKnockControlCyl4            ; zylinderindividuelle Zündwinkelspätverstellung KR
wped             ;AccelPedalPosition                       ; Normierter Fahrpedalwinkel

I setup VisualME7Logger according to the instructions provided in the video.

As described in the thread http://nefariousmotorsports.com/forum/index.php?topic=17419, I can

  • - only connect VisualME7Logger after having connected with NEFMoto VW Audi ME7 Flasher Logger 1.9.4.3.
  • - as soon as I start the engine a FormatException occurs and the engine stops immediately.
  • - as long as the engine is running I cannot connect to the ECU with NEFMoto VW Audi ME7 Flasher Logger 1.9.4.3.
  • - as long as the engine is running I cannot connect to the ECU with VisualME7Logger 2018.07.02.28.

Can anyone tell me what I need to do to solve the issue with the FormatException? Is it the solution to change something in the region settings of windows os?
« Last Edit: January 25, 2023, 01:48:25 PM by M.Mischler » Logged
BlackT
Hero Member
*****

Karma: +79/-39
Offline Offline

Posts: 1415



« Reply #262 on: January 25, 2023, 08:04:55 PM »

Try to connect without cluster. I have found that many 4B and 8D clusters make problems
Logged
M.Mischler
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 32


« Reply #263 on: January 26, 2023, 04:53:37 PM »

Try to connect without cluster. I have found that many 4B and 8D clusters make problems

Thanks for your tip. This means driving without speed indicator, tachometer and warning lights....

Did you disconnect the complete instrument cluster? So all three connectors (blue connector, gray connector and green connector)?

...Ah, sorry. I just see that this has already been discussed: http://nefariousmotorsports.com/forum/index.php?topic=12466.msg103350#msg103350
« Last Edit: January 26, 2023, 05:56:37 PM by M.Mischler » Logged
Leonhard
Full Member
***

Karma: +27/-2
Offline Offline

Posts: 112


« Reply #264 on: January 27, 2023, 01:27:31 AM »

Try to connect without cluster. I have found that many 4B and 8D clusters make problems
Yes, same findings, with separated K-Line no more problems
on these cars I install second OBD-port with K-Line switch
Logged
Pages: 1 ... 16 17 [18]
  Print  
 
Jump to:  

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