Topics created by izeman

@izeman yeah, add a G4 P200 before the final check to allow the IO to refresh.

Two ways to deal with it.

Change the M208 settings so the max values correspond to the actual physical position when the endstop sensor is triggered

Use G92 to adjust the logical X and/or Y position so the position at the center is correct. Put the G92 in the homing file of X and/or Y with the values needed to obtain the correct center position. One way to do this is have a G1 command at the end of the homing file with the value needed to move to the center and then have a G92 command with 0 as its value to set the logical position to 0, thus matching the physical position. For example in homeX.g you might have: G90 G1 Xnnn G92 X0

Two issues with that:

So instead of saying I can move 250/250 I tell the printer it can only move 250-10/250-15? It's not easy to find the "real" 0/0 when you're homing at some random 250/250 (which in reality could be 248/251 or something else) and then re-iterate from there where your real "0/0" is. Isn't it?

When I use G92 to move the working coordinates I have the issue that it can't pick up the klicky probe after homing again as it's location has change then ...

@izeman said in Is there a need to upgrade my stepper drivers?:

THIS is the bench of HORROR

Nah, I can still see bench space!

Ian

@izeman I've added a note to the documentation: https://docs.duet3d.com/en/User_manual/Connecting_hardware/Display_12864#overview

As of September 2023, BTT firmware still MOSTLY works with RRF. Heating, movement, monitoring prints etc works, however accessing the Duet filesystem does not. There may be other quirks that break RRF support as the firmware develops. Duet3D is not responsible for the BigTreeTech firmware; please contact BTT to get these fixed. See this thread on the forum for more information.

You could raise an issue on Github, though it looks like BTT isn't doing much of the development work. A similar issue here https://github.com/bigtreetech/BIGTREETECH-TouchScreenFirmware/issues/2569 seems to have gone unanswered, except for a link to this explanation, which might explain why you can't access the file menu https://github.com/bigtreetech/BIGTREETECH-TouchScreenFirmware/issues/2572#issuecomment-1217818116

With remote printing engaged, the TFT has no idea of the host managing the print (it can be OctoPrint or any other unknown client) so the only safe rule that can be followed by the TFT is simply to act as passthrough between remote host and mainboard (the TFT is simply providing the communication channel with the mainboard). Furthermore, the TFT does not support response forwarding for request originated by the TFT (e.g. M601). Even if the TFT supported the response forwarding, the TFT couldn't make any assumption about the handling provided by the remote host receiving the response (e.g. the remote host could discard the notification and continue the print).

For those reasons and for the concept of remote printing (something fully controlled by the remote client), the TFT's role is limited to display stats info and nothing more.

Ian

Zarrsito created this issue in bigtreetech/BIGTREETECH-TouchScreenFirmware closed [Q] BTT E3 RRF V1.1 & TFT35 E3 3.0.1 Issue or wrong config? #2569 Rneil-ca created this issue in bigtreetech/BIGTREETECH-TouchScreenFirmware closed [FR] Send Pause and Stop Command While Remote Printing #2572

@jay_s_uk said in "Error: Probe already triggered at ...." based on location??!:

@izeman sounds like a wiring issue then and moving passed a set point pulls a wire

OH MAN! Seems it REALLY IS A WIRING ISSUE. I checked all connectors, measured for short and voltage before. Twice, three times, but it seems the long wire coming from the board is broken somewhere.
I can trigger the PINK 1000 by moving the wire.

THANKS!!

@droftarts Seems your tips may have worked. No problems so far. And I also ordered replacement pins for my bltouch.
Keep your fingers crossed,

Thank you all!

@gloomyandy said in Babystepping and 12864 goes crazy:

@izeman @izeman When I was doing some testing of these displays I found it was relatively easy to end up with the rotary switch positioned "bewrween" two of the steps which seemed to result with some odd combination of the switch output that resulted in constant change of the value. I wonder if you might be seeing this?

I thought so too, but it's working perfectly fine for EVERYTHING else. And once you set it to E4 it works as expected as well. But of course I have no idea how the encoder and debouncing is handled by the firmware ...

@t3p3tony Much appreciated. Thank you!

@t3p3tony, @dc42 I ordered mine from here: https://www.aliexpress.com/item/33025401119.html?spm=a2g0s.9042311.0.0.27424c4dHiZgRO