Advanced Search

I don't know how to do this

It changes when I press the Set key, but I cannot connect it to a variable in the gui.

I think it is not possible to change this without going into the hal file. I tried every way I could think of but it didn't work.

I bound all other settings to variables. However, since this value is brown, I think the status file cannot be intervened. Does this color mean that this pin cannot be intervened?

TheRoslyak wrote:

Strange. I have this kind of drive, and I didn't have any problems with it, although I didn't run it for long. Actually, when you buy it, it's initially sold as either closed-loop or open-loop, and the seller asked me about it when I purchased it. Well, I immediately chose the closed-loop one.
 

Yes I have its big brother ECT86 running perfectly. I am sure I had this running  in testing with no load but lost the config. I think my manual XML has been used by most people on these drives. Pretty sure its found its way into ScottLairds linuxcnc-ethercat driver too.

@besriworld, I was hoping you had nailed it, but not to be. Being a plasma guy, I forget about inertia! I  tried disconnecting the drive and see if it runs with no load  but its no better.
The fault is "Joint 1 amplifier fault"

@tommy, this ethercat drive looks after the encoder connection. I can see the DRO moving when I twist the shaft so its OK. It has automatic tuning by default and the motor and drive are a matched pair. It can be set manually, but I don't think I need to go there.

Thanks everyone for their ideas. I am still none the wiser. From memory, there is an internal error register I might publish a pin for and review.

Hi guys. Since i've worked about this topic, i wanted to say something. First of all, Benb you are right. I also think software e-stop should be implemented in software side. I've integrated emergency stop button like yours to my machine some time. It was actually a circuit which cuts the power of motors, so when you pressed it the motor movements were being stopped but with a problem. The problem is that user was being able to open e-stop via gui(change the pins iocontrol.emc-enable-in and iocontrol.user-enable-out) while the emergency button is still pressed. And of course user was being able to move motors in software, without actual physical movement. I wanted to stop this action. As result, i've tried to add some logic in hal layer. But it didn't work as i want. The thing i really wanted was updating iocontrol.emc-enable-in and iocontrol.user-enable-out pins with extra control, which is emergency button is pressed or not. I've decided to examine the iocontrol component's source code because of this is the component which does the software e-stop. I've changed the source of iocontrol component in the way i described before, and it worked. I've left it as it is. The thing i did is:
1. Intervention to EMC_AUX_ESTOP_ON_TYPE and EMC_AUX_ESTOP_OFF_TYPE with checking extra pin which shows the button status. If button is pressed, iocontrol.emc-enable-in and iocontrol.user-enable-out are not gonna changed. If button is not pressed, it is okay to open e-stop in software.
2. Check the pin which shows emergency stop button is pressed in iocontrol's while loop, if it is pressed, update iocontrol.emc-enable-in and iocontrol.user-enable-out pins to do e-stop.

This solved my problem. User is no more able to change iocontrol.emc-enable-in and iocontrol.user-enable-out pins with a pressed emergency button and when the button is pressed, machine actually stops the movement and does e-stop.

This is my solution. I've changed the iocontrol component and integrated it in the way i described. The problem is that the way i check emergency stop button is pressed or not can be late. Because i am actually measuring the voltage which is given to motor drives. When it is lesser from some value, i am updating my hal pin as button is pressed. So the software receives the button status little bit late. But it is ok, if the button is pressed and there is no power, motors are not gonna be moved. I think it is safe.


I hope i didn't get your problem wrong. This is what i understand from the topic. If you guys have any questions, i can answer it in this context.

Thanks.

Which of the 3 options? What didn't work?
The easiest route is to install the kernel from Google Drive by downloading both files and install with:To compile it yourself, the easiest way is to use the already rt patched source. Then you need to use the right config file, the one in the attachment will probably also work for yours. Assuming that you downloaded that config file in your Downloads directory: 

Ok….
Erst mal danke …
So wie ich jetzt festgestellt habe wenn ich den G-Code ohne
M190 in QtPlasmaC lade nimmt werden die Mat-Daten ( Mat-Nummer ) die eingestellt sind abgearbeitet.
Ich dachte im G-Code muss immer ein G 190 Pn stehen

Ok…. alles gut

Danke und
King regarde
Juergen

Hello,
My system is:
- Debian Bookworm, LCNC 2.9.3
- Installed on Desktop PC with scripts: www.linuxcnc.org/linuxcnc-install.sh
I just revise SCARA dimensions:
My question is: after revising scarakins.c, how to let the installed LCNC know and run ?.
Thank you.

how can i resolve it..?when i  try to download manualy but it is shows 404 page not found
 

 I tried many things but I can't change cia402.0.pos-scale

   

Well, and I wrote the XML manually.

I solve the issue by making a custom tab and adapting the code snippets KCJ wrote four jears ago.

Strange. I have this kind of drive, and I didn't have any problems with it, although I didn't run it for long. Actually, when you buy it, it's initially sold as either closed-loop or open-loop, and the seller asked me about it when I purchased it. Well, I immediately chose the closed-loop one.

dacb wrote:

I also have this driver.  What are you using to power it?  I thought it might be my power supply.

220V

@royka Thank you for your reply. I have carefully read your answer, tried your plan, and finally decided to give up. Forgive me, this rookie, I really can't solve it.

Could you open halmeter from a terminal and select the pin plasmac.feed-reduction and then do another video. It should change to 60 as it begins each fillet end return to 0 at the end of each fillet.