If OpenSCAD supports user defined attributes on a face-by-face basis, one can
> Well there you go then, the concept will work (my para 3).
> It will not detect an over deep rough cut that misses the finished surfaces, and
> that may be a problem too - loading everything up from the cutter to the workpiece.
>
> But that leads me on to think - by modelling each cut step and calculating it's
> volume...hmm, would need to difference the tool with a 'work so far' model at
> any instant to check for too much plunge or just slamming sideways into the piece.
>
> Could be done.
>
> You would also probably want to do a minowski on the 'designed' STL to reduce it
> a skim. THis would prevent arithmetic errors causing tiddly bits of intersection
> and make the go/nogo result clear.
>
> On 03/02/2015 16:52, Stuart Stevenson wrote:
>>
>>
>> On Tue, Feb 3, 2015 at 10:46 AM, Richard Benjamin <
[hidden email]
>> <mailto:
[hidden email]>> wrote:
>>
>> I can see the value of the cut by cut approach.
>>
>> If you did the whole lot in one batch, then cmpare the result STL to the
>> designed STL, eg by differencing, you will get to see gouges and uncut
>> areas, but not where in the program it occured.
>>
>> If you create each program step cut as an additive operation then
>> intersect that with the designed STL, you will see over/deep/gouge cuts,
>> or nothing, at each step.
>>
>> You probably don't need to see cuts that don't touch the finished part as
>> they will be lots of roughing etc.
>>
>> Many times the miss cut event is a roughing cut that is incorrect. You are not
>> able to see it until the finish passes and you must examine the finish passes
>> in detail to determine the problem is not in the finish passes. You can always
>> find the problem but it can be easier and quicker with certain techniques.
>> It is a time, frustration issue. :)
>>
>>
>> On 03/02/2015 15:27, stustev wrote:
>>>
>>>
>>> On Tue, Feb 3, 2015 at 9:06 AM, kintel [via OpenSCAD] <[hidden email]
>>> <
http:///user/SendEmail.jtp?type=node&node=11392&i=0>> wrote:
>>>
>>> On Feb 3, 2015, at 08:12 AM, Stuart Stevenson <[hidden email]
>>> <
http:///user/SendEmail.jtp?type=node&node=11389&i=0>> wrote:
>>> >
>>> > […]
>>>
>>> > Open OpenSCAD
>>> > Run the Perl output line in OpenSCAD
>>> > […]
>>> > Save the resulting model and close OpenSCAD
>>>
>>> Instead of doing this, I would simply generate an OpenSCAD script
>>> directly from Perl, and _in the end_, open the entire script in
>>> OpenSCAD to get the the final geometry calculated. That way, the
>>> perl script will be simpler and decoupled from OpenSCAD itself.
>>> This way you could also experiment with other engines in addition to
>>> OpenSCAD by simple changing your output (e.g. Netfabb, Blender, the
>>> various openjscad-like tools etc.).
>>>
>>> -Marius
>>>
>>> I agree this should be an option.
>>> I like the idea of line by line. That allows finding exactly which line
>>> of code makes which cut. Sometimes, it is clear by just looking but other
>>> times it is not clear which line of code did exactly what. If there is a
>>> way to highlight the cut surfaces/sections and see which line of code cut
>>> it then preprocessing the entire CAM program would be just fine.
>>>
>>> Being able to process the entire CAM program will surely be early in the
>>> cycle.
>>>
>>>
>>>
>>> _______________________________________________
>>> OpenSCAD mailing list
>>> [hidden email] <
http:///user/SendEmail.jtp?type=node&node=11389&i=1>
>>>
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org>>>
>>>
>>> --------------------------------------------------------------------------------
>>> If you reply to this email, your message will be added to the
>>> discussion below:
>>>
http://forum.openscad.org/nc-code-verification-tp11373p11389.html>>> To unsubscribe from nc code verification, click here.
>>> NAML
>>> <
http://forum.openscad.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Addressee is the intended audience.
>>> If you are not the addressee then my consent is not given for you to read
>>> this email furthermore it is my wish you would close this without saving
>>> or reading, and cease and desist from saving or opening my private
>>> correspondence.
>>> Thank you for honoring my wish.
>>>
>>>
>>> --------------------------------------------------------------------------------
>>> View this message in context: Re: nc code verification
>>> <
http://forum.openscad.org/nc-code-verification-tp11373p11392.html>
>>> Sent from the OpenSCAD mailing list archive <
http://forum.openscad.org/>
>>> at Nabble.com.
>>>
>>>
>>> _______________________________________________
>>> OpenSCAD mailing list
>>>
[hidden email] <mailto:
[hidden email]>
>>>
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org>>
>>
>> _______________________________________________
>> OpenSCAD mailing list
>>
[hidden email] <mailto:
[hidden email]>
>>
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org>>
>>
>>
>>
>> --
>> Addressee is the intended audience.
>> If you are not the addressee then my consent is not given for you to read this
>> email furthermore it is my wish you would close this without saving or
>> reading, and cease and desist from saving or opening my private correspondence.
>> Thank you for honoring my wish.
>>
>>
>>
>> _______________________________________________
>> OpenSCAD mailing list
>>
[hidden email]
>>
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org>
>
>
> _______________________________________________
> OpenSCAD mailing list
>
[hidden email]
>
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
Locked
