axismd.ai
Heidenhain Controller
Servo/Axis · Intermediate · 30-120 minutes
Heidenhain 231-6850 - 6850 CC (log): LSV2 test command for FS error injection
This log entry confirms that an LSV2 test command was successfully received by the control to inject a fail-safe error condition, which is a normal diagnostic procedure. It is not indicative of a malfunction but rather a verification that safety-related diagnostic communication channels are operational. This typically occurs only during service, commissioning, or functional safety validation activities.
231-6850
Heidenhain 231-6850 - 6850 CC (log): LSV2 test command for FS error injection
6850 CC (log): LSV2 test command for FS error injection
This is a diagnostic log entry, not a critical alarm. It indicates that an LSV2 (Leitstand-Verbindung 2) test command was executed to intentionally inject a fail-safe (FS) error for testing purposes. This typically occurs during commissioning, service diagnostics, or when using TNCremo/TNCtest software for functional safety verification.
Root Cause Summary
This log entry confirms that an LSV2 test command was successfully received by the control to inject a fail-safe error condition, which is a normal diagnostic procedure. It is not indicative of a malfunction but rather a verification that safety-related diagnostic communication channels are operational. This typically occurs only during service, commissioning, or functional safety validation activities.
Safety
- Refer to Heidenhain service manual
- Ensure qualified technician performs repairs
Causes and Fixes
- 1
Verify Active LSV2 Connections
Press MOD key, navigate to System Messages, then select 'CC Log' to review the complete log entry including timestamp and connection details. Note the exact time and correlate with any service activities.
The CC log will show the source IP address or connection identifier if the LSV2 command came from external software.
- 2
Check for Active Service Software
Look for TNCremo or TNCtest windows on connected service laptops or network terminals. Verify with service personnel if functional safety testing is in progress.
Do not interrupt ongoing safety function tests as this may invalidate acceptance test protocols required for SIL certification.
- 3
Review Test Documentation
If this occurred during commissioning, verify that the test is documented in the machine acceptance protocol. This log entry may be required evidence for functional safety validation.
Export the CC log via MOD > System Messages > CC Log > [BACKUP] to include in commissioning documentation.
- 4
Clear Log Entry if Test Complete
Once test completion is confirmed, the log entry can remain for documentation purposes. No action is required unless repeated unexpectedly outside of test procedures.
Call a technician if:
- ·FS system shows actual safety faults
- ·LSV2 parameters are corrupted
- ·Network hardware failure suspected
Prevention
- Properly close all diagnostic sessions before disconnecting tools
- Schedule FS testing during planned maintenance windows
- Maintain stable network connections during commissioning
Common Mistakes
- Ignoring the alarm assuming it's just a test
- Modifying LSV2 parameters without understanding their function
- Not verifying FS system status after clearing the alarm
Seeing Multiple Alarms?
Seeing another alarm with this one? Enter the code.
Get machine-aware diagnosis
AxisMD logs alarms against your actual machines, tracks patterns, and gives AI context your manual doesn't have.
Start freeWas this guide helpful?
Always verify with your machine manual or a certified technician before performing service procedures.