Advanced Search

Well, that's disappointing! Thats exactly what I have done.
And all of my statuswords 1-3 are zero.
If you can see any obvious errors in the XML, let me know

Funny, I was just looking too. There is only one lcec slave showing

 

So if I go back and rework all the cia402 joints to point to the correct variable/pdo for that one slave, it might work!
 
 
XML and dump of PDO's is attached 

Hi, I am measuring on all pins (11 13 15 17) with no LPTR connected ~ 1.6V - When grounding CS (Pin 17) nothing changes....
LED CR3 is constantly on.

What can i che k in the FPGA configuration that may not be set to have SPI enabled?
Not sure if i used a spi cfg for my custom Bit file...

I created some for ethernet 7i80 and Epp sucessfull 7i90hd previously.... but then things went wrong....

QtPlasmaC updates - Master (v2.10):

• rename variables to avoid conflict with python builtin names
• remove redundant str() calls in f-strings
• fix tab level
• fix typo in pmx485 fault list
• allow file clear button to work if single cut encounters a bounds error
• clarify section/option error message for user buttons
  

I asked Rony for it, let's see what he says.

Here is a litttle exercise.
Comment out all connections to lcec for the say fourth drive. No cia involved, only lcec.
Start linuxcnc and then start halshow.
First set lcec.0.x.4-opmode to 8.
Then step by step enter 6, 7 and 15 as 4-controlword (or 4-cia-controlword).
Watch how 4-statusword changes for every number entered.
Use a dec-to-bin converted to decode statusword.
Some of the statusword combinations are belwow
Probably especially valuable to compare the drive that works with one that doesn't.



 

yeh it was down here during the day (your night) quite a lot

  So all day yesterday I could not bring up the LinuxCNC forum. I could go to the main site but not the forum.
Does anybody know if the forum was actually down or is the USA starting to limit how it's citizens can interact
with others in the world? I tried multiple locations and devices yesterday and none of them would successfully
bring it up.
Obviously I can connect to it now. but the question remains.

The manual is google translated from Chinese and there is a windows configuration program that connects via USB. Too big to upload sorry but it is all there even if presentation is a bit lacking. It identifies all of the PDOs so it does not make sense if one axis works and others don't 

Is there some additional info needed? Like a SDO that specifies which drives to activate?

Do you have the manual? Couldn't find it, nor the esi/xml file.

Also, no errors or warnings in the syslog?

Actually Scott Laird on his repo mentions he only supported one axis on the Rtelligent ECRX2 and ECTx2
github.com/linuxcnc-ethercat/linuxcnc-et...mentation/DEVICES.md
Which also disheartened me. If it was easy he of all people would have done it

yeh, will see, the XML is correct and I have seen other posts about multi axis configs not working. Its a pretty simple drive so hard to get lost in it.
I think swapping the order would be a good early test. I still have to get things workinng reliably first.


 

HI PCW
Is it possible for you to provide us with firmware for the following combination please?
7i92T - 7i77 - 7i89
and
7i92 - 7i77 - 7i89

Thanks
Henk

I'm stupid. was using a messed up config somehow.

*nevermind!*

edit: technically I'm not stupid. this is weird. if I start from the menu, its the wrong config somehow. and if I start from the icon on the desktop its fine. even though they both point to the same config. Weeeird.

Ah, it is in here. it was a modbus conflict. but that makes no sense why it would come back. unless im using the wrong config, or my modbus dongle is misbehaving? (seems fine).

grr

But that's not how it works. AI?
All data from all lcec pins are collected by lcec and is sent to all slaves
in one datagram by lcec.writeall.
As long as cia402.read-alls and cia402.write-alls are between lcec.read-all and lcec.write-all
all cia402 pins should be updated and written to all slaves.
The different drives are just seen as different PDOs. Edit. In your case with a slave with multiple drives. End edit.
Follow drive 2,3,4's controlword and statusword in halshow or halscope to see this.