Hey guys, I'n not new to CNC but certainly new to the Workbee with Blackbox. I'm still getting used to the system, but I'm finding that the system stalls when negotiating tight radii or curves and programmed straight out of Vectrix. The X and Y stall so badly they barely move. I bought this machine ot produce guitar bridges with and if this cannot be resolved, this would be a total waste. Please help!
Tried two laptops 1 - Apple Macbook Pro - 2017 not sure of the rest 2 - Dell Precision i7 16GB Ram Windows 10 Pro $0=10 ; Step pulse time, microseconds $1=255 ; Step idle delay, milliseconds $2=6 ; Step pulse invert, mask $3=5 ; Step direction invert, mask $4=1 ; Invert step enable pin, boolean $5=0 ; Invert limit pins, boolean $6=0 ; Invert probe pin, boolean $10=1 ; Status report options, mask $11=0.020 ; Junction deviation, millimeters $12=0.002 ; Arc tolerance, millimeters $13=0 ; Report in inches, boolean $20=0 ; Soft limits enable, boolean $21=1 ; Hard limits enable, boolean $22=1 ; Homing cycle enable, boolean $23=1 ; Homing direction invert, mask $24=100.000 ; Homing locate feed rate, mm/min $25=1000.000 ; Homing search seek rate, mm/min $26=250 ; Homing switch debounce delay, milliseconds $27=5.000 ; Homing switch pull-off distance, millimeters $30=12000 ; Maximum spindle speed, RPM $31=3000 ; Minimum spindle speed, RPM $32=0 ; Laser-mode enable, boolean $100=200.100 ; X-axis steps per millimeter $101=199.810 ; Y-axis steps per millimeter $102=200.830 ; Z-axis steps per millimeter $110=2500.000 ; X-axis maximum rate, mm/min $111=2500.000 ; Y-axis maximum rate, mm/min $112=2500.000 ; Z-axis maximum rate, mm/min $120=150.000 ; X-axis acceleration, mm/sec^2 $121=150.000 ; Y-axis acceleration, mm/sec^2 $122=150.000 ; Z-axis acceleration, mm/sec^2 $130=510.000 ; X-axis maximum travel, millimeters $131=620.000 ; Y-axis maximum travel, millimeters $132=75.000 ; Z-axis maximum travel, millimeters
Hi, tried this but no difference. I ran the same program on my commercial router with no slowing at all. Surprisingly it only occurs in the areas shown below. Must be off now as it is late in Australia. Any other suggestions for tomorrow?
Very short G1 sections (from the color red) - can you set your CAM to do those curves as G2/3s? Or at least set the minimum line segment length a little longer if it has to do polylines there
Hi Peter, tried saving dxf using polylines instead of splines and cured the problem. Does not make a whole lot of sense, but it worked and can now complete profile with no feedrate loss. Thanks for your help. I would still like to understand this better as it is quite limiting but for now it works! Cheers
Modelling = Solidworks 2020 CAM = VCarve Desktop (Current Version) PP to Openbuilds default. I've tried numoeroud other PP's but still the same effect. Control = Openbuilds I've uploaded the original DXF as exported as well as the GCode files. Both were created in exactly the same way but for the polyline / spline difference. I have not been using VCarve for long but there does not appear to be much control over how to treeat vestors / splines etc. Hope this helps as I would really like to understand the phenomena.
Even the filesize is already a good clue Gcode = 7kb for the Polyline, 152Kb for the Spline version. So - may have to ask Vectric Support to look into this one - see why their toolpathing creates such very short segments What's happening is when you break it into polylines - its it actually split that section into approximate Arcs (not really full polylines - where each arc would also be split down into segments) - but nice, since it is Arcs, their CAM could just spit out perfect G2/3s: ARC in = ARC out. With Splines - Vectric basically has to convert it into a bunch of short segments - as by nature most bezier curves/splines do not have a constant radius. Because the input is not an Arc, it explains why the output cannot be Arcs. The only odd behaviour is the length of segment Vectric creates for itself to work from - it Code: G1X40.722Y-15.615 G1X40.721Y-15.615 G1X40.719Y-15.617 Just an extract, those three moves each only move 0.001-0.002mm each - you could probably go down to 0.1mm minimum moves and still not notice that on the actual cut. With such crazy short lines, the Grbl planner cannot stay full, thus starving for moves, decelerates, and each move is so tiny you cannot see it, it just feels stalled. So for now, Polylines it will have to be
