|
SB_GLI
|
 |
« Reply #375 on: August 04, 2014, 02:02:07 PM »
|
|
|
I finally dug into the issue that I was having logging my Jetta. I could only get like 5 or samples a second and had to cut down the number of variables that I logged.
Since I am using VisualME7Logger, ME7Logger needs to write the log to both the stdout and the file. Writing to both was causing the issues with my car / pc combo. This was only an issue for my jetta, as I have logged other vehicles with my PC at 20 frames per second with no issues. If I write just to the log, or just to the stdout, it logs with no issue. Otherwise it would just take a few samples and then puke out.
Testing with ME7Logger from the command line, it still has the same issue when trying to print to the stdout and file at the same time, so it's not VisualME7Logger related.
I added an option to disable real-time display in VisualME7Logger and now I can log 50+ variables at 20+ frames per second, I just can't see stuff as I am driving unless I go back to around 5 samples a second. I will release this option in the near future or as needed if someone else notices this problem.
|
|
|
|
|
Logged
|
|
|
|
|
|
|
aef
|
|
« Reply #377 on: August 05, 2014, 01:32:20 AM »
|
|
|
you can try it with car off and ignition on. dash should went dark if you pull fuse 5 i think. then you have to play with the settings: Slow-0x00 12 HM0 56000 if you are able to connect the me7logger you can try it with dash. if this doesnt work put a killswitch into k-line to dash, maybe this will work. you are allowed to start the car, kill the kline (immo related), turn on logger  |
|
|
|
|
Logged
|
|
|
|
gitman
Newbie
Karma: +0/-0
 Offline
Posts: 12
|
|
« Reply #378 on: September 12, 2014, 10:02:03 AM »
|
|
|
wanted to report an issue - when I mouse over points plotted out on "Y Axis2", it does not pop up a tooltip with the X,Y, and cell values that you can see if you mouse over a point plotted out on the first "Y Axis"
|
|
|
|
|
Logged
|
|
|
|
metronet
Full Member
Karma: +5/-0
Offline
Posts: 73
|
|
« Reply #379 on: September 28, 2014, 10:13:34 AM »
|
|
|
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.
Another vote for a binary compiled for Arm processors like the RaspberryPi. It would be really cool!  |
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #380 on: November 16, 2014, 03:18:49 PM »
|
|
|
Another vote for a binary compiled for Arm processors like the RaspberryPi. It would be really cool! BUMP! Hey setzi, if you are too busy, just release the source  |
|
|
|
|
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
|
|
|
fknbrkn
Hero Member
Karma: +185/-23
 Online
Posts: 1454
mk4 1.8T AUM
|
|
« Reply #381 on: December 07, 2014, 10:16:04 AM »
|
|
|
little diy. howto generate vag-com measurement groups vs variables table C:/vw/me7logger/bin/me7info.exe C:/vw/my_ecu.bin -g > C:/vw/my_ecu.txtlegend: path to me7infopath to your bin filepath to output fileMeasgroup table for file 06A906032DR_0002.bin
Map measgroup -> result_type(variable name) for all the sub-results
measgroup 000: 0050(tmotlin ), 0002(rl ), 000E(nmotll ), 0051(wub ), 0007(wdkba ),
0087(dmllri_w ), 0013(dmvad_w ), 001C(fr_w ), 001F(rkat_w/rkaz_w ), 0021(fra_w )
measgroup 001: 0001(nmot ), 0050(tmotlin ), 001C(fr_w ), 000D( )
measgroup 002: 0001(nmot ), 0002(rl ), 004A(ti_b1 ), 000A(mshfm_w )
measgroup 003: 0001(nmot ), 000A(mshfm_w ), 0007(wdkba ), 0009(zwout )
... |
|
|
|
|
Logged
|
|
|
|
fknbrkn
Hero Member
Karma: +185/-23
Online
Posts: 1454
mk4 1.8T AUM
|
|
« Reply #382 on: December 07, 2014, 10:19:25 AM »
|
|
|
here is mine
wideband 1.8t
|
|
|
|
|
Logged
|
|
|
|
melu
Newbie
Karma: +0/-0
Offline
Posts: 6
|
|
« Reply #383 on: December 11, 2014, 02:39:38 PM »
|
|
|
Is there a way to use ME7Info with a ME7.9.10?
If I try to use it, I will get the error, that the flash length is not correct, as ME7.9.10 uses a 832kB flash.
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #384 on: December 11, 2014, 02:56:06 PM »
|
|
|
Unfortunately, no.
|
|
|
|
|
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
|
|
|
melu
Newbie
Karma: +0/-0
Offline
Posts: 6
|
|
« Reply #385 on: December 12, 2014, 02:55:19 PM »
|
|
|
It's a pity  I tried also with ME7.5.20, didn't work neither Still struggling with disassemble ST10F275 |
|
|
|
|
Logged
|
|
|
|
juutasqsa
Newbie
Karma: +0/-0
Offline
Posts: 3
|
|
« Reply #386 on: January 22, 2015, 09:47:31 AM »
|
|
|
Hi,
I installed ME7Logger and GUI into my win7 64bit laptop and I can't get ME7Logger working.
Below error came:
can't load library ftd2xx.dll
Initialization failed, exiting ...
exiting (cause=0x1)...
Is it cause I have 64bit OS and can someone help me how to solve this problem?
Thanks in advance.
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #387 on: January 22, 2015, 10:27:40 AM »
|
|
|
I installed ME7Logger and GUI into my win7 64bit laptop and I can't get ME7Logger working.
Below error came:
can't load library ftd2xx.dll
Which FTDI driver did you install? |
|
|
|
|
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
|
|
|
juutasqsa
Newbie
Karma: +0/-0
Offline
Posts: 3
|
|
« Reply #388 on: January 22, 2015, 10:29:00 AM »
|
|
|
Hi,
I installed ME7Logger and GUI into my win7 64bit laptop and I can't get ME7Logger working.
Below error came:
can't load library ftd2xx.dll
Initialization failed, exiting ...
exiting (cause=0x1)...
Is it cause I have 64bit OS and can someone help me how to solve this problem?
Got help for this problem, I added that .dll into bin folder and I took away 'Boot in intelligent mode' from VCDS. Thanks Okkim, again.
|
|
|
|
|
Logged
|
|
|
|
A4Rich
Full Member
Karma: +10/-0
Offline
Posts: 116
|
|
« Reply #389 on: January 22, 2015, 03:28:39 PM »
|
|
|
I had the same problem on W7 64-bit with genuine VCDS K+can cable but did get it working. I didn't have the VCP driver from ross-tech installed fully. Check this thread out, click and use the FTDIchip.com instructions for more guidance (note, I never couldn't get the FTDIchip driver to work). |
|
|
|
|
Logged
|
|
|
|
|
