RhinoPower Ltd

TechSupport · Guru

RE: Latest news

TechSupport · Guru

I'm not intending to release the protocol for the actuators.

kostuch · Veteran Member

Are you going to describe command codes that should be send to ECU, to move actuators?

TechSupport · Guru

The ECU commands all appear to be common, so actuator controls should work on any ECU that supports that function.

fordem · Senior Member

Would this new functionality require me to do additional "discovery" to determine the addresses used by the actuators?

TechSupport · Guru

I'm hoping to release v0.9 within the next couple of weeks, its bench tested but not yet tested on vehicles.

The big change for this release is that actuator controls are included, the pics below show what it looks like:

Rhinoview Actuator Controls

The pic below shows the actuator control panel when in RPM Control mode, the target idle value shown in the monitor window is the value returned from the ECU under test.

Rhinoview Actuators

I have also fixed the flashing text problem in the FaultCode viewer

TechSupport · Guru

Rhinoview v8.6 is released. This release fixes a few bugs that weren't quite squashed in v8.5

http://www.rhinopower.org/Rhinoview/release/Rhinoview.zip

TechSupport · Guru

v8.5 released

TechSupport · Guru

Rhinoview v0.84 is released

TechSupport · Guru

RE: Latest news

TechSupport · Guru

v0.83 is released, support for 16V models is improved.

http://www.rhinopower.org/Rhinoview/release/Rhinoview.zip

-- Edited by Rhinoman on Thursday 19th of May 2011 09:16:06 PM

TechSupport · Guru

The settings should be saved automatically when you close RV. There is a file called Rhinoview.ini in the bin folder, ini is a standard Windows configuration file and is a text file so you can open to examine what it contains using Notepad or similar. If its not saving its settings properly then let me know and I'll take another look at it.

I'm already working on v8.23 and have changed the code for the dataviewer so it switches the display between MAP/MAF/VAF, both VAF and MAF will be titled AFM but the units are different.

Cheers

James

TheZuke · Member

Maybe I'm ignorant on saving settings so when I (re-)start RV8v2

I don't have to reset the ECU ID, Comm port and speed each time?

Or is it something for the your RV to do list?

Thanks, its a nice piece of software!

TechSupport · Guru

Rhinoview v0.82 Released

fordem · Senior Member

RE: Latest news

TechSupport · Guru

I've found and fixed a bug in the fault code viewer, an update will be released tomorrow.

TechSupport · Guru

v0.81 released

TechSupport · Guru

Latest news

TechSupport · Guru

The main fault code registers are usually located at the first four addresses, 0 to 3. they can be considered as two 16-bit words, addresses 1,0 are the current faults and 3,2 are the stored faults. Below are bit definitions for the 1112 ECU, you can see that each bit represents a fault code and these defined in descending order.
The 1112 ECU has a California variation and hence has an extra register at address four which contains the breakdown of the California specific codes, omodels may also have extra registers for immobiliser functions etc..
Note that the scantool can access more fault codes than using the Check Engine Light method (i.e. Code 38 = faulty CEL!).

Address 1 (current faults)

Bit7 - GND Circuit (Code 53)
bit6 - EGR             (Code 51)
Bit5 - Idle Switch (Code 45)
Bit4 - Idle Switch (Code 44)
Bit3 - CMP            (Code 42)
Bit2 - IFS             (Code 41)
Bit1 - MAP Low     (Code 32)
Bit0 - MAP High    (Code 31)

Address 0 (current faults)

Bit7 - IAT Low (Code 25)
bit6 - VSS        (Code 24)
Bit5 - IAT High (Code 23)
Bit4 - TPS Low (Code 22)
Bit3 - TPS High (Code 21)
Bit2 - WTS        (Code 15)
Bit1 - WTS        (Code 14)
Bit0 - O2 Sensor (Code 13)

Address 2 (stored faults)

Bit7 - IAT Low (Code 25)
bit6 - VSS        (Code 24)
Bit5 - IAT High (Code 23)
Bit4 - TPS Low (Code 22)
Bit3 - TPS High (Code 21)
Bit2 - WTS        (Code 15)
Bit1 - WTS        (Code 14)
Bit0 - O2 Sensor (Code 13)

Address 3 (stored faults)

Bit7 - GND Circuit (Code 53)
bit6 - EGR             (Code 51)
Bit5 - Idle Switch (Code 45)
Bit4 - Idle Switch (Code 44)
Bit3 - CMP            (Code 42)
Bit2 - IFS             (Code 41)
Bit1 - MAP Low     (Code 32)
Bit0 - MAP High    (Code 31)

Address 4 (current faults)

Bit7
bit6
Bit5
Bit4
Bit3
Bit2 - EGRT Open cct (Code 51)
Bit1 - EGRT Short cct (Code 51)
Bit0 - EGR                  (Code 51)

There are a number of codes (like 51) which break down into more than one fault and other codes that have more than one definition, often petrol v diesel, because of this I have defined each specific fault code a function number.
In the configuration folder each address is broken down into bits and each bit is defined a function. If a bit doesn't appear to have a function then it should be allocated the function number 55. If this appears in the fault code display then it means that there is an unrecorded fault code and further investigation is required.

TechSupport · Guru

I need to produce a help file but I am probably going to have to change the format of the datastream file to allow me me introduce selective polling. Currently the effectiveness of logging is limited by the slow poll rate, being able to turn off unneeded address will allow other addresses to update faster.
The datastream format is explained elsewhere, in the datastream file the addresses of the fault code registers are allocated to functions called 'Fault Codes(1)' through to 'Fault Codes (5). In the faultcodes file each function 'Fault Codes (n) is broken down into individual bits, each one of which represents a fault code.
I'll put together a document that explains that better.

I confess that I have only run this on the simulator, the Vit is still in storage and I need to add the configuration for the Baleno.

Editted: ECU ID 0000 doesn't need to be used if your ECU is already defined in the datastream.csv file.

-- Edited by Rhinoman on Monday 7th of March 2011 08:23:48 PM

fordem · Senior Member

How do I configure the faultcodes - perhaps a readme file should be included in the archive with the configuration instructions for both the faultcodes & the datastream.

I did a copy & paste of the faultcodes for the 1112 ECUID and renamed the new column 1902 to match my ECU and then forced an IAT error but the display wouldn't show anything.

TechSupport · Guru

Rhinoview v0.8 is released. New features are:

Fault Code Viewer
Configurable sample rate
Reduced timeout on bad data
Additional parameters added including EGR temp for California models
Ability to reset ECU/clear fault codes

The fault code viewer uses a new configuration file, faultcodes.csv. This is located in the bin directory and can be editted using Excel or similar, currently only the 1112 ECU is defined.
The old rhinoview.csv configuration file that defines the diagnostic address has been renamed datastream.csv. There are a couple of added parameters and the maximum number of addresses can be defined, previously the software polled a fixed number (50) of addresses. This change makes polling a little faster on ECUs that use fewer addresses.
The status bar has a new field that shows the bad data count, the Comms menu includes a new setting for sample rate. To optimise the polling rate the sample rate can be reduced until just before the ECU starts showing bad data being received.
The timeout on a communications failure has been made proportional to the sample rate so that the apparent screen freezing is greatly reduced. Note that any sample rate can be typed into the box. Rhinoview reads four addresses at a time so at a sample rate of 100ms, forty addresses a second will be read which means that for most ECUS any one data parameter will be refreshed at an interval of a little under one second.

TechSupport · Guru

I pulled the DTC (fault code) display a couple of issues ago because I wasn't too sure about the function of some of the registers. I've now done an analysis of the fault code flags on the 56B series of ECUs, two of the 'extra' registers are 'history' flags, the ECU logs faults to these registers and they are kept until the fault codes are cleared or the ECU is reset.
The last register is a 'California' register which flags faults with the EGR temperature sensor - note that the Check Engine Light codes do not differentiate between an EGR fault or an EGRT fault, they are all included in Code 51.
Code 42 which is only available through the CEL while cranking is retained in the history.
The Fault Code display will be restored in the next release, there are, as always, likely to be mapping differences between ECU series so a seperate config file will be used. This config file will also hold the mapping data for the status registers a display for that is also work in progress.

1112 ECU DTC Summary:

Address 00 - Current
7 - IAT Low   (Code 25)
6 - VSS          (Code 24)
5 - IAT High   (Code 23)
4 - TPS Low   (Code 22)
3 - TPS High (Code 21)
2 - ECT          (Code 15)
1 - ECT          (Code 14)
0 - O2S         (Code 13)

Address 01 - Current
7 - GND Cct   (Code 53)
6 - EGR          (Code 51)
5 - Idle Sw    (Code 45)
4 - Idle Sw    (Code 44)
3 - CPS          (Code 42)
2 - IFS           (Code 41)
1 - MAP Low  (Code 32)
0 - Map High (Code 31)

Address 02 - History
7 - IAT Low   (Code 25)
6 - VSS          (Code 24)
5 - IAT High   (Code 23)
4 - TPS Low   (Code 22)
3 - TPS High (Code 21)
2 - ECT          (Code 15)
1 - ECT          (Code 14)
0 - O2S         (Code 13)

Address 03 - History
7
6 - EGR          (Code 51)
5 - Idle Sw    (Code 45)
4 - Idle Sw    (Code 44)
3 - CPS          (Code 42)
2 - IFS           (Code 41)
1 - MAP Low  (Code 32)
0 - Map High (Code 31)

Address 04 - Current
7
6
5
4
3
2 - EGRT O/C (Code 51)
1 - EGRT S/C (Code 51)
0 - EGR         (Code 51)

Grimreefer · Member

Hey Rhinoman, Congrats on the job, we all know you will use the leassons learned to produce a great product. I know the forums users will be heard within your projects, even if it's paddle stick control on a vit or a SJ

Will pull RV tonigh and play this weekend, would you like a mirror over here?
Glad the GF on insurace list, been trying to get my lady to drive while i document but she thinks i can 'drive via wire' so is not willing to hand over to a nerd in the passenger just seat yet, everyone elese stops at the bar along the way

Does this mean the GF gets a vit of her 'own' soon ? or did i just sink a battle ship there ?
Update me one the MCu project when you can.
Grim

TechSupport · Guru

Temp scaling may be off, I did a bunch of tests but there may have been a problem. I think that RV may have been displaying the value in F but showing C on the gauge. There is also a problem with the MAP which I've fixed but haven't tested.
TPS is probably swapped angle/volts in the config file, it was changed at one point.
Inj PW I will check out also, its not showing on the Baleno either but the config file wasn't complete.
I will do a lot of testing this weekend, the GF is insured to drive the Baleno so I can sit in the passenger seat with the laptop.

fordem · Senior Member

Running 0.7 with no changes to the config file - I get the following ...

a - temperature scaling is off - IAT indicates 102F on an 86F day - ECT indicating 171F
b - tps scaling off - shows 34% with throttle closed.
c - no injector pulse width displayed,
d - mpg shows a figure with ignition on/engine off, increments until full scale is reached.

I can probably fix the temp scaling by playing with the gain & offset values, but the config file entries for b & c seem match what I've been using all along, and worked at least up to the 0.5 version.

Maksut11 · Newbie

It would be good smile

TechSupport · Guru

It should be possible to write a plug-in, the main code from Rhinoview would be portable but the gauges are custom library functions and might be more difficult.

Maksut11 · Newbie

Whether and it is possible to make a plug-in for Centrafuse 2.1? Because at me in the car CAR PC.

-- Edited by Maksut11 on Sunday 31st of October 2010 08:07:29 AM

TechSupport · Guru

All of the Suzuki ECUs that I've looked at have the same scaling factor for battery voltage, is yours different? can you post, or email me, a picture of the circuit board?
Thanks
James

Maksut11 · Newbie

Many thanks for the program Rhinoman. I badly speak on English. Nevertheless I need her. Also would like to ask to add in the program scaling factors for Battary V. At me Suzuki Baleno 1998 1.3 16Valve ECU 1453. Germany.

-- Edited by Maksut11 on Saturday 30th of October 2010 08:21:33 PM

TechSupport · Guru

I've released version v0.7 which has the temperature C/F switch fixed and also has MPH/KPH selectable. Additional functionality has been added to the DataLogger and the Dataviewer. The config file has changed again to add some extra functions.

http://www.rhinopower.org/Rhinoview/release/Rhinoview.zip

TechSupport · Guru

The config file should have been correct, I thought that I had incorporated all your feedback. the main changes with v0.6 are the MAF/MAP switch and the filter constant for the MPG display which is the number of samples over which the reading is averaged.
The temp scaling problem I mentioned in my post below, I will look at that today.

fordem · Senior Member

OK! ...

First - I do need to sit down and look at the changes made to the config file structure - and make sure I have the correct entries, I basically did a copy & paste of the 1902 column from the 0.5 config file to the 0.6 file, and adjusted the scaling factors by hand, however my time schedule may not allow that before Sunday.

There is possibly a quirk in the temperature display routines - when farenheit is selected, the gauge display still shows C, and the coolant temp full scales at 120* - I had a centigrade display of 71*C which would translate to 159*F, which sounds about right for the actual engine temp (I didn't measure it), but if the display is set to farenheit, I get a full scale on the analog and 120* on the digital.

TechSupport · Guru

Good point. I'm going to restore the fault code page in the following release but currently there are only a couple of ECUs for which the fault code fields have been decoded. For the next release the raw data will be displayed in the DataViewer, I will also add options to clear the fault codes and to reset the ECU.
Status fields need to added as well but few of those are decoded either, hopefully with full logging capabilites they will be easier to decode, those will added in a staggered release in the same way that the fault codes.

fordem · Senior Member

If I recall correctly there is nothing that shows the CEL codes - maybe a CEL display window or page (a window might require a scroll bar if there are multiple codes).

TechSupport · Guru

I'm already working on the next release, so far the improvements are:

Improved data transfer between objects which removes some bugs, particularly in the dataViewer.
I've added a timestamp to the log file
Saving to file is optional
Logger settings are retained

Still to implement:
add more functions to the datalogger and dataviewer
fix some bugs in the temp C/F switching
fix the MPH/KMH switching

any more?

-- Edited by Rhinoman on Tuesday 26th of October 2010 12:08:39 PM

fordem · Senior Member

OK - that works.

I probably won't get much chance to do anything with it for the next week or so - as I'm in the middle of installing kitchen cabinets this week, and as soon as I'm through that I'm off to Trinidad to attend my daughter's convocation - she graduates with a masters in coastal engineering & management on Thursday.

TechSupport · Guru

oops, try here:

http://www.rhinopower.org/Rhinoview/release/Rhinoview06.zip

fordem · Senior Member

I get a file not found error

TechSupport · Guru

Rhinoview v0.6 is available for anyone that wants to test it. Please note that I haven't as yet tried this on a vehicle!

Latest features are:

Datalogging to file - yes its finally arrived and may even work!
Improved support for models with a Mass Air Flow meter - MAF voltage only.
Improved polling routine should give faster data updates
New configuration file allows mpg averaging to be adjusted by the user
Maybe even some other things I've included in the last 8 months and forgotten about!

http://www.rhinopower.org/Rhinoview/release/Rhinoview06.zip

-- Edited by Rhinoman on Monday 25th of October 2010 04:43:49 PM

fordem · Senior Member

Thanks much for the work done, I really do appreciate it.

TechSupport · Guru

TPS reverts to 255 every time I reopen the project, thats a bit of a head scratcher. As a temporary measure I've put in a work around to set it to 100 in the initialisation code.
Currently the software polls every address, I will be implementing selective polling where you will be able to turn off unwanted addresses, that will increase the refresh rate quite a bit. Unfortunately if the polling rate is too fast the ECU comms port will crash.
I've got a few other jobs to concentrate on and I'm going away next week so I don't anticipate any more updates for a few weeks.
Thanks
James

fordem · Senior Member

TPS still does not indicate full scale when saying 100%, mpg works now - but - it might benefit from some sort of smoothing or averaging (or maybe a faster refresh rate, if that's possible).

In light traffic the display can be very erratic - jumping from low numbers to high numbers, seemingly at random - I say seemingly, but I know there is nothing random about it - holding position in a stream of traffic requires constant small variations in throttle position, and this translates in to suprisingly large variations in the fuel being injected - going from rolling on a trailing throttle to just a slightly open throttle can change the pulsewidth from what is essentially an idling engine (2.4 in my case) to perhaps two or three times that.

Get out onto an open road where you can hold a steady speed and it will display a nice steady reading - slightly optimistic in my opinion, but if necessary that can be corrected by varying the flowrate in the config file.

fordem · Senior Member

Thanks much - I'll download now and try it in the morning.

Regarding that 21 mpg and it being low, I'm not disagreeing with you, but I don't think it's too far from where it should be - as far as I know the J20A engined GV is not that economical a vehicle, especially in and around the city.

TechSupport · Guru

I've just uploaded a modified executable.
The TPS should be OK now, max scale was set to 255, the MPG gauge also had a wrong max. scale (18).
There was a problem with a value being rounded down to zero in the MPG calculations, that should also be fixed now. For the values that you gave me I get around 21mpg, this seems a bit low but I suspect that that is because the injector PW time includes dead time so you will need to tweak the injector flow rate to compensate. Hopefully this will all be OK now, I tested the code in a test programme and then cut and paste.
Save to file isn't implemented yet.
Cheers
James

-- Edited by Rhinoman on Monday 1st of February 2010 11:02:24 PM

fordem · Senior Member

2500 rpm in 4th gear gives approximately 40 mph - driving into the wind with 12~16% throttle - the indicated injector pulsewidth varies between 4.5~5.5, shows around 5.0 most of the time - the same road travelling in the opposite direction a few minutes later (so the wind is behind us) and we can hold the same speed with a hair less throttle 10~14%, and a wee bit less fuel used - indicated pulsewidth is between 2.0~4.0, indicating 3.6 most of the time.

What email address do you want the config file sent to?

Oh - I tried using the data logger to capture the details - set it to get VSS on the first channel, rpm on the second and pulsewidth on the third, but it doesn't seem to let me save it to a file.

Edit..

I forgot to mention - when the vehicle is in motion both the analog and the digital sections of the mpg gauge indicate zero - when it's on the overrun and in fuel cutoff, the analogue mpg gauge goes full scale, but the center digital display says 18 mpg.

-- Edited by fordem on Monday 1st of February 2010 07:50:36 PM

TechSupport · Guru

fordem wrote:

I was using the latest config file - although what I did was copy and paste the "1902 column" from the previous release as a quick & dirty way of keeping the existing the address/function mappings.

I'm about to make a quick trip out so I'll get some numbers and report back shortly - you're asking for INJPW and injector pulsewidth - does this mean you want the actual pulsewidth off of the scope?

That was a typo, I've editted it to only ask for one inj PW reading. Can you please send me your updated config file so I can update the master copy
Cheers
James

fordem · Senior Member

I was using the latest config file - although what I did was copy and paste the "1902 column" from the previous release as a quick & dirty way of keeping the existing the address/function mappings.

I'm about to make a quick trip out so I'll get some numbers and report back shortly - you're asking for INJPW and injector pulsewidth - does this mean you want the actual pulsewidth off of the scope?

That could be a bit of a problem, as right now I can only run the scope off of AC power - the battery is dead.

TechSupport · Guru

You do need to use the latest config. file. I will look into the TPS problem, I probably failed to change the max, displayed value from 255 to 100.
Can you give me some approx values for RPM, MPH and injector pulsewidth at some constant speed, say, 30mph. I can then plug those values into the algorithm and see where its going awry
Cheers
James

-- Edited by Rhinoman on Monday 1st of February 2010 04:59:14 PM