Posts made by 0xde4dbeef

@T3P3Tony excellent! thank you very much!

Nice, thank you @dc42!

Hello Gentlement,
I have started a pick and place project using OpenPnP and a Duet3. So far so good, the machine is moving nicely and all that is left is configure the additional axis and utility pins for LEDs, pumps and solenoid valves. Especially the latter is an issue I struggle with finding documentation.

Essentially I want to repurpose the IO pins, for example one heater pin with mosfet switch to drive the vacuum pump. I have searched the forums and documentation but I was not immediately successful, realizing I simply don't understand how RRF3 is expected to be configured. I realize there is a CNC and Laser mode for machines that are not a 3d printer, but the Gcode documentation seems that's only reltated to the laser and spindle (so does not apply to me).
So what would be the proper Duet-way of setting these things up? What are the documentation parts I need to look at? I have the impression most of the documentation is in the list of GCode commands, but searching for letter-number combinations is not exactly efficient

Any hint is greatly appreciated!

Well, the problem I ran into with Klipper, was that while klipper still knew about the current setting, but the TMC driver forgot about it. Since klipper had no means to know if Vin is present, it also had no means to know it had to instruct the driver again about the current settings. I am aware that the Duet3 monitors the input voltage.

@Phaedrux said in Duet3: TMC driver current setting after power cycle:

At least that's what I think is going to happen.

Thats exactly what cost me a not exactly cheap and especially hard to source Nema8 motor Hence I figured it's best to ask before I go to just find out by trial and error ...

I have a quick question regarding how the Duet3 handles a power cycle on the main Vin rail (as in for example turn the main power supply off with the MCU still powered via USB and then back on)?
Specifically I have the experience with a different board running Klipper that after a power cycle you need to call a TMC_INIT command manually in order to reset settings like RMS current of the TMC drivers, as they would reset when the main power rail is cycle. This did cost me a rather hard to get small motor as it burned out in a very short amount of time (only handles like 0.4A RMS). I'd like to avoid this mistake from the start

So with the duet3, will I need to call any commands after power cycle or does the firmware handle this gracefullly, as in automatically detects Vin power cycle and configures drivers automatically?

@fcwilt

You guys are extremely fast! Thank you very mch!

I am new to the duet world and in the process of setting up my new machine. It has a dual X-Motor and I am reading up on the documentation for M584. However the syntax described in the docs is not the same syntax in the config file from the generator.
The generator came up with this:

M584 X0.0 Y0.1 Z0.2            ; set drive mapping

The docs describe a syntax like this:

M584 X0 Y1 Z2:3 E4:5:6 

specifically, the generated gcode uses a dot (.) as a separator, and the docs use a colon (:) as a separator, and I am not at all certain that the separators do the same in those examples ...

Since this is a potentially machine-breaking config section I found it's best to ask in hear to clear up the situation, before I just go in and try hoping for the best ...

More specifically, how do I correctly set up the x-motor on driver 0 and 1? M584 X0.1 Y0.2 Z0.3 or M584 X0:1:2 Y0.1:2 Z:0.2:3 or M584 X0:1 Y2 Z3?

thank you!

@bearer felt if I post my issue here there is a chance it gets fixed.

i managed to upload the SDiap file via SD card and it updated fine.

I'm in the same boat, just connected to the web control on a new board, ran the config wizard, was instructed to download the updated firmware file and got this error message after upload.

Found this post via google and tried uploading the file via web interface. The upload interface in File Management/System gets stuck trying to upload the file. Just wont finish uploading, I need to reload the page to get the upload button back responding. Deleting the firmware file and uploading it again finishes successfully.