FabMo
Update "System Variable Numbering"
We have carried over the ability to call up system variable in opensbp using %(var num).
At the moment, the specific numbering order is a hold-over from Sb3. Now would be a good time to make slight changes to the FabMo system to be more consistent with FabMo configs and better ordered. The numbering for the C axis and jerk values are some examples.
Relatively easy to change, but need to make sure well documented and as minimally different from sb3 as possible.
What are the odds that it makes sense tro add "system variable aliases" i.e. that a system variable can be assessed as %(5000) or %(CurrentPositionOfQaxis) as well as reordering?
Can we specify what changes we want to make in the text of this issue before we start making them?
I don't understand the question. You quote an issue that is about a different topic (e.g. "user variables"). This issue topic is about the numbered "system variables".
It references the general matter of the overlap of how machine configuration items are managed between FabMo and G2 and about the matter that when OpenSBP was conceived we did not anticipate more than 4 axes so that there are now inconsistencies in how the numbering of system variables, which are sometimes also config variables, works.
The issue 882 is about user-named-variables of the &var and $var type and what we want to expose by way of allowing the user to manage them ... and as noted in the issue, we have one model in Josh's "Config App" that is installed in the dev-test profile.
I think we need to talk about this. I can see you didn't understand my comment. I appreicate the specifics for what you think are the kinds of things that need changing. I can understand how numbering might be off as more axes have been added. Didn't know that was the issue. Are there other issues like that? can we enumerate them here?