Hi!

Is there anyone working on Hungarian translation for DWC?

If no one has started yet, I could do it.

@T3P3Tony I think it would be logical to add a fault state possibility to all the different subsystems, eg. tools, axes and to machine (or system) level, similar to heaters.

For example, if a tool change macro fails, that could trigger a fault state on the tool, raise a "toolchange-fault" event, and also change the current machine state to paused.
I think it would make sense to pass a "cause" to a pause (or any automatically called) macro and let the user decide what to execute depending on what caused the pause, eg. user-request, toolchange-fault, heater-fault, etc...

I think handling aborts in system-level macros could put the whole machine into a fault-state which in turn could further prevent running any other "doing" action, eg. tool change, move, home, etc. which would change any current (physical?) state.

There is something here that has to be thought out: allow executing "disable" commands in system-wide fault state, eg. turn off heater, spindle, motor, power, etc. So it is not that easy to just prevent any executive command to run.

I think resetting any fault could be done in a standardized way, just like how resetting a heater-fault works already with M562. Maybe it could be extended to be able to reset any sort of fault (selectively). Then the user could decide whether it wants an UI popup, or it recovers automatically from an event macro, or issues the command by hand, etc...

Just my thoughts...

@chrishamm Thx for your reply, I have started already. I forked the repo on GH and created a branch for the translation off of v3.5-dev as I wanted to compile it and see how it looks.

It is pretty usable already at this point, but there are still a lot of strings to go, I'd say it is 75% complete. Unfortunately I can't test everything as I do not have everything on my machine, but I'll try to do my best.

Btw, this is the first time I have seen the 3D G-Code viewer, this webapp is seriously sophisticated now, I love it! Thank you for your and every contributor's work!

Hi!

The docs of M200 says:

To set filament diameter without enabling volumetric extrusion, use M404.

I presume this is not valid (anymore?).

It seems that M404 does not set the filament diameter for volumetric extrusion, while M200 with a D parameter does, even without actually enabling it with S1.

echo move.extruders[0].filamentDiameter
1.750
M404 N3
echo move.extruders[0].filamentDiameter
1.750
M200 D2
echo move.extruders[0].filamentDiameter
2.000

@chrishamm Thx for your reply, I have started already. I forked the repo on GH and created a branch for the translation off of v3.5-dev as I wanted to compile it and see how it looks.

It is pretty usable already at this point, but there are still a lot of strings to go, I'd say it is 75% complete. Unfortunately I can't test everything as I do not have everything on my machine, but I'll try to do my best.

Btw, this is the first time I have seen the 3D G-Code viewer, this webapp is seriously sophisticated now, I love it! Thank you for your and every contributor's work!

Hi!

Is there anyone working on Hungarian translation for DWC?

If no one has started yet, I could do it.

@T3P3Tony I think it would be logical to add a fault state possibility to all the different subsystems, eg. tools, axes and to machine (or system) level, similar to heaters.

For example, if a tool change macro fails, that could trigger a fault state on the tool, raise a "toolchange-fault" event, and also change the current machine state to paused.
I think it would make sense to pass a "cause" to a pause (or any automatically called) macro and let the user decide what to execute depending on what caused the pause, eg. user-request, toolchange-fault, heater-fault, etc...

I think handling aborts in system-level macros could put the whole machine into a fault-state which in turn could further prevent running any other "doing" action, eg. tool change, move, home, etc. which would change any current (physical?) state.

There is something here that has to be thought out: allow executing "disable" commands in system-wide fault state, eg. turn off heater, spindle, motor, power, etc. So it is not that easy to just prevent any executive command to run.

I think resetting any fault could be done in a standardized way, just like how resetting a heater-fault works already with M562. Maybe it could be extended to be able to reset any sort of fault (selectively). Then the user could decide whether it wants an UI popup, or it recovers automatically from an event macro, or issues the command by hand, etc...

Just my thoughts...

Hi All,

I am not sure whether this has been asked or not, but I couldn't seem to find anything nor could I manage to make it work. I wanted to pre-"extract" the part of the object model, namely a heater and an extruder associated with a given tool, to later do some queries on it with less clutter.

var tool = 0
;--- FIXME! - these assume one heater and one extruder per tool
var toolExtruder = move.extruders[tools[var.tool].extruders[0]]
var toolHeater = heat.heaters[tools[var.tool].heaters[0]]

;--- These are not working:
echo var.toolHeater.current
echo var.toolExtruder.position

If I enter global toolExtruder = move.extruders[tools[0].extruders[0]] in the console, then I enter echo global.toolExtruder then it shows that this is an {object}. So I assume that the variable assignment has worked. I feel that it should work somehow, but I failed to figure out how to reference its members. Tried with using all kinds of parenthesis, without any luck.

Is this possible with some syntax?