Advanced Search

I just released version 1.2.1 of Flex GUI which includes Axis style controls and an example of Axis style GUI using Flex GUI.

JT

I tested it. (Updated dialog_widget.py and macro_widget.py)
It works fine, but only with the "load" button. If I want to save the settings, it's the old way. (path from qtdragon.pref)

I think it would be better to always use the path defined in the macro file. Then each macro can collect its different settings in a defined directory.

If it's a lot of work I wouldn't bother. Either I will finish the qt version or adapt your version.
Qt version seems to mostly work, but looks slightly different:

 

 

Does the sample basic spacer work for you?
Also the turners cubes I can't get to work (flat verse diameter error)

Chris

PCW wrote:

With Mesa hardware (and most external hardware step/dir interfaces
or even EtherCAT drives), the velocity (step rate in this case) is updated
every servo thread.

This means that there is a constant velocity between updates. This constant
velocity means that that you will  have a small error (chord error) between a
desired curved path and the actual (linear interpolated) path.
 

Okay, that's interesting, and of course I have more questions.

First, does the Mesa know how many steps it should count?  Will the longer period introduce greater error in the length of each chord?  I.e.,  might it overshoot by 1ms worth of steps, vs. just 500ns worth of steps?   Or is the command to the Mesa really just "start moving at N steps/second"? (rather than "start moving at N steps/second, for 10500 steps")

Second, the chord error you describe would only occur for a curved path.  If the G-code is written completely using straight-line approximation (which of course introduces its own chord errors), it seems like the longer servo period wouldn't introduce any more error at all.  True?

In any case, it sounds like I can stop worrying about my 2ms servo period for the time being.

paul

For a 7i96 spindle you have to add that manually at this point. Now that the 7i96 is back in stock I might work on adding a spindle to it in MesaCT.

Watch the output pins as you toggle flood and mist in the halshow program.

JT

macrotab will now honour these entries in MACEOOPTIONS:
default:default.txt
path:~/linuxcnc/nc_files/macros

You can set them to any valid name.path you like (filename must end in .txt)

Do you think it would be nicer to use this path the very first time then use one from the preference file? This would make it remember the last used path rather then always using the one defined in the macro file.

I prefer the ice40 when I need more pins, e.g. the Devantech iceWerx iCE40-HX8K.
it has the advantage that it can be used with the opensource toolchain.

otherwise the tomverbeure.github.io/2021/01/22/The-Col...velopment-board.html is also pretty cool

Since a QT version is currently in development, I think it would be better to use that version for QT interfaces.whithout making strange combinations.

Regards
Giovanni

There is a slowly developing version for qt screens:
github.com/LinuxCNC/linuxcnc/commits/qt_ncam/

One more correction would be useful.

In the macro file there is such an entry as path:~/macro,
I think that it should be the directory where configurations are saved and from where they are read. Instead, it always opens the directory from the "last_loaded_directory" entry in qtdragon.pref

> 2. Where are the videos ?

Coming soon. Our 4G cell service and broadband internet went down for nearly a day :|

> Sometimes stuff shifts mechanically

I verified that the PCB is working as expected. No welded contacts, etc.

> Is the PC you use to control the machine "frozen in time" (not connected to the internet or outside world)

It is connected to the internet, but there are no automatic updates happening. The software hasn't changed in at least 6 months. I also haven't touched the relevant HAL sections in as long.

1. Alan is right, not the same problem/issue
2. Where are the videos ?

I think in one of his videos, the Velocity Anti Dive is always active and THC is never active despite being enabled, hence my procedure.
BTW, that procedure should be in the docs, preferably a bit better explained and formatted, and should be mandatory for properly setting up the machine initially. This would save a lot of headache later in daily use, although definitely the Phils Auto Volt thingy does a pretty damn good job given the variety of hardware used and the amount of things that can be wrong and still cutting decently.
And so should be the Cutting fine tuning, again not very important but can be the difference between 3 minutes of cleaning and 30 minutes of cleaning parts. I am sure i wrote about it, but can not find it, and again, this would also need a bit of fines as i am still not good at explaining stuff.

> I do have the same problem
If your torch moves at all you have a different problem than me. I'd recommend opening a new thread and ask for help there.