|
Post by bucksfolly on Dec 15, 2011 16:52:03 GMT -8
CamBam generates a tool listing in the header of the Gcode. Could Mach or MSM pick this up and use it in place of the user entering a separate library?
|
|
|
Post by DaveCVI on Dec 16, 2011 9:37:31 GMT -8
Hi, well.... it's software, so anything is possible.... but it's not part of mach today and it would not be trivial to add. To elaborate a bit: From a gcode viewpoint, I think the info Cambam generates are actually comments in the gcode file (the cambam info is enclosed in parenthses right?). Being comments they are ignored by mach when running the gcode (other than mach puts comments in the status line as the file runs). Thus mach has no knowledge of the contents of the comments (and should not have since they are comments). To do anything with the cambam comments contents, they would no longer be comments.... that would effectively be changing the definition of gcode to handle a special case of cambam comments. If I were the mach author I would not want to do that as it would be special handling code for cambam and then I'd have to worry about what happens if some other cam program made a comment that looked like a special cambam comment but was not etc... Re MSM parsing the cambam comments - I'd not want to do it in MSM as the screen set level does not know about gcode file contents. Teaching MSM to know about special cambam comments (that would really be instructions instead of comments) would be even messier in MSM than in Mach (and would require that MSM learn how to parse gcode independently from mach - which would be an ongoing maintenance headache for MSM). Even if one did do this, you would still only get a little bit of info to put in the mach tool table - maybe a tool description text and perhaps the nominal diameter (but not the wear diameter). None of the Toll Length Offset (TLO) info would be provided by Cambam as that is not cam generated info. My conclusion would be that the technical issues make this an undesirable exercise (from the Mach & MSM programmer viewpoint). Dave
|
|