I'm about 30 miles east of Dallas in Royse City..

I will be looking to do some testing on the EVO X in the area at some point in the near future.

 

So did anyone close to NC get a beta cable? I have an EvoX if someone would like to pull the image off the ECU.

Ironically, I almost moved to Dallas area in Jan as well. The company I used to work for got bought by it's biggest competitor, and I was offered to go to Plano or find a new job. I found a new job, but dang, if I knew all this was going to happen and that's where the closest beta cable was located, maybe I would have gone to Dallas. No, just joking.

 

EnglishRacing (SW WA) is also looking for a X to pull a ROM off of and work with a tune. Contact for more information please.

 

this would be pretty cool to log without the laptop. but what if you want to log your wideband afr as well?

 

Log it via the rear O2 input. (It also has support for Innovate's logging bus natively, so LC-1 owners should be able to log without additional wiring.)

 

yeah analogue input's FTW... I hate LC1 serial bs!

 

It does have a serial port (the jack that the reflash plug plugs into) that can be used for logging wideband data. Currently the plan is to log the Innovate wideband, but looking at the hardware, it can log anything that has an rs232 port. For standalone logging, it depends on what types of features and firmware support Colby puts into it.

This will be able to log any Can bus car or truck, along with nearly any OBD-II car once all of the support is put into it. I know from experience that OBD-II stuff is a bit of a pain to develop, MUT was quite a bit easier. But if the data is on the CAN bus, it will be available to be logged if we know what we're looking for.

This cable can do much more than what is already documented, but it looks like it will work in many dashboard and logger applications that support CAN and Passthrough cables once its complete.

My immediate plans are to build an equivalent to Mitsulogger for logging MUT through this new cable. The other features will come as the driver/dll support evolves.

 

So, are things working now? I'm willing to beta/charlie test a bit, just don't want to spend an extra $20.

Do I need the one with the full connector set or can I buy the cable only?

(I'm not clear on whether the secondary power connector comes with the $169 cable only version.)


EDIT: Just got a very nice call back from Tactrix. Still pushed back a couple of weeks as colby is waiting for software from vendors still, their sales software is just being finicky and listing as available. For the Evo VIII/IX you will order the cable only version and then just an extra connector which will be less than ordering the full set.

 

what does openport 2 give us that we dont already have?

 

lighter wallets! I keeeeed

 

For pre-CAN cars, the attraction is the ability to log data to a microSD card that can be inserted into the OpenPort 2 plug.

For CAN (and other protocol) cars, the attraction is more apparent.

Will you be revising EvoScan to work with an OpenPort 2 cable when it becomes available?

 

The logging to SD thing is huge for me... it would allow me to do data captures much more regularly and much more often when I think somethings up. Would be very handy right now for dialing in my e85 boost

 

I agree, I used to take my laptop with me everywhere until it was stolen out of my car...hiding the SD card/cable should be much easier and let me get back to regular logging.

 

I think the biggest value of the new cable for those who already have an openport cable is the logging to SD card. If you can already read/write/log/flash then there's not a huge difference in functionality.

For those of us who are tuners, or data log many different cars, this cable supports WAY more than the earlier cable. The ability to read/write can equipped cars (not just the Evo) logging OBD-II or Diagnostic Data protocols of nearly any domestic or foreign car equipped with an OBD-II port, a full set of controllable OBD pins to trigger other diagnostic modes, etc..

I picked up a Infiniti G35 just to work with CAN bus and the Consul-II protocol, I have a ford to work with VPW, and access to new and old GM and BMW cars. So a working one-cable-fits-most is worth it.

In some cases, the final driver functionality of the cable will function as a true compatible passthrough device that should be recognized by dealer diagnostic software (And third party software) that support passthrough cables.

Mitsulogger's new variant Unilogger is already working to log MUT-II through the new API, it will log CAN Bus data (not anything specific at the moment) once I can verify it works and can build a bench harness with CAN specific functionality (this is a bit more expensive of a project for me)

The drivers work, we can read and write ECU's for both early Evo and Subaru (basically what the 1.3 cable already does) fairly reliably, but its not 'perfect' yet. Once that is squared away, all the new functionality will begin to come together.

I am also looking to get the Nissan (350z and G35) ECU support into ECUFlash and will work towards that, along with CAN Bus equipped mitsubishi and Hyundai vehicles which share similar ECU's

There's alot going on and very little time, but it looks like everyone on the beta team is very diligent and has very specific skills and target vehicles to test with, so this should actually go pretty quickly.

 

Hmm. I'll need to check in elsewhere to see if the Enginuity/RomRaider folks are aware of or beta-testing this yet.