Hakan wrote:

rodw, I kind of think of a structure like this

Code:

if drive ready   if csp   else if csv   else if pv ...   else if probing   else if homing      if homing_method == 1      else if homing_method == 2      else if homing_method == 37         Do the torque homing. Although it doesn't seem to be standard       Keep track of what op-mode we were in last time so we recognize a transition between op-modes. To deal with offsets and such things.

Great feedback I wasn't really happy with what came after the state machine but I've had to put this project down for a week or so and you forget everything when its so complex. 

The 7I76EU is compatible with 7I76E hal/ini files, so you can
just select "7I76E" in pncconf.

If you have usb, you can update with Deb files

Run another update i think your on the faulty commit. Should be resolved now, stable is now 0.6.5

Does this value always needs to be equal to the min value? Please help, thanks.

Hello. 
I'm new in this form. I couldn't config my Mesa Card 7i76EU, the PncConf doesn't show the 7i76eu. I'm using Linux CNC 2.9.8. Thanks in advance.

You maybe could check the lathe macros uo files using editvcp and fine the lathe macros in the probe basic widgets directory and verify the parsee widhet entry names correspond correctly with the macros being used. From a glance it appears they may not be the same.

github.com/kcjengr/probe_basic/tree/main...dgets/conversational

You need to make sure those variables are get ng from the ui to the subroutine at the top.

rodw wrote:

There is no need for a GUI to get involved with external hardware. Thats what halui is for.
When GUIs extendRod their scope, we get a mess with differing configs for no reason.

Rod, I use the Axis GUI as representing what the hardware controls on my Three axis mill have done and are doing. In particular when setting the tool offsets using the touch off gui buttons, If the X or Y axis instead of the z is selected, then the tool table gains an unexpected x or y offset. If you control the machine by the gui that's my lookout, but to move a big machine around you must use a pendant. I have mpg and three momentary buttons to select the axis for the mpg to drive. It is very easy for me to move the machine only with the pendant, and lastly touch down the z direction for work and tool touch off with the x still selected because my jog buttons are not reflected in the gui. Done it too many times.
But, today, I found the forum.linuxcnc.org/38-general-linuxcnc-q...ns/50151-axis-select  python script, and its transforming. The radio buttons move with the last jog axis selected, and I can stop worrying quite so much about stray tool table entries.

Sorry for not responding but Ive been trying other distributions (Mint, Ubuntu, and some wonky 3rd one I cant remember) hoping for better results and all end in either failed installs or crappy results.

I have another pc im hoping to try but havent gotten to it yet. Ill try the clock correction thing tomorrow and see if that yields anything better.

grandixximo wrote:

New PR from YangYang is ready, hopefully will be merged soon in master

This adds ruckig in the planner type 1
if you want to test it get the binary from

github.com/LinuxCNC/linuxcnc/actions/runs/21975584400

or build source from my repo

github.com/grandixximo/linuxcnc

Testers are welcome to report here or in github, thanks!
 
Hello gentlemen,

movement are incredible smooth ... basic shaping what I have tested till now is pretty ... but during movement at more points during simulation of rotation interpolation its jumping or woobing ... kind off braking and next accelleration 

most spiking during cloud of points are gone ... some spiking are still present but it a huuuuge step forward 

testing setup 2ms benchtop profibus master 3axis geany gui ... 3 servo axis with synchronized speed control loop at 2ms

some testing fault popups triggered during the movement of file 3_1001.ngc

I am still testing at default simulation file from past but splitted to separated operations ..

thanks a lot for your progress ... I am watching it every single day with mount open and box of popcorn to reading the edits ... 

regards E.
 

I have noticed the slowing during the round movement too but I forgot to noticed it here.... yes it is present and its present during 100% feed value ...

crashes are not present during the 100% feed just if its not 100% ... 

crash log is in the attachement if somebody are interested ... 

I’ve updated AndyPugh macros to the latest version, and now it seems to work, but it shows the tool change tab and doesn’t go any further.