Advanced Search

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

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.

Conseguiu o procedimento?
Eu posso te ajudar, entre em contato e-mail removed

Do not make me regret this.

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.

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)