3 ms·

I am actively exploring replacing kepware with telegraf. It seems very promising. Kepware was purchased and deployed before I joined the company. I think it's t

I am actively exploring replacing kepware with telegraf. It seems very promising. Kepware was purchased and deployed before I joined the company. I think it's the defacto standard in the controls world and they never really considered anything else. Do you have experience with modbus in telegraf? If so I'd love to chat for a bit to learn what you've learned.

notTooFarGone 2y ago
It's just making mqtt messages from modbus is such a simple task that you can just write the software yourself. There are many intricate stuff in modbus that maybe does not translate too well for generic translators and where you want to have full control. For example messages over multiple registers, breaking interfaces between vender versions and all that legacy stuff. Telegraf is also nice (but only used it for mqtt topics) but the same applies here. The functionality is fairly simple. In telegraf depending on your data your .conf file gets fairly large and has to be maintained. If you have your data model already in code it's fairly easy to just write it yourself and gain the simplicity of just using the classes you have anyway. In my current stack the data ingestion both the initial data->mqtt and mqtt-> database/cloud is just small programs that share their internal data objects. It's very easy to maintain for a small team imo.