How to switch to secondary table?

[codenamezero]

I've tried the following settings (and a few others variation) but it doesn't look like the SManager switch over to the 2nd table.

- Always Enabled
- Engine speed 4000-7000
- Engine load 70-500 (kPa) <= default
- Throttle 0% (i assume this is the minimum throttle position required?)

I did a couple of pulls all the way to redline but the secondary table never have anything logged. If ever it switched over to the secondary table, and click on the "Estimated change in fuel to target lamda", is it suppose to show the % under high speed table?

Do i need to turn off "Close Loop operation" in order for this to work?

[newsoltsc]

did you try putting the TPS % at like 10 or something?

[Spunkster]

Post the calibration and a datalog showing the problem.

[codenamezero]

b18b, just doing basic n/a tuning to get familiar with the software

i've attached the requested files. thank you.

[Spunkster]

According to your datalog it is working. Make sure you go to Options and check tables follow secondary.

[codenamezero]

Thanks a lot Spunkster. That actually that sorta solved one of the thing i wanted to do with S300. I think I've got the "Low speed table" section covered however...

I also wanted to tune the engine under high load in high speed (perhaps from 100-120km/h and up) using the "High speed table". Is there a setting where i could tell S300 to switch over to use the high speed table?

Tonight I began to tune my low speed secondary table... Instead of keeping the exact same RPM index as my primary table, I've removed several index and added a lot more from 3500 to 7000 (250 stepping). I wonder if this would cause any problem? (haven't upload my new calibration file to the ECU yet)

Basically,
primary table, 500-3500 rpm (250 stepping)
secondary table, 3000-6500 rpm (250 stepping)

[Spunkster]

Options, Tables follow VTEC

[codenamezero]

Is there a way to lock the delta value from the datalog on the secondary table? Right now everything is being logged under the primary table, and when i switch over to secondary, the logged data aren't being reflected...


I think this maybe a bug in in the S300 software... technically, you should have 4 different integer array in memory storing all the logged data...
- 1 array for low speed primary
- 1 array for low speed secondary
- 1 array for high speed primary
- 1 array for high speed secondary

But looking at the software's behavior, it seems like there is only 1 array collecting the data, and it doesn't reflect the rpm differences either.

[codenamezero]

anyone having this problem? or how do you log only the secondary map? the logging is incorrect... for the secondary map

[Spunkster]

This is the way it was designed.

[codenamezero]

This is the way it was designed.

I am going to try it with the VTEC (high speed) map then... i hope the logging will be correct there...

Doesn't make sense to me, the ECU follows the secondary table according to the RPM, but the logging doesn't. And there is no way to lock onto the secondary table so that it would force the S300 to log only for the secondary table.

Honestly, I believe this is more of a design flaw, it would be a good improvement to log data individually under for each map.

I'm a programmer, and i know is not that hard to do, should ask your programmer to do a quick fix for it... and here is some C pseudo code for it...

Code: Select all

Assign an index for each and every map
0 - low speed primary
1 - low speed secondary
2 - high speed primary
3 - high speed secondary

typedef {
   uint8_t map[10*20];  // 200 cells
} DATALOG_MAP;

DATALOG_MAP * map_array[4];
DATALOG_MAP * datalogmap = NULL;

for (i=0; i<4; i++) {
   map_array[i] = memalloc(DATALOG_MAP, 1, sizeof(DATALOG_MAP);
}

So when you log the data, you will log it to 
datalogmap = &map_array[current_table_index];

ANYWAY... i really wish you guys would just patch it.

[Johnny_9]

This is the way it was designed.

I am going to try it with the VTEC (high speed) map then... i hope the logging will be correct there...

Doesn't make sense to me, the ECU follows the secondary table according to the RPM, but the logging doesn't. And there is no way to lock onto the secondary table so that it would force the S300 to log only for the secondary table.

Honestly, I believe this is more of a design flaw, it would be a good improvement to log data individually under for each map.

I'm a programmer, and i know is not that hard to do, should ask your programmer to do a quick fix for it... and here is some C pseudo code for it...

Code: Select all

Assign an index for each and every map
0 - low speed primary
1 - low speed secondary
2 - high speed primary
3 - high speed secondary

typedef {
   uint8_t map[10*20];  // 200 cells
} DATALOG_MAP;

DATALOG_MAP * map_array[4];
DATALOG_MAP * datalogmap = NULL;

for (i=0; i<4; i++) {
   map_array[i] = memalloc(DATALOG_MAP, 1, sizeof(DATALOG_MAP);
}

So when you log the data, you will log it to 
datalogmap = &map_array[current_table_index];

ANYWAY... i really wish you guys would just patch it.

i think reverse engineering the hexadecimal code is very time consuming (weeks of labour), and i am not a programmer....