RMA
Member
I'm not around much at the moment as I'm spending quite a lot of time on site commissioning - with no Internet access (doesn't half take a long time to catch up if you miss 4 days!).
This week somebody switched off one of the DP-Slaves to make some mods - and the CPU promptly went into STOP! Actually, it's not the first time I've noticed this and I've even mentioned it before I believe, but so far I've not found a solution. The actual problem that causes the CPU to stop is a buffer overun, according to the diagnostic buffer - presumably because OB85 is being called too often (some of the entries in the Buffer state that OB85 is not available).
It probably won't actually be a serious problem in practice, but it strikes me as the sort of fault that just shouldn't happen.
Does anybody have any suggestions for a strategy to react to the first fault so as to keep the CPU alive? I tried calling my routine to disable the DP-Slave concerned using SFC12, but it doesn't appear to react quickly enough.
This week somebody switched off one of the DP-Slaves to make some mods - and the CPU promptly went into STOP! Actually, it's not the first time I've noticed this and I've even mentioned it before I believe, but so far I've not found a solution. The actual problem that causes the CPU to stop is a buffer overun, according to the diagnostic buffer - presumably because OB85 is being called too often (some of the entries in the Buffer state that OB85 is not available).
It probably won't actually be a serious problem in practice, but it strikes me as the sort of fault that just shouldn't happen.
Does anybody have any suggestions for a strategy to react to the first fault so as to keep the CPU alive? I tried calling my routine to disable the DP-Slave concerned using SFC12, but it doesn't appear to react quickly enough.