CODESYS Forge - CODESYS Forge / Talk / Runtime 🇬🇧: Run communication after reboot

Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched. Close

Run communication after reboot

Forum: Runtime 🇬🇧

Creator: suibaf

Created: 2016-02-13

Updated: 2016-02-18

suibaf - 2016-02-13

Hi,

EtherNet/IP communication tra Raspberry PI2(scanner) and a PLC work fine as you can see:

But if I reboot the raspberry the communication does not work.

To start the communication it need a hot reset or a cold reset.

How is it possible to run the communication itself after a reboot?

Thank you

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

suibaf - 2016-02-14

If someone want to look the project, you can download it from following link.

https://dl.dropboxusercontent.com/u/152 ... ectarchive

The project work fine, but if reboot the raspberry, the ethernet/IP communication does not work.

Currently for start up communication after reboot I have to perform a hot or cold reset.

BR

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

suibaf - 2016-02-15

Maybe I understand the problem, but I have no solution. Please look the screenshot! Have you advice for me?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

eschwellinger - 2016-02-15

guess we could provide you with an solution tomorrow.... some additional tests are needed.
BR
Edwin

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

eschwellinger - 2016-02-16

we need more time ... sorry for this.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

suibaf - 2016-02-16

No Problem Edwin! I wait!
Do you think that it is a bug?
BR

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

eschwellinger - 2016-02-18

Hi,

yes it is a bug and it need to be solved in CODESYS
The workaround is to use a static assigned IP till the fix is released.
BR
Edwin

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

suibaf - 2016-02-18

Hi Edwin,

Raspberry has already a static assigned IP.

BR

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

suibaf - 2016-02-18

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

suibaf - 2016-02-18

OK now it work fine:

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.