Topics created by Marco Bona

@dc42 thanks, I hadn't thought of this option.

@dc42, hi, I have installed latest internal release, prelease 3.4 beta 3+1 on mainboard while on the expansion board there is the latest release3.4 beta 3, leaving a delay although minimal in the moves it works correctly, the only strange thing that known is that I have to load configuration file 2 times to be able to load the parameters on the expansion board, I don't know if it is due to the fact that some updates are missing on expansion board. With this release I'm getting perfect prints, great job !!

Out of curiosity - do you get the same if you disconnect the PT100 board and connect the DHT to the duet directly?

@dc42, that's right, there are M584 commands inside some tool change and various homing files.
I publish configuration file:
config.g
Unfortunately I cannot confirm the exact operation of tool change in an older version of rrf because I am finishing implementing it now.
Also I point out that when I restart filmware, warnings like this are displayed:

Warning: M307: Heater 2 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C Warning: M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 672C Warning: M307: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 478C

I seem to remember that with RC1 it was fixed.

@chrishamm, sorry for delay in replying but this week I had a commitment, I upgraded yesterday to beta 4.1 which works perfectly even if I don't know why I had to recalibrate BLTouch because I find a difference of 0.05mm. I think the problem is not related to firmware however I solved it.
Thanks for the support.
Marco

@chrishamm ,great, thanks again !!

@dc42, @chrishamm, I update the situation:
-I managed to install the 3.2 beta2 package (sorry but I missed a key point in the guide) and the problem occurred again.
-I ran firmware in standalone mode and printer works surprisingly well indeed I dare say it works better than with SBC connected. The printer seems to respond better to the gcode and I noticed that all messages are displayed on paneldue that were not present with the SBC connected.
Not to argue and also seeing the problems that other users encounter the question that arises is are you sure that duet3 + SBC works as it should?
Are you sure that no changes have been made to what is currently the 3.1.1 revision that was not problematic before?
I am now doing a test print in standalone mode and it seems the printer is working fine.
I will keep you updated if the problem occurs again even in this condition.

@BoA , now it's clear. I got that value from 3D Printer Calc Toolbox, the formula should be same, although I have some doubts about actual current value (I set 2.24 A). Rated current is set on 2.8A

I use this code in my homez.g to run automatic tramming (three motor bed) and mesh levelling only if the machine has been off or been reset:

if move.calibration.numFactors = 0 ; no bed levelling run yet G32 M98 P"homing/unsafe-homez.g" G29 else M98 P"homing/unsafe-homez.g"

with unsafe-homez.g containing

G1 X{move.axes[0].max/2} Y{move.axes[1].max/2} F15000 ; move to homing position M558 H10 ; careful when homing G30 ; home precise with Z-probe M558 H3 ; back to speed

@bearer, @Kolbi, @aidar, thanks for clarification!!

Sounds like the cause would be in the slicer area. The firmware doesn't have a concept of infill.

@Phaedrux, I finally managed to solve, all the fault of bad insulation of heated bed ...........

@dc42 , only panel due restarts, I see the initial screen with the logo, instead the printing proceeds without problems. The strange thing is that when I restart Duet wifi a series of line errors are displayed but I cannot tell you which ones because it is too fast to do it and they do not remain stored in the console. Tomorrow night I check the 5V, but if it were unstable that line can also create all the other problems?

@Phaedrux , there he is:

M117 Preparing ;write Preparing G4 S2 ;delay 2 seconds M140 S60 ;set bed temperature and move on M141 S0 ;set heated chamber temperature and move on M104 T0 S195 ;wait for the extruder to reach desired temperature M107 ;start with the fan off G28 ;home all axes T0 ;select tool 0 G1 X-23 Y-24 F10000 ;go to the center of bed G1 Z10 F1000 ;E go to Z10 M107 P0 ;turn off leds G30 X-23 Y-24 S-2 H1.915 ;probe current position and ajust Z offset G1 Z40 F1000 ;E go to Z40 M106 P0 S1 ;turn on leds T0 ;reset current tool M584 P4 ;apply custom setting G1 X-137 Y160 F10000 ;go to X-137 Y160 M117 Spray print adhesive ;write Spray print adhesive G4 S2 ;delay 2 seconds M226 ;pause M190 S60 ;wait for the bed to reach desired temperature M109 S205 ;wait for the extruder to reach desired temperature G1 U130 F10000 ;go to U130 G92 E0 ;reset the extruder position G1 E25 F500 ; extrude 25mm of feed stock G92 E0 ;reset the extruder position G1 E-4 F5000 ;retract 4mm G1 X-187 F500 ;go to X-187 G1 Y165 F500 ;go to Y165 G10 ;retract G1 X-137 F500 ;go to X-137 and clean nozzle G1 XO Y0 U0 F10000 ;go to X0 Y0 U0 M584 P3 ;apply custom setting G21 ;metric values G90 ;absolute positioning M117 Print starting ;write Print starting G4 S2 ;delay 2 seconds G92 E0 ;reset the extruder position G1 E4 F500 ;unretract 4mm G11 ;unretract

I was considering doing operations using subprograms.
I have to find some time to write and try them.

@droftarts ,I try to reduce it to 16mm / s

@dc42 ,I managed to solve by connecting an Arduino, although in reality it is M80 in sleep.g which gives the signal to interrupt. I publish the Arduino code that I used if someone were to serve it.
Duet3_on_off_switch.txt

@Marco-Bona said in Question about magnet filament monitor:

-The runout sensor is activated
-Continue printing for another 800mm
-Pause printing

Not exactly what you are looking for but here somewhat similar scenarios that I believe are feasible

Runout sensor activated Printing paused Pause script purges 800 of filament.

or

Runout sensor activated and trigger a delay After X seconds the duet receives the sensor activated signal Printing paused

There is another solution that will delay by extrusion length rather than time but it's more complex. It's related to the stepper analyzer discussed somewhere else here, which can tracks in realtime the extrusion length.

@bearer ,Now it works perfectly, thanks a lot for the explanation

@Danal, I am running on Duet wifi, RRF3.1-RC3, but in the past I had had the same problem with a previous version of the firmware, then I had set aside the configuration to fix another problem. I'm definitely doing something wrong. Could you kindly share the tool changer files to be inspired?