Skip to content

Support ESI for Ethercat #132

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mgiaco opened this issue Aug 13, 2024 · 3 comments
Closed

Support ESI for Ethercat #132

mgiaco opened this issue Aug 13, 2024 · 3 comments
Labels
📭 needs: author feedback More info/confirmation awaited from OP; issues typically get closed after 30 days of inactivity

Comments

@mgiaco
Copy link

mgiaco commented Aug 13, 2024

Hi, I a wondering if there is any plan to support also ESI Format for Ethercat in the future?

@nimrof
Copy link
Collaborator

nimrof commented Aug 13, 2024

Hi @mgiaco,
No official plan to support ESI format or anything related to Ethercat.
This is the closest you get to a official plan: #102

The internal/common format used in the project uses CanOpen EDS so AFIK it would be a big job to support Ethercat

@CANopenNode
Copy link
Owner

CANopenNode commented Aug 14, 2024

It depends, which information ESI file needs. According to wikipedia, Ethercat may use CANopen device profiles, so it may be possible to generate some sort of ESI file from existing data.

I don't have access to Ethercat specifications, but someone with access could:

@nimrof nimrof added the 📭 needs: author feedback More info/confirmation awaited from OP; issues typically get closed after 30 days of inactivity label Sep 28, 2024
@CANopenNode CANopenNode closed this as not planned Won't fix, can't repro, duplicate, stale Oct 9, 2024
@mgiaco
Copy link
Author

mgiaco commented Dec 2, 2024

Sorry i forgot to write back. Many thanks for your help. I will check in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📭 needs: author feedback More info/confirmation awaited from OP; issues typically get closed after 30 days of inactivity
Projects
None yet
Development

No branches or pull requests

3 participants