A SINUMERIK manual-jog velocity is selected in an axis context. The term axis-specific means that editing 32020 JOG_VELO while X is selected changes the X-axis setting; it does not automatically copy that value to Z. A reported change from 2000 mm/min to 4500 mm/min produced 4500 mm/min on X while Z remained at 2000 mm/min. That result identifies separate axis data, not a common jog-feed setting.
Configure and prove each motion axis independently. Treat turret indexing as a different machine function: 32020 JOG_VELO controls axis jogging, not the turret swivel sequence.
Axis-context identification
On SINUMERIK 810D/840D, an axis-specific machine-data page presents data for the currently selected axis. The same identifier can therefore appear for both X and Z while holding different values. A valid edit in the X context can leave Z unchanged without producing an alarm or indicating a failed write.
| Observed condition | Meaning | Required action |
|---|---|---|
X jogs at 4500 mm/min; Z jogs at 2000 mm/min
|
The edit was applied to X while Z retained its previous value. | Select Z in the axis-specific data view and edit its own 32020 JOG_VELO. |
| Both displayed settings match, but measured motion does not | A feed override, active motion limit, or machine condition is restricting one axis. | Compare command and actual velocity, then inspect the active restriction. |
| Turret swivel time is unchanged | The turret sequence is not governed by the linear-axis jog velocity. | Leave 32020 JOG_VELO out of turret-time troubleshooting. |
| A value changes in the editor but not during motion | The edit may not yet be active, or another limit is lower. | Read the control's activation indication and follow the machine builder's commissioning procedure. |
Check 1: Select X and read 32020 JOG_VELO; expect 4500 mm/min in the reported configuration. Select Z and read the same identifier; expect 2000 mm/min before correction.
Baseline capture and change control
Record each axis value before editing. This preserves the machine builder's baseline and prevents a later comparison from relying on memory. Capture the selected axis name, the existing 32020 JOG_VELO value, the requested value, and the control state required to activate the edit. Do not change unrelated machine data while searching for a speed difference.
The requested 4500 mm/min is a jog command value, not proof that the mechanics can or should reach that velocity under every condition. Axis limits, feed override, deceleration behavior, travel proximity, and machine-builder interlocks can reduce actual motion. Retain the original 2000 mm/min value so it can be restored if the higher command produces unacceptable behavior.
| Record | X axis | Z axis |
|---|---|---|
| Original value |
2000 mm/min was reported before the change |
Read directly before editing |
| Requested value | 4500 mm/min |
4500 mm/min |
| Post-edit value | Read back from the X context | Read back from the Z context |
| Actual jog velocity | Observe during a controlled test | Observe during a controlled test |
Check 2: Compare the recorded settings with the live axis-specific displays; expect one traceable original value and one requested value for each axis, with no unrelated machine-data changes.
X-axis jog configuration
Establish X first because its reported behavior already demonstrates the intended result. This also creates a known-good reference for the Z-axis correction. Keep the feed override in a documented position during every comparison; changing it between tests invalidates a direct velocity comparison.
- Place the machine in the commissioning state required by the machine builder.
- Open the commissioning path identified as
IBN, then open the axis-specific data view. - Select X explicitly and confirm that the page identifies X as the active axis context.
- Locate
32020 JOG_VELOand read the current value. - Set the X value to
4500 mm/minif it is not already present. - Apply the activation method displayed by the control or specified in the machine documentation. Do not guess whether a reset or restart is required.
- Return to manual jog mode and command X over clear travel at a controlled override setting.
Observe both commanded and actual velocity if the control exposes them. Near an endpoint or during acceleration and deceleration, actual velocity may remain below the command; evaluate the steady portion of travel.
Check 3: Read X-axis 32020 JOG_VELO after activation; expect 4500 mm/min. During a suitable steady jog, expect X to reach the commanded velocity unless an identified override or limit is active.
Z-axis jog configuration
The Z correction uses the same identifier in a different axis context. Re-entering 4500 mm/min while X remains selected merely rewrites X and leaves the original symptom intact.
- Return to the axis-specific machine-data view.
- Change the selected axis from X to Z and verify the axis label before touching the value.
- Locate
32020 JOG_VELO. In the reported condition, its Z value is2000 mm/min. - Record that value, then enter
4500 mm/minfor Z. - Use the applicable activation method shown by the control or prescribed by the machine builder.
- Read the parameter again while Z remains selected.
- Jog Z through clear travel using the same documented feed-override position used for X.
A matching parameter readback proves configuration equality; it does not by itself prove equal actual motion. Compare the steady commanded and actual velocities. If Z remains at 2000 mm/min, first reconfirm that the Z context was active during the edit. Then identify any displayed velocity limit or interlock rather than increasing another machine datum blindly.
Check 4: With Z selected, expect 32020 JOG_VELO to read 4500 mm/min. Under equivalent override and travel conditions, expect the Z jog command to match the X jog command.
Command-versus-actual velocity diagnosis
The configured jog velocity, commanded velocity, and actual velocity are separate quantities. The configured value supplies the requested manual-jog rate. The motion control can shape that request for acceleration and deceleration, while override and active limits can reduce the command. The drive and mechanics then determine the measured actual velocity.
| Comparison | Diagnostic conclusion | Next check |
|---|---|---|
| Parameter values differ by axis | Axis-context configuration mismatch | Correct 32020 JOG_VELO on the slower axis. |
| Parameters match; commands differ | An override, jog mode, or control-side limit differs | Normalize the operating state and inspect active restrictions. |
| Commands match; actual velocities differ | The restriction lies downstream of command generation | Inspect drive diagnostics, axis status, and mechanical loading. |
| Velocity rises and falls only near the ends of the move | Acceleration or deceleration is being observed | Compare the steady portion of travel. |
Do not defeat a lower machine limit merely to force the displayed actual velocity to equal 4500 mm/min. Identify why the limit is active and obtain the machine builder's approved value before changing it.
Check 5: At a fixed override setting, expect matching configured values to produce matching jog commands. If actual motion remains unequal, expect the diagnostic display to distinguish a reduced command from a following or drive-side limitation.
Turret swivel boundary
Turret swivel time is outside the function of 32020 JOG_VELO. A turret index is a machine sequence, not an X- or Z-axis manual-jog move. It can include release, motion, position confirmation, and clamping, with the sequence governed by the machine implementation and its interlocks.
For the reported control context, the turret swivel time is not an operator-adjustable consequence of changing the jog velocity. Raising X or Z JOG_VELO will therefore not make the turret index faster. If indexing is abnormally slow, diagnose the sequence by observing which stage consumes time and then consult the machine manufacturer for the applicable service procedure. Do not search unrelated axis machine data for a generic turret-speed setting.
Check 6: Command one normal turret index and observe the sequence stage by stage; expect no change in swivel time from the X/Z 32020 JOG_VELO edits.
End-to-end commissioning verification
- Select X in the axis-specific view. Expect
32020 JOG_VELO = 4500 mm/min. - Select Z without leaving the axis-specific view. Expect
32020 JOG_VELO = 4500 mm/min. - Set and record one feed-override position for both tests.
- Jog X over clear travel. Expect the configured command during the steady portion of motion, subject only to an identified active limit.
- Jog Z under equivalent conditions. Expect the same configured command as X.
- Compare actual velocities. Expect any difference to correlate with a displayed restriction, drive condition, or mechanical condition rather than a remaining parameter mismatch.
- Stop motion, re-open both axis contexts, and read back the values. Expect both entries to remain at
4500 mm/min. - Test one turret index separately. Expect its swivel timing to remain independent of the X/Z jog setting.
Frequently asked questions
Why does SINUMERIK jog X at 4500 mm/min but Z at 2000 mm/min?
32020 JOG_VELO is axis-specific. The X value was changed to 4500 mm/min, while the Z-axis instance remained at 2000 mm/min.
Why does changing 32020 JOG_VELO not update every axis?
The axis-specific data view writes the instance belonging to the selected axis. Select Z, verify the Z axis label, and enter 4500 mm/min in its own 32020 JOG_VELO field.
Why is actual jog speed lower after both values match?
Compare configured, commanded, and actual velocity at a fixed feed override. A lower command points to an override or active control limit; a matching command with lower actual velocity points to drive, axis-status, or mechanical diagnostics.
Does 32020 JOG_VELO make the turret index faster?
No. It changes axis jog velocity, not the turret swivel sequence. Final check: read 4500 mm/min for both X and Z, prove equal jog commands under the same override, and verify separately that turret timing is unchanged.