Advanced Search

Yes Cakeslob it's for my mill. Bought a cheap 24" touchscreen from Amazon and got carried away testing it lol Static IP address, is it 10.10.10.10 or 10.10.10.11  for the board ?

murphy, is this a new linuxcnc and remora install?

I'm trying to upload the config on another EC500 but I'm getting this error. It's bookworm installed from the linuxcnc iso on a PC.

Grotius wrote:

Hi,

Can we test the cia-402 and shortcut linuxcnc pos-cmd to pos-feedback so
there is no ferror in linuxcnc that can trigger a motion stop? 
Or test it by hooking the cia-402 to a stepgen or pid without closed loop feedback. 



 

 

hi
in my last test there was no following error on gcode running, the problem was the very low acceleration.
following errors appears on homing procedure

edit
testing now in axis tab manual controll it disable the drivers, i can only run when in MDI tab
Controll word in all drivers is
15 before hit start
Then all goes 6 and then 4 very quickly
 

Guys, can anyone tell me why the id.ngc and od.ngc macros don't work (nothing happens and there are no errors). The other macros taper-od.ngc and g76diam.ngc and sphere work fine? What could it be?

Hi,

Can we test the cia-402 and shortcut linuxcnc pos-cmd to pos-feedback so
there is no ferror in linuxcnc that can trigger a motion stop? 
Or test it by hooking the cia-402 to a stepgen or pid without closed loop feedback. 


 

The motor type doesn't matter, it just needs to be supported by the drive.
The drive needs to be EtherCat compatible or you will need an EtherCat
-> step/dir interface.

The problem is that the 'on_counts_value_changed' function uses the 'value' (encoder counts) as an absolute value (as you said), but you could use it as a relative value.

if new value is higher then the last value, then move up 10% higher then the current rate.
if new value is less then the last value then move down 10% from the current rate

The current rate you can get from STATUS or from the appropriate widget.
I'm sure there will be some minor details to adjust to.

Hello everyone, 
This my first post, I am a DIY hobbyist I am trying to learn what hardware is being used for a diy CNC mills. I ran across different system and setups but I have been unable to get a clear understanding on stepper motors being used in a diy home type CNC mill for a EtherCat setup.I have poked around and searched youtube but still have not got a clear knowledge, my question is can a Nema 23 closed loop stepper motors with encoder be used in a EtherCat setup or dose the stepper have to be EtherCat designated style motor.
I have some 23HS30-5004D-E1000 motors I was going to try and play with and see if I can learn a Ethercat system 

It's pretty rudimentary. There are these basic PDOsso basically one send a wanted position to the drive and read the current position back. That's all.
Following error is calculated in linuxcnc.
The cia402 module basically just passes position after scaling to the drive. And reads back actual position.
It also does the state machine walking, but that's in the beginning, then that idles.
 

Thayloreing wrote:

I do the ST Linkv2 procedure and it does everything right,
 

hi
by correct procedure you mean the one described by @Scotta to convert a STlink V2 into a CMSIS-DAP probe.
Pyocd will not see it as STlink, but as CMSIS-DAP

 

Some easier way to do this ?
This code github.com/LinuxCNC/linuxcnc/blob/master.../hallib/xhc-hb04.tcl
creates hal pins pendant_util.X can do something with these pins?

Moin,
willkommen im forum.

für den Raspberry gibt es auch einen Parport adapter, so könnte man ein altes alte Mach3 BOB vielleicht weiter nutzen:

byte2bot.com/products/parallel-port-raspberry-pi-hat

aber es kommt auch immer darauf an was man vor hat, es gibt da einiges an hardware die man nutzen kann: Mesa, Remora, Rio, GPIO.

Gruß Olli

hmm, I am not seeing 6065 in my drives manual.

0x603F reports any errors including following errors which are described as Closed-loop mode tracking error over limit

In practice, a drive error is thrown and this pin can be referred to to determine the error . I have seen a few following errors here.
 

English is not my native language, so sorry for possible mistakes.

I write a c++ program that I run by adding loadusr myprogram to custom.hal(I'm using AXIS gui). This program do some stuff and closes with exiting from AXIS. I catch unix signals like SIGTERM and SIGQUIT to gracefully terminate this program(closing file descriptors, sockets and so on). Everything worked fine on LinuxCNC 2.8.4 but stopped working when I switch to LinuxCNC 2.9.2.
I can catch and handle signals when I directly run my program from terminal, but I can't catch signals when I run it via loadusr. I try with SIGTERM, SIGINT and SIGQUIT signals, nothing gets caught. Looks like in LinuxCNC 2.9.2 AXIS does't sending any of this signals to close it's loadsur subprocesses. Does it use any other signals to close its subprocesses? Or do I need to use another way to catch the termination of the program?