If you recently upgraded to Crome 1.6.5 from 1.5 and your data logging just quit, doesn't work, won't function and doesn't do anything, or if you are on 1.6.5 and its not logging at all. Then read!

This experiment was tested on a fresh installed copy of:
Windows 7 64bit
Triple Core AMD at 2.99 GHZ.
8 GB of Ram
500 GB HDD

The hardware used is:
P06 Automatic- chipped to manual with an SST27SF512 Chip.
Moates OBD1 Bench Tester
USB to TTL, data logger cable using a PL2303 chipset.
GQ4X - USB chip programmer
-----------------------------------------------------------------
I installed Crome 1.5 first, loaded the serial key for Pro.
Installed the Datalogging cable and the drivers.
Changed the Baud rate of the USB cable under windows to 120000
Set Crome settings for 920000 baud rate for OBD1.
Didn't even give Crome Admin rights.
------------------------------
VIOLA!!!!! DATALOGGING!!!!
(SEE photo 1) or
http://postimg.org/image/a7pdxjb6h/
Now since it was running good I tried different settings but OBD1 was the only setting that worked and it connected every time I wanted datalogging.
----------------------------------

Now comes the Fun Part where I install Crome 1.6.5.
-Unfortunately it does not replace the Crome Folder in Crogram Files/
-Crome 1.6.5 installed somewhere else in users/NAME/appdata/Roaming
-This requires yet another serial key.
-You can take the Crome contents of 1.5 that were installed in Program files, copy and paste them over to the new directory 1.6.5 and you will still get to keep the serial key without having to input another KEY!! ***COPY but DO NOT REPLACE ANY FILES***

Issues: Could not datalog what soever even though all the hardware settings was left as it was !!
http://postimg.org/image/6vr348jfd/

----------------
Solution!
Here is the final trick to get Crome 1.6.5 to datalog.
If you copied the contents of Crome 1.5 to the Contents folder of Crome 1.6.5 ***COPY but DO NOT REPLACE ANY FILES***
The serial key will still be the same, but you get to use a different version of Crome.

I ran Crome 1.6.5 and 1.5 at the same time.
http://postimg.org/image/cxypuq7vd/

***1.6 Is on the Left side and 1.5 is on the Right side***
-As you can see 1.5 will still datalog with the settings you have, but 1.6 DOES NOTHING!
-Whatever you do no matter how many settings you change in CROME 1.6 you will never ever get to datalog....
BUT
In order to datalog you must go into windows settings and change your datalogger settings to COM PORT 1!!!
http://postimg.org/image/dh8ehqont/

Originally I had something else on COM1, so my logger became COM3
You must make sure that nothing else uses COM1 for Crome 1.6
------------

After changing to COM1 and leaving the baud rate at 38400.
These settings should work with any version of Crome with its default settings when you install Crome.
-Changing to COM1 is under Advanced Settings for your logger.
-Change baud rate to 38400
-You are done!

**1.6 is on the left, 1.5 is on the Right**
http://postimg.org/image/krzbg4fo9/

As you can see, I can now log with 1.6.5 and not have any issues even when I did not give Crome admin rights.

============================
Conclusion:
1.) Leave everything for the logger at default under windows First.
2.) Data logger must be Set to COM 1 in windows control panel
3.) Set the Bits Per Second at 38400 in windows control panel
4.) Nothing else must be using COM1 not even another version of Crome
5.) All drivers must be installed
6.) Your chip and Map must have RTP+Data logger enabled
7.) You must have Crome Pro serial Key or Gold!
8.) Ensure everything is wired up properly and good

REMARKS:
I feel that paying $150 for a buggy software with no support, or even a proper manual is bogus.

You can help me pay for this damn test by buying one of my USB dataloggers for $20 shipped. At least they are tested and proven true to work. Windows XP - 7 Only.

 

Thank you.

I will gladly purchase one of your cables.

Send me your PayPal addy.

 

Can you post a pic of the datalogger?

 

Are you setting COM1 in Crome or in the DEVICE MANAGER in Windows?

Edit...looks like you are setting it to COM1 in both. Odd, but if it works, GREAT and thanks for sharing!

 

**** I just tried it and still can't connect.

I'm going to stomp this laptop.

Brb, uninstalling and reinstalling crome.

 

Black, If you can't get it to data log and your failing that loop back test its more than likely your logger is fried or damaged. Your drivers may also be missing or corrupted.

As far as the settings go in Crome, you can leave everything at default since it picks up com 1 in version 1.6.5. I think this is a bug, because if you picked some other port it defaults back to 1 when connecting to ECU.

If you still can't get it to run you may try changing the settings in crome, but if you followed the steps to ensure that in windows control panel your logger device is set to com 1 and all the other devices have different com ports you should be able to connect to the ECU using Crome.

I have noticed that on my laptop its using Com5 but I have no other devices using any other com ports and its working. Therefore, further testing needs to be done.

 

Well GD it works with the cable you sent me and the directions above!

I had to download the drivers for the cable from prolific but that's it. Com1 wtf?!

 

Ah so that was you! I am glad you got it working. I just saw your email a little bit ago and couldn't get a hold of you since nothing would go through operamail.
I meant to say COM 1 lol

 

Crome is actually bugged and set to run on COM 1 if you did the upgrade. I couldn't get any other COM ports to run with the upgrade, But on my laptop that has just 1.6.5 WITHOUT the upgrade it will run on any port. Doing both on Crome and under windows control panel just insures that everything runs smooth.

 

SoD,

The funny thing is that I tried the hulog AND the tunerview2 output and neither worked.

The only thing that worked was your cable.

 

The TunerView may not have worked because they changed the datalogging protocol. The TunerView is only set to work with the Crome datalogging script that's FREE.

 

Wow tunerview doesn't work is just a poor excuse. Their has to be a way in order to update the tuner program with the latest protocol. I think the reason why Hulog doesn't work may be because Crome 1.6.5 doesn't support a Hulog, But it may be other reasons too since I couldn't get mine to work with an upgrade without messing around with the settings under window.

 

Not a poor excuse at all. The TunerView doesn't support any "newer protocols" for Crome since they're not public and not part of Crome FREE. That has nothing to do with Crome not working properly. I was simply specifying that since my product was mentioned in your post.

 

The Hulog doesnt have specific support in the program either...its not like John has to add a specific protocol for use with a Hulog, or my cable...or yours.

I will try and ask John to review all of this and make some changes and get a new release out ASAP.

Remember though, this was John's COLLEGE project just to make use of time...things change for people over time and life takes over especially if something isnt your main source of income.

If he didnt somewhat update things over time, then Crome would completely disappear, our options would be limited and the biggest reason HONDAS have been so popular over the years have been because of tuning options IMHO so be easy on him

 

I wasn't trying to call your product into question.

I'm just trying to get it working with the other products I've already purchased.

 

Hey what it look like