Alarm 195 occurs when critical machine parameters requiring initialization during boot sequence have been modified. The NGC control prevents operation until a complete power cycle loads the new parameter values into active memory.
HaasServo/AxisBasic10-30 minutes
195
Haas 195 - B CABLE FAULT | Haas CNC Alarm
B CABLE FAULT
The MOCON board has detected a communication or electrical fault on the B-axis motor cable circuit, typically indicating an open connection, short circuit, or signal integrity problem between the servo amplifier and motor encoder or power connections. The control continuously monitors cable continuity and proper electrical characteristics through the feedback loop, and this alarm protects against operation with compromised cabling that could cause runaway motion or position loss.
Root Cause Summary
Alarm 195 occurs when critical machine parameters requiring initialization during boot sequence have been modified. The NGC control prevents operation until a complete power cycle loads the new parameter values into active memory.
Safety
Always perform a controlled shutdown using the control's POWER OFF button before disconnecting main power to avoid corrupting the operating system or parameter memory.
After rebooting from encoder or feedback parameter changes (Parameters 100-119), jog axes at reduced feedrate (10-25%) initially to verify servo stability before running production programs, as incorrect encoder settings can cause sudden runaway or following errors.
Causes and Fixes
1
Verify Parameter Changes
Press SETTING, then PARAMETERS. Check if any parameters in ranges 70-99 or 200-299 show asterisk (*) indicating recent modification.
Use SETTING > ALARMS > HISTORY to see exactly which parameters were changed and when.
2
Document Current Settings
Write down or photograph the modified parameter values before power cycle in case rollback is needed.
Incorrect servo parameters can cause axis runaway or damage.
3
Perform Complete Power Cycle
Turn main power switch OFF, wait 10 seconds for capacitors to discharge, then turn ON. Allow full boot sequence to complete.
Watch for any new alarms during boot that might indicate parameter conflicts.
1
Check I/O Parameters
Navigate to SETTING > PARAMETERS and review parameters 10-69 for asterisk markings indicating recent changes to I/O, spindle, or ATC settings.
Parameter 11 (spindle type) and 50-series (I/O assignments) are most commonly modified.
2
Verify Hardware Connections
If I/O assignments were changed, confirm physical wiring matches new parameter settings before power cycle.
Mismatched I/O assignments can cause unexpected machine behavior or safety system failures.
3
Execute Power Cycle
Turn main disconnect OFF, wait for all LEDs to extinguish, then turn ON. Monitor I/O status lights during initialization.
Use SETTING > DIAGNOSTICS > I/O to verify all inputs/outputs function correctly after reboot.
1
Identify Network Parameter Changes
Go to SETTING > PARAMETERS and check 310-349 range for modifications, particularly parameters 310 (Ethernet enable), 311-314 (IP settings).
Parameter 340-349 control DNC and FTP settings that also require power cycle.
2
Record Network Settings
Document IP address, subnet mask, and gateway settings before power cycle to verify correct initialization.
Incorrect network settings may prevent remote access or DNC operation.
3
Power Cycle and Test Connectivity
Perform complete power OFF/ON cycle, then test network connectivity using SETTING > NETWORK > PING TEST after reboot.
Allow 2-3 minutes after boot before testing network functions for full initialization.
1
Review Option Parameters
Check SETTING > PARAMETERS 37-46 for changes. Common ones include Parameter 37 (4th axis), 39 (probe), 44 (tool measurement).
Match parameter settings to actual installed hardware options to avoid initialization errors.
2
Verify Hardware Installation
Confirm that enabled options have proper hardware installation and connections before power cycling.
Enabling options without proper hardware can cause boot failures or erratic operation.
3
Complete Power Cycle
Turn main power OFF, wait 15 seconds, turn ON. Watch boot messages for option initialization confirmations.
Check SETTING > DIAGNOSTICS > OPTIONS after boot to verify all enabled options are properly detected.
1
Identify System Parameter Changes
Review parameters 1-9 and 350+ range for recent modifications affecting system memory, program storage, or control behavior.
Parameter 7 (memory lock) and 350+ (system configuration) most commonly require power cycle.
2
Backup Critical Data
Save programs and offsets to USB or network location before power cycle as precaution against memory issues.
System parameter errors can potentially affect program storage or offset retention.
3
Perform Extended Power Cycle
Turn OFF main power, wait 30 seconds for complete memory discharge, turn ON and allow full boot sequence including memory tests.
Monitor boot messages for any memory or system initialization errors that might indicate parameter conflicts.
DIY Feasiblehigh confidence
Call a technician if:
·Parameters were changed accidentally and original values unknown
·Power cycle doesn't clear alarm
·New alarms appear after power cycle
·Machine behavior abnormal after parameter changes
Prevention
Document parameter values before making changes
Make parameter changes during scheduled downtime
Understand which parameters require power cycle before modification
Use parameter backup/restore function before major changes