@droftarts Buonasera, ho caricato il firmware 2.05.1 se voglio agganciare il filo giallo del bl touch ei =a e2 del configuatore rf devo utilizza il pin pwm v_ in o al pin +3.3 V.
grazie

@Phaedrux so I guess maybe I could just switch out the cards right?

@dc42 Ok thanks - Yes my printer has separate Z adjustments for each print head - have raised enhancement request.

Referenced Multiple Motion System Mesh Adjustment and Z hopping in the same request - but could separate them out if that would be better.
https://github.com/Duet3D/RepRapFirmware/issues/1106

ukdavewood created this issue in Duet3D/RepRapFirmware open [FeatureRequest]: Multiple Motion System - Micro Z Adjustment and Z Hopping #1106

@droftarts amp coin v18 - PLA.gcode

@phoenix

That's why we are here!

If we cannot help, we can mess things up in style. 🤠

Frederick

@dc42 Again, thanks! I can confirm that this fixes my probing issue.

@CaiJonas the stuttering movements appear to be a feature of the moves generated. They are not arc moves, they are a sequence of line segments. Here's an example from line 2270 of your example file:

G1 X60.133 Y46.575 E.6074 ; perimeter G1 E-.5 F3000 ; retract G1 X60.509 Y46.911 F18000 G1 X75.371 Y60.871 ; move to first infill point G1 X75.561 Y61.029 ; move to first infill point G1 X75.728 Y61.145 ; move to first infill point G1 X79.425 Y63.53 ; move to first infill point G1 X79.396 Y63.585 ; move to first infill point G1 X78.911 Y63.328 ; move to first infill point G1 E.5 F3000 ; ; unretract ;TYPE:Internal solid infill ;WIDTH:0.420424 G1 F12000 M106 S81 ; enable fan G1 X77.989 Y64.25 E.0389 ; infill

The commanded speed is F18000 but RRF can't maintain that speed at the boundaries between moves because the direction changes between the moves would cause the jerk limit to be exceeded. So RRF reduces the speed at the boundary to a value that doesn't cause the jerk limit to be exceeded.

It's possible that you are getting movement queue underruns, which would contribute to the jerky movement. The M122 report you published doesn't show any, but perhaps you didn't run M122 after a print.

If you are getting layer shifts then it's likely that you have the maximum speed or acceleration or jerk set higher than the motor can handle at the current you are using. You can try increasing XY motor currents, if the motor rated current allows. This won't help if the speed is high enough for the torque to start reducing. You can use the calculator at https://www.reprapfirmware.org/emf.html to estimate that speed.

@Michael-P How are you flashing the image to your RPi? Using the Raspberry Pi Imager, or something else? These versions of DuetPi have been tested extensively recently, on RPi 3, 4 and 5. I assume your RPi 3B+ has 1GB RAM? Try using the 'lite' 32-bit version, and try starting with the Duet disconnected from the RPi.

Ian

@scooby The PanelDue only shows temperatures related to heaters, ie nozzles, beds and chambers. If your bed temperature sensor isn't used by a heater (ie usually the bed heater), it will show on the 'Extras' tab in DWC only. You can define a 'dummy' heater, that uses an unused output, and map the temperature sensor to that, and define it as a bed or chamber. See https://docs.duet3d.com/User_manual/Connecting_hardware/Heaters_bed#configuring-a-bed-heater

Ian

@dc42 That's an interesting idea. I do have io3 available on each board that I could put to some use.

@coseng I'm sorry to hear that your project is shutting down. I suggest you post in a new thread with "For sale" in the title and give the machine specifications and your location in that post.

@rkutun theres a CAN out connection on the 3HC. Use that.
CAN-FD is a bus so its just one continuous run