Tags:
tag this topic
create new tag
view all tags
---++ Target Runs, Debugging * After Chaz and Johannes had seen some images being taken before move finished (12000 steps moves) we added back the wait command * Johannes analyzed whether the above issue happens on target runs by manual inspection and concluded it does not occur. (Measured time for moves and mean was always 4.xx ms.) * Hrands Timing Calculation is off by a factor of 4 because he uses 1ms interleave interval at every single step (instead of actual ontime) and multiplies it by max number of steps for each positioner in a group and addds all these values for each group (15 groups). * Moving direct from previous target position tested on 9/29 target run. Seems to work. * Discussed cap of steps per iteration with Hrand, might be problematic for collision avoidance blind moves. * Discussed testing of collision avoidance. * Analyzed the reason for previous target runs taking long time -> PID3 motor map was off so that 42k steps were commanded at some point -> 65 seconds moves. -- Main.JohannesGross - 29 Sep 2015
E
dit
|
A
ttach
|
Watch
|
P
rint version
|
H
istory
: r1
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r1 - 2015-09-29
-
JohannesGross
Home
Site map
Antarctica web
Gattini web
SPRITE web
Cahill web
Gemini web
Keck web
MOSFIRE web
NGAO web
Main web
Palomar web
GASP web
PTF web
PalmLGS web
RoboAO web
SDC web
SEDM web
SWIFT web
TMAS web
Triplespec web
WaSP web
ZTF web
SNAP web
Sandbox web
Subaru web
PFS web
TMT web
More...
PFS Web
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
P
P
View
Raw View
Print version
Find backlinks
History
More topic actions
Edit
Raw edit
Attach file or image
Edit topic preference settings
Set new parent
More topic actions
Account
Log In
Register User
E
dit
A
ttach
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki?
Send feedback