@nikscha The Duet 2 WiFi is set to spreadCycle continuously. You could try running it in spreadCycle on the Mini 5+, and to avoid coil whine have it switch to stealthChop when stationary (set changeover speed at below the jerk value). The spreadCycle on the Mini 5+ is different from the Duet 2; they use different drivers, and different versions of spreadCycle.

Are the other axes noisy? What happens if you swap motors over?

Ian

Hello Ian, that's right, that's how it works without the M950 command.
Thank you very much and problem solved now, thank you.

If these are neopixel LEDs, you could cut out the Arduino middleman and drive them directly off of CONN_LCD

https://docs.duet3d.com/User_manual/Connecting_hardware/IO_Neopixel_DotStar#connections

That will require adjustment of the macros setting the LEDs but will likely be a better setup overall.

@thaug29 oops sorry, yes, io0.out, not io1.out.

Ian

@R006 said in sd card corrupted:

Means you say i can't use the board?

If the DIAG light is on with no SD card inserted, most likely the firmware has been erased. I would disconnect everything, remove the Duet from any enclosure, and test it on your desk with only USB plugged in.

Connect via USB only, and check that the 5V and 3.3V LEDs come on. Make sure to manually erase the firmware (with the erase jumper, see https://docs.duet3d.com/User_manual/RepRapFirmware/Updating_firmware#all-other-duet-boards), in case the firmware is corrupted and causing the board not to start properly. Check how hot the SD card, WiFi and MCU are getting. Check if the board is being seen by your PC (device manager in Windows, system report on MacOS).

If the board isn't being seen on the USB port by your PC, and things are getting hot, it's most likely that the board has failed, and is likely to be uneconomical to repair. It's hard to say what caused it to fail, though the SD card and WiFi getting hot does usually mean a short of VIN to 5V or 3.3V. If you want to post a good, sharp, high resolution image of both sides of the board, we can have a look for failed components.

Ian

@Jeronimo88 said in Duet mini 5+ Ender 5 plus Z double stepper drivers not working:
In the future it would be better to start a new thread for a new problem....

In your bed.g the break statement is not being seen as part of the if statement (If what you have posted actually matches your file). It should look like this....

; called to perform automatic bed compensation via G32 ; ; generated by RepRapFirmware Configuration Tool v3.3.16 on Tue Aug 08 2023 14:15:35 GMT+0200 (Central European Summer Time) M561 ; clear any bed transform G28 ; Home while true G30 P0 X25 Y166 Z-99999 ; probe near a leadscrew, half way along Y axis G30 P1 X315 Y166 Z-99999 S2 ; probe near a leadscrew and calibrate 2 motors if abs(move.calibration.initial.deviation) < 0.01 || iterations > 5 break ; set the Z=0 datum which may have changed due to bed leveling ; step 1 - move probe to center of bed G1 X{175-sensors.probes[0].offsets[0]}, Y{166-sensors.probes[0].offsets[1]}, F6000 ; step 2 - do single probe which sets Z to trigger height of Z probe G30

Your file also has a mixture of tabs and spaces used to indent the code, this is probably not a good idea as it causes lots of confusion.

@droftarts

That's sorted it!! Thanks you so much! I'd just assumed that having put the files in there and gone through the upgrade on the main board that they would also get done, hadn't realised that I needed to do them seperately. Also can't believe I didn't think to check it 😛

A further update and a moment of head banging/thinking aloud...

While the stepper motors work as expected, without sending a bunch of mystical runes to the TMC2209 chips via the UART port, the current flow is causing "toasty" steppers. As I am using a PanelDue I tried to jump the UTXD1 pin from the ESP32 port (not used) to the Mini 2+, only to discover that it doesn't seem to actually allow external access via M575 P2... trying the UTXD0 port that the PanelDue would otherwise work resulted in the next problem that I can't seem to resolve - actually sending the mythic runes (ASCII representations of the HEX codes I want to send). It seems that M117 will only send character strings, not hex values.

M118 P2 S"ìU»ìU=

‚"
Error: M118: control character in string

If I could send a bunch of HEX values directly I can bypass "control character" by feeding the TMC the desired string (05 EC 10 55 BB 05 EC 10 02 55 3D 05 90 01 1A FF 05 90 01 1A 0A E6) more or less "hey, can you maybe look at setting IRUN to 800mA, thanks, I don't like my steppers melting" - other mystic runes set microstepping, StealthChop etc etc.

Anyone figured out how to send fancy fancy via M117? Failing this I shall have to figure out another way to send the settings... or resort to old school external stepper drivers with trimpots and jumpers to set what I need.

@Kiwi-0 what is the exact error message you are getting?

@dc42 are there any potential issues if the 24V is on the board before the 5V? Should the SBC Duet systems boot order be: Screen, Raspberry Pi, then Duet?

@kans Apologies for the delay in getting back to you. It does look like the right-most pins of the SD socket are poorly soldered, and probably not connecting. Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.

Ian

@fcwilt Thanks, that answers all my questions. I will indeed go that route: the 6XD for all servos and closed loop steppers. and if i have a normal stepper i can always choose to use the 3HC addon or the tool card or an extra external driver. Solved.

@droftarts I maybe moving it off the SD card in the near future. I don't believe the RPi's treat SD cards differently to any other storage. I think it means if you run gcode outside of a build/print process the endstops don't work? Perhaps macros are in a bit of no-mans land there?!

@FrankHowardNUSA Stock Railcores use a Duet 2 or 3 mainboard only, no additional CAN connected boards, as far as I can see. Anything beyond that is a 'custom' setup, and is going to require you to configure and maintain the setup yourself.

However, this forum (and the Railcore Discord for more Railcore-specific questions) is here to support you, and the latest version of the configuration tool should get you most of the way in setting up the machine; see https://configtool.reprapfirmware.org/

For your actual choice of boards, as the mainboard is only running the Z axis, if you are using the LDO-42STH40-1684MAC NEMA 17 motors (1.6A), a Duet 3 Mini 5+ would be plenty for them.
For the X and Y motors, a NEMA 17 motor (the same as Z) is specified in the BOM; is there a mod for NEMA 23 motors? 2 x Duet 3 M23CL closed loop motors can be used if so. The 6HC and Mini 5+ support them.
For the toolboard, as you want a scanning Z probe, you may as well use the new Roto toolboard. It would be capable of driving your Bondtech BMG and Mosquito, as well as having the SZP (and accelerometer) built in. You may have to create a custom mount for it on the toolhead, though.

For CAN connection advice and cabling, see https://docs.duet3d.com/en/User_manual/Machine_configuration/CAN_connection

Ian

SOLVED - Cable
The cable used was a traditional RJ11 phone extension cable. The ends are not the same, which created the confusion of the wires being associated with L & H.
I've switched to a twisted pair cable and all is working as designed.
Thanks for the input and time, as I worked through this speed-bump.
For reference see the pics and notice the flipping of the cable.
RJ11_ORIG.jpg

RJ11_ACT.jpg

@dc42 said in Duet3 mini -> fastest read interval temperature-sensors?:

@L_B_ RRF produces a reading for each temperature sensor every 250ms. You could read them more often if you compile the firmware yourself. The constant that controls it is this line in file CANlib/src/RRF3Common.h:

constexpr uint32_t HeatSampleIntervalMillis = 250; // interval between taking temperature samples

You might also need to reduce the number of ADC readings averaged per reading.

-> Could you please be kind to point me to where to find the Analog-digital-conversion (I assume) readings averaged per reading...?

@wildblue DB2W40300L is a part number so you can look it up, basically a 3A 40V Schottky diode. D18 is a 1A fast recovery silicon diode rated 40V or greater.

@DocTrucker no negatives i can think of