[INSTRM-1051] Ensure that hexapod moves always move _up_ to final position. Created: 14/Aug/20 Updated: 13/Jan/21 Resolved: 30/Sep/20 |
|
| Status: | Done |
| Project: | Instrument control development |
| Component/s: | ics_enuActor |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | cloomis | Assignee: | arnaud.lefur |
| Resolution: | Done | Votes: | 0 |
| Labels: | SPS | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
PFS_SM1_Hexapod_Positioning_Repeatibility (1).pdf
|
||||||||
| Issue Links: |
|
||||||||
| Story Points: | 4 | ||||||||
| Sprint: | SM1PD-2020 G2, SM1PD-2020 H | ||||||||
| Description |
|
Can the hexapod driving code always ensure that the slit moves up to the final position? I.e. if the target position is below the starting position, the hexapod should be moved past/below the target position first. Or maybe moves should always go past/down, then back? This would at least make moves consistent w.r.t. gravity. |
| Comments |
| Comment by arnaud.lefur [ 03/Sep/20 ] |
|
I have two options: |
| Comment by arnaud.lefur [ 30/Sep/20 ] |
|
merged in 1.1.0 |
| Comment by hassan [ 13/Jan/21 ] |
|
Added document PFS_SM1_Hexapod_Positioning_Repeatibility (1).pdf |
