DJScopeSOFM/Two-Trees-Multi-Printer-Marlin-Bugfix-Compiler

UBL moves Z in wrong direction

Closed this issue · 19 comments

The UBL cold mesh probe moves the Z in the wrong direction, its moving away from the probe.

I have tmc 2209 on x, y and e0, tmc 2208 on z and e1

I have it set like this:

  #define INVERT_X_DIR true
  #define INVERT_Y_DIR true
  #define INVERT_Z_DIR true

  #define INVERT_E0_DIR true
  #define INVERT_E1_DIR true 

which printer?

On my plus I have z and E1 set to false. I have 2209 on all

Sapphire Plus

for some odd reason, while im trying to print the kfactor calibration its just doing a bunch of filament changes

im starting to think my board is defective, getting heater failed alarms also

the only thing is that everything works fine with Lester JW's firmware, just no advanced features like linear advance :(

I've added a section in setup where you can change the direction of the motors.

im using that, the issue is only with auto bed level.

Can you send your configuration,h configuration_adv,h and setup.h files?

20201205_002330_HDR
20201205_002316_HDR
20201205_001620_HDR
20201205_002255_HDR

I don't see any issues with your setup. I just did a merge with the latest sources. Can you please update and report back if you've still got the issue?

Do I need to disable the SOFTWARE_DRIVER_ENABLE?

im using standalone mode on all drivers

If you're using standalone than it shouldn't matter.

probe does a few self tests then the bed moves up some amount and then nothing else happens

how do you have the BLTOUCH connected?

pw_det
blue is connected to the green wire on the wire extension.

I have a feeling that the 3pin is not wired correctly. It looks like it's getting an inverted signal. Can you swap the signal and 5V pins?

16073913422927008055438675608524
16073913897109175482696334331418

I checked the continuity between the connector on the bltouch and theconnection of the extender.
3dtouch was working on Lester's firmware

You seem to be the only one with this issue...

I found the issue, I was using what was infact mt_det1, two trees sapphire plus manual thats included labelled that as power failure that I assumed was pw_det.

Good to here that you've found the issue.