Ooooooooooooo Its so close I can taste it..

I can release v1.5 with the UTEC/TUNER and Zeitronix ZT2 logging in a few days, or I can sit on it and release it when I finish the Innovate LC1 code...

Right now I'm just resolving some issues with getting the forms to load and unload properly, but as long as you don't do anything really unusual, its a real stable program.

Just a quick update..

the UTEC/TUNER will append **ALL** the UTEC or TUNER data to the MUT logs, which means you get boost, AFR, and everything else you can log with the devices Not only that but if you have an EGT sensor installed, you can log that and all of the Tuner Pro inputs through the Tuner.

Zeitronix guys are also in for a surprise, AFR, EGT, MAP, USER1 are all logged parameters, I can allow logging for RPM, but its not really needed, and when its not hooked up, the logs say "Inifinity" due to how the formula works so I left it out unless you guys really want it.

the LC1 code I *JUST* started, and will delay the release of 1.5, I can release a 1.6 version with LC1 support later on if I release 1.5 in the next few days.

So far it seems like everything works fine in a controlled environment, and the current Definition file would need to be revised for the new parameters (I'll add a few specific ones that are common to all wideband logs)

 

just release it jack, the lc1 guys can wait hahaha.

 

I think MJ's earlier point was that the LC-1/LM-1 guys already have both a free and shareware option for combined logging.

-jjf

 

That was exactly my point, 2 more weeks won't really affect those guys, plus I want to support the protocol properly and not just hack it together.

 

Since I just finished up getting my ZT-2 installed, my vote is to release! That and you can use the 1.6 release to fix any bugs that crop up when a larger pool of users hammer on it.

 

I can guarantee you guys will find bugs.. LOL

 

I was more teasing/tweaking the laugh. I should have used a maniacal laugh, like MUHHAhahahahahhhhh, instead of a wink.

I'd say if you taste it, release it. That is the fun of doing free and open stuff, you don't have to run every change or diversion through marketing and management for approval!

Switching notes. If I never pointed this out, you can use the free MTS SDK without LogWorks. Just install the OCX control and the file mts.dll from the latest version of LogWorks in your installation directory. Register the control and you should be good to go.

On the flip side, don't hesitate to ask if you have any questions about a native implementation.

-jjf

 

Thanks..

Since I have a good set of Comms written I will definitely go with a native implementation, I'm going to go back and look at the stuff you gave me already and then work from there once I get a data stream going.

 

I have made a decision, partly on my desire to support the entire Innovate product suite and serial data, It will not make it into v1.5 of mitsulogger, LC1 and LM1 support should make it into 1.6, and full MTS support in Unilogger (Mitsulogger 2.0)

I want to get something out for you guys to test in the next day or two after I verify I didn't make any stupid errors.

FWIW I now have a really cool test bench setup to do this sort of thing, now I only need the misc connectors for an ECU and some sensors or sensor simulators and I can do even more R&D on the ECU itself.

 

Malibujack Ftw !!!!!!!!!!!

 

Malibu,

Is there a way for you to include logging for dutycycle from the factory ecu?

 

Duty cycle isn't logged by the ECU that I'm aware of, there is a formula to calculate it from RPM and IPW, I think its posted somewhere on the forum, which means if you need it, you can add it right now.

On another note, looks like you should see 1.5 beta in the next day or two, then once I get some feedback on any bugs or problems, a 1.5 release by the end of the weekend.

 

If you can find like a 98 turbo eclipse in the junkyard the connectors are the same, i tested one because I was going to make a harness

 

I have quite a few of the physical ECU connectors, AMP sent samples of them to me a few years ago just before I worked with a Skunk2 and Z1auto to have a few of the Field CN04 harnesses imported from japan. It was actually the first time one of these harnesses was used on an Evo. Since then, several companies manufacture them and are pretty widely available (boomslang, etc..)

But I need the OBD-II and MUT Diagnostic connectors (the car side) and some documentation on which pins need to be connected to what on the ECU to create a bench harness (surprisingly every time I've asked about this information, either nobody replied or nobody knew) I know theres 12v power, 12v Switched Power, 2 Grounds, and at least 2 diagnostic port pins, but thats all the info I have, nothing on how to wire it. I would have wanted to create a complete simulator so I can test some of my ideas, but thats just too complex, so at the least I just want something that I can test/reflash an ECU at my desk.

This alone as been the major reason I haven't made more progress than I have with the ECU and learning about the maps and other things, as on the bench I can trace logic, control individual I/O, and other interesting things.

But this is off-topic and unrelated to this thread...

 

Malibu,

you have been pm'ed