Lauritz Knudsen xD1000 Programming Guide: Which Menus to Use for Your Application
⚡ The xD1000 uses a compact 4-digit, 7-segment keypad and a menu-code system rather than a full-text display — ConF → FULL → menu (e.g. 500-) → code (e.g. 501.0) → value. That’s efficient once you know your way around, but it means the fastest path to a working setup is knowing which codes your job actually needs, rather than paging through the full 143-page manual. This guide distills the official xD1000 Installation & Programming Manual (SP51099), the Complete Parameters List (SP51102) and the Quick Start Guide (SP51101) — plus real-world commissioning notes from our own engineers — into a practical, click-to-expand reference.
💡 How to use this guide: complete the universal setup below first (every xD1000 needs this regardless of application), then click on your function to see exactly which menu codes to set and why.
✅ Step 1: Universal Setup (Every Drive, Every Application)
Before anything application-specific, every xD1000 commissioning starts the same way: basic wiring, a macro shortcut, motor nameplate data, and the run-control type.
| Menu / Code | Name | What to set |
|---|---|---|
| — | Basic wiring | Mains to R/L1, S/L2, T/L3; motor to U/T1, V/T2, W/T3; ground below the output terminals. Double-check ground continuity — the anodized heatsink on this drive can insulate the mounting surface if the recommended grounding point isn’t used. |
| [100] | Macro-Configuration | 00 = Start/Stop (Forward only assigned) · 04 = PID regulation (dedicates AI1 to feedback) · 09 = Speed (preset speeds via logic inputs). Picking the closest match before auto-tuning pre-wires sensible AI1/AO1/LI/R1 defaults instead of leaving you to assign every I/O by hand — you can still fine-tune any of them afterward in their own menus. |
| [301, 304–308] | Motor nameplate data | Enter standard frequency (301: 50/60Hz), rated voltage (304), current (305), frequency (306), speed (307) and maximum frequency (308) exactly from the motor nameplate — every torque, protection and thermal calculation downstream assumes these are accurate. |
| [309] | Motor control type | 03 = Standard U/F 2-point (factory default — fine for most pumps, fans, conveyors) · 00 = Performance/Vector control (better low-speed torque) · 06 = Pump U²/F (quadratic curve suited to centrifugal loads). Set this before auto-tuning. |
| [318] | Auto-tuning | 01 = Request auto-tuning, with the motor stationary and nameplate data already entered. Improves both torque accuracy and thermal protection over the generic factory model. |
| [201] | Type of control | 00 = 2-wire (the level or state of the logic input controls run/stop) · 01 = 3-wire (separate momentary Stop/Forward/Reverse pushbuttons). Must be set before auto-tuning — changing it later resets your digital input assignments to factory defaults. |
| [401] / [407] | Reference channel 1 / Command channel 1 | Two separate settings, easy to mix up: 401 decides where the speed comes from (01 terminal/AI1 · 163 remote display · 164 Modbus · 183 integrated keypad jog dial). 407 decides where the run/stop command comes from (01 terminals · 02 integrated display · 03 remote display · 10 Modbus). In factory settings both RUN and the jog dial are inactive until you set these. |
| [102] | Factory / recall parameter set | Set to 64 (hold ENT 2s to confirm) any time you want a clean factory baseline before commissioning, or 02 to reload your own saved backup (see [101] Store customer parameter set). |
📌 Step 2: Pick Your Function
✅ Run Control: 2-Wire, 3-Wire & Jog
✅ Speed Reference Sources & Local/Remote Switching
✅ Multi-Speed / Preset Speed Configuration
✅ Ramps, Stop Methods & Braking
✅ Torque Boost, Speed Limits & Skip Frequency
✅ Up/Down (Motorized-Pot) Control & Catch-on-the-Fly
✅ PID Control & Sleep/Wake (Pumps, Fans & Pressure Loops)
✅ Fault Management: Reset, Auto-Restart & Fault Inhibition
✅ Fan Control & Motor Thermal Protection
🏃 Run Control: 2-Wire, 3-Wire & Jog
Most installations use simple 2-wire control from a maintained switch or PLC output. A 3-wire station (separate momentary Start/Stop pushbuttons) needs its own wiring pattern and one extra parameter.
| Code | Setting | Why / how |
|---|---|---|
| 201 = 00, 202 | 2-wire, then choose 202: 00 Level · 01 Transition* · 02 Forward priority | Level: the LI must stay closed to keep running. Transition: a pulse toggles run/stop. Forward priority: if both Forward and Reverse LIs are active at once, Forward wins — a sensible safety default on a machine that could otherwise receive conflicting signals. |
| 201 = 01 | 3-wire control | LI1 = Stop, LI2 = Forward pulse, LI3 = Reverse pulse (source wiring example in the manual). Set this before auto-tuning and before wiring a physical start/stop station. |
| 500→505.0 | Jog assignment, e.g. L4H = LI4 active high | Gives a momentary low-speed run for manual positioning or threading, independent of the normal ramp and run command. |
| 505.1 | Jog frequency — 0 to 10Hz (5Hz*) | Keep this low deliberately — jog is for manual positioning, not production speed. Note that Jog and Preset Speed can’t be assigned to the same logic input; if both are wired, Jog takes priority. |
💡 Real-world quick recipe (2-wire, running from the terminal with speed set from the keypad button): initialize the drive (102=64) → set reference to the integrated display (401=183) → enable separate command/reference channels (406=02) → set run command to terminal (407=01) → give the run command through the terminal and adjust speed with the keypad’s own Run button/dial.
🎯 Speed Reference Sources & Local/Remote Switching
The xD1000 can take its speed reference from four different places, and — separately — its run command from four different places. Understanding that these are two independent settings avoids the most common beginner mix-up on this drive.
| Code | Value | Meaning |
|---|---|---|
| 401 Reference channel 1 | 01 · 163 · 164 · 183 | 01 = Analog terminal (AI1) · 163 = Remote display terminal · 164 = Modbus · 183 = Integrated display with jog dial. |
| 407 Command channel 1 | 01 · 02 · 03 · 10 | 01 = Terminals · 02 = Integrated display · 03 = Remote display · 10 = Modbus. |
| 406 Channel configuration | 01* Combined · 02 Separate | Separate mode lets the reference and command come from two different places at once (e.g. speed from AI1, run/stop from Modbus) — needed for most PLC-integrated setups. |
| 408 Forced local assignment | 00* Not assigned, or L1H–L4H / LUH | Wire a logic input here to let an operator force the drive into local (keypad) control on demand — useful for maintenance or manual override without reprogramming. |
| 409 Forced local reference | 00* Not assigned · 01 Terminal · 163 · 183 | Sets which source takes over once forced-local is active via 408. |
💡 If your PLC talks to the drive over Modbus, set 401=164 and 407=10, and remember a drive with Modbus assigned as its reference or command channel shows freewheel stop (502.1) and stays in that state until the bus actually sends a command — this is normal, not a fault, and is documented in the “drive does not start” troubleshooting section of the manual.
🔢 Multi-Speed / Preset Speed Configuration
The xD1000 supports up to 8 preset speeds, selected by combining logic inputs — a common pattern for conveyors, mixers or any machine that cycles between a small number of fixed speeds without needing a PLC.
| Code | Setting | Why / how |
|---|---|---|
| 507.0 | 2 preset speeds — assign one LI, e.g. L2H | Toggles between the base reference and Preset speed 2 (507.3) via that one input. |
| 507.1 | 4 preset speeds — assign a second LI, e.g. L3H | The two LIs combine (00/01/10/11) to select between the base reference and presets 2–4. |
| 507.2 | 8 preset speeds — assign a third LI | Three LIs combine to select between the base reference and presets 2–8. On a 4-LI drive this uses most of your available digital inputs, so plan your I/O budget before committing to 8-speed operation. |
| 507.3–507.9 | Preset speeds 2–8, each 0–400Hz (defaults 10/15/20/25/30/35/40Hz) | Set each stage’s actual frequency here, independent of the accel/decel time used to reach it. |
⚠️ Preset speed is not compatible with the PI (PID) regulator or Jog on the same logic input — per the drive’s function compatibility table, Jog takes priority over a preset speed request, and Preset speed/PID regulation can’t be active at the same time. If your application needs both multi-speed and PID (e.g. a booster set with a manual override speed), assign them to different, non-conflicting logic inputs and test the interaction before commissioning.
🔄 Ramps, Stop Methods & Braking
How the drive accelerates, decelerates and stops matters as much as how fast it runs — get this wrong and you’ll see nuisance overvoltage trips on deceleration or a load that doesn’t stop the way your process needs.
| Code | Setting | Why / how |
|---|---|---|
| 501.0 / 501.1 | Acceleration / Deceleration — 0.0 to 999.9s (3.0s* each) | The core ramp times. Too short trips on overcurrent (accel) or overvoltage (decel); too long wastes cycle time. |
| 501.2 | Ramp shape — 00 Linear* · 01 S-shape · 02 U-shape | S-shape smooths the start/end of the ramp for gentler mechanical transitions — useful on conveyors carrying loose material or geared loads sensitive to jerk. |
| 501.3–501.5 | Ramp switching commutation (LI assignment) + Acceleration 2 / Deceleration 2 (5.0s* each) | Wire a logic input to switch between your normal ramp and a second, independent ramp — e.g. a fast ramp for normal running and a slow one for a delicate load-in condition. |
| 501.6 | Decel ramp adaptation — 01* Active | Left on factory default, the drive automatically stretches the deceleration ramp if it detects a risk of DC-bus overvoltage from the regenerated energy — the single biggest reason a “fixed” decel time still avoids nuisance trips on default settings. |
| 502.0 | Type of stop — 00 Ramp* · 03 DC injection · 08 Fast stop · 13 Freewheel | Ramp stop follows 501.1. Fast stop uses the same ramp divided by 502.3 (1–10, 4* — i.e. 4× faster by default). Freewheel simply cuts output and lets the load coast — the quickest to command but with no braking control. |
| 502.1 / 502.2 | Freewheel / Fast stop assignment via a logic input (active low to stop) | Wires an emergency-style stop input independent of the normal run command — these functions are active at zero/open by design, so a broken wire fails safe into a stop. |
| 504.0–504.2 | Automatic DC injection — 00 off · 01* time-limited · 02 continuous; current 0–120% (70%*); time 0.1–30s (0.5s*) | Injects DC current briefly at the end of a stop to lock the motor shaft in place — useful on loads that could drift or free-spin after the ramp reaches zero. |
⚠️ Freewheel, Fast stop and DC injection are mutually exclusive stop modes on this drive — if two are triggered at once, priority goes to whichever was activated first, per the function compatibility table in the manual. Don’t rely on two of these being active together as a layered safety measure; use a hardware safety relay for that instead.
🔭 Torque Boost, Speed Limits & Skip Frequency
These are the tuning knobs for getting a hard-starting load moving, keeping the drive inside a safe operating window, and avoiding a mechanical resonance point.
| Code | Setting | Why / how |
|---|---|---|
| 310 | IR compensation — 25 to 200% (100%*) | The xD1000’s torque boost — raises voltage at low speed to help a load break away against static friction. Used to optimize torque at very low speed; raise it for a hard-starting load, but watch for motor humming/overheating if pushed too far on a light load. |
| 512.0 / 512.2 | Low speed (0 to High speed, 0Hz*) / High speed (Low speed to Max frequency, 50/60Hz*) | Clamps the usable frequency window — protects a pump from running below its minimum flow point, or a fan/spindle from exceeding a mechanical speed limit. |
| 512.1 | Low speed operating time — 0.1 to 999.9s (0s* = unlimited) | Limits how long the drive can run continuously at low speed before an action is taken — relevant where prolonged low-speed running risks motor overheating (self-ventilated motors cool less at low RPM). |
| 508 | Skip frequency — 0 to 400Hz (0Hz*) | Sets a frequency the drive jumps past (±1Hz) rather than running at continuously — use it to ride through a mechanical resonance point in the driven equipment instead of dwelling in it. |
| 315 / 317 | Switching (carrier) frequency — 2 to 12kHz (4kHz*) / Motor noise reduction — 00*/01 | Raising the carrier frequency quiets the audible motor whine but increases drive heat and forces current derating above 4kHz (10% derating at 8kHz, 20% at 12kHz per the drive ratings table) — don’t raise it past what your enclosure/ventilation can handle. |
↑↓ Up/Down (Motorized-Pot) Control & Catch-on-the-Fly
Two independent conveniences worth knowing: a motorized-potentiometer-style speed control using two simple pushbuttons, and a smooth restart onto a load that’s already spinning (a coasting fan, for example) instead of tripping or lurching.
| Code | Setting | Why / how |
|---|---|---|
| 506.0 / 506.1 | Up speed command / Down speed command — assign to LIs, e.g. L2H / L3H | Two pushbuttons raise/lower the running speed continuously while held — a simple alternative to an analog input where an operator just needs “faster/slower” control. |
| 506.2 | Store — 00* No · 01 RAM · 02 ROM | RAM keeps the adjusted speed only until the next stop/power cycle. ROM makes it persist across a power cycle — useful for a process that should resume at its last set speed, but means every adjustment is a small write to non-volatile memory, so avoid pairing frequent up/down nudges with ROM storage. |
| 506.3 / 506.4 | Clear function (LI assignment) / Reactivity of +/− speed around reference (0–100%, 0%*) | 506.3 resets the adjusted speed back to the base reference on command. 506.4 adds a small dead-band/response tuning around the reference for smoother manual adjustment. |
| 603 | Catch on the fly — 00* Inactive · 01 Active | Lets the drive detect a motor that’s already spinning (freewheeling after a brief power loss, or a fan still coasting) and smoothly ramp back onto it, instead of a hard restart from zero or a trip. |
💧 PID Control & Sleep/Wake (Pumps, Fans & Pressure Loops)
For constant-pressure booster pumps, tank-level control, or any closed-loop process, the built-in PID (Menu 59-) reads a feedback signal and continuously adjusts frequency to hold a setpoint — and can stop the motor automatically at zero demand.
| Code | Setting | Why / how |
|---|---|---|
| 100 = 04 | PID macro-configuration | The fastest starting point — dedicates AI1 to PID feedback and the integrated jog dial to the reference before you fine-tune anything else. |
| 59.00 | PID feedback assignment — 00* Not assigned · 01 Terminal (AI1) | Must be set to 01 for the PID loop to actually read your pressure/level transducer — easy to miss if you didn’t use the PID macro above. |
| 59.01–59.03 | Proportional / Integral / Derivative gain (0.01–100, 1* / 1* / 0.00–100.0, 0*) | Raise proportional gain if the response is too slow; back it off (along with integral) if the output hunts or oscillates. Most pressure loops leave derivative at 0. |
| 59.05 / 59.11 | Activate internal PID reference (00*/01) / Internal PID reference (0–100%) | Set 59.05=01 to use a fixed internal setpoint (59.11) rather than an external reference — the simplest way to commission a single fixed-pressure booster. |
| 59.06–59.10 | 2/4 preset PID assignment (LI) + preset PID references (25%/50%/75%*) | Switch between multiple fixed setpoints via logic inputs — e.g. a day/night pressure schedule on a booster set. |
| 512.0 / 512.1 | Low speed + Low speed operating time — used together with sleep | A practical recipe: set 512.0 to a low frequency (e.g. 10Hz) and 512.1 to a short dwell time (e.g. 10s) so the drive briefly confirms low/no demand at low speed before actually sleeping, rather than sleeping on a momentary dip. |
| 59.19 / 59.20 | Wake-up level / Wake-up threshold (0–100%, 0%*) | Sets how far the feedback has to drop before the drive wakes and restarts — too sensitive and it short-cycles; too loose and pressure sags noticeably before it responds. |
| 59.25 / 59.26 | PID feedback supervision (00* not assigned · 01 Free wheel · 04 Fallback speed) / Fallback speed | Decides what the drive does if the feedback signal itself is lost (a failed/disconnected sensor) — running at a safe fallback speed is usually kinder to the system than an abrupt freewheel stop. |
💡 Real-world quick recipe (fixed-setpoint booster pump): 100=04 (PID macro) → 401=183 → 59.00=01 (feedback from AI1) → 59.05=01, 59.11=50% (internal setpoint) → 512.0=10Hz, 512.1=10s (low-speed dwell before sleep) → 59.19=5% (wake-up level). Tune the P/I gains (59.01/59.02) last, once the loop is basically holding pressure.
🔧 Fault Management: Reset, Auto-Restart & Fault Inhibition
Decide in advance how the drive should recover from a fault — manually, automatically, or (for life-safety fans/pumps) by continuing to run through certain faults entirely.
| Code | Setting | Why / how |
|---|---|---|
| 601 | Detected fault reset assignment (LI) | Wire a logic input to remotely reset a clearable fault instead of needing to cycle drive power every time. |
| 602.0 / 602.1 | Automatic restart — 00*/01, with a max retry window of 5min/10min/30min/1h/2h/3h/Infinite | Enables the drive to clear certain faults and restart on its own once the cause disappears — useful for unattended pumps/fans, but use with caution on any machine where an unattended restart could be a safety hazard. |
| 614 | Reset previous faults via the Run key — 00*/01 | Lets an operator clear a fault by pressing Run on the keypad itself, without navigating into the fault-reset menu. |
| 610 | Detected fault inhibition assignment (LI) | This is the Fault Inhibition mechanism our general xD1000 product guide describes as “Fire Mode” for tunnel ventilation fans, smoke extraction fans and fire-fighting pumps — a logic input here inhibits and clears specific faults (F007, F025, F028 among them) so the drive keeps running through conditions that would normally trip it during an actual emergency. |
| 605 / 606 / 609 / 611 | Output phase loss / Input phase loss / 4-20mA loss / Modbus fault management — each offer “Detected fault ignored” | These let you individually decide whether a specific non-critical fault stops the drive or is ignored — a deliberate, application-specific decision, not a default to change casually. |
⚠️ Enabling fault inhibition or ignoring a protective fault means the drive (and possibly the motor) can be damaged by the very condition it would otherwise have tripped on. Only use this on equipment where continued operation during an emergency is a deliberate design requirement — verified with a qualified engineer — not as a way to silence nuisance trips on ordinary equipment.
🌬️ Fan Control & Motor Thermal Protection
Two protection settings worth reviewing rather than leaving on default, especially if your motor is smaller than the drive’s rating or has its own separate cooling fan.
| Code | Setting | Why / how |
|---|---|---|
| 513 | Cooling fan control — 00 Fan runs whenever the drive runs · 01* Thermal control | Thermal control (factory default) only spins the drive’s own cooling fan when needed — quieter and extends fan life. Force it to always-on in very dusty/hot environments where you’d rather over-cool than risk a thermal trip. |
| 604.0 | Motor thermal current — 0.2–1.5× In (matches drive rating by default) | Set this to the actual motor’s rated current, not the drive’s, whenever they differ — install external thermal monitoring if the motor’s current is below 20% of the drive’s rating, or if you’re switching between multiple motors on one drive. |
| 604.1 | Motor protection type — 01* Self-ventilated · 02 Motor-ventilated (forced/separate cooling fan) | Self-ventilated motors cool less at low RPM since their own shaft-mounted fan slows with them — the drive’s thermal model accounts for this. If your motor has an independent, constant-speed cooling fan, set 02 for a more accurate (less conservative) thermal curve. |
| 604.2 / 604.3 | Overload fault management (00 ignore · 01* freewheel stop · 08 DC injection stop) / Thermal state memory (00* not stored at power-off · 01 stored) | By factory default the motor’s calculated thermal state resets to zero every power cycle — set 604.3=01 if your process repeatedly power-cycles the drive and you want thermal history to carry over for accurate protection. |
🛡️ Quick Reference: Monitoring & Diagnostic Codes
Press the jog dial in Monitoring mode (MOn) to cycle through these — useful for a quick health check without opening a laptop.
| Code | Reading | Notes |
|---|---|---|
| 801 / 802 | Speed reference / Output frequency (Hz) | 801 is what’s being asked for; 802 is the estimated actual motor speed — compare the two to spot a drive that’s current-limiting or stalled under load. |
| 803 | Motor current (A) | Estimated output current, ±5% accuracy. During DC injection this shows the maximum injected current instead. |
| 807 / 808 / 809 | Main voltage (V) / Motor thermal state (%) / Drive thermal state (%) | 808 and 809 trip Motor Overload (F013) and Drive Overheat (F011) respectively above 118%. |
| 810 | Output power (% of drive rating) | Estimated shaft power versus the drive’s own rating. |
| 811 | Drive status code | –00 Ready · –01 Running · –02 Accel · –03 Decel · –04 DC injection · –05 Current limitation · –06 Freewheel · –09 Auto-tuning · –10 Fast stop · –11 No line power · –13 Remote control · –14 Local control. |
| 901 / 902 | State of LI1–LI4 / State of LO1 & relay R1 | A live view of your digital I/O — the fastest way to confirm whether a wiring or PLC-side signal is actually reaching the drive. |
| 913 | Modbus communication status | r0t0 = idle · r0t1 = transmitting only · r1t0 = receiving only · r1t1 = both — use this to confirm the bus is actually talking before chasing a Modbus fault elsewhere. |
| 914–921 | Last faults 1–4 and drive state at each fault | A rolling history of the last four detected faults, each paired with a bitmask of what the drive was doing at the moment it tripped — genuinely useful for diagnosing an intermittent fault you didn’t see happen live. |
⚠️ Quick Reference: Fault Codes & Troubleshooting
The first fault detected is stored and flashes on the display; the drive locks output and opens the R1 relay contact. Some faults clear automatically once the cause is gone; others need a manual reset or a full power cycle — see the manual’s Diagnostics chapter for the complete breakdown by category.
| Code | Name | Likely cause & remedy |
|---|---|---|
| F001 | Precharge | Charging relay/resistor fault, or unstable mains. Power-cycle, check connections and supply stability. |
| F009 | Overbraking | Sudden braking or load inertia too high. Increase deceleration time, or fit a braking resistor module. |
| F010 | Overcurrent | Motor/load parameters wrong, inertia too high, or mechanical locking. Check parameters, reduce switching frequency (315), verify ground connections. |
| F011 | Drive overheat | Drive temperature too high. Check load/ventilation/ambient temperature; let it cool before restarting. |
| F013 | Motor overload | Excessive motor current. Check motor thermal protection configuration (604-) and actual load. |
| F014 / F015 | 1 / 3 output phase(s) loss | Loose motor connection, motor not connected, or a downstream contactor open. Check drive-to-motor wiring; for test-bench use without a motor, disable Output Phase loss detection (605=00). |
| F016 | Main overvoltage | Line voltage too high, or no run command with 20%+ over-voltage. Check and adjust line voltage; if intermittent, set R1 assignment (205) to overvoltage warning. |
| F017 | Input phase loss | Blown fuse, failed supply phase, or a 3-phase drive run on single-phase. Check supply and fuses; can be disabled (606=00) for unbalanced/special supplies. |
| F018 / F019 / F020 / F021 | Motor / Ground / IGBT / Load short-circuit | Check cable and motor insulation, ground connections, and switching frequency; for F020 specifically, contact Lauritz Knudsen support. |
| F022 | Modbus interruption | Communication bus interrupted. Check bus connections and the Modbus time-out setting (704). |
| F025 | Overspeed | Instability, or inertia-driven overshoot. Check the load/mechanism, consider a braking resistor, and review speed-loop tuning. |
| F026 | PI feedback fault | PID feedback below its lower limit. Verify the PID feedback assignment (59.00) and its supervision settings (59.25/59.23). |
| F027 | IGBT overheat | Drive overheated internally, or load/drive undersized. Reduce switching frequency (315); let the drive cool before restarting. |
| F028 | Autotuning fault | Motor not connected, phase loss, a special motor, or the motor was rotating during the tuning run. Ensure the motor is present, correctly sized and completely stopped before retrying. |
| F029 | Process underload fault | Motor current below the underload threshold for too long. Check the process underload threshold (211) and delay (210) against your actual load profile. |
| F030 | Undervoltage | Line supply too low, or a transient voltage dip. Check the supply and the undervoltage menu (607-) settings. |
| F031–F034 | Incorrect / Invalid / Download-invalid configuration | A configuration mismatch, often after an HMI swap or an interrupted parameter upload. Return to factory settings (102=64) or reload a valid backup, then power-cycle. |
| F033 | AI1 current loss | AI1 configured as a current input but reading below 2mA. Check the terminal connection and the 4-20mA loss behavior setting (609). |
❓ Frequently Asked Questions
My xD1000 won’t start and shows no fault code — what should I check?
✅ This is almost always a control-source mismatch, not a defect. Check whether Fast Stop or Freewheel is assigned to a logic input that isn’t currently powered (the drive shows 502.1 or –00 at freewheel end — this is normal, since these functions are active-at-zero by design). Confirm the run command is actually being sent through the source assigned in Command channel 1 (407), and that Reference channel 1 (401) matches where you’re actually sending speed from. If Modbus is the assigned reference or command channel, the drive will sit at freewheel stop until the bus sends a valid command.
How do I fully reset the drive to factory defaults?
✅ Go to ConF → 102 (Factory/recall customer parameter set), set it to 64, and hold ENT for 2 seconds to confirm. This restores every parameter to its factory value — useful as a known-good starting point before commissioning, or if a configuration fault (F031–F034) won’t clear.
Can I test the drive with a smaller motor, or with no motor connected at all?
✅ Yes. To bench-test without a motor of the same rating, deactivate Output Phase loss detection (605=00) and, in the motor control menu, set Motor control type (309) to 03 (standard). If the substitute motor’s nominal current is below 20% of the drive’s rating, install external thermal monitoring — the drive’s built-in motor thermal protection isn’t accurate that far below its designed range.
My PID loop hunts, or my pump never quite reaches the target pressure — what do I adjust?
✅ Hunting/oscillating usually means the proportional gain (59.01) is too aggressive — lower it first. Never reaching setpoint usually means the gain is too gentle, or the high speed limit (512.2) is capping the drive’s output below what the process needs — raise the gain slightly and check that limit before assuming the pump itself is undersized.
Can I keep a fan or pump running through certain faults during an emergency?
✅ Yes — that’s what Detected fault inhibition assignment (610) is for, tied to a logic input from your fire/emergency system. It’s the mechanism behind what our general xD1000 product guide calls “Fire Mode” for tunnel ventilation fans, smoke extraction fans and fire-fighting pumps. Treat this as a deliberate, application-specific safety decision made with a qualified engineer — not a way to silence ordinary nuisance trips.
⚠️ Before You Program a Drive
This guide is a practical starting point drawn from Lauritz Knudsen’s official xD1000 Installation & Programming Manual (SP51099), Complete Parameters List (SP51102) and Quick Start Guide (SP51101), not a replacement for them. Always confirm menu codes and default values against your specific unit’s firmware on the keypad before committing changes. Wiring and commissioning should be carried out by a qualified electrician, and any safety-critical or life-safety installation — fire mode/fault-inhibited fans and pumps especially — should have final settings verified by a qualified technician before going into service.
🛒 Related xD1000 Resources
✅ xD1000 Series — Features, Specifications & Model Guide — full spec sheet, model-number decoder and wiring reference
✅ Shop all 12 xD1000 models — 0.37kW to 30kW, in stock
✅ Knowledge Base: VFD Installation, Wiring & Programming Guide — start here if you’re new to VFDs