@Polyneutron21 maybe you need to flash the board with firmware then. Best look at bossa recovery for the board you have

@droftarts

Well I updated to 3.6.0 BETA 4 and the WiFi connection failed even sooner than it did under 3.5.4.

The features of 3.6 sound interesting but not at the expense of no WiFi connection.

I was able to revert to 3.4.6 so that is good for now.

Thanks.

Frederick

@tru_ann Are your Z axes belt or leadscrews? As noted here https://docs.duet3d.com/en/User_manual/Connecting_hardware/Sensors_stall_detection#limitations-of-stall-detection, stall homing is not as precise or repeatable as endstops or probes:

The stepper drivers only update the stall detection state every 1 or 4 full steps, depending on configuration. So the actual position of the stall is uncertain to either +/- half a full step or +/- 2 full steps. This means that when using stall detection to replace endstop switches, the position defined by the stall is much less accurate than with typical endstop switches.

Ian

@ProfChris I'm glad you got it working. Having read your comments, I have updated the page on stall detection.

@omar its identifying as a "bossa programming port" which indicates there is no firmware loaded so try the following to load the firmware:

https://docs.duet3d.com/en/User_manual/RepRapFirmware/Updating_firmware#fallback-procedure-2

This was posted just a few days ago. Why not search first?

https://forum.duet3d.com/topic/37421/printers-sold-retail-using-duet-hardware/7?_=1739481184715

I guess it was my mistake
I used F0 in M563 command, but should've used F3

I have been using Orca for several months now
But today is the first day I tried to use second extruder and found out that you have to write some gcode to support it

The first thing you need to do to use Orca is to configure your Printer settings. And especially the start gcode

For my FFCP this gcode works for now. Though it might not be ideal.
Also there is a ready preset for duet based printers, check it out

My start gcode if it helps

But be careful if you use bed mesh compensation, this code disables it

M83 ; extruder relative mode M140 S[first_layer_bed_temperature] ; set bed temp {if is_extruder_used[0]}M109 T0 S{nozzle_temperature_initial_layer[0] - 30}{else}{endif} ; preheat right extruder {if is_extruder_used[1]}M109 T1 S{nozzle_temperature_initial_layer[1] - 30}{else}{endif} ; preheat left extruder M190 S[first_layer_bed_temperature] ; wait for bed temp M561 G28 ;G32 ; Levels Z Tilt and probes Z=0 ;G29 S1 ; load mesh bed map G1 X0 Y0 Z2 F2000 {if is_extruder_used[0]} ; quote if right extruder is used for printing and if so beginn to with purging T0 ; activate right extruder M109 T0 S{nozzle_temperature_initial_layer[0]} ; wait for right extruder temp G1 X-10 Y5 Z0.3 F1000.0 ; go outside print area G92 E0.0 G1 Z0.2 E8 ; Purge Bubble G1 X60.0 E5.0 F1000.0 ; intro line G1 X100.0 E8 F1000.0 ; intro line G92 E0.0 {else}{endif} {if is_extruder_used[1]} ; quote if left extruder is used for printing and if so beginn to with purging T1 ; activate right extruder M109 T1 S{nozzle_temperature_initial_layer[1]} ; wait for extruder one temp G1 X-10 Y5 Z0.3 F1000.0 ; go outside print area G92 E0.0 G1 Z0.2 E8 ; Purge Bubble G1 X60.0 E5.0 F1000.0 ; intro line G1 X100.0 E8 F1000.0 ; intro line G92 E0.0 {else}{endif}

Parts of this gcode are based on these posts https://forum.raise3d.com/viewtopic.php?t=23727

@T3P3Tony Thanks for confirmation. Ill look into other options.

@Alva @dc42 sorry for writing again, but will there be fix regarding this topic in the next version?

No there isn't a software RRF emulator.

@droftarts thank you for the quick response I will try that.

@dc42 thanks, that was the thing I was looking for