@samlogan87 best post your config and tell us a bit more about your setup

@theolodian If you want an example to reference have a look at my repo for the MQTT4DSF project. It's depreciated now, but its written in python and uses the API for talking to DSF, and should still be functionally relevant.

The API allows you to "subscribe" to the keys in the object model you want to monitor and will push updates when the values change. It can also handle executing gcode commands.

@fredih said in Extruder doesn't spin/ onlyVibrates:

@deckingman okay, thanks. That's very insightful. Yes, I did some google-fu, on how to add a second stepper for the Z-axis, and the answer was to simply add a second extruder to the configurator, then re-map it in the config file, which is probably how I ended up with double values for two extruders.

As others have pointed out, that's not the way to add a second drive to an axis. Here is some info which might help your understanding.

Any axis can have a number of drives assigned to it but things like acceleration, steps per mm, instantaneous speed change, motor currents etc are all applied on a per axis basis. That is to say, any drives associated with an axis will all be assigned the same values. If you think about, that's the way it has to be because you can't have two motors driving the same axis using different acceleration values for example - they have to synchronised. For that reason, we don't use colon separators for individual drives on the same axis - every drive will have the same values by default.

Extruders are treated similarly to axes but each extruder can only have one drive assigned to it. Tools can have one or more extruders assigned to them but that's another matter. For machines which have multiple extruders, we have to stipulate the acceleration, jerk, steps per mm etc for each extruder, just as we would for separate axes (X,Y and Z might use the same values but they might equally use different values depending on pulley size or lead screw lead). We do that by using multiple values separated by a colon. It's just a shorthand way of saying the first value applies to extruder 0, the second the extruder 1, the third to extruder 2 etc.

@phaedrux @droftarts Thank you for your response and sorry for delay on response, I finally got all the hardware and I'm with testing now the configuration and movement 🙂

Regards

@dc42 Great thanks! Are there any resources about implementing something like this?

@jay_s_uk @Phaedrux - Thanks for taking time to reply. I followed the process using BOSSA and it seems to have worked.

FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.1.1 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2020-05-19b2

Cheers,

Christian

I don't have any particular complain about the connectors, I'm pretty easy going on that regard. The very small beige ones are tedious to crimp but fortunately I've purchased the wire-kit.

I know it's already pretty small but what I would love is for it to be with one side 40mm max, even sacrificing a connector (or using a smaller one) or dropping the switches.

I'm doing a magnetic toolchange with very small heads and I'm having troubles positioning the toolboard (I'm actually thinking of using an expansion 3HC instead of the toolboard).

Hi,

I have checked the M122 B1/2 comand. The firmeware update I installed in September, didn´t install the firmeware to the expansions, only to the mainboard. Now I manualy installed the 3.2beta to expansions (with the M997 B1/2) an the mainboard. I keep you updated.

@signpostman

I haven't read this entire thread so I don't know what you mean by "Is there any other way to connect my ClearPath Servos to the Duet 3 main board?"

If you have specific questions, you should probably start a new thread with those questions and I'd be happy to help.

@HenryHil said in Big 3D printer (BigFDM):

Also I noticed that BigFDM page recommends to use SSRs for this size bed heaters. With Duet 3 it seems that we would be able to drive these with the four IO pins using four SSR or just connect a single SSR's input to OUT0 and then connect these four bed heaters to the SSR.

when mains powered SSR is the way to go for the beds, you could also probably run 4 SSRs off the single output. that would allow you to later reconfigure to use 4 outputs to control quarters of the bed, as well as lower the load and potential need for cooling on each SSR.

(not sure how thermal expansion affects partially heated bed in practical terms, but there are at least on thread on here that deals with it for a large printer).

Reduce the PWM of the heater. This way the heater will heat up slower along the heat to soak into the build platform at a more constant over all temperature. I believe that you can set the PWM on the heater tuning.

@bearer @Phaedrux

I have solved the issue by installing the unstable version (DSF Version: 2.1.3) of Duet Software Framework on Raspberry Pi. and also reverting back to RC11

The guide links to the stable version of the DSF and latest version of the reprap firmware which, at least in my case is not compatible and will lead to the "DCS is unavailable" Error.

cheers Max

The 3.0 beta firmware had a problem with frequent data corruption when you uploaded files using the on-board Ethernet. Maybe that was the reason?

Thank you @bearer and @gtj0. Sounds like it should work well. 👍

Fixed in duetwebcontrol 2.0.1

@alex-cr said in Duet 3 powering via ext 5v:

@gtj0

Careful, that link actually doesn't apply to the Duet3.

It works for my Duet3 6HC without major issues. The only piece of information missing is to pull the SBC jumpers.

Yeah you're right. Every time I look at the schematic, I get a headache.
The description for the PS_ON header says...

3-pin KK labelled PS_ON: open drain mosfet output for controlling an ATX-style power supply or a SSR. The +5V pin can also be used to provide external 5V power. A small amount of 5V power can be drawn from this pin (through an internal 220 ohm resistor), so that the control terminals of an SSR can be connected directly between the +5V and PS_ON pins. Note: on the v0.5 board this connector is rotated 180 degrees compared to the intended orientation on later version boards.

It doesn't actually say that you can PROVIDE power via that header.

The schematic does show that you can input 5V from that header but if you try to draw 5V from it, it goes through the 220ohm resistor.
428f8b31-ee34-4e8d-b56a-fff08d8b024e-image.png

The power options do seem to be spread out.
https://duet3d.dozuki.com/Wiki/Duet_3_Mainboard_6HC_Hardware_Overview#Section_Power_distribution doesn't even discuss the PS_ON header.

Duet 3 uses CAN-FD bus to communicate between the main board and expansion boards, and we plan to make a Smart Tool board using the same CAN-FD-bus.

For devices that are just sensors, CAN is likely to be overkill. Duet 3 uses a simpler interface with a 4-pin connector to connect sensors, including endstops sensors, Z probes and filament monitors. The benefit of CAN-FD is that it can handle high data rates and it can tolerate the ground noise that stepper motors and PWM'd heaters cause.