Advanced Search

OK I think that's beating a dead horse now, hopefully a mod will just wipe out the last 10 posts or so.....

Anyway I posted this as an issue on the Git repo of this....

I'm pretty bad with "code" so it'll take me all day to probably get nowhere but when I first started messing with Arduino Connector I whipped up a couple of different BOBs and first used it with a matrix style key pad I made. My friend added some code to AC that made it work correctly but I wasn't thrilled about the scanning/pulsing LEDs. So I went back and made the keypad out of I2C IO expanders. These are really just I2C inputs and outputs, nothing specific to a keypad. I built the keypad but dropped this cuz of the lag issues.

Now that I'm sort of picking it back up (hopefully the lag is resolved) I actually got to testing the keypad and it does work with a basic test sketch. Ideally it would be nice if I2C IO were added as a different input type to Arduino connector but just as basic inputs/outputs.If anyone wants to make an attempt, this is an example of working I2C IO and the schematic for my keypad. Seems like an easy thing if you know what you're doing.....unfortunately I don't. I'm testing this with an Arduino Mega but the I2C keypad was actually made for a Teensy 4.1 which is a hell of alot faster but has much less IO 

 
 

Is there any mechanism to use a qstackedwidget and some pushbuttons instead of the tab widget? I suppose you generally need to stuff some python in there to use the former.

Yes and yes. 

JT wrote:

That's best part about the Flex GUI you can put what YOU want/need in the GUI. I would think you can build the GUI you want in just a few minutes. BTW, there is a series of videos on Flex GUI. www.youtube.com/@Gnipsel/playlists
 

It's always hard to get started with something like this, starting from an example is generally easier but I think I'll start from scratch. I'll throw some questions at a more general post about flex....don't wanna clog up this one.

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?