Advanced Search

Dear forum members,Hello!I am currently setting up and running two systems based on LinuxCNC and EtherCAT, and I have encountered an issue regarding system startup performance. I hope to receive assistance and advice from you all.Overview of System Configurations:

1. First System:
   • LinuxCNC Version: 2.8.4
   • EtherCAT Version: 1.5.2
   • I compiled the Linux kernel, Xenomai, LinuxCNC, and EtherCAT myself, and used a real-time network card driver.
   • This system's EtherCAT drives quickly enter the OP state within 1 second after startup.
2. Second System:
   • LinuxCNC Version: 2.9.3
   • EtherCAT Version: 1.6.1
   • Installed according to the stickied post on the forum. "Ethercat installation from repositories - how to step by step"
   • This system takes a long time (over 10 seconds) for the EtherCAT drives to enter the OP state after starting LinuxCNC, and sometimes it fails. At this point, I have to close and reopen LinuxCNC, which may sometimes result in success, but it is not consistent.

Commonalities and Differences Eliminated:

• Both systems are deployed on the same hardware platform, eliminating hardware differences.
• The configuration files are almost identical.

Request for Assistance:Given that the first system performs normally, how can I resolve the startup delay issue on the second LinuxCNC system?

• Is it worthwhile to try using different versions of EtherCAT?
• If so, what are the specific steps I should follow to do so?

Thank you very much for your valuable time and assistance! I look forward to your replies.Best regards

never trired OpenOCD, but you can send me the error mesage of the openfpgaloader.

with openocd you should make sure that it is written to the flash and not just to the ram, otherwise everything will be gone again after a restart

You can see whether it has worked by the flashing LED

btw, the default ip is '192.168.10.194'

the w5500 module has a little power led on the bottom, there is no jumper to power on/off this module.


not realy shure what you mean with the mapping,

the bob pins are mapped 1:1, if you need P17 (relais) on the BOB, you can use 'LEFT:P17' in your config.

 

if your BOB is connected to the other connector on the right, then you need to use 'RIGHT:P17'
 

Hi All,

I have an old VMC that is based on the Mitsubishi Meldas controller and Mitsubishi motors. The machine is in good mechanical condition but the control has given up the ghost, so I plan to replace all the servo drives and do a new controller based on LinuxCNC. 

A few questions that I'd like some input on:

• The machine has 3 phase 1kW, 3000 RPM motors on it for the X and Y axes and 2kW, 2000 RPM for the Z axis - they are Mitsubishi HA83  and Mitsubishi HA103 and have rotary encoders on them that means the original servo drives keep track of the absolute position. Does anyone have any thoughts on sticking with this motors or replacing them?  If replacing them, any suggestions for a good brand/family?
• If I just replace the drives, then it seems that the Nidec/Control Techniques Unidrive M700 series might be a good choice? Any thoughts. Ideally I would power the drives directly from the 3 phase 415V supply (the machine currently has a transformer which delivers 200V to the drives).
• On the control side, any suggestions as to which Mesa cards are well suited? Previously I have converted machines using the 7C81 and a Raspberry Pi and 5i25 and PC - I think this will need quite a lot of I/O so I'm thinking a PC based card this time.

Thanks,
Greg