Posts made by Jojo 0

@T3P3Tony
okay, thank you.
I'll search there.

@T3P3Tony Is there any possibility to also write the target temperature the nozzle or bed should reach? As example sth like activated temperature?

My goal is to compare the target temperature with the current afterwards.

@T3P3Tony
Just fpound a way to write it into a c-file stored beneath the job with the same name.
So I can transfer it afterward into a excel file.

echo >>{job.file.fileName}^".c" {state....

@T3P3Tony
I guess thats no good idea, cause it will create a seperate file for each second

@T3P3Tony
I saw that already, but the problem is that the daemon.g is not able to create or find the folder.

Error: Failed to create folder 0:/sys/templog_0: in path 0:/sys/templog_0:/gcodes/2023-8-10-17-21_230808_7_KF-FDM010_D1_KF-FDM010_JB_155_110_MH-Professional-
Error: in file macro line 5 column 57: meta command: Failed to create or open file

For better understanding:

• the Job-Name: 2023-8-10-17-21_230808_7_KF-FDM010_D1_KF-FDM010_JB_155_110_MH-Professional-daemonG.gcode

• the path of the jobs: 0:/gcodes/

@T3P3Tony Thank you for your support!!!
I tried it that way, but the there is an error with the combination of the folder and the filename.
The file is just called "templog_"

I tried different ways to skip that, but the only thing worked with job.file.fileName was to name the file exactly same as the job in a text file or to write it into the gcode.

@T3P3Tony Does this work also automatically so I dont have to change the name of the file for each job manually?

What do I have to write instead of the folder "0:/sys/templog.csv" in daemon.g ?

@T3P3Tony
Thank you very much Tony,

after some problems with the command "echo" I found out that the fimrwareversion was still 3.3.
So I did the update to 3.4.6 and now it works perfect.

A question I have is if it is possible to name the logtemp.csv after the current running job so the data is clearly defined and not only called logtemp.

Do you have any idea?