Advanced Search

Good Afternoon,

I am in need of a 3 axis milling sample program. I am converting my Anilam Crusader M 3 axis mill to LinuxCNC. I use Gibbscam and in order to help me with the post processor they need a sample program that contains gcode that generate lines, circles, tool changes, etc. I sent them a link to the LinuxCNC G Code catalog. Any help is greatly appreciated.

Thank You,
Steve in Indy

I was thinking that 1:1.45 overdrive of the spindle could be an issue, but it just doesn't make sense that it would also misbehave without encoder feedback, when it's just an open loop system.

The motor is rated 5.5kW. It's on the slower side but the torque should be plenty I'd think. I've spent the last night rolling around thinking of this and I'm pretty sure it must be something to do with step scaling, accel values or something like that. Maybe there is too many steps? 10k per revolution and it's causing issues for unknown (to me) reason. I will try to test that next and see if that makes any difference.

Thank you, it was the analog line of the Z axis, it was switched around. Switching it and inverting the output scale from 60 to -60 did the trick.

Now I wonder how it worked in the first place. I think the GND of that connection must have been bad, and when I added the index lines, it got connected.

That's great news, glad you got it sorted out!

As I'm planning to do live coin minting at some events I attend, I will retrofit a proxon milling thing to make my own coin dies.
Model is this one:
forum.drucktipps3d.de/file-download/12960/
I'm in contact with a nice austrian guy, who has done that before LinuxCNC exists (uses some old DOS software via par port). So the mechanical part is quite proven.
Plan is as follows:
- replace all threads with ballscrews
- a mesa 7i96s (have that from a dead project)
- stepper motor and microstepper driver (from yet another dead project)
- maybe place a 1:6 gear between stepper and ballscrew (this is actually trick from the austrian guy) for higher detail
My main question is about the milling spindle. As I will mill little amounts of material, I was aiming for some small spindle (partially for lower weight to have faster and more precise movements). On the other hand it should have quite high rpm and very good concentricity.

So far I was thinking a AMB 530 FME. At least I couldn't find a lighter one that would serve the purpose.

Please let me know if my plan might generate a working machine or if I have a major f-put in my plan.

Just getting started with Flex; I've never really done a GUI from scratch so I haven't internalized any 'best practices' or anything.

Goal is something like below.  I started fiddling last night but quickly realized I needed some experienced advice on how to organize & lay-out this thing.

Details aren't set in stone now, but I want a GUI with no on-screen controls/jogging on the main page.  Will be used with 15.6" touchscreen 1920x1080p monitor - so I can't cram lots of small stuff in.

Maybe something like:

• Main window
  • Horizontal layout
    • Frame (variable displays top)
      • Vertical layout
        • Stacked widget (left)
        • Frame for stacked widget buttons (right)
    • Frame (fixed displays middle)
      • Vertical layout
        • Frames across for each 'section'
    • Frame (fixed indicators btm)
      • Vertical layout
        • indicators + estop/on btns

Or is there a better way of laying this out that doesn't wind up with me painting myself in to a corner?  I don't like tabs, so no tabbed widgets.

Thx
 

Make a new config and give it a try.
If that does not work:
-make sure the analog wires are properly making contact inside the connectors
-check if analog is correctly wired as reversing polarity of those two wires can cause most of the issues you have

all you need to do is type
sudo apt-get install linuxcnc-uspace linuxcnc-uspace-dev

This will get you 2.94 which is  a couple of bug fixes behind the current 2.98 version

If you want to get to 2.98 (which is probably not a big issue  for now), follow the directions here
linuxcnc.org/docs/stable/html/getting-st...th_preempt_rt_kernel

Laptops are not good candidates for linuxCNC because of all the latency inducing features in them but its worth trying. If you do need a better PC, go to 2.98 then. Install with the ISO on the downloads page
linuxcnc.org/downloads/

I have a few installation videos on my @MrRodW YouTube channel

Is there a way to create custom widgets without directly editing /usr/lib/python3/dist-packages/qtvcp/ items?

I'd prefer to store these custom widgets in user directory to track modifications easier.  Otherwise I have to edit as root.

I've tried and failed to pinpoint where the include directory is defined.

why not get a kit of closed loop steppers and use them with say a 7i97t in velocity mode. or use a 7i96s and add an encoder board later.
Then you might be able to get your scales going in position mode at your leisure and have a dual feedback system.
But I have a similar Seig SX3 and it may be overkill for what it is. A friend has an early Syil CNC machine which is based on a SX3.... open loop steppers and he does some really intricate stuff.
 

Okay i see so i dont get away with a cheap stepper driver like those from steppersonline.
I need one which has real closed loop capability. Like  leadshine el8  I mean this is a total different price class
I wonder if it makes sense on a cheap chines benchmill... Probably not my bad I bought the mill with the glass scales.

The leadshine el8 has this external encoder plug. This cheap chines glass scales have only VGA plug.

The question also would be if the glass scales provide the right signal via the cabel for the stepperdriver.

Has anybody have experience with that?

raggielyle1@gmail.com wrote:

Sorry about the delay. I cant upload the file because it has a sh extension. Please email me This email address is being protected from spambots. You need JavaScript enabled to view it. and I send the file.
 

just change it to end in .sh.txt

Thanks, I don't know how good a teacher I will be...
I'm almost there on my state_tag_arcs branch at github.com/rodw-au/linuxcnc

I've got all of the calculations tested and working in the interpreter. For some reason, data is getting lost on its way to motion. I will troubleshoot that in the next day or so.

Its been more complicated than I remember. I've got a better method of setting the tags but they are only updated at the beginning of a gcode segment but we want to get real time headings all the way around a G2/G3 arc. To do this, I needed to calculate the heading in real time (eg with the servo thread) in motion. No wonder no-one has tried to do this before!

 

Hello everyone,

I would like to announce the release of NativeCAM 2.0b — a community port 
of the original NativeCAM (by Fernand Veilleux) migrated to Python 3 and GTK3.

The original NativeCAM was written for Python 2.7 / GTK2, which is no longer 
available on modern distributions. This port makes it fully compatible with 
LinuxCNC 2.9 on Debian 13 Trixie.

--- What's new in 2.0b ---

* Full Python 3 / GTK3 migration
* New: Side Drill feature — horizontal drilling from Top / Bottom / Left / Right 
  faces of the workpiece, designed for multi-spindle machines like Biesse Rover
* New: Horizontal tool visualization in AXIS — tool rotates correctly in the 
  3D view when a side spindle is active (uses tool table Q column: 10-13)
* Fix: Phantom GTK popup windows no longer remain on screen after LinuxCNC exits
* Fix: About dialog now shows version correctly (Python 3 bytes decode bug)
* Fix: Validation Messages menu now uses checkboxes showing current state
* Debian packaging updated for modern build tools

--- Download ---

GitHub: github.com/cnc-proton/nativecam-py3-gtk3
Releases: github.com/cnc-proton/nativecam-py3-gtk3/releases

Install:
  sudo apt install ./nativecam_2.0b_all.deb

--- Tested on ---

* Debian 13 Trixie + LinuxCNC 2.9
* Biesse Rover 336 (multi-spindle, 4-side horizontal drilling)

Any feedback, bug reports or pull requests are welcome on GitHub.

Credits to Fernand Veilleux (FernV) for the original NativeCAM project.

Best regards,
CNC Proton

You are using DC. Confirmed.

All four slaves show "Distributed clocks: yes, 64 bit" and all four report 0x1C32:01 = 0x0002 which means DC Sync0. Your drives are running in DC synchronized mode right now. This is the best mode for a CNC machine.

The only thing that does not work for you is the alternative sync strategy where the master follows the reference slave clock instead of the other way around. But that is just a different way of keeping everyone in sync, not a better or worse one. What you have now, master as reference with refClockSyncCycles=1, is perfectly fine and is DC.

One thing I notice is that your reference clock, slave 0, is not one of the SD700 drives. It is a separate device, the first on the bus. That could be related to why syncToRefClock=true causes problems, if that device reports timing that my PLL does not handle well. If there is an opportunity to test this any time in the future within a better setting, I'd love to debug it remotely.