mixing CoE and mailing
01 Sep 2023 18:03 - 04 Sep 2023 12:20 #279596
by bkt
CoE read register that not support PDO's (solved) was created by bkt
Explain me better .... I have a drive that support CoE .... I can work on it whitout problem ... but it ha have more nice register to read, only is not supported from PDO system .... so think is possible read it with ethercat register data exchange system (EoE I think). But how I can do? need to make a new component derived from "generic drive" one? or need to make a new config file with EoE xml? or can mix a simple csp CoE .xml file with a EoE xml file?
best regards
and thanks in advances for every help
best regards
and thanks in advances for every help
Last edit: 04 Sep 2023 12:20 by bkt.
Please Log in or Create an account to join the conversation.
01 Sep 2023 18:57 #279602
by rodw
Replied by rodw on topic mixing CoE and mailing
If the PDO's exist, they should be able to be added to your xml file
The following user(s) said Thank You: bkt
Please Log in or Create an account to join the conversation.
02 Sep 2023 08:06 - 02 Sep 2023 08:22 #279651
by bkt
Replied by bkt on topic mixing CoE and mailing
sorry not well understand ... actually I can move that motor whitout problem .... my machine work!
Only I have some nice register like "temperature register", "torque sensor register", "ethercat status register (like preop, op, safeop, init)", "error type register (not 603F register other one more specific)" that not support PDO, but can be read trought modbus or EoE ..... so you suggest to add standard SDO and PDO in a one only .xml file for EoE comunication?
the above example can work ? (referred to red row):
regards
Only I have some nice register like "temperature register", "torque sensor register", "ethercat status register (like preop, op, safeop, init)", "error type register (not 603F register other one more specific)" that not support PDO, but can be read trought modbus or EoE ..... so you suggest to add standard SDO and PDO in a one only .xml file for EoE comunication?
the above example can work ? (referred to red row):
<masters>
<master idx="0" appTimePeriod="1000000" refClockSyncCycles="2">
<slave idx ="0" type="generic" vid="00000024" pid="00242C04" configPdos="true">
[color=#e74c3c]<initCmds filename="mailboxex-extra-io-rw-permission.xml"/>[/color]
<syncManager idx="0" dir="out">
</syncManager>
<syncManager idx="1" dir="in">
</syncManager>
<syncManager idx="2" dir="out">
<pdo idx="1600">
<pdoEntry idx="6040" subIdx="00" bitLen="16" halType="complex">
<complexEntry bitLen="1" halPin="M710_ctrlw_SwitchOn" halType="bit"/>
regards
Last edit: 02 Sep 2023 08:22 by bkt.
Please Log in or Create an account to join the conversation.
02 Sep 2023 13:34 #279661
by db1981
Replied by db1981 on topic mixing CoE and mailing
Attention:
CoE (Can over Ethercat) and
SoE (Sercos over Ethercat)
are both communication layers which are related to the ethercat slaves mailbox communication layer (pre op state) . Both are usable with the lcec.
EoE (Ethernet over Ethercat) is an layer to establish ethernet communication over you ethercat bus (tcp/ip ftp , drive setup software etc..) . if your slave is able to do EoE you can create an virtuall network adapter for direct acces to the slave through your ethercat master. (there is an long thread about Indramat drives and the necessary setup for this, ~3-4 years ago.... )
All these things are not related to process data communication (pdo, sdo) at running state. (ethercat op)
CoE (Can over Ethercat) and
SoE (Sercos over Ethercat)
are both communication layers which are related to the ethercat slaves mailbox communication layer (pre op state) . Both are usable with the lcec.
EoE (Ethernet over Ethercat) is an layer to establish ethernet communication over you ethercat bus (tcp/ip ftp , drive setup software etc..) . if your slave is able to do EoE you can create an virtuall network adapter for direct acces to the slave through your ethercat master. (there is an long thread about Indramat drives and the necessary setup for this, ~3-4 years ago.... )
All these things are not related to process data communication (pdo, sdo) at running state. (ethercat op)
The following user(s) said Thank You: tommylight
Please Log in or Create an account to join the conversation.
02 Sep 2023 21:51 #279680
by bkt
Replied by bkt on topic mixing CoE and mailing
thanks db1981 ..... so in OP mode can or not use CoE AND EoE at same time? CoE for drive motor with usual PDO and EoE only for read some register not possible to read trought PDO?
Example: I use my machine.xml file with SDO and PDO for preop and than op state .... but need to read reg 1001h udint 16bit (that not support PDO) .... can insert an .xml file for EoE reading?
regards
Example: I use my machine.xml file with SDO and PDO for preop and than op state .... but need to read reg 1001h udint 16bit (that not support PDO) .... can insert an .xml file for EoE reading?
regards
Please Log in or Create an account to join the conversation.
03 Sep 2023 20:11 - 03 Sep 2023 21:05 #279759
by bkt
Replied by bkt on topic mixing CoE and mailing
@db1981 ok find .... you means have a second master or bridge port for EoE comunication only right? so i can have lcec.1.x.myNonPdosReg value right? I well undestand these time? these is the only possibility?
@all .... I find these: fh-soft.de/src/ethercat-userspace.html#Usage than these: forum.linuxcnc.org/ethercat/22346-ethercat-hal-driver?start=330
regards
@all .... I find these: fh-soft.de/src/ethercat-userspace.html#Usage than these: forum.linuxcnc.org/ethercat/22346-ethercat-hal-driver?start=330
regards
Last edit: 03 Sep 2023 21:05 by bkt.
Please Log in or Create an account to join the conversation.
04 Sep 2023 09:18 - 04 Sep 2023 09:49 #279806
by bkt
Replied by bkt on topic mixing CoE and mailing
Ok an other solution can be using pyton routines for launch reg_read istance every 500ms so we can update 2 or 3 interesting register whitout using EoE or other complicated stuff like make new one Lcnc Ethercat
drive for read SDO
(because that register was object and not pdos entry) .... plus I can read during OP mode i think .... NEW problem, command:
return every time these error on terminal ....
think because bad usages .... how make wrong?
regards
ethercat download -p1 0x607A -t float
return every time these error on terminal ....
'download' takes 2 or 3 arguments!
think because bad usages .... how make wrong?
regards
Last edit: 04 Sep 2023 09:49 by bkt.
Please Log in or Create an account to join the conversation.
04 Sep 2023 12:14 #279816
by endian
Replied by endian on topic mixing CoE and mailing
Very interesting reading..
I had common problem of reading some PDO but it did not want to add without cyclic communication over ethercat... there is object for startup but no for any source of read only during cyclic operation....
I am currently pinning myselft here
I had common problem of reading some PDO but it did not want to add without cyclic communication over ethercat... there is object for startup but no for any source of read only during cyclic operation....
I am currently pinning myselft here
Please Log in or Create an account to join the conversation.
04 Sep 2023 12:15 #279817
by bkt
Replied by bkt on topic mixing CoE and mailing
I solve .... these is the currect comand (upload instead download) ..
for example and obtain manufactorer custom string
regards
ethercat upload -p 1 -t string 0x1009 00
for example and obtain manufactorer custom string
regards
Please Log in or Create an account to join the conversation.
04 Sep 2023 12:19 #279818
by bkt
Replied by bkt on topic mixing CoE and mailing
In these case if you would read only at startup (preop) .... see link for read SDOs object .... but personally would check that object sometime ... so prefer send a terminal command like these above and grab value ....
No time for develop EoE comunication ... and upload commend can launch during moovement whtout problem ...
regards
ethercat upload -p 1 -t string 0x1009 00
No time for develop EoE comunication ... and upload commend can launch during moovement whtout problem ...
regards
Please Log in or Create an account to join the conversation.
Time to create page: 0.114 seconds