Advanced Search

I use two stmbl - I just plug them in, but I use a different card and a 7i44.

I think each stmbl needs a separate smart serial connection.

Happy new year!
I have a mill with spindle that has 7.5kw asynchronous 3phase motor driven by inverter.
Inverter driven by -10+10V from 7i33TA also i have installed an encoder ABZ 500lines to some gear of spindle (known motor:spindle ratio)
connected to 7i33TA. How can setup spindle for rigid tapping ? Is there any howto/tutorial ?
Thank you

It’s impossible to know what’s going on without looking at his config.

I think some of the confusion with GUI estop buttons and QtPlasmaC comes from the fact that every time estops come up with regard to plasma a certain forum user shares his infinite wisdom and Hal logic and completely muddies the waters.

edit:  in case it wasn’t clear I didn’t mean you Tommy

I reckon the transistor was a pretty good invention, yeah an improvement on what the vacuum tube does, but a new way of doing it.

Yeah old mate Nikola go screwed with the whole radio thing.

Mate wait til you meet an Australian Chippy, they'll tell their shit don't stink, tho judging how full of shit some are I doubt if they have actually done one, this one reason why I dropped out of my trade.

is this a dev version? Did you run the . /scripts/rip before?

IIRC, when choosing normal button for e-stop, it does not add a line in hal for it.

F-engrave allows the user to add a one line header. I want to have two pieces of gcode added:
G64 P0.001 and G4 P3
The three second delay is the ramp up time on my spindle.

Including both on the one line allowed results in an Axis error, it says I can't have multiple P words on the same line.
I tried inserting /n (and \n) in between; Axis complains about the slash.

Is there some other way to get Axis to interpret a single line of gcode as two lines, or to allow two P words?

Thanks!

It'd be much easier to help you if we had a back up of your config created from the GUI.

linuxcnc.org/docs/devel/html/plasma/qtplasmac.html#_support

That said, by default in QtPlasmaC, the estop shown on the GUI is an indicator only.

Setting Estop type = 0 in the [GUI_OPTIONS] section of the <machine_name>.prefs file, will change this button to an indicator of the hardware E-stop’s status only. This is the default behavior.

So I confirmed that all declared ini variables are READ_ONLY

file: src/emc/rs274ngc/interp_namedparams.cc

param.attr = PA_GLOBAL | PA_READONLY | PA_FROM_INI;

Documentation should make that clear.

Yea phil rime i get it.
And we do have the mini lathe too.

Been at a school in norway.

Sitting still for 6 years.
Got it working again.
But need to add safety stuff like e stop limit sensor ect

Ive circled back to this after getting annoyed with renumbering my tools for every program.


I've updated to 2.10 since the last time.  (LINUXCNC - 2.10.0-pre0-3745-g8102217123)

I renamed interpret.py and grabbed the latest version from GH (with the 'fix') and put it in the same folder.

Unfortunately, I'm still getting the same error.  Same thing - any tool number >199 causes the error.  Changing the tool(s) to a lower number makes the error go away.

Is there something else I should do to patch, or maybe the patch isn't working?
 

Here is a rt kernel for the rk3588:
drive.google.com/drive/folders/1r76sUsfG...6fGcz?usp=drive_link

Here you can see the result:
forum.linuxcnc.org/18-computer/48079-can...cnc?start=370#312714

do the inputs:

hm2_7i96s.0.inm.00.input-00
hm2_7i96s.0.inm.00.input-01

Change when you move the jog wheel?

If not, there may be a wiring error or the MPG A/B outputs don't have enough swing.

Check the high level at the 7I96S inputs. if lower than say 3.5V they may
need a pullup resistor to 5V to get enough swing for the isolated inputs

If the swing is too low, another option is to tie the 7I96S input common to +5V
(but this forces all inputs to be sourcing 5V type)
 

Ok moved mpg gnd to tb3-12, still nothing, im really stumped on this one.

Hooked the scope up while the motor was running. And it's interference that seems to be causing the loss of counting. Pulses look terrible .I'd imagine it's the motor is causing it. I have filters and coils on the AC lines and motor lines from the VFD. The encoder is mounted in a 3D printed mounting so it's not touching the case. When I ground the outer encoder case to a ground it helps a little but not much. Any ideas to mitigate the noise. Should I get another encoder with differential outputs and single end it close to the ec500? Or use the existing encoder and put a differential IC close to the encoder and Rx IC single end close to the ec500?