@KenW said in trigger inputs not de-bounced?:

Somewhere I have a stack of plastic and stainless steel templates for logic and electronic circuits.

I had forgotten about those what with the "rise" of computer apps like KiCad.

As well as a few storage boxes of discete logic chips.

I have two draws full of current electronic devices that I use for making things using Arduino boards and the like.

I used the rolls of paper long ago when I painted trim along baseboards.

Rolls of paper? Drafting paper? For drawing schematics?

Frederick

@axiom If you use two motors on one driver (either by using the two outputs on the Z axis, or by wiring the motors together and connecting them to the single output on any driver), that driver will have to work a bit harder, but so long as these aren't particularly big motors, or trying to go very fast, it should be fine. Ideally you'll be using a 24V power supply.

With the motors on separate drivers, you are spreading the load, and the motors can even be controlled independently. That's why people often use them for the Z axis, because the axis can then be levelled automatically. People with CNC routers often have two motors on Y, and put these on separate drivers, which allows them to square the X gantry to the Y axis. Normal commands to the axis are carried out by both motors unison. Though this isn't a particular advantage in the way you want to use them, as your motors are connected to the same belt.

I'm assuming you're using RepRapFirmware 3.x. If you are older firmware, please post your current config.g and the response to M116.

X motors connected to different drivers

If you connect the second motor to E1 (driver 4), you should add an M569 to set that motor driver. So add something like this to config.g:

M569 P4 S1 ; physical drive 4 goes forwards M584 X0:4 Y1 Z2 E3 ; set drive mapping

If the extra X motor turns the wrong way, change M569 P4 S1 to M569 P4 S0. There's also an example on this page https://docs.duet3d.com/User_manual/Connecting_hardware/Motors_configuring#using-more-than-one-motor-on-an-axis-with-a-separate-driver-for-each-motor

X motors connected to Z driver

If you connect both X motors to the two Z driver outputs (the labels don't really matter, the Z driver is driver 2), it's probably easiest to swap the Z motor onto the X driver (driver 0), assuming you only have one Z motor. This leaves your E1 driver still available:

M584 X2 Y1 Z0 E3 ; set drive mapping

If the extra X motor turns the wrong way, you'll need to adjust the wiring of the motor, and swap the two wires of one of the phases in the plug. See https://docs.duet3d.com/en/User_manual/Connecting_hardware/Motors_connecting#using-the-internal-drivers for an explanation of the motor phases. Lower on that page is a description of connecting two motors to the ZA and ZB connector.

X motors wired together in series, connected to the X driver

Alternatively, you can wire the motors themselves in series to one plug, and connect it to the X driver. You won't have to change M584 for this:

4072e6c5-0875-4a14-aa76-15aefae64f8c-image.png

If you're still not sure, please post your current config.g and the response to M116, so I can see what firmware you are on.

Ian

I'd be curious to see if it's still the case with RRF3 running on it.

@bubblevisor maybe bossa the board. Who knows what changes fysetc have made to that beta version

@dc42 said in 1HCL 1.0 closed loop controller:

@supertb1 the homing move or moves should aways be done in open loop mode, and should be followed by the basic tuning move before switching to closed loop.

You mean after homing, switch to closed loop and THEN do the tuning maneuvre? The documentation states it that way...?
Still having trouble with my Nema34's closed loop so i'm looking at everything right now.

Having the same problem here, cant get my Nema34's tuned correctly, incosistent tuning backlash and so on.

motors i'm using: https://www.omc-stepperonline.com/p-series-nema-34-closed-loop-stepper-motor-12nm-1700oz-in-with-with-electromagnetic-brake-34e1kbk50-120
Datasheet: https://www.omc-stepperonline.com/download/34E1KBK50-120.pdf

Ran through the documentation about 15 times now, including the full tuning guide. but still no succes.
It runs in closed loop tho, only with alot of vibrations and oscilations.

@mmueller70 it's as @deckingman says, you can use a common positive wire for all fans that use the same supply voltage. The thermistor cannot share a ground wire with anything else except another thermistor, because Duet boards use separate analog and digital grounds in order to provide better accuracy and less noise in the readings.

@dc42 Hi,
That's an easy one... I already have the Duet 2 Wi-Fi board!
I can't afford to just replace it with a Duet 3 as much as the more compact board etc interests me.

@droftarts

Forever in your debt . that indeed did the trick.

My config g must have lost the configuration for the DUEX2 (not5 by the way)

I uploaded my config with the repraptool and came to the conclusion it didn't have the duex2 in the file.
then saw your post

IT's back to all working now with this fan config

cheers mate

Thanks oliof,
For example, if I take GND from out6, how to configure the M950 command?
M950 E0 C"out6"

Is that correct?

@dc42 Could you help me solve this problem?

@ageis This page seems to have the best description of the wiring https://www.3dpedie.cz/en/manuals/p.i.n.d.a-v2/

BLACK > Output signal from the probe
BLUE > GND, or ground
BROWN > +5V
WHITE > Temperature sensor output

I think you have a Duet 2 Ethernet? You'll need to split out the +5V (Brown) and temperature sensor output (White) and connect them to +5V (the Z probe header only has 3V) and a thermistor input respectively. Black and Blue can connect to the appropriate connections on the Z probe header.

For configuration, define the probe with M558, the thermistor with M308 and the probe offsets and compensation with G31. There's an example in the Gcode Dictionary in the G31 entry: https://docs.duet3d.com/en/User_manual/Reference/Gcodes#g31-set-or-report-current-probe-status

; RRF 3.3 and later example of probe with thermistor and temperature compensation M558 P8 C"io2.in" H1 F1000 T6000 A3 ; Prusa PindaV2 Endstop M308 S2 P"temp2" A"Pinda V2" Y"thermistor" T100000 B3950 ; Prusa PindaV2 Thermistor G31 P500 X23 Y5 Z1.1 S21 H2 T0.02 ; Nozzle offset - Smooth Sheet

The above is for Duet 3, so change the input pins to the ones you are using (M558 C parameter, M308 P parameter).

Ian

@Phaedrux

Hey Phaedrux.

I have one Paneldue with 3.4.1 and this display is not working with any of my Duet's (3.4.6).... Therefor I dare not to upgrade the other ones, before this one display with 3.4.1 works...

@deckingman

Thank you very much for your config. I will look through mine for errors.

You are absolutely correct, i need to 3 heaters to be assigned to 3 different tools to allow for seperate control.

Thank you - will report back!

The Duet2 has no USB host interface.

Would it be possible for them to run the Duet 2 in wifi access point mode where the Duet creates an isolated network SSID that a computer could connect to?

@Drak said in Duex5 fan not connecting:

; Fans

M950 F3 C"fan3" Q200 ; create fan 0 on pin fan0 and set its frequency
M106 P3 S0 H-1 ; set fan 0 value. Thermostatic control is turned off

; Tools
M563 P0 D0 H0 F3 S"Main"

If you only have the one fan, just call it F0/P0

The fan3 port on the Duex has pin name duex.fan3

So putting that all together you'd have

; Fans M950 F0 C"duex.fan3" Q200 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off ; Tools M563 P0 D0 H0 F0 S"Main"

@achrnCan I use your files for my prusa Mk 2.5s? Would they work with a Super Pinda installed? thank

@hlwerschner I'd try running the same macro in standalone mode (you will need to insert an sd card with a sys directory on it into the board) and see what happens with that. Other than that post your full (combined) config.g file so @dc42 and or @chrishamm can try running it.

@OxFire795 Yeah i mean ilumination leds, seems like i hit one, tested 2 that are working but one is Broken so others are not on..

@jjem in RRF 3.4 and later there is a heartbeat, but a disconnection shorter than 2 seconds may not be noticed.