Skip to content

Parameter index

Every drive parameter that this project touches, with the value it must hold and the reason. Restored from WT_MS_1's bring-up notes and WT_MS_2's diagnosis.

Application setup

Parameter Name Value Why
99.02 APPLIC MACRO 1 ABB Standard macro. Other macros change the register map and the parameter visibility.
99.07 MOTOR NOM FREQ 60 Hz Motor nameplate. Used by the drive for internal scaling.
99.08 MOTOR NOM SPEED ~880 RPM Motor nameplate. Used as 100 %-reference in fieldbus scaling. WindTunnelControl.ps1 reads this at launch.

Fieldbus / communication

Parameter Name Value Why
98.02 COMM PROT SEL 4 (EXT FBA) RETA-01 is active.
51.03 DHCP 0 (disabled) We use a static IP.
51.0451.07 IP octets 1–4 192, 168, 50, 10 RETA-01 address.
51.0851.11 Netmask octets 1–4 255, 255, 255, 0 Standard /24.
51.16 PROTOCOL 0 Modbus/TCP, ABB Drives profile. Other settings = different register map.

Command sources

Parameter Name Value Why
10.01 EXT1 COMMANDS 10 (COMM) Start/Stop from Modbus. Without this, the drive ignores fieldbus start commands.
11.02 EXT1/EXT2 SEL 0 (EXT1) EXT1 is the active command source.
11.03 REF1 SELECT 8 (COMM) REF1 (speed setpoint) from Modbus. Without this, REF1 writes are silently ignored.

Limits and ramps

Parameter Name Value Why
20.01 MAXIMUM FREQ (site-specific) Hard upper limit on output frequency. Verify before changing.
20.02 MINIMUM FREQ (site-specific) Hard lower limit on output frequency.
22.02 DECEL TIME (site-specific) Ramp-stop time. Too short causes overvoltage faults at high speed.
22.01 ACCEL TIME (site-specific) Ramp-up time.

The exact values for the limits and ramps depend on the motor and load; they are not documented as fixed constants here. The right values were set during the drive's initial commissioning and should be left alone unless the motor or fan is changed.

Reading parameters over Modbus

Address = group × 100 + index − 1.

Examples:

  • 10.01 → address 1000
  • 11.03 → address 1102
  • 51.04 → address 5103
  • 99.08 → address 9807

Where the dump lives

When we run a full parameter dump (planned per Maintenance → Schedule), the output CSV goes into WT_MS_<n>/captures/. The most recent dump is the authoritative snapshot; this page is the human-readable summary.