Advanced Search

These are mathematical heresies

• Runs on Linux, perpetual license- want to encourage that!
• Speed seems good, both in general use and generating toolpaths (though have only tried small models)- again, very nice in a world full of (eg) node.js burn-your-cpu-to-render-1-fps nonsense.
• Not mysteriously 10 GB for reasons I can't comprehend!
• Adaptive toolpaths!!!
• Actually runs offline- Wireshark confirms that (only ran it for a few minutes, so hardly a conclusive test), manual is offline as well
• Supported 3Dconnexion mouse out of the box

• Defaults: G43 disabled, 3D mouse Z inverted
• Output includes "2026-09-30T20:03:01-0500 INFO frontend.licensing.gate: [LICENCE] active, licence_id=xxxxxxxx... updates until 2029-09-27", maybe just a placeholder ETA for when this major version will be done
• Payment tripped fraud alert, made 3-4 authorizations, though only one of them turned into a real charge
• UI/workflow is definitely different from FreeCAD and Fusion 360. It seems buggy to me (creating/deleting operations, notably), but I'm trying to withhold judgement until I've used it more.

• Adaptive ONLY appears to machine the inside of your part- if you want to rough the outside, too bad, I guess?
• Adaptive has no option to force specific depths- it has a stepdown setting, but will always do Z plane detection and cut any depth it finds one. Really breaks the high-DOC-low-WOC idea of adaptive in practice- especially since it cuts top-down, instead of cutting the bulk out from the bottom, then rest-machining the next layer up, and so on.
• Chamfer operation is real rough. Sometimes it works when you select a top or bottom face (to chamfer all edges of said face), sometimes it doesn't. Manually selecting edges kinda works, but the hit box for edges is tiny, and the closed loop detection seems to only sometimes work. You can't seem to de-select edges by clicking on them in the model, you need to find them in the list. Some edges it seems to entirely refuse to recognize.
• No option I can find for ramping into pockets- helix or plunge only. Problematic if you have a long, narrow pocket that you want to ease into, but no space for a helix. Literally the only time I accept a plunge entry is drilling.
• Lead-in/-out options are limited- you can pick a lead-in radius on some operations, but not others, and you can't add a slight overlap between the lead-in and -out points on closed contours
• Collision detection seems over-sold- eg, the chamfer operation will happily crash into a wall where the edge you're chamfering meets another face.
• I'm also not seeing a way to control where an operation starts or to add offsets to start/stop points to manually work around that. Looks like it only does collision detection for 3D operations

tuxcnc wrote:

"G93 is fine for me" means nothing.

 

Channel 1 → Turret 1 / Main spindle
Channel 2 → Turret 2 / Sub spindle
Channel 3 → Milling unit
Channel 4 → Additional machining unit
...

Channel 1:
X1 Z1 C1

Channel 2:
X2 Z2 C2

Transfer C1 →

Channel 2:
X2 Z2 C2 C1

• part transfer between main and sub spindle
• synchronized machining
• waiting for another turret
• synchronized spindle operations
• coordinated tool changes
• machining sequences involving several channels

• cylindrical surface machining
• face machining
• C-axis milling
• turning/milling combinations

• complete machine geometry
• tools
• workpiece
• fixtures
• spindles
• turrets
• axis movements

• tool and machine
• tool and chuck
• tool and fixture
• turret and spindle
• machine components
• workpiece and machine

• tool geometry
• tool offsets
• sister tools
• tool life monitoring
• remaining tool life
• automatic replacement with sister tools
• tool status
• tool usage tracking

• INDEX machines
• Gildemeister / DMG machines
• multi-spindle machines
• dual-turret lathes
• main/sub-spindle machines
• complex LinuxCNC configurations

grandixximo wrote:

Did you try

pipx install bcnc?
That should install it in its own env, and not conflict with qtDragon at all...

 

djdelorie wrote:

Having had my machine slow to a crawl because it applied "in/min" to "degrees" (usually by accident, I use G93 most of the time), I would like an option to "do better".  Some ideas:
* Use radians instead of degrees if you have to use them at all, since those are much closer to linear distance.
* Scale by the WCS Z coordinate to figure out "actual" circumference/distance
* Specify the machine location of the rotary in the config, like Y=10 Z=-3 (which implies it points along X) and calculate circumference based on that
* manually specify some scaling factor