My question is very simple (but a search yielded nothing)..

I just picked up a used UTec, and noted that the form factor is somewhat changed from the first gen UTec I ran on my WRX a few years ago. Needless to say that the UTec obviously now has a single toggle switch to put it into reflash/update mode. Unfortunately, while the user manual mentions position A and position B, my UTec is not marked as such nor is there anything else to indicate which is the reflash position and which is the 'run' position.

Given that I bought the thing used, I don't want to make any assumptions on which position the toggle switch is at. So, if the toggle switch is moved toward the edge of the device that it's closest to, is that reflash mode or run mode?

Second question: The serial cable was not included. If I pick up a standard DB9M-DB9F PC Serial cable, will that suffice or will the extra (unused) pin connections cause problems for the UTec?

Thank you.

-pace

 

If you havent already, go download the latest manual from turboxs' website. This will explain the switch position. You have to pull the UTEC out to change this switch postion. If you dont get an answer Ill pull mine out just to check the switch position. I dont believe it boots up though if its in the flash position.

Any RS-232 DB9 Null modem cable should work fine.

 

The current Evo UTEc manual on their website describes popping the cover and manipulating either an array of dipswitches or two toggle switches. This appears to conflict with a photograph near the beginning of the manual that depicts a single recessed external dipswitch which reflects what I see on my UTec. The manual supplied with my UTec is also different from the one hosted on their website, in that it makes reference to the single dipswitch with two positions (A & B). However, as I said above my UTec has no markings to indicate position A or position B nor does the manual say which is which.

It seems the easiest thing would just be for me to power up the UTec with the switch in either position and see if I can access the UI.

Cheers,
-pace

 

Just for the record, this is incorrect. A null modem cable has the following pinout:

5 - 5
2 - 3
3 - 2

..that is, it crosses over pins 2 and 3. I purchased a null modem this evening, and was unable to connect to the UTec. I then made up my own cable to do a straight through (Serial pinout) which allowed me to connect just fine:

5 - 5
3 - 3
2 - 2

Regarding the single dipswitch on top of the UTec: I found that flipping it toward the edge of the device that it's closest to, puts it into reflash mode (ie. that is the 'A' position). I have version 1.0 of the manual. The version that is on the TurboXS website (version 1.6) outlines a reflash procedure that does not match my UTec device. ie. It mentions that the device will either have two internal toggle switches or an array of dipswitches. If my memory serves me, that is the layout for the WRX board. Assuming that the Evolution UTec has not changed from the form factor I have (single dipswitch), then it seems that the v1.6 Evo manual was copied from the WRX manual, and they forgot to edit the section X "Software Maintenance". They also mention in section X that the current software version is 3.1, which I believe is a WRX firmware version number.

Just a friendly heads-up.

-pace

 

If you push the switch to the closest edge, it is in reflash mode and when it is pushed the other direction, it is in running mode. (When mounted in the car, the switch going UP is reflash, going does in running) You can flip the switch when the UTEC is in the car, you just need to frabricate a tool to do so since typically your hands are too big. I used a bent paperclip and it works great.

Alfred

 

I do the same thing.. Flip it up with a paperclip or occasionally I can get my finger in there enough to flip the switch..

You are correct, the manual is incorrect and reflects the first and second gen WRX switches.. The newer ones should only have the one switch for reflashing.. If there's another switch, its hidden in the case and obviosly isn't intended to be accessed..