s300 no longer records datalogs to ecu
used to record
running v1.1.1.0
under datalog tab:
check box is checked
speed - 25hz
radio button "based on enginer parameters" selected
start conditions - 5600 rpm 88% throttle
stop conditions - 4000 rpm 200kph
tried searching but couldn't find this problem in a post already.
thanks.
matthew.
s300 no longer records datalogs to ecu
First, you should upgrade SManager.
Then check that you can datalog with the laptop.
Next, in the ECU information screen check that it reports the datalogging memory to be something other than zero.
If that looks ok, clear the datalog memory with the 'delete all' function.
Last, if things still are not working, change the start parameters to something like the brake pedal, and check that pressing the brake pedal with the engine running creates a datalog.
Then check that you can datalog with the laptop.
Next, in the ECU information screen check that it reports the datalogging memory to be something other than zero.
If that looks ok, clear the datalog memory with the 'delete all' function.
Last, if things still are not working, change the start parameters to something like the brake pedal, and check that pressing the brake pedal with the engine running creates a datalog.
Hondata
updated to v1.1.7.0.
still will not datalog.
ecu reports all memory is zero and has 20(?) free recordings.
performed delete all function anyhow.
changed parameter to brake pedal.
still no datalog.
pressed 'record' button.
nothing still.
chose parameter 'always on'
this did allow datalogging but with problems:
readings like RPM, ECT, ACT totally skewed and off the charts.
in addition the sensor readings seem to freeze and change momentarily.
the 'error code' window was throwing many CEL codes but the CEL
on the cluster never lit up.
im lost on where to go from here. everything worked fine originally.
still will not datalog.
ecu reports all memory is zero and has 20(?) free recordings.
performed delete all function anyhow.
changed parameter to brake pedal.
still no datalog.
pressed 'record' button.
nothing still.
chose parameter 'always on'
this did allow datalogging but with problems:
readings like RPM, ECT, ACT totally skewed and off the charts.
in addition the sensor readings seem to freeze and change momentarily.
the 'error code' window was throwing many CEL codes but the CEL
on the cluster never lit up.
im lost on where to go from here. everything worked fine originally.
1. I'm assuming that you re-uploaded your calibration after upgrading SManager. If not, do this first.
2. Check datalogging from the laptop (not the onboard memory). If it won't datalog from the laptop, then you don't need to diagnose the on board datalogging.
3. Check that you can upload, and the changes make a difference. eg Upload a new rev limit of 2500 rpm, and check that this works.
4. Go over your socketing carefully again and check for any potentially bad soldered joints.
2. Check datalogging from the laptop (not the onboard memory). If it won't datalog from the laptop, then you don't need to diagnose the on board datalogging.
3. Check that you can upload, and the changes make a difference. eg Upload a new rev limit of 2500 rpm, and check that this works.
4. Go over your socketing carefully again and check for any potentially bad soldered joints.
Hondata
yes sir uploaded new parameters.
i can hit the datalog button (F10) and see the sensors on the laptop, what I cant do is get the ECU to record the data based on engine parameters or based on a switch. if i choose "always on" i noticed the output display on the laptop flips out. i thought maybe because i was recording and trying to record to ECU but that wouldn't make sense because it never records even when i dont have laptop plugged in.
i can make changes to the program.
will inspect socketing.
i can hit the datalog button (F10) and see the sensors on the laptop, what I cant do is get the ECU to record the data based on engine parameters or based on a switch. if i choose "always on" i noticed the output display on the laptop flips out. i thought maybe because i was recording and trying to record to ECU but that wouldn't make sense because it never records even when i dont have laptop plugged in.
i can make changes to the program.
will inspect socketing.