Advanced Search

Hi,
I am currently running a 7i96S with a 7i74 sserial card (7i96s_7i74d.bin), but I need a second hardware PWM generator (pwmgen.01) on Step 5 (or any available physical Step pin) to modulate my Raycus fiber laser with a variable duty cycle. Is it possible to configure the 7i96s like that ?

I'm looking for a way to execute a. Bash script or some other way to setp the value of a number of Hal pins or hal signals when the machine goes to the off state. Not when just when aborting a running program. But a situation during a running program that results in machine off, such as hitting a hard limit, I would want to execute this.

I just re-read what I posted - that was kinda unhelpful of me.  Sorry.

The dirty way to 'turn off' the underlying M-code hal pins is an and2 component.

I assume you're using a motion.digital-out-NN to set the pins (G64 Pnn).  From there, the digital-out-NN pin is connected to something, maybe through some other signals/pins.

At some point downstream of the digital-out-NN pin, you can insert an and2 component that requires motion.motion-enabled (or halui..machine-is-on) be true along with the digital-out-NN pin.

Problem with that method is that an aborted program may leave the digital-out-NN pin true, and the second you turn the machine back on the above and2 component will resolve true and permit the and2.N.out to go true.

What you (and I) need is some way to clear out - reset - any lingering hal pin states left from aborted programs.  And the problem (as far as I know) is that an 'on-abort.ngc' file is only triggered during a program that's aborted on purpose.  If you get a power outage, or just hit the machine-off or estop button, the on-abort.ngc file isn't run and the undesired hal pin states aren't reset.

Some sort of start-up sequence that ensures the machine state is what you want - and it has to be set/run/active before the machine is permitted to enter the ON state.

This is why I'm thinking Ladder is maybe the route.

Are you looking for an 'abort' sequence, or a machine-is-off/tripped sequence?

The abort - i.e. an aborted g-code program - you can do with an on-abort.ngc that calls various M-codes to set the machine in a state you want.

If you need to force hal pins or write specific values to pins, you can create a bash program M-code and directly manipulate the hal pins.

I'm sympathetic to your question because I really, really need to go through all my custom stuff/logic and figure out the same thing you're thinking about now.  What are the various machine states, and what do I want to happen when it turns back on?

Example - I have a pneumatic door cover for my ATC.  If I stop the machine in the middle of a tool change the door stays open.  But when I retract the ATC (manual ATC M-codes) and restart LCNC, the door slams shut the moment the machine is 'on.'  Scares the you-know-what out of me every time.

It's not a graceful error-handling situation.

I'm rambling here, but I suspect all of the machine-state error handling and permissions might be better handled in Ladder.

A machine I'm working with uses a couple of M1xx custom M-codes to put the machine in a peculiar state for some machining processes.  This causes some significant problems if they are not properly canceled in the appropriate way.  To help with this, I would like to be able to "reset" the hal pins that the custom M-codes manipulate if the machine is disabled (put in the F2 "machine off" state.)  Is there a way to do this that won't interfear with the way the custom M-codes setp the hal pins they need to manipulate?  Basically I need the machine to setp certain hal pins when it goes to the "Machine Off" state.

Hello,

I created a topic about a LinuxCNC EtherCAT configuration from scratch -  CiA 402 Folder Missing . I did receive support there but the topic got a bit large in pages and posts. By the way, thanks to @andrax, he was quite active in helping me to get the EtherCAT working.

The reason for this new topic is to help everyone create a working and robust EtherCAT homing configuration. Perhaps, it will be great if the people who worked on the CiA402 and CiA402 Homing components join and discuss together.

I am not an expert in LinuxCNC, I started a few months ago with the idea to upgrade my plasma machine and out of curiosity. During the last days I managed to get a working configuration with the servo drive internal homing. I would like to share the settings here and get feedback, because it does not completely match the documentation but it works.

Basically, this is the example from dbraun CiA402 component. What I achieved is that using the signal 'x-home-index' I can home the drive using its internal homing method. The feedback from the servo drive is also available - 'stat-homing' and 'stat-homed'. I tested with homing methods 34 and 19 and it works fine every time I set the 'x-home-index'.

As per dbraun's documentation this configuration should work only for index pulse homing but by changing the homing method via the 'ethercat-download' command it works for every homing method selected. This is kind of confusing because I was expecting that in order to use any internal servo homing method I should use rodw's custom home component. The index homing described by dbraun was interpreted by me that the servo drive sends its index pulse via CiA402 and the LinuxCNC takes it and completes the homing but apparently it does not work like that.

Attached are the configuration files.

Best Regards
Konstantin Kolev

That is not the issue, it is the result of the issue, see if there is "raspi" mentioned in the error report.

Hello, First of my name is Samuel and I am completely new to the whole Linux enviroment but want to learn the process. I am experiencing some issues that I can go through whole setup process and everything is fine but the whole thing falls apart only when the sudo apt update followed by sudo apt upgrade messes everything up. And by evertyhing I mean I lose my link to mac address and some dependenciy files fail to complete and are left unconfigured. 
 What am i doing wrong I've MrRodW install and SZolkaa install and get the same result.

Below is what is not completing. Thanks again.

dpkg: error processing package linux-headers-rt-amd64 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-image-6.12.86+deb13-rt-amd64
 linux-image-rt-amd64
 linux-headers-6.12.86+deb13-rt-amd64
 linux-headers-rt-amd64
Error: Sub-process /usr/bin/dpkg returned an error code (1)

 

Hi all,
I’m looking for some advice on configuring a tool changer for a Samurai 120 CNC.The machine is currently running a Raspberry Pi 5 with EtherCAT-based Leadshine EL8 servo drives and motors.
The tool changer will require two additional motors, which I haven’t purchased yet. At the moment I’m considering the StepperOnline EtherCAT servo motors, as they’re significantly cheaper than the Leadshine units.
Has anyone here configured an EtherCAT-based tool changer using two motors, or got any advice on the best way to approach the setup and control side of it?I’m also using the Probe Basic interface, so I’ll probably need some help understanding how to correctly configure everything to work with that as well.Any guidance would be greatly appreciated.
 

I've added a few more filter and sort functions



 

I really feel like "Oscar the Grouch" now. I deleted the rant. haha.

I find wire EDM fascinating. However it is complicated. For small square sheet metal parts I suggest a bench vise, hack saw and file.

• fret saw
• jig saw
• scroll saw

No need to build my own waterjet to cut one stone with 2 birds. 

When is disconnects, is the init light illuminated on the 7I76E?
 

tommylight wrote:

Can you power off the machine and leave only Mesa powered?

I turned everything off except the PC and it no longer disconnects on its own and it doesnt show my mesa connection. But when I turn the mesa board and the machine on it starts disconnecting again every 45 seconds. So now I think you guys have a good point and maybe this could be hardware related.

Not my stuff!
Bumped into this, looks nice and usable