Hi,
Maybe I've not yet understood precisely what you need, correct me if I'm
wrong.
Every configuration SDO sent via ecrt_slave_config_complete_sdo is meant
as and SDO addressed to the EL6751 and the only use is to configure the
EL6751 or Can configuration telegrams to the Can slaves, allowed
Thank you Thomas for sharing your code :) In my code I'm doing almost the
same, except that I do encode the configuration bytes directly in an array
instead of converting it from a string.
Also I do not have to configure CANOpen-Slaves. The only slave listening on
the CAN-Bus expects "raw"(Layer2)
Thank you for your response, Gavin. I'm pretty sure that the device
supports complete access. It is stated in the documentation, that either I
can use complete access or "consistency nesting" for configuration
purposes. I derived the object layout directly from the Twincat SDO-Startup
tab for that
Hi,
Sometimes a piece of code is better than explanations ...
Here is mine, which configures the PDO of the CanOpen side on my EL6731
static int err_code;
static int cnt;
static int x, y, z, i, num_config_lines;
static char app_str[1024];
static unsigned char pb_config_buf[2048];
static int ecrt
It’s hard to say without seeing what specific commands you’re trying to run.
ecrt_master_sdo_download* is intended for one-off synchronous transfers before
starting the realtime loop, eg. for cases where you’re trying to interrogate
the device or otherwise do out-of-band exchanges. (You can
