Hi, Is there a way to diagnose how many safety CANopen messages are being received or sent within a given time? The idea is to implement a "drift check" which monitors the timeliness. If every message is delayed slightly so that it doesn't trigger the timeouts, then the data will "drift" behind. This is what I'm trying to prevent, this check is a requirement.
Looks like you're missing a library for normal CAN, so the higher level CANopen protocol can't work.
Hi again Eschwellinger, Could this be because it's CANopen safety? When the communication breaks, it's supposed to go into a safe-state. Do you know if it's possible to have the manager restart communication once the slave comes back up, without needing a HW restart?
Hello, I am working on a safetyPLC project and need the use of EVL/EVC to share variables between safetyPLC and non safe PLC side. Recently we discovered that function blocks instances have some additional safety requirements that would we have to fulfill, but since we only use these blocks once it made sense to change to all to PRGs instead. After changing them all, the EVC list stopped displaying the variables, it seems that there are too many PRGs for it to handle. The code still works, but I...
Thanks for the response. Yes, I've tried using S_xErrorAck, but it didn't help. I've been thinking about this problem; I think it's related to an SDO request we have. I'm going to investigate that further and will be contacting the plc vendor if I don't resolve it.
bump
I work with a Safety PLC, and I have noticed that with one built-in conversion FB, " bool to safebool" , I get errors too. It was determined that this was hardware related, it wasn't supported by our specific plc/vendor. This might not answer your specific question, but I believe those conversions might not be supported with the new device. Take it with a grain of salt. If this is the case though, there might be other ways to make those conversion, like converting explicitly?
I work with a Safety PLC, and I have noticed that with one built-in conversion FB, " bool to safebool" , I get errors too. It was determined that this was hardware related, it wasn't supported by our specific plc/vendor. This might not answer your specific question, but I believe those conversions might not be supported with the new device. Take it with a grain of salt. If this is the case though, there might be other ways to make those conversion, using different conversion FB's perhaps.
I work with a Safety PLC, and I have noticed that with one built-in conversion FB, " bool to safebool" , I get errors too. It was determined that this was hardware related, it wasn't supported by our specific plc/vendor. This might not answer your specific question, but I believe those conversions might not be supported with the new device. Take it with a grain of salt.
https://help.codesys.com/api-content/2/codesys/3.5.12.0/en/_cds_vartypes_retain_persistent/ "The requirement for full functionality is an appropriate memory range on the controller (NVRam, UPS)." Not sure if that's possible
https://help.codesys.com/api-content/2/codesys/3.5.12.0/en/_cds_vartypes_retain_persistent/ "The requirement for full functionality is an appropriate memory range on the controller (NVRam, UPS)." Not sure if that's possible, if FRAM is supported?
https://help.codesys.com/api-content/2/codesys/3.5.12.0/en/_cds_vartypes_retain_persistent/
Try username : admin password : leave the password blank This is what works for my set-ups with softPLC and real PLC, I'm just thinking those might be the defaults, worth a try.
Try username : admin password : leave the password blank
and here is the CANopen settings for the PC slave
Hi, I am working on a project where we have CANopen communication between a safetyPLC (CANopen Manager / master)and an industrial PC (slave). It's working pretty well, except for this one issue; When the PC slave device shuts off, CANopen stops. But when the PC comes back up again, the CANopen communication does not resume until I do a PLC restart (power off and on), or code re-download. In our application, we use the S_CANopen_PC_SIL2.S_xActive to monitor communication status. I experimented by...