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.

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

[slave] Use the AL error field to inform master from failures #139

Open
Rdk-T opened this issue Feb 22, 2024 · 1 comment
Open

[slave] Use the AL error field to inform master from failures #139

Rdk-T opened this issue Feb 22, 2024 · 1 comment

Comments

@Rdk-T
Copy link
Collaborator

Rdk-T commented Feb 22, 2024

At the moment the slave stack does not handle the error code.

ie:

  • Fail to switch state in ESM
  • Fail to load EEPROM ?
@Rdk-T
Copy link
Collaborator Author

Rdk-T commented Feb 23, 2024

Check if these info in ETG 1000.6 are relevant

In case of an error first the AL Status Code shall be set and then the Error Flag has to be set.
After clearing the Error Flag the AL Status Code should be cleared, too. The master shall ignore
the AL Status Code if the Error Flag is clear.
In case of a state transition from AL state Op to SafeOp with Error the output SyncManager
shall be disabled. The input SyncManager shall only be disabled in case of an error which
results in invalid inputs (input error or synchronization error).
The Output-SyncManager shall be re-enabled if the error was acknowledged and there is no
output error remaining.
The Input-SyncManager shall be re-enabled if the error was acknowledged and there is no input
error remaining.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant