Advanced Search

What do you mean with "SoE"?
Maybe i try to get a used Beckhoff AX5xx from eBay when thats easyer to use with LCNC.

... the SIEMENS etherCAT pcb is hard to get. it starts to annoying me...


endian post=327010 userid=29161

AX5xxx from beckhoff is SoE and it can be pain to create custom .xml which should be editable out of Sachas own .xml files...

 

tommylight wrote:

Rod, why?
He did not confirm that the machine has switches on both sides yet, so why send him that way, he will end up with a mangled machine.
 

Well he did say

Mother wrote:

I would imagine that it does. All the documentation suggests so and from what i can see on the other side (Its right up against a wall) It looks the same on both sides so I would wager it has them on both. So im going with yes on that.

 

I have managed to make some progress over the past weeks.

I believe I managed to add homing properly to the DeMS300 driver, however I am now facing the issue that the homing mode PDOs 6099, 607C and 609A (respectively homing speed, homing offset and homing accel.) are simply not showing up. Hence why the driver fails to initialize them. Interestingly 6098, the homing method, does show up on, but the other 3 do not. This makes the drive give the motor a current and fixes it in place, however it is not able to start the homing procedure and just stays in place. The control and status words look entirely correct, so my assumption is that the missing 6099, 607C and 609A PDOs are causing it to be unable to start homing.

As you can see in the driver I modified, those PDOs are commented out at the initialization (on lines 225-227). Uncommenting them has the driver compile successfully, yet it fails to start as it is unable to initialize them. I am not sure how I should initialize them properly. In the header file I changed LCEC_DEMS300_PDOS to 15 as well (it used to be 11).

Do you think the PDO mappings are the problem here? I had no success in establishing a connection over TwinCAT, but I may need to look into that again.

No, its random driver without any documentation (2abs servo driver)

You can't get the ECL16DP to show up on the ethercat bus?
This is the unit, right?
 
There sure seems to be an ETH1 and an ETH2.
There is nothing on "ethercat slaves" when you connect to ETH1 and power on?

Ah, ok, now things make sense.

That is actually the MX4660. But I had that servo with the built-in drive so I was only going to use 3 channels. The stepper power output channel plugs are a row under another row of plugs, hard to see, I didn't realize I skipped the 3rd and had the Z hooked to the 4th channel.

A common error is to not have the right vid and pid in the ethercat-conf.xml file.
Double-check that the vendor id and product code from the output ofmatches the vid and pid fields in ethercat-conf.xml.
Check that for all slaves (0,1,2,etc)
If that didn't help please attach the ethercat-conf.xml file, the hal file and the output of "ethercat slaves -v"

The hal and ini files are empty.
Is it the VEICHI SD700 drive www.veichi.com/product/sd700-high-performance-servo-system.html?
 

Hello everyone, I ask for help, I encountered a problem connecting the driver via etcherkat, everything is displayed via the terminal and the driver is visible, but when I launch Linux, the driver does not move. In my case, the driver is connected directly to the PC, and does not go into OP mode. I tried to connect to the delta drivers and everything worked. Unfortunately, there are no instructions for my driver. My assembly (hal, ini and xml files):

I have same issue,
QT5 designer doesnt load custom linuxcnc widgets,

what should I do?

Really situation is these: S1-M20 is a coupler based on Hishler chips as multiprotocol demux. You can set from ethercat modbus and other .... there are not a real connection from DI, DO module. Hishler chips drive the right master in module with correct register used from various protocol type. So if bus is not inizialize on Hishler, no comunication with DI DO, no pdos no sdo .... only comunication established. Need to know right inizialization sdo i think, and producer not know that because not usual with IGH. Really not sure Hishler is supported from IGH. SO for sure need to load original xml file on tiwincat, after check if usable xml is produced .... but probabily need to write a new component based on file that producer share with me. For sure that "driver" as it is write is not possible to build inside ethercat component forlder ... wrong library used and wrong structures. If someone have some suggest on these (whitout writing new component ... that become a sort of copy of one used for EL1xxx or EL2xxx) is welcome.

Real thanks for attention on these.