Decoding Siemens MASTERDRIVES DriveMonitor Hex Parameter Values

Overview

The Siemens SIMOVERT MASTERDRIVES family (converters 6SE70 / 6SE70-MC / 6SE70-VC) communicates engineering data to commissioning tools through DriveMonitor and the successor STARTER commissioning platform using a mix of fixed-point, floating-point, hexadecimal, and bit-coded formats. Decimal parameter values (P554 = 1, P554 = 65, etc.) are read directly, while signal-source and bit-coded parameters are translated to hexadecimal because the integer value is a packed bit field or a connector/binector index. This produces readings such as 0x1001, 0x2111, or 0x2011 in the parameter editor.

A 6SE7038-2EH85 is the Siemens catalog designation for an MC-series MASTERDRIVES inverter in the 38-class (approx. 700 V DC class / 660-690 V AC 3-phase) frame, sized for 38 A armature/line current with a 2-style book-size construction and EH85 control electronics. When commissioning this unit through DriveMonitor V05.05.00.01_00.00.02.94, every parameter that selects a binector (boolean signal source) or connector (analog/word signal source) inside the firmware will display a hexadecimal source address, not a text description. The reading is correct, but untranslated, because the firmware-32 display library of DriveMonitor releases prior to V05.10 does not contain all textual mappings for MC firmware 02.xx and later. Reading the value as raw firmware data still reveals the underlying bit assignment.

Control Word Architecture

The Siemens MASTERDRIVES defines a 16-bit control word (German: Steuerwort, abbreviated SSt) that is interrogated by the inverter every 2 ms (equivalent to one time slice at the default 10 kHz current-loop tick, sub-multiple 5). Bit assignments are firm-defined by firmware and printed in the operating instructions as Figure 4.4 (FC) / Figure 4.4.2 (MC). The mapping for firmware 02.xx and later is:

The status word (German: Zustandswort, ZSW) mirrors the same indexing but reflects drive telemetry. Common status bits include:

Parameter P554 Source Mapping

P554 is the master Control Word Bit 0 source selector on the MC build. The expected raw numeric value is the binector address, an integer that DriveMonitor formats as hexadecimal because the firmware stores it as an unsigned 16-bit index. The most common mapping referenced in 6SE70 commissioning guides is:

The DriveMonitor firmware database may carry the binector-to-text mapping for the most common indices (terminal DI inputs) but will show raw hex where the routing crosses fieldbus, parameter-data-set, or compounded bit-assignment paths. Where 0x2111 is shown and the manual excerpt does not list it, the value should be interpreted as not yet labeled in the engineering tool version in use rather than as a missing or invalid entry.

Compound Parameters P312 and P315

The values appearing in P312 and P315 are not encrypted or random nibble-patterns; they are nibble-coded configuration words in which each 4-bit half-byte selects a function.

P312 — Current-controller average mode

P312 selects the averaging mode used by the IDC-current regulator inside the MASTERDRIVES MC firmware function block Id control (Figure 4.4.2 of the RRU / Id Firmware Operating Instructions shipped with 6SE7038 builds).

P315 — Pulse-pattern / firing mode

P315 selects the firing-pulse pattern in conjunction with the relevant firmware function. The nibble structure is preserved on select MC firmware 02.xx branches. Always verify against the firmware-revision-specific operating instructions because late-revision firmware may repurpose the upper nibble to vector-control or dead-time compensation.

Hex-to-Bit Decoding Procedure

Where the manual does not give the source behind a hexadecimal display, perform this engineer-grade decode sequence in DriveMonitor or STARTER:

1. Capture the raw value in integer mode (decimal) by switching the parameter display to DEC under Settings -> Display format. The decimal equivalent, not the hex text, is the canonical value used by the firmware.
2. Convert to binary using a calculator. Each bit corresponds to a fixed signal source per the binector table; for MC firmware 02.xx the standard binector map is in the operating instructions section "BICO converters".
3. Cross-reference each set bit against the binector numbering scheme. Upper nibble commonly designates the source class (digital input, USS slot, Profibus, PMU, internal flag). Lower nibble designates the bit/terminal index inside that class.
4. Confirm with the live trace by setting DriveMonitor online and dragging the suspected binector onto a trace channel (x-power x-numeric value) together with the parameter under investigation.
5. Document the result in the commissioning log so future field service engineers reading the same hex string can resolve without firmware manuals.

Worked Example: 0x1001 Decoded

Hex   : 0x1001
Bin   : 0001 0000 0000 0001
Upper nibble 0x1 : Digital input class
Lower nibble 0x1 : Terminal 1
Result: P554 is sourced from terminal X101.1 (binector B1025 by MASTERDRIVES routing)

Worked Example: 0x2111 Decoded

Hex   : 0x2111
Bin   : 0010 0001 0001 0001
Upper nibble 0x2 : USS / serial field bit class
Middle byte      : 0x11 (slot 1, channel 1)
Lower nibble     : 0x1 (bit index 1)
Result: P554 is sourced from Profibus/USS slot 1, channel 1, bit 1

DriveMonitor Tool Configuration

DriveMonitor V05.05.00.01_00.00.02.94 with release baseline V05.05.00.00_20.00.00.00 ships a default text mapping library that supports firmware 02.0x baseline. To extend the translation table for later MC firmware revisions:

1. Launch DriveMonitor and connect via PROFIBUS, USS, or RS232-C (MPI on the SICOM interface, baud 19 200-115 200 bps depending on option board).
2. Open File -> Update Device Database and verify that the latest device description files (DDP, .dpv variants) are loaded from the Siemens Industry Online Support portal for 6SE70 / SIMOVERT.
3. Select Tools -> Option Packages and confirm that "Drive ES" option bit for HEXEXT or extended COM-Master is enabled if fieldbus source mapping beyond DI is required.
4. Restart DriveMonitor to refresh the parameter browser cache.

Version compatibility matrix

Where a translated descriptor is missing, the workaround is to either (a) upgrade DriveMonitor to V05.10 or later, (b) migrate to STARTER (Siemens part number 6SL3072-0AA00-0AG0 for license) which carries an updated COM database, or (c) keep DriveMonitor and rely on the manual BICO table for manual decode as covered above.

Status Word Decoding in Online Mode

For online monitoring of a running 6SE7038-2EH85, DriveMonitor exposes the live status word through parameter r0002 (firmware-32 parameter model: status word, decimal) and r0003. The values are produced already in decimal; to interpret hex:

1. View r0002 in decimal (e.g., 0x6F03 displayed under hex mode). Note the running pattern.
2. Switch to bit-level visualization via Tools -> Display -> BICO bit inspector.
3. Match against the ZSW table above. A value of 0x6F03 decodes to bits 0, 1, 8, 9, 10, 11, 12, 13 which corresponds to "Ready to switch on + Ready to operate + speed reached + n-controller released + drive running + direction active + torque limit reached".

Field Commissioning Verification

After resolving any hex-source parameter that drives a safety-rated input, perform this verification sequence before returning the drive to production:

1. Source freeze: Write-read-back each affected P-number (P553-P567 family) and confirm that the decimal value persists through a drive cold start (power off, capacitor discharge > 5 minutes for 690 V MC class).
2. Safe stop route: Wire the hard-wired OFF2 (terminal) through a path that cannot be overridden by software, then pulse OFF2 by removing the source edge. Output stage must pulse-suppress within 50 ms.
3. Bench trace: With motor unloaded, capture r0002 status word trace, P554 effective source bit, and DI1 line through TraceX into a .trc file; confirm source bit-to-DI mapping matches the decoded plan.
4. Fault injection rehearsal: Trip an F-coded fault (e.g., F011 overcurrent) and verify that Acknowledge (StW bit 7) reaches the firmware via the route selected by your hex source, not via an unintended alternate route such as USS slot 0 or PMU button.
5. Document sign-off by recording the binector trace route, software revision, the operator panel version, and the date in the device's parameter card (DriveMonitor File -> Save Parameter Set).

Common Pitfalls and Field Notes

The following are the most frequent field issues encountered on 6SE70 / 6SE7038 hardware:

• Hex value mistaken for a fault address. 0x1001 is not a fault code; the F-coded fault indices are 0xFxxx values (visible only on the F-queue).
• Writing hex to a display-only parameter. P and r parameters are not interchangeable. Hex like 0x2011 shown for an r-parameter must never be entered back to the firmware as a P write.
• Safety inputs routable by software. STOP-C, Stop-D safe functions on the 6SE70 use a separate terminal path through the option board (S01/S02). Hex control-word bit selection is not a substitute for the safety wiring.
• DriveMonitor language file drift. When the connected drive firmware exceeds the DriveMonitor version baseline, some binector indexes revert to hex even for normally-text-displayed sources (DI1, DI2, DI3). Confirm by checking the firmware hash shown in DriveMonitor against the device database version.
• P312/P315 changed silently after firmware update. Firmware 02.xx to 03.xx migrators may shift the nibble significance for current-control mode. Always re-write P312 / P315 after a firmware upgrade.
• PROFIBUS header bit confusion. Slot 0 word-and-bit indexing into the binector table is non-intuitive; 0x2111 often looks similar to 0x2011 and is often mistaken for one. Maintain a project-specific mapping table in the engineering repository.

Cross-Reference Summary Table