Use of ODOT Ethercat coupler I/O?

More
04 Jul 2023 08:28 #274729 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.
 

Please Log in or Create an account to join the conversation.

Time to create page: 0.342 seconds
Powered by Kunena Forum