Duet Controller/Fusion 360 post fix

Agreed access to the parameters and notification of your current offset would be a godsend but does not seem to be available on the Duet.
The changes to g10 are discussed on the duet forums here. Agree its not NIST (but very handy). It doesent seem to be in the Wiki yet.

I used VS code to build the zip, but first i used a text editor on the Appxxxx.js file in the www/js folder on the sd card. If you remover the tar,gz the system will use the uncompressed file you may have edited.

 

Thanks, I hadn't seen that, I'll modify my macros.

 

Hi,

I have just found this thread. If anyone still has any questions which need answering please let me know

Ryan

 

Hi Ryan,
I've been using 1.0.7 Beta for some time and for my single WCS applications it's much easier to use and a great improvement over the 3d printer DWC versions.
For a typical new part, I can now
1) Power on, HomeXYZ
2) Jog to corner of workpiece (I don't have a corner probe)
3) Z Probe for tool length (I have a Z Probe macro that Sets the XY workpiece zero as well as the Z, so no SETXYZ needed)
4) Run the Program

Perfect (less is more) for most things that I do.

The hard-coded G53Z94 in the Goto Work Zero, isn't correct for my C-Beam machine, fortunately my maximum Z is larger, otherwise the machine would go out of limits, but that's only a minor detail. Maybe a macro could be used, unless you can read the Z after the Home macrocall ??
Anyway, I've just spotted that you have Beta2 since 23/08, I'll install that tomorrow.
Good to see you on this thread! Geoff

 

Hi Ryan,
I have done some tests of DWC 1.0.7 Beta2; looking very good so far, here are a few questions and requests:-
1) What is the large "Compensation & Calibration" ComboBox above the Jog Controls to be used for?
2) A display of programmed Spindle Speed RPM, optionally with the corresponding Makita or Dewalt rotary dial number would be nice.
3) Could the feedrate units be displayed in mm/min or in/min since these are the standard units of the F address (NIST), or maybe a Settings option to display units/s or units/min?
I think wherever "Speed" is written it should say "Feed" or "Feed Rate"
4) The feedrate over-ride (Speed Factor slider) doesn't take effect until a number of moves in the Gcode buffer are completed , which can be long and too late to avoid cutter, workpiece or machine damage. I see that the DWC is sending M220, so presumaby this is a Duet Firmware issue.
5) Z Babystepping is a very useful function, but I think "Adjust Tool Length Offset" or similar would be a better title for the WorkBee, probably an age thing!
6) For advanced users with multiple vices or other hold-downs, multiple WCS would be beneficial and Fusion 360 caters for this, although so far as I know Vectric software doesn't.
Ian McFadden has suggested and implemented a current WCS scenario for the DWC whereby WSC selection would be manually via the GCode console. The Fusion360 post-processor will output with all appropriate WCS codes. This scenario also works for the solitary G54 which is default, and would require no further input.
Geoff

 

Hi @GeoffH

Thanks for the feedback some great suggestions in there:

I will see have the Go To Work Zero command, and probably change this to either a macro file or system file so it can be customised.

1) This be used when we introduce our touch probe, i am still too delve into that and remove what is not needed
2) Now on my TODO List
3) Also Now on my TODO List
4) I probably can't change this as i think it is firmware, but i will double check
5) Thanks for the suggestion, i will see if it can be renamed better.
6) Working on this as we speak in the interface via a dropdown list above the movement commands

Ryan Lock

 

Alex - I am not in favour of hard-coding, I think you misunderstand - Geoff

 

Alex, sorry to hear that you are having a bad time at the moment.
I think Ryan is implementing buttons like Set XYZ in js because they should never require changing and will not contain any hard-code, (Ian has removed the only hard-code (G54) in his modifications for multiple WCS).
When you get around to installing DWC v1.0.7, I'm sure that you will agree that it's a great improvement for CNC Routers.
- Geoff

 

@Alex Chambers @GeoffH Yes i agree for experienced users having things hardcoded isn't ideal, but i do have to keep in mind new users that who buy our machines. I am thinking that i will keep the Set Work Zero buttons hard coded as i can't think of any reason why these would ever need to be different. But the Go To Work Zero to be a system setting file, not a macro. So still editable by the user, but not in the Macro folder. The reason being is that is linked directly to a button on DWC, so is a system file.

I am working on at the moment switchable work coordinates directly in the interface

 

Yes Ryan, I agree with that.
Regarding the work coordinate selection it looks like the Duet will support G54 to G59.3 which makes 9 in total.
It would be neat to see the current WCS adjacent to the Work Coordinate display, eg a drop-down list
But I might be too late
Geoff

 

Hi Geoff,

Thanks for the info, i finished it off last night . I just need to remove the hardcoding of Go To Work Zero now.

Ryan

 

Hi to all JavaScript aficionados on this thread, I'm certainly not one but I've been pondering!

Duet Macros are useful but restricted to straight gcode text files with no embedded scripting language.

Since the DWC is JavaScript based it occurred to me that it would be useful if an additional layer of js functions could be written that could be called from both the DWC (eg for probing) and from the executing Duet Gcode program? These functions / methods should be easily accessible to the user, not requiring to be built with the DWC, not to replace Macros but additional, to provide greater flexibility when needed.

By way of an example, Post-Processing in Fusion 360 is JavaScript based which gives good control and flexibility, compared to the flat Configuration File used by Vectric for Post-Processing, which whilst being quick and easy to use, can be restrictive if you want to do something special.

I'm not familiar with JavaScript Frameworks, so I wondered if anyone in this thread has had similar ponderings, and might know how to do it?

Geoff

 

@GeoffH Sounds like a unique idea i haven't heard from before. I am not a js expert, just about good enough to program the interface. It could potentially be possible i will have to ponder it some more

 

Hi Ryan, what I described is for the future, maybe best from the Duet people, if they are interested. Then merging your changes with a new DWC from Christian may be a challenge for GitHub?
Keep up the good work! Geoff

 

Hi Ryan, I noticed that Beta 3 has arrived, I will install that later, but I noticed that the Probing macros still have G10 P1 ... I believe the P1 should be removed to use the current WCS (from Ian here), also G54 should go. Geoff

 

Yeah this one brings in Work Coordinate Selection. Integrating touch probe into the software is what i am working on now, so it will all be re-done on the next Beta and there will be no touch probe macros. Here is a sneak peak of the touch probe settings.

 

Hi Ryan. Ok didn't know you were planning to remove your Z-probe macros. Geoff

 

Hi Alex, no I didn't change to NC.
That's assuming that you are using your own config.sys, because I can't remember if Ryan has gone to NC in 1.07?
You will have to check your probing macros from what I remember, generally remove any G55 that you may have in any macro?
You will have to change the G55 to G54 output in your Post-Processor for the first work offset, G54 is default, so it's not needed. The standard vectric post grbl(mm) doesn't output a work offset, so that's ok.
Other than a much better DWC, the main idea in 1.07 is that the macros work with the currently selected work offset.
You can make others current from the drop-down or entering G55 etc. at the Console. That said, I'm not using multiple offsets so I can't say how well that is working?

Geoff

 

Yes Alex, I'm using a probe, and I still use macros for that. I think Ryan is writing some js to do probing from a DWC pull-down, but you can still use macros if you want. I noticed that Duet may change to G38... for probing instead of M585 which isn't standard, so macros/js may need changing a bit when that happens. Homing is still using macros. Geoff

 

Hey Guys, the probing macros will be replaced with GUI buttons in 1.0.7. Initially, the buttons will be not editable, only configurable via settings, but these settings should cover most configurations. In future i may add an option for advanced users to link their own macros to the GUI buttons, and override our defaults. The new buttons will work with NO and NC probes. In 1.07 you can select your WC, which ever one is selected is what the commands will run in. The homing isn't changing in 1.07

 

Hi Alex, macros are implemented in the Duet control, the DWC has a GUI to manage and call them from the macros/system folders, I can't believe that this will be removed in 1.07, it isn't in Beta3.
I think that Ryan is simplifying the DWC for new or basic WorkBee customers who are not interested in macro writing or modifying, but shouldn't restrict anything for more advanced users who may want to use macros for a variety of things including specialist probing - Geoff

 

Yes Alex, optionally calling macros from the buttons would be good, maybe specify the macro name in the appropriate settings form, or similar?
Didn't know that NC was now used for WorkBee limit switches, yes that would seem to be a problem with a simple DIY touch probe using the Zendstop, I guess?? Maybe commercial probes will have NC/NO options I don't know or you could use one of the extruder endstops for probing? Geoff