Engin-X stress rig: waveform generator issues
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 25/100
- Issue 类型
- 缺陷
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 领域
- embedded-iot
调研方向
首先追踪报告中描述的 IBEX 波形生成器 GUI 和 IOC 的行为，然后重现每个问题：振幅显示缩放、停止后的编辑，以及通过下拉菜单或安全机制更改控制模式。完成标准是显示的值和单位与活动模式匹配，并且停止后仍可更改周期数和振幅。
由索引模型根据 Issue 内容生成。
描述
From JK (Engin-X):
- [...] When the wave amplitude is set correctly, and the test therefore runs as expected, the value displayed in the IBEX block is misleading. As it stands now, the units here should be ignored, and the value is simply a fraction of the full scale of the transducer for the selected control mode. For this experiment in Strain control we were using an extensometer with +/- 20% strain travel, and the amplitude number displayed here was 1/20 of the actual set amplitude. I think in principle this bug would also be present for the other control modes.
- Once the waveform generator has been started and stopped (with the GUI Stop button) once, the cycle count and (I think) amplitude can no longer be changed. Resetting the IOC [...] seems to restore the expected behaviour though.
- Changing the control mode will in principle update the displayed units for the wave amplitude, but it seems to display the units for the mode that was set immediately previous to what the actual mode currently is. Setting the desired control mode to the same mode twice thus ensures the amplitude displays the correct units. I’ve not investigated if this is merely a display issue for the units, or whether the rig actually does the wrong thing if you try and do a waveform with the wrong units set for the amplitude.
- The amplitude showing the wrong units can also happen under other conditions if the rig changes mode by any mechanism other than the drop-down combo box, e.g. because a limit is tripped or the rig is manually turned to low power. Typically these put the rig in Position control as that is deemed the safest and most predictable control mode. Again, I’ve not tested the true implications of the incorrectly displayed units to see if it affects the actual rig behaviour.
- 主要语言
- 没有语言数据
- 星标
- 6
- 派生
- 2
- 平均合并
- 12 天 19 小时
- 30 天内合并 PR
- 3
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
ISISComputingGroup/IBEX 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
ISISComputingGroup/IBEX#9023 ·
-
难度 2/5 1-3 小时 新手友好度 78/100
ISISComputingGroup/IBEX#9005 ·
-
Good First Issue
难度 2/5 1-3 小时 新手友好度 65/100
ISISComputingGroup/IBEX#8889 ·
-
0
难度 1/5 1 小时以内 新手友好度 65/100
ISISComputingGroup/IBEX#2304 · 1 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 75/100
ISISComputingGroup/IBEX#2078 ·
查看 ISISComputingGroup/IBEX 的全部 Issue
相似的 Issue
-
area: core priority: p2 type: bug
难度 2/5 1-3 小时 新手友好度 72/100
EPFL-TOP/smart-microscope-control#132 ·
维护者通常 1 天内回复
-
scope:mqtt-bridge type:feature
难度 2/5 1-3 小时 新手友好度 74/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
bvis/aegis-hass#588 · 1 条评论 ·
维护者通常 1 天内回复
-
integration: homewizard
难度 2/5 1-3 小时 新手友好度 66/100
home-assistant/core#186409 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 90/100
joleys/niko-home-control-II#321 ·