Advanced Search

Search Results (Searched for: )

  • rodw
  • rodw's Avatar
Today 10:27
Replied by rodw on topic XHC WHB04B development?

XHC WHB04B development?

Category: General LinuxCNC Questions

I only have the wired versions of it (3 of them) and they are solid.

A hard wired pendant with no USB is only $30 to $50
  • MRx
  • MRx
Today 10:25
Replied by MRx on topic XHC WHB04B development?

XHC WHB04B development?

Category: General LinuxCNC Questions

I only have the wired versions of it (3 of them) and they are solid.
  • rodw
  • rodw's Avatar
Today 10:23

Technical questions about CIA402 and homecomp.comp on A6

Category: EtherCAT

I have an idea.
rodw: Can you make the bits from 0x6041 available as pins?
Then we can observe the bits during the home run.
If we know which bit is set when, the state machine could be set up accordingly.
 

Of course, that is supported. I wanted to do this with #if debug statements but it is not possible to insert such statements before the pins so I had to also include some comments to put them in or out.

Sorry but I am flat out on other projects right now!
  • rodw
  • rodw's Avatar
Today 10:14
Replied by rodw on topic XHC WHB04B development?

XHC WHB04B development?

Category: General LinuxCNC Questions

I'm going to operate it with a large CNC in the near future so I will see if it will hit me too.
 

I don't think I would trust a USB device under these circumstances. I would recommend you go back to XHC's website and look for a 433 MHz pendant that hard wires in to send/receive unit. After years  of use, these have never let me down 
  • mr_huxley
  • mr_huxley
Today 09:21

IndraDrive + LinuxCNC – PDO configuration problems

Category: EtherCAT

Following the procedure by Hakan on this topic to disable EoE: forum.linuxcnc.org/ethercat/58080-ver-2-...e-when-disabling-eoe
I was able to put it to work and I can finally jog it. Now I will continue with further configurations.
Also I wasn't aware of "sudo dmesg" but there is a lot of relevant information there.
  • Marcos DC
  • Marcos DC's Avatar
Today 05:13 - Today 05:17

PLC + LinuxCNC for industrial machine with simple HMI (non-G-code operators)

Category: General LinuxCNC Questions

File Attachment:

File Name: opcbridge_main.py
File Size:18 KB
Hi all, just to close the loop on this thread.
I ended up implementing a small Python bridge between a PLC/HMI (via OPC UA) and LinuxCNC, following the “PLC as cell controller, LinuxCNC as motion controller” approach discussed here (handshake, heartbeat, command/status boundary, etc.).
The script is vendor-agnostic (standard OPC UA) and already includes an MIT license header, so feel free to use, modify, or adapt it for your own setups.
If someone adapts it to Modbus TCP, MQTT, or another transport, feel free to share back.
Thanks to everyone for the input in this thread — it helped a lot to shape the final architecture.
— Marcos DC
  • tommylight
  • tommylight's Avatar
Yesterday 02:05

ayuda nesecito el prosedimiento para cargar paremetros HSD RTU 500 ( ROVER 22)

Category: General LinuxCNC Questions

E-mail removed from post above to protect from spam, you can post it again only if the OP requests it, and remove it as soon as you get confirmation from him.
  • Rover20biesse
  • Rover20biesse
Yesterday 01:52 - Yesterday 02:03

ayuda nesecito el prosedimiento para cargar paremetros HSD RTU 500 ( ROVER 22)

Category: General LinuxCNC Questions

Conseguiu o procedimento?
Eu posso te ajudar, entre em contato e-mail removed
  • tommylight
  • tommylight's Avatar
Yesterday 00:52
Replied by tommylight on topic How to build LinuxCNC on OpenBSD?

How to build LinuxCNC on OpenBSD?

Category: Off Topic and Test Posts

Do not make me regret this.
  • Marcos DC
  • Marcos DC's Avatar
Yesterday 00:45

Technical questions about CIA402 and homecomp.comp on A6

Category: EtherCAT

From what I understand, the immediate goal here is to get the A6 working reliably, and for that it makes a lot of sense to tailor the logic to what this specific drive exposes in 0x6040/0x6041. In that context, taking an SCL-style example and adapting it is a very pragmatic approach.

I also agree that the resync problem itself is exactly what homecomp is trying to solve. During internal CiA-402 homing the drive moves on its own, so LinuxCNC needs a way to keep pos_cmd in sync with pos_fb or to resynchronize cleanly afterwards to avoid the jump / E87.1. So the mechanism for handling this is already there.

Where I think we just need to be a bit careful (based on the docs and on what’s described in this thread) is mainly in the integration details:

1) The actual semantics of the homing bits.
Yes, 0x6040/0x6041 are standardized for the basic FSA, but in practice the homing-related bits are OMS / manufacturer-specific. Bosch uses 10/12/13 in a very clean and well-documented way, but Lichuan, for example, documents “origin found” on bit 15 and leaves 12/13 as “mode specific”. So for the A6, it probably makes sense to first confirm which bits really indicate “in progress / done / error” and then wire exactly those into homecomp.

2) When exactly the resync should happen.
homecomp provides the mechanism, but it still depends on being told when homing is active, when it is finished, and when it failed. If those signals come from bits that don’t quite match the drive’s real behavior, the resync may simply happen at the wrong time. So the key part here is just making sure the drive-specific semantics are mapped correctly.

3) Details like how “start homing” is triggered (pulse vs level, required preconditions, etc.) also tend to be drive-specific and are probably best verified on the A6 itself.

So I think we’re actually pretty close in approach: for the A6, observing the bits during a home run and adapting the logic accordingly sounds like the right next step. My only point is that the state machine itself is the easy part — the main work is just confirming the drive’s real homing semantics and hooking those cleanly into homecomp so everything stays consistent.
  • landoneilers
  • landoneilers
Yesterday 00:30
Replied by landoneilers on topic Was the forum down 2-3-2026

Was the forum down 2-3-2026

Category: Off Topic and Test Posts

Did you try accessing it directly via its IP address?

Sometimes that works (but why?).

(Use bgp.he.net to find the IP address of any non-Cloudflared site)
  • Lcvette
  • Lcvette's Avatar
Yesterday 00:27

Probe Basic Tool Setter touch off pos Y not set

Category: QtPyVCP

glad you got it sorted out!
  • landoneilers
  • landoneilers
Yesterday 00:27
How to build LinuxCNC on OpenBSD? was created by landoneilers

How to build LinuxCNC on OpenBSD?

Category: Off Topic and Test Posts

I have grown to like OpenBSD with its well thought through update commands and all.

Additionally, the absurdly high security makes using an outdated system less of an issue.

OpenBSD also comes with 3 (admittedly highly primitive) GUI options, which is a plus.

I managed to get the ./configure script to run with the attached script.

Due to a lack of the
pidof
command on OpenBSD, I got AI to make a script to emulate it using 
pgrep
(see attached file for details).

However, there are currently 4 issues:
1. Lack of tclx package (ostensibly a runtime dependency of LinuxCNC) on OpenBSD for some reason.
2. Lack of a libmodbus package on OpenBSD for some reason (functionality likely is reduced).
3.
make
refuses to work.
4. No idea about realtime on OpenBSD.

BTW:
On OpenBSD,
/bin/sh
=
KSH
  • ihavenofish
  • ihavenofish
Yesterday 00:26
Replied by ihavenofish on topic Mini wannabe datron build

Mini wannabe datron build

Category: CNC Machines

www.minimonster.ca

Tarts for allll!!! :P

It's been an entertaining and frustrating journey to get to finally be able to sell these machines. Thanks to everyone that helped me with all my linuxCNC needs.
  • Hakan
  • Hakan
Yesterday 23:39 - Today 10:10
Replied by Hakan on topic XHC WHB04B development?

XHC WHB04B development?

Category: General LinuxCNC Questions

Thought a bit about this with disconnects/reconnects.
It is actually normal behavior and the component is designed to work with that.
In run(), that is the main loop, github.com/LinuxCNC/linuxcnc/blob/ffc393.../xhc-whb04b6.cc#L414
There is a loop that opens the device, processes and teardown usb, repeatedly.

The stop in setupAsyncTransfer() should not be fatal. The assert() statement makes it fatal.
I now remember my original issue I opened two? years ago, it was to remove assert() statements,
because I at that time found that the code does the right thing, in principle. Just that the asserts() 
should be removed.

The call to setupAsyncTransfer tries to see if the usb device is connected with the mIsRunning flag,
but if I understand right (not necessarily) things change sometimes before libusb_submit_transfer().
github.com/LinuxCNC/linuxcnc/blob/ffc393...whb04b-6/usb.cc#L539
github.com/LinuxCNC/linuxcnc/blob/ffc393...whb04b-6/usb.cc#L456

I think now that the right thing to do is to have a failed libusb_submit_transfer() not crash the component through an assert() call
Instead finds it way in the call stack back to ::run() where the usb comm is torn down and the device is reconnected
and everything can continue.



 
Displaying 1 - 15 out of 19124 results.
Time to create page: 0.205 seconds
Powered by Kunena Forum