Had a really shitty day today trying to get a car running
I could say its one of those days...
Laptop kept having error
wifi wouldnt connect and neptune somehow lost my license so it had to connect to internet
Got that to work got the car good enough to move across the yard.
Then switched to crome and that sht didnt work as always

I followed the setup manual and ostrich connects good but then randomly says "rtp is not connected" and other times works good

Then hulog says timed out could not connect but life tuning sidebar shows most sensors but doesnt show map sensor and tps reading is buggy as well
Neptune worked great but neptune/demon is my own ecu.

i reinstalled drivers also
Laptop is fresh copy of windows 10

So finally after all was done im ready to make some adjustments and the ****** mtx-L stopped working.
Brand new mtx-l was on the car for maybe 3 very short idle runs before .
it was calibrated and installed properly and now suddenly shows E8
At first it would calibrate and then show E8 then after second time trying to calibrate it just stays in "cal" and doesnt go anywhere from that.

 

I'm reading everywhere but don't see why I'm having this problem

 

I've used my Ostrich 2.0 and my datalogger with Crome 1.6.15 a few days ago without any problems. Running windows 7 x64.

 

is anyone else having problems with crome and windows 10?

I checked and rechecked everything again and again and it just wont connect.

it connected before for few minutes and now it doesn't

when the hulog and ostrich is plugged in I always get Microsoft runtime error

 

why are there so many issues with crome is It ostrich/hulog issue or crome issue?

if its crome issue why does he keep updating it every 6 months without fixing the issues?
makes no sense at all.

does john even talk to anyone in Honda community at all or is he just updating crome and hiding in a cave since 2009?
or is it something to do with hondata and pgmfi thing because it seems like crome died at the same time hondata got on the pgmfi and there has been no improvements in crome since then(it still has same issues as it did back then)

 

so why is crome still fucked up even though john keeps updating this crap every 6 months?

why does he even bother to update when theres no improvements or fixes?

he fixes it one time then next update something is not working again so he fixes that in next update and then the circle continues its like he is trolling everyone...

and then hes not eveninvolved in anything related to Honda and is completely gone from any online Honda forums... I don't understand what is his plan? to continue to troll from his cave?

everyone keeps saying switch to Neptune. yes its the obvious choice when youre a shop owner and you profit from people switching to Neptune or hondata.
but everyone seems to ignore that crome is still better for DYI builders who don't want to fork out 500 bucks for every Honda they own that has a basic swap in it. but again when money comes into play, somehow the DIY people get ignored again
and everyone keeps referring to crome like a separate entity like crome is just bad on its own like theres no person behind it who cant get that **** fixed for years now and to make it work without connection issues.
how ****** hard is it to fix the damn connection issues
why does Neptune work flawlessly and crome keeps having same ****** issues for years already despite being updated twice a year?

ive been following every crome manual and every walkthrough and yet my HULOG still cant connect and I get timeout every ****** time

 

I don't have issues with my Burn2, Ostrich 2.0, or Hulog... I have CROME dealer though. I use Windows 7 x64 and also have a backup laptop with Windows Vista or 2000 (can't remember - almost never use it)... I do have another laptop with Windows 10 on it, but I haven't needed to try it yet.

But I agree about what the deal is with CROME and the games... it's quite sad.

 

Moates told me to check AddDatalogging.js version but i dont see it anywhere
i finally by some magic got it to log yesterday but all the datalog numbers are wrong
the only thing it shows correctly is tps %
No tps voltage
No map
temp shows 284 degrees
Ignition shows 6 degrees
cel says its on when its not

But its logging and not timing out finally im excited lol. Pretty low expectations now ...

Maybe if all the victims of crome get together and sign a petition john cui will come out of hiding and fix the damn thing i mean its been 10 years

 

I tried using p30 basecode and p72 basecode
same result.
and I just noticed that the CEL shows ON in live tuning but not on the dash
and it shows codes for all the sensors
but the only thing it reads properly is TPS % but no voltage

 

Raver, I think you have a huge problem on the driver-software chain. Have you tried to fully uninstall Crome and Ostrich drivers?

Do you have access to another laptop running Windows 7?

 

I have but the license is for a single laptop i cant just reinstall crome on another laptop like neptune
I reinstalled everything 3-4 times

 

Are you sure? 150 bucks license gives me three licenses, for three different computers. Now I'm using two of them (principal + backup laptop).

 

it came with the laptop I don't know.
its says dealer license...all the features work.
masterlink. does your crome have that file in its directory?
AddDatalogging.js

 

most drivers don't work on windows 10, there's a 99% chance you won't get that to work.

 

what about windows 8 or 8.1?
are you talking about ftdi drivers? their webpage says they are compatible with windows 10
"2.12.10 WHQL Certified Available as setup executable"


datalogging works with Neptune/demon on same ecu and same laptop.
I'm using the drivers from HRtuning someone said to use their auto installer it works better for Neptune and crome


this is what I get from live view

 

Nope!

 

weird.
dave Blundell told me to check to make sure that file is same version as crome. but I cant even find it on the internet except in the leftovers of PGMFI...

 

that just looks like the wrong datalogger protocol. if your chip is QD2 and you're using the QD3 protocol (or vice versa) that tends to happen. Otherwise the rom is bad. There have been updates to the QDL so I would import the maps to a new rom.
I only use windows 7, every other OS is garbage anyway.

 

if it's connecting and logging, it's *probably* not your driver.