How are they? Not only the transport, but also the data structures of the items.
This would allow the user to have a reference of what you can request in the items. Looking to the future, this would be a must for the OPC-UA server. Kind regards, El dom, 9 ene 2022 a las 6:10, Christofer Dutz (<christofer.d...@c-ware.de>) escribió: > Hi all, > > I know initially I built the Plc4X API to generally allow any form of > driver to use any form of transport. > However, this only would have worked in theory. > > I think we should probably have every driver provide a list of supported > transports. > This would also help make tool integration easier. > > If we see that for example sometimes, we have ModbusRTU passed along > TCP/UDP connections via serial-to-ethernet adapters, we can definitely > support that and if we come across a mode of operation, that we haven't > encountered, it should be easy to extend. > > But this way we could ensure that we build the drivers in a way that they > know what to expect. > > What do you think? > -- *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: support.aan.automat...@siemens.com <support.aan.automat...@siemens.com>*
