Memory dump of ECU

[Dessertrunner]

If a number of people are going to work on JDash then would it be best to have it on a seperate thread then it won't get so confusing with all the topics at once.

[TomsSVX]

you did use the dump facility right?? Hit the get ID button to get started... Then close the dump and open the select monitor to get going

Tom

[SVXRide]

FYI,
If we need some JAVA programming, I have a brother who knows how to program in it. Just let me know what we need him to look at.
-Bill

[Hocrest]

Originally Posted by TomsSVX

you did use the dump facility right?? Hit the get ID button to get started... Then close the dump and open the select monitor to get going

Tom

Yeah, I got a "null"

[TomsSVX]

Ok, SVXRide is nice enough to lend me his innovative wideband that has datalogging software and hardware. it allows me to monitor the AFR along with 4 other 0-5v analog sensors.... What can I use?? I mostly want to monitor timing retard, TPS, RPM, and anything else someone would suggest? Also, what is a good way to tap into these??

Tom

[Nomake Wan]

Originally Posted by SVXRide

FYI,
If we need some JAVA programming, I have a brother who knows how to program in it. Just let me know what we need him to look at.
-Bill

Awesome!! I'd have to test the darn thing out before I could say what (if anything) is wrong with the software, but it'll be at least a week before I'm able to do that. Work is starting to pile up.

Hocrest: Sounds like a connection issue, but let's make sure it isn't something simple before jumping to conclusions like "my cable isn't working." Open SelectMonitor.ini (the modified one, which you should have replaced the VRWX one with). Now, leaving that open (but ignoring it for now), go to Start-->Control Panel. Then (assuming you're using XP/Vista and using "Classic View" for the Control Panel) open the "System" panel.

Click the "Hardware" tab, then click the "Device Manager" button. Click the "+" box next to "Ports (COM & LPT)" and check to see which port you're using. If it's a USB adapter, it will most likely be named something obvious like "USB Serial Adapter." The COM # next to it is what you need; it'll say something like "COM11."

Using COM11 as an example, you then go into SelectMonitor.ini, and change:

CommPort=1

to

CommPort=11

Then it should work. If that does not work, then you do have a problem with either the USB hub on your computer (unlikely) or the cable itself (likely) or the car's transmitter (unlikely).

In the event the above does not solve the problem, post such and I have another test which can be performed.

[Hocrest]

Yeah, I set it to com 5. I'm gonna check it out on my 97 Leg tomorrow to see if that does anything different....

[Nomake Wan]

In that case, please get the RS232 Comm Tool from here:

http://www.rs232pro.com/include/RS232HD60.exe

I'll add you to AIM and see if I can talk you through the small test.

[Hocrest]

It's downloaded... I'll be here all morning.

[sd2649]

Originally Posted by TomsSVX

Ok, SVXRide is nice enough to lend me his innovative wideband that has datalogging software and hardware. it allows me to monitor the AFR along with 4 other 0-5v analog sensors.... What can I use?? I mostly want to monitor timing retard, TPS, RPM, and anything else someone would suggest? Also, what is a good way to tap into these??

Tom

I would love to see some data on the 5v torque control wire. Although, I believe an FWD and AWD model MIGHT have different results under different conditions.

[TomsSVX]

without the auto trans it will not show anything

Tom

[Hocrest]

So between phone calls with Tom and chatting with Upnorth Mike and Nomake, it still isn't working. Mike thinks I need to add on a board to correct for the "92 ECU problem"

Chatting with Nomake today, we couldn't get it to communicate with the TCU either. Here is the a copy of the chat;

[10:58] nomake wan: Ready for a little experiment?
[11:12] nomake wan: So open up the comm tool, and hit F1. It'll bring up the port config screen.
[11:13] Hocrest1: ok
[11:13] nomake wan: Set to
Baud: 1953
Data: 8 bit
Stop: 1 bit
Parity: Even

And whatever COM port yours is.
[11:13] nomake wan: Then click open and it'll start up. Then turn the ignition on if it isn't already.
[11:13] Hocrest1: flow?
[11:14] nomake wan: No flow control.
[11:14] nomake wan: Forgot that was an option.
[11:14] Hocrest1: ok
[11:14] nomake wan: Once it's all up and all. Type this in:

45123400

and hit enter
[11:14] nomake wan: You should get a stream of numbers back.
[11:14] Hocrest1: ok
[11:14] Hocrest1: nothing
[11:15] nomake wan: Crud. Looks like the connection's hosed. :\
[11:15] Hocrest1: all i got back is TX>45123400<TX

[11:15] nomake wan: Yeah, which is just what you sent.
[11:15] Hocrest1: yeah,
[11:15] Hocrest1: one of the wires broke
[11:15] Hocrest1: h/o the iron is still hot
[11:16] nomake wan: k
[11:19] Hocrest1: ok, lets try this again
[11:19] nomake wan: k
[11:20] Hocrest1: same thing
[11:21] nomake wan: Hm... where'd you get the cable from? Or how is it connected?
[11:21] Hocrest1: ebay, i just have pins soldered on following this match up
[11:21] Hocrest1:
GND(black)(USB-cable) to GND #9 (green/black)(SSM-connector)
TXD(white)(USB-cable) to RXD #3 (blue/white)(SSM-connector)
RXD(blue)(USB-cable) to TXD #2 (orange/white)(SSM-connector)
[11:22] nomake wan: What's the model number on the eBay cable?
[11:23] Hocrest1:LINK
[11:24] nomake wan: Yeah, I just saw that. Hm. Lemme check the datasheet.
[11:25] Hocrest1: i'm in the device manager, should i set the properties in there that you gave earlier
[11:25] nomake wan: Nah, because when you run a program like SelectMonitor and Comm Tool it overrides the default settings.
[11:26] Hocrest1: k
[11:26] nomake wan: Is this the first USB->Serial adapter you've plugged into this computer?
[11:27] Hocrest1: that i can think of
[11:27] nomake wan: When you plugged it in, did it just install itself? Or did you use the drivers off of the website for the cable?
[11:27] Hocrest1: it came with a disk with drivers
[11:28] nomake wan: Hmm... Open up the properties page in the Device Manager.
[11:28] nomake wan: Go to the drivers page, there should be a version number.
[11:28] Hocrest1: ok
[11:28] Hocrest1: 5.0.0.0
[11:28] Hocrest1: silicon lab
[11:28] Hocrest1: 6/21/2007
[11:28] nomake wan: Well crap, that's pretty recent. Newest is 5.1 but I can't imagine that it would be the problem.
[11:28] nomake wan: It was in my case but you've got the right drivers. :\
[11:29] nomake wan: Oh.
[11:29] nomake wan: Here's an interesting idea.
[11:29] Hocrest1: ok
[11:29] nomake wan: Connect the TXD and RXD wires from the USB cable together.
[11:29] nomake wan: Leave ground connected to the car.
[11:30] Hocrest1: ok
[11:30] Hocrest1: ok
[11:30] nomake wan: Then try the whole "45123400" thing in the comm tool again. You should get two lines instead of one.
[11:30] nomake wan: (since it'll receive what it sent)
[11:31] Hocrest1: TX>45123400<TX
3400

[11:32] nomake wan: Even parity, makes sense. The cable's working.
[11:32] nomake wan: I guess you could try reversing the TXD and RXD from the car.
[11:32] nomake wan: And then do the comm tool again.
[11:32] Hocrest1: i did it 2 more times and got this
[11:32] Hocrest1: TX>45123400<TX
3400
TX>45123400<TX
451234
00
TX>45123400<TX
45123400

[11:33] Hocrest1: ok
[11:33] nomake wan: Yeah, cable's working. The comm tool just formats oddly (line breaks).
[11:33] Hocrest1: same thing, just the tx>...
[11:34] nomake wan: Damn...wait
[11:34] nomake wan: ...
[11:34] nomake wan: omg
[11:34] nomake wan: Is this the racer?
[11:34] Hocrest1: no
[11:34] Hocrest1: my stock car
[11:34] nomake wan: Oh. Auto and all?
[11:34] Hocrest1: yep
[11:34] nomake wan: damn
[11:34] nomake wan: the "45123400" talks to the transmission, which in all tests works regardless.
[11:34] nomake wan: So the TCU should be responding.
[11:34] Hocrest1: i have a 97 legacy i can plug it in to
[11:35] Hocrest1: i have the odbII pin outs also
[11:35] nomake wan: One last test before that.
[11:35] Hocrest1: ok
[11:35] nomake wan: Type

78123400

and hit enter
[11:35] Hocrest1: same thing
[11:36] nomake wan: damn.
[11:36] nomake wan: Okay, legacy time
[11:36] Hocrest1: give me a minute
[11:44] nomake wan: Ah crap, I gotta head to work. The thing for the Legacy is exactly the same. Try 78123400 for the engine and 45123400 for the automatic transmission. If nothing, then post the results in the ECU Dump thread. Link to the datasheet for your cable so b3lha can look it over.
[11:44] nomake wan: He might see something I'm not.
[11:44] nomake wan: Cable is working so... hm. Later./
[11:45] Hocrest1: ok, i'll let you know

The Legacy acted the same way.

Any thoughts? If I can't get this cable to work, I'll just get one of Mike's...

[b3lha]

I may be wrong, because the datasheet is a bit cryptic, but it looks to me as if the CP2102 chip in your USB cable is for 3.3 volt TTL. The car uses 5 volt TTL.

This could be the problem. The cable is using 0v to send logic 0 and 3.3v for logic 1. The car is expecting 0v for logic 0 and 5v for logic 1. It could be that 3.3v isn't quite high enough for the car to recognise it as logic 1. In other words, it could be the 92 problem in the opposite direction.

[Nomake Wan]

Phil, you're correct. I just read the datasheet and it is indeed a 3.3V model.

http://cgi.ebay.com/ws/eBayISAPI.dll...ype=osi_widget

That, however, is the +5V model.

[Tobi]

So is it, you need a 5V-TTL-Level.