Close

plc in growing in my head

A project log for oiyshTerminal

Local server collection of IoT system with some additional futures. Works by default offline, based on .deb .npm .pipy

yoyoek1yOyOeK1 03/16/2023 at 16:520 Comments

So started from some simple api to get only topics list in system now is slowly starting to be a plc in / out manager layer. 

Image it! - drawing is helping me with finding what is where This is a big decision to make. Possibilities main blowing. One instrument set by default is working in telemetry mode. As mqtt telemetry can be. With idea of `Bundles` this is object orientated. 

No difference if you check battery at your car in garage, rc model charger, battery in green house, .... it's a `Bundle` battery. 

If sensors channels / topics by plc api will get name, bundle, type of value, unit, post process for data if needed. Then any multimeter site in yss can do all them not knowing from where is it's sourced. Bum Nice! 

You want to get all possible alarms emitters in your system. One query to api.

IoT automatized

If plc api will collect new traffic it will be a nice source of new sensor in your system to set in up as bundle or define nicer name set units.

Check drawing and let me know what scenario can't be managed with this... 

More on wiki link ...

Discussions