turret (rotary floor in dome)
nov 03
23jul20: turret does
not arrive on position during sbTx test.
29nov19: turret torques at
various maximum velocities (measured 04nov19)
30oct19: torque
oscillations when turret sitting.
29may18:zeroVelOffset
jumps are caused by dac or signal conditioning board.
11feb18: turret brake fail.
19feb17: turret does not
arrive at position. dac zero velocity error.
12jan16: turret does not
arrive at position. This is a dac zero velocity offset error.
15aug14: Turret does not
arrive at position. adjusting the backlash board, see oscillation
in spd,torque
27jul12: amman- &
whitney report on feed platform rotating floor (.pdf)
03may11: small jerks in turret
while rotating
12sep05: replacing 1 section of
rolling surface. Tilt sensor measuremen
08may04: turret encoder
11feb04 : turret aToD and signal conditioning.
14jan04: Weigh rotary floor with
hydraulic jacks (.pdf)
12nov03:
weight
distribution on the turret.
history/modification log:
turret schematics (r elias oct96)
(.pdf)
Communications
protocol (for td but includes master) (.pdf)
Turret brakes
drive system
kollmorgen
amp,motors
- Includes bds4 manual and rdp2 backlash manuals.
notes,gotchas
Drive system:
The turret drive system consists of:
- There are two motors to move the floor: the master and the
slave.
- The little star computer generates a single velocity command
for the floor.
- This is sent via a dac and then signal conditioning board to
the backlash compensation board
- The backlash compensation board then sends the velocity
command to the master and slave amps
- A small backlash compensation is added to remove backlash in
the gears.
- As the velocity increases this compensation is slowly
removed.
Notes, gotchas:
15aug14: If the turret does not arrive
at the requested position..zero velocity offset adjustment:
the dac probably has a dc offset (see 15aug14)
To fix:
- run montur
- command turret to a position. look at VelocityCnt (say 2009)
- compute what zero velocity offset this would be for the dac:
- zeroVelOffset= VelocityCnt + 100 - 2048. this is the
value that should be loaded in the little star
- See what value is currently loaded in little star
- in vw% window execute tcl:
- for
{set i 0} {$i < 38} {incr i} {
puts "[pnt tur qpar $i]"
aog delay 10
flush stdout
}
- Then on observer2: cd /home/phil/vw/datatk/pnt/ttt/tt
- in the shell execute: ttParms
- 34
zeroVelOff
53 where 53 would be the
zero velocity offset
- If it is off by more than a count or two
- from observer2:
- rsh pnt ttTst
- 21 1
- 9 34 Value you computed above for zeroVelOffset
- 10 34 read back into vxWorks
- 99 quit
- The try ttParms again.. you should now see the new zero
velocity offset.
<-
page up
home_~phil