Advanced Search

Tebrikler.

Since you asked me to show my work, I'm developing my own CNC controller using C, Ubuntu Linux with real-time capabilities, and EtherCAT.You can find more about my software development work at https://www.fahriworks.com.I'll share more technical details about the CNC project as development progresses.Wishing everyone the best with their projects!

Thanks for your suggestions! I'll look into your recommendations.(FlexGUI and QtPyVCP.)

However, I'm developing my own CNC controller from scratch rather than using LinuxCNC. The real-time control core is written in C, and I'm integrating EtherCAT for servo communication.

I'm mainly trying to decide on the best HMI architecture for my own system: a native C/C++ GUI or a modern React-based web interface communicating with the C control core through a separate backend.

I'd be interested in your thoughts on this architecture, particularly regarding reliability, real-time performance, and communication between the HMI and the control core.

How do i buy this card an how much does it cost?
yurtaev.com/yssc3p.html

Thank you. It turned out that my internet provider was having problems accessing your website. The provider has already resolved the issue. Access to your site has been restored.

It is working, but there are issues for sure, probably due to panic caused by some news yesterday and may server getting shut down completely.
Both our servers are working, but i could not access the forum from yesterday afternoon till today morning, but i could access the website just fine.
In the meantime, use a free proxy located in USA, it will work fine for browsing etc, but i would not use it to login anywhere.

Hello,I can open the forum (forum.linuxcnc.org) without any problems from my home computer, but the main website linuxcnc.org does not load at all (even when using a VPN). From mobile data the main site works fine.It looks like my home IP might be blocked on the main site. Is this possible? What could be the reason, and what is the recommended way to resolve such an issue?Thank you.

This looks a lot like a wiring issue, at an educated guess, one of the Mesa outputs to Y2 is tied to 5V.

Selling Mesa 7i76 and 7i92, good condition.
www.ebay.com/itm/327407051979

Hi all,

a quick update from the multichannel LinuxCNC project I posted about earlier (looking for testers with real machines). Everything now lives on our new site: www.cnc.gmbh

What you'll find there:

Try it online – a live test environment where you can run the multichannel system in your browser, load programs for several channels and see how the synchronisation (wait marks, channel coordination, Sinumerik-style syntax) behaves, no install needed.

Download - the current .deb packages for Debian [12/13] (amd64, [arm64]) plus the full source code. Build instructions are included.

Config generation offer, since the most common question is "how do I get my machine running with it", we're offering, for a limited time, to generate the complete LinuxCNC configuration (INI/HAL, channels, axes, spindles, I/O) for your retrofit, works for existing LinuxCNC setups you want to migrate as well as brand-new retrofits. Send us your machine data and drive/IO hardware via the form on the site, and you get a ready-to-run multichannel config.

Feedback, bug reports and especially reports from real machines are very welcome, either here in this thread or via the site.

Thanks,
Daniel

Right now I don't think there is any form of "active" spindle. There is the primary spindle which responds to commands with no spindle designation or $0 commands. And all spindle commands intended for spindles other than the primary one must be appended with with $n, where n=the spindle's designation number.

Before the addition of multiple spindle support, one of the main work arounds was to create custom M-codes to designate "active" spindles that would then receive the standard spindle commands. But that isn't how the current multi-spindle support works. In some ways I think that is almost a better way to make it work. And It still can be done this way, but it does make for a much more complicated hal configuration.

One way to debug this might be to do a halscope plot of the homing sequence.
That is, plot the home switch states and Y +Y1 motion during a home 
move.

Hi HansU,

I'm not sure the files are the issue since nothing has changed since the panel last functioned properly. However, I've attached both files.

Thanks for working with me.

Kind Regards,

Hi PCW;

I reinstalled the boards and then verified with halshow that all of the field input switches were functioning correctly. With the spindle located in the middle of the table I started the homing sequence. Z and X both homed properly, however, when Y started the homing process a, "joint.1 failed to unhome" message was presented 3 times then joint.1 began to home while joint2. failed to move.

The machine is configured with both the Y and the Y2 axes (joint.1 and joint.2) set up with "both limits and home" switches using a single input for each axis. Thus, neither axis home switch was triggered yet LINUXCNC could not logically unhome one of the two axes.

What is the next step to resolve this issue?

Kind Regards,

Good to know. Thank you very much for taking the time to respond.