Hello,
What used to work fine does not work anymore since I upgraded to 3.5.17.
I installed 3.5.17 then re-installed the safety package 4.2.0.0. I also installed all the xml files from Beckhoff.
Now my EL6900 is not recognized anymore and there also seems to be an issue with EL1904 and EL2904.
What can I do to fix this?
Thank you.
The issue seems to be related to my new EL6900. Is it too recent?
I used an older EL6900 and it seems to work. The new one I just bought for this project is not recognized!
What can I do?
Nervermind, it works anyway.
I just don't understand why sometimes the scan works and somtimes it does not. Now the scan does not work on my old EL6900 but it works anyway...
would be intresting need to be investigated - could you send us device log - and projectarchive to the store helpdesk?
What is the store helpdesk?
here: at the very bottom, Contact / Service / Support https://store.codesys.com/en/
I am still having the same issue. Here's what the log says:
This will be fixed with 4.3.0.0 Ethercat release.
Log in to post a comment.
Hello,
What used to work fine does not work anymore since I upgraded to 3.5.17.
I installed 3.5.17 then re-installed the safety package 4.2.0.0.
I also installed all the xml files from Beckhoff.
Now my EL6900 is not recognized anymore and there also seems to be an issue with EL1904 and EL2904.
What can I do to fix this?
Thank you.
The issue seems to be related to my new EL6900. Is it too recent?
I used an older EL6900 and it seems to work. The new one I just bought for this project is not recognized!
What can I do?
Last edit: yannickasselin 2021-06-28
Nervermind, it works anyway.
I just don't understand why sometimes the scan works and somtimes it does not.
Now the scan does not work on my old EL6900 but it works anyway...
would be intresting need to be investigated - could you send us device log - and projectarchive to the store helpdesk?
What is the store helpdesk?
here: at the very bottom,
Contact / Service / Support
https://store.codesys.com/en/
I am still having the same issue.
Here's what the log says:
This will be fixed with 4.3.0.0 Ethercat release.