search

MarkWheadon / velocity-painting

#VelocityPainting: patterning 3D prints by modulating the print speed
Other
198 stars 31 forks source link

zOffset portion defaults to extremely slow speed #15

Closed markingle closed 7 years ago

markingle commented 7 years ago

I got some time to test the new version of velPaint while traveling and found an issue with the zOffset section generated at a very slow speed @ 600/mm. My testing was done with the Cylinder Print Type.....seems like it should be set to the lowSpeed value?

screen shot 2017-04-02 at 12 14 27 pm screen shot 2017-04-02 at 12 14 12 pm

The interface is a great addition! Great work Guillaume!

.

MarkWheadon commented 7 years ago

That does look odd. It also looks like there are holes in that bottom section (on the right for example)? Could you attach the files you used to create the above scenario?

MarkWheadon commented 7 years ago

FYI I don't know if Guillaume is listening here. Are you listening Guillaume? :)

markingle commented 7 years ago

The holes are part of the design! There is a tiny drawer for the new ring! :)

files are attached....rename from .txt to .gcode MainHeart.txt

heartpattern

vef445 commented 7 years ago

Yes I'm here :) As I replied on the other bug reported by @markingle , I'm not sure UI-related issues should pollute this Git, but I'll pass by regularly anyway.

For this specific issue, I will test and compare if the result is the same while the UI or command line and report on my finding.

vef445 commented 7 years ago

@MarkWheadon , you should look at your code, I've got the exact same result when using my UI or launching the process directly in command line. (I was concerned by the extra space generated by the UI when "image width" is not used/set). screen shot 2017-04-04 at 11 43 49 screen shot 2017-04-04 at 11 47 31

MarkWheadon commented 7 years ago

@markingle As an aside, you'll get better contrast if you modify that image to be pure black and white -- the red will be mapping onto a darkish grey rather than black, which means the hearts won't be mapping on to the high speed you specified.

markingle commented 7 years ago

Thanks @MarkWheadon !

MarkWheadon commented 7 years ago

I suspected as much. Will do.

On 4 April 2017 at 10:49, vef445 notifications@github.com wrote:

@MarkWheadon https://github.com/MarkWheadon , you should look at your code, I've got the exact same result when using my UI or launching the process directly in command line. (I was concerned by the extra space generated by the UI when "image width" is not used/set). [image: screen shot 2017-04-04 at 11 43 49] https://cloud.githubusercontent.com/assets/5900426/24651096/c45081f4-192c-11e7-88e9-44a8a79567b1.png [image: screen shot 2017-04-04 at 11 47 31] https://cloud.githubusercontent.com/assets/5900426/24651097/c489a0c4-192c-11e7-8bc6-e551023a80f6.png

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/MarkWheadon/velocity-painting/issues/15#issuecomment-291450444, or mute the thread https://github.com/notifications/unsubscribe-auth/AYZjUdqen8-DF0DkgqS_7xN8S_c4yxxYks5rshIygaJpZM4Mw2ao .

MarkWheadon commented 7 years ago

It's becuase you have the high and low values the wrong way round -- you need to swap them. That, and making the heart pattern pure black-and-white gets you this:

screenshot 2017-04-06 13 53 46

Black and white pattern is this: heartsmonochrome

There's still a little fuzz on some of the top edge if you look closely. I'm guessing that's something that's not at a constant speed -- you still have one of the slow-downs configured in your S3D settings somewhere?

MarkWheadon commented 7 years ago

Or, on reflection, it could be a bug to do with it not noticing the first vector of a layer under some circumstances. If there's nothing wrong with your slicer settings let me know and we may need to raise a separate issue.

markingle commented 7 years ago

@MarkWheadon Thanks for looking into this! I am using slic3r to generate the gcode and S3D to view/confirm the changes (Also learning S3D to switch from Slic3r at the same time). The high/low values were swapped to reduce the print time - 8hr to 5hr. Now that I know how the contrast relates to speed there is no need to swap. Thanks for creating a black/white for me. I plan on making another print this weekend and will post here. Really good work you have done! I hope you make a $1M dollars! :)

Is it possible the fuzz on top is from my retract settings in Slic3r? Just a thought...

MarkWheadon commented 7 years ago

Heh, so do I, but the Bucket Of Money fairy appears to be busy elsewhere.

Mark

On 6 Apr 2017 5:38 pm, "markingle" notifications@github.com wrote:

@MarkWheadon https://github.com/MarkWheadon Thanks for looking into this! I am using slic3r to generate the gcode and S3D to view/confirm the changes (Also learning S3D to switch from Slic3r at the same time). The high/low values were swapped to reduce the print time - 8hr to 5hr. Now that I know how the contrast relates to speed there is no need to swap. Thanks for creating a black/white for me. I plan on making another print this weekend and will post here. Really good work you have done! I hope you make a $1M dollars! :)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/MarkWheadon/velocity-painting/issues/15#issuecomment-292232212, or mute the thread https://github.com/notifications/unsubscribe-auth/AYZjUfoJ--rrC5aXIf_dHiY-Anc8_PMQks5rtRTygaJpZM4Mw2ao .