Hello, In the case of high communications load to the PLC, it is best for the driver to maintain an image of the device, so that this image is consulted first. It is a more complicated design but for high loads it is the best solution.
In some tests I use a disruptor as an entry point for the driver clients and the task assigned by the disruptor handles the PLC4X driver and associated image. At the time it can be implemented by the optimization layer of the PLC4X drivers. My grain of sand Greetings to all, El mié, 7 abr 2021 a las 4:16, Christofer Dutz (<[email protected]>) escribió: > Hi all, > > Today I learnt of a case where a S7 PLC was asked for a lot of data in > very short periods. This seems to have caused the send-queue to build up > faster than it could be drained. In the end this caused OutOfMemory errors. > However, we should probably detect this situation in which over a longer > period of time the queue grows. > > How do you think would be the best way to address this? I know we're using > Julian's transaction thingy to take care of the sequence in which things > are sent to the PLC ... so I would assume this would be the place to fix it > as this would fix the problem for all drivers. > > @Julian Feinauer<mailto:[email protected]> could you possibly > find some time to come up with a "solution" to this problem? I think we > can't gracefully handle it as this is something where the user is trying to > do the impossible, but at least we should probably fail requests if the > queue is growing too fast ... OutOfMemeory errors are unfortunately nothing > you can gracefully recover from. > > Chris > > -- *CEOS Automatización, C.A.* *GALPON SERVICIO INDUSTRIALES Y NAVALES FA, C.A.,* *PISO 1, OFICINA 2, AV. RAUL LEONI, SECTOR GUAMACHITO,* *FRENTE A LA ASOCIACION DE GANADEROS,BARCELONA,EDO. ANZOATEGUI* *Ing. César García* *Cel: +58 414-760.98.95* *Hotline Técnica SIEMENS: 0800 1005080* *Email: [email protected] <[email protected]>*
