Advanced Search

Does the 6I25 finish configuration loading?  (no red LEDs except briefly at power up)

Is the 6I25 jumpered for 33 MHz PCI clock?

 

JT wrote:

blazini36 wrote:

I installed the new deb from releases but it doesn't seem to be adding anything new. I don't have qabstractproperties on the pushbutton whether I set it inside the stacked widget or not. Do I have to do anything special when upgrading flexgui?
 
I'm not sure what qabstractproperties is, what are you trying to do with that?

If you download the deb from the latest release and install it with gdebi or your favorite way you have the latest.

I'll add a screenshot to the docs.

JT
 

Sorry I mean, Dynamic Properties. I couldn't remember the name because it does not appear. This is from your video
 

This is what I actually have.
 

I see what you're doing there, I got it from the first video.....I just can't do it because it doesn't exist. So I'm asking where dynamic properties for the QPushButton came from

I installed the 1.1 deb from git using apt yesterday

cakeslob wrote:

Ok, zelo, do a quick test to see if the speed doubles if you reduce the scale by half

Velocity doubles until 79, when set to 80 it will give error.

Actually up to 79.7 works.

i just did an install yesterday on one of my machines, my method of choice is how i listed it in the docs here:

kcjengr.github.io/probe_basic/development_quick_start_apt.html

thing of note, i had to go into the synaptic package manager after install and manually change to the preempt rt kernel as shown below, just search for linux-image in synaptic to bring up the different kernels. i also like to remove any unused or older kernels on my machine pc's once i have fully tested updated kernels.

 

post your config files without them there isn't any way to identify the issue(s)

yep, already had that thought with the 4-jaw chuck route. the pneumatic idea will require different jaws for different material size but those could be made as well. that's the easy part. figuring out how to put it all together and not break the bank in the process is the hard part any kind of hollow body design for something fancy gets expensive quick the bigger you get.

I'm trying to get my head around the calculation of the shortest suitable step length/space timings for the Delta B3 servo drives I'm using.

The manual for the servo drives lists the following specification:

 

I have the drives set to 10 000 steps per revolution and I'm using 5mm pitch ball screws with a 2:1 belt reduction.

My goal is to have a rapid speed of 8 000 mm/minute on the X/Y axis. In order to reach that speed with the current number of steps per revolution I have to set the step timing to the following values:

DIRSETUP   = 800
DIRHOLD    = 800
STEPLEN    = 700
STEPSPACE  = 700

My question is how do I calculate how much safety margin these values leave me given the specifications of the Delta B3 servo drives?

I assume the Mesa 7i96s card I'm using will not be the limiting factor.
 

Thank you for your reply.

This is the latest version of you ds402.comp file?

forum.linuxcnc.org/ethercat/47358-kollmo...over-ethercat#279190

As an added bonus I just added Next Previous buttons for a stacked widget so you only need two buttons for unlimited number of pages.



JT

Moved to QtPyVCP section.

The problem I see is unless it can be used to only make a select obscenely rich people even richer it
is kept locked away from the general public's view.

  Usually when I 3D print stuff I will make a pocket for a nut to either be pressed in or slid in place. That way if I have
to scrap the part I can recover the metal nut back out of it. I do understand though that their are times when that
simply isn't possible.

Lower-case INI file variables are OK in most circumstances.
For example adding this into the Touchy GUI init code (I just happened to have that one in the editor, not a special choice)

And inserting this in the corresponding INI file

Gives this result
So lower case INI variables work in the general case.

But it seems that they do _not_ work in the case of G-code INI-file access.
This is probably because all G-code is lowercased before being sent to the interpreter. And then the bit of the interpreted that reads #<_ini....> variables explicitly uppercases them.
github.com/LinuxCNC/linuxcnc/blob/master..._namedparams.cc#L222

So, the actual situation is that if you want to read an INI variable from G code it must be capitalised, because case info is lost during the process of interpreting the G-code, and the interpeter assumes capitals.

To answer a question from the original posts, you can create a set of global parameters with particular values in the STARTUP_GCODES (would need to be a custom code or subroutine call, though).
But reading from the INI is probably best, accepting the limitations discussed here.

The first video really didn't show the steps to create a stacked widget page change buttons very well.



And I added a screen shot to the docs
gnipsel.com/linuxcnc/flexgui/controls.html#stacked-widget

JT

edit
If write 256(dec) to hal pin opens
and if write 512(dec) to hal pin closes
Also works function 16..

How to write values 256 and 512 to hal pins need a python script to convert boolean value to 16bit hex ?