Error stop called because of bltouch error restart with m999

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:Mar...

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

cybercipher

Posts: 4
Joined: Sun Jan 19, 2020 1:20 am

3D Touch Problem — STOP called because of BLTouch error — restart with M999

I’m having a problem with my 3D Touch on my Ender 3 with MKS Gen L It’s been working fine for about a year now. Yesterday I finished a 48hr print and went to start a new print and ran into this problem: Whenever I try to home the Z axis I get a ‘STOP called because of BLTouch error — restart with M999’ error. I’ve seen this error before and it had to do with loose wiring, but this time I have double checked the wiring and everything is fine so it appears to be something else. Maybe the sensor itself is now defective?

Here a video showing the problem


User avatar

William

Site Admin
Posts: 6340
Joined: Tue Jun 07, 2016 9:38 am

Re: 3D Touch Problem — STOP called because of BLTouch error — restart with M999

Post

by William » Mon Jan 20, 2020 9:32 am

:D Hi, you can send the commend «M280 P0 S160» to release the alarm in Repetier Host.
and You can try to use the tool to adjust the probe.

-Keep your mind and try to test it. :)
-Everything will be fun!-Support all Getech printer.
-You can ask me the questions and I will kindly reply.
-Respect others is the best way you can get help!


cybercipher

Posts: 4
Joined: Sun Jan 19, 2020 1:20 am

Re: 3D Touch Problem — STOP called because of BLTouch error — restart with M999

Post

by cybercipher » Tue Jan 21, 2020 7:52 am

Hi! I tried this and here was the result: Setting M280 P0 S0 extends the pin fully and red light turns off. Setting M280 P0 S100 retracts the pin fully and the red light turns on.
That all appears to work as intended, but that does not help solve my problem except to confirm that the servo controls of the device appear to be working fine so the problem probably lies elsewhere. What should I try next?


User avatar

William

Site Admin
Posts: 6340
Joined: Tue Jun 07, 2016 9:38 am

Re: 3D Touch Problem — STOP called because of BLTouch error — restart with M999

Post

by William » Tue Jan 21, 2020 9:13 am

:D You can remove your z-axis limit switch

-Keep your mind and try to test it. :)
-Everything will be fun!-Support all Getech printer.
-You can ask me the questions and I will kindly reply.
-Respect others is the best way you can get help!


cybercipher

Posts: 4
Joined: Sun Jan 19, 2020 1:20 am

Re: 3D Touch Problem — STOP called because of BLTouch error — restart with M999

Post

by cybercipher » Tue Jan 21, 2020 11:32 pm

I removed that a long time ago when I installed the 3D Touch. The printer has been running fine with the 3D touch for about a year before this problem showed up.


User avatar

William

Site Admin
Posts: 6340
Joined: Tue Jun 07, 2016 9:38 am

Re: 3D Touch Problem — STOP called because of BLTouch error — restart with M999

Post

by William » Wed Jan 22, 2020 10:37 am

:D Hi, You can adjust the z-axis and see if the probe is stuck.
I found this: https://github.com/MarlinFirmware/Marlin/issues/8926

-Keep your mind and try to test it. :)
-Everything will be fun!-Support all Getech printer.
-You can ask me the questions and I will kindly reply.
-Respect others is the best way you can get help!


cybercipher

Posts: 4
Joined: Sun Jan 19, 2020 1:20 am

Re: 3D Touch Problem — STOP called because of BLTouch error — restart with M999

Post

by cybercipher » Wed Jan 22, 2020 12:07 pm

Thanks for that, I ran through those commands and throughout all of the tests the M119 result always z_min: TRIGGERED
The pin moves and the light turns on/off but It never returns OPEN
I checked the wiring again and am really very sure it’s fine and nothing came loose.


User avatar

William

Site Admin
Posts: 6340
Joined: Tue Jun 07, 2016 9:38 am

Re: 3D Touch Problem — STOP called because of BLTouch error — restart with M999

Post

by William » Wed Jan 22, 2020 1:11 pm

:D Hi, In the test of the limit switch, if you do not hold down z endstop
Z_min: TRIGGERED appears
The limit switch is abnormal;

If the screw of the 3d touch is adjusted, the magnetism of the probe is guaranteed;
But still the situation you described before,
There may be problems caused by 3d touch itself.

-Keep your mind and try to test it. :)
-Everything will be fun!-Support all Getech printer.
-You can ask me the questions and I will kindly reply.
-Respect others is the best way you can get help!


Hy everyone, i just had the chance to install a cheap 3d touch, that i had laying around from a long time, to my ender 3 pro but i keep getting this error when i want to level the bed.

I have an mks gen l v1.0 motherboard with tmc2208 for XYZ and A4988 for E , tft28 v4 touchscreen, i have just flashed Marlin 2.1.2. Also i have 2 5015 fans installed.
i have followed several videos and tutorials for installing this touch probe, G28 sometimes work sometimes it doesn’t, it homes X/Y then goes to the middle, raises up a little, stays, probe down, come up then probe again but at the first or second time for sure i will get this error sayng that is something wrong with the bltouch. If it manages to pass the G28 and i send G29, it preheats then goes to the first corner and the error pop after the first probe.

The wires that come out of it are soldered directly to the long ones that goes to the motherboard where i have some connectors that i have squishes a little so i can fell that they make good contact with the pins on the board. the connections are as in the diagram for the mks gen l, black/white to z end stop — gnd/sign, the others to the servo pins.

i also have messed with internals, the wires are soldered good inside, i have magnetized the magnet again and it atracts verry well so i have changed the termo tube and cut it a bit longer so that the set screw doesn’t get in contact with the magnet directly but instead there is a bit of a distance enough for the coil to attract and reject it down. there was a play in the channel where the tip goes inside, the part with the magnet on top had room to go around since the hole in the plastic was bigger (hence the tip doesn’t stay perfectly straight) and i have placed another layer of termo tube just on the top of the magnet so it fills a bit more the space but still has room to move a bit, it work even if it not perfectly straight with the plastic housing.

i have tried different distances for the set screw so that is closer/further away and i got better results when it was closer for that i am thinking that there might be a time that is exceeded when it takes a bit longer for it to engage when the screw is further up and has to move more. Or the magnetic field that measure something might be messed.

At some point i got the error «echo:endstops hit: z:-0.11» (and even bigger like ~ -1.X i think) wich i don’t understand since it homes first with G28 then G29 gives me this. Isn’t the 0 position the one first measured with G28? i haven’t moved anything just the z axis moved by g code some mm up that is set in the firmware

Here are all the changes i have done in marlin so far for everything i have on going with the printer:
Changes in configuration.h marlin;

#define MOTHERBOARD BOARD_MKS_GEN_L //1113
#define X_DRIVER_TYPE TMC2208_STANDALONE
#define Y_DRIVER_TYPE TMC2208_STANDALONE
#define Z_DRIVER_TYPE TMC2208_STANDALONE
#define E0_DRIVER_TYPE A4988
#define DEFAULT_AXIS_STEPS_PER_UNIT { 80, 80, 400, 98.34 }
#define PREHEAT_BEFORE_LEVELING
#define LEVELING_NOZZLE_TEMP 200 // (°C) Only applies to E0 at this time
#define LEVELING_BED_TEMP 60
//#define SPEAKER
#define BLTOUCH
#define PROBING_MARGIN 20
#define NOZZLE_TO_PROBE_OFFSET { -56, -18, 0 }
#define MULTIPLE_PROBING 2
//#define MIN_SOFTWARE_ENDSTOP_Z
#define AUTO_BED_LEVELING_BILINEAR
checked if defined #define Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN
#define ENABLE_LEVELING_FADE_HEIGHT
//#define RESTORE_LEVELING_AFTER_G28
#define EXTRAPOLATE_BEYOND_GRID
#define Z_SAFE_HOMING
#define SLIM_LCD_MENUS
#define ENDSTOPPULLUP_ZMIN_PROBE
#define FAN_SOFT_PWM
#define SOFT_PWM_DITHER
#define SOFT_PWM_SCALE 1
#define PROBING_HEATERS_OFF
//#define WAIT_FOR_HOTEND
#define DELAY_BEFORE_PROBING 200

Changes in configuration_adv.h

#define BLTOUCH_DELAY 500
#define E0_AUTO_FAN_PIN 7 //for hotend fan
#define BABYSTEP_ZPROBE_OFFSET
#define BLTOUCH_FORCE_SW_MODE

Also if there is anything i have to modify for the serial com to work and not interfere with the tft screen would be great, the SERIAL_PORT -1/#define SERIAL_PORT_2 0 doesn’t allow me to set to -1. It works now but just to be sure that they don’t interfere.

I would really appreciate some help from anyone!
Regards, Alex!

Attachments:

open | download —
327058435_6438169519545409_7848155813561498630_n.mp4
(5.55 MB)

Понравилась статья? Поделить с друзьями:
  • Error stop 00000
  • Error stoi is not a member of std
  • Error steering angle control unit e53
  • Error steamworksauthfail among us что делать
  • Error steamworksauthfail among us на пиратке