Hi CoDeSys! Another question about CANOpen Device Stack. Is Expedited, Segmented or Block SDO transfer mode supported on stack level? I need to transfer large portion of data between two PLCs over CAN using SDOs and could not find any suitable solution...
Hi eschwellinger! Thank you for reply, I always use method described above. I am using IFM CR710S combined Standard/Safety PLC and this code sits on Safety PLC side. I think the problem is that safe retain GVL, safe PLC_PRG, non-safe PLC_PRGs and CANOpen Slave Device stack on Safety PLC have either different starting sequences OR non-safe PRG (to which I am only allowed to map CANOpen Slave Device variables) are randomly "floating" within task time because safe data processing takes highest priority....
GDay guys! I'm playing with CANOpen Slave Device in CoDeSys 3.5.11.0 and trying to achieve behaviour of any off-the-shelf CANOpen slave device (encoder, inclinometer, etc...) inside CoDeSys, particularly with SDOs. Usually then you use any CANOpen configuration software (e.g. IFM Maintenance) to change SDO parameter of any CANOpen slave, the change is either automatically retained OR you should write "SAVE" string to 0x1010h and power cycle device. Unfortunately I could not achieve similar behaviour...
GDay guys! I'm playing with CANOpen Slave Device in CoDeSys 3.5.11.0 and trying to achieve behaviour of any off-the-shelf CANOpen slave device (encoder, inclinometer, etc...) inside CoDeSys, particularly with SDOs. Usually then you use any CANOpen configuration software (e.g. IFM Maintenance) to change SDO parameter of any CANOpen slave, the change is either automatically retained OR you should write "SAVE" string to 0x1010h and power cycle device. Unfortunately I could not achieve similar behaviour...
GDay guys! I'm playing with CANOpen Slave Device in CoDeSys 3.5.11.0 and trying to achieve behaviour of any off-the-shelf CANOpen slave device (encoder, inclinometer, etc...) inside CoDeSys, particularly with SDOs. Usually then you use any CANOpen configuration software (e.g. IFM Maintenance) to change SDO parameter of any CANOpen slave, the change is either automatically retained OR you should write "SAVE" string to 0x1010h and power cycle device. Unfortunately I could not achieve similar behaviour...
GDay guys! I'm playing with CANOpen Slave Device in CoDeSys 3.5.11.0 and trying to achieve behaviour of any off-the-shelf CANOpen slave device (encoder, inclinometer, etc...) inside CoDeSys, particularly with SDOs. Usually then you use any CANOpen configuration software (e.g. IFM Maintenance) to change SDO parameter of any CANOpen slave, the change is either automatically retained OR you should write "SAVE" string to 0x1010h and power cycle device. Unfortunately I could not achieve similar behaviour...
GDay guys! I'm playing with CANOpen Slave Device in CoDeSys 3.5.11.0 and trying to achieve behaviour of any off-the-shelf CANOpen slave device (encoder, inclinometer, etc...) inside CoDeSys, particularly with SDOs. Usually then you use any CANOpen configuration software (e.g. IFM Maintenance) to change SDO parameter of any CANOpen slave, the change is either automatically retained OR you should write "SAVE" string to 0x1010h and power cycle device. Unfortunately I could not achieve similar behaviour...
GDay guys! I'm playing with CANOpen Slave Device in CoDeSys 3.5.11.0 and trying to achieve behaviour of any off-the-shelf CANOpen slave device (encoder, inclinometer, etc...) inside CoDeSys, particularly with SDOs. Usually then you use any CANOpen configuration software (e.g. IFM Maintenance) to change SDO parameter of any CANOpen slave, the change is either automatically retained OR you should write "SAVE" string to 0x1010h and power cycle device. Unfortunately I could not achieve similar behaviour...