Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

one VE table per strategy #459

Open
mck1117 opened this issue Aug 5, 2024 · 2 comments · May be fixed by #539
Open

one VE table per strategy #459

mck1117 opened this issue Aug 5, 2024 · 2 comments · May be fixed by #539
Assignees
@nmschulte

Comments

@mck1117
Copy link
Collaborator

mck1117 commented Aug 5, 2024

Right now we share one VE table for all strategies. We should have one table per strategy to enable on-the-fly switching and blending.
mck1117 added a commit that referenced this issue Sep 25, 2024
@mck1117
don't inject VE table, prep #459
e259625
@nmschulte nmschulte self-assigned this Jan 17, 2025
@nmschulte
Copy link
Contributor

and the commit prior is important: fca72c4

@nmschulte
Copy link
Contributor

@mck1117 how are you envisioning this works? Three separate VE Tables in persistent_config_s (config)/rusefi_config.txt all sharing axis bins/size?

Image

@nmschulte nmschulte linked a pull request Jan 17, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nmschulte nmschulte

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

per strategy ve table nmschulte/fome-fw
2 participants
@mck1117 @nmschulte