Hondata

Hi all,first few posts & i am very pleased with my S300 to date.

Ive just been trying to set up a datalogging switch on the SCS input on my JDM P72.

Went out to the drags a couple of nights later after i thought i had the switch working correctly(switching the SCS input to ground to activate),tested it a couple of times,seemed fine.

When i got home,tried to download the recordings(should of been about 7x1min recordings) & found that the memory had already been filled with 20 rubbish idling recordings.

A few of the recordings were 59sec long(i assume being spiked into action by the changeover on the 1min turbo timer i have setup) & the others being 2sec(i assume spiked by the start up test signal) & 0sec(i dunno?).

Does anyone have any idea on this & how i could solve it?,I'm running out of inputs & the SCS is the last one left.

EDIT:sorry one last thing i forgot to ask,does initiating the datalog with the SCS input also put me into "set base timing" mode or does the S300 disable this once the input is assigned to datalogging?

Thanx kindly for any input
Jason

Can you post your calibration with the settings for on-board datalogging

Ok,hope i attached it right

I tested this and it works perfectly. I would double check your wiring of the switch and made sure you no longer have the wires connected to any of the original places they went (they should go only to the switch).

thanx for taking a look Spunkster,your right it works perfectly,the problem was staring me in the face the whole time,but all i could think of was ,its just a switch.

The switches i used actually have a little 12V incandescent globe in them,which i powered off another circuit then switching to ground with the datalog & launch control,to light them up & remind me that they are still on.I totally overlooked these globes the whole time,completely forgot they even existed.

Solution:a diode in the power line to the globes to stop the backfeed tripping off the datalog upon certain events.