Advanced Search

Wie du das MDI löschst bzw. exportierst musst mal googlen.
Hier gibt es eine Beschreibung zur  MDI_HISTORY_FILE
Ich hab das alles noch nicht wirklich gebraucht, mein MDI ist voll bis oben hin )

G0 G1 ist wie von dir beschrieben richtig.
Das M0 ist solange aktiv bist du die Pause Taste wieder drückst oder auf der Tastatur "s"

Ob Du das M0 tats brauchst musst Du ja entscheiden, hab das nur mal rein gemacht, weil ich dachte
Du machst was wenn die Achsen auch X110 und Y200 sind.

So dann viel Erfolg,

Gruß Fritz

Ob du zwei Achsen mit unterschiedlichen Geschwindigkeiten gleichzeitig verfahren kannst, glaub ich nicht.
 

I have worked through all the documentation, compared my files with the sim and changed all relevant subroutines (toolchange and m10 to m26) to fit my setup.
I know that my subroutines work, because (assuming T1 is in the ATC and T0 in the spindle) if I first type in a "T1" in the MDI Dialog, then press "Stop" because nothing happens and then type "M6" in the MDI dialog, then the full toolchange gets completed just like it should. The machine and ATC move correcty, all the subroutines that are called by toolchange.ngc do what I want and at the end the machines get set back into it's idle state. And this works with any tool combination. All good.

The buttons for moving the ATC CW and CCW, Clamping, unclamping and so on work perfectly fine as well.

But if I type "M6 T1" or "T1 M6" in the MDI dialog nothing happens, the machine doesn't move, and the cycle never ends despite the log showing that the toolchange sub and all the other subs connected to it got called and ended. Like I described in the last post, even changing to the tool that already is in the spindle doesn't work.
The "store tool in carusel" button doesn't work either since it is basically doing the same thing.

I have no idea where this might be coming from. Can you maybe send me a .hal and .ini file of a working real world config to compare to?

Ok, thank you. I've just finished running a toolpath generated by your updated nativecam and it's gone without problems.

Another difference I just noticed:
when you add a new feature to the feature tree, all visible fields e.g. subfields of features like array->item->polyline->start collapse to the minimum view; I'm used to them staying visible.

Under the 'view' menu, 'Hide All Fields' is greyed out for me and in the right-click menu in the tree view window, 'Show All Fields' is also greyed out. I don't remember using these in the past, since the default behaviour (of not collapsing feature sub-menus) was good/what I got used to.

Let me know if there's anything particular you want me to try out.

I didn't think about there being spindle brake override inputs in Halui. Those would probably be useful for this. But a little experimentation is showing me that you might need to use both of the Halui brake-on and brake-off pins for full control. By using those override pins you would not need to mess with the existing spindle.0.brake hal signal and it's connections.

To clarify, I got a notification of JT's Test message. That is the first and only notification I've received at my new email address.

I just found the cause of the strange voltages. 
it was some dirt that accumulated between the torch nozzle and the Shield. 
after cleaning the voltage dropped drastically. Between 2 and 10 volts. 
after this I put a pull up Resistor between positive in and negative in of the Thad.

that put the fluctuation to below 5 volts 
 Now it looks like ohmic probing works perfectly. 

This time it seems to have gone come through, (but I did have to fish it out of the spam folder.)

I dont know why someone would refuse from a picture, crazy as you can just google it…
Esab’s DMX bevel head is one of the nicest ones in the market, the simplicity is just really good.

Kutavar, former ESCCO, uses flash cut. Getting highdef from Hypertherm “easier” I call BS.

Note that the 7I53 will not work with the 7I94T (its a 50 pin Daughtercard)
A 7I89 will but that only gives you 8 encoders

You might consider 2x 7I84 rather than 7i70+7I71 if you don't need
so much I/O (2x 7i84 would give you 64 inputs and 32 outputs)

Thank so much you JT it seems to be working now

MennilTossFlykune wrote:

In gcode_graphics.py, yet another self.makeCurrent()

    def select_fire(self):
        if self.inhibit_selection: return
        if STATUS.is_auto_running(): return
        if not self.select_primed: return
        x, y = self.select_primed
        self.select_primed = None
        self.makeCurrent()
        self.select(x, y)

Does that work?

 

I added it to qt5_graphics and it didn't - I missed that gcode_graphics redefined it. thank you.

kcjengr.github.io/probe_basic/index.html

The link to the docs, see the parameters section and the config section

Hurray, glad to hear it!

The latest version of probe basic had many changes, many which deal with parameters being passed yo subroutines. You need to look at the subroutines in the sim folder and also the other files such as ini etc to find the new parameters. The var file also requires additional numbered parameters be added to store the ui user parameters and new subroutines were added that are required.

It is best to start with the new subroutine folder and edit only the machine specific changes required in the toolchange .ngc and m10 thru m26.ngc files for the machines io signals. This will resolve your issue. For parameters now being used see the probe basic docs which is linked in the sticky section.

Hello.
I'm "new" in LCNC ( I can copy paste with a little understanding the process)
The axis, and the spindle is working and moveing and doing the homeing sequence (with index).
Now I'm tryin to figure out the carousel component.
The machine is a Baz 15 CNC with random tool changer. (=1 in the config - axis ui)
The I/O signals connected to the mesa 7i96s and to a 7i84 board.
All signals now has names.
The carousel motor has a break. In the VFD it's hooked up and by running it loose, stops it lock. So the control should be with motor ON (cw) and a REVerse (ccw) signal. (there was 2 different speeds 24Hz 83hz, but on the new vfd i can't make them work, because in multispeed is in % and the revers is controled with negative %)
Activating the ATC output signals from LCNC one-by-one everything is moveing, the inputs are blinking.
The question is, how to make it move on by own with one command?
There are 3 sensors for tool search. 
S4 - index
S5 - count
S6 - count (on position)?
S7 - when changing and hide the carousel.

When I will be at home, i will add some fotos.
The tool change looks like this: