@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

@Markcus

M587 S”XY1789" P”Jake78"

It looks like in your command you used curly quotes. Make sure you're using straight quotes in all commands, ie " rather than curly quotes, ie ”. Also, you didn't get an 'ok' after the command, so it didn't go through.

SerialTools works, but is a bit finicky about input; you have to get the command right, without pressing delete or cursor keys. I think it sends each character to the Duet as you type them (raw mode), rather than when you press return. If you navigate away from SerialTools to another application, and then back, in the middle of writing the command, the command won't work. You should get an 'ok' when a command goes through correctly. It's also the only terminal program available on the app store that I've found.

If you're okay with downloading software not on the Apple app store, I've been using CoolTerm from https://freeware.the-meiers.org/. Coolterm works well, though I usually have it set to Options > Terminal > 'Line mode', which sends your command line when you press return rather than character by character, and turn on local echo so it shows the command you have sent.

Ian

@moris I suspect that the wiring between the endstop and the Duet is incorrect. Please provide photographs showing how you have connected both ends of the cable.

@jay_s_uk
Thanks,

The last piece is going to be trying to figure out what caused it to short in the first place. I will mention that I was plugging in the bltouch. Not sure if that was it or what. (was on) as soon as I noticed, it was too late.

@PCR I know this is old post, but if you have some left, I am interested

Problem is solved,
I removed diodes D10 and D32.
Now the USB no longer supplies the Duet with five volts and the USB communication works properly.
Thanks for the help.

@3DGarage For reference, here's a config.g (for Duet 2, RRF 3.4.5) published by Modix on GitHub. I'm not sure if it matches your printer, and it doesn't match your 6HC for sure.

; Modix Big-60 V2 to V3 upgrade, Electronics only system upgrade, Dual Printhead ; Configuration file for Duet WiFi (firmware version 3.4.5) ; Generated by Modix - Version 3.4.5 Config B global config_version = "Version 3.4.5 Config B" global generation = 2 ; Version 2 to version 3 printer global printhead = 0 ; Aero printhead global expansion = 0 ; no expansion board is installed global printheads = 2 ; Dual printhead, change this value to 1 to switch it to a single-printhead setup ; General preferences_________________________________________________________ G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M555 P2 ; Set output to look like Marlin M575 P1 B57600 S1 ; Set auxiliary serial port baud rate and require checksum (for PanelDue) ; Network_____________________________________________________________________ M550 P"Big 60 V2 to V3" ; set printer name ;M551 P"MODIX3D" ; Set password (optional) M98 P"config_networking.g" ; load networking settings G4 P300 ; wait 300ms ;M552 P0.0.0.0 ; Uncomment this command for using Duet Ethernet board ; Drives_________________________________________________________________________ M569 P0 S1 ; Physical drive 0. X-Axis M569 P1 S0 ; Physical drive 1. Y-Axis M569 P2 S0 ; Physical drive 2. Z-Axis M569 P3 S0 ; Physical drive 3. Primary Extruder M569 P4 S0 ; Physical drive 4. Secondary Extruder ;Motor to stepper motor driver mapping_________________________________________________________ M584 X0 Y1 Z2 E3:4 P3 ; Driver mapping ;Settings_________________________________________________________ M350 X16 Y16 Z16 E16:16 I1 ; Configure microstepping with interpolation M92 X100 Y100 Z2000 E418.5:418.5 ; Set steps per mm M566 X360 Y360 Z30 E3600:3600 P1 ; Set maximum instantaneous speed changes (mm/min) M203 X9000 Y9000 Z200 E5000:5000 ; Set maximum speeds (mm/min) M201 X1000 Y1000 Z200 E5000:5000 ; Set accelerations (mm/s^2) M204 P500 ; Set print and travel accelerations (mm/s^2) M906 X1800 Y1800 E1000:1000 Z2300 I50 ; Set motor currents (mA) and motor idle factor in per cent M84 S100 ; Set idle timeout - 100 seconds ; Axis Limits M208 X0 Y0 Z-3 S1 ; set axis minima M208 X600 Y600 Z600 S0 ; set axis maxima ; Endstops M574 X1 S1 P"xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop M574 Y2 S1 P"ystop" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin ystop ; Z-Probe M558 P9 C"zprobe.in" H5 F120 T6000 A1 R0.7 ; BLTouch probing settings M950 S0 C"exp.heater3" ; set probe pin M376 H50 ; Height (mm) over which to taper off the bed compensation G31 P500 X-14 Y21 ; BLTouch X and Y offset from nozzle M557 X{move.axes[0].min + sensors.probes[0].offsets[0] + 1, move.axes[0].max + sensors.probes[0].offsets[0] - 1} Y{move.axes[1].min + sensors.probes[0].offsets[1] + 1, move.axes[1].max + sensors.probes[0].offsets[1] - 1} P10:10 ; define mesh grid M98 P"config_probe.g" ; Load the Z-offset from the config_probe.g file ; The Z_offset value is now set in config_probe.g, not in config.g ; Adjust the values there, do not adjust anything here. ; Heaters___________________________________________________________ M140 H-1 ; disable heated bed (overrides default heater mapping) ;E0_________________________________________________________________ M308 S0 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 0 as thermistor on pin e0temp ;M308 S0 P"spi.cs1" Y"rtd-max31865" ; Configure sensor 0 as PT100 via the daughterboard ;M308 S0 P"e0temp" Y"pt1000" ; Configure sensor 0 as PT1000 on pin e0temp M950 H0 C"e0heat" T0 ; create nozzle heater output on e0heat and map it to sensor 0 M98 P"PID_tune_E0.g" R1 ; PID calibration ; M307 is not used in this config. The M307 files are stored and executed from the PID_tune_E0.g file. You can verify the values there. M143 H0 S285 ; set temperature limit for heater 0 to 285C if {global.printheads} = 2 ;E1_________________________________________________________________ M308 S1 P"e1temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin e1temp ;M308 S1 P"spi.cs2" Y"rtd-max31865" ; Configure sensor 1 as PT100 via the daughterboard ;M308 S1 P"e1temp" Y"pt1000" ; Configure sensor 1 as PT1000 on pin e1temp M950 H1 C"e1heat" T1 ; create nozzle heater output on e1heat and map it to sensor 1 M98 P"PID_tune_E1.g" R1 ; PID calibration ; M307 is not used in this config. The M307 files are stored and executed from the PID_tune_E1.g file. You can verify the values there. M143 H1 S285 ; set temperature limit for heater 1 to 285C ; Fans & LED_________________________________________________________ M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 C"Primary blower fan" ; set fan 0 value. M950 F2 C"fan2" Q500 ; create LED on pin fan2 and set its frequency M106 P2 S0 H-1 C"LED" ; Disable fan channel for LED if {global.printheads} = 2 M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M106 P1 S0 H-1 C"Secondary blower fan" ; set fan 1 value. ; Tools______________________________________________________________ ;T0_________________________________________________________________ M563 P0 S"E0 Primary" D0 H0 F0 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S210 ; set initial tool 0 active and standby temperatures to 0C if {global.printheads} = 2 ;T1_________________________________________________________________ M563 P1 S"E1 Secondary" D1 H1 F1 ; define tool 1 G10 P1 X0 Y51.5 Z0 ; set tool 1 axis offsets G10 P1 R0 S210 ; set initial tool 1 active and standby temperatures to 0C ; Automatic power saving____________________________________________ M911 S22.5 R29.0 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss. Power Failure Pause ; Filament sensor settings__________________________________________________ M591 D0 P1 C"e0stop" S1 ; Regular filament sensor for E0 M591 D1 P1 C"e1stop" S1 ; Regular filament sensor for E1 ; Add-on settings__________________________________________________ ; Primary hotend Clog detector__________________________________________________ ;M591 D0 P7 C"e0stop" S1 L3.2 E10 R10:300 ; Clog Detector E0 [Add-On] ;Secondary hotend Clog detector__________________________________________________ ;M591 D1 P7 C"e1stop" S1 L3.2 E10 R10:300 ; Clog Detector E1 [Add-On] ; Crash detector__________________________________________________ ;M950 J2 C"zstop" ; create Input Pin 2 on Z-endstop to for M581 Command. ;M581 P2 T0 S0 R0 ; Crash Detector [Add-On] ; Emergency stop button__________________________________________________ ;M950 J3 C"exp.e6stop" ; create Input Pin 2 on pin E6 to for M581 Command. ;M581 P3 T0 S1 R0 ; Emergency stop [Add-On] ;M581 P3 T1 S1 R1 ; Emergency stop, pause the print [Add-On] ;M581 P3 T1 S1 R0 ; Emergency stop, pause always [Add-On]

A noticeable difference to your config is in the definition of the X endstop: according to Modix, it is positioned at the low end. In a first step, you need to verify this to match the printer's geometry.

Apart from being quite elaborated, you may want to incorporate at least some of the values Modix has set for Accel, steps/mm, speed changes, axis limits etc. in your own config.g.

EDIT: I was wrong with my assumption of the Modix being a CoreXY - please remove

M669 K1

from your config.

@dc42 I know, but still 😉
Tbh pin names are the most confusing part of Duet stuff. I tried converting to Klipper to try it out, but came back to RFF as I couldn't get bltouch working - just couldn't find the correct pins ...
Nethertheless I don't think I need klipper anyway. Ordered an accelerometer now and will try input shaping. Great stuff!!

I second the fix, my module has always had the same issue, I gave up on it awhile back and just waited hoping each firmware upgrade would solve it. I just did the latest upgrade to 3.5.0 rc1. still didn't resolve it- continued trouble shooting and ran across this thread- tried the 500ms pause and it works flawless!!! Thanks

@Blackpart almost certainly it is caused by a bad connection and it is coincidence that it started when you did a firmware upgrade.

BTW you have two M307 H1 commands in config.g. The first one should be moved to be after the M950 H1 command that creates the corresponding heater, and the second one removed.

@DavidSummerlin

Here is simplified DXF of 6XD.

Screenshot 2023-09-16 191038.jpg

Duet3 - 6XD.dxf

@Andrey the STM32H7 boards that are supported by the STM32 port are listed here https://teamgloomy.github.io/supported_boards.html#stm32h7-boards-with-native-support although I would discount the Fysetc Spider King.

@DekJak thanks. I've created https://github.com/Duet3D/RepRapFirmware/issues/910 to track this.

dc42 created this issue in Duet3D/RepRapFirmware open Review behaviour of G30 S0 #910

@o_lampe
I will try those (again), but normally those names are not used by klipper, instead it uses the internal GPIO pin names.

Update - No those definitely are the RRF specific remapped names, don't work outside of RRF.

Great. Thanks!

@awitc RRF doesn't need to know what microstepping is in use, it just needs the steps/mm setting for that axis or motor. The M350 command was introduced to allow RRF to select the microstepping to use when using drivers that allow it to be controlled.

I guess we could improve the error message, because what it really means in this case is that RRF is unable to select x32 microstepping on your driver, because it has no control over the driver microstepping.

After more thorough reading of the Duet2 documentation, I found out that the pson pin does not support pwm so that answers my first issue. I am still curious about the second issue (alternating dimmer/brighter pwm output) although truth be told, it probably isn't an issue in the great big scheme of things.