@Maurits also add a G4 S2 command early in config.g to make sure the expansion 6HC is ready to accept CAN commands when the M584 E command is executed.

@Jarery see the response earlier from @oliof about how to test the temperature reading accuracy of the Duet.

I might be onto something:

I cut off the pins that I don't need on the 2209 from the J3 column (pins 2, 3 & 5). 40239395-a074-42b3-ad22-2af4380e8002-image.png

After declaring the drivers in the board.txt file this is the status of the drivers from m122:
7760f99d-d9ea-4a64-af31-332f66a85791-image.png
(I think my driver 1 socked is broken, no matter what I put in there it sais that there is no driver, I will look into it some other time)

Now I need to reconnect the cables to the board as before so that I can go on with testing.

Update:
Succes! All axis moving as they should.

@T3P3Tony

I will be able to check that in January, once I'm back from holidays

@droftarts

Same, will test it out in January once I'm back. The wiring I've done per the guide you've shown. I had missed the driver enable polarity jumper, so that's quite likely the issue there.

With re-sending the commands we were able to get the printer up and running, and the printer has completed a successful print, though hopefully we won't need to use the driver_enable.g file I used before with the fixes recommended.

Thanks both for the help, I'll enjoy the Christmas break for now and get back to it in Jan

@martinv what is the chamber heater controller actually controlling? How many heaters, fans, temperature sensors etc?

@droftarts

My mistake... I'm sorry for mixing up the firmware numbers. I thought I had the latest firmware on both boards but I don't. I updated the firmware on the 6HC and it's now working.

Thanks so much for your help!

@jay_s_uk Thank you !

That's simple enough it seems like i should have tried it, I'm grateful for your quick response sir !

@droftarts please can you confirm if the issue can be replicated using @mike_b 's config.

@Leeuw123 Just so you understand what has changed, and the effect of that, see M569

The M569 D parameter lets you choose the mode of operation between stealthChop (D3) and spreadCycle (D2). stealthChop is a quiet mode of operation for stepper motors at standstill and at low velocities, but will struggle at higher speeds. While stealthChop is a voltage mode PWM controlled chopper, spreadCycle is a cycle-by-cycle current control. It can react extremely fast to changes in motor velocity or motor load. spreadCycle will give better performance in medium to high velocity range for motors and applications which tend to resonance.

spreadCycle is the default mode of operation, because printers have been getting faster, and reaching the limitations of stealthChop, causing missed steps. RepRapFirmware also allows you to switch over from stealthChop to spreadCycle, using the V parameter. However, this changeover needs to happen at a relatively low speed, as there is a jolt when the changeover happens. The higher the changeover speed, the worse the jolt.

The V parameter defines at what speed this happens, except V isn't the actual speed, it is the interval in clock cycles between 1/256 microsteps below which the drivers will switch from stealthChop to to spreadCycle mode. Low V means the changeover happens at high speed, high V means it happens at low speed.

We suggest the use of one of the following configurations:

stealthChop changing over to spreadCycle a very low speed. Compared to running in spreadCycle always, this reduces standstill noise with some motors. stealthChop changing over to spreadCycle at a little over your normal maximum printing speed. It will switch to spreadCycle for travel moves, except very short ones. This will only be viable if the jerk at switchover is tolerable. Limit your travel speed so that you can keep the printer in stealthChop mode always.

Send M569 P... to see the speed this changeover happens, and tune V to a sensible speed for your setup. eg On my machine, if I send

M569 P0.0 S0 D3 V40 18/12/2024, 13:53:56 M569 P0.0 Drive 0 runs in reverse, active low enable, timing fast, mode stealthChop, ccr 0x00053, toff 3, tblank 0, tpwmthrs 40 (117.2 mm/sec), pwmScaleSum 11, pwmScaleAuto 0, pwmOfsAuto 36, pwmGradAuto 14, pos 8

You can see the changeover speed is 117.2mm/s. I usually set the speed to be above 0mm/s, but below the jerk setting (M566, on my machine set to 5mm/s), so it's in spreadCycle for all movement, but stealthChop at standstill, like this:

M569 P0.0 S0 D3 V1000 18/12/2024, 14:24:59 M569 P0.0 Drive 0 runs in reverse, active low enable, timing fast, mode stealthChop, ccr 0x00053, toff 3, tblank 0, tpwmthrs 1000 (4.7 mm/sec), pwmScaleSum 11, pwmScaleAuto 0, pwmOfsAuto 36, pwmGradAuto 14, pos 8

Tune the V parameter to get the right balance of noise reduction and performance for your machine.

Ian

@mmcc as @droftarts said. For a PT100, if you see positive spikes then a bad connection between the daughter board and the sensor is most likely. If the wires are long or there are any connectors in the wiring then I strongly recommend using a 4-wire connection.

@fotomas I can't see anything wrong with your wiring.
I'm not aware of it being possible to damage when programmed as a probe. We do have a few users who haven't been able to get one working recently though. I've only ever tested a v1 microprobe. I don't have a V2.

@chimaeragh if you're getting a replacement board I would look at one of the duet 3 products as the duet 2 is end of life

@Simon-1 I wired a slider switch into the 5v power line mounted to the side of the PD cases. Super easy if your using serial. Might be harder with the ribbon cable. However, I almost never use the switch the screen saver seems good enough.

@droftarts I get 100K if I measure between nozzle and another 1lc copper plated hole (not the one where wire grounding is connected). If I measure between nozzle and negative slot on PSU, I am getting 2.2 k.

@FrankHowardNUSA if you run stepper motors at their full rated current they get very hot. It's normal to run them at 60 to 80% of that current. So 1A should be enough anyway.

Sadly it's not possible to get anywhere close to the maximum figures headlined by Trinamic, especially when space is constrained. The headline figures are for intermittent operation with a very large PCB area for heatsinking. However, we should be able to increase the maximum current of the Roto Tool board somewhat.

@SamKudarauskas the second one uses the HX711 chip, which is too slow to be used for bed probing. The first one is a Force Sensitive Resistor (FSR) and we mention those in our documentation about connecting Z probes. See https://docs.duet3d.com/User_manual/Connecting_hardware/Z_probe_connecting#force-sensitive-resistors.

@HeidiH assuming you are running without attached single board computer then one possible issue with removing power is that if the board is writing to the SD card at the time then the SD card may be corrupted. SD card writes can occur when uploading a file or doing a other DWC action that changes files, within 15 seconds following the last log message written if you have enabled logging, when a simulation completes, and any time you execute a command that writes to file e.g. an echo command with output redirection.

So as long as you don't do anything in daemon.g that writes to file or creates log message when the machine is idle, removing power is fine. It's what I do.

To avoid clogging the hot end you may need to wait until the hot end has cooled sufficiently before removing power to the hot end cooling fan.