OK, so I DID create some chips, but only in Foam and only with “Pen” CAM code generated from ESTLCam, just run with my spindle instead.
I’m running into several issues, but I think a few questions might get me on the correct path.
- @Ryan: should I increase the length on my 4-corner leg tubes? They seem rather shorter than I would expect--Instructions say 3-4" usable height, and corner pipes should be that - 0.5", my corners at most 2"! I presume you did that to make it easier to pack for trips--if so, where did you get the stainless steel tube, as I'd like to get the same?
- @Ryan, I presume I should go ahead and update the Marlin in my board, as it was programmed before 3/31/2019, and it looks like you did an update on 4/27. Do you agree?
- When, if ever do you use the Custom Command, Reset All coordinates? I've been using that to set my "Part Coordinate" X0, Y0, Z0, and I'm wondering if that is wrong.
- Is it safe to upgrade CNC.js and Octoprint versions from that included in the base V1Pi image? I know both have been updated and for some reason, CNC.js keeps crashing on my Pi. Perhaps I should just go get 0.16.0? @Jeffeb3 ?
- I'm using Fusion 360 to do my CAM generation (Yes, I know most of you are likely using ESTLCam, but as I do all my design work in Fusion, I'd really like to do my CAM generation there--I'm using the Post processor linked from the bottom of Milling Basics: https://www.v1engineering.com/forum/forumz/mostly-printed-cnc-mpcnc/getting-started/ . Assume this for all remaining questions. Also, for those who aren't @Ryan, I'm using the Dual-end stop machine.
- I'm not setup for a Z-probe (in Hardware), but I'm thinking I should be as it appears in the demo for the Dual-end Stop firmware, and my CAM generation seems to expect it. Is that correct?
- None of the gcode commands seem to pop-up any prompting messages on the display to indicate z-probe connect/disconnect or Tool change messages--do you just have to have all that memorized so that you know when to do what?
- My machine seems to want to drive the Z-axis through the bottom of the board at the start of my program--I've tried to examine the g-code by hand to see if I can understand why, but I haven't found a cause yet--are there any "common mistakes" that Noobs make that causes such behavior (I'm using a DW660) spindle. (Maybe my short corner legs??)
- Are there any full video walk throughs of taking a simple part in F360, generating the Gcode and then actually taking it to the MPCNC, placing stock, ALL the button presses and the screen display? I've been trying to JUST use the text display and knob and without prompts or some other clues, I don't seem to get my coordinates setup correctly.
I think that’s enough for a first post in this thread ;-).