›

Webcam snapshot and printed information for Print-Report

Faris_SaadFaris_Saad
in Repetier-Server
My 3D printers contain automated bed emptying solutions. The beds are being emptied after a print is completed and is initiated from the END_PRINT macro. I am relying on my print reports to verify whether a print is successful or failed. Unfortunately the webcam snapshot in the print report always shows an empty bed as the snapshot is taken after the beds are being emptied. Is there a way to call out the function for these snapshots which I can put in my END_PRINT macro? Or is there another way to solve this?

My second question is, is there a way to customize the information that is listed on the print reports? For example, I don't really care about the achieved temperature precision and the long text below it. I also would like to customize the Event Notes at the bottom to list more user understandable error messages, like: Emergency pressed, Filament runout, Filament Jam, etc.

Best regards, Faris (Felix / LFT / Insolution)

Comments

  • RepetierRepetier
    You can add a constant message to the reports and with custom g-code you can add own messages as will, see

    @writeReport Message

    Write a message to the print report with timestamp if reporting is enabled.


    Regarding snapshots I see the problem. Belt printers might also have same issue, so having a custom command to trigger the image would be a good idea and if it was not triggered we still can make one like we do now. Will put it on my todo list for improvements.
  • Faris_SaadFaris_Saad
    My 3D printers contain automated bed emptying solutions. The beds are being emptied after a print is completed and is initiated from the END_PRINT macro. I am relying on my print reports to verify whether a print is successful or failed. Unfortunately the webcam snapshot in the print report always shows an empty bed as the snapshot is taken after the beds are being emptied. Is there a way to call out the function for these snapshots which I can put in my END_PRINT macro? Or is there another way to solve this?
    Hi, is there a solution on this matter? it would be nice to have these print reports show the completed printed items.

    Best regard, Faris (Felix / LFT / Insolution)

  • RepetierRepetier
    Actually yes. There is a server commands

    @makereportsnapshot

    that when it is called makes a snapshot for the report. If such a snapshot exists it is used instead of making one at the end, so just put it where everything is fine and it should work.

    Only thing is I'm not sure if it is already in stable versions. So just try if it works otherwise it will work after next update.

  • Faris_SaadFaris_Saad
    I cannot seem to get this command to work, could you check if our current version (Felix / LFT / Insolution version 1.4.18) is yet supporting it? 
  • RepetierRepetier
    It is still present and calls in the end the same function as the report when you did not call it before. The question is when do you call it exactly? It must be while running the print and before the report generation starts.

    I noticed that feedback is not optimal in case it does not grab the image you get no feedback, so for 1.5.0 I will add some response to log.
  • Faris_SaadFaris_Saad
    mm, I see what you mean. I will call it from within the gcode file.
    Would it be possible to call it from within my END_PRINT macro for example?


  • RepetierRepetier
    END_PRINT macro sounds like klipper gcode macro. We do not see what klipper runs in such macros so that would not work. You can add it in the slicer end gcode before you move away - I mean that is the only reason you do it manually anyway so it must be run before the object is out of camera.
  • Faris_SaadFaris_Saad
    I tried various positions at the end of the g-code file, but none of them appear to be working

    https://imgur.com/a/CXOXsn8

    I am starting to believe it is not implemented yet in our version of Repetier Server.
  • RepetierRepetier
    Sorry, you are right it is not working. It had a wrong snapshot reference - it actually makes a snapshot for timelapse due to wrong function reference. Will be fixed in 1.5.0
  • Faris_SaadFaris_Saad
    No problem! I look forward to 1.5.0  :)
Sign In or Register to comment.