***Please Note*** 16/04/2009
Just in case you do not scroll down past this post and read the rest of the thread, then make sure after installing version 2.0 below, you then download the upgrade to version 2.02, using the files in this attachment http://www.myrollingroad.com/attachm...6&d=1239899582
************
At last got time to work on Version 2.0 of MutMonitor
I have it working again with Tactrix OpenPort 2.0 cable this end, but need it confirmed by others with this cable before I shout too loud
Please remember this software is FREE and in Beta/Test permanently. So expect bugs.
Also still could do with input on the calculations.
Please find attached and please send any bugs in on this thread.
P.S Battery is reading low on screenshot as using bench ECU and battery very LOW.
my cars in pieces sean gettin some major changes, will test it FIRST thing its back on the road, which will be like 1-2 weeks, but thats awsome you got mutv.2!
__________________
"...and 100% reason to remember the name"
my cars in pieces sean gettin some major changes, will test it FIRST thing its back on the road, which will be like 1-2 weeks, but thats awsome you got mutv.2!
Not a problem Greddy, be good to see if it goes in a couple of weeks
Car: Evo 260, do-luck wider arch kit, K-sport coilvers, whiteline bushes/arbs/droplinks, ECUTek, + more
Check out:
Title:
Member
Status:Offline
Join Date: Feb 2009
Location: Bristol
Posts: 19
Thanks: 0
Thanked 1 Time in 1 Post
Nice work Sean, glad the cable helped has there been a new firmware update for it to allow the through put or did you manage to sort some other communication out?
The cable is still on the same Firmware as when you sent it.
Main problem seemed to be the Init String I was using and found a bit of time while home over the 4 days of easter to sit down and examine it a bit more
Lets hope it works with other OP2.0 cables as well, if not then you have some custom software for your own cable
Do you need to short pins 1 & 4 to kick in the diagnostic mode? I've not done that so was getting the following:
Opening Com Port 2
Started 18:52:03 13/04/2009
Sending 5 Baud Init
61 72 66 33 20 32 D A
61 72 65 20 37 D A
Changing to 15625 Baud
Connected! 18:52:03 13/04/2009
Starting to Monitor
Invalid Reply or Timeout
Disconnected
Stopped 18:52:14 13/04/2009
If that's not the reason let me know if you want me to try anything. This was on Vista btw, didn't get chance to try your earlier version before I updated the firmware so it might even be related to that (it was run in admin mode).
Do you need to short pins 1 & 4 to kick in the diagnostic mode? I've not done that so was getting the following:
Hi Paul
Damm good question, I have packed my Bench ECU away for this weekend as away working early tomorow morning.
I tested it on the EVO 6 ECU and EVO 9 ECU and must admit I did short pins 1-4 on the 6 ECU. Did not even think of trying it without, just in case the OP2.0 does actually have this ability built in.
Ummm got me thinking now, but I do not think I will have time tonight to drag it all out and check.
When the OP2.0 is plugged in, do the dash lights start flashing if not then this could be the reason.
lol, yep just been out and tried it as well with them shorted and it's logging fine, but the AYC and ABS lights are still flashing with the engine running :/ That's a shame else I would have kept it shorted.
Not sure if you saw my earlier edit, this is running on Vista as well
Thanks for looking at the init stuff again and the software, will have a play now
Cheers,
Paul
The Following User Says Thank You to Paul R For This Useful Post:
lol, yep just been out and tried it as well with them shorted and it's logging fine, but the AYC and ABS lights are still flashing with the engine running :/ That's a shame else I would have kept it shorted.
Not sure if you saw my earlier edit, this is running on Vista as well
Excellent news Paul
The AYC and ABS lights flashing are the normal when it is shorted, you could put a simple switch on two bits of wire, so simply flick the switch when you want to log.
There might yet be a command that controls the OP2.0 Pin1 that I have not found yet even.
As stated some of the calculations will need working on, but most should be okay.
Were you impressed with the logging spee, as must admit I was
Brillianr to here it is working on Vista as well ! all good stuff
Good thinking, I might add a switch but I think I read somewhere that pins can be individually controlled.
Speed wise, fantastic Calculations, I compared it with the S-AFC that is plumbed in there for checking knock. The RPM was logged at a fairly static 875 and the S-AFC showed between 869 - 872 (ish) ... hmm I'll be able to get rid of that soon
Many thanks for the feedback mate
Glad it is working for you as well, good stuff
Cheers
Sean.
The program communicates with the ECU very well, but I keep getting an error when I try to "log to file" the error message says that I there was a bad file name. I think the error code was 52.
The program communicates with the ECU very well, but I keep getting an error when I try to "log to file" the error message says that I there was a bad file name. I think the error code was 52.
Someone else also seems to be getting this error, so will try and find time tonight to look at the code and do the file handling in a different way.
I just reinstalled 1.9 (I deleted it earlier because I thought it was useless) and I'm going to try it right now. I didn't try it out yet because my cable and car is not here right now. I didn't change anything, the file path goes back to the logs folder in c:\Programs(x86)\MutMonitor\Logs.
Quote:
Originally Posted by CLaNZeR
To set the path, you should just have to Click the Set Log Path button.
Then navigate to the folder you want to set and then click the Open button.
As simple as this. After the Open button is clicked it should update the MutMonitor19.cfg file that lives in C:\Program Files\MutMonitor
If you edit it with notepad, at the very bottom you should see the path listed.
After setting the Path, tick the Log to File Check Box and start monitoring.
The Application will then generate the log file name using the date and time.
What are your Regional settings that end out of interest?
I would stick to version 2.0 as there is a few other little fixes been put in there.
Version2.0 still uses the mutmonitor19.cfg file.
Could you change your path to c:\ out of interest just incase the (x86) is effecting it, as strange to have ( in a path.
Alright I changed the path to C:\MutMonitor\ and I set the logs to log into that folder just for now. I'l see if everything is in working order tonight.
SOLUTION: two words - regional settings. I have changed my region to English(United Kingdom) + reg. settings for non unicode programs as well, and that's it! Mut Monitor loaded with my OP 2.0 cable and what is the most important - without any lag. As soon, as I change my regional settings back(localy), Mut Monitor doesn't work.
This evenin is better than good for me. Finally, I have a universal cable, which is usable with all cars and all the soft I need. It's worth to mention, that sometimes Mut Monitor "crashes" - disconnects, but it is not a problem at all to press "start monitor" button So, if Clanzer would give me a debug version, I could test more, I don't need it for myself, as I have mentioned, I am satisfied 100%, but I think we could make/test together this wonderfull FREE software fail-proof.
My compliments and respect for Clanzer
As I promised yesterday evening, I took another alptop as well! I tested OP 2.0 + evoscan software. In case it's OT, you can del/moderate this... The most interesting thing appeared is incompatibility of my personal laptop PC with OP 2.0 cable It just has some problems with baud rate, just as Clanzer wrote day ago... still don't know how to solve this... but I have suspicions that my PC uses same port for unknown device, because when I open device manager -> Ports (COM & LPT), I can see device named Communications Port, which is missing on the laptop I have borrowed.
The Following User Says Thank You to dolphin For This Useful Post:
I'm glad to say that the new patch or update has worked! The only thing I didn't like was the very confusing txt file once the logs were recorded, BUT I'm still VERY happy that I can log my car now!
Thanks so much Sean!
-Tim
The Following User Says Thank You to timmiii For This Useful Post:
Mut Monitor Version 2.0 Released 12/04/2009
gettin some major changes, will test it FIRST thing its back on the road, which will be like 1-2 weeks, but thats awsome you got mutv.2!
has there been a new firmware update for it to allow the through put or did you manage to sort some other communication out?
Linear Mode
