@Phaedrux said in Need help with stopend switch.:

It's not possible to slow down before the endstop, because it doesn't know where the endstop is before being homed. Typically homing would be done in two passes. A fast movement to the endstop, followed by a short movement back, and then a slower movement towards the endstop again for better accuracy.

Thanks.

You could also use G92 U0 to set the axis as homed without allowing unhomed movement for all axis.

@iff7378 said in Modix Big120X Upgrade:

Awesome thanks! Any idea when that release is planned to happen?

Release 3.01 should be out by the end of this month. 3.02 will most likely arrive late March or late April.

Edit: Is it possible to directly connect the monitors to the Duet 3 mainboard with the current firmware?

Yes.

@KeithW said in Problem commissioning Smart Effector.:

Do I need the RepRapFirmware.bin and the DuetWebControl-1.22.6.zip?

Yes. Or you can use DWC 2.0.7. Your choice.

What is the Symbols-RepRapFirmware-Duet085.zip?

They are files that I archive for debugging purposes, when users report unexpected resets.

Is there are recommended way to update from 1.18.1 to the latest?

Looks like you've already checked the upgrade notes, so you should be OK using your existing config.g and homing files, if you check them for the issues you listed.

Perfect... I'll get going then 😊

you'll find the reprap releases here https://github.com/dc42/RepRapFirmware/releases

Is there a lot of friction/stiction in your Z axis such that very small 0.02mm movements don't seem to register?

What version of the firmware/dwc are you using?

@dc42 bought the thermocouple daughter board last summer. It says v1.1 on the back so I'm guessing not the most recent type.

Will look into grounding the hotend - thanks!

@dc42 one other thing, on the sensor connector there is 1 GND point but I have a GND to the Probe and to the PT100 (I think anyway). Can they be joined together or does the second wire from the PT100 go to one of the T connections so use both T1 and T2?

Edit: Nevermind, I think I put the pt100 wires to Pins 2 and 3.

I may add 12864 display support in a future version of RRF for Duet WiFi/Ethernet, however it will need a small amount of external hardware (74HCT08 chip) to interface the 3.3V signals on the SPI daughter board connector to the display module.

@Vasir I am interested to know if you were successful. I have a X1 and just got a Formbot Troodon, for work, with a Duet 2 wifi and I like the interface better than on the X1. Please let me know if you would do it again given your experience. Thanks

+1 on the PA21 crimper.

I have about 3 or 4 PA "engineering" crimper's in various sizes to handle most of what I do, i personally dont like ratchet style crimpers as it is too easy to mess up and fiddly and a down right P.I.T.A to unlatch if you need to "re-set" the crimp for any reason.

@Archeantus See comment here https://forum.duet3d.com/post/131959

Basically, they are in the works, but focus was on getting the tool board finished. No timeline for delivery, yet.

Ian

@sven Where did you get the config.g file you are using? Is it from BLV MGN community? It is a complicated config.g. If you don't understand how this configuration works, it is going to be very difficult for you to build your printer. You need to read the documentation; translate it with google. Unfortunately it is not 'plug and play'.

No, you do not need a fan connected. Are you pressing the fan +/- buttons?!

I'm not sure why you are getting the 'Error: over temperature shutdown reported by driver(s) 1' message. Did you reset the Duet after running '04-Test_motors' macro? This may overheat the Duet if you left it for long enough.

Please replace your config.g (make a copy of it first) with the one below.

; Test configuration file for Duet WiFi ; General preferences M80 ; Turns on the ATX power supply
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves ; M667 S1 ; Select CoreXY mode ; Network
M550 PBLV mgn Cube ; Set machine name
M552 S1 ; Enable network
M586 P0 S1 ; Enable HTTP M586 P1 S0 ; Disable FTP M586 P2 S0 ; Disable Telnet ; Drives
M569 P0 S0 ; Drive 0 goes backwards blv: its was S1 M569 P1 S0 ; Drive 1 goes backwards blv: its was S1
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes backwards WAS 0
M569 P4 S1 ; Drive 4 goes
 M584 X0 Y1 Z2 U3 V4 ; Drive mapping M350 X16 Y16 Z16 U16 V16 I1 ; configure microstepping with interpolation M92 X80 Y80 Z80 U80 V80 ; set steps per mm M566 X900 Y900 Z900 U900 V900 ; set maximum instantaneous speed changes (mm/min) M203 X6000 Y6000 Z6000 U6000 V6000 ; set maximum speeds (mm/min) M201 X500 Y500 Z500 U500 V500 ; set accelerations (mm/s^2) M906 X1000 Y1000 Z1000 U1000 V1000 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout M564 S0 H0

This is a simple config.g, just for testing motor movement. It creates 5 axes; X, Y, Z, U, V. Connect one motor to each stepper motor output. Best with just the motor, no axis connected. When you reset the printer, and connect to DWC, you will see 5 motor axes. Use these buttons to test movement of each motor:

edefc75c-070f-497c-9046-56fd0e22dd58-image.png

DO NOT connect/disconnect motors when the Duet is powered on. This can damage the stepper drivers.

Let me know which motors work. If that still does not help, please post a picture of your Duet and wiring.

Ian

@bjackson said in Updating a FolgerTech FT-5:

@jay_s_uk No, I did not know that. Since I'm a bit new to this community, after reading some of those posts I'm concluding that I should probably not stray that far into the world of "beta" configurations.

Also, my recent experiences with these BigTreeTech SKR 1.3 boards have made me worry a whole lot about their quality control and longevity.

I had one of the boards evidently working normally, when all of a sudden the PC bonged like it does when something happens on the USB port (which had been connected and in use). I told Repetier to reconnect, but it could not. Based upon what I could see on the PC, it looked like the USB cable had become unplugged, but it had not.

I finally did unplug the USB cable, waited a few seconds, and plugged it in again. The computer did not react. A few seconds later a little six legged SMD component of the SKR board burned up with a flash of fire and small puff of smoke. Not good!

About a 1/2 hour later I noticed the computer that had been connected to the printer was off. The thing is, I had not turned it off. Yep, it's what you might have been expecting: the computer was off and would not restart. Had to replace the motherboard.

Also worth noting is that we designed the Duet hardware to support 3D printing firmware efficiently. All the PWM outputs are generated in hardware. Control of stepper drivers using SPI or UART is done using a hardware serial port built into the microcontroller, and DMA to send commands and read back status with minimum CPU usage. Whereas the port for LPC-based boards such as the SKR 1.3 uses software PWM and software serial to control TMC22xx drivers, because the hardware doesn't provide the required functionality.

The guys who did the RRF port to LPC processors did an amazing job (especially squeezing the firmware to run in 64K of RAM), but they are handicapped by the hardware.

EDIT: I've solved the problem below, the heater supply and drain were crossed, meaning I was PWM controlling the whole supply to the tool board rather than just the heater.

So, an update. Everything is now connected. BL Touch is working, thermistor is working, extrusion motor is working. I am having a problem with the fans though.

When the hotend heater comes on, the heatsink fan completely dies, as PWM starts to kick in as the heater reaches it's setpoint, the fan starts to ramp up again.
Without the heater on, PWM behaves as expected on the fan.
I have power to the tool board coming direct from the PSU, wiring is sufficient diameter, nothing feels like it's getting warm where it shouldn't.
It appears to be a voltage drop issue where supplying the heater causes the fan voltage to just die. Connecting the fan drain to ground gives no improvement, the fan dies when the heater is supplied. I can't work out why though? It's a standard V6 heater at 35W (1.46A @24v) the wiring and connectors used should be good for 5A at least.
As luck would have it one of my Fluke leads also died today so I can't even measure it reliably.
Here's how I have it wired, 24v from PSU, drain from each the fans and heater go to the corresponding drain pins on the Duet mainboard.
3566b470-d51b-4d06-99aa-9a27083abd1f-image.png

You are absolutely right! Thank you! Don't know how i missed that...

@peterfrosta My personal opinion is that you have to be very careful indeed before concluding that filament slippage may be an issue. The only reports I've seen as evidence of it are where people have extruded 100mm or so of filament, and measured the filament itself. The problem with that is this is not reprentative of what happens in "real life" because a 100mm filament move would need an XY move of many metres, which will never happen unless you have a really large printer. Also, it is highly likely that if slippage occurs, it would be due to back pressure which will build up during the course of a long move. Therefore that slippage might only happen after say 50 mm of filament has been extruded and there may be no slippage on the first 50 mm, or so which is the band within which most "normal" print moves occur. So using non linear extrusion may be compensating for something that does not happen under normal circumstances. Hence you need to be very careful before deciding that a print issue is due to filament slippage.
That's just my opinion - others will likely disagree.

@Dz said in Duet 2 Wifi IoT module is disappointing:

This my gcode upload times from ~15-30m to ~1-2 minutes.

Does this fast upload go through the disappointing esp8266?

What's special is that M106/M107 commands with no P parameter (as commonly generated by slicers) are routed to fan 0 by default, unless you change that in your M563 commands. So it makes sense to use fan 0 for the print cooling fan, and fan 1 as the hot end fan.