RhinoPower Ltd

goss · Member

RE: 33920-77ED 0 TA11W 3-dr Escudo 2.0 V6 H20A

TechSupport · Guru

I've looked at the logger and the issue is that when it autoscales it restarts from the right hand side so it appears that there is data missing. I will have to look at scaling the parameter so that autoscaling doesn't occur.

I haven't checked the O2 issue yet.

TechSupport · Guru

There is an issue with the Fahrenheit/Centigrade switching, there is a new release coming this week that will fix that.

The ECU ID is no longer displayed unless it is not recognised by RV.

The datalogger appears to jump around a bit due to the autoscaling, the data should display OK in Excel, please let me know if it doesn't.

I'll check out the raw data/formatted data, you may need toggle it a couple of times to get it to switch properly.

The O2 sensor display I will check, I'm not aware of an issue with that.

goss · Member

Hi Rhinoman,

I have found some minor bugs in RhinoView v0.91.1:

1. My ECU ID is not shown in the dataview window (Sniffed serial communication: 10 03 ED 10 05 16 01 D4)

2. ATS and CTS parameters are not shown correctly (There is about 9°C outside, the motor is almost cold after approx 1min working. ATS=48°C, CTS=62°C. It seems to be it is in Farenheit, but shown as Celsius...)

3. Datalog graphs have a lot of gaps and sometimes lines dissapears and appears randomly...

4. sometimes both O2 sensors shows "0", then they go back to normal values (I hope this is a bug too...)

5. DataView display "Format"/"Raw data" button is not initialized to "Raw data".

I have screenshots and captured data if you need.

Best regards,
Gabor

goss · Member

Rhinoman,

I have found the problem. The prolific USB-serial cable had a ~10% baud rate error. It works well with FTDI :) The program works well, thank you very much!

Do you plan to support ABS and AirBag ECMs too? If so, I would be happy to help in the work. For example I have now issues with the G-sensor and it is a little annoying that I cannot read out the trouble codes with the blinking ABS lamp, because it lights continously... I know that there is a pin on the ABS diagnostic connector for this purpose, but the ABS and AirBag ECM support SDL too...

Gabor

goss · Member

It is a '96 Vitara for German market. The connector is similar to the GM 12 pin diagnostic connector, so it is not ODB II. There are 3 pins in the connector: GND, +12V, SDL.

Thanks,
Gabor

TechSupport · Guru

I now have all the data for OBD1 ECUs from 1991 through to 2010 although my interface only supports the SDL interface on pin 9. RhinoView only supports engine data but there is no longer any need for user configuration. It would appear that your interface is faulty or your ECU does not support SDL, what year is the vehicle and what market was it intended for?

goss · Member

Hi All,

Last weekend I have found the "ALDL" connector of my Vitara :) As an electrical engineer it's a "must" to communicate with the ECU. Looking for more information I have found this topic. Could you tell me what is the status of the H20A ECU config?

My ECU label shows 33920-77E1. Last weekend I tried to communicate with the ECU, without success. I have used a prolific USB-RS232 cable and the MAX232+diode circuit. I have noticed, that the data line stucked in "0" after the first start bit, so I have applied a 10k pullup resistor to +5V... The baudrates (8192, 7812 or 15625) and the signal shape seems to be ok. I will continue the trial at this weekend too. Once I will have success, I would be happy to help in the project.

Preparing for the weekend I have some questions:
- What is the voltage level and baudrate for the data line? I suppose that is has an 5V open collector TTL RS232 like interface with 7812bps... right?
- Can I communicate with other modules on this line (eg. ABS, Airbag)
- Do I really need the pullup resistor or the data line is broken somewhere?

Best regards,
Gabor

TechSupport · Guru

I don't have one of these in stock but if your ECU is faulty then I can probably repair it.

kikiclark · Newbie

hi

can you find one for me computer ECU for suzuki vitara escudo TA11W, year 1995, 3doors, diesel. ref: 33920-77E00

i have some problem so i wantto buy

-- Edited by kikiclark on Tuesday 27th of March 2012 11:29:26 AM

shenglu · Newbie

I look forward to helping to add another ECU / configuration files. This will ensure more insight to their own, when I complete all of the sensors.

TechSupport · Guru

The O2 values should bounce about between 0V and 1V, it would be a good idea to unplug them one at a time and see if the values at those locations freeze. It looks like bank 1 needs to halg its value, I suspect that the location for bank 2 is incorrect.

I heard about the earthquakes, I do hope you are not too close to the epicentres.

the alfer · Member

Like you, I got distracted as well... by another few earthquakes Monday last week. And a nice long weekend out of here to 'reload' the nerves.

The O2 sensor values are jumping around in yellow, red and green. Going up and down and I have no idea what the correct values should be (probly the green ones aww ) or how stable they should be. Maybe even the values I see are not from the O2 sensor? Or are you sure that the location where you get the data from are from the O2 sensor (can I check that for you in some way?). If the data logging works, I could maybe drive around while logging the sensors that you need?

Just ideas...

Cheers,

Ron.

TechSupport · Guru

I got distracted from this but I'm going to try and take a look at it over the next couple of days. The O2 sensor readings aren't quite right so I'll look into that. I'll take a look at the air and coolant sensors too, the Russian info is a bit more complete than the english language FSM, hopefully the data will tally.

the alfer · Member

Hi James. Just emailed some info in Russian. confuse But maybe you can make sense of the graph that's on it.

Cheers,

Ron.

the alfer · Member

No, don't have the FSM. No FSM to be found for the H20A on the net. cry

Will see if I can get some info on the net about just the sensors?? (tommorrow)

Cheers,

Ron.

TechSupport · Guru

I had a look at IAT and CTS yesterday, the correction factor is quite different from the other models that we have looked at so far. Do you have a factory service manual? if so a scan of the graphs for the sensors would be useful.

the alfer · Member

Hi James,

Had another look this morning. RPM looks good again. Haven't driven the car, but no doubt speed will be working again as well.

Send you an updated Excel sheet of this morning.

Target Idle went down from 192 together with RPM while warming up and settled at 102.
Actual RPM reading was 1549 with Target idle of 192 and rpm of 824 with Target idle of 102.
So Target Idle value doesn't show the target idle speed in RPM?

Noticed another thing; 
The CTS (which is the Coolant Temp Sensor, right?) started at -22 with a cold engine (10am, 10 degrees Celcius outside after a 0 degrees night)
and settled at a reading of 48 after running idle for 15 minutes, with the temp gauge in the car halfway between Cold and Hot,
which is the normal reading while driving.
So guess there is something not right in the conversion of the data to readable info.

Cheers,
Ron.

(and thanks for your patience in explaining things to an ignorant soul.)

-- Edited by the alfer on Saturday 11th of June 2011 12:48:10 AM

the alfer · Member

Hi James.

Sorry, no time to do anything yet. Had a long day yesterday and it's going to be a long day today (workwise). So I'll let you know/ have a drive tomorrow. All that working realy cuts in my hobby-time furious

Cheers,

Ron.

TechSupport · Guru

OK, download that file again, I've put the RPM and VSS addresses back where they were originally.

TechSupport · Guru

Vehicle speed is taken from the vehicle speed sensor on the rear of the speedo so it won't be corrected for tyre size. If the speedo reads the same for both mph and kph there must be a bug, I'll check that. I think that most people are using MPH so I haven't had any comments on that before.

I'll change the file back to use the previous address for MPH and VSS. Target idle should display the idle speed so on a cold start you will see it fall with the actual idle speed. It should stabilise at 800rpm or thereabouts

the alfer · Member

Just had a quick drive before that ..... laptop battery died again. (got a new one, just has to get charged overnight.)

The RPM on the old version is correct according to the rpm in the car. 2000 = 2000 and 3000=3000. The Speedo works, but has wrong values, where does it get it's info from?

Reason why I ask is, I got a mechanical drive (cable) to the speedo, but also my tyres are bigger, causing a wrong (theoretical) reading on the meter of about 17.47% to slow.

ALSO.. changing MPH to kph doesn't make a difference in readout, so readings I got on RV are in MPH? Ehhmmm... That makes sense, I stand corrected.

RV Reading IS correct, but shows MPH only (so the tyresize don't matter to the program)

Speedo Reading of 30 kph shows RV reading of 18, which in miles would convert to 28.9kph.

Speedo Reading of 45 kph shows RV reading of 27, which in miles would convert to 43.4kph.

Speedo reading of 70 kph shows RV reading of 44, which in miles would convert to 70.8 kph

On the new one you've send NO RPM at all, also NO Speedo.

Didn't have the time to look at the target idle... not that that matters as I don't know what it should be. (I did tell you I'm no mechanic )

So what do I have to look for at the target idle?

TPS reading went to 100% when opening up the throttle to full.

I haven't checked any of the other addresses yet, so will have to get back to you about that.

Cheers,

Ron.

TechSupport · Guru

I just changed the RPM locations because they didn't tally with the 1701 definition I have from Regressor, if you were getting RPM correctly then something isn't quite right. Check out the rest of the addresses and I'll change that back if necessary, does the target idle look OK?

The auto has a very complete set of status flags, it'll make a good test of the statusviewer once its released.

the alfer · Member

I've just send the excel sheet. Hope you can do something with it. If it's no use to you, let me know how I can give you some useful info.

My car is an automatic, yes.

I'll have a look at the definition this evening (if it's dry) after work.

Cheers

Ron

TechSupport · Guru

the alfer wrote:
Hi James. Well, I got some time to have a look today (until the rain came..) I've put all the info I gathered into a spreadsheet. Where can I send it to, as it's a bit much to put in here .

Sorry I missed that bit, please send it to rhinoman@rhinopower.org. I will work through it all on the simulator along with the data from regressor. I've put the bank 2 stuff into the datastream definition but I will need to do a software update to get the correct ISC parameter, the latest definition is linked below, please copy it to your bin folder and see how that looks to you.

http://www.rhinopower.org/Rhinoview/release/datastream.csv

Your vehicle is an auto transmission? there are a whole bunch of status flags for the AT I will need to work through.

Cheers

James

TechSupport · Guru

There are three definition files for the ECU, each sorted by ECU ID number, the main file is the definitions for all the diagnostic addresses and scaling values. If that definition is present then you will get the data displayed on the dashboard and on the dataviewer and logger, not all of the addresses for the 1701 are currently defined because previously this ID was only known to be used on the J20 engined Escudo.

For the fault codes the value at each address defines up to eight fault codes, a second file defines the locations (bits) for each of the fault codes. The definition for the 1701 needs to be added to this file.

There is a third file that defines the locations of the status flags but the status viewer is still under development and is due to be included in the next release.

A few years back Regressor logged the 1701 ECU using a Carman scan tool so I have all the addresses. I will modify the definition to add the additional registers required for the V engine and then we'll take a look at the numbers that you're getting. When Regressor did his work we didn't have much of an idea as to how all the scaling factors worked so that part is incomplete. We were also curious as to why the scan tool was showing locations for bank two - you've answered that one now.

the alfer · Member

Ok.. here are the results from New Zealand wink

I used a freshly downloaded RV to be sure no previous tampering in the program would affect anything.

After starting the laptop, connecting the interface and switching on Contact (motor off).

(Yes, that might be a good point to add in the 'manual to be' )

Started RV, Set the comm settings to the one I found works for me. (Com5, 7812).

Connect

ECU ID Right Bottom then shows 1701.

Message pops up "Fault Code Analysis not available for this ECU".

Pressing 'OK'

And here it conflicts a bit (I think) with your description as it did NOT switch to ECU ID 0000. (Unless the warning message you were referring to is something like "Unknown ECU xxxx, defaulting to 0000" and not the one I got.)

Guess we have a bit of a 'halfway point' here.

? For the 1701 not everything ( fault code analysis) is available and that is why the program shows the message, but some things ARE available (I can see a reliable RPM, Battery Voltage and possible more) and so the program doesn't switch to 0000. ?

So far my bit. Tell me what to do next maestro

Cheers,

Ron.

TechSupport · Guru

When you connect RV will request the ECU ID, if it is a known ID then the software automatically selects the correct mapiing for that ECU. If the mapping is not known then the software will display a warning message, while that message is displayed the ECU ID should be displayed in the status bar. When you press 'OK' it will switch to ECU ID 0000.

I will change the next release to try and make it all a bit more user friendly. I will change the warning message to display the ECU ID and also display the real ECU ID in the status bar rather than the '0000' ID. I'll delete the ECU ID option from the menu bar as well because it is no longer needed and hasn't been supported since v0.2.

Its good that you aren't an expert, I need this sort of feedback to help improve the software.

Thanks

James

the alfer · Member

If it's dry tomorrow, I'll check it.

Is the 1701 always a (manual) choice in the ECU choice, next to the 0000 and 1112?

TechSupport · Guru

If the ECU ID is 1701 then RV should start displaying data once you hit connect. You shouldn't get the ECU ID not supported message, you will see 1701 in the sataus bar on the right hand side.

the alfer · Member

Hi James. Well, I got some time to have a look today (until the rain came..) I've put all the info I gathered into a spreadsheet. Where can I send it to, as it's a bit much to put in here confuse . I was unable to drive around with the laptop as the battery died completely.

A few things I think I can conclude out of the info I got so far.

I THINK when doing the ID-request, I got 1701.

With ECU-ID at 0000

Locations;

TPS 12 and 13

Air Intake Temp 11

WTS 10

Faultcodes location 3 changed in the following without resetting between unplugging sensors; (location 3 was 1 at start)

Air intake Temp; 65 (forgot to write down loc 0 (or was it 0?), sorry)

WTS; 69 (loc 0 = 4)

TPS; 85 (loc 0 = 16)

Disconnecting MAF didn't change anything, but switching contact off and back on (with MAF disconnected) changed location 38 from 1 to 144. But switching contact off again, reconnect MAF and contact on kept location 38 to 144 ??

I then started the engine, selecting ECU-ID of 1701

RPM, MPG, Battery values all looked OK to a non-mechanic like me, so possibly the 1701 has (almost?) the same layout as my ECU?

Guess if you take a look at the values in the Excel sheet it makes sense to you smile . I wrote down the values at RPM of 870 (idle) and slightly raised at 1500 RPM, hoping that would help you to conclude something out of that.

Hope this is of some help, tell me what to do/check next (while I'm going to look for a working laptop or battery cry )

Cheers,

Ron.

TechSupport · Guru

OK, no problem we'll be patient biggrin

the alfer · Member

Hi James. Will have another look. But it looks like I'll have to do the investigating in the weekend. Over here it's dark before I come home and I have to work outside.. To say the least winter IS coming, currently about 4 degrees C outside. So, give me some time, but I'm looking forward helping to add another ECU/configuration file to the list. It'll sure give myself more insight of where all the sensors are when I'm finished biggrin . Nice project to work on.

Cheers,

Ron.

TechSupport · Guru

When you first plug in you should get an ID displayed in the status bar until you hit the OK to confirm that the ECU ID is unknown. We need that ID and then we can start building a map if necessary.

The drop down menu is a legacy piece of code that I need to remove. For now use ECU ID 0000. Check the first four or five addresses, those will be your fault codes, record any numbers that are currently showing and then clear the codes. Now unplug a few sensors, one at a time and record the numbers that show in the dataviewer and post them here.

Cheers

James

the alfer · Member

Thnx Fordem, Rhinoman / Rhinopower told me when I bought the interface that my Zuk/ECU wasn't in the list yet, so I'd probably have to do some work (like you said). That's why I assumed I had to figure out which ECU to choose (had the choice of 3; 0000, 1701 and 1112) Seeing there are way more numbers available in the listing of TheZuke, I guess these 3 are the ones the software came up with based on whatever info it got from the ECU.

Now just have to figure out the rest of the screens and what they represent. For instance I have a '1' at Fault flag 2, while fault flag 1,3 and 4 are '0'. Now.. is there any conclusion I can draw from that? Like I said earlier, don't really want to start asking questions before I've had a good look around on the Forum for answers, but it looks like you've done a lot of work with the software, mapping your car, seeing the posts towards Rhinoman. Maybe a brief answer hmm ? There is no short 'manual' that I've missed about the software is there?

Cheers, Ron

fordem · Senior Member

Once connected, RV will "autoselect" the correct ECU-ID, IF it has a configuration file entry for it.

Check the bottom line of the display, right corner - you should see an ECU-ID there.

Here's a list of the known IDs

If your's is not on the list, you'll need to create a configuration file entry to match.

the alfer · Member

Just got the interface in by mail. Looking into finding out more about my Zuk. Especially the fault codes.

Got the engine light sometimes coming on at 100 km/h (yes, only at that speed so far). Lifting my foot off the throttle a bit and it goes out. throttle back on and after a minute or so it comes back on. This 2 to 5 times in a row and after that suddenly no problems what so ever... confuse Will have to find a way to get the interface connected all the time when I've figured out HOW to use the software and such wink . (Did I mention I was a newbee.?)

But I'll post the problem in the correct Forum biggrin

Using the interface and software found that choosing ECU 1701 gives me readings that makes sense (well, as far as I can tell, no mechanic). ECU 1112 not so much as I was already driving 67 kpH with 0 RPM stationary on the driveway..

So guess the ECU 1701 should be my starting point to work from??

Any tips / help is appreciated.

Attached the ECU tag