Has there been any updating on adding this feature back into DWC?

It was mentioned you can use T-1 P0, does that cause subsequent tool changes to not run the macros, the documentation does not seem to imply this.

I finally managed to make it work. I switched my 4 axes to X, Y, Z and U. I do not know why but trying A B U V didn't work no matter what I did. It might be because I still had my XYZ axis setup, so I really had 7 axes, and maybe the endstops were just checking the first axis they were setup for (i.e. X instead of A, Y instead of B, and Z instead of U)

Thanks a lot for your help @fcwilt and @Phaedrux

I ended up using Firefox. I set the web interface as my home page and that's all I use Firefox for. Seems wasteful but....

Just to finish this adventure off.

It works now, because i managed to use my original modem in bridgemode with a new router. The printer works now with the new router as before.

@Phaedrux It looks like the only way for them show up on the dwc is through a "virtual" heater? not ideal, but at least it shows me the readings

PS - I suspect the issue is that the Duet web server can respond to a maximum of 4 HTTP requests concurrently.

@chrishamm - finally figured this out. I was using 5V from the 6HC mainboard to power my display. During power off with M81, the 5V line voltage to the display would vary a lot (enough to cause the problems seen). Connecting the display to a separate (dedicated) 5V power source has eliminated the problem reliably. Probably should have used an O-Scope to quantify the variation; however, the cleaner power clears up the display.

slightly offside; language and locale aren't necessarily the same setting.

I.e I run English language and switch between English and Norwegian locale (and keyboard layout)

@arhi said in Drive 0 value in DWC?:

cool so when I start print from SD it will start from 0 and count till the end of the print. Thx.

I think so too. I believe that's what DWC uses to give the estimated completion time based on filament usage.

Wll esteps and flow rate are modifying the same thing, how much rotation is needed to move the desired amount of plastic, so where ever the modification happens is less relevant. Changing the estep is the less preferred way because it's higher up in the chain. If you treat estep as fixed based on ideal calculation, then you can modify it after either in the slicer or with M221. That way it doesn't have to change the fundamental motor config. That said either way should work, but you can see why changing higher in the chain could be more problematic.

If anyone is crazy enough to need this 🙂
https://github.com/arhi/EthernetSPI2

@dc42 - thanks i think !? 🙂

I kind of hope i 'hit 'it' in a way

@iains said in Smart Effector delta auto calibration speed:

Now I have a question on the Panel Due. My screen is a 4.3 but the software thinks it is a 7 inch. How do i recalibrate it. The calibration dots don't respond?

Flash the correct firmware binary.

I'm not really sure what could be going on. But I think maybe there is a version mis match. You haven't actually said what version of firmware and DWC you are using, but I suggest that you try upgrading to version 3.0 and then 3.1.1. Use the web config tool to get a fresh config set for v3.

there is the console page, but it generally doesn't provide much feedback unless you send wrong gcode (or enable debugging with M111)

The DWC version can also be found in the settings page of DWC.

https://github.com/Duet3D/DuetWebControl/

Now for what I had intended to post here...

While I suspect the Duet is the issue, if it works when everything is disconnected as pr above you can refer to this thread on how to test if the pins on the pi are working as they should. But I wouldn't spend any time on that before you have a Duet board with a steady 1hz flashing red DIAG LED.

@arhi said in Simplify3D send gcode directly to Duet 2 Maestro?:

@dlc60 said in Simplify3D send gcode directly to Duet 2 Maestro?:

Wait, scripting in the RRF? I didn't see that.

check out for e.g. https://duet3d.dozuki.com/Wiki/Macros#Section_Tool_change

There are normally three specified tool change macros (any of which can contain no commands if desired) that execute in this order:

Actions to do with the old tool before it is released - macro name: tfreeN.g where N is the tool number; Actions to do with the new tool before it is selected - macro name: tpreN.g where N is the tool number; Actions to do with the new tool after it is selected - macro name: tpostN.g where N is the tool number.

So you can have a macro to execute before tool is release, before is selected and after it is selected, same thing for every tool, called automatically, you just make files tfree0.g tfree1.g tfree2.g tpre0.g tpre1.g ... put stuff in ... and enjoy 😄 .. so when S3D sends T1 the RRF will execute tfreeX (where X is whatever was before T1) etc etc..

and in this macro files you can use dynamic g-code with loops and conditionals and...
https://duet3d.dozuki.com/Wiki/GCode_Meta_Commands

That is really useful. I can put the g-code scripts that I use for dual filament prints into these macros and not need to bother with what slicer I am using. Awesome! The scripts that I wrote for S3D and dual filament deliver the goods. CURA scripting is terrible and the outcome seems totally random. I have to try now. 😁

Thanks,
DLC