RhinoPower Ltd

cosmic_splatter · Member

RE: issues with the track/Kick 1202 definition

TechSupport · Guru

I'm not permitted to publish details of the Suzuki protocols, if you give me a couple of days I will update the TP file.

randy h · Member

Rhinoman wrote:
Did you see the Rx Error count incrementing?

I did not happen to notice. I will watch for that and report back.

cosmic_splatter wrote:
What shows up in your device manager when you plug in the interface? Does it show as a com port?

I have two USB to Serial devices in my Device Manager. One for a GPS antenna, and one for RhinoView. The Prolific driver for GPS shows Com 3. The driver for the tool to interface with RhinoView shows as " USB Serial Port (Com4) "
This is on a Windows XP operating system. I am sure windows just creates the next virtual com port in sequence from the last one already in place (my GPS driver).

-- Edited by randy h on Saturday 30th of August 2014 03:57:56 PM

TechSupport · Guru

randy h wrote:
One thing did happen that I have never seen before. The Rhino Screen quit updating. I closed it and restarted it and everything seemed fine.
randy

Did you see the Rx Error count incrementing? There is a problem with the Suzuki protocol that I've seen show up on the Tech1 tool, it only occurs when trying to run the comms at full speed. I should be able to put in some code to auto-recover from that but I haven't been seeing it happen on the bench.

cosmic_splatter · Member

I tried to get it working tonight on a macintosh running parallels with Windows 7. I installed the drivers you recommended Randy, but Rhinoview still refuses to see the interface. Lower left says, "no interface detected." I tried setting baud and then connecting...no joy.

Mac Parallels is seeing the interface I believe since it is reporting. But, when I look in device manager after plugging it in, it goes to COM3 every time.

http://s957.photobucket.com/user/johnhovan/media/USB_zpsb50d773b.png.html

What shows up in your device manager when you plug in the interface? Does it show as a com port?

Any ideas?

-- Edited by cosmic_splatter on Saturday 30th of August 2014 04:41:28 AM

randy h · Member

This release worked well for me.

Status Flag for EGR and OS2 Activated are reporting well. I know OS2 activation was not reporting previously. I am not sure if EGR flag working is new or not.
CTS is reporting well. 177 F for me on my test drive.
The MAF is probably working, my test drive was at the time of day when i could not see that part of the screen well. I will watch for that or use the Data Logger next time.

One thing did happen that I have never seen before. The Rhino Screen quit updating. I closed it and restarted it and everything seemed fine. This may have just been my PC, or maybe the ambient air temp here in Arizona during the test drive: 110 F !!
I will watch for this happening in the future.

But over all I am very pleased. Full Screen on my PC now and improved data reporting. Thanks Rhinoman.

randy

TechSupport · Guru

I've released RV v1.1, this should fix the 1202 definition and the USB handler. Please let me know how you get on with this, it should be much faster as well.

cosmic_splatter · Member

ps. Is the "closed loop" address for a 1202 ecu 0x1A or 0x1B?

John

cosmic_splatter · Member

Thanks Rhinoman for the explanation!

I have my car back together and was finally able to play with tuner pro tonight with the 1202 definition file you created.

Here is what I am noticing...

1. Closed loop status defaults to "active" when I load the program and connect to the computer. It never says deactive even with a cold engine. There is no change in this value throughout the testing.

2. RPM reports 200 at idle while dash reading and rhinoview software read proper.

3. Water temp is still an issue. I tried to convert the values to Fareinheit in the definitions, so I may have changed something I wasn't supposed to.

4. IAT reports zero.

5. EGR reading is wrong. I may have done something when trying to convert to Farenheit on this value.

6. EGR status always reads off even when revving the engine. I may need the wheels moving for this value to change.

Here is a screen shot...

TechSupport · Guru

When Rhinoview was originally written TunerPro didn't support anything other than GM ALDL protocols. I used to use it only for editing maps, when TunerPro RT v5 was released I wrote definitions for the ECUs that I was working on then and I've continued to develop Rhinoview in parallel, because TP was used for tuning only the definitions don't include Fault Codes or controls. TP does have the advantage of having very good datalogging and its very customisable but you have to take some time to learn that and you really need to understand how the diagnostic link works.

Rhinoview was originally developed only for my own 8V Vitara and its been added to to support other ECUs which makes it difficult to maintain and improve. I am planning on developing a whole new software package which will support a new multi-protocol interface and I'm currently using RV as a test bed for that. The new plug and play USB interface is part of that testing, I have tested that today on the OBD1 interface of 1997 OBD2 Sidekick ECU and I'm seeing six times the data rate that I was getting with the old Virtual Com Port driver which I'm very pleased with. To put that into perspective that's around 80 PIDs per second, using a USB ELM and Palmer software I am seeing an average of 5.75 PIDs per second, so RV is running around 15 times faster. The TP definitions that I wrote test a 'smart scan' algorithm that polls the faster changing data more often than the slower changing data so it appears faster than it is and is better suited to tuning work, that scan method will also be incorporated into the new software.

cosmic_splatter · Member

Rhinoman,

What benefits does the Rhinoview offer over tuner pro software? I'm wondering why you are releasing a different version if tuner pro does everything.

Is Rhinoview better at real time?

John

randy h · Member

That is good to know. I am looking forward to the update.

randy

TechSupport · Guru

An update:

I had my main bench PSU fail but that is fixed now and I'm catching up with work. I've done a fair bit of work on the USB handler and the main software and everything seems to work quite well and I'm getting double the data rate so the screens refresh much quicker now. I've got a couple of ECU repairs to get out now so I'll be using the new version of software for testing those and if no issues arise then I should release a new build this weekend. I'm fairly sure that there is a lot more speed to come but I'll get a working version released first and then do some more tests

TechSupport · Guru

All the definitions should be in the TunerPro file, its a long time since I looked at that though because its not an ECU that has been tuned. One of the cool things about TP is that you can change the functions displayed - if you right click on a gauge or value then you will get a list of parameters. You can also create your own dashboards and monitors, its all highly configurable, it just needs a little time spent learning the software.

cosmic_splatter · Member

Rhinoman,

Do you have a spreadsheet/list of all the possible stored data locations/addresses/calls? Are all the known 1202 definitions in the 1202.adx file? Or, did you use a subset of the known values?

thanks for your help! I will have my car back together in a few days and will play with tuner pro some.

John

-- Edited by cosmic_splatter on Wednesday 20th of August 2014 11:13:59 PM

TechSupport · Guru

You will see the O2 sensor activated flag go to 'Active'

cosmic_splatter · Member

Rhinoview,

Is the "closed loop status" an ecu reported event? Or, is this calculated in the software based on several sensor readings?

thanks,

Jobn

TechSupport · Guru

TunerPro was originally developed for OBD1 GM vehicles. The xdf files are used on any ECU that can be tuned, OBD1 or OBD2. In some cases, like the early MX5/Miatas, a daughterboard is fitted to the ECU, in others, like the late 8V Vitara/Samurai and the 95 Geo Metro the EPROM is modified or replaced with an emulator.

cosmic_splatter · Member

So, XDF files are for computers whereby you can change the performance of the engine? On these old suzuki's I don't think you can change to many things...correct? I think you can reset the computer and set rpm? That's seems about all you can do.

I guess things really changed in ODB2.

John

TechSupport · Guru

The adx file is the diagnostics, xdf files are for ECU tuning. There is a guide to setting up the diagnostics here:

rhinopower.activeboard.com/t36100328/tuner-pro-v5/

The help file for RV9.1 explains what all the terms are, its located in the help folder.

cosmic_splatter · Member

Oops. I think I found an .adx file. Do i need a .xdf file?

cosmic_splatter · Member

Ok. I found it in the datastreams thread.

John

TechSupport · Guru

The 1202 definition is here:

http://rhinopower.activeboard.com/t53648850/tunerpro-datastream-files/

cosmic_splatter · Member

Thanks Rhinoman!

I found the tuner pro website, but I am not seeing a 1202 definitions file.

Can you point to a place I can find the 1202 defs?

thanks for all your help!

John

randy h · Member

Cosmic,
Rhinoman has indicated in the following thread that there is an issue with V1.0 and connecting to the interface. He indicated he will be looking into that:
rhinopower.activeboard.com/t58213893/change-display-resolution-for-rhinoview/

In the mean time, I was able to get mine to connect like this:
To successfully connect, I have to launch Rhinoview, then first set Baud Rate (even if it already says the correct rate), by clicking OK. Then I can click Connect successfully, if I perform those steps in exact order.

Also, be sure and install the different driver set for the V1.0:
http://www.ftdichip.com/Drivers/D2XX.htm

I don't know if this apply to your situation, but i thought I would throw it out there for you.

randy

-- Edited by randy h on Sunday 17th of August 2014 12:53:00 PM

TechSupport · Guru

If you're running VMware on a MAC then try TunerPro RT with the 1202 definition.

-- Edited by Rhinoman on Sunday 17th of August 2014 12:45:32 PM

cosmic_splatter · Member

Rhinoman,

Would it be extremely difficult to fix the engine cooling issue and set the closed loop flag in the .9 version?

I don't think I can run the new software using parallels on a mac.

John

TechSupport · Guru

It doesn't use a COM Port.

cosmic_splatter · Member

Which com port is it using? Does it default to com1?

TechSupport · Guru

V1.0 uses a true USB driver which auto detects the interface, it won't work with third party interfaces. I'm trying to achieve a hardware/software package that will be fully plug and play, there are quite a lot of improvements that I want to do but the limited support for ComPorts within Windows means consigning the VCP to history, Windows hasn't properly supported the serial port since 2000 and every interface that I've sold has been programmed to be compatible with the true USB driver, its just taken me a long time to release it.

cosmic_splatter · Member

Rhinoman,

I went to play around with your 1.0 software and was unable to use it. The "settings" menu appears to have disappeared. I use com3 since I'm running a virtual pc on my mac.

What happened to the settings menu where you can change com ports? Can you bring it back?

thanks,

John

cosmic_splatter · Member

Thank you! I'll be watching for updates.

John

TechSupport · Guru

I didn't make any changes to the database for the v1.0 software. I am working on an update now, I hope to have it tested by the end of this week. There is a Tunerpro datastream definition but I haven't rechecked that yet. I will check the definitions on the simulator but I also have a Vitara with a 1202 ECU coming in on Friday so I'll be able to do some live tests.

cosmic_splatter · Member

Thank you! Were these issues fixed in the 1.0 release?

Let me know if you want me to beta test when you have a new release ready. I haven't tried 1.0 yet.

I will help spread the word about your software solution! It's awesome!!

John

TechSupport · Guru

I have been made aware of issues with the definition for the Track/Kick/Vit 16V 1202 ECU. I erroneously used the definition for the never released 1995 'OBD2' ECU, I'm working on fixing that and will release a new build of RV. If you think you have problems with one of these ECUs then please contact me before replacing any parts.