@argo Update on this issue: using the curve smoothing solves the problem. Also, I made a copy of the original STL using solidworks, exported it as STL but using max quality for the STL and also the print came out PERFECT.
So all this issue is about the STL quality
Thanks all for the help
Best posts made by Tinchus

RE: "waves" on rounded prints

RE: delete
@blv there is no need to teach formulas or motion theroy, at least to me, Im a senior mechanical engineer, I guess I have those topics very clear. So Im pretty sure you can post your slicer profile, your config, and the STL so we can all see the sizes involved and it will be very simple to demostrate what I said is correct. But we can also do very super quick calulations looking the video: the size of the object is aprox 12 cms long. I has a soft cuve too. so lets say that segment is a real 15 cms as much it it is straight? If you print at 500 mm/s that means we should be watching your printhead cover those 15 cms in aprox 1/33 of a second without taking into consideration the acceleration. If we take into consideration the accel of 9000 you will reach something around 300 mm/s of max speed AND ONLY for a fraction of the path. Im dpoing all these calculation by my eye so I might be wrong in 20/50 mm/s max error.
And Im still not taking into account your jerk settings.
And this is the speed you get in your longest path, the rest of your STL model wont get even half of the calculated speed I have mentioned.
So...And Im not fan of nobody. I use what I considere that covers my needs. I have used klipper. It is based on python, python uses an interpret to work. That means an extra layer between klipper and the processor. So it works very nive, but no software till today is as fast as a well C++ / C code is working directly with the processor... Or have you ever seen an OS written in python ?
The firmware duet is working on is really powerful, enough for me moving from marlin.
But hey... if you are fine with klipper, OK! keep using. You have to use whatever covers your needs man.
Also I think it would be usufull if you clear what you mean with "extra perfomance", it would be a good way to contibute here to the developers.

RE: Z offset on Inductive sensors
@fcwilt because I planned the printer to have eough power to have all the build plate full of print, and since it is a big volumen, theoretically I can have like 15 kgs if I print metal. So Z motors have enough power to move that mass.
BUT, if something goes wrong, the also have the power to destroy my hotenfd and bend the bed if the printhead crash against the bed at full powwer. By reducing to 30% while homing, if something goes wrong, they will start to loose steps before bending my bed. 
RE: Spurious heater faults again
Here I have the latest data from a tunning try today: it is my heated chamber
I ran M303 H0 P0.88 S120
The P0.88 is because I need to lower the power input to the resistor in order to not burn it.
The tunning finished OK:
8/17/2022, 2:39:15 PM Auto tuning heater 0 completed after 3 idle and 14 tuning cycles in 8036 seconds. This heater needs the following M307 command:
M307 H0 R0.125 K0.058:0.000 D44.76 E1.35 S0.88 B0
8/17/2022, 1:10:13 PM Auto tune starting phase 3, measuring
8/17/2022, 12:47:41 PM Auto tune starting phase 2, settling
8/17/2022, 12:25:23 PM Auto tune starting phase 1, heating upI saved the values, I restarted the board, I checked new values are being used.
Now I try to heat the chamber and I get:
Error: Heater 0 fault: temperature rising too slowly: expected 0.02Â°C/sec measured 0.03Â°C/sec
This has happened with every try to tune PID.
The PID was working on this same chamber , same resistors, same PWM in version 3.3Actual version is 3.4.1, board duet3 in SBC mode

RE: z probe sensibility and mesh calibration with G29
@jay_s_uk I created the mesh.g file, and modified accel and jer there for mesh calibration the restore the original values to normal after the G29 S0 command .

RE: emergency stop
@ZhangJianyu Thanks for the tips.
I have tried your idea. Using it exactly as your wrote, it "works", the problem I see is that this is not exactly and emergency stop. The buzzer works, but the printing doesnt stop till the buffer is empty, and in my example gcode, that took like 5 extra seconds. That makes a total of 10 second to stop the printing... no t exactly an emergency stop jajajaja
Then I tried:
removing the M400: still not perfect, the machines stops after 5 seconds (little more may be), but buzzer is not triggered
removing the G4 delay: the same, it stop after seconds, and buzzer is not triggered. 
RE: Update interrupted
Thanks both. Yes, I had the local display, wich turned black after loosing the ssh connection.
I rebooted, it booted on 3.3 version. Then I repeated the comand in ssh and I got a "resume" message, wich worked ok. Thanks! 
RE: Bug in firmware / DWC
@fcwilt said in Bug in firmware / DWC:
M141 P0 S80 P1 S80
It does the same. It turns on for just 1 second P0 then turns it off and turns on P1 wich stay on.

RE: Switch I/O pins during macros?
@dc42 When they compete with motion system... That explain my problem about this. My macro trigger the use of an extra stepper motor, which is connected to a driver on an expansion board. So depending on the printing speed, Im detecting strange "pauses" either on the gcode printing or in the time the extra motor moves..
Now I understand why, the re is a competition for the motion system even when this extra motor is not really part of the motion of the printer, it is just vor moving a heavy filament spool, but I guess since it is using a stepper driver, it is considered part of the motion system? 
RE: DWC not starting after update try
@chrishamm Hello. The update fixed the issue. Sadly, I had scheduled the execution of your requested command for monday, so I cant provide you with the output of that command in order for you to fully diagnose the problem.
But this update did the magic. THANKS!
Latest posts made by Tinchus

RE: Connecting 2 Duet3 boards with CAN
Somethig works, others no: I can see sensors state (and create them) from the main board. In my main config I have this to test:
M950 J9 C"!1.io1.in"
And It works, I can see the state of that ping on the objects model page. So the CAN connection is there.
On the other board, the config file is:
; Enable network
M552 P0.0.0.0 S1M669 K0
M569 P0 S1 D2
M569 P1 S0 D2
M569 P2 S1 D2
M569 P3 S1 D2
M569 P4 S1 D2
M569 P5 S0 D2
M584 X0 Y1 Z2M350 X16 Y16 Z16 I1
M92 X320 Y320 Z1600
M566 X200.00 Y200.00 Z300.00
M906 X1000 Y1000 Z1000
M208 X0 Y0 Z0 S1
M208 X220 Y220 Z200 S0M950 J9 C"!1.io1.in"
;M581 P9 T4 S1 R0M954 A1
That M950 doesnt work, I cant create a sensor located on the same board, but I can do it from the main board.
BUT, the motion system on the secondary board works. I have access through the web iterface and I can move the axes with no problem or issue movements commands indepently from the can connection.
daemon.g is also not working on the secondary board.I think the project will stop here
As a wich list to think about: having the ability to connect 2 duet3 boards is usefull, but if they cant have some kind of freedom, I dont really see why this would be better than using other extension biards, for sure would be cheaper.
So to unleash all the power, wouldnt it be super good to be able to connect them with the CAN but each board can have its independency? 
RE: Connecting 2 Duet3 boards with CAN
@deckingman Well, I have this already working:
"main " board has its motion system defined and its axis (cartesian system). On the other board I have defined also a cartesion system and assigned axis to the drivers, and I can move both motion system so far (I have lauched a print on the main board, and I can move the X axis of the other board perfectly. And the CAN connectio is OK because MAIN board has defined a sensor on a IO.3 pin on the other board and receives the data) 
RE: Connecting 2 Duet3 boards with CAN
Firsts test has failed:
I have achieved to connect both duet3 boards connected throug CAN. And basically the same config I was using with the previous expansion card, work perfect with the new duet3 board as expansion card. But my objective was:
. using the expansion board, when a triggered was detected, the execution of that triggered paused the print till that trigger finishes. Not good clearlu (the trigger reads a sensor and then moves a "D" axis with its stepper motor. This pauses the print because as @dc42 said in another post, this competes in this case with a resource, the motion system, even when this "D" axis is not related at all with the printing itself. It just used for moving the spool, a heavy spool by the way)My idea was connecting 2 duet3 boards, so using the CAN 1 of the boards could read the state of the sensors connected the other board. And the board where the sensors are connected, would handle this trigger and the stepper motor, so no pause on the print would happen.
This seems to not work, the CAN connection happens, but if I define an axis on the secundary board, looks like the connection is broken (at least looks like because defining a "D" axis on the sencond board is just ignored.
Any ideas?

RE: Connecting 2 Duet3 boards with CAN
Thanks you all for the information. Im on the work. I will start by trying to do the update. Reading all the info I gathered, the command M954 states that this would be tipically the only one command on the config file of the "main expansion board".
I will try but in the meantime I will ask: my intention was having a communication between both boards using the CAN cable, so 1 of the boards is the "master" the other one is the "slave" but I though that by using a complete duet3 board, I could use all the power of the boair (its processor) to handle tasks in parallel, freeing resources in the main baord (like moving steppers with triggers detected by the slave board, so the printing on the main board is not paused, like it was happening my previous test using a normal expansion board). This will work? 
Connecting 2 Duet3 boards with CAN
Hello. I have seen than in one of the last updates, now it is possible to connect 2 duet3 boards through CAN
I havent found information about this (sorry if Im wrong), so I have some questions:1. I guess I just connect both boards using the CAN ports, but how do I know or setup wich is the main one and which is the "extension"?
2. One of my boards need to update its firmware, can I do that using the can connection? I have tried uploading the firmware file but nothing happened (I did this into the board that is meant to be the "main" and it is already updated to 3.4.4, the other one is 3.3 I guess)
3. Any other consideration regarding the connection?
Thanks in advance 
Duet3 and Expansion board channel / trigger question
Hello. I will do some tests on a project I have and I would like to know in advance while I wait for some hardware to arrive:
I have a duet3 board, 3.4.4 in SBC mode. All [printing is handle there.
I want to add and expansion board. The one I bought has 3 extre stepper drivers and 6 input/output pins. My project includes:I will have an extra sensor connected to IO_3. My objective is that when this sensor is triggered (it is and NO sensor), a stepper motor will be used to move a tool I desgned. This stepper motor is connected to driver0.
In my config all this will be handle by a trigger (lets say test_trigger1.g) and will move this motor some X steps.
The expasion board is connected to the duet3 using a can cable
My question is: if Im printing, I guess the main duet3 board will be "busy" handling the printing, si how fast it will be the detection of the sensor connected to IO_3 on the expansion board, will be instantly deteted or I can expect some "delay" beicause the duet3 board is doing the print?
Also: when the triggered is executed, this execution of the .g file will run in parallel with the print or I can have some risk of the print being stopped for a second while executing that trigger and then the gcode will be resumed?
Thanks in advanced

RE: Layer chart empty
@jay_s_uk Here you have:
; Prepare for EndOfLayer
G1 X23.373 Y284.669 E1.92904
G1 X23.374 Y293.452 E0.2921
G1 X23.374 Y295.588 E0.07106
G1 X23.374 Y297.329 E0.05791
G1 X23.565 Y297.707 E0.01409
G1 X23.98 Y298.039 E0.01766
G1 X23.968 Y298.245 E0.00687
G1 X23.724 Y299.227 E0.03368
G1 X23.682 Y299.69 E0.01544
G1 X23.656 Y299.968 E0.00928
G1 X23.648 Y300.062 E0.00315
; time estimate: pre = 90.957397, post = 83.438141
; Dwell time remaining = 63.438145
; END_LAYER_OBJECT z=30.400
;
; *** Every 1 Layers ***
M141 S170
G10 S410
G92 E0
;
; BEGIN_LAYER_OBJECT z=30.600 z_thickness=0.200
;
; 'Loop Path', 1.1 [feed mm/s], 32.0 [head mm/s]
; Chain Extrusion
G1 X23.588 Y300.072 Z30.6 E0.00694 F300
; Chain flows: 0.400 > 2.560
; head speed 32.000008, filament speed 1.064329, preload 0.000000
G1 X23.601 Y299.96 E0.00376 F1920
G1 X23.64 Y299.623 E0.01129
G1 X23.705 Y299.061 E0.01882
G1 X24.003 Y298.033 E0.0356
G1 X24.036 Y297.925 E0.00374
G1 X23.532 Y297.546 E0.02098
G1 X23.374 Y297.13 E0.0148
G1 X23.374 Y295.397 E0.05766
G1 X23.374 Y293.296 E0.06986
G1 X23.374 Y257.894 E1.17749
G1 X23.369 Y226.45 E1.04584
G1 X23.525 Y225.998 E0.01589
G1 X23.811 Y225.765 E0.01228
G1 X24.408 Y225.742 E0.01988
G1 X25.872 Y225.742 E0.04869
G1 X25.867 Y219.108 E0.22065
G1 X25.848 Y218.979 E0.00435
G1 X23.909 Y218.975 E0.06449
G1 X23.599 Y218.828 E0.01141
G1 X23.417 Y218.537 E0.01142
G1 X23.373 Y218.035 E0.01677
G1 X23.384 Y209.835 E0.27273
G1 X23.541 Y209.325 E0.01774
G1 X23.914 Y208.844 E0.02025
G1 X24.406 Y208.55 E0.01906
G1 X24.903 Y208.445 E0.0169
G1 X87.058 Y208.442 E2.06728
G1 X110.514 Y208.447 E0.78017
G1 X111.041 Y208.574 E0.01802
G1 X111.499 Y208.875 E0.01821
G1 X111.824 Y209.302 E0.01786
G1 X111.987 Y209.803 E0.01754
G1 X112.006 Y210.765 E0.03201
G1 X112.006 Y218.404 E0.25408
G1 X111.81 Y218.757 E0.01341
G1 X111.44 Y218.975 E0.01428
G1 X109.281 Y218.978 E0.0718
G1 X109.026 Y218.979 E0.00848
G1 X109.007 Y219.368 E0.01294
G1 X109.008 Y225.743 E0.21205
G1 X111.342 Y225.75 E0.07765
G1 X111.695 Y225.838 E0.0121
G1 X111.937 Y226.079 E0.01134
G1 X112.007 Y226.398 E0.01087
G1 X112.007 Y285.785 E1.97523
G1 X112.01 Y313.34 E0.9165
G1 X111.899 Y313.675 E0.01173
G1 X111.596 Y313.951 E0.01362
G1 X111.076 Y313.978 E0.01732
G1 X109.024 Y313.978 E0.06824
G1 X109.006 Y314.408 E0.01432
G1 X109.015 Y320.633 E0.20703
G1 X109.073 Y320.741 E0.0041
G1 X111.391 Y320.746 E0.07708
G1 X111.772 Y320.916 E0.01388
G1 X111.985 Y321.199 E0.01179
G1 X112.008 Y321.606 E0.01354
G1 X112.003 Y329.796 E0.27243
G1 X111.873 Y330.324 E0.01806
G1 X111.566 Y330.778 E0.01823
G1 X111.124 Y331.105 E0.01827
G1 X110.648 Y331.26 E0.01668
G1 X109.804 Y331.277 E0.02807
G1 X58.419 Y331.278 E1.70908
G1 X28.731 Y331.274 E0.98741
G1 X28.329 Y331.128 E0.01424
G1 X28.097 Y330.84 E0.01228
G1 X28.073 Y330.306 E0.01779
G1 X28.07 Y325.333 E0.16542
G1 X27.922 Y324.562 E0.02612
G1 X27.853 Y323.659 E0.03009
G1 X28.018 Y322.577 E0.03641
G1 X28.073 Y322.147 E0.01444
; Prepare for Perimeter
G1 X28.066 Y305.741 E0.54564
G1 X28.026 Y305.608 E0.00464
G1 X27.331 Y305.447 E0.02373
G1 X26.531 Y305.123 E0.0287
G1 X25.671 Y304.576 E0.03391
G1 X24.938 Y303.889 E0.03343
G1 X24.61 Y303.436 E0.01859
G1 X24.347 Y303.073 E0.0149
G1 X24.117 Y302.607 E0.01727
G1 X24.04 Y302.45 E0.00584
; Perimeter Length = 434.834534
;
; 'Perimeter Path', 1.1 [feed mm/s], 32.0 [head mm/s]
; Chain Extrusion
G1 X23.979 Y302.322 E0.00471
; Chain flows: 2.560 > 0.000
; head speed 32.000008, filament speed 1.064329, preload 0.000000
; unsupported segments 3
; Unsupported degree: 0.605618
; Overhang(46.9)
; Unsupported Fan = 0 (from 0)
G1 X23.946 Y302.245 E0.00277
G1 X23.865 Y301.967 E0.00964
G1 X23.725 Y301.49 E0.01654
G1 X23.724 Y301.457 E0.0011
G1 X23.739 Y301.427 E0.0011
G1 X23.766 Y301.408 E0.0011
G1 X23.979 Y301.33 E0.00755
G1 X24.054 Y301.255 E0.00353
G1 X24.07 Y301.23 E0.00096
G1 X24.074 Y301.202 E0.00096
G1 X23.983 Y300.174 E0.03433
G1 X24.091 Y299.159 E0.03392
G1 X24.365 Y298.21 E0.03288
G1 X24.526 Y297.846 E0.01323
G1 X24.529 Y297.802 E0.00148
G1 X24.504 Y297.765 E0.00148
G1 X23.869 Y297.309 E0.026
G1 X23.77 Y297.04 E0.00952
G1 X23.769 Y226.476 E2.34699
G1 X23.897 Y226.185 E0.01059
G1 X23.922 Y226.156 E0.00126
G1 X23.958 Y226.145 E0.00126
G1 X26.209 Y226.146 E0.07486
G1 X26.242 Y226.137 E0.00115
G1 X26.267 Y226.113 E0.00114
G1 X26.276 Y226.079 E0.00115
G1 X26.273 Y218.692 E0.24569
G1 X26.247 Y218.597 E0.00328
G1 X26.223 Y218.562 E0.00144
G1 X26.182 Y218.548 E0.00143
G1 X24.215 Y218.578 E0.06542
G1 X23.91 Y218.56 E0.01017
G1 X23.871 Y218.545 E0.00137
G1 X23.849 Y218.51 E0.00137
G1 X23.773 Y218.219 E0.00999
G1 X23.778 Y209.939 E0.2754
G1 X23.941 Y209.44 E0.01748
G1 X24.246 Y209.09 E0.01543
G1 X24.774 Y208.855 E0.01922
G1 X30.548 Y208.843 E0.19203
G1 X65.129 Y208.842 E1.15017
G1 X110.509 Y208.847 E1.50938
G1 X110.996 Y209.004 E0.01698
G1 X111.356 Y209.305 E0.01562
G1 X111.591 Y209.838 E0.01938
G1 X111.605 Y211.679 E0.06125
G1 X111.611 Y218.316 E0.22073
G1 X111.444 Y218.533 E0.00913
G1 X111.423 Y218.551 E0.00091
G1 X111.396 Y218.559 E0.00092
G1 X111.165 Y218.578 E0.0077
G1 X108.71 Y218.578 E0.08167
G1 X108.668 Y218.593 E0.00148
G1 X108.645 Y218.631 E0.00148
G1 X108.604 Y218.824 E0.00655
G1 X108.605 Y226.079 E0.24132
G1 X108.614 Y226.113 E0.00115
G1 X108.638 Y226.137 E0.00115
G1 X108.672 Y226.146 E0.00115
G1 X111.313 Y226.147 E0.08784
G1 X111.535 Y226.224 E0.00782
G1 X111.564 Y226.244 E0.00117
G1 X111.578 Y226.276 E0.00117
G1 X111.605 Y226.438 E0.00544
G1 X111.607 Y294.024 E2.24795
G1 X111.613 Y313.339 E0.6424
G1 X111.468 Y313.544 E0.00836
G1 X111.444 Y313.565 E0.00105
G1 X111.413 Y313.572 E0.00105
G1 X108.856 Y313.575 E0.08506
G1 X108.672 Y313.575 E0.00612
G1 X108.638 Y313.584 E0.00115
G1 X108.614 Y313.608 E0.00114
G1 X108.605 Y313.641 E0.00115
G1 X108.605 Y314.133 E0.01636
G1 X108.609 Y321.046 E0.22993
G1 X108.615 Y321.075 E0.00096
G1 X108.633 Y321.097 E0.00097
G1 X108.69 Y321.145 E0.00245
G1 X108.71 Y321.156 E0.00077
G1 X108.733 Y321.16 E0.00078
G1 X111.335 Y321.15 E0.08656
G1 X111.557 Y321.27 E0.0084
G1 X111.581 Y321.292 E0.0011
G1 X111.592 Y321.324 E0.0011
G1 X111.608 Y321.547 E0.00745
G1 X111.602 Y329.793 E0.27427
G1 X111.442 Y330.276 E0.01691
G1 X111.133 Y330.634 E0.01573
G1 X110.608 Y330.864 E0.01907
G1 X108.576 Y330.876 E0.06756
G1 X38.232 Y330.878 E2.33969
G1 X36.105 Y330.878 E0.07074
G1 X34.364 Y330.878 E0.05789 F1855.6
G1 X33.01 Y330.878 E0.04503 F1791.2
G1 X32.042 Y330.878 E0.03219 F1726.8
G1 X31.461 Y330.878 E0.01934 F1662.3
G1 X31.266 Y330.878 E0.00649 F1597.9
G1 X31.11 Y330.878 E0.00519 F1533.5
G1 X30.642 Y330.877 E0.01557 F1469.1
G1 X29.862 Y330.875 E0.02594 F1404.7
G1 X28.77 Y330.873 E0.03633 F1340.3
G1 X28.535 Y330.767 E0.00854 F1275.8
G1 X28.509 Y330.745 E0.00115 F1211.4
G1 X28.497 Y330.713 E0.00115
G1 X28.476 Y330.502 E0.00706
G1 X28.472 Y329.013 E0.04953
G1 X28.467 Y327.228 E0.05937
G1 X28.462 Y325.146 E0.06922
G1 X28.325 Y324.564 E0.01989
G1 X28.255 Y323.678 E0.02955
G1 X28.367 Y322.809 E0.02917
G1 X28.476 Y322.409 E0.01378
G1 X28.474 Y308.747 E0.45441
G1 X28.474 Y306.912 E0.06103
G1 X28.474 Y305.376 E0.05108
G1 X28.462 Y305.337 E0.00135
G1 X28.43 Y305.313 E0.00134
G1 X28.259 Y305.253 E0.00601
G1 X27.595 Y305.112 E0.02259 F1275.8
G1 X26.713 Y304.757 E0.03163 F1340.3
G1 X26.245 Y304.463 E0.01836 F1404.7
G1 X25.904 Y304.248 E0.01342 F1469.1
G1 X25.633 Y304.004 E0.01213 F1533.5
G1 X25.52 Y303.89 E0.00532 F1597.9
G1 X25.181 Y303.551 E0.01596 F1662.3
G1 X24.678 Y302.826 E0.02933 F1726.8
G1 X24.264 Y301.914 E0.03333 F1791.2
G1 X24.084 Y301.277 E0.02202 F1855.6
G1 X24.065 Y301.246 E0.0012 F1920
G1 X24.032 Y301.23 E0.0012
G1 X23.706 Y301.165 E0.01109
G1 X23.669 Y301.144 E0.00141
G1 X23.652 Y301.105 E0.00141
G1 X23.608 Y300.572 E0.01779
G1 X23.583 Y300.266 E0.0102
G1 X23.582 Y300.184 E0.00272
;
; 'Loop Path', 1.1 [feed mm/s], 32.0 [head mm/s]
G1 X23.009 Y299.143 E0 F15000
; head speed 32.000008, filament speed 1.064329, preload 0.000000
; Prepare for Loop
G1 X23.01 Y299.047 E0.0032 F1920
G1 X23.012 Y298.759 E0.0096
G1 X23.016 Y298.278 E0.01599
G1 X23.303 Y298.01 E0.01306
G1 X23.429 Y297.986 E0.00427
G1 X23.545 Y298.076 E0.00488
G1 X23.384 Y298.736 E0.02259
G1 X23.265 Y299.221 E0.01661
G1 X23.248 Y299.348 E0.00428
G1 X23.061 Y299.266 E0.0068
G1 X23.009 Y299.143 E0.00442
;
; 'Destring/Wipe/Jump Path', 0.0 [feed mm/s], 68.0 [head mm/s]
; 'Destring Suck' by 'A'
G1 E1 F1125
; head speed 68.000008, filament speed 0.000000, preload 0.000000
G1 X23.009 Y299.143 Z31.6 E0 F300
;
; 'Loop Path', 1.1 [feed mm/s], 32.0 [head mm/s]
G1 X22.609 Y328.81 E0 F15000
G1 X22.609 Y328.81 Z30.6 E0 F300
; 'Destring Prime'
G1 E1 F1125
; Chain flows: 0.000 > 2.560
; head speed 32.000008, filament speed 1.064329, preload 0.000000
G1 X22.609 Y328.614 E0.00653 F1920
G1 X22.609 Y328.025 E0.0196
G1 X22.609 Y327.042 E0.03267
G1 X22.609 Y325.667 E0.04574
G1 X22.609 Y323.899 E0.05881
G1 X22.609 Y321.738 E0.07187
G1 X22.608 Y284.61 E1.23489
G1 X22.616 Y208.956 E2.51626
G1 X22.717 Y208.512 E0.01517
G1 X22.983 Y208.109 E0.01606
G1 X23.371 Y207.821 E0.01606
G1 X23.815 Y207.69 E0.01541
G1 X27.066 Y207.678 E0.10811
G1 X99.22 Y207.677 E2.39987
G1 X111.461 Y207.683 E0.40713
G1 X111.986 Y207.809 E0.01796
G1 X112.423 Y208.139 E0.01823
G1 X112.701 Y208.613 E0.01826
G1 X112.772 Y209.243 E0.0211
G1 X112.766 Y330.741 E4.04106
G1 X112.637 Y331.28 E0.01843
G1 X112.341 Y331.657 E0.01593
G1 X111.955 Y331.927 E0.01565
G1 X111.392 Y332.039 E0.0191
G1 X82.205 Y332.042 E0.97078
; Prepare for Perimeter
G1 X30.015 Y332.04 E1.73585
G1 X27.974 Y332.04 E0.06788
G1 X26.288 Y332.039 E0.05606
G1 X24.958 Y332.039 E0.04426
G1 X24.17 Y331.899 E0.02661
G1 X23.614 Y331.595 E0.02109
G1 X23.368 Y331.378 E0.01093
G1 X23.286 Y331.305 E0.00364
; Perimeter Length = 431.670105
;
; 'Perimeter Path', 1.1 [feed mm/s], 32.0 [head mm/s]
; Chain Extrusion
G1 X23.191 Y331.211 E0.00443
; Chain flows: 2.560 > 0.000
; head speed 32.000008, filament speed 1.064329, preload 0.000000
G1 X23.146 Y331.162 E0.00222
G1 X23.006 Y330.923 E0.0092
G1 X22.758 Y330.5 E0.01632
G1 X22.677 Y330.23 E0.00938
G1 X22.659 Y330.201 E0.00112
G1 X22.63 Y330.184 E0.00113
G1 X22.267 Y330.091 E0.01247
G1 X22.231 Y330.067 E0.00143
G1 X22.217 Y330.026 E0.00143
G1 X22.212 Y329.189 E0.02785
G1 X22.206 Y328.18 E0.03356
G1 X22.206 Y326.349 E0.0609
G1 X22.207 Y324.134 E0.07368
G1 X22.212 Y208.986 E3.82985
G1 X22.325 Y208.399 E0.01986
G1 X22.613 Y207.925 E0.01845
G1 X23.072 Y207.521 E0.02036
G1 X23.631 Y207.308 E0.01989
G1 X25.055 Y207.278 E0.04737
G1 X97.205 Y207.276 E2.39971
G1 X111.425 Y207.28 E0.47298
G1 X112.035 Y207.391 E0.02063
G1 X112.561 Y207.716 E0.02053
G1 X112.948 Y208.184 E0.0202
G1 X113.149 Y208.748 E0.01994
G1 X113.172 Y210.78 E0.06759
G1 X113.172 Y253.258 E1.41281
G1 X113.172 Y295.551 E1.40669
G1 X113.171 Y330.639 E1.16704
G1 X113.082 Y331.238 E0.02012
G1 X112.816 Y331.734 E0.01872
G1 X112.365 Y332.156 E0.02056
G1 X111.841 Y332.391 E0.01909
G1 X111 Y332.442 E0.02802
G1 X53.799 Y332.443 E1.90251
G1 X24.945 Y332.439 E0.9597
G1 X24.277 Y332.344 E0.02245
G1 X23.718 Y332.134 E0.01986
G1 X23.168 Y331.756 E0.0222
G1 X22.676 Y331.209 E0.02445
G1 X22.36 Y330.582 E0.02335
G1 X22.255 Y330.13 E0.01546
G1 X22.258 Y330.09 E0.00133
G1 X22.283 Y330.059 E0.00133
G1 X22.455 Y329.946 E0.00682
G1 X22.572 Y329.927 E0.00396
G1 X22.602 Y329.915 E0.00106
G1 X22.622 Y329.891 E0.00105
G1 X22.628 Y329.86 E0.00104
G1 X22.615 Y329.285 E0.01915
G1 X22.609 Y328.999 E0.0095
G1 X22.609 Y328.965 E0.00114
;
; 'Loop Path', 1.1 [feed mm/s], 32.0 [head mm/s]
G1 X23.043 Y329.998 E0 F15000
; Chain flows: 0.000 > 2.560
; head speed 32.000008, filament speed 1.064329, preload 0.000000
G1 X23.039 Y329.894 E0.00349 F1920
G1 X23.028 Y329.579 E0.01046
G1 X23.009 Y329.055 E0.01744
G1 X23.009 Y328.01 E0.03476
G1 X23.01 Y326.581 E0.04755
G1 X23.01 Y324.766 E0.06036
G1 X23.011 Y322.566 E0.07316
G1 X23.017 Y301.286 E0.70779
G1 X23.081 Y301.171 E0.00439
G1 X23.259 Y301.103 E0.00631
G1 X23.459 Y302.033 E0.03163
G1 X23.754 Y302.783 E0.02681
G1 X24.181 Y303.555 E0.02934
G1 X24.808 Y304.34 E0.03342
G1 X25.623 Y305.04 E0.03575
G1 X26.577 Y305.594 E0.03668
G1 X27.673 Y305.977 E0.0386
G1 X27.666 Y322.391 E0.54594
G1 X27.534 Y322.923 E0.01822
G1 X27.45 Y323.938 E0.0339
G1 X27.596 Y325.047 E0.03718
G1 X27.672 Y325.508 E0.01555
G1 X27.676 Y330.752 E0.17442
G1 X27.816 Y331.137 E0.01363
G1 X27.889 Y331.264 E0.00486
G1 X27.712 Y331.64 E0.01383
G1 X26.797 Y331.643 E0.03041
G1 X25.756 Y331.635 E0.03462
G1 X24.85 Y331.628 E0.03015
G1 X24.329 Y331.522 E0.01767
G1 X23.788 Y331.232 E0.02044
G1 X23.33 Y330.747 E0.02218
G1 X23.182 Y330.407 E0.01232
G1 X23.08 Y330.171 E0.00855
G1 X23.043 Y329.998 E0.00588
;
; 'Loop Path', 1.1 [feed mm/s], 32.0 [head mm/s]
; Chain Extrusion
G1 X23.421 Y329.849 E0.01354 
error in update plugin manager dependency?
Preparing to unpack .../022duetpimanagementplugin_3.4.4_armhf.deb ...
Error:
An assembly specified in the application dependencies manifest (PluginManager.deps.json) was not found:This error appeared during an 4.3.4 try update
The comnads used for the update were
sudo apt update
sudo apt distupgradeIt is a duet3 board in SBC mode
The update by itself finished, I see no failure so far 
Layer chart empty
My payer chart is empty, showing no information at all. Vesion 3.4.3 duet3 SBC mode.
Is something due to the slicer not generating some particular gcode or something? Im using kisslicer 
RE: Inductive sensor failing
@Phaedrux I found the problem: the temperature was expanding the probe casing, and the probe was somehow "faulty" (not really, the problem was n the cable, despite it was not broken, my homing routing was hitting the cable base and that must have loosen something in the conection with the electroncs, and that problem only showed when everything was really hot). Also this was triggered because of the histeresis of the probe, the faulty connection caused by the temperature expansion together with the histeresis, made the probe to sense and then stay on the triggered state)