russian wrote:Not sure what you mean here do not understand what is this question about
get_int command? set_int command?
I want show offset TS or command for show all offset for file rusefi.ini .
russian wrote:Not sure what you mean here do not understand what is this question about
get_int command? set_int command?
okrussian wrote:this is probably close to what I am planning to finish maybe today or tomorrow - https://sourceforge.net/p/rusefi/tickets/125/
the tool I am working on would be making all the offsets in the configs, that would allow you to get 16x32 table you are looking for relatively easy
Code: Select all
2015-02-08 00_14: PortHolder: Sending [sec!11!triggerinfo]
2015-02-08 00_14: EngineState: confirmation_triggerinfo:11
2015-02-08 00_14: EngineState: Template Mi4G93 (16) trigger TT_MITSU (11)
2015-02-08 00_14: EngineState: trigger#1 event counters up=4843/down=4844
2015-02-08 00_14: EngineState: expected cycle events 4/8/0
2015-02-08 00_14: EngineState: trigger type=11/need2ndChannel=No
2015-02-08 00_14: EngineState: expected duty #0=0.37/#1=0.38
2015-02-08 00_14: EngineState: isError Yes/total errors=2421 ord_err=1/total revolutions=2421/self=No
2015-02-08 00_14: EngineState: gap from 1.24 to 2.08
2015-02-08 00_14: EngineState: sn=Yes ignitionMathTime=2049 schTime=1188 triggerMaxDuration=228510
2015-02-08 00_14: EngineState: maxLockTime=39600 / maxTriggerReentraint=0
2015-02-08 00_14: EngineState: maxEventQueueTime=37698
2015-02-08 00_14: EngineState: primary trigger input: PC6
2015-02-08 00_14: EngineState: primary trigger simulator: PD1 OM_DEFAULT freq=1200
2015-02-08 00_14: EngineState: trigger error extra LED: NONE OM_DEFAULT
2015-02-08 00_14: EngineState: primary logic input: PA8
2015-02-08 00_14: EngineState: secondary logic input: NONE
Code: Select all
2015-02-08 00_35: EngineState: isError No/total errors=1 ord_err=1/total revolutions=209/self=No
2015-02-08 00_35: EngineState: gap from 1.24 to 2.08
2015-02-08 00_35: EngineState: sn=Yes ignitionMathTime=2045 schTime=1165 triggerMaxDuration=228525
2015-02-08 00_35: EngineState: maxLockTime=38921 / maxTriggerReentraint=0
2015-02-08 00_35: EngineState: maxEventQueueTime=37828
2015-02-08 00_35: EngineState: primary trigger simulator: PD1 OM_DEFAULT freq=1200
2015-02-08 00_35: EngineState: secondary trigger simulator: PD2 OM_DEFAULT phase=6
2015-02-08 00_35: EngineState: 3rd trigger simulator: NONE OM_DEFAULT
2015-02-08 00_35: EngineState: trigger error extra LED: NONE OM_DEFAULT
2015-02-08 00_35: EngineState: primary trigger input: PC6
2015-02-08 00_35: EngineState: secondary trigger input: PA5
2015-02-08 00_35: EngineState: primary logic input: PA8
2015-02-08 00_35: EngineState: secondary logic input: NONE
i.e. it is ignoring your second sensor, that's a bug, and I was recently touching something close to this. Let me see...2015-02-08 00_14: EngineState: Template Mi4G93 (16) trigger TT_MITSU (11)
2015-02-08 00_14: EngineState: trigger#1 event counters up=4843/down=4844
2015-02-08 00_14: EngineState: expected cycle events 4/8/0
2015-02-08 00_14: EngineState: trigger type=11/need2ndChannel=No
2015-02-08 00_14: EngineState: expected duty #0=0.37/#1=0.38
2015-02-08 00_14: EngineState: isError Yes/total errors=2421 ord_err=1/total revolutions=2421/self=No
It done for your purposes of changing map sizes. See comments in the ticket for details on how configuration is defined currently.Tambralinga wrote:How ihis ticket http://sourceforge.net/p/rusefi/tickets/125/ is going on?
Code: Select all
pageIdentifier = "\x00\x00"
pageReadCommand = "R\x00\x00%2o%2c"
burnCommand = "B\x00\x00"
pageActivate = "P\x00\x00"
pageValueWrite = "W\x00\x00%2o%v"
pageChunkWrite = "C\x00\x00%2o%2c%v"
you should read the source code - https://sourceforge.net/p/rusefi/code/HEAD/tree/trunk/firmware/console/binary/tunerstudio.cpp & https://sourceforge.net/p/rusefi/code/HEAD/tree/trunk/firmware/console/binary/tunerstudio_io.cppTambralinga wrote:I want example command show all config or show CLT,RPM.
I do not understand the work of TS.
Code: Select all
2015-04-13 16_30: EngineState: TunerStudio size=196 / total=1017 / errors=0 / H=0 / O=0 / P=273 / B=0
2015-04-13 16_30: EngineState: TunerStudio W=0 / C=0 / P=0 / page=0
2015-04-13 16_30: EngineState: page size=15288
2015-04-13 16_30: EngineState: Sending 256 done
2015-04-13 16_30: EngineState: READ m=1 p=0 o=8448 c=256
2015-04-13 16_30: EngineState: TunerStudio W=0 / C=0 / P=0 / page=0
2015-04-13 16_30: EngineState: firmware error: operationMode mismatch
2015-04-13 16_30: EngineState: firmware error: operationMode mismatch
2015-04-13 16_30: EngineState: firmware error: operationMode mismatch
2015-04-13 16_30: EngineState: firmware error: operationMode mismatch
2015-04-13 16_30: EngineState: firmware error: operationMode mismatch
2015-04-13 16_30: EngineState: firmware error: operationMode mismatch
2015-04-13 16_30: EngineState: firmware error: operationMode mismatch
2015-04-13 16_30: EngineState: firmware error: operationMode mismatch
2015-04-13 16_30: EngineState: firmware error: operationMode mismatch
2015-04-13 16_30: EngineState: firmware error: operationMode mismatch
2015-04-13 16_30: EngineState: firmware error: operationMode mismatch
2015-04-13 16_30: EngineState: firmware error: operationMode mismatch
2015-04-13 16_30: EngineState: firmware error: operationMode mismatch
should be fixed now.Tambralinga wrote: 2015-04-13 16_30: EngineState: firmware error: operationMode mismatch
2015-04-13 16_30: EngineState: firmware error: operationMode mismatch
Burn stops TS for a couple of seconds, that's pretty much expected behavior.Tambralinga wrote:Ok
The problem now is to write data the TS.It will stop for 10 seconds if Brun program.
Dev console :can not edit table?
???Tambralinga wrote:Now can use Know sensor?
sorry ,Knock sensorrussian wrote:???Tambralinga wrote:Now can use Know sensor?
this is not done yet, see http://rusefi.com/forum/viewtopic.php?f=5&t=778Tambralinga wrote:sorry ,Knock sensor
input mode is now done automatically, you do not need to specify it anymore. use analoginfo to make sure it looks goodTambralinga wrote:New firmware @8050 cann't set analog input mode in TS.
pull-up and op-amp in case of my hall sensor, yours could be different,Tambralinga wrote:Input speed sensor pull-up or pull-down?
If my hall sensor input primary input channel PC6 and secondary input channel PA5.russian wrote:pull-up and op-amp in case of my hall sensor, yours could be different,Tambralinga wrote:Input speed sensor pull-up or pull-down?
My VSS hall sensor uses same exact circuit as your your shaft position hall sensor: pull-up, then op-amp, then op-amp output is traced to VSS rusEfi pin which is PA8 in my case.