Advanced Search

Attached is the "test driver" I made, which repeatedly polls the pendant and displays the data received. It can also update the display if you uncomment the last line in usb_interrupt_callback(). Just unzip the file into a folder and running from the terminal you should get something like:You need to have libusb-1.0-0-dev installed for this to compile it. But if you already compiled LinuxCNC from source, I think you should already have it.

And regarding repeated disconnects... It may be normal behavior in as far as that is what happens. But it is for sure not correct behavior.

I would also prefer a wired pendant over this wireless one. But when I bought it this seemed like the best option for me for a relatively low cost. And I do not think that the issues we see are caused by the RF link failing.

I'm using the hardwired version for years without any problems - no disconnects.
Can you open your pendant and take some photos of the PCBs so I can compare it with mine?

To clear an "amplifier fault" (drive error) I can do it using the halshow and then via cia402.0.fault-reset but I read somewhere that the fault should also be cleareable when clicking the enable/power on button. It works but only sometimes if I keep pressing the button it will clear the error and the time after that allow to power on. Should the enable button clear the error reliably? Maybe there is something wrong with my setup. Probably latency issues as I'm using a RPI4...

Also, with ethercat there is no way to use the UI emergency button, correct?

You're missing a G40. 

First run the installdeps script.

Then run:
This all works fine.

However, when I try to run gmake or remake (which is apparently just gmake with better debug output), it fails with an error partway.

Does anyone know why?

Does anyone know how to fix it and get it to compile?

Hello,
i need some buttons in Probe basic which activates outputs from my Mesa 7i76e. The attached photo show what i need. 
I found /user_buttons/template_user_buttons/template_user_buttons.ui (attached). Would that a nice place add the buttons. But so far i don´t know how to start the ui ind Probe Basic GUI.

Best regards
 

Hi all,
At 19:55 in this video...

 

I was making a set of lathe tool height adjusters, and used a loop with G55 to repeat my tool paths along a piece of stock. This worked great for engraving and drilling such as this code...
o100 Sub
 G0 X0 Y0
 G0 Z5
 G01 Z-2 F100
 G01 Y-14.5 F1000
 G01 X10.5 Y-20 
 G01 X21
 G01 X30 Y-14.5
 G01 Y0
 G01 X0
 G0 Z50
o100 endsub

#50 = 0
G17 G21 G54 G90
; OP 1 engraver outline
M6 T16 G43; Drag engraver

o110 while [#50 LE 5]
    G10 L2 P2 X[#5221]  Y[#5222 -23* #50] Z[#5223]
    G55
    o100 call
    #50 = [#50 + 1]
o110 endwhile
M2

However, my last tool path was a 10mm endmill to cut the contour, and I just reused the engraved path and added G42 to cutter comp it. This errored out with Linuxcnc throwing this message.
 

Here is the code...
o100 Sub
 G0 X-10 Y0
 G0 Z5
 G01 Z-2.5 F100
 G01 X0 Y0
 G01 Y-14.5 F1000
 G01 X10.5 Y-20 
 G01 X21
 G01 X30 Y-14.5
 G01 Y0
 G01 X0
  G01 Z-5.5 F100
 G01 X0 Y0
 G01 Y-14.5 F1000
 G01 X10.5 Y-20 
 G01 X21
 G01 X30 Y-14.5
 G01 Y0
 G01 X0
  G01 Z-7.75 F100
 G01 X0 Y0
 G01 Y-14.5 F1000
 G01 X10.5 Y-20 
 G01 X21
 G01 X30 Y-14.5
 G01 Y0
 G01 X0
  G01 Z-10.5 F100
 G01 X0 Y0
 G01 Y-14.5 F1000
 G01 X10.5 Y-20 
 G01 X21
 G01 X30 Y-14.5
 G01 Y0
 G01 X0
 G0 Z50
o100 endsub

G17 G21 G40 G54 G90
M6 T10 G43; 10mm end mill
G42
G0 X-10 Y0
G0 Z50
M1
S3000 M3
G4 P4
#50 = 0
o110 while [#50 LE 5]
    G10 L2 P2 X[#5221]  Y[#5222 -23* #50] Z[#5223]
    G55
    o100 call
    #50 = [#50 + 1]
o110 endwhile
M5 M9 G40
M2

Is this just a simple error on my side? I didn't find anything in the reference doc's on cutter comp and work offsets not working together.
Cheers,
Mark
 

It could be the radio version that have the crash issues I guess.

MRx, you don't see these disconnects/reconnects for your wired pendant?

MRx wrote:

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

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

andrax wrote:

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!

MRx wrote:

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 

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.

Hopefully this helps somebody, I noticed the "skip lines with /" box was checked from your screenshot and it so happens I just got the same error right after I checked it and stopped after I unchecked it, It might be worth looking into. Good luck friends.

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