Advanced Search

See point #11 under this link :

linuxcnc.org/docs/html/config/ini-config...#sub:ini:sec:display

I noticed this recently as well, although I've not checked since. 

Hello,
I have the following problem: Every time I want to change a tool, I get this error message

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/qtpyvcp/widgets/display_widgets/vtk_backplot/vtk_backplot.py", line 1453, in update_tool
    self.tool_bit_actor = ToolBitActor(self._datasource)
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/qtpyvcp/widgets/display_widgets/vtk_backplot/tool_actor.py", line 423, in __init__
    points.InsertNextPoint((self.tool.xoffset, 0.0, -tool.zoffset))
                                                     ^^^^
NameError: name 'tool' is not defined

I completely rebuilt the system as described in Git. Everything seems to be working great, except for changing the tools. Does anyone have an idea what it could be?Greetings, Sebastian

I did give them a new IMG, maybe they did not deploy it.
Can you try this version? It should fix the screen issue
drive.google.com/file/d/103AY24a8eZ18pRH...ge2/view?usp=sharing

sorry not been here for awhile but life just got in the way, very bussy months here

looks like you have been bussy Grotius

dont forget with multi program running like i showed, its important that you dont tie each "interperter locekd to an axis group" becasue it needs to be far from it to be powerfull, any instanact should read any spindle feedback, know where other axis are so can follow them as a slave or master axis "offset" etc
so yes that a hal layer thing so hal can pass info between each other.

because each program group can and should be able to command other axis out side its "group" so program 2, shuld be able to move Z1 , so part can position from the guide bush. very much how you manage mode/group switching

ill try and find the page in one of my manuals for lathe and share will give you some ideas i think. better than many words, but abit like this...

while on swiss yes each "program instance" has an axis group set. i can change mode with a G code, like G710 etc (there are loads of these code sets) and it will control how these 3 programs interact together, you have to use same G710 setting code in all 3 or it alarms out

then control knows program 2 is now master , or program 3 is master etc realy which axis group the other 2 must be salved too..
(btw not all swiss etc have 3 heads, some only have 2, some have just 1)

eg
that way, you can program threading on program 1 , have X and Z do thread of a pitch say 1mm, while program 2 can also do threading, following Z in the program of Z1 but do a different pitch on Z2 of say 2mm , as it can read the spindle encoder also into both interpreters etc..,

on a fixed head lathe, you dont need to follow Z1 as your stock does not move,
unless your chasing the main turret with a sub spindle, while main turet works on front spindle like that miyano video.

yes you can bring in a sub for support and hold the part, and have Z3 follow Z1 while turret does what ever.. sounds complex but with simple switching etc becomes abit natral thinking on program layout etc for the siwss world of coding and setup.

but yes as you said making linuxcnc multi interpreter and multi hal is abig challenge many have looked at it before and no one has ever taken it on.

sorry for long reply

Yes its a nice vid.

I see you have HOME_SEQUENCE = 2 for your tandem axis YY

This should be HOME_SEQUENCE = -2

The -2 lets the system know that it is a tandem axis.

Minor clarification on my earlier post

I don't think it matters when carousel.comp is in INDEX mode, but the config above is for a step/dir motor (stepper in my case) run through a 5:1 reducer.

The basic connections should work for a geneva wheel mechanism, too, but I just wanted everyone to be aware that the carousel.comp parameters/settings will need to be adjusted for speed and the fine alignment speed/time.

Chris - if you're contemplating a GUI-facing ATC interface with a 'settings' page to pass values through to carousel.comp (like the probe page does), you'll need to:

• Include ALL the carousel.comp pins/parameters for all the encoding types, or
• Lock it down to INDEX mode, and the user is required to have both sensors

Hello Tommy
Thanks for that - I will look into hal components. I was really not sure where to start. It is only a model engineering lathe so will not be pushed as much as a production machine. I will fit a tachometer to the spindle but accurate feedback is not really of great concern. And yes it was CSS I was referring to. At least I will have continuously variable spindle speeds on the new lathe - the previous one was too much trouble to mess around with the spindle gears and in theory the spindle speed needs to change with the tool X position anyway for optimum results. I have been using LinuxCNC on the lathe (and mill) for at least a decade, but the old lathe was far too crude to be worth messing around with optimisation.

COFHAL wrote:

yes, work.

???

No plugins, but hal components written in C, fairly simple once you have a look at them.
I think you mean CSS or constant surface speed, i am pretty sure LinuxCNC can do that, but it does require having spindle feedback wired to LinuxCNC (physically and in hal), prefferably A, B, and Index to be able to also do threading (it can do with 2 of those, not sure exactly).
Stoping spindle during tool change is built in and can be set in the ini configuration file. Pretty sure it is by default as i had to change that on my Mazak, been over a year since i did that....

Interference/EMI so:
-drive must be grounded
-motor must be grounded from the drive
-ferite bead on motor wires helps a lot
-get a good USB cable, Baseus, Ugreen, Satechi are good quality

Also, what acceleration is set in the ini file?

yes, work.

Here is a nice Video

SPI can be enabled by modifying the config.txt file and enabling the SPI option which is disabled by default.

sudo nano /boot/broadcom/config.txt

# uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
dtparam=spi=on