Use of ODOT Ethercat coupler I/O?
- SteveP_CNC
- Offline
- New Member
-
Less
More
- Posts: 8
- Thank you received: 2
04 Jul 2023 08:28 #274729
by SteveP_CNC
Use of ODOT Ethercat coupler I/O? was created by SteveP_CNC
Hi All,
Currently working on another small project, which has one servo motor and a bunch of I/O. I had knocking around in my goodies cupboard a Odot CN-8033 coupler and a CT-121F 16 input card and CT-222F 16 output card. These look very much the same as the Beckoff equivalents, they are very cheap (about a third the cost) and it would be nice to use these.
When plugging these in they are seen by the network, however the ID is very strange.
steve@linuxcnc:~$ ethercat slaves
0 0:0 PREOP + RS750E(COE)
1 1:0 PREOP + 0x00860816:0x20008033
Plenty of information is received if the sdo is checked, here is a small sample:
steve@linuxcnc:~$ ethercat sdos -p1
SDO 0x1000, "Device type"
0x1000:00, r-r-r-, uint32, 32 bit, "Device type"
SDO 0x1001, "Error register"
0x1001:00, r-r-r-, uint8, 8 bit, "Error register"
SDO 0x1008, "Device name"
0x1008:00, r-r-r-, string, 160 bit, "Device name"
SDO 0x1009, "Hardware version"
0x1009:00, r-r-r-, string, 24 bit, "Hardware version"
SDO 0x100a, "Software version"
0x100a:00, r-r-r-, string, 24 bit, "Software version"
SDO 0x1018, "Identity"
0x1018:00, r-r-r-, uint8, 8 bit, "SubIndex 000"
0x1018:01, r-r-r-, uint32, 32 bit, "Vendor ID"
0x1018:02, r-r-r-, uint32, 32 bit, "Product code"
0x1018:03, r-r-r-, uint32, 32 bit, "Revision"
0x1018:04, r-r-r-, uint32, 32 bit, "Serial number"
SDO 0x10f1, "Error Settings"
0x10f1:00, r-r-r-, uint8, 8 bit, "SubIndex 000"
0x10f1:01, rwrwrw, uint32, 32 bit, "Local Error Reaction"
0x10f1:02, rwrwrw, uint16, 16 bit, "Sync Error Counter Limit"
SDO 0x10f8, "Timestamp Object"
0x10f8:00, rwrwrw, uint64, 64 bit, "Timestamp Object"
SDO 0x1600, "CT-222F"
0x1600:00, r-r-r-, uint8, 8 bit, "SubIndex 000"
0x1600:01, r-r-r-, uint32, 32 bit, "SubIndex 001"
SDO 0x1a00, "CT-121F"
0x1a00:00, r-r-r-, uint8, 8 bit, "SubIndex 000"
0x1a00:01, r-r-r-, uint32, 32 bit, "SubIndex 001"
SDO 0x1c00, "Sync manager type"
0x1c00:00, r-r-r-, uint8, 8 bit, "SubIndex 000"
0x1c00:01, r-r-r-, uint8, 8 bit, "SubIndex 001"
0x1c00:02, r-r-r-, uint8, 8 bit, "SubIndex 002"
0x1c00:03, r-r-r-, uint8, 8 bit, "SubIndex 003"
0x1c00:04, r-r-r-, uint8, 8 bit, "SubIndex 004"
SDO 0x1c12, "SyncManager 2 assignment"
0x1c12:00, r-r-r-, uint8, 8 bit, "SubIndex 000"
0x1c12:01, r-r-r-, uint16, 16 bit, "SubIndex 001"
SDO 0x1c13, "SyncManager 3 assignment"
0x1c13:00, r-r-r-, uint8, 8 bit, "SubIndex 000"
0x1c13:01, r-r-r-, uint16, 16 bit, "SubIndex 001"
SDO 0x1c32, "SM output parameter"
0x1c32:00, r-r-r-, uint8, 8 bit, "SubIndex 000"
0x1c32:01, rwr-r-, uint16, 16 bit, "Synchronization Type"
0x1c32:02, r-r-r-, uint32, 32 bit, "Cycle Time"
0x1c32:03,
, type 0000, 32 bit, "SubIndex 003"
0x1c32:04, r-r-r-, uint16, 16 bit, "Synchronization Types supported"
0x1c32:05, r-r-r-, uint32, 32 bit, "Minimum Cycle Time"
0x1c32:06, r-r-r-, uint32, 32 bit, "Calc and Copy Time"
0x1c32:07,
, type 0000, 32 bit, "SubIndex 007"
0x1c32:08, rwrwrw, uint16, 16 bit, "Get Cycle Time"
0x1c32:09, r-r-r-, uint32, 32 bit, "Delay Time"
0x1c32:0a, rwrwrw, uint32, 32 bit, "Sync0 Cycle Time"
0x1c32:0b, r-r-r-, uint16, 16 bit, "SM-Event Missed"
0x1c32:0c, r-r-r-, uint16, 16 bit, "Cycle Time Too Small"
0x1c32:0d,
, type 0000, 16 bit, "Shift Time Too Short"
0x1c32:0e,
, type 0000, 16 bit, "SubIndex 014"
0x1c32:0f,
, type 0000, 32 bit, "SubIndex 015"
Also, I have noticed that they do not present any pdo data at all. I do have the .xml file which the manufacturer supplies if that is any use.
Looking through the forum, I understand that if no pdo values are given, it can only be fixed by writing/compiling a driver. however the link which is given on how to do this is broken.
Is there anyone who could point me in the right direction on how to solve this? I'm not a Linux expert, but can usually figure things out in the end (given lots of time and reading) and if I can get this working will post the files back to the forum so others may be able to use this option.
Thanks for any help
Steve.
Currently working on another small project, which has one servo motor and a bunch of I/O. I had knocking around in my goodies cupboard a Odot CN-8033 coupler and a CT-121F 16 input card and CT-222F 16 output card. These look very much the same as the Beckoff equivalents, they are very cheap (about a third the cost) and it would be nice to use these.
When plugging these in they are seen by the network, however the ID is very strange.
steve@linuxcnc:~$ ethercat slaves
0 0:0 PREOP + RS750E(COE)
1 1:0 PREOP + 0x00860816:0x20008033
Plenty of information is received if the sdo is checked, here is a small sample:
steve@linuxcnc:~$ ethercat sdos -p1
SDO 0x1000, "Device type"
0x1000:00, r-r-r-, uint32, 32 bit, "Device type"
SDO 0x1001, "Error register"
0x1001:00, r-r-r-, uint8, 8 bit, "Error register"
SDO 0x1008, "Device name"
0x1008:00, r-r-r-, string, 160 bit, "Device name"
SDO 0x1009, "Hardware version"
0x1009:00, r-r-r-, string, 24 bit, "Hardware version"
SDO 0x100a, "Software version"
0x100a:00, r-r-r-, string, 24 bit, "Software version"
SDO 0x1018, "Identity"
0x1018:00, r-r-r-, uint8, 8 bit, "SubIndex 000"
0x1018:01, r-r-r-, uint32, 32 bit, "Vendor ID"
0x1018:02, r-r-r-, uint32, 32 bit, "Product code"
0x1018:03, r-r-r-, uint32, 32 bit, "Revision"
0x1018:04, r-r-r-, uint32, 32 bit, "Serial number"
SDO 0x10f1, "Error Settings"
0x10f1:00, r-r-r-, uint8, 8 bit, "SubIndex 000"
0x10f1:01, rwrwrw, uint32, 32 bit, "Local Error Reaction"
0x10f1:02, rwrwrw, uint16, 16 bit, "Sync Error Counter Limit"
SDO 0x10f8, "Timestamp Object"
0x10f8:00, rwrwrw, uint64, 64 bit, "Timestamp Object"
SDO 0x1600, "CT-222F"
0x1600:00, r-r-r-, uint8, 8 bit, "SubIndex 000"
0x1600:01, r-r-r-, uint32, 32 bit, "SubIndex 001"
SDO 0x1a00, "CT-121F"
0x1a00:00, r-r-r-, uint8, 8 bit, "SubIndex 000"
0x1a00:01, r-r-r-, uint32, 32 bit, "SubIndex 001"
SDO 0x1c00, "Sync manager type"
0x1c00:00, r-r-r-, uint8, 8 bit, "SubIndex 000"
0x1c00:01, r-r-r-, uint8, 8 bit, "SubIndex 001"
0x1c00:02, r-r-r-, uint8, 8 bit, "SubIndex 002"
0x1c00:03, r-r-r-, uint8, 8 bit, "SubIndex 003"
0x1c00:04, r-r-r-, uint8, 8 bit, "SubIndex 004"
SDO 0x1c12, "SyncManager 2 assignment"
0x1c12:00, r-r-r-, uint8, 8 bit, "SubIndex 000"
0x1c12:01, r-r-r-, uint16, 16 bit, "SubIndex 001"
SDO 0x1c13, "SyncManager 3 assignment"
0x1c13:00, r-r-r-, uint8, 8 bit, "SubIndex 000"
0x1c13:01, r-r-r-, uint16, 16 bit, "SubIndex 001"
SDO 0x1c32, "SM output parameter"
0x1c32:00, r-r-r-, uint8, 8 bit, "SubIndex 000"
0x1c32:01, rwr-r-, uint16, 16 bit, "Synchronization Type"
0x1c32:02, r-r-r-, uint32, 32 bit, "Cycle Time"
0x1c32:03,
, type 0000, 32 bit, "SubIndex 003"
0x1c32:04, r-r-r-, uint16, 16 bit, "Synchronization Types supported"
0x1c32:05, r-r-r-, uint32, 32 bit, "Minimum Cycle Time"
0x1c32:06, r-r-r-, uint32, 32 bit, "Calc and Copy Time"
0x1c32:07,
, type 0000, 32 bit, "SubIndex 007"
0x1c32:08, rwrwrw, uint16, 16 bit, "Get Cycle Time"
0x1c32:09, r-r-r-, uint32, 32 bit, "Delay Time"
0x1c32:0a, rwrwrw, uint32, 32 bit, "Sync0 Cycle Time"
0x1c32:0b, r-r-r-, uint16, 16 bit, "SM-Event Missed"
0x1c32:0c, r-r-r-, uint16, 16 bit, "Cycle Time Too Small"
0x1c32:0d,
, type 0000, 16 bit, "Shift Time Too Short"
0x1c32:0e,
, type 0000, 16 bit, "SubIndex 014"
0x1c32:0f,
, type 0000, 32 bit, "SubIndex 015"
Also, I have noticed that they do not present any pdo data at all. I do have the .xml file which the manufacturer supplies if that is any use.
Looking through the forum, I understand that if no pdo values are given, it can only be fixed by writing/compiling a driver. however the link which is given on how to do this is broken.
Is there anyone who could point me in the right direction on how to solve this? I'm not a Linux expert, but can usually figure things out in the end (given lots of time and reading) and if I can get this working will post the files back to the forum so others may be able to use this option.
Thanks for any help
Steve.
Please Log in or Create an account to join the conversation.
- isulistiawan
-
- Offline
- New Member
-
Less
More
- Posts: 3
- Thank you received: 0
04 Sep 2024 05:19 #309328
by isulistiawan
Replied by isulistiawan on topic Use of ODOT Ethercat coupler I/O?
I have same problem with odot......i'm using CN-8033 CT-122F CT-222F CT-5142
Please Log in or Create an account to join the conversation.
- onceloved
-
- Offline
- Premium Member
-
Less
More
- Posts: 121
- Thank you received: 58
04 Sep 2024 05:48 #309332
by onceloved
Replied by onceloved on topic Use of ODOT Ethercat coupler I/O?
Can I take a look at it? Using remote assistance, what is your contact information?
Please Log in or Create an account to join the conversation.
- onceloved
-
- Offline
- Premium Member
-
Less
More
- Posts: 121
- Thank you received: 58
04 Sep 2024 05:55 #309334
by onceloved
Replied by onceloved on topic Use of ODOT Ethercat coupler I/O?
I saw they have io configuration software you can try www.odot.com.cn/upload/20240530/4fed8860...15e94cbc23e106fd.exe
Please Log in or Create an account to join the conversation.
- ts
- Offline
- New Member
-
Less
More
- Posts: 9
- Thank you received: 0
22 Aug 2025 12:59 - 23 Aug 2025 14:34 #333773
by ts
Replied by ts on topic Use of ODOT Ethercat coupler I/O?
Hi
Is your modules state PreOp or you switch them to OPstate?
Please could you share your xml files for linixcnc?
Ps working on the same task, try to connect odot 8033 with linixcnc 2.9.4 as i understood oncase of beckhoff each module - coupler, di, next on di, do, next one do, ai - each have own id in ethercat network. But as in case of odot, perhaps, only coupler have own address ethercat, other modules using special address register according position from the coupler.
Is your modules state PreOp or you switch them to OPstate?
Please could you share your xml files for linixcnc?
Ps working on the same task, try to connect odot 8033 with linixcnc 2.9.4 as i understood oncase of beckhoff each module - coupler, di, next on di, do, next one do, ai - each have own id in ethercat network. But as in case of odot, perhaps, only coupler have own address ethercat, other modules using special address register according position from the coupler.
Last edit: 23 Aug 2025 14:34 by ts.
Please Log in or Create an account to join the conversation.
- ts
- Offline
- New Member
-
Less
More
- Posts: 9
- Thank you received: 0
23 Aug 2025 14:33 - 23 Aug 2025 14:36 #333801
by ts
Replied by ts on topic Use of ODOT Ethercat coupler I/O?
Hi
Today i made few experiments. I put only one coupler 8033 on network, and one module odot ct222F, and one End module odot 5801. After that - ethercat slaves - show me one node in network and its have state PreOP +. Next step was starting configuration with this module - it was an axis plus lcec cia402. Starting was without.alarm or warnings or any errors. But during active axis program, command ethercat slaves in terminal show me PreOp E, that means Error. Btw on the display there are was no errors. Ok, next step - exit shutdown axis configuration linuxcnc. And reboot PC. After reboot - run: ethercat slaves, shows answer PreOP +, and ethercat state -p0 OP , next "ethercat slaves" shows PreOP E. Ok, next step put another equip in to the configuration. Foe example delta asda b3-e (asdress in ethercat network 1). And after command switch p1 in OP state - slaves command show that Delta in OP state... So, looks like we didn't do some extra initialisation procedure... Does anyone have some ideas?)
Best regards,
Alexander
Today i made few experiments. I put only one coupler 8033 on network, and one module odot ct222F, and one End module odot 5801. After that - ethercat slaves - show me one node in network and its have state PreOP +. Next step was starting configuration with this module - it was an axis plus lcec cia402. Starting was without.alarm or warnings or any errors. But during active axis program, command ethercat slaves in terminal show me PreOp E, that means Error. Btw on the display there are was no errors. Ok, next step - exit shutdown axis configuration linuxcnc. And reboot PC. After reboot - run: ethercat slaves, shows answer PreOP +, and ethercat state -p0 OP , next "ethercat slaves" shows PreOP E. Ok, next step put another equip in to the configuration. Foe example delta asda b3-e (asdress in ethercat network 1). And after command switch p1 in OP state - slaves command show that Delta in OP state... So, looks like we didn't do some extra initialisation procedure... Does anyone have some ideas?)
Best regards,
Alexander
Last edit: 23 Aug 2025 14:36 by ts.
Please Log in or Create an account to join the conversation.
- Hakan
- Offline
- Platinum Member
-
Less
More
- Posts: 814
- Thank you received: 282
23 Aug 2025 18:30 #333821
by Hakan
Replied by Hakan on topic Use of ODOT Ethercat coupler I/O?
When the slave is in PreOP, use the command "lcec_configgen" to get a list pf PDOs if there are any.
Try with the output from lcec_configgen as your ethercat-config.xml. Normally a good starting point, may need to editing.
You can normally not manually switch to state OP, this is done by the lcec component when linuxcnc runs.
The command "sudo dmesg | tail -30" should give you the 30 last messages, the reason for the "E" is there.
30 is an example to keep the listing short.
To sum up. Get yourself an ethercat-conf.xml from lcec_configgen, start linuxcnc and if you get errors, check the output from linuxcnc and from "sudo dmesg".
Try with the output from lcec_configgen as your ethercat-config.xml. Normally a good starting point, may need to editing.
You can normally not manually switch to state OP, this is done by the lcec component when linuxcnc runs.
The command "sudo dmesg | tail -30" should give you the 30 last messages, the reason for the "E" is there.
30 is an example to keep the listing short.
To sum up. Get yourself an ethercat-conf.xml from lcec_configgen, start linuxcnc and if you get errors, check the output from linuxcnc and from "sudo dmesg".
The following user(s) said Thank You: ts
Please Log in or Create an account to join the conversation.
- ts
- Offline
- New Member
-
Less
More
- Posts: 9
- Thank you received: 0
24 Aug 2025 18:53 - 24 Aug 2025 18:54 #333867
by ts
Replied by ts on topic Use of ODOT Ethercat coupler I/O?
Hi, Hakan!
Good points to check. Will do tomorrow
Also i first of all tryed to start from PreOP from started linuxcnc, but slaves command show me an error state..so i try to do switch To OP state manually.
So i build xml from xml odot file from their site, and also from ethercat sdos -p0 command.
Also thos evening im asked for deep seek about this problem, and also received some recommendations)) which also will check tomorrow and will write here about it.
Good points to check. Will do tomorrow
Also i first of all tryed to start from PreOP from started linuxcnc, but slaves command show me an error state..so i try to do switch To OP state manually.
So i build xml from xml odot file from their site, and also from ethercat sdos -p0 command.
Also thos evening im asked for deep seek about this problem, and also received some recommendations)) which also will check tomorrow and will write here about it.
Last edit: 24 Aug 2025 18:54 by ts.
Please Log in or Create an account to join the conversation.
- ts
- Offline
- New Member
-
Less
More
- Posts: 9
- Thank you received: 0
25 Aug 2025 05:36 - 25 Aug 2025 06:05 #333884
by ts
Replied by ts on topic Use of ODOT Ethercat coupler I/O?
dmesg says:
[ 42.224233] EtherCAT ERROR 0-0: Failed to set SAFEOP state, slave refused state change (PREOP + ERROR).
[ 42.224475] EtherCAT ERROR 0-0: AL status message 0x001D: "Invalid output configuration".
[ 42.226186] EtherCAT 0-0: Acknowledged state PREOP.
additional information listing of sdos command - i have only coupler and ct222f module (16 do):
[ 42.224233] EtherCAT ERROR 0-0: Failed to set SAFEOP state, slave refused state change (PREOP + ERROR).
[ 42.224475] EtherCAT ERROR 0-0: AL status message 0x001D: "Invalid output configuration".
[ 42.226186] EtherCAT 0-0: Acknowledged state PREOP.
additional information listing of sdos command - i have only coupler and ct222f module (16 do):
r@LCNC2:~$ ethercat sdos
SDO 0x1000, "Device type"
0x1000:00, r-r-r-, uint32, 32 bit, "Device type"
SDO 0x1001, "Error register"
0x1001:00, r-r-r-, uint8, 8 bit, "Error register"
SDO 0x1008, "Device name"
0x1008:00, r-r-r-, string, 256 bit, "Device name"
SDO 0x1009, "Hardware version"
0x1009:00, r-r-r-, string, 24 bit, "Hardware version"
SDO 0x100a, "Software version"
0x100a:00, r-r-r-, string, 24 bit, "Software version"
SDO 0x1018, "Identity"
0x1018:00, r-r-r-, uint8, 8 bit, "SubIndex 000"
0x1018:01, r-r-r-, uint32, 32 bit, "Vendor ID"
0x1018:02, r-r-r-, uint32, 32 bit, "Product code"
0x1018:03, r-r-r-, uint32, 32 bit, "Revision"
0x1018:04, r-r-r-, uint32, 32 bit, "Serial number"
SDO 0x10f1, "Error Settings"
0x10f1:00, r-r-r-, uint8, 8 bit, "SubIndex 000"
0x10f1:01, rwrwrw, uint32, 32 bit, "Local Error Reaction"
0x10f1:02, rwrwrw, uint16, 16 bit, "Sync Error Counter Limit"
SDO 0x10f8, "Timestamp Object"
0x10f8:00, rwrwrw, uint64, 64 bit, "Timestamp Object"
SDO 0x1600, "CT-222F"
0x1600:00, r-r-r-, uint8, 8 bit, "SubIndex 000"
0x1600:01, r-r-r-, uint32, 32 bit, "SubIndex 001"
SDO 0x1c00, "Sync manager type"
0x1c00:00, r-r-r-, uint8, 8 bit, "SubIndex 000"
0x1c00:01, r-r-r-, uint8, 8 bit, "SubIndex 001"
0x1c00:02, r-r-r-, uint8, 8 bit, "SubIndex 002"
0x1c00:03, r-r-r-, uint8, 8 bit, "SubIndex 003"
0x1c00:04, r-r-r-, uint8, 8 bit, "SubIndex 004"
SDO 0x1c12, "SyncManager 2 assignment"
0x1c12:00, r-r-r-, uint8, 8 bit, "SubIndex 000"
0x1c12:01, r-r-r-, uint16, 16 bit, "SubIndex 001"
SDO 0x1c13, "SyncManager 3 assignment"
0x1c13:00, r-r-r-, uint8, 8 bit, "SubIndex 000"
0x1c13:01, r-r-r-, uint16, 16 bit, "SubIndex 001"
SDO 0x1c32, "SM output parameter"
0x1c32:00, r-r-r-, uint8, 8 bit, "SubIndex 000"
0x1c32:01, rwr-r-, uint16, 16 bit, "Synchronization Type"
0x1c32:02, r-r-r-, uint32, 32 bit, "Cycle Time"
0x1c32:03, ------, type 0000, 32 bit, "SubIndex 003"
0x1c32:04, r-r-r-, uint16, 16 bit, "Synchronization Types supported"
0x1c32:05, r-r-r-, uint32, 32 bit, "Minimum Cycle Time"
0x1c32:06, r-r-r-, uint32, 32 bit, "Calc and Copy Time"
0x1c32:07, ------, type 0000, 32 bit, "SubIndex 007"
0x1c32:08, rwrwrw, uint16, 16 bit, "Get Cycle Time"
0x1c32:09, r-r-r-, uint32, 32 bit, "Delay Time"
0x1c32:0a, rwrwrw, uint32, 32 bit, "Sync0 Cycle Time"
0x1c32:0b, r-r-r-, uint16, 16 bit, "SM-Event Missed"
0x1c32:0c, r-r-r-, uint16, 16 bit, "Cycle Time Too Small"
0x1c32:0d, ------, type 0000, 16 bit, "Shift Time Too Short"
0x1c32:0e, ------, type 0000, 16 bit, "SubIndex 014"
0x1c32:0f, ------, type 0000, 32 bit, "SubIndex 015"
0x1c32:10, ------, type 0000, 32 bit, "SubIndex 016"
0x1c32:11, ------, type 0000, 32 bit, "SubIndex 017"
0x1c32:12, ------, type 0000, 32 bit, "SubIndex 018"
0x1c32:13, ------, type 0000, 0 bit, "SubIndex 019"
0x1c32:14, ------, type 0000, 0 bit, "SubIndex 020"
0x1c32:15, ------, type 0000, 0 bit, "SubIndex 021"
0x1c32:16, ------, type 0000, 0 bit, "SubIndex 022"
0x1c32:17, ------, type 0000, 0 bit, "SubIndex 023"
0x1c32:18, ------, type 0000, 0 bit, "SubIndex 024"
0x1c32:19, ------, type 0000, 0 bit, "SubIndex 025"
0x1c32:1a, ------, type 0000, 0 bit, "SubIndex 026"
0x1c32:1b, ------, type 0000, 0 bit, "SubIndex 027"
0x1c32:1c, ------, type 0000, 0 bit, "SubIndex 028"
0x1c32:1d, ------, type 0000, 0 bit, "SubIndex 029"
0x1c32:1e, ------, type 0000, 0 bit, "SubIndex 030"
0x1c32:1f, ------, type 0000, 0 bit, "SubIndex 031"
0x1c32:20, r-r-r-, bool, 1 bit, "Sync Error"
SDO 0x1c33, "SM input parameter"
0x1c33:00, r-r-r-, uint8, 8 bit, "SubIndex 000"
0x1c33:01, rwr-r-, uint16, 16 bit, "Synchronization Type"
0x1c33:02, r-r-r-, uint32, 32 bit, "Cycle Time"
0x1c33:03, ------, type 0000, 32 bit, "SubIndex 003"
0x1c33:04, r-r-r-, uint16, 16 bit, "Synchronization Types supported"
0x1c33:05, r-r-r-, uint32, 32 bit, "Minimum Cycle Time"
0x1c33:06, r-r-r-, uint32, 32 bit, "Calc and Copy Time"
0x1c33:07, ------, type 0000, 32 bit, "SubIndex 007"
0x1c33:08, rwrwrw, uint16, 16 bit, "Get Cycle Time"
0x1c33:09, r-r-r-, uint32, 32 bit, "Delay Time"
0x1c33:0a, rwrwrw, uint32, 32 bit, "Sync0 Cycle Time"
0x1c33:0b, r-r-r-, uint16, 16 bit, "SM-Event Missed"
0x1c33:0c, r-r-r-, uint16, 16 bit, "Cycle Time Too Small"
0x1c33:0d, ------, type 0000, 16 bit, "Shift Time Too Short"
0x1c33:0e, ------, type 0000, 16 bit, "SubIndex 014"
0x1c33:0f, ------, type 0000, 32 bit, "SubIndex 015"
0x1c33:10, ------, type 0000, 32 bit, "SubIndex 016"
0x1c33:11, ------, type 0000, 32 bit, "SubIndex 017"
0x1c33:12, ------, type 0000, 32 bit, "SubIndex 018"
0x1c33:13, ------, type 0000, 0 bit, "SubIndex 019"
0x1c33:14, ------, type 0000, 0 bit, "SubIndex 020"
0x1c33:15, ------, type 0000, 0 bit, "SubIndex 021"
0x1c33:16, ------, type 0000, 0 bit, "SubIndex 022"
0x1c33:17, ------, type 0000, 0 bit, "SubIndex 023"
0x1c33:18, ------, type 0000, 0 bit, "SubIndex 024"
0x1c33:19, ------, type 0000, 0 bit, "SubIndex 025"
0x1c33:1a, ------, type 0000, 0 bit, "SubIndex 026"
0x1c33:1b, ------, type 0000, 0 bit, "SubIndex 027"
0x1c33:1c, ------, type 0000, 0 bit, "SubIndex 028"
0x1c33:1d, ------, type 0000, 0 bit, "SubIndex 029"
0x1c33:1e, ------, type 0000, 0 bit, "SubIndex 030"
0x1c33:1f, ------, type 0000, 0 bit, "SubIndex 031"
0x1c33:20, r-r-r-, bool, 1 bit, "Sync Error"
SDO 0x2000, "ConfigurationParameter"
0x2000:00, r-r-r-, uint8, 8 bit, "SubIndex 000"
0x2000:01, rwr-r-, type 0030, 1 bit, "SourceOfConfiguration"
0x2000:02, rwr-r-, type 0030, 1 bit, "InputFaultAction"
0x2000:03, rwr-r-, type 0030, 1 bit, "OutputFaultAction"
0x2000:04, rwr-r-, type 0030, 1 bit, "DiagnosticFunctionEnable"
SDO 0x7000, ""
0x7000:00, r-r-r-, uint8, 8 bit, "SubIndex 000"
0x7000:01, rwrwrw, uint32, 32 bit, "SubIndex 001"
SDO 0xf000, "Module device profile"
0xf000:00, r-r-r-, uint8, 8 bit, "SubIndex 000"
0xf000:01, r-r-r-, uint16, 16 bit, "Index distance"
0xf000:02, r-r-r-, uint16, 16 bit, "maximum number of modules"
SDO 0xf010, "Module Profile List"
0xf010:00, r-r-r-, uint8, 8 bit, "SubIndex 000"
0xf010:01, r-r-r-, uint32, 32 bit, "SubIndex 001"
0xf010:02, r-r-r-, uint32, 32 bit, "SubIndex 002"
0xf010:03, r-r-r-, uint32, 32 bit, "SubIndex 003"
0xf010:04, r-r-r-, uint32, 32 bit, "SubIndex 004"
0xf010:05, r-r-r-, uint32, 32 bit, "SubIndex 005"
0xf010:06, r-r-r-, uint32, 32 bit, "SubIndex 006"
0xf010:07, r-r-r-, uint32, 32 bit, "SubIndex 007"
0xf010:08, r-r-r-, uint32, 32 bit, "SubIndex 008"
0xf010:09, r-r-r-, uint32, 32 bit, "SubIndex 009"
0xf010:0a, r-r-r-, uint32, 32 bit, "SubIndex 010"
0xf010:0b, r-r-r-, uint32, 32 bit, "SubIndex 011"
0xf010:0c, r-r-r-, uint32, 32 bit, "SubIndex 012"
0xf010:0d, r-r-r-, uint32, 32 bit, "SubIndex 013"
0xf010:0e, r-r-r-, uint32, 32 bit, "SubIndex 014"
0xf010:0f, r-r-r-, uint32, 32 bit, "SubIndex 015"
0xf010:10, r-r-r-, uint32, 32 bit, "SubIndex 016"
0xf010:11, r-r-r-, uint32, 32 bit, "SubIndex 017"
0xf010:12, r-r-r-, uint32, 32 bit, "SubIndex 018"
0xf010:13, r-r-r-, uint32, 32 bit, "SubIndex 019"
0xf010:14, r-r-r-, uint32, 32 bit, "SubIndex 020"
0xf010:15, r-r-r-, uint32, 32 bit, "SubIndex 021"
0xf010:16, r-r-r-, uint32, 32 bit, "SubIndex 022"
0xf010:17, r-r-r-, uint32, 32 bit, "SubIndex 023"
0xf010:18, r-r-r-, uint32, 32 bit, "SubIndex 024"
0xf010:19, r-r-r-, uint32, 32 bit, "SubIndex 025"
0xf010:1a, r-r-r-, uint32, 32 bit, "SubIndex 026"
0xf010:1b, r-r-r-, uint32, 32 bit, "SubIndex 027"
0xf010:1c, r-r-r-, uint32, 32 bit, "SubIndex 028"
0xf010:1d, r-r-r-, uint32, 32 bit, "SubIndex 029"
0xf010:1e, r-r-r-, uint32, 32 bit, "SubIndex 030"
0xf010:1f, r-r-r-, uint32, 32 bit, "SubIndex 031"
0xf010:20, r-r-r-, uint32, 32 bit, "SubIndex 032"
0xf010:21, r-r-r-, uint32, 32 bit, "SubIndex 033"
0xf010:22, r-r-r-, uint32, 32 bit, "SubIndex 034"
0xf010:23, r-r-r-, uint32, 32 bit, "SubIndex 035"
0xf010:24, r-r-r-, uint32, 32 bit, "SubIndex 036"
0xf010:25, r-r-r-, uint32, 32 bit, "SubIndex 037"
0xf010:26, r-r-r-, uint32, 32 bit, "SubIndex 038"
0xf010:27, r-r-r-, uint32, 32 bit, "SubIndex 039"
0xf010:28, r-r-r-, uint32, 32 bit, "SubIndex 040"
0xf010:29, r-r-r-, uint32, 32 bit, "SubIndex 041"
0xf010:2a, r-r-r-, uint32, 32 bit, "SubIndex 042"
0xf010:2b, r-r-r-, uint32, 32 bit, "SubIndex 043"
0xf010:2c, r-r-r-, uint32, 32 bit, "SubIndex 044"
0xf010:2d, r-r-r-, uint32, 32 bit, "SubIndex 045"
0xf010:2e, r-r-r-, uint32, 32 bit, "SubIndex 046"
0xf010:2f, r-r-r-, uint32, 32 bit, "SubIndex 047"
0xf010:30, r-r-r-, uint32, 32 bit, "SubIndex 048"
0xf010:31, r-r-r-, uint32, 32 bit, "SubIndex 049"
0xf010:32, r-r-r-, uint32, 32 bit, "SubIndex 050"
0xf010:33, r-r-r-, uint32, 32 bit, "SubIndex 051"
0xf010:34, r-r-r-, uint32, 32 bit, "SubIndex 052"
0xf010:35, r-r-r-, uint32, 32 bit, "SubIndex 053"
0xf010:36, r-r-r-, uint32, 32 bit, "SubIndex 054"
0xf010:37, r-r-r-, uint32, 32 bit, "SubIndex 055"
0xf010:38, r-r-r-, uint32, 32 bit, "SubIndex 056"
0xf010:39, r-r-r-, uint32, 32 bit, "SubIndex 057"
0xf010:3a, r-r-r-, uint32, 32 bit, "SubIndex 058"
0xf010:3b, r-r-r-, uint32, 32 bit, "SubIndex 059"
0xf010:3c, r-r-r-, uint32, 32 bit, "SubIndex 060"
0xf010:3d, r-r-r-, uint32, 32 bit, "SubIndex 061"
0xf010:3e, r-r-r-, uint32, 32 bit, "SubIndex 062"
0xf010:3f, r-r-r-, uint32, 32 bit, "SubIndex 063"
0xf010:40, r-r-r-, uint32, 32 bit, "SubIndex 064"
0xf010:41, r-r-r-, uint32, 32 bit, "SubIndex 065"
SDO 0xf050, "Detected Module Ident List"
0xf050:00, r-r-r-, uint8, 8 bit, "SubIndex 000"
0xf050:01, r-r-r-, uint32, 32 bit, "SubIndex 001"
0xf050:02, r-r-r-, uint32, 32 bit, "SubIndex 002"
0xf050:03, r-r-r-, uint32, 32 bit, "SubIndex 003"
0xf050:04, r-r-r-, uint32, 32 bit, "SubIndex 004"
0xf050:05, r-r-r-, uint32, 32 bit, "SubIndex 005"
0xf050:06, r-r-r-, uint32, 32 bit, "SubIndex 006"
0xf050:07, r-r-r-, uint32, 32 bit, "SubIndex 007"
0xf050:08, r-r-r-, uint32, 32 bit, "SubIndex 008"
0xf050:09, r-r-r-, uint32, 32 bit, "SubIndex 009"
0xf050:0a, r-r-r-, uint32, 32 bit, "SubIndex 010"
0xf050:0b, r-r-r-, uint32, 32 bit, "SubIndex 011"
0xf050:0c, r-r-r-, uint32, 32 bit, "SubIndex 012"
0xf050:0d, r-r-r-, uint32, 32 bit, "SubIndex 013"
0xf050:0e, r-r-r-, uint32, 32 bit, "SubIndex 014"
0xf050:0f, r-r-r-, uint32, 32 bit, "SubIndex 015"
0xf050:10, r-r-r-, uint32, 32 bit, "SubIndex 016"
0xf050:11, r-r-r-, uint32, 32 bit, "SubIndex 017"
0xf050:12, r-r-r-, uint32, 32 bit, "SubIndex 018"
0xf050:13, r-r-r-, uint32, 32 bit, "SubIndex 019"
0xf050:14, r-r-r-, uint32, 32 bit, "SubIndex 020"
0xf050:15, r-r-r-, uint32, 32 bit, "SubIndex 021"
0xf050:16, r-r-r-, uint32, 32 bit, "SubIndex 022"
0xf050:17, r-r-r-, uint32, 32 bit, "SubIndex 023"
0xf050:18, r-r-r-, uint32, 32 bit, "SubIndex 024"
0xf050:19, r-r-r-, uint32, 32 bit, "SubIndex 025"
0xf050:1a, r-r-r-, uint32, 32 bit, "SubIndex 026"
0xf050:1b, r-r-r-, uint32, 32 bit, "SubIndex 027"
0xf050:1c, r-r-r-, uint32, 32 bit, "SubIndex 028"
0xf050:1d, r-r-r-, uint32, 32 bit, "SubIndex 029"
0xf050:1e, r-r-r-, uint32, 32 bit, "SubIndex 030"
0xf050:1f, r-r-r-, uint32, 32 bit, "SubIndex 031"
0xf050:20, r-r-r-, uint32, 32 bit, "SubIndex 032"
0xf050:21, r-r-r-, uint32, 32 bit, "SubIndex 033"
0xf050:22, r-r-r-, uint32, 32 bit, "SubIndex 034"
0xf050:23, r-r-r-, uint32, 32 bit, "SubIndex 035"
0xf050:24, r-r-r-, uint32, 32 bit, "SubIndex 036"
0xf050:25, r-r-r-, uint32, 32 bit, "SubIndex 037"
0xf050:26, r-r-r-, uint32, 32 bit, "SubIndex 038"
0xf050:27, r-r-r-, uint32, 32 bit, "SubIndex 039"
0xf050:28, r-r-r-, uint32, 32 bit, "SubIndex 040"
0xf050:29, r-r-r-, uint32, 32 bit, "SubIndex 041"
0xf050:2a, r-r-r-, uint32, 32 bit, "SubIndex 042"
0xf050:2b, r-r-r-, uint32, 32 bit, "SubIndex 043"
0xf050:2c, r-r-r-, uint32, 32 bit, "SubIndex 044"
0xf050:2d, r-r-r-, uint32, 32 bit, "SubIndex 045"
0xf050:2e, r-r-r-, uint32, 32 bit, "SubIndex 046"
0xf050:2f, r-r-r-, uint32, 32 bit, "SubIndex 047"
0xf050:30, r-r-r-, uint32, 32 bit, "SubIndex 048"
0xf050:31, r-r-r-, uint32, 32 bit, "SubIndex 049"
0xf050:32, r-r-r-, uint32, 32 bit, "SubIndex 050"
0xf050:33, r-r-r-, uint32, 32 bit, "SubIndex 051"
0xf050:34, r-r-r-, uint32, 32 bit, "SubIndex 052"
0xf050:35, r-r-r-, uint32, 32 bit, "SubIndex 053"
0xf050:36, r-r-r-, uint32, 32 bit, "SubIndex 054"
0xf050:37, r-r-r-, uint32, 32 bit, "SubIndex 055"
0xf050:38, r-r-r-, uint32, 32 bit, "SubIndex 056"
0xf050:39, r-r-r-, uint32, 32 bit, "SubIndex 057"
0xf050:3a, r-r-r-, uint32, 32 bit, "SubIndex 058"
0xf050:3b, r-r-r-, uint32, 32 bit, "SubIndex 059"
0xf050:3c, r-r-r-, uint32, 32 bit, "SubIndex 060"
0xf050:3d, r-r-r-, uint32, 32 bit, "SubIndex 061"
0xf050:3e, r-r-r-, uint32, 32 bit, "SubIndex 062"
0xf050:3f, r-r-r-, uint32, 32 bit, "SubIndex 063"
0xf050:40, r-r-r-, uint32, 32 bit, "SubIndex 064"
0xf050:41, r-r-r-, uint32, 32 bit, "SubIndex 065"
Last edit: 25 Aug 2025 06:05 by ts.
Please Log in or Create an account to join the conversation.
- Hakan
- Offline
- Platinum Member
-
Less
More
- Posts: 814
- Thank you received: 282
25 Aug 2025 06:16 #333885
by Hakan
Replied by Hakan on topic Use of ODOT Ethercat coupler I/O?
Output of lcec_configgen?
The following user(s) said Thank You: ts
Please Log in or Create an account to join the conversation.
Time to create page: 0.141 seconds