Posts made by amimafe

@gloomyandy

Wow, it's certainly very interesting and I think it might be just what I needed. I will study it well and give an answer.

Thank you very much

Hi @gloomyandy ,

The problem I see is that if I increase the jerk to improve the speed of the arcs, when the printer makes a corner it will make a very strong jerk.
Is there no way to make the printer perform a constant movement as if it were performing a straight line?

Hi,

I am performing various tests and configurations on a clay printer. I have noticed that when I generate the gcode with the instructions G2/G3 it reduces the speed to half when I make the movement of an arc.
Do you know what could be the cause of this. I have checked the Gcode and I don't see any Fxxxx command before the arcs.
Do you know if it could be a config.g parameter or is it something in the firmware?

Thank you.

Hi @marzubus

Thank you for your help.
I'm going to look into the G60 instruction to see if it can be of any help to me.

Thanks again

Sorry @OwenD ,

Yes, I hadn't mentioned that. It is a clay printer. I'm going to check what you told me about the G60 and see if this could be solved, although I think it is not exactly the initial idea.

Gracias.

Hi @oliof ,

What I want is that if at some point the 3D printer stops extruding I can pause, go back to the gcode position where the failure occurred and continue printing.
The material I print with is not plastic and I need that the correction can be done quickly without the need to modify the gcode.
With industrial PLC it can be implemented more easily, but I would like to know if it could be done with duet or object language.

Thank you.

Hi,

I want to make a macro for Duet2 that allows me to read the lines of a gcode file in reverse.
I have seen that with the M110 command you can know and establish the gcode line, but I don't know how I could implement it.
Any idea how I could do it?

Thank you!

@fcwilt

The slicers we use add a comment on the layer changes that DUET2 recognizes.

Hi @dc42 ,

I read the postRe: Job.Layer not working anymore with 3.3rc2 and wanted to do something similar. Execute a command at each layer change. Entering the layer change comment with the laminator would not be a problem.
Is there still an option? I tried to do it with creating a variable and assigning it the job.layer value to compare with its current values but it doesn't work.
The idea was to make everything more compact with the duet firmware.

Thanks again

Hi @fcwilt ,

Yes, that's the other option I had thought of, but I preferred to do it by daemon.g and if a third party manages the machine, everything is integrated with the firmware.

Thank you.

Hi,

I have been editing daemon.g to save several values during printing in a .csv file.
I have managed to get it to work correctly and it saves them according to the time I set with the G4 command.
What I want to do now is to save the variables once per layer. I have been testing with the object "job.layer" but I have not been able to do it.
Could you give me a solution?
I have thought to create a macro that is executed in each layer change calling it from the laminator, but I would like more to execute it from daemon.g

Thanks

@oliof

Gracias por tu ayuda. Me diste una pista de cual era el fallo y finalmente lo he podido solucionar. Era un error al indicar el número de sensor que quería.
Revisé el archivo config.g y lo configuré correctamente.

Declaración de los sensores en config.g:

;DHT Sensor on Temperature Daughterboard SPI CS1 pin
M308 S10 P"0.spi.cs1" Y"dht22" A"Temperatura" ; define DHT22 temperature sensor
M308 S11 P"S10.1" Y"dht-humidity" A"Humedad [%]" ; Attach DHT22 humidity sensor to secondary output of temperature sensor

daemon.g:

if !exists(global.logTemps)
    global logTemps = false
 
while global.logTemps ==true && job.file.fileName != null
    echo >>{"0:/sys/templog/templog.csv"} {sensors.analog[10].lastReading}^","^{sensors.analog[11].lastReading}
    G4 S30

@oliof

Thanks for your quick response.

Daemon.g modified:

if !exists(global.logTemps)
    global logTemps = false

while global.logTemps ==true && job.file.fileName != null
    echo >>{"0:/templog/templog.csv"} {state.time}^","^{sensors.analog[0].dht22.lastReading}^","^{sensors.analog[0].dht-humidity.lastReading}
    G4 S1

I get the following error:

Error: in file macro line 5 column 57: meta command: reached null object before end of selector string

@T3P3Tony

Hello,

I have done a lot of tests to find the optimal Jerk setting but I can't find it.
I need that for closed angles like 45º the Jerk is lower to avoid abrupt speed changes and for more open angles like 160º-180º I don't apply the Jerk and continue at constant speed.

Is this possible? With meta commands this could be done?

Thanks!

Hi,

I am trying to edit daemon.g to make a log of a DHT22 sensor among other data. (Re: while-loop to track temperature)
I manage to create the .csv file but I always get the same error on line 5:

Error: in file macro line 5 column 72: meta command: expected an expression

I am missing some number between the []?
I attach the code of my daemon.g:

if !exists(global.logTemps)
    global logTemps = false

while global.logTemps ==true && job.file.fileName != null
    echo >>{"0:/templog/templog.csv"} {state.time}^","^{sensors.analog[].dht22.lastReading}^","^{sensors.analog[].dht-humidity.lastReading}
    G4 S1

Thanks!

Good morning,

I have a large format printer with DUET2 WIFI and we have noticed that when the models to be printed have many short distances the machine makes many accelerations and decelerations. Is there any way to configure duet not to accelerate or decelerate if there is no minimum printing distance?

Thank you!

@chrishamm Thanks for your help. I was finally able to compile using an older version of Node.js. Version 18.18
I want to modify some DWC parameters to suit our machine.
I hope this can help other users with the same problem.

Hi,

I am trying to compile the DWC source code but when I launch the command "npm run serve" I get the following error.
What is the reason? Can someone help me?

Thank you very much.

@dc42

I thought the same thing at the beginning but I have tried different jerk values (from 0 to 300mm/s) with different accelerations and although it improves the movements with high jerks, it still stutters a little bit.
Is there any way to avoid deceleration at certain angles?
Our printer has a size of 3.5m for the Y axis and 2.5m for the X axis. In case this information is useful.