hill831017
Member
Normally everybody use pulse memory bit generate all necessay pulse,tact(100ms,200ms,1s...).
Then in the FB we use (for example 100ms) to count delay for the output.
My problem - I have a system with more than 100 drive, big profinet network - arround 200+ deivce, and safety program also running in this PLC. Scan time of PLC is 45-55ms. I already choose the most faster PLC I could - CPU319F 0.004ms/1000 instructions.
Some place I need stop delay, but under this scan time every time part stop on different place. After optimize scan time lower than 50ms, then part mostly stop on rigt postion.
So I guess it's should more or less relate with scan time and pulse which I use. It seems not like following equation when scan time is above 50ms.
Part Stop distance 30mm = 0.6mm/s*(100ms*5(Setting from IDB)+Communication delay(could be ignor))
Real stop different can be 30-80mm, which means it may cause by miss counting 100ms by each 100ms.
Some idea from my colleague is changing time unit resolution 100->200ms when CUP SCAN time is more than 50ms. But is really a big modification that I have to change all the IDBs. And Privcy Blocked FB.
Anyone have better solution for such kind of stop delay?
Then in the FB we use (for example 100ms) to count delay for the output.
My problem - I have a system with more than 100 drive, big profinet network - arround 200+ deivce, and safety program also running in this PLC. Scan time of PLC is 45-55ms. I already choose the most faster PLC I could - CPU319F 0.004ms/1000 instructions.
Some place I need stop delay, but under this scan time every time part stop on different place. After optimize scan time lower than 50ms, then part mostly stop on rigt postion.
So I guess it's should more or less relate with scan time and pulse which I use. It seems not like following equation when scan time is above 50ms.
Part Stop distance 30mm = 0.6mm/s*(100ms*5(Setting from IDB)+Communication delay(could be ignor))
Real stop different can be 30-80mm, which means it may cause by miss counting 100ms by each 100ms.
Some idea from my colleague is changing time unit resolution 100->200ms when CUP SCAN time is more than 50ms. But is really a big modification that I have to change all the IDBs. And Privcy Blocked FB.
Anyone have better solution for such kind of stop delay?