people learn best by visual instruction. you can fit 100 times the information in a video than in a static pic.

do you mean like this one?
http://www.evox forums.com/forums/showthread.php?t=31168
(remove the space in the link above)

 

I have not found that to be the case, learn better and quicker by reading imho. Videos are more entertaining though.

Yes, that static picture is great for showing the correct connection, didn't have it at the time so... in trying to get my gps to work I tried every which way I could think of to connect it. It ended up being my lack of understanding that the GPS device was not "plug 'n play" but you have to customize the contents of SD card for your specific Evo that was my problem after all, not the connection. This is where I think a simple write up or a "Quick Start Guide" may be helpful.

As an aside; I have been unable to get circular bar guages to work in 2.2 beta even when using the “carbonXX.txt" files that came with 2.2 I’ve had to add a circular gauge overlay with pointer to get an analogue reading. Today I tried the GTR circular bar gauges in 2.1 and 2.0 and... they work! Should I revert to 2.1 for the time being to get the circular bar gauge to display correctly or is there a better workaround?

 

Tired of crawling in the dark like a blind kitten. Spat and decided to buy a PLX, is much clearer and easier to use.
Just wasting time and money.
My GPS Navigator on sale! For only 520US $ for the full kit

 

PLX can't datalog mode23 EvoX, and PLX can't datalog Mitsubishi, nor Subaru.

 

Really? Can you prove it?
And how about this. http://dashxl.net/dashboard.php?dashboard=73
I doubt that people create custom skins of Dashboard gauges, for software that does not work.
I need a device primarily as a gauge to avoid clutter up the dashboard.
datalogging for tuning I can do with my laptop.

 

You know it has been so long, and searching I couldn't find the answer *quickly* but it makes ask: what does mode23 give us that we can't get without it? As best I can tell the answer is basically everything that I can't see in oh ... let's say Torque. Which is a whole lot.

That said, if all you want is basic gauges of OBD2 parms then I suppose EvoNav is overkill; in fairness it just isn't for everyone. Then again so is PLX when you can just run Torque with a $60 obd plug. Assuming you have a smartphone. Of course as best I can tell obd2 boost is limited to like 22.1psi and it is slow (16parms/sec) but that might be my ebay-obd2 dongle.

 

2 Jumperalex
Deep datalogging for tuning, I can do with my laptop.
On the street I need to monitor the engine & SST oil temp, EGT, AFR, boost. And all of these parameters on one monitor / gauge. Evoscan for it requires a lot of different kinds of manipulation, adjustments.
In addition, there is a problem with Evoscan 2.6 PC version, ie after working with Evoscan 2.6, Ekuflash 1.4 not read / write ROM. Because of this, I still can not enable Mod23. And not only me.

 

where have all the experts gone from evom? this thread is a speculation fest lol. I think they all moved over to evoxforums.

 

- There is no known problems with enabling mode23.
- Mode23 is immensely superior than OBDII, nobody with a mitsubishi vehicle uses OBDII.
- OBDII maxes out at about 16 params per second (10400baudrate). whereas mode23 is 500,000baudrate
- Yes Evoscan GPSNav requires updating the data.xml to an EvoX mode23 version, and editing gauge templates since v2.0
- PLX is only obdII and only usdm, nobody on this forum is interested about obdii because it sucks, maybe I am biased, but I started EvoScan because I wasn't at all satisfied with obdii.

 

Mode23 is slow thou..

i only get 100 samples a second... roughly

so there is a lot of that 500k baud left to use

 

Sweet, some experts do still hang out here Hi Tephra.

yeah there sure is a lot of headroom. It is due to the J2534 and Op2.0 microcontroller interface rounds trips limiting it.

I have some new USB based EvoX CAN cables going on sale, could be a shock once you see how fast these operate.

I am also putting EvoX EFI actuators into EvoScan GPSNav this week.
====== 1 injector disable ======
====== 2 injector disable ======
====== 2 injector disable ======
====== 3 injector disable ======
====== 4 injector disable ======
====== Fuel pump ======
====== purge control solenoid ======
====== spark advance -5BTDC ======
====== radiator fan (high) ======
====== radiator fan (low) ======
====== cooling fan ======
====== VENT solenoid ======
====== A/C relay ======
====== Oil control Valve ======
====== EGR valve ======
====== Wastgate solenoid valve ======
====== variable intake air control ======

I have also now got the Security Key for EvoX, I may be able to have a button on the GPSNav to "enable mode23" option soon.

I am also investigating some faster data transfer modes. I am seeing step up speed modes for ECU reprogramming in a number of CAN ecus.

 

nah its the ECU rate limiting the CAN requests... presumably for the particular protocol we are using... KWP2000/SSF14230

I have tried a few times - although unsucessfully - to speed it up..

Which security key thou - as I said to Acamus there are a few depending what mode (diag/flash) and then a few more depending what sec level you want (1-9)

 

From what I've seen, the 2010's log about twice as much data per second as the 2008's do. I have no idea why, just seen it happen time and time again.

 

really?

i will have to check it out - might be onto something

 

Really? I haven't noticed that, although that doesn't mean it isn't true.