I suddenly started having datalogging and map tracing issues.
Specs:
Crome pro 1.6.3
Hulog
Ostrich 2.0
Chipped p28
j12 cut
Laptop running vista

Yesterday everything was working fine. I did some street tuning/datalogging and worked on the map last night. Upon connecting to the car today, the map tracing and datalog will not work. I can read and load from the ostrich, and the car runs flawlessly. I can start datalogging, but it only shows strange values that dont change (ie. Tps -12%, boost like 6543532 or so, battery voltage like 6.4). When I turn the car off it says connection lost and goes away.

Things I've tried:
Rechecking com ports, uninstalling drivers, driver cleaner from moates.net, crome uninstall and reinstall, and even tried another working ecu to check and the values stay the same. I also checked each separately as well.

I'm leaning toward laptop computer/hardware issues, but I cannot believe both went bad at once.

Anyone got any suggestions?

 

Screenshot of the values and .bin file for reference.

 

Try a different data loging cable, check solder joints, maybe the cables upside down?

 

The soldering in the ECU looked fine, I even tried a second chipped ecu with the same results. Today I formatted my computer and reinstalled crome. I had to burn one of my crome licenses to do it. Same issues, so I'm contacting Moates.net to see if there are any troubleshooting for it.

The car is running great, but it's kinda frustrating fixing one thing only to have another issue come up.

 

What are your COM Port settings in Device manager and Crome?

Xenocron Moates Datalog Settings

 

Thanks for the link, but i had already had it up and tried it. I used the virtual terminal and jumper test as well. I ended up doing a rma and sending it back to moates.

 

I have just joined this forum to try and fix this exact problem.
When I read your symptoms, I know it's EXACTLY the same problem, cause even the random values ste the same. weird hey?

Anyhow, I'll work my easy through the fixed listed thus far.

I was kinds under the impression that if I was able to read and write to the demon, then the days logging should work fine. But NO.....!

 

Are you using the Moates Demon or the Hulog?

This thread is concerning issues with using the Hulog not the Demon. However, that being said. I think there is a current thread here discussing similar issues using the Demon with Crome vers 1.6.* as well. You might want to see if you can search for that thread for more specific help.

 

True, I'm using the demon. But as I said, I'm getting the same random values.
16.5 BTC etc. makes me wonder if it's the same problem.

 

From what I recall Crome had a few compatibility issues with the Moates Demon. You would probably get better results checking pgmfi.org for answers.

The ops issues where strictly hardware related and yours could be software to hardware compatibility issues.

Are you using Crome Free or Crome Pro?

 

Pro. Noob, but not that noob. LOL

I'm swapping the ECU for a P72 with a Hondata S300 anyhow, but the demon will be going into another project, so I'd like to figure this out.

Just seemed to much like the same problem to me....

 

OK then! I would imagine that your best bet would be to contact the boys @ Moates.net or Xenocron.com. I'm sure they will be able to help you out.

 

I received my new Extreme Hulog in the mail today, and I am still having the datalog issue.

Things I have tried:
Reinstalling drivers for Moates devices,
Driver cleaner and reinstall
Formatting laptop and reinstalling crome (burned one of my licenses)
tried a second working ecu
returned the Hulog and got a new one

The datalogging was working and and allowed me to tune the basemap, but I cannot refine/finish the street tuning and am getting really frustrated.

Is there anything else that I can try?

 

A new ROM, or different Datalog Serial Protocol (i.e. Crome QD2). This usually happens when you're using an old ROM version with Crome 1.6.3, or the wrong datalog plugin if you're running a P30/P72 base.

 

I'm also beginning to think that It might be my laptop as well. It was fine one day and non functional the next. I'll give a new rom a try.

 

Well I feel like a tool now. I created a new P30 map from crome and uploaded it to the ostrich and it started datalogging again. I have been migrating my fuel values over to the new base P30 map. I took it for a couple test drives today and it works great.

Thanks for the help.

 

Same problem talk to my tuner he said use a p30 basemap and click plugins and remove checksum routine and click wuickdatalogger +rtp and that’s it!!

 

Interesting. In the almost 10 years I’ve tuned with Crome I never bothered getting data logging to work but I’ll have to give it a shot using a p30 basemap and see if it works.