Is openPOWERLINK offers support for VxWorks? I do not see it mentioned in the documentation. If so, what is the relative level of effort to port openPOWERLINK to VxWorks?
Thanks,
Simon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There used to be an implementation for VxWorks in the old branch of openPOWERLINK (openPOWERLINK 1.x series). During the move to version 2.x it was decided to drop VxWorks support and purely focus on Linux as the main target operating system.
You may, however, take a look into the current sources and even find some VxWorks code parts ported to 2.x. But they have never been tested and most likely need some "polishing".
Out of curiosity: Can you describe your application that you are about to design?
Best regards,
Wolfgang
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We have an embedded real-time environment with 1 MN and ~10 CNs. They are connected via a 1 GbE switch. We have an existing application that runs under VxWorks. We are trying to ascertain whether to port OPLK to VxWorks or port our application to real time Linux which currently supports OPLK.
BTW, I have a question about Segemented Transfers posted in the Technology section. Can you help?
Thanks,
Simon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think, this depends on your application and the requirements whether porting the stack or porting the application will be the right approach.
Some years back (in the old stack), a port for VxWorks was created and compared to Linux/RTPREEMPT. Back then, VxWorks performed better regarding minimum cycle time and jitter behaviour on standard PC hardware.
However, since then RTPREEMPT has also evolved.
Best regards,
Wolfgang
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
Is openPOWERLINK offers support for VxWorks? I do not see it mentioned in the documentation. If so, what is the relative level of effort to port openPOWERLINK to VxWorks?
Thanks,
Simon
Hi Simon,
There used to be an implementation for VxWorks in the old branch of openPOWERLINK (openPOWERLINK 1.x series). During the move to version 2.x it was decided to drop VxWorks support and purely focus on Linux as the main target operating system.
You may, however, take a look into the current sources and even find some VxWorks code parts ported to 2.x. But they have never been tested and most likely need some "polishing".
Out of curiosity: Can you describe your application that you are about to design?
Best regards,
Wolfgang
Hi Wolfgang,
We have an embedded real-time environment with 1 MN and ~10 CNs. They are connected via a 1 GbE switch. We have an existing application that runs under VxWorks. We are trying to ascertain whether to port OPLK to VxWorks or port our application to real time Linux which currently supports OPLK.
BTW, I have a question about Segemented Transfers posted in the Technology section. Can you help?
Thanks,
Simon
Hi Simon,
I think, this depends on your application and the requirements whether porting the stack or porting the application will be the right approach.
Some years back (in the old stack), a port for VxWorks was created and compared to Linux/RTPREEMPT. Back then, VxWorks performed better regarding minimum cycle time and jitter behaviour on standard PC hardware.
However, since then RTPREEMPT has also evolved.
Best regards,
Wolfgang