Im in need of a driver for IEC 60870-5 101/104. In Sweden it is widely used within communication with switchgears and other electrical devices. Our biggest competitor within the area is Citect and they have this driver and it’s a clear argument from the customers to not introduce more products in the line of communication, i.e. OPC. Also, the whole backbone of the Railroad administration uses 104. Here we compete with Zenon who has the driver also. I post this to be able to vote for it in https://ideas.inductiveautomation.com/.
So, if you see the same need as I do, please vote for it😊
I know its solvable with Kepware and such solutions, but native drivers are most often heavy arguments.
This post (and every other request I get like it) makes me sad.
It's not too late for the industry to embrace open, multi-vendor, interoperable solutions that assemble the best available pieces for the job...
But as a whole you continue to sleepwalk towards a walled garden / single-vendor lock in, all for the mild convenience of having one phone number to call for support instead of two or three
I really understand what you are saying, but there are quite a few other aspects of it…one is that you have situations with an installed base that goes 20-30 years back that covers all installations of a whole country or a whole hospital, etc. It requires quite a rework to changes those things…..and we want Ignition to handle everything, both green- and brownfield.
That's a bit over the top, for an IEC standard. There's no question OPC UA and MQTT are the future in the IT space, but I doubt they will ever completely replace dedicated protocols in the OT space.
ok, then I misunderstood you, although what I wrote still applies. But connected to what you wrote, it's about adapting to what the industry looks like in order to be included in the game. 2 or 3 phone numbers are probably ok, but when you get up to 20-30, it's a different matter. You increase the risks of ending up in the classic blame game situation and that you will find it difficult to get help with your possible problems.
A point of clarification - every Ignition "native" driver is actually just a plugin for Ignition's OPC UA server. If you are using an Ignition driver, then you already have OPC in the line of communication. It's just not an OPC server from another vendor.
Yeah, I know, I guess its not regarding the name of the communication, it's all about third-party products. At least in Sweden, which is quite Citect heavy, native drivers are seen as very important by most customers.
