ISISComputingGroup / ISISComputingGroup/IBEX
Beckhoff: Engineering units are left at microns by default
- Langage dominant
- Aucune donnée de langage
- Étoiles
- 6
- Forks
- 2
- Merge moyen
- 16 h 40 min
- PR mergées (30 j)
- 2
Description
As a scientist I would like my Beckhoff to tell me what its engineering units are through IBEX. I identified when commissioning LARMOR that the units for the system were incorrect. The units should be `deg` for LARMOR as it's a rotating bench, however by default we display `um` as the EGU. We should talk to the motion team about how we can add this functionality.
### Acceptance Criteria
_What is the acceptance criteria?_
- [ ] A discussion is had between us and the motion team about adding this functionality.
- [ ] Changes are implemented in tcioc for the units info to propagate to each axis (units may also be different per axis?)
- [ ] Tests are added to make sure this info is propagated correctly
### Extra Information
This information currently isn't stored in the status struct, or subsequently the .tpy file. It may be best to add these through the global struct instead, for example how nAXIS_NUM is added (even though we don't currently use it!)
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
Commencez par examiner tcioc et la manière dont status struct, .tpy data et global struct exposent des valeurs telles que nAXIS_NUM. Discutez de la conception de la propagation des unités avec le motion team, notamment pour déterminer si les unités diffèrent selon l’axe. Le travail sera considéré comme terminé lorsque les unités d’ingénierie atteindront chaque axe et que des tests vérifieront les informations propagées.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Domaine
- embedded-iot
- Type d'issue
- Fonctionnalité
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 30/100