Wolf 3D New software is terrible.
#1
New software is terrible.
So I finally got to fire up the laptop w/ the new software on it. I'm very disappointed in the datalogging to say the least.
1. Graphs do not display in real time, ever.
2. Recording seems to work great, however trying to load a log crashes the software 50% of the time. The other 50% of the time it crashes when you scroll the log
3. Its great they have no input displays on the axis. You can however, choose AFR. Unfortunately, even tho my oxy volts was reading properly and over the full range, AFR likes to read 20 all the time. And not move at all.
It's nice to see they're working on it and trying to get datalogging in, but I don't see how they can be charging people for this. It doesn't seem like there was ANY quality control work done on this at all. Maybe they should have spent less time on the 3-D graphs and more time on making software that does what its supposed to.
I do not feel safe using this software. I will be tuning with the old software until they fix this.
1. Graphs do not display in real time, ever.
2. Recording seems to work great, however trying to load a log crashes the software 50% of the time. The other 50% of the time it crashes when you scroll the log
3. Its great they have no input displays on the axis. You can however, choose AFR. Unfortunately, even tho my oxy volts was reading properly and over the full range, AFR likes to read 20 all the time. And not move at all.
It's nice to see they're working on it and trying to get datalogging in, but I don't see how they can be charging people for this. It doesn't seem like there was ANY quality control work done on this at all. Maybe they should have spent less time on the 3-D graphs and more time on making software that does what its supposed to.
I do not feel safe using this software. I will be tuning with the old software until they fix this.
#2
I agree. Mine worked rubbish. It looks very fancy but really the old software with some basic datalogging would be 100x better. Here are some problems I experienced.
1. The screen doesn't fit in anything smaller than a 19inch monitor
2. Theres constant debugging error messages coming up when swapping to datalog mode.
3. The gauges run way too slow when the ecu is connected and car running. It sometimes pauses for a bit then starts again, or jumps to random values like 300000rpm. It also does this while datalogging everytime i gave my car full throttle in 2nd gear. Which then make the values in the table out of range and unloadable.
4. Playing back the datalogging the gauges tend to occasionally display something until the graphs stop then it plays back on the gauges. You can even grab the tacho and move the needle with your mouse.
5. And the most important thing with the dataloggin is missing. You can't go step by step through each logged point it can only play and pause. Also on the graphs it doesn't have an origin where the gauges are reading from.
I could go on and on. I mean did they even test the software? I thought it was sent out to dealers to find all the bugs before they release it. You can't even use it at all to tune in regards to datalogging.
Thats my bitching over.
OK now we know wolf will never make good software how do we go about getting the techedge datalogger to work with rpm, load etc?
1. The screen doesn't fit in anything smaller than a 19inch monitor
2. Theres constant debugging error messages coming up when swapping to datalog mode.
3. The gauges run way too slow when the ecu is connected and car running. It sometimes pauses for a bit then starts again, or jumps to random values like 300000rpm. It also does this while datalogging everytime i gave my car full throttle in 2nd gear. Which then make the values in the table out of range and unloadable.
4. Playing back the datalogging the gauges tend to occasionally display something until the graphs stop then it plays back on the gauges. You can even grab the tacho and move the needle with your mouse.
5. And the most important thing with the dataloggin is missing. You can't go step by step through each logged point it can only play and pause. Also on the graphs it doesn't have an origin where the gauges are reading from.
I could go on and on. I mean did they even test the software? I thought it was sent out to dealers to find all the bugs before they release it. You can't even use it at all to tune in regards to datalogging.
Thats my bitching over.
OK now we know wolf will never make good software how do we go about getting the techedge datalogger to work with rpm, load etc?
#3
You mean no afr datalog either on the wire in? I know the datalog is quite useless with the plug n play version, but also withthe wire in using the LSM11? now that dissappoints me. well I was using Mike's logger and I plan on keeping up my habit!
True, the AAAAAHHHHHH about this software may really be ill founded.
Did you notice that you cant tranfer csv files?you cant transfer one table. if anone knows how to get this software in admin mode kindly post here.
I still use the old software..... for sure i will on my new rebuild!!!
my 0.2c
G
True, the AAAAAHHHHHH about this software may really be ill founded.
Did you notice that you cant tranfer csv files?you cant transfer one table. if anone knows how to get this software in admin mode kindly post here.
I still use the old software..... for sure i will on my new rebuild!!!
my 0.2c
G
#4
I think nyt was saying the AFR voltage display works but the AFR display didn't.
Even if it did work the software is that bad I wouldn't trust it at all.
I looked at some of my excel files with all the data. On some points the ignition is recording
-ve values. also during some acceleration the rpm actually went lower from one point to the next, which is impossible unless i hit the brakes while the car was still on boost.
Even if it did work the software is that bad I wouldn't trust it at all.
I looked at some of my excel files with all the data. On some points the ignition is recording
-ve values. also during some acceleration the rpm actually went lower from one point to the next, which is impossible unless i hit the brakes while the car was still on boost.
#5
I just tried the software on my work pc. It seems a lot smoother than my laptop but its still not really smooth. Plus this machine is a 3.4ghz p4 with 2gb ram. I doubt any laptops are going to be any faster.
So it could be that the software isn't half as bad as we thought just it was programmed and tested on an ultra fast machine which is pretty useless because most people will be using old laptops etc.
So it could be that the software isn't half as bad as we thought just it was programmed and tested on an ultra fast machine which is pretty useless because most people will be using old laptops etc.
Trending Topics
#8
I was running it on an athlon 1.3 and it seemed fine. As for techedge logging, if you want to see boost you can get an external map sensor and hook it up. Currently I'm just using the techedge to log RPM/AFR.
IMO the following changes really need to be made to the wolf logging software:
1. Fix the crashing
2. Fix the logging playback
3. Draw graphs in real time while the car is running. It's not cpu intensive to do 2 math functions and plot a point.
4. Always save the ecu streaming data in memory, allow that to be saved. The record feature that stops everything else is pretty archaic as is not having a display while logging.
5. I want to be able to pick a point in the datalog, and go to that fuel or ignition cell that is being used at the time.
This is all pretty trivial to implement. Not asking for miracles here, just something that works.
If someone could pass this on to someone at wolf that works with the software, that would be great.
IMO the following changes really need to be made to the wolf logging software:
1. Fix the crashing
2. Fix the logging playback
3. Draw graphs in real time while the car is running. It's not cpu intensive to do 2 math functions and plot a point.
4. Always save the ecu streaming data in memory, allow that to be saved. The record feature that stops everything else is pretty archaic as is not having a display while logging.
5. I want to be able to pick a point in the datalog, and go to that fuel or ignition cell that is being used at the time.
This is all pretty trivial to implement. Not asking for miracles here, just something that works.
If someone could pass this on to someone at wolf that works with the software, that would be great.
#10
Rotary Enthusiast
Join Date: Feb 2004
Location: North Queensland Australia
Posts: 778
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by raddavey
I think nyt was saying the AFR voltage display works but the AFR display didn't.
Even if it did work the software is that bad I wouldn't trust it at all.
I looked at some of my excel files with all the data. On some points the ignition is recording
-ve values. also during some acceleration the rpm actually went lower from one point to the next, which is impossible unless i hit the brakes while the car was still on boost.
Even if it did work the software is that bad I wouldn't trust it at all.
I looked at some of my excel files with all the data. On some points the ignition is recording
-ve values. also during some acceleration the rpm actually went lower from one point to the next, which is impossible unless i hit the brakes while the car was still on boost.
This is the point I was making about the data logging. It doesn't log AFR only voltage and the software can't keep up with the ECU if you flat rev it. Some times I see this in my software when the ECU skips sending data at a high processor load within the ECU. I had a look at the data logs it made and I saw problems too. My program is faster as it does less and can wait around for the ECU to talk. I have not used the NEW version 1.62 software but the last version of 1.5 I debugged still had some issues but it was getting better. The data logging was flakey but all the data changing part of the software worked without crashing.
I would guess that most of the bugs should have been worked out by now but anyone using the version 1.62 software could you post your experiences here please.
Cheers
Michael Smith
#12
Rotary Enthusiast
Join Date: Feb 2004
Location: North Queensland Australia
Posts: 778
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by raddavey
The top two from nyt and myself were both using v1.62.
Maybe I will make a stand alone Log playback program with speed control.
I must be MAD.......
Michael Smith
#14
Passenger
Posts: n/a
here is a letter i typed to steve at wolf:
hello Steve,
I just received the Wolf newsletter update and I noticed a screen in the wolf software that I have never seen before, copy and paste this link to see the screen I am talking about:
http://www.wolfems.com/images/v500fe...ms-trimmed.jpg
is there a newer version than the last one you sent me (ver 4.72 rev 1.62) ? can you send me the newest one?
also I also would think you might be interested in the negative feedback many people are talking about regarding the new software, it lists the issues one by one and it might help you make some useful changes....
https://www.rx7club.com/showthread.php?t=558264
Best regards,
Jeremy
Here is his reply:
Hi Jeremy,
Thanks for your email. The Trim Potts that you
see in the screen shot are only available to on the new
Wolf V500 ECU.
Thanks for emailing me the link to the RX7 group. We have a
new Software update that we should be releasing next week.
Anyone who has bought the PC Software from us will
receive an email with this update, and they will receive
future updates as they become available.
Regards,
Steve..
lets all keep this positive and hope that only great updates will come of this software.....
hello Steve,
I just received the Wolf newsletter update and I noticed a screen in the wolf software that I have never seen before, copy and paste this link to see the screen I am talking about:
http://www.wolfems.com/images/v500fe...ms-trimmed.jpg
is there a newer version than the last one you sent me (ver 4.72 rev 1.62) ? can you send me the newest one?
also I also would think you might be interested in the negative feedback many people are talking about regarding the new software, it lists the issues one by one and it might help you make some useful changes....
https://www.rx7club.com/showthread.php?t=558264
Best regards,
Jeremy
Here is his reply:
Hi Jeremy,
Thanks for your email. The Trim Potts that you
see in the screen shot are only available to on the new
Wolf V500 ECU.
Thanks for emailing me the link to the RX7 group. We have a
new Software update that we should be releasing next week.
Anyone who has bought the PC Software from us will
receive an email with this update, and they will receive
future updates as they become available.
Regards,
Steve..
lets all keep this positive and hope that only great updates will come of this software.....
#15
Well i tried it on p4 1.7ghz lappy it seemed better at first (still not that smooth). The gauges were moving pretty much in real time and just free revving in neutral a little it logged ok. But as soon as i went for a drive (not even driving hard) it just lost sync and jumped around from 0rpm to 30000rpm+. Which of course puts the data out of the allowable range and you can't open the log file up after.
Its possible it needs the latest firmware to work correctly.
Its possible it needs the latest firmware to work correctly.
#17
What kind of connection are you using between ECU and computer? serial port or USB-serial adapter?
Here I mention some tests I did:
https://www.rx7club.com/wolf-3d-125/serial-port-vs-usb-adapter-562532/
Here I mention some tests I did:
https://www.rx7club.com/wolf-3d-125/serial-port-vs-usb-adapter-562532/
#24
Rotary Enthusiast
Sorry if this is a newbiew question, but does the laptop software simply record data/ show gauges, or is it used for tuning as well? Well all do you need to do to "install" the laptop (simply run a cable from car computer to laptop? How mush is the software & where can I get it? Thanks