I have used in the past Schneider M251 codesys based PLCs and they have a pretty fast boot time of about 10 seconds.
I am starting to use a Wago PFC200 now and the boot time for the same application (ported to e!cockpit) is over 60 seconds!
Has anyone found a way to reduce the startup time on PFC200-8202 controllers?
Cheers,
Louis.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for getting back to me.
I found the log and rebooted the PLC to capture a startup. Please see attached.
I'm not sure where the 'processor load exception' would be coming from but will search the forum to find more information. Would you mind looking at the log to see why it might be taking so long to start-up please? Is it all the services starting & activating licenses maybe. Traditional PLCs take no where near this long to boot so it's not all that great if it takes a minute to boot.
Thanks for looking at it for me, yeah I have contacted them and heard back, they said that this is normal.. I would think this would be a major design concern for them!
Anyway I'll try running stock codesys on it and see if it improves, if not I'll have to mitgrate to other/faster booting hardware.
Regards,
Louis.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes I have installed the codesys runtime on the PFC200.
After porting code but not yet visualisations, the boot time is around 32 seconds which is much faster then the e!cockpit runtime and probably acceptable for our application.
It would be good to know what the issue is, I have noticed too that the stock codesys software is much smoother to use than e!cockpit too - also ethernet scanning has not been implemented yet.. which we need for our application.
Regards,
Louis.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi There,
I have used in the past Schneider M251 codesys based PLCs and they have a pretty fast boot time of about 10 seconds.
I am starting to use a Wago PFC200 now and the boot time for the same application (ported to e!cockpit) is over 60 seconds!
Has anyone found a way to reduce the startup time on PFC200-8202 controllers?
Cheers,
Louis.
Hi,
I would recommend to check the plc logger…
BR
Edwin
Hi Edwin,
Thanks for getting back to me.
I found the log and rebooted the PLC to capture a startup. Please see attached.
I'm not sure where the 'processor load exception' would be coming from but will search the forum to find more information. Would you mind looking at the log to see why it might be taking so long to start-up please? Is it all the services starting & activating licenses maybe. Traditional PLCs take no where near this long to boot so it's not all that great if it takes a minute to boot.
Regards,
Louis.
PLC LOG.xml [40.6 KiB]
Hi,
not sure, but the runtime start
8:39:18 to 8:39:59 … not sure this could be improved.
Would recommend to ask the Wago support.
BR
Edwin
Hi Edwin,
Thanks for looking at it for me, yeah I have contacted them and heard back, they said that this is normal.. I would think this would be a major design concern for them!
Anyway I'll try running stock codesys on it and see if it improves, if not I'll have to mitgrate to other/faster booting hardware.
Regards,
Louis.
Hi Luis,
if you check this with CODESYS,
please let me know the result.
BR
Edwin
Hi Edwin,
Yes I have installed the codesys runtime on the PFC200.
After porting code but not yet visualisations, the boot time is around 32 seconds which is much faster then the e!cockpit runtime and probably acceptable for our application.
It would be good to know what the issue is, I have noticed too that the stock codesys software is much smoother to use than e!cockpit too - also ethernet scanning has not been implemented yet.. which we need for our application.
Regards,
Louis.