I really could use some help trying to figured out how to setup a delay for amp.joint when I enable the machine i get a instant error from joint.amp using clearpath SD HLFB  , from what ive read i need to add a delay for it.But the problem is ive tried but no luck please someone show me a confing to get me started.

Thanks 

I did not get a working stepper configuration out of MesaCT with a 7i76eu. I have posted the output and my working config here forum.linuxcnc.org/configuration-tools/5...erated-configuration

The output was supposed to be on the 02 stepper but it was connected to the 00 stepper. The feedback loop was not closed and it was not set to be in velocity mode. Look at the two configurations.

Raspberry Pi 4B running Gmoccapy 4.9.4 without any significant issues on a 3-axis turret mill.

CamBam used to produce 3D MOPs for cast iron model locomotive wheels.
Camotics and NCViewer used to simulate the GCode files produced. 

But, as we all know, issues do arise that need review.

NCViewer displays the GCode file and a 3D representation of the paths.
It includes an option that shows each GCode data point in the 3D display as a GCode line is highlighted.
The reverse does not work, selecting a data point does not highlight the equivalent GCode line.
 
Looking for suggestions on how to identify a GCode line when a path/point is selected on a 3D path display.
 
John

Here's at least a first attempt:


 

 

I searched through the documentation before starting this thread. That only shows how to wire it to a raspberry pi.

As I said at the beginning I do not want to use a raspberry pi. I want to use a w5500 ethernet board. Then connect with a pc. Like shown in the demo video.

Futterama
Thanks for your error reports and certainly for the corrections.
I >think< Tommylight usually amended the link in Post #1 to the latest version. Unfortunately I am still not afloat. There is a 95% finished update of the script with quite a few amendmends. Not good to go public yet. I do hope I could give this some time soon.
Meanwhile, please do as you please and keep posting your findings.
greez
chris
... and thanks for the flowers anyway

I have a similar setup on my lathe; I'll send it to you later.

forum.linuxcnc.org/27-driver-boards/4698...7i96s?start=0#252760

I made a lathe with manual control of two axes simulatively, although apart from the servo motor as the main spindle I didn't have another axis as in your Z that could do its thing while these two are moved manually as I understood. maybe something in this topic can help.

this won't work either in sim mode or in reality, I tried something via chatgpt but I know that it doesn't work, it can't create a routine. here is my configuration if anyone is free to look at where the error is and what needs to be added in Hal eventually. Tx m6 works but will not return the tool to its pocket when you give it another tool, it also reports in the bottom line that there is no tool even though in reality it took it. each pocket has its own active high sensor on inputs 16-21 and the spindle has a sensor for ``flush'' input 10 the tool is in the spindle, input 12 reports that there is no tool in the spindle. Thanks 


youtube.com/shorts/CXxlm92xtt8

Sorry for my bad English 
Here are a picture from the handwheel /mpg and from the mess/cabinet

Not sure if it will help a lot 
Pg up and Pg down buttons works well however I need to manually select the axis. The knob doesn't change the selected axis in Axis gui

Edit: I finally found the issue, I always struggle between axis and joint... 
I managed to move axis using the joint instead of axis. 

I'll try an make new firmware sometime today or tomorrow.

What I will do is add combined encoder/stepgen index pin to the first 4 stepgens
on 7I89 encoders 0..3

There are some constraints with muxed encoder/stepgen index pins so
5 is awkward but  6 is possible if really needed (with a dummy stepgen)

5i25

Ok, thanks, I'll try the G540.

It that a 5I25 or 5I25T?
 

adding:
        self.w.jogincrements_linear.setEnabled(0)

to the end of
    def init_widgets(self):

Will make it not respond to screen clicks, but should still respond from HAL pin changes