Upgraded to newest version of Crome pro - datalogging broken:

Well it's been a long time since I played with crome pro, so I broke out my laptop and started messing with a tune on my new dd ef. It has an obd1 built na b18a.

For some reason, I upgraded to version 1.6.5 and when I did, I had to put on a new authorization reg string.

Well after emailing xenocron and John cui, and going back and forth I got it along with a warning that if I needed another one I'd have to purchase it again?! :/

Anyway, for some reason I can't seem to get the datalogging to work in this version - and it was working before!

I went through all the steps again for setup:

J12 is removed
Check sum removed
datalogging enabled

In the device mgr I made sure to select com port 5 as well as in crome settings.
Crome serial protocol looks different in this version, but I tried qd2 as you're supposed to and got two error boxes on top of each other:


-------------------
Datalog error
Connection timed out
Ok
-------------------

Not connected
Could not connect to the ecu
Ok
-------------------


Here's the physical connection:




Is there a new plugin I need to download or new drivers for the hulog?

 

that happens with this crome version, happened the same 2 me

 

Give this a try; Xenocron.com Datalog with Crome Pro

Following that tutorial worked for me. I haven't had any further issues.

 

What windows version are you running?

 

Xp

And GA, I tried that already...

Going back through again to see if I missed something.

 

the problem is not with the windows , and not with the configuration, the problem is with the crome version 1.6.x that have a bug with the datalogging.

you have to downgrade it to work with datalogging

 

I am not having any connection issues with my Crome Pro version 1.6.5. I am running it right now as I am typing. Should mention that I haven't had it running in over 6 months and it fired right up without having to do a thing. I have the USB cables for both the Hulog and Ostrich hooked up, a USB wireless adapter and a USB wireless mouse. There is no version issue, if you are seeing Connection timed out and Could not connect to the ecu errors. That is a hardware or config issue.

Make sure that you unplug and plug your USB cables back in after setting the com ports. This locks the data int the system settings. I always do a restart and then go back in to device manager to make sure my com port settings were saved. I found sometimes it would reset back to default even after setting them...... It's a POS windows thing. That's why I like my MSIII and TunerStudio software...it's MAC friendly.

OP. I remember having issues at first. All I did was manually uninstall all of the FTDi (USB) drivers and then start from scratch.

 

Fuuuck.

 

Are you trying to use a Crome Gold ROM? If you are and you do not have a dealer license it will not datalog.

 

Nah man, I'm a longtime pro user.

I created a new bin and it runs the car fine, but I want to fine tune the a/f ratio and it seems that upgrading to 1.6.5 broke the datalogging somehow.

Idk if I can downgrade because wont it ask for the reg string registry again?

 

Not sure about the reg string.

In any case, you shouldn't have to change to a lower version of Crome to datalog. It is probably something simple that is being overlooked.

If you look under the help menu and click "About Crome" what do you see?

top right should have: Professional version: 1.6.5
Then down below it should have your name, usage type, in my case Home usage and then my license number.

 

you're probably using the wrong datalog protocol, try QD2. and make sure the port latency is at 1.

 

I tried all the settings including qd2 like I'm supposed to.

Latency is at 1.

 

u know i had datalogging issues on xp.
and somehow everything just started working right before i got rid of it. i was taking pictures to post on craigslist suddenly datalogging turned on and had no problems since then.

the only thing i did is download and install drivers from neptune webpage.

i also searched and tried every single trick that was available with no luck.
and i honestly have no idea why it just started working. and most likely still works since the buyer didnt say anything... wtf? i dunno.

 

Is it just me or do you only have 2 wires hooked up to the CN2 port?

 

theres 3 i can see the black wire also

 

try a new rom. otherwise, start replacing hardware.

 

Windows com port settings should be reset to default. Then change the baud rate to the highest setting. Crome seems to pick it up at 38000 or something at that rate automatically, under QD2 with the correct com port. If all else fails your datalogger cable is broken or you have forgot to add the RTP+datalogger option in the new crome 1.6 rom.

 

Thanks SoD, I'll give it another go today.

 

I still can't get it working.

I'm looking for updated drivers on xenocron's site for the hulog.

I'll start posting screen shots out of pure frustration...!

 

I am not entirely sure who makes a Hulog but the data says it Uses FTDI drivers.
You can probably upgrade it at the FTDI site.

http://www.ftdichip.com/Drivers/CDM/...0Certified.zip

If this doesn't work, you might consider ditching the Hulog and getting a Cheap TTL to USB cable off ebay they run $10 and I have had a lot of success with these on Windows XP - 7 on 3 different ECU. They don't work on Windows 8 though.

http://www.adafruit.com/products/954...FStp7AodMmsA3g

 

Do not ditch the Moates Hulog....... I have my Crome Pro 1.6.5 datalog working without issue.

You probably need to do a complete uninstall of the old FTDI drivers and reinstall the new ones. I had to do this a few years back when I was having datalogging issues with my Hulog.

Here is the FTDI driver .exe from Moates....Moates FTDI drivers I'm pretty sure it's the same thing as the link above.... Uninstall all of the existing FTDI drivers and then install the new drivers. This is what worked for me.

 

I tried another known good USB cable with the hulog, burned a new .bin with QD + rtp / checksum removed.

I tried all the different drivers for the hulog from ghost's link above.

Here's the screen shots:







The only thing I can think of is maybe there's a new QD plugin for crome 1.6.5?

Or maybe my hulog suddenly died, so I need a new 4pin to USB or other converter?

Grrrrr!

 

I just installed freelog so I could test the hulog connection:

It fails loopback test:

 

Bits per second should be at Max for first screen shot.
You need to check that Box for "SERIAL ENUMERATOR" or Click on "DEFAULT" Your advance settings are off!