rusefi.com

I'm trying to set up my car in TS and questions about what things mean come up...

In general:
- I would have all pins default to "NONE" instead of PA0.
- In many cases the name of the menu point differs from the name displayed on the window. This confuses me....
- Pin mode usually offers "default", "default inverted", "open" and "open inverted". What do they mean?
- Fuel correction coefficients: There are a plethora of fuel correction coefficients. But how do they modify fuel? Are they a multiplier for pulsewidth (100% means unmodified PW), or are the additive (0% means unmodified PW)?

Specifics:
1. Engine
1.1. Base Engine Settings
- two wire wasted ignition settings: What does this mean?
- debug mode: I assume that puts some debug output on the console- correct? Could use an option to disable

1.2. Trigger configuration
- under "Settings Trigger": "use only front": meaning?
- under "Settings IO": Primary and secondary channel: which is Cam, which is Crank? I assume Cam is primary.

1.3. Injection settings
- Injector Open Time (msec). I assume this is "Dead Time". I suggest to rename to Dead Time since that's also used in the table on the right
- phase offset: what's that?
- Injector Dead Time Battery Correction: value appears to be ms/V. So if my Dead Time at 13.6V is 1.36ms (which happens to be the case for my injectors) it would be 0.10ms/V at 13.6V? If so, why do we need "Open Time" at all? Or is this an adder/multiplier for "Open Time"?

1.4. Ignition settings
- My car definition is set to 4 cylinder, wasted spark. But in ignition settings I get to fill out 4 of the 6 ignition pins. What are they? I'm only using two pins with WS.

(as an aside here, the pinout table https://docs.google.com/spreadsheets/d/1G8olOoZOSNjRBk2r0EeqKDDZw9X7n2TUZjAuxP7xtkA/edit#gid=0 shows 3 ignition/spark output pins and 5 injectors. Somebody must have built one weird-as-hell engine!)

1.5. MAP Sensor Settings
- You can enter MAP at minimum and at maximum voltage, but you can't enter those voltages. 0V-5V as standard?

1.6. MAF Sensor
- I'm not running MAF, so don't care personally, but there's no way to select a pin.... Never mind, found it further down the line under "Other Inputs" - could use a relocation.

1.7. Battery and Alternator Settings
- Battery Input Divider Coefficient(coef). Did you have a German name that one? And what does it do- is it a multiplier?
- PID control: dTime. Is that how often the loop runs?

1.8. Speed Sensor
- Is that ADC? Most speed sensors I know are VR or Hall sensors, so this appears to be somewhat useless....

1.9. Tach Output
- What is "Rise at trigger Index"?

1.10. Other Inputs
- TPS. How do I calibrate this?
- Baro ADC: Same: How do I calibrate?
- The two coefficients are presumably for calculating baro correction- correct?

1.11. MIL settings
- Don't know what MIL is.....

2. Tuning
2.1. General
- Difference between MAP and Speed-Density?
- I can select a "Sensor Chart", but don't know, what they are, or where they are to be entered

2.2. Cranking duration correction
- Looks like this should be some sort of taper? Maybe from 100% at 0 events down to 50% or so at 100 events?

2.3. Warmup AFR correction
- Are we correcting target AFR here? Or PW?

2.4. Warmup AFR auto correction
- A PID doing exactly what? (I'm not really currently interested in this. Manual correction is fairly trivial except for accel enrichment under warmup conditions)

2.5. Coolant based target AFR
- Doesn't really make sense, since we have a 3D target AFR table. We'd need a coolant-temp based table modifier....

2.6. Target AFR table
- Is this actually used in the fueling calculation? I.E. If I change target AFR during my tuning from 10 to 9, does the ECU automatically know to inject 10% more fuel?

2.7. Ignition IAT correction
- Y-Axis reads "Intake Load". Is that IAT in ºC?

I think that's it for now. Please note that I don't expect answers to all these points in a single post!!!

I've created https://sourceforge.net/p/rusefi/tickets/273/ just to not forget to resolve all these questions.

> Pin mode usually offers "default", "default inverted", "open" and "open inverted". What do they mean?
that's about stm32 GPIO output pin mode. "open" means "open collector" with whatever is the normal convention for logic zero and logic one on open collector. "open inverted" has the logic flipped. "default" means that "off" is 0 volts and "on" is 3.3 volts, while "default interred" means "off" as 3.3v and "on" as 0v. I am all ears on how these names could be improved or how this could be documented better within TS.

> Fuel correction coefficients. multiplier or additive.
These are all multipliers, I am looking for suggestions how to make this more obvious. While we are on this subject, there is a know issue here: tunerstudio does not use floats, historically everything in MS configs is integer (unless I am wrong?). I believe that in version 2.6 they've added F32 type - float type - specially for open5xxxecu - but it is my understanding that they have no motivation to fix all the bugs in F32 support. One of the bugs is that 2D curve editor ignores everything after the decimal point. I have just recently given up on them to fix this and I've started converting from "1.05" as "1.05 multiplier" as in 5% extra to "105" as in "105% multiplier". Most of the curves are still broken, I believe I've only fixed a couple of curves which are related to warmup. I now have a motivation to fix more of these In the meantime, rusEfi console is a work-around but I should just sit and fix all these curves.

stefanst wrote:I would have all pins default to "NONE" instead of PA0.

which ones are we talking about? I am seeing most as NONE and some have defaults. Two pins cannot be the same PA0, that would break things!

This one is not a very important point- just requires a lot of checking an re-checking.
When I opened rusefi.ini (from the 2/26/16 nightly build) pretty much all pins were set to pa0. I assume that's an effect from pa0 usually being the first pin in the option list in the TS setup.

In other news:
I did manage to:
- upload FW
- run the console
- set engine type to 9 (Miata NB)
- Connect using Tunerstudio

now to my problems:

Connecting TS gives a huge list of errors. This appears to be the readable output for the console being interpreted as ECU errors. Setting "fl 0" in the console seems to fix that, but it's annoying having to do this every time.

- I connected my JimStim to the primary/secondary trigger inputs. JimStim voltage was set to 3.3V. Confirmed with oscilloscope trace. Signals look like NB cam/crank trigger signals on the scope. But the ECU seems to have trouble interpreting things properly. Looks like the crank signal is inverted. See picture. Console output looks like this: On the positive side: We have communication, the FW seems to do firmwary things and the next few days may actually see a testrun once that pesky trigger problem is sorted.

http://rusefi.com/forum/viewtopic.php?f=5&t=210

Grounding pin PB1 controls which protocol uses which hardware.
No PB1<>GND jumper on startup: console is on USB.
With PB1<>GND jumper on startup: console is on UART.

can you please zoom in? it looks like there is noise on the second channel
1) 116 117 118 are event counters withing a cycle, these numbers should not be so high with this trigger shape
2) note how the inside of one of the narrow lines is blue

The noise in the signal was caused by operator error.
I fed the signal into the brain-board directly, but without disconnecting the frankenso board first. Running the brain on the stim by itself yields perfect results

Also adding the jumper to PB1 certainly helped with TS.

Thanks!

stefanst wrote: - two wire wasted ignition settings: What does this mean?

Comment label added to the dialog

stefanst wrote: - debug mode: I assume that puts some debug output on the console- correct? Could use an option to disable

No, this is about what info goes into "debugFloat1" "debugFloat2". You've seen "debugInt1" on the recent alternator on/off video

stefanst wrote: 1.2. Trigger configuration
- under "Settings Trigger": "use only front": meaning?

Renamed to "use only rising edge", "With VR sensors only rising edge has reliable position" comment added

stefanst wrote: - under "Settings IO": Primary and secondary channel: which is Cam, which is Crank? I assume Cam is primary.

Yes. Sometimes you have two Cams like on Miata NA - one has to be primary

stefanst wrote: 2.7. Ignition IAT correction
- Y-Axis reads "Intake Load". Is that IAT in ºC?

Label changed to "intake temperature"

Downloaded the new FW and rusefi.ini last night- thank you very much!

I copied my fuel and spark maps over and noticed that the spark map looks very 'flat' when viewed in 3D mode. It appears this behavior is caused by the low/high values in rusefi.ini

I changed the following:
ignitionTable = array, F32, 12632, [16x16],"deg", 1, 0, -720, 720, 2
to
ignitionTable = array, F32, 12632, [16x16],"deg", 1, 0, -20, 90, 2

in line 575 and now I have a nice looking topographical spark map.

Now I just have to figure out how to get the increments in the 3D map when using the cursor keys from "1" to "0.1". Funny enough it works on my MS tune, even though in the settings it displays "1", but the actual increments are 0.1....

stefanst wrote: ignitionTable = array, F32, 12632, [16x16],"deg", 1, 0, -20, 90, 2

fixed, thank you!

I wonder if that value with 0.1 increment has a multiplier of 10 by any chance? I wonder if they increment by one before the multiplier is applied, with the multiplier of 10 that would be a 0.1 increment.

stefanst wrote:1.5. MAP Sensor Settings
- You can enter MAP at minimum and at maximum voltage, but you can't enter those voltages. 0V-5V as standard?

Yes, label was improved

stefanst wrote: 1.8. Speed Sensor
- Is that ADC? Most speed sensors I know are VR or Hall sensors, so this appears to be somewhat useless....

That is not ADC, that is VR or Hall. These magic pins are the ones capable of what stm32 datasheet calls "input capture unit" - these pins are capable of producing an interrupt on rising and falling front.

stefanst wrote: 1.11. MIL settings
- Don't know what MIL is.....

renamed to Check Engine

to be continued.

I am setting up VICS to be controlled with FSIO, based on rpm. Is there any way to program some hysteresis with FSIO? I would like VICS to come on at >= 5000rpm and turn off at <=4800rpm in order to avoid flutter.

This was mostly doable and now I've added 'self' which would return current FSIO value so that this is totally doable.

Unfortunately the UI for RPN conversion is not finished yet (anyone to work on rusEfi console?) so you just need to manually do RPN of Well, I can tell you that it would be so the command is

great- "self" is what I needed!
BTW: I'm old enough to have used hp pocket calculators and am still somewhat familiar with RPN. I also seem to remember a stack-based programming language named "forth" that I played around with in the eighties...