Ошибка м999 3д принтер

При включении принтера ТО показывает просто заредельную(999),через некотороевремя проскакивают участки,в которых можно ,допустим прогреть стол но не более ≈180 градусов.И такая ерунда каждый раз.Искал,но ничего не нашел.

Ответы на вопросы

Two immediate issues I can think of are:

• Do the floppy drive and DVD drive stepper motors have sufficient torque to turn whatever you have connected them to? You don’t say what sort of printer you have built, but a holding toque of 44 N·cm (62oz·in, 4.5kg·cm) or more, is desirable. Maybe you should consider upgrading your floppy ad DVD drive motors to Nema 17 motors… See RepRapWiki — Nema 17 for more details.
• Do you have the correct thermistor selected in the firmware? Check your firmware configuration file.

To further check the thermistor, disconnect it from the RAMPS board, and using a multimeter, check its resistance at room temperature. Then compare it with the temperature characteristic graph of your thermistor type. A general 10K thermistor has the following response curve (source):

Does the reading that your multimeter gives, seem reasonable?

Also check the RAMPS thermistor input, by shorting the thermistor pins on the RAMPS board (using a jumper). What is the temperature reading now? It should be whatever MAX_TEMP is defined as, typically around 400°C. Again, check your firmware configuration file.

In addition, M999 is not an error, but a command used to reset the firmware/printer, after an error has occurred.

Hello,

I’ve been working on getting a BLTouch sensor to my prusa i2. I’m running ramps 1.4 and octoprint. When my octopi starts this is what the terminal outputs:

Recv: start
Recv: echo:Marlin 1.1.6
Recv: 
Send: N0 M110 N0*125
Recv: echo: Last Updated: 2017-10-10 12:00 | Author: (none, default config)
Recv: eN0 M110 iled: Dec 28 2017
Recv: echo: Free Memory: 5215  PlannerBufferBytes: 1232
Recv: echo:V41 stored settings retrieved (498 bytes; crc 23991)
Recv: echo:  G21    ; Units in mm
Recv: 
Recv: echo:Filament settings: Disabled
Recv: echo:  M200 D3.00
Recv: echo:  M200 D0
Recv: echo:Steps per unit:
Recv: echo:  M92 X80.00 Y80.00 Z4000.00 E97.00
Recv: echo:Maximum feedrates (units/s):
Recv: echo:  M203 X250.00 Y250.00 Z2.00 E22.00
Recv: echo:Maximum Acceleration (units/s2):
Recv: echo:  M201 X1000 Y1000 Z5 E1000
Recv: echo:Acceleration (units/s2): P<print_accel> R<retract_accel> T<travel_accel>
Recv: echo:  M204 P500.00 R500.00 T500.00
Recv: echo:Advanced: S<min_feedrate> T<min_travel_feedrate> B<min_segment_time_ms> X<max_xy_jerk> Z<max_z_jerk> E<max_e_jerk>
Recv: echo:  M205 S0.00 T0.00 B20000 X20.00 Y20.00 Z0.40 E5.00
Recv: echo:Home offset:
Recv: echo:  M206 X0.00 Y0.00 Z0.00
Recv: echo:Auto Bed Leveling:
Recv: echo:  M420 S0 Z0.00
Recv: echo:PID settings:
Recv: echo:  M301 P22.20 I1.08 D114.00
Recv: echo:Z-Probe Offset (mm):
Recv: echo:  M851 Z0.00
Recv: Error:STOP called because of BLTouch error - restart with M999
Changing monitoring state from 'Connecting' to 'Error: STOP called because of BLTouch error - restart with M999
'
Recv: Error:Printer stopped due to errors. Fix the error and use M999 to restart. (Temperature is reset. Set it after restarting)
Recv: ok
Changing monitoring state from 'Error: STOP called because of BLTouch error - restart with M999
' to 'Offline'

I’m able to restart the serial connection and run Gcode commands. I found some troubleshooting suggestions here and this are the results of my testing:

1. Blue LED will be ON if a servo signal is present. Blue LED is faint.
   Result: Blue LED is on
2. M119 ; should return OPEN. If not check that the BLTouch is enabled in the configuration. If enabled then check wiring and check that the correct pin is being used.
   Result: Open
3. M280 P0 S10 ; should deploy the probe and the orange LED will be OFF.
   Result: probe acted as it should
4. M119 ; should return OPEN
   Result: Open
5. M280 P0 S90 ; should stow the probe and the orange LED will be ON
   Result: probe acted as it should
6. M280 P0 S60 ; puts it into the M119 test mode.
7. The probe should remain stowed and the blue LED should be OFF.
   Result: probe acted as it should
8. M119 ; should return TRIGGERED
   Result: probe acted as it should
9. M280 P0 S160 ; returns it to normal operation
10. M119 ; should return OPEN.
    Result: Triggered

This is the output of terminal when I run G29:

> Send: G28
> [...]
> Recv: echo:busy: processing
> Recv: X:100.00 Y:100.00 Z:0.00 E:0.00 Count X:8000 Y:8000 Z:0
> Recv: ok
> [...]
> Send: G29
> [...]
> Recv: echo:busy: processing
> Recv: Error:STOP called because of BLTouch error - restart with M999
> Changing monitoring state from 'Operational' to 'Error: STOP called because of BLTouch error - restart with M999
> 
> Recv: Error:Printer stopped due to errors. Fix the error and use M999 to restart. (Temperature is reset. Set it after restarting)
> Recv: echo:busy: processing
> [...]
> Recv: echo:busy: processing
> [...]
> Recv: echo:busy: processing
> [...]
> Recv: Error:Probing failed
> Recv: X:5.00 Y:0.00 Z:25.00 E:0.00 Count X:402 Y:2 Z:100000
> Recv: ok

I’ve attached is my configuration.h file. If anyone has any suggestions about what my next step to get the sensor and printer running correctly I would certainly appreciate it.

Thanks so much!

20171228_Marlin1.1.6config_h.txt