Closed ct2034 closed 4 years ago
I've drawn the rename and PEP-8 out of this PR so this PR is just about braketest and opmode as its title suggests.
@martiniil @JonathanGruner I gave it another try rephrasing and grouping the options. I'm still unsure, what the sto
option does? Is this used for braketest and operationmode as well? And why should a user disable operation mode support? I see just one usecase with safety function and one without - no need for finegrain feature selection.
@martiniil @JonathanGruner I gave it another try rephrasing and grouping the options. I'm still unsure, what the
sto
option does? Is this used for braketest and operationmode as well? And why should a user disable operation mode support? I see just one usecase with safety function and one without - no need for finegrain feature selection.
@jschleicher Yes, I think the use-cases you desribe are sufficient. Currently, sto
serves for specifying the safety controller, which is of course misleading.
edit: The braketest-module may be missing, but this could also be decided dependent on the name of the safety controller?
I would suggest the following:
We merge this, as it is now. Because this will work with the current state of pilz_robots
.
And then we continue the discussion about naming of sto there. There are more aspects to this: https://github.com/PilzDE/pilz_robots/pull/315 Ok, @martiniil @jschleicher ?
I read through your comments, and from mine/customer point of view I would write both tags below the tag with "sto" (which I requested to change to "device" because a STO is something else, see https://github.com/PilzDE/pilz_robots/pull/315 , and than maybe you can define your own device in the future), but commented.
But I would prefer to discuss how we design the user frontend together in the next sprint review on Wednesday.
remaining changes addressed in #16
@jschleicher I like your first suggested change more.