Advanced Search

I have a sim config for a b-axis head / c axis table in my suite of twp-configs on my github site:
github.com/Sigma1912/LinuxCNC_Demo_Configs/tree/main

 

to test this you need to:

1. download and unpack the folder 'LinuxCNC_Demo_Configs-main'
2. from the unpacked folder copy the folder '5axis-twp' and paste it into your 'configs/sim' folder
3. right click->Properties->mark as executable the following files (otherwise you get the permission error you got):
- '5axis-twp/twp-helper-comp.py'
- '5axis-twp/vismach/xyzbc-trsr-gui.py'
 

 
 
 
 

I tried to figure out if I see something with pyOCD but I don't understand if I'm using jlink/stlink or links wrong....

Dear Community,

I’m excited to share io-samurai, an open-source, budget-friendly interface for LinuxCNC and remote I/O projects, built from the ground up for makers like you! I’ve been working hard on this project, and I’m thrilled to announce that once the first batch of final PCBs arrives and I’ve thoroughly tested them, I’ll be releasing the full project on GitHub under the MIT License. Here’s a sneak peek at what’s coming:
What is io-samurai?
io-samurai is a versatile platform for CNC control and remote I/O, powered by Raspberry Pi Pico/Pico 2 and W5100S/W5500-Lite Ethernet modules. Key features:

    16 inputs (20–50 V, MCP23017, I2C) with Zener protection.
    8 high-current outputs (50 V, 500 mA, TD62783-driven, MCP23008-controlled).
    Single analog inputs (10 kΩ potentiometer, 0–3.3 V, GP26).
    40 MHz SPI (~6000 Hz burst) for fast Ethernet communication.
    Optional SH1106 OLED for I/O status and IP display.
    LinuxCNC uspace HAL driver (compiled with halcompile, .so), with safety features like timeout and data checks.
    Python library for automation and remote I/O.

It’s perfect for LinuxCNC users, but also great for IoT, home automation, or any project where you want to experiment with hardware and software.
Current Status
I’ve invested $268 into prototyping, and the first five final PCBs are on their way (~$40–50 each). Once the PCBs arrive and pass testing, I’ll publish the project on GitHub, including:

    Firmware: Pico/Pico 2 code with Wiznet’s ioLibrary_Driver (MIT licensed).
    HAL Driver: Uspace .so for LinuxCNC, with full setup guide.
    Hardware: Gerber files for PCB manufacturing (e.g., JLCPCB, PCBWay).
    Documentation: Detailed pinout.md, setup-guide.md, and io-samurai-manual.pdf.
    Python Library: For remote I/O and automation.

The GitHub repo (github.com/atrex66/io-samurai) is ready to go live under the MIT License, ensuring everyone can use, modify, and contribute to the project.
Get Involved!
I’m passionate about making io-samurai accessible to the LinuxCNC and maker communities. Here’s how you can join the journey:

    GitHub: Follow the repo for the upcoming release (github.com/atrex66/io-samurai).
    X: Follow updates and share your thoughts: @aTrEx77.

What’s Next?

    PCB Testing: Validate the final boards with W5500-Lite, MCP23017, MCP23008, and 10 kΩ potentiometer.
    GitHub Release: Share all code, docs, and Gerber files under MIT License.
    Roadmap: Mach3 driver, FPGA-based step generator, (~$150 full CNC or HMI control with display and pi Zero 2W).

I’d love to hear your feedback or ideas for io-samurai in LinuxCNC setups! What features would you like to see? Let’s build something awesome together. Built with ❤️ in Hungary.

Cheers,
Zsolt Viola

Patreon: Support development for early firmware access, technical posts, or consultations ($5–$30/month)
Patreon link ( #)
 

Thanks for taking the interest.

Just realized that T1 at 0.000 is sensible.
It is the datum point against which the other tool offset heights are measured.
My previous post used the wrong terminology, not 'cutting length' but 'tip offset'.

I have an edge finder permanently mounted in a NT30 chuck.
I could set all my tool height offsets reference that.
Could be an ideal time to start using my table mounted tool height setter.

I never tripped over this in years of Axis use.
Always just touched-off the actual tool when it was mounted, never used the tool table.
When the mill is next in use, I will check how Axis handles this.

Hi Aciera,

thank for the input. Today I started to configure vismach, when i realized that my TCP moves seem off by quite a bit. Which leads me to the following questions:

With the Mazak Z axis is lying horizontal and X standing vertically. -> So i switched X and Z in my vismach model and everything's fine. But in TCP i realized that if i switch between normal and TCP my Z axis was moving left and right. Which had to do with the X/Y offsets for TCP. Witch made me lead to the conclusion, that in the TCP calculation the tool-offset need to be applied to X and not Z. Which than begs the question if the formulas for X and Z need to be switched completely.

So i started doubting everything and searched the forum. I found your XYZBC-TNR example which sadly i can't run right now because of some permission problems:

But I'm still not quite sold if i can copy the the TCP math from this example. With the Mazak the head is swiveling around Y (B-axis) in your example it's a dual table config.

I would be real glad if you could give me some input on:

- 5 - axis Kinematic with swiveling B axis head
- The X and Z axis switch debacle
 

Hi,

Using the linuxcnc iso & ethercat my jog speed is max 5000 mm/min. and apptime 50000.
This is tested on a laptop. Very bad performance.

I used to have apptime 15000 and jog speed around 19000 mm/min using a desktop pc.
 

It's the same screen. Jim's original name was silverdragon. When I incorporated it into linuxcnc, I renamed it in the code. We just got used to calling it qtdragon so in 2.9 I went with it.

Jim also has a newer version in github.

notJamesLee wrote:

Friends,

from what I can only assume is inconsistencies in diameter or something but 533.33 is the number.

with 533 after 20+ revolutions you can see the starting point creep earlier -- indicating its just short of the number of steps to complete a full circle.

with 534 after 20+ it goes the opposite way.

I have a few follow up questions:

- what should i have the dip switches set to? Now that we've figured out they don't do anything to effect the steps per revolution is there an optimal value for this? I dont need insane amounts of torque or rpms

- is this something i can easily fix with the encoder once i do move to LCNC and tune in the encoder error?

thanks all for sanity checking me thus far, nice to know im not 100% crazy.

Sounds like you're still struggling with the driver, yes?

Maybe I missed it, but what brand/model driver do you have?  Asking because some drivers can be tuned via software (in addition to dip switches), and there may be a setting (or another dip) that disables the external dip switches.

No need to apologize, war is hell.

If I see it correctly it has a LPT port?
There are different version I see now. So it has 7 input pins (GPI) and 7 output pins (GPO).
With a XYZ machine you'll have just enough output pins to control the steppers, but like PCW said you'll need to create a driver for it.
If you could still return it, the one with a LPT port might be a better choice. If you want to be more sure that it will work reliable with a fast rate a hardware controller will be a better choice.

Fair enough. Perhaps when it’s ready for prime time, we can work through the other issues to come up with a cohesive solution and find a way to push the project as a whole forward.

I prefer to be positively realistic

Keep up the nice work!

Yes you should switch. At least try it.

yes but they are not answering

Control cabinet almost finished. I just need to install 20 push buttons and connect them to the usb matrix board. I will mount a new keyboard with a trackball also.

theslawek wrote:

1. Should I expect M5 to stop all spindles, or do I have to get used to using M5 $-1?
   • Is it possible to get M4 to work? It doesn't do anything right now.

M5 - I recall some discussion on Github about what should be the default behavior for multi-spindle M5 commands.  I found a commit that appears to change M5 to 'stop all spindles', and any of the $ modifiers are for individual spindles.
github.com/LinuxCNC/linuxcnc/commit/01a0...d65486193ead51027c29

Probably want to do some testing yourself.

M4: I think what's going on is that step/dir spindles require an explicit reverse speed value in the INI file, despite what the manual indicates.
linuxcnc.org/docs/devel/html/config/ini-...:ini:sec:spindle-num

adding
[SPINDLE_1]
MAX_REVERSE_VELOCITY = 550

Might do the trick.

If this doesn't work, the next thing is for you to get used to using the 'halshow' feature in LCNC.  This is a simple but powerful tool for debugging since it lets you see what LCNC is doing behind the scenes.  In your case, you want to know why M4 isn't working so you should display all the HAL pins which affect the spindle - including the PID pins.

When you open halshow there's a folder tree on the left where you can click on all the pins (real physical pins, or logical pins) in LCNC.  Once you select those they will appear on the right in the 'watchlist'.  On/off (bit) pins will look sort of like red/yellow LED's, and other pin types will display the value.
What you want is to display all the pins which form the internal logic chain that starts with and M4 command and ends with the mesa stepgen outputting signals to the drive.  Figuring out all the pins and how they're logically interconnected is not always straightforward... but it also didn't cost you buckets of money.

This is where coming to terms with HAL is necessary:

All this stuff like this below still makes no sense to me as to what its purpose is.
net spindle1-vel-cmd-rps        <=  spindle.1.speed-out-rps

'spindle.1.speed-out-rps' is a logical (not physical) pin inside LCNC.  When LCNC starts up and reads the HAL file, there are a number of default functions that are automatically loaded. One of these functions is called 'motion.comp', and a description of what it does and all the related pins which are created is located here:
linuxcnc.org/docs/devel/html/man/man9/motion.9.html

If you read through that page, what you find is a list of logical pins which are created when LCNC starts.  Once those pins are created, you can do 'stuff' with them by connecting them together.  I won't go in to specifics right this minute, but any pin which is connected to spindle.1.speed-out-rps will receive a value that is equal to the commanded rotary-axis spindle speed in revolutions per second.

Hopefully this will click with you soon.

BUT

Assuming you didn't mess things up significantly during your editing, I think there may (still) be at least one bug in Mesact or PNCconf for step/dir spindles.

See where spindle.1.on is connected to hm2_7i76e.0.stepgen.04.enable through signal spindle1-enable?

This connection will result in the stepgen shutting off instantly when the spindle is turned off - no controlled deceleration.  This result in a massive BANG! when the motor drive stops dead, and can lead to over-voltage trips in the drive or broken things.

This should have been fixed in LCNC 2.9, but it appears to still be an issue:
github.com/LinuxCNC/linuxcnc/issues/2748

This bug shouldn't affect M4/reverse not working, but I bet your spindle stops HARD right now and doesn't decel gracefully.