legacycentral bbs

Just learned about this thing yesterday. I kinda dig the Windows Compatibility thing... and the gauge readout.

Anyone else using it? Kinda weary about building a converter they need to run through a serial port.

link?

http://www.vwrx.com/index.php?pg=selectmonitor

head2wind mentioned something about it in the marketplace. Looks real cool, i like the gauge face readout.

Yeah I remember that from a while back....

+1 I like it too & have a junker laptop that could say in the car just for this....

I have a junker laptop i will test it on, but i plan on building a car PC and i think windows will be easier to use vs. DOS with VRG's tool.

Im wondering if theres anyway to change the guage display to remove some of the unecessary gauges like tach & rpm...

Someone explain what parts I need exactly to for the serial port? I heard something about the radio connector then get the serial connector of course?

I'm using this on my SVX, but I have tested it on my Legacy and it does work.

I built the circuit on the VWRX website, but a better way is to get a USB to 5v TTL cable:
http://www.ftdichip.com/Products/Evalua ... 32R-WE.htm
Then you solder the radio connector onto the end of it. No circuit building required.

For more info, see http://www.alcyone.org.uk/ssm

b3lha thanks a ton for that info!

Your linux software, does that have a gauge interface like the Win32 software does?

Im interested in displaying a couple gauges instead of every one of them. Think you can help in any way?

Can this software log?

Gary

The VWRX software does not log. It is possible to turn guages off and only display the ones you want.
Kevin is not willing to release the source code so there's no way to customise it or fix the bugs. I would like to add a another set of O2 sensor guages, because the SVX has two, but the software only allows for one.

My linux software is not very useful. It just allows you to dump areas of ECU/TCU memory to a file. It does include a library of functions that a C programmer could use to create fancy logging and graphical software. I haven't developed it because I don't see many people running Linux, everybody wants Windows software.

The only other software I know of is JDash. The author has made provision to support older scoobies, but he needs somebody with a scooby and java programming skills to finish it off.

Lack of good software is the big issue at the moment. The hardware side has all been figured out thanks to Kashima and Vikash.

b3lha wrote:Kevin is not willing to release the source code so there's no way to customise it or fix the bugs.

I remember reading the forums at VWRX and he was waiting for VRG to release source code for his scantool... its funny he's not willing to do the same.

When you say it is possible to turn off gauges, how does one go about doing that?

TheSubaruJunkie wrote: I remember reading the forums at VWRX and he was waiting for VRG to release source code for his scantool... its funny he's not willing to do the same.

I would be the happiest guy in the world if people took my source code and developed it further. But not everybody thinks like that.

TheSubaruJunkie wrote: When you say it is possible to turn off gauges, how does one go about doing that?

You edit the config file:
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;Parameter "Mode" values have 3 options
;2=Parameter Enabled and not Scanned
;1=Parameter Enabled and Scanned
;0=Parameter Disabled
;-1=Parameter Invisible
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
BatteryVoltageMode=1
VehicleSpeedMode=1
EngineSpeedMode=1
CoolantTempMode=1
IgnitionAdvanceMode=1

etc.

I believe the program I got didnt have a config file, but I will look again.

AH!!! Look at that, the SelectMonitor.ini file

Thanks for the help. Now I just gotta build one of this fancy converter deals.

-Brian

A mini-review.

I tried making Vikash's scantool many times, but I was never able to get it to work. I tried both interfaces without success. I know my serial port is good but still no love.

I decide to give the VWRX software a go. As reccomended, I ordered up the FTDI USB cable. This is the one you want:


Mouser is the US distributor. Thier part number, phone and address is:


It only takes 3 wires.
1: Transmit from the ECU to recieve on the cable.
2: Recieve on the ECU to transmit on the cable.
3: Ground to ground.
I even used electrical tape to test with. No problems.


WinXP identified the cable and added a new serial port to the hardware manager as soon as I plugged it in. In my case it was Com6. I modified the .ini file to look for Com6.

Fired it up and first try it found the ecu and started reading the engine parameters.


Refresh is acceptable, and if you drop it down to 1 or 2 parameters it's downright fast. My laptop does have a problem returning from guage mode. I think it's a software bug and not my laptop. I also occasionally have the "'92 problem". At least the USB cable can provide the power for the comparitor circuit if I decide to build one.

For a $25 cable and a good faith donation to the VWRX site, this is a viable alternative to Vikash's scantool for those of us that just can't seem to get it going.

phyrram - i tried using the same exact cable as the one you show in your post, the TTL-232R-WE, and connected it the same way.

it read my ROM fine, so i know it is hooked up correctly; however the data would read fine for a few parameters, then go to obviously bad data (0's, -128's, etc), then recover for a few more, etc.

is this the "92 problem" that you and alcyone refer to?

Yes. The temporary solution is to reduce what your viewing to just 1 parameter. Then it re-syncs itself and you get usable results.

I have not attemped to build the comparitor circiut because my engergies have turned to the Power FC project.

i've been playing more with my TTL-232R cable and the vwrx software.

to summarize, i get the ROM ID read fine, then a few parameters read fine, then some garbage (0's and -128's), followed by re-synching for a few parameters, etc. etc. on and off.

iyesterday i tried running a port monitor from sysinternals.com while running the vwrx software, and to my surprise the extra load (or buffering or ???) on the port (or CPU or ???) makes it stays synched 80% of the time. it seems to be a buffer or synch problem rather than bad data for me.

anyone have any similar problem or luck fixing the synch?

I'm trying to use this same program with the cable I got from evoscan site. When I try to read the ecu. The rom ID is read as 464849? And it doesn't show anything. I switch the port and then the rom ID shows as null? Am I just using the wrong ports on my computer?

Something like that. 464849 is a non connection. Check the port, it's settings, your connetion is the right way around.

The 92 problem... I have been using a homemade rs323 adaptor for a few years and in my experiance... If the wires from the diagnostic port to the rs323 are too long there can be either a weak signal or you pick up interferance. I found that by keeping the rs323 adaptor close to the cars's diagnostic plug and using long wires(preferably shielded) from there to the laptop, the signal was better. I also have a FTDI chipped adaptor and I use a usb extension lead to it so the wires from the chip to the cars plug are as short as possible. I'm not really sure if it makes a difference with the FTDI lead but it might be worth a try.

Ahh, koo koo. Well Everything works now. I just had to keep refreshing it till it connected. Took about 4-5 start and stops to get it to go. Thanks for the info XD