Jump to content

SowaPowa

Dormant
  • Posts

    2
  • Joined

  • Last visited

Posts posted by SowaPowa

  1. 18 hours ago, SowaPowa said:

    ...I'll post the results.

     

    -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

     

    The CPE printed fairly well the TPU never stood a chance. String city.

    TPU (2) is over 1mm high off the build plate. I'm getting the unrealistic difference message after auto leveling.

    I tried manual for the first time unsuccessfully. I'll wait til the core is swapped out before printing dual core again.

    Great time to play around with the Python code.

     

    Wish List:

    1. Modify @Unlimited Bacon's code to either set layer change capture as default or:

    2. Create Time Function with (2) arguments

     

     

     

    IMG_20180228_150400 (1).jpg

  2. Quote

    Yes.

    On Windows, V13 and V14 seem to have this feature (not tried V12 as its quite out of date).

    I didn't notice the feature until I connected an old USB web cam and expected to need to use a separate timelapse program, but a new tab appeared in the Print dialog, showing the a preview and allowing some setting changes like folder to save to and some colour correction stuff (possibly associated with the camera driver)

    However on a print that lasted an hour, the timelapse video only lasted around 10 secs, so I wanted to change how often a picture (frame) was captured.

    Looking on GitHub there are various bits of code that seem to control the timelapse.

    e.g. https://github.com/daid/Cura/search?q=timelapse&ref=cmdform

    https://github.com/daid/Cura/blob/722656b7ba94d44cdfa993e12f50a6285e939e0b/Cura/gui/util/webcam.py

    I've just had a trawl though the code and it looks like this bit of code causes the camer to take a new image

    def mcZChange(self, newZ):

    self.currentZ = newZ

    print 'Z:%f' % newZ

    if self.cam is not None:

    wx.CallAfter(self.cam.takeNewImage)

    wx.CallAfter(self.camPreview.Refresh)

    (see https://github.com/daid/Cura/blob/4d1c0da752fe45ffaf6e9257bd5d1abe86d53fe0/Cura/gui/printWindow.py)

    So I'm no expert, but it appears to be taking a photo every time the Z changes.i.e once per layer, so as my object only has 75 layers and the resultant movie is probably 24 fps, the movie is only just over 3 seconds long (which is a bit short for a 1 hour print :wink:

    I suspect that if its not too much overhear, that perhaps it could be put into

     

    
    
     

    def UpdateProgress(self):

    e.g around line 458, where it appers to get the print time.

     

    
    
     

    printTime = self.machineCom.getPrintTime() / 60

    so we could take a picture every 10 seconds using this code (probably... Note its been a while since I did any python programming :wink:

    if self.cam is not None && printTime%10 == 0:

    wx.CallAfter(self.cam.takeNewImage)

    wx.CallAfter(self.camPreview.Refresh)

     

     

    Edit.

     

    I implemented basically the change I described above, and it appears to work, however I did a print and it hung after about 10 minute.

     

    However I don't think this is necessarily a consequence of taking the timelapse video, as I have issues with power glitches, and in this case I'm fairly sure there was a brownout that hung the print.

     

    So I'll try again today and see if it hangs this time.

     

    Note. Even 10 seconds doesnt give a very long or smooth video, as at 24 fps playback, a photo every 10 secs is 1/240 normal speed, so a 1 hour print is compressed to just 15 seconds, which I think is probably too short, unless the build print is very very long, i.e even a 4 hour print would only produce 1 minute of video.

     

    Probably a better time lapse setting is between 1 and 5 seconds per frame, depending on how long the print is estimated to take.

     

    i.e Perhaps the best way to approach this is to add something to the UI where you enter the desired length of the final video e.g. 1 minute,. and the code calculates how often to take the individual pictures, based on the Estimated Print Time.

     

    ***************+++++++++++++_______________++++++++++*************

     

    @All thanks for contributing to the time lapse topic.

    the above quote discusses a previous built in time lapse capability.

    This would be useful for me as I print and run out of the office.

    Curremtly ,after unclogging, the the nozzle is leaking and it's touch and go.

    I started a print last night with CPE AND TPU and the temp remelted crystal PLA.

    Steam began blowing from the fan and globs of maple syrup randomly smeared early layers.

     

    I had to leave. I'll post the results.

     

    @Unlimited Bacon @MarcoTvM @HarrryPlotter et al:

     

    Wish List

    1. Integrate the layer snapshot timing.

    2. Add uploading of the completed file so no open ports or Pi's are needed. 

     

    Attached is a photo of the plug removed from the nozzle.

    After separating the nozzle I put it in the microwave in a mug of soapy water.

    With bit of coaxing and wiggling it came free.

    IMG_20180222_145908.jpg

×
×
  • Create New...