i took an alternative approach and used grey scales, layers and inkscape guides to get the positions
This is the first time i used guides in inkscape and it works like a dream
for some reason the center hole does not render in firefox not sure why, I doublechecked re-uploaded and again it’s not renderig in FF.
Guides and snap to center of an object to guides works very nice to touch up the details.
Over on G+ Skorch has mentioned some SVG weirdities he’s run into with his K40 M2Nano software. While not as bad as DXF/DWG files it’s not pothole free
K40 as in China Laser??
I have played with a china laser with LaserCut Software that also had lots of SVG weirdness
Yep. It’s called K40 Whisperer, uses the stock controller, no dongle required iirc, so it can coexist with LaserDRW and Corel.
Thanks for the Big Print file! When I printed it out and put it all together, my sled Diameter is exactly 17" across. But elsewhere (in this thread), it says the final sled is 18". Has anyone used this drawing? Did yours come out 17" or 18"?
17" is correct for the version this was generated from. You could check by comparing the chain bracket mounting holes. There’s no magic about sled diameter, though. A larger sled might be needed for one of the triangular linkages.
I’m not sure I have any definitive resolution to this issue.
First off, Inkscape is not opening the SVG files correctly for me as well. I suspect what’s going on is that Inkscape handles different units and scales incorrectly. I’ve had troubles in the past with exporting Inkscape create SVGs under non pixel units (mm, say) and having to hard code a rescaling factor because Inkscape refused to generate SVGs that had the proper units in them. Though I’m a little unclear as to what the underlying issue is, I notice some traffic with the “dpi” settings and other unit issues in Inkscape’s bug tracker, specifically bug #16700913 “… using mm as units and scale of 1 causes problems”, which has activity as recent as 2017-05.
Under Linux, I’ve had luck opening the SVG provided by the MaslowCNC Mechanics repo under a tool called karbon. Using karbon, I can open the MaslowCNC files fine, save as SVG and then open them in Inkscape. I’ve put the converted SVGs into my own repo:
| 6_Inch_Square_Test_Shape_u.svg |
| All_Parts_Laid_Out_u.svg |
| Arms_u.svg |
| BraceType1_u.svg |
| BraceType2_u.svg |
| BraceType3_u.svg |
| BrickHolder_u.svg |
| MotorMountingPlate_u.svg |
| Sled_u.svg |
| tempSled_u.svg |
I’ve confirmed that they can be viewed in the version of Inkscape that I have (0.91). If the MaslowCNC folks want me to push this to their main repo somewhere, I’d be happy to oblige.
I’m still confused about the discrepancy in the sled diameter. Looking at the SVG for the sled, the diameters is 18.02". Looking at the GCocde provided by in the MaslowCNC repo, the diameter is 17.1645", accounting for the routing bit diameter.
Looking at the Sled.svg, you can see the inner holes meant for the brick brackets have a diameter of 0.28", which I interpret as 0.25" with 0.03" headroom for the 0.25" bolt that is to go through.
I don’t know how they’re creating the GCode files and why there’s an approximate 0.84" difference between the SVG and the GCode files. Does anyone have insight into this?
I would love that! If you’ve got versions which fix the issue let’s use them!
I’m betting that this is a matter of the gcode being from an older version of the sled which was slightly smaller size. I think we should just not be providing gcode and only send out the .svg files. I’ve created a pull request to delete the old gcode files here
Pull request submitted here. I hope there aren’t any problems.
OK, thanks, that clears things up!
Thanks for the fix @abetusk !!! 
