Crome/FreeLog Help Needed
I have some questions about Crome and am having some difficulty getting FreeLog to work. I have searched and tried everything possible to resolve my issues before posting up asking for help.
I am using:
Crome 1.5.3
Freelog 1.0.93
Ostrich V1 (It has the picture of the Ostrich on it)
Hulog
I messed with this last night as well and did some reading, discovered that my J12 resistor was not cut, so I cut it and resumed today.
When I tried to get FreeLog to work today, I documented my process as I went along to help you guys hopefully help me.
So here's what's happening in Crome that has me asking questions:
I open Crome, go to settings, make sure the Comm settings match with where the Ostrich is plugged in with regards to Device Manager

Baud for ports is 9600 so I set Crome to 9600.

I hit detect connection and get Successfully connected to the ECU

Then when I click ok the baud rate automatically changes to 920000. Why does it do this and is it supposed to do this?

Just for ***** I wanted to see if Crome still connects to the ecu so I hit Detect Connection and it says successfully connected to the ECU

I click okay and toggle realtime programming toolbar, hit Read and the map in the Ostrich comes up


Now, I start the car...I am a n00b to tuning so I am unsure if this is supposed to happen, but with the car running i cannot READ or VERIFY in REALTIME without the car revving to 2000RPM and staying there...Even if I close crome it continues to idle at 2000rpm, I turn the ignition off and then start the car again to resolve this.
I have a feeling this is just my own misuse of the program. Am I right in assuming that this is happening because in all actuality what I am doing is unnecessary? I can WRITE just fine to the Ostrich with the car running and the changes occur and REALTIME works fine as well but some insight about the revving when READING or VERIFYINGwould be nice.
Now on to my biggest problem...Using Freelog
I have a P06 chipped for VTEC with 4 pin header in CN2, J12 cut
I open freelog and go to settings, I have read conflicting things in regards to Baud Rate...some say set Freelog to Port settings in device manager,
others say to select the proper comm and change settings in device manager to match existing Freelog settings, I've tried both with no luck

Loopback and Sanity check both fail...Datalogging +RTP and Remove Checksum routine have both been applied to the basemap in the Ostrich.


At this point it would seem that I have Crome pretty well figured out. Rev limit changes occur with car running etc...the only issue i am having is if I try to READ or VERIFY while the car is running, which I am assuming would happen to anybody.
I've tested with car off, with ignition on and with car running and I get failed loopback and sanity test.
I really want to get FreeLog working so I can start Datalogging. I'm not super concerned with the answers about the Crome issues I'm having but it'd also be nice to have them answered.
I am using:
Crome 1.5.3
Freelog 1.0.93
Ostrich V1 (It has the picture of the Ostrich on it)
Hulog
I messed with this last night as well and did some reading, discovered that my J12 resistor was not cut, so I cut it and resumed today.
When I tried to get FreeLog to work today, I documented my process as I went along to help you guys hopefully help me.
So here's what's happening in Crome that has me asking questions:
I open Crome, go to settings, make sure the Comm settings match with where the Ostrich is plugged in with regards to Device Manager

Baud for ports is 9600 so I set Crome to 9600.

I hit detect connection and get Successfully connected to the ECU

Then when I click ok the baud rate automatically changes to 920000. Why does it do this and is it supposed to do this?

Just for ***** I wanted to see if Crome still connects to the ecu so I hit Detect Connection and it says successfully connected to the ECU

I click okay and toggle realtime programming toolbar, hit Read and the map in the Ostrich comes up


Now, I start the car...I am a n00b to tuning so I am unsure if this is supposed to happen, but with the car running i cannot READ or VERIFY in REALTIME without the car revving to 2000RPM and staying there...Even if I close crome it continues to idle at 2000rpm, I turn the ignition off and then start the car again to resolve this.
I have a feeling this is just my own misuse of the program. Am I right in assuming that this is happening because in all actuality what I am doing is unnecessary? I can WRITE just fine to the Ostrich with the car running and the changes occur and REALTIME works fine as well but some insight about the revving when READING or VERIFYINGwould be nice.
Now on to my biggest problem...Using Freelog
I have a P06 chipped for VTEC with 4 pin header in CN2, J12 cut
I open freelog and go to settings, I have read conflicting things in regards to Baud Rate...some say set Freelog to Port settings in device manager,
others say to select the proper comm and change settings in device manager to match existing Freelog settings, I've tried both with no luck

Loopback and Sanity check both fail...Datalogging +RTP and Remove Checksum routine have both been applied to the basemap in the Ostrich.


At this point it would seem that I have Crome pretty well figured out. Rev limit changes occur with car running etc...the only issue i am having is if I try to READ or VERIFY while the car is running, which I am assuming would happen to anybody.
I've tested with car off, with ignition on and with car running and I get failed loopback and sanity test.
I really want to get FreeLog working so I can start Datalogging. I'm not super concerned with the answers about the Crome issues I'm having but it'd also be nice to have them answered.
I know that Crome Free is not capable of datalogging...that is the reasoning behind using FreeLog. FreeLog is the datalogger program. I have since upgraded to Crome Pro, but still am having difficulties datalogging. I have read,read and read some more. I'm beginning to think that my ecu might need to be replaced.
Thread
Thread Starter
Forum
Replies
Last Post




