I would find it usefull to have a custom channel as gearshift strategy activation.
We could for example decide to activate the strategy only after a few seconds to give time to all modules connected to CAN to boot properly.
On the project I am working now on startup sometimes it shifts automatically.
I know there are other ways to work around this but a custom activation would be a neat solution.
Hi,
Please describe the issue and setup in detail first.
We have to understand it to decide if the solution you are proposing is good.
What kind of gearbox is used, and what inputs are used for shifting?
Can you record the shift at startup issue on the log and post it here?
What exact CAN modules do you want to wait for and why?
The setup is as follows:
- emupro-16
- sequential gearbox with pneumatic paddle shift, actuated by emupro
- paddle inputs over CAN (AIM PDM32)
Unfortunately logging only starts after this shift has occured and so does not show this event.
I was thinking this shift occured because of the PDM sending a message on startup that is seen as a shift request by the Emupro. But I start to doubt this is the case.
Is it possible the Emupro just shortly actuates outputs at startup?
Can you change the Shift actuator outputs to Auxiliary output and try again?
Normally it should not actuate outputs till its programmed to do so. or unless it receives a message. and if does it should be in the logs or live logging when you are connected
Why would you want me to do so? Is there a chance injector outputs are “tested” at startup and aux outputs not?
As I told before, logging starts later then this event at startup so this will not make us wiser. Logging takes a few seconds to get going and this happens in the second after power up.
When the ECU starts, there is a very short pulse at the injector output, lasting a few microseconds.
Pulse that short wouldn’t actuate the solenoid.
By changing the assignment, you can confirm whether it’s an output or strategy issue.
Select different, unused outputs for the shift solenoids.
If the issue still exists, it’s an issue with startup/output.
If the issue is gone, it’s an issue with the paddle inputs.
The strategy will not actuate the output unless there is an active request.
Since you send the data over CAN, it can be an issue of default value or other configuration.
To check the configuration, I need to look at the project file.
If you are connected to the ECU with a laptop, the logging is active around half a second after power-up.