by VPV-Motorracing on Fri Feb 26, 2010 5:26 am
I made some further test and now I'm 99,9% sure this is a software bug, or my unit have some problems in it.
I made a very short 100R equipped twisted cable from M400 to UTC and located it far from ignition parts -> No effect on behaviour
I configured the M400 to output special RS-232 data at 9600 baud and received it using hex-capable software. When M400 totally refuses to connect PC it simultaneously stopped sending RS-232 stream. Only after power-off-on reset it started again. This same happened even if there was no PC-connection
After some hang the Motec software said that the file in M400 doesn't match file on PC -> Flash oh the M400 has corrupted during hang
I made also some testing without ignition on; I used screwdriver or rotated engine back and forward by hand equivalent to 0-120rpm. During this test the Vortex CDI don't make any sparks so no EMI. Even with this test the system totally hangs. I also logged the trigger signal and it was something like 1-3V, so no overvoltage during this test
And finally I made again the test using 4-cylinder setup without sync-sensor. I started the engine and run it several minutes without single communication problem. During this test the signal from sensor is over the limit, about +-30V, so this overvoltage seems to be no problem. Also datalogging was very clear and correct
System don't have any high current draw systems connected, no injectors etc. Only wide band lambda option is on. Power comes from 14V LiFePo4 2.3Ah battery capable to feed 70A for 10s
What do you, Motec engineers think of this?
VPV