i can not stand alone datalog my wideband with my mpvi pro. did i miss the memo or am i configuring wrong? i have my cfg that i want to use and it works fine with the laptop.
Printable View
i can not stand alone datalog my wideband with my mpvi pro. did i miss the memo or am i configuring wrong? i have my cfg that i want to use and it works fine with the laptop.
Are you using 2.22 or 2.23 (beta)? If I remember correctly, using the beta 2.23 release doesn't allow stand alone data logging at this point.
i am using beta. i am assuming it's possible with the production release. correct?
There was a beta release that didn't but it was fixed. I believe latest beta will work fine.
bill says not yet. thanks for looking guys.
Yeah I talked to our software designer about this about a week ago, he's currently working on the firmware update and he'll try to get this reenabled in the beta once the firmware is worked out.
Oh I see its only on newer units, right?
I'm on 2.23.248.
I can log now without the PC (I am SO happy this works now!), but cannot log the WB.
Am I understanding correctly that this is a known issue and will be addressed at some point in the future?
Yes, please Bill!
WOW I wish I had read this way before now, I don't have any hair left. One day I was able to do a stand alone and log the EIO inputs just fine and now nothing................
Any updates on this yet?
I need this................I hate going backwards
Thanks!
with your stand alone, you have to limit the parameters you are scanning. I cant recall how many are allowed in the MPVI. Then you have to write that configuration to the MPVI. The last couple updates ive gotten have been able to do stand alone if the configuration has been written to it.
Thanks!
What update are you using?
I just finished downloading the most recent update so I will try it today.
I still can't get it to work.............Phil whats your secret???????
According to Bill today
"Still working on it"
Thanks,
William Henn
HP Tuners LLC.
Well, it's not useless, you just need to have a laptop in the car connected to the MPVI logging data in order to use the wideband sensor. Not ideal at all, but not useless either.
I'm about to install a blower, and I'll need to log afr's which is even more critical with boost then NA, so my laptop will just have to go along for the ride.
aux's are still on the no list.
Just tested latest beta. Still disabled?
I always have the laptop in the car. I did not know it would log with out it. My start and stop buttons have never worked. I have to do it from the tool bar on the laptop. which blows sometimes.
same issue for me. waiting for fix so I can data log using just the MPVI PRO unit. who wants to put a lap top in the car to get logs when you have a tool like this that should work.
Can I go back to a previous version ( I am on the latest as of 6/13/11 - ver 2.23.207 beta which was created by HP Tuners on 3/22/2011) to get around this problem for now?
Any help is appreciated.
Is the logging issue fixed?
When I try to start a log after downloading the Config the Device ERR LED lights up an no logs are collected.
For I only trying to log the Short and Long tern fuel trim data.
Since my laptop only lasts around 30 Mins on the Battery logging with the VCM Pro module is a necessity if I am going to be able to collect some decent logs.
I don't suppose these is a pre beta firmware that needs testing?
The current beta has the firmware fix.
The software fix I'm working on now. It is one of my top priorities.
Hi Keith,
My ECU details are :-
Vehicle Type : Holden V8 Sedan.
ECU Type : E38
ECU OS ID : 12612381
MPVI pro Serial : 1168012220 Date: 04/29/11
Hardware: 121 Firmware: 110
Part Number: 6220
Logging to a Laptop works.
Problem Description.
Downloaded a config to the pro's memory produces no errors.
The config is only logging ecu pids for stft's, map, rpm, etc.
When I push the record the system goes to busy for a second or so then the ERR led comes on and stays on untill I either start logging via a laptop or scan for DTC's.
Still working on this Keith?
is there a fix yet. if you need a software engineer maybe i can help.
For those, like me, that paid for the Pro unit for the standalone logging capability and HAVE to use the beta for support of later ECMs and features, given the time frame that this has been useless, it is beginning to go beyond ridiculous! :banghead: :mad:
PLEASE, get this fixed ASAP!!! :pray:
yeah i noticed this recently also, i'm going to see if i can just use 2.22 to get by to write my config and hope it'll work for me
Still no fix? What is taking so long?
Hi,
I don't suppose any o your developers have bothered to test the latest drivers CDM driver suite from FDTI???
The reason I ask is that there numerous api fixes relating to IO errors, Bus handshaking and others.
I have attached the Release for the lateat api/driver release which lists them all.
Given the number of api bugs fixed since v 2.04.16 they would seem overdue for update.
This delay seems very abnormal. This may be more than a priority issue!!!
I'm using beta version 2.23.274 and I can log data with the standalone, but no inputs still. It's become even more critical as I need to log wideband afr as well as fuel pressure.
Is there a newer beta version?
I'm at one year and still counting.......
It's a little surprising to see new features being released while the standalone logging external inputs are still not working as advertised.
If you ignore it long enough...it will go away.