Advanced Search

also you may need
sudo apt install git

try 
sudo apt install linuxcnc-uspace-dev

halcompile is part of the dev package.

So now I'm stuck at this step. it says git command not found....

---

If you are using cia402 compatible drives:

cd ~/dev
git clone github.com/dbraun1981/hal-cia402
cd hal-cia402
sudo halcompile --install cia402.comp

unknown wrote:

Been reading this for while, I think you need to reassess what you think you know compared to what you actually know.
Usually the stepper drivers are pretty hardy, the ones I have in my mill are about 15 years old and haven't missed a beat.
I've never heard of anyone having to make modifications.
Some of the early TB6600 drivers weren't as reliable as they should have been, no experience with them myself but many reports of them being that way.
So just settle down, do things the recommended way and don't try to modify things that don't require modification. And if you still insist of doing board level mods consult the data sheets for the components that will be affected. I'm sure this would have resolved the issue of "no flyback diodes".

 
I bought two 2nd hand machines with stepper system. They were pre configured for 4 axis, so I had some spares to kill. Out of the 8 drivers two or three are still working. (so I would say occasional death happens)
At least one or two I probably finished by creating a short when I was "repairing" the machines long time ago.
My guess is that the drivers were running at their limit for a long time and were a little undersized for the motors. (or can something age inside?)
The last year drivers started quitting service one by one. First by making some humming noises during machine start, then eventually stopped working.
Given the prices of new ones, not worth investigating. (but we are still talking 10-15 years, before failure)

If you have no space you can mount a Kuka robot on the seiling.


But I think plasma makes some mess, so a big feature is the water tray.
I skipped any ideas of laser or plasma. Laser I find too expensive for my hobby. $$$ and a plasma has to compete with the local laser company that cuts things for a small fee.

I am using LinuxCNC+EtherCAT to retrofit an old NC controller in Japan. I am not good at English, so I am posting on the forum using Google Translate.

I apologize if it is difficult to read.

I am currently using an old torque-controlled servo amplifier controlled by Beckhoff's EL5101+EL4132.

The problem is that in Homing, Index-enable is connected to jioint, PID, and Encoder, but when it is moving at the HOME_LATCH_VEL speed, when it seems to detect the C phase of the Encoder, it goes into a runaway state for a moment and immediately goes to the HOME_FINAL_VEL speed.

After Homing ends, the same phenomenon does not occur when Homing is performed again. It only occurs during Homing immediately after powering on.

When I made it with EM7004 before, I was told that I did not connect Index-enable to PID, but this time I am having trouble resolving the problem.

I cannot increase the PID gain because it goes out of control.

I am attaching the INI and HAL. Please let me know if there are any mistakes.

I am using LinuxCNC 2.9.4. The EM7004 system was created with 2.3.2 and has not been upgraded.

I have asked a question on "General LinuxCNC Questions" about whether there is a problem with the PID, but I was unable to find a solution.

Thank you in advance.

 

looking good!

I really like the look of QTDragon_HD too. I am using it with a ASUS VT229 21.5" touch screen monitor. It works really well.

I think you would need to build from source so you can select the code branch via git checkout

Dear forum members,
Hello!

I followed the stickied post to install Linuxcnc and EtherCAT, titled "EtherCAT installation from repositories - how to step by step". I simply want to switch to a different version of EtherCAT for some experiments, without altering any other software or configurations. How should I proceed?
 Thank you very much for your valuable time and assistance! I look forward to your replies.
Best regards

watched that vid... doesnt help. haha. (well no, it helps a little)
the auto config i did see but i got the impression it wasnt quite ready to go.

Needed some time to find this, see if it helps

or the wizard
forum.linuxcnc.org/ethercat/54495-ethercat-auto-configurator

xml file
 

Thank you for your response. These are the printout messages from two different systems, respectively.

First System:
[  238.627879] EtherCAT: Requesting master 0...
[  238.627885] EtherCAT: Successfully requested master 0.
[  238.639567] EtherCAT 0: Domain0: Logical address 0x00000000, 450 byte, expected working counter 27.
[  238.639571] EtherCAT 0:   Datagram domain0-0-main: Logical offset 0x00000000, 450 byte, type LRW at ffff91a4e6ce0318.
[  238.640138] EtherCAT 0: Master thread exited.
[  238.640141] EtherCAT 0: Stopping EoE thread.
[  238.640157] EtherCAT 0: EoE thread exited.
[  238.640159] EtherCAT WARNING 0: EoE External processing required!
[  238.640160] EtherCAT 0: Starting EtherCAT-OP thread.
[  239.249213] EtherCAT 0: Domain 0: Working counter changed to 21/27.
[  239.291171] EtherCAT 0: Slave states on main device: PREOP, SAFEOP.
[  239.572573] EtherCAT 0: Slave states on main device: PREOP, OP.
[  239.860401] EtherCAT 0: Slave states on main device: PREOP, SAFEOP, OP.
[  240.181272] EtherCAT 0: Slave states on main device: PREOP, OP.
[  240.251335] EtherCAT 0: Domain 0: Working counter changed to 24/27.
[  244.842333] EtherCAT WARNING 0-main-0: Slave did not sync after 5000 ms.
[  244.852890] EtherCAT 0: Domain 0: Working counter changed to 27/27.
[  244.886478] EtherCAT 0: Slave states on main device: SAFEOP, OP.
[  245.167387] EtherCAT 0: Slave states on main device: OP.


Second System:
[ 3248.220047] EtherCAT: Requesting master 0...
[ 3248.220054] EtherCAT: Successfully requested master 0.
[ 3248.225443] EtherCAT 0: Domain0: Logical address 0x00000000, 406 byte, expected working counter 21.
[ 3248.225447] EtherCAT 0:   Datagram domain0-0-main: Logical offset 0x00000000, 406 byte, type LRW.
[ 3248.225471] EtherCAT 0: Master thread exited.
[ 3248.225474] EtherCAT 0: Stopping EoE thread.
[ 3248.225489] EtherCAT 0: EoE thread exited.
[ 3248.225490] EtherCAT 0: Starting EoE thread.
[ 3248.225559] EtherCAT 0: Starting EtherCAT-OP thread.
[ 3248.225732] EtherCAT WARNING 0: 16 datagrams UNMATCHED!
[ 3248.299560] EtherCAT WARNING 0-6: Other mailbox protocol response for eoe0s6.
[ 3248.315523] EtherCAT WARNING 0-6: Other mailbox protocol response for eoe0s6.
[ 3248.339530] EtherCAT WARNING 0-6: Other mailbox protocol response for eoe0s6.
[ 3248.356219] EtherCAT WARNING 0-6: Other mailbox protocol response for eoe0s6.
[ 3248.371609] EtherCAT WARNING 0-6: Other mailbox protocol response for eoe0s6.
[ 3248.391524] EtherCAT WARNING 0-6: Other mailbox protocol response for eoe0s6.
[ 3248.409001] EtherCAT WARNING 0-6: Other mailbox protocol response for eoe0s6.
[ 3248.423525] EtherCAT WARNING 0-6: Other mailbox protocol response for eoe0s6.
[ 3248.439516] EtherCAT WARNING 0-6: Other mailbox protocol response for eoe0s6.
[ 3248.455500] EtherCAT WARNING 0-6: Other mailbox protocol response for eoe0s6.
[ 3248.471503] EtherCAT WARNING 0-6: Other mailbox protocol response for eoe0s6.
[ 3248.487610] EtherCAT WARNING 0-6: Other mailbox protocol response for eoe0s6.
[ 3248.503529] EtherCAT WARNING 0-6: Other mailbox protocol response for eoe0s6.
[ 3248.519501] EtherCAT WARNING 0-6: Other mailbox protocol response for eoe0s6.
[ 3248.535504] EtherCAT WARNING 0-6: Other mailbox protocol response for eoe0s6.
[ 3248.551521] EtherCAT WARNING 0-6: Other mailbox protocol response for eoe0s6.
[ 3248.567541] EtherCAT WARNING 0-6: Other mailbox protocol response for eoe0s6.
[ 3248.583503] EtherCAT WARNING 0-6: Other mailbox protocol response for eoe0s6.
[ 3250.223357] EtherCAT WARNING 0: 6 datagrams UNMATCHED!
[ 3251.223374] EtherCAT WARNING 0: 10 datagrams UNMATCHED!
[ 3252.223350] EtherCAT WARNING 0: 16 datagrams UNMATCHED!
[ 3253.223370] EtherCAT WARNING 0: 10 datagrams UNMATCHED!
[ 3254.223357] EtherCAT WARNING 0: 6 datagrams UNMATCHED!
[ 3255.223368] EtherCAT WARNING 0: 4 datagrams UNMATCHED!
[ 3256.223343] EtherCAT WARNING 0: 4 datagrams UNMATCHED!
[ 3257.223350] EtherCAT WARNING 0: 16 datagrams UNMATCHED!
[ 3258.223347] EtherCAT WARNING 0: 2 datagrams UNMATCHED!
[ 3258.720269] EtherCAT ERROR 0-6: Timeout after 10000 ms while setting state OP.
[ 3258.727412] EtherCAT 0: Slave states on main device: PREOP, SAFEOP.
[ 3259.223344] EtherCAT WARNING 0: 6 datagrams UNMATCHED!
[ 3260.223352] EtherCAT WARNING 0: 16 datagrams UNMATCHED!
[ 3261.223364] EtherCAT WARNING 0: 4 datagrams UNMATCHED!
[ 3262.223349] EtherCAT WARNING 0: 8 datagrams UNMATCHED!
[ 3263.223381] EtherCAT WARNING 0: 6 datagrams UNMATCHED!
[ 3264.116265] EtherCAT WARNING 0-0: Slave did not sync after 5000 ms.
[ 3264.223353] EtherCAT WARNING 0: 12 datagrams UNMATCHED!
[ 3265.227471] EtherCAT WARNING 0: 4 datagrams UNMATCHED!
[ 3265.287422] EtherCAT ERROR 0-3: Mailbox error response received - Unknown error reply code 0x0000.
[ 3265.287431] EtherCAT WARNING 0-3: Invalid mailbox response for eoe0s3.
[ 3265.327467] EtherCAT ERROR 0-3: Mailbox error response received - Unknown error reply code 0x0000.
[ 3265.327474] EtherCAT WARNING 0-3: Invalid mailbox response for eoe0s3.
[ 3266.227344] EtherCAT WARNING 0: 4 datagrams UNMATCHED!
[ 3267.227351] EtherCAT WARNING 0: 2 datagrams UNMATCHED!
[ 3268.227347] EtherCAT WARNING 0: 6 datagrams UNMATCHED!
[ 3269.227348] EtherCAT WARNING 0: 6 datagrams UNMATCHED!
[ 3270.033265] EtherCAT ERROR 0-6: AL status message 0x002D: "No Sync Error".
[ 3270.036267] EtherCAT 0-6: Acknowledged state SAFEOP.
[ 3270.227348] EtherCAT WARNING 0: 14 datagrams UNMATCHED!
[ 3270.435372] EtherCAT 0: Slave states on main device: OP.
[ 3271.227376] EtherCAT WARNING 0: 10 datagrams UNMATCHED!
[ 3273.239359] EtherCAT WARNING 0: 2 datagrams UNMATCHED!
[ 3274.239353] EtherCAT WARNING 0: 6 datagrams UNMATCHED!
[ 3275.243359] EtherCAT WARNING 0: 8 datagrams UNMATCHED!
[ 3276.243376] EtherCAT WARNING 0: 6 datagrams UNMATCHED!
[ 3278.247366] EtherCAT WARNING 0: 10 datagrams UNMATCHED!

(Repeated warnings about unmatched datagrams...)
Based on a cursory review, I speculate that the first system might be using a compatible version of the EtherCAT protocol with the slave devices (drivers), whereas the second system might be utilizing a newer version of the protocol that is not fully compatible with the older version supported by the slave devices.

Additionally, the "UNMATCHED" warnings seem to persist throughout the operation in the second system, indicating potential issues with data packet matching or communication synchronization. Note that I haven't included all the printouts, but the frequent occurrence of these warnings suggests ongoing communication issues.

Excellent let me know of any bugs please.