@droftarts said in I could use some help:

@mac @fcwilt you had the z probe working. Using an endstop on the low end is a retrograde step.

Ian

In your opinion. I see it as a distinct improvement.

X and Y can be homed with no Z movement required.

And generally Z homing can be faster.

But that is just my opinion.

Frederick

I was among the first users of Duet on a CNC machine over four years ago. Back than I had a genuine, first version, Workbee, with several years of using GRBL on another low cost CNC. While Duet was lacking features of GRBL that I was already used with, the old Pololu DRV8825 drivers were not up to the task and I decided not to spend to much on proper Leadshine drivers. So Duet looked perfect as a hardware platform.

With CamBam for the CAM part, configuring it to generate a GCode that was understood by Duet back then was OK (G2 and G3 were not even planned back then, not to mention the work coordinates!). I wrote on the forum about the issues that I have found, I complained about some of the missing features, and things slowly got better.

These days the Duet boards are a good choice, depending on the CNC you want to control.

3 years later problems started to creep in. Being an Electronics engineer, I started digging. It all came down to the on-board drivers. Randomly, only at powering on, they reported disconnected and/or shorted steppers. I checked all connections, I replaced connectors, I ended up replacing cables - no luck! And, worse, sometimes I was not able to use the CNC for a whole day. Once started, all went flawlessly! I was not the only one with the symptom, just search the forum for "phase disconnected". There was no clear solution to the problem!

My ten cents - even if properly cooled, using the on-board drivers at 2.4A (my steppers are rated for 3A) for hours at a time is affecting them over time. The higher power drivers on the Duet 3 board should be better. But there is another problem - the supply voltage! You can't get proper performance from the steppers on a larger CNC without using at least 36V as supply. Even the new Duet 3 boards are limited to 32V.

So I decided to put the Duet board to storage and moved to PlanetCNC MK3 with Leadshine drivers. The bill was slightly higher, but not hugely higher (less than double!). And it comes with a lot of CNC specific bells and whistles.

@chrishamm Oh and Ill check the voltage next time it happens.

@chrishamm

I finally returned home and tested the new FTP code.

On all of my printers (two Duet 2 WiFi, one 6HC and one Mini 5):

I was able to download all of the files from the SYS folder via my FTP client I was able to upload all of the files to the SYS folder via my FTP client

No sign of file loss or truncation.

I will now continue with my normal activities using FTP and see if I encounter any problems.

Frederick

@droftarts Ah I used v40 from another post, but V0 makes sense and I will update

@phaedrux so I think I have solved the problem

I looked at the motor config recommendations, and found that we had interpolation on for the M350 command. I turned it off and I could spin the motor at 13000 with the full 8.25 expected rotations.

now I want to verify I am understanding the problem fully and why this worked. because the duex still works and still has interpolation on. how could this be?

@agusano the only type of endstop supported for extruders is a stall detect endstop. This allows you to feed filament quickly through a Bowden extruder (typically using reduced motor current) until the filament reaches the hot end. As others have said, if you require some other sort of extruder homing, you can temporarily change it to be an axis.

@lbtqsb at present only a single idle current setting is a available. I have have it on my work list to support per-axis idle current setting.

@mbtobeca you need to use a more recent version of gcc that produces smaller code. The required compiler version is specified at https://github.com/Duet3D/RepRapFirmware/wiki/Building-RepRapFirmware.

@phaedrux I made your recommended change.

I would say it made it a little more reliable (based on the 4 days I've had it changed) but did not fix the issue all together.

Still had to power On and Off three times his morning to get it connected to internet.

If you have anymore recommendations, id be willing to give them a try

@buurman

There is a video out there showing that microswitches are actually very, very good when it comes to repeatability.

They are simple, safe and if you don't use the plain kind (not circuit board) they only need 2 wires. If you go the route be sure to the the COM and NC connections.

The kind with the circuit board have a couple of advantages (usually). They provide an LED to verify state. The signal is actively pulled-down or pulled-up so the signal wire to the Duet is never dealing with an open circuit which can act like an antenna pickup up noise.

There may be kinds a circuit board that don't behave that way but all the ones I have used do.

Frederick

I would also appreciate support for the ADXL345.

@moth4017 said in need Guru on duet 3 mini5 using stall guard/sensor less homing:

@fcwilt

I have the x y sensorless homing well just a gentle tap for homing,
the Z homing max also works with a gental tap, but sometimes the motor just stalls and doesnt move.

That suggests you are reducing the current too much (I assume you are reducing the current) which helps with obtaining the gentle tap but also may be creating the lack of movement.

Frederick

@oliof
Finaly get it working
Here it is

var endstop0_triggers=0 var endstop1_triggers = 0 var endstop2_triggers = 0 var endstop3_triggers = 0 var endstop4_triggers = 0 var endstop5_triggers = 0 var endstop6_triggers = 0 var endstop7_triggers = 0; while iterations <30 M106 S1.0 if sensors.endstops[0].triggered set var.endstop0_triggers = {var.endstop0_triggers+1} ; ; if sensors.endstops[1].triggered ; endstop1_triggers = {endstop1_triggers+1} ; G4 P400 M106 S0 G4 P500 ; this adds a 1 second pause, if you want to measure every second, measure your cycle time and reduce the pause accordingly echo var.endstop0_triggers echo >>"sys/counts" var.endstop0_triggers

I've no idea if any of this is relevant, especially as I'm not too concerned about the speed of DWC but I'll throw it out there anyway as people were commenting about board types and wired vs wifi etc.

Uploading a circa 40 MB gcode file from my aged wifi connected laptop to the printer via DWC takes around 58 seconds at a reported transfer speed of around 750kbits/sec. Uploading the same file via my desktop Ethernet connected PC takes about half that time at a reported speed of roughly 1.6Mbits/sec. Transferring that same file from my Desktop (Ethernet) PC to my aged (WiFi) laptop takes around 3 seconds (no idea what speed that was because it happened too quickly for me to catch it).

All that means is that transferring a file to my printer SD card is about 10 times slower than transferring the same file, from the same machine, to a (aged and slow) Laptop, but it probably proves nothing. It's not my field of expertise by any means but I guess there area number of things at play here, not least of which would be the write speed of the SD card and/or the size of any cache files? It probably has nothing to do with DWC.

@wapuraralf did you get this solved ?

@deckingman This does help me a lot, thank you!

@pro3d you're right, I confused this with the 2209s. Apologies.

@pickett most corexy setups move the bed to the head rather than the other way, so its very common.
-z moves the bed up, +z moves it down. Its no different to a moving gantry setup.

@grahamsoukup

Make sure to update the configuration and macro files to those compatible with RepRapFirmware 3.4.1

The instructions can be found on the modix support site, and you can download them here

https://github.com/Modix3D/Modix-V3-configuration-and-Macro-files/releases/tag/v3.4.1.a

@hebigt said in How well does RTV silicone stick to a silicone heater?:

@mrehorstdmd Interesting, thank you for including the photo. I never would have guessed that would be the outcome of a bubble. Those traces must get hot!

It's fairly easy to trap a bubble of air under such a heater during application. It has to be done slowly and carefully. Using a seam roller to try and insure the best possible adhesion can also helpful.

Frederick

@droftarts Thanks very much. That sorted it.

@aceycv8 said in FW Bug? Heatbreak Fan thermostatic Control issue:

I've upgraded to 3.4.1 however my heatbreak fan will now run at full speed and i can't lower the speed.

The M106 S parameter is now ignored when a fan is configured as thermostatic. This is documented in the release notes for one of the releases you upgraded to or skipped. You can still use the maximum PWM parameter to limit the speed in thermostatic mode.

@phaedrux would I use M591 D0 S1 to enable and M591 D0 S0 to disable and would I need to change S1 to SO disable them in config.g?

Shouldn't it be disabled in tfree rather then tpost?

I haven't used these before so I'm tryting to figure it out now. I should have a tfree, tpre and tpost file for each tool correct? I am using a single nozzle with 4 extruders.

Here is what I have for my tfree0.g, tfree1.g, tfree2.g and

M83 ; relative extruder mode G1 E-150 F300 ; retract 150mm G1 E-300 F2500 ; retract 300mm

for tpre0.g,

M591 D0 S1

tpre1.g

M591 D1 S1

tpre2.g

M591 D2 S1

tfree3.g

M591 D3 S1

For tpost0.g, tpost1.g, tpost2.g and tpost3.g

M116 P0 ; wait for tool 0 only to reach operating temperature M83 ; relative extruder mode G1 E450 F2500 ; undo retraction

Does this look OK?

Do I need to include a tool change script in my slicer (simplify 3d) to run the macros?

Sorry for all of the questions. Thanks