rusefi.com

Posted: **Fri Jan 30, 2015 12:33 pm**

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 .

Posted: **Fri Jan 30, 2015 12:38 pm**

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

Posted: **Sat Jan 31, 2015 6:04 am**

russian 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

ok

Posted: **Sat Feb 07, 2015 8:47 am**

firmware version 6707

set_engine_type 16 have problems

2015-02-07 15_33: EngineState: injection #1 @ PB9
2015-02-07 15_33: EngineState: injection #2 @ PB8
2015-02-07 15_33: EngineState: injection #3 @ PE3
2015-02-07 15_33: EngineState: injection #4 @ PE5
2015-02-07 15_33: EngineState: ignitionPins: mode OM_DEFAULT
2015-02-07 15_33: EngineState: ignition #1 @ PE14
2015-02-07 15_33: EngineState: ignition #2 @ NONE
2015-02-07 15_33: EngineState: ignition #3 @ PE12
2015-02-07 15_33: EngineState: ignition #4 @ NONE

spark 3 and injection 3,4 problems

Posted: **Sat Feb 07, 2015 12:23 pm**

The answer could be that error message in the corner:
where is second trigger signal?

please execute triggerinfo and post the results

Posted: **Sat Feb 07, 2015 5:28 pm**

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

This firmware version 6452 ok

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

Posted: **Sat Feb 07, 2015 7:17 pm**

this issue is about

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

i.e. it is ignoring your second sensor, that's a bug, and I was recently touching something close to this. Let me see...

Posted: **Sat Feb 07, 2015 7:33 pm**

That was a stupid bug, fixed in #6713.

Posted: **Mon Feb 09, 2015 3:45 pm**

I'm not sure error occurs.

Connect with TS is necessary to reset frequently.

After version default firmware ford aspire error is not very often.

Posted: **Mon Feb 09, 2015 4:27 pm**

I have just fixed the console - it should handle this error better

And MAYBE fixed the bug, at least maybe the error message would be more helpful. Please try #6737

Posted: **Sun Feb 15, 2015 10:57 am**

How can I know the command (manual) of the TS with Frankenso ?
I'm note sure you have link in somewhre.

I would like to know any command form TS, for check results.

;-x

Posted: **Sun Feb 15, 2015 4:39 pm**

I am not exactly sure what you are asking

What do you call a command in tunerstudio?

For dev console commands the only manual is http://rusefi.com/wiki/index.php?title=Manual:Software:dev_console_commands

the firmware would give you the list of all commands if you send a 'help' command, it would also print it if you input a wrong command. Just added the link to http://rusefi.com/wiki/index.php?title=Manual:Software:dev_console_commands into help command output

No documentation

That's bad. No resources to create a full documentation

Posted: **Thu Feb 26, 2015 6:40 am**

if anyone has ever tried ecu rusefi on 6A13TT galant car? can explain to me.

Posted: **Fri Mar 06, 2015 4:55 pm**

How ihis ticket http://sourceforge.net/p/rusefi/tickets/125/ is going on?

Posted: **Fri Mar 06, 2015 5:20 pm**

Tambralinga wrote:How ihis ticket http://sourceforge.net/p/rusefi/tickets/125/ is going on?

It done for your purposes of changing map sizes. See comments in the ticket for details on how configuration is defined currently.

Posted: **Fri Apr 03, 2015 10:30 am**

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"

I want example command show all config or show CLT,RPM.
I do not understand the work of TS.

Posted: **Fri Apr 03, 2015 1:58 pm**

Tambralinga wrote:I want example command show all config or show CLT,RPM.
I do not understand the work of TS.

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.cpp

CLT&RPM are all inside handleOutputChannelsCommand and config is pageReadCommand

Posted: **Mon Apr 13, 2015 9:35 am**

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

็have Error new firmware 13-Apr-2015 00:26
Dev console have command show data in fule table and ignition?

Posted: **Mon Apr 13, 2015 11:35 am**

Tambralinga wrote: 2015-04-13 16_30: EngineState: firmware error: operationMode mismatch
2015-04-13 16_30: EngineState: firmware error: operationMode mismatch

should be fixed now.

Looks like there are no commands to show tables in console right now

but there is the table editor build into dev console, have you seen it?

Posted: **Fri Apr 17, 2015 4:27 am**

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?

Posted: **Sat Apr 18, 2015 8:01 pm**

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?

Burn stops TS for a couple of seconds, that's pretty much expected behavior.

TS console can edit tables - use the icon to save changes.

Posted: **Thu May 07, 2015 7:22 am**

Now can use Know sensor?

Posted: **Thu May 07, 2015 11:15 am**

Tambralinga wrote:Now can use Know sensor?

???

Posted: **Thu May 07, 2015 4:01 pm**

russian wrote:
Tambralinga wrote:Now can use Know sensor?
???

sorry ,Knock sensor

Posted: **Thu May 07, 2015 4:48 pm**

Tambralinga wrote:sorry ,Knock sensor

this is not done yet, see http://rusefi.com/forum/viewtopic.php?f=5&t=778

Posted: **Sat May 09, 2015 7:31 am**

New firmware @8050 cann't set analog input mode in TS.

Posted: **Sat May 09, 2015 9:50 am**

Tambralinga wrote:New firmware @8050 cann't set analog input mode in TS.

input mode is now done automatically, you do not need to specify it anymore. use analoginfo to make sure it looks good

Posted: **Mon May 11, 2015 5:58 pm**

Input speed sensor pull-up or pull-down?

Posted: **Mon May 11, 2015 7:26 pm**

Tambralinga wrote:Input speed sensor pull-up or pull-down?

pull-up and op-amp in case of my hall sensor, yours could be different,

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.

Posted: **Wed Jun 17, 2015 8:43 pm**

russian wrote:
Tambralinga wrote:Input speed sensor pull-up or pull-down?
pull-up and op-amp in case of my hall sensor, yours could be different,

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.

If my hall sensor input primary input channel PC6 and secondary input channel PA5.
I can setting speed sensor PC6 or PA5?

rusefi.com

Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)

Re: Mitsubishi 4G63 and 4G92 (#6)