Posts made by JRDM

@droftarts I guess that would work but that’s more cables and connectors. I’ll weigh my options.

I could use a 3XD (3 external drivers) expansion board in my next build and I haven’t seen one available or proposed on the web.

My printer is running RRF 3.4.6 on a Duet 2.
I'm using an Orcaslicer 2 RC and it emits part names RRF doesn't like for M486 command.

The whole line:
M486 S0 A"Enclosure_Heater_Duct_for_Delta5020.stl_id_0_copy_0"

It doesn't halt printing. I haven't used part cancellation feature yet so maybe that would be a problem then.

I'm sure I can change the part names to something shorter but any chance in extending the allowed string length?

@DocTrucker Polycarbonate has good flame retardancy (V-0 and better IIRC) but easy to print grades are often heavily adulterated so you would need to check their data sheets to make sure you're getting what you want.

If it's for a regulated use you should get your parts tested to make sure the part is up to requirement. I say this because some filament manufacturers in the past have used pellet manufacturer's data rather than test actual printed coupons.

@o_lampe That's interesting. Can the second stream be interrupted?

I'd like to set up a Duet3 board to run a step motor in a constant RPM indefinitely (or until I request a different RPM), where I set an RPM not a distance.

If this is already available I'd appreciate a point in the right direction, I couldn't find it in the docs or the forum.

@dc42 OK thank you. I didn't pick up on that from the docs. I made the changes, removed my attempt at a dummy heater output. It works great now.

I have three heaters set up and in use on my 3HC. I also want to monitor and control/limit a heat break temperature to a set point. I'm using firmware 3.4.6.

I tried to set up IO output 2 as a heater but the firmware gives me a fault. I also tried to not assign it a heater and it didn't work.

I don't want an actual heater for this, I just turn on a fan if my heat break exceeds a set temperature.

With RRF 2 we used to have virtual heaters that allowed this kind of setup. Is there anything I can do? Right now I have it set up on my 6HC but I'd really love to see it on my 3HC for wiring simplicity but I seem to have run out of heater loops.

@JRDM Also 3.4.6 installs fine now too:

Firmware: RepRapFirmware for Duet 3 MB6HC 3.4.6 (2023-07-21)

@Phaedrux OK.

Also I noticed a suggestion in the SD card section to use an official SD card formatter because Windows format doesn't format the card optimally and I probably did a Windows quick format too. The docs: "DO NOT use Windows 'Quick Erase'. This generally does not create a clean FAT32 partition."

So I did that, installed 3.1.1 then installed 3.3 and it works great now. I was formatting it as you posted that so I don't know if it was one, the other or both but it works now.

Thank you.

@Phaedrux I connected by terminal and got:
M997 S0
Error: M997: In-application programming binary "Duet3_SDiap_MB6HC.bin" not found

I have the correct version of that file and Duet3Firmware_MB6HC.bin in /firmware and /sys so I don't understand why it's complaining. I also checked the file names in case that's the problem.

@Herve_Smith I tried to follow those instructions to no avail.
I screen recorded an upgrade attempt.
https://www.youtube.com/watch?v=QjLY6KMK-_I

Reported in DWC:
Board: Duet 3 MB6HC (MB6HC)
Firmware: RepRapFirmware for Duet 3 MB6HC 3.1.1 (2020-05-19b2)

6HC board version is 1.01

The board seems to run fine so far, but I haven't tried running any motors, heaters or fans yet. I don't want to get carried away with my setup until my firmware is up to date.

I try to install newer firmware. DWC's version number changes but the electronics firmware version doesn't.

I've tried installing Duet2and3Firmware-3.x.x.zip and also Duet3Firmware_MB6HC.bin for versions 3.2, 3.3, 3.4 and 3.4.6.

DWC says it's updating the firmware but when it'd done rebooting the firmware version reported in Settings and M122 hasn't changed, staying at 3.1.1.

I'm not seeing any errors or warnings. I'm not running any other Duet machines right now.

Am I missing something?

@dc42 Thank you the suggestion of deploying before and retracting after the group of G30 calls did the job

@JRDM I did do a mesh probe on a lark and reduced point count, and that didn't do the dock & undock for every point. Thankfully.

I have a Duet2 Ethernet, running RRF 2.05.1 and Euclid probe installed. Euclid is a switch on a magnet that can be docked and undocked.
I have my deploy and retract macros set up properly the best I can tell. I can do single point and four point probing for 3 screw levelling.

When I do the bed.g routine, it undocks and docks the probe for every single point. I'd understand if my M558 probe type was P9 but it's P5.

What can I do differently to reduce the excessive docking?

My config.g lines for the probe:

M574 Z1 S2
M558 P5 H8 F300 T9000 A3 S0.01
G31 P500 X3.2 Y34 Z7.7

My bed.g:

M561             ; clear any existing bed transform
G1 Z5 S2
G30 P0 X15 Y45 Z-99999
G30 P1 X15 Y275 Z-99999
G30 P2 X275 Y275 Z-99999
G30 P3 X275 Y45 Z-99999 S3
G1 X150 Y150 F5000               ; move the head to the corner (optional)

I suspect it's not needed but for good measure my deploy probe macro:

M564 H1 S0            ; Allow movement BEYOND axes boundaries (for X to reach probe dock)
G91                          ; relative positioning
G0 H2 Z10 F1000              ; move Z 15 for clearance above dock.
G90                          ; absolute positioning
G0 X20 Y270 F8000             ; move ot preflight position
M400                         ; wait for moves to finish
G0 X-12 Y291 F4000              ; move adjacent to probe dock location
M400                         ; wait for moves to finish
G0 X-12 Y300 F4000               ;  move over dock 
G4 P250                      ; pause for pickup
G0 X30 Y300 F4000              ;  slide probe out of dock - slowly at 300
M400                         ; wait for moves to finish
G0 X150 Y150 F8000           ; move to center of bed 
M400                         ; wait for moves to finish
M564 S1                      ; Restrict movement to within axes boundaries (for normal Y movement)

retract macro:

G90	                           ; absolute positioning
M564 S0                        ; allow movement outside the boundaries
G0 X50 Y300 F8000                ; move to the re-entry staging position
M400                           ; wait for moves to finish
G0 X30 Y300 F4000                ; move to the dock re-entry position
M400                           ; wait for moves to finish
G0 X-12 Y300 F4000                  ; move into the dock position
M400                           ; wait for moves to finish
G4 P250                        ; pause 250 usecs 
G0 X-12 Y290 F4000                ; move to the side swipe off probe
G0 X20 Y270  F4000             ; move away from the dock
M400                          ; wait for moves to finish
G0 X150.0 Y150.0 F4000           ; move to the center of the bed
M400
M564 S1                        ; set movement limit to axis boundaries

@o_lampe On a Duet 2? I just checked the pinout on the BTT adapter and it doesn't match the pins on the Duet2.

Assuming I don't find an existing design that works, I think I'll make an adapter using perfboard.

@o_lampe I meant an adapter similar to the "Duet Expansion Breakout Board" with level shifting for fully external drivers such as Geckos. But with that model, maybe I can two-step it because there's stepstick to screw terminal adapters with level shifters.

I have a mature and stable Duet 2 Eth + Duex5 installation. I'd like to use stepper channel 10 & 11 for experiments on the machine using external drivers.

Has anyone made an adapter board to hook up external drivers to these channels?

I don't want to duplicate anyone else's work if there's one that fits my needs.

I have a friend that is offering to sell me me a couple Duet Tool Board 1LC v0.6 he isn't using.

Is this still supported, and if so, how long will support last compared to current versions of the 1LC?