I have seen in the device description file that you have texts like these: >Zitat:
realtime priority (SCHED FIFO 66)
I was wondering when i have a realtime kernel does Codesys automatically create processes for the tasks that runs with SCHED_FIFO according to the device description?
Because when looking with ps in the linux shell I can only see two codesys processes that are SCHED_OTHER.
And I read on another forum a tip that I should schedule the two codesys processes as SCHED_RR to make Codesys run with lower Jitter... But that doesnt seem to change anything if I try It and that setting is lost when rebooting.
Is there anything you can do to try and improve the jitter? I am not having any problems at the moment but I like to know these things so that when it becomes a problem I know what to do.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
you just need to apply and rt_prempt kernel patch for your Linux kernel this is mandatory to have realtime and less jitter.
That's it.
You will see then on you Pi jitter <150us and even better in the highest prio task.
An additional option is the muclticore version of the PI.
This will improve the jitter additional and a lot ( depending on how you distribute the application in the CODESYS project to your cores see the screen captures attached)
BR
Edwin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The problem may be that I am using a device Pigeon RB-300 which is based on a Rpi CM3.?
The kernel is based on Raspbian Stretch Lite with kernel version 4.9.80 with Preempt RT patch.
I am getting on a empty project in the Jitter colum a jitter value of 414us(-208/+206) in my task with prio 1.
I tried to disable GPIO, SPI master etc no difference.
So I guess with this hardware this is the best I can get.
Another question..
If I already have a License is there a possibility to purchase only a upgrade to multicore if deemed needed or do I need to buy a new license again?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
i have done no Tests with the CM3 so far,
bubt even around 200 us is not so bad and for most Things good enough.
Zitat:
If I already have a License is there a possibility to purchase only a upgrade to multicore if deemed needed or do I need to buy a new license again
No this is not possible - this is a different product with different price.
BR
Edwin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello.
I have seen in the device description file that you have texts like these: >Zitat:
realtime priority (SCHED FIFO 66)
I was wondering when i have a realtime kernel does Codesys automatically create processes for the tasks that runs with SCHED_FIFO according to the device description?
Because when looking with ps in the linux shell I can only see two codesys processes that are SCHED_OTHER.
And I read on another forum a tip that I should schedule the two codesys processes as SCHED_RR to make Codesys run with lower Jitter... But that doesnt seem to change anything if I try It and that setting is lost when rebooting.
Is there anything you can do to try and improve the jitter? I am not having any problems at the moment but I like to know these things so that when it becomes a problem I know what to do.
Hi,
you just need to apply and rt_prempt kernel patch for your Linux kernel this is mandatory to have realtime and less jitter.
That's it.
You will see then on you Pi jitter <150us and even better in the highest prio task.
An additional option is the muclticore version of the PI.
This will improve the jitter additional and a lot ( depending on how you distribute the application in the CODESYS project to your cores see the screen captures attached)
BR
Edwin
The problem may be that I am using a device Pigeon RB-300 which is based on a Rpi CM3.?
The kernel is based on Raspbian Stretch Lite with kernel version 4.9.80 with Preempt RT patch.
I am getting on a empty project in the Jitter colum a jitter value of 414us(-208/+206) in my task with prio 1.
I tried to disable GPIO, SPI master etc no difference.
So I guess with this hardware this is the best I can get.
Another question..
If I already have a License is there a possibility to purchase only a upgrade to multicore if deemed needed or do I need to buy a new license again?
Hi,
i have done no Tests with the CM3 so far,
bubt even around 200 us is not so bad and for most Things good enough.
No this is not possible - this is a different product with different price.
BR
Edwin