Advanced Search

Believe me… I have read through countless hal-, ini- and remap-configurations, but since LinuxCNC is a relatively complicated piece of software, it’s hard to find all the needed information and sometimes I almost don’t even know what to look for.

I have watched Erik Salos’ video several times, and it is by far one of the best sources I have found on this topic. And even though he is using the carousel.comp (which I also would have used if my tool-carousel wasn’t controlled by a +-10V signal) I have gathered a lot of useful info from that video.

But back to the topic…

I have the M6 and Tx remap working to the point that when I run an M6 Tx command from MDI, LinuxCNC executes the necessary prolog and epilog functions and executes the change.ngc file.

I have put some print-commands in the change.ngc file to verify that it is beeing called and executed and I have also successfully returned different parameters to verify that everything is working as intended.

But I can’t get it to execute G-codes from within the change.ngc-file. I have tried running G0-commands (e.g. G0 C180 and G53 G0 C180) but it’s just skipping the lines containing the G-code and the axis doesn’t move. When I run the axes in MDI they work just fine.

Any tips regarding this?

Thanks Tommy.  That was the one I watched about 3 times before the motion.digital-in stuff started sinking in.

I would note that it would likely be easier
to find a 7I97T than a 7I97.

I have a problem with the system coordinates, I have represented the machine axes in blue (when I click on the + button in axis and on each axis).
and the axes I need to orientate on fusion 360 so that the cnc machines in the right place (in red).

would the problem come from fusion or axis?

I have another cnc with another control card (edingcnc) and I don't have this problem.
 

 

Hey everyone.

I need to have the functionality of triggering M3 $0 S1 (plasma start) , and then, after a while, turn on another output. What G-Code can i use for this?

Then, I woud add also another one at M5 to turn off both at the same time.

M5 $0 (plasma end)
M7 $0

I cannot use the same output from M3 a timer for this, because the delay between both outputs will be variable and parameterized with the g-code.

Can i use the output from the marker? what if i also need the marker, are there other options available?

thank you.

 

I have always found a good search through the linuxcnc manuals to be of great benefit. See link
linuxcnc.org/docs/stable/pdf/

Hallo zusammen!

Ich habe mittlerweile einige Tests mit meinen beiden LCNC 2.9 Configs gemacht, die eine läuft auf AXis die andere unter QTDragon. Beide werden mit dem Desktop Symbol , das mal der PnCconfig Wizard erstellt hat, zuverlässig gestartet.
Jetzt habe ich eine weitere MESa 7i96S dazugekauft. Die habe ich auch erst mal mit dem PnCconfig Wizard erstellt, aber blöderweise das Desktop Symbol gelöscht.
Denn - über das Anwendungsmenü kann ich kein Linuxcnc mehr starten. Wie kommt denn das? Ich hatte das bisher nicht nötig gehabt, war aber der Meinung dass das immer gehen müsste. Was habe ich getan? Was kann ich tun, um das wieder zu bekommen?
Da ich noch immer Linux NEwbie und eher ahnungslos bin habe ich hier ein echtes Problem und bin für jeden Hinweis dankbar!
Vielen Dank schon mal und
Grüße,
Arno

Hi all
Have a lathe with linuxcnc with 2x vertical rotating 4 position tool holders.
When stop or e-stop the program midway a program i loose my tool offsets .
all the tools offsets are reset by the same amount. what could the problem be?

I'm thankful for any input of the many knowledgeable people here. I am currently educating myself on the topic of mesa cards and interfaces. So far I have the feeling that this retrofit will work well given that all 24v relais and the axis/spindle drivers can be used.

Are there any well documented "by the book" retrofits that I can study to see how this is done properly.

Yes I'm pretty much set on the retrofit since I just heard from Alcor's supplier that the parameter list is not available anymore.

Yes i am, just giving you a head start as it seems you are already set on retrofitting it.
I might be a bit quick on the draw since i have done several retrofits already, all use Mesa cards, all other machines i build use Mesa, i have nothing with Mesa, except the experience of never ever failing or any hiccups ever. And the best support on earth. Also, whatever the price of them, i have to pay at least twice since i live in a black hole, but i pay it gladly.

Yes, the signal is +-10V

In terms of number of IO pins, the control currently has 18 digital outputs, 34 digital inputs, the 3 analog axes, an analog signal (also +- 10v)for the vfd and two more analog pins.
The machine has position feedback through Heidenhain glass scales and a 3 axis module with a single output cable. To close the position loop, the data from this 3 axis module must also be read into linuxCNC, right?

@tommylight: are you referring to the mesa cards i would need to run this system?

Also, the machine comes equipped with 3 encoder handwheels on the front of the machine. I think that layout is really slick for manual type work on this machine and general movement compared to pressing buttons at the control. I've read before that with linuxCNC anything is possible if you are willing to tinker with the software and invest enough time, so adding these 3 "Jogwheels" should not be a problem right?

spumco wrote:

.. there's an excellent vid on YT from Erik Salo (sp?) about configuring a tool changer.  His explanation and demonstration of the digital in/out hal pins is excellent. 

This one ?

If the drives are analog +-10V, then in this order
Mesa 7i97
Mesa 7i92TM + 7i77
Mesa 7i92TM + 7i85 + 7i83 + 7i84
Mesa 7i96S + 7i85 + 7i83 + 7i84

my1987toyota wrote:

Ok Amazon you really failed me . I searched on there site with BTS7960 as the search query and
literally got NOTHING.

Yeah, this is getting really frustrating with google and youtube and duckduckgo, spend half hour looking for something you found a few days earlier with the same exact name, nothing, zero, zilch,! All those have become like PMS with mood swings!

I think it's time for you to do some (more) research.

First... there's an excellent vid on YT from Erik Salo (sp?) about configuring a tool changer.  His explanation and demonstration of the digital in/out hal pins is excellent.  Even if your configuration will be different (not using carousel.comp), it's still a very good introduction of all the things which have to be choreographed.

Second, there are many, many examples of tool-changer configuration files - including gcode subroutines - on the forum.  Yes, the forum editor is horrible, and the search tool is a bit lacking, but I'd suggest digging through posts as much as you can stand.  Once you've found a handful of configurations & subroutine examples to digest, go through them and make yourself notes in narrative form exactly what the author was trying to achieve.  Pay particular attention to what signals were passed between what 'things', and how that was accomplished.

That should give you an idea of the steps & sequence you need to really get started your own config.

As another resource, the Probe Basic GUI includes an ATC simulator - which also has various subroutines and so forth to review and digest.  No need to install the GUI if you don't want - just download the relevant files from github.  The PB tool changer scheme does not use carousel.comp, nor does it treat the platter as an axis.  All of the 'go-to-this-pocket' logic is contained within the subroutines, and the whole thing is designed to work with geneva-wheel mechanisms and 'dumb' motors.