Industry solutions

eight industry solutions, each a working plant that configures litmus edge for you and then runs against it every one brings up an operator view you can show, a live industrial protocol server that the edge polls, and a set of faults you can inject on demand they are demonstrations rather than production systems, but nothing about the litmus edge side is simulated real devicehub devices and tags, real digital twin models and instances, real analytics processors, over the protocol the industry actually uses the solutions solution industry devices and tags protocol bottling line # food and beverage 6 devices, 94 tags modbus tcp bioreactor suite # pharmaceuticals 5 devices, 94 tags modbus tcp collection system # water and wastewater 9 devices, 274 tags dnp3 vision inspection # food and beverage 1 device, 15 tags modbus tcp and nats body shop framing line # automotive 7 devices, 181 tags modbus tcp and open protocol rotating equipment reliability # power and utilities 6 machines, 90 tags sparkplug b over mqtt grid substation # power and utilities 9 devices, 69 points iec 60870 5 104 steel mini mill # metals 8 devices, 122 tags opc ua solutions provisioner # is a control panel that starts and stops all eight from one page and connects them to a litmus edge once rather than one at a time it is optional; each solution runs perfectly well on its own they are designed to run side by side ports do not collide, and all eight against one litmus edge is about 47 devices, which is a realistic load before you start litmus edge 4 0 x , reachable over https from wherever you run the solution an api token for that edge, or a username and password, or a client id and secret any one of the three is enough docker and docker compose on the host that will run the solution a network path in both directions this is the one that catches people out; see below the three values every solution needs each solution ships a compose file with three values to fill in, either directly in the file or in a env beside it value what it is edge url the litmus edge to configure, for example https //10 0 0 5 edge api token a token for that edge or edge username and edge password , or edge client id and edge client secret sim host the address the edge should poll to reach the solution sim host is the one worth understanding the solution serves an industrial protocol and litmus edge connects to it, so the edge needs an address it can route to leave it as auto when the solution runs on the edge itself or with host networking, and the address is worked out from the route to the edge otherwise set it to the address of the host running the solution, as the edge sees it get this wrong and the failure is quiet the devices are created, they show as online, and no tag ever reads a value, because the address baked into the template is one the edge cannot reach each solution refuses to apply a template whose address is obviously unreachable and tells you why, rather than succeeding and doing nothing deploying one every solution follows the same three steps \# 1 get the compose file and, if you are working offline, the image tarball \# 2 fill in the three values, in the file or in a env beside it \# 3 start it docker compose up d then open the operator view on the solution's ui port within about a minute the edge is configured and the page fills in images are published to us docker pkg dev/litmus customer facing/litmus solutions if your site cannot reach a registry, each solution is also available as a tarball you load with docker load , and there is one bundle carrying all of them together with the control panel what each solution puts on litmus edge on startup, with apply on start left at its default of 1 , a solution configures the edge itself devicehub devices and their tags, pointed at the protocol server the solution is running digital twin models and instances for the equipment analytics groups and processors behind the kpis the operator view shows this takes 30 to 60 seconds, because litmus edge restarts devicehub while it applies the ui is available immediately and tells you what is happening set apply on start=0 to run the simulator without writing anything to an edge every solution can also remove exactly what it created, so a shared edge can be returned to how you found it ports each solution serves its operator view on 401x and its industrial protocol on 502x , so all of them can run at once none of these collide with litmus edge's own services solution operator view protocol solutions provisioner 4009 bottling line 4010 5020 bioreactor suite 4011 5021 collection system 4012 5022 vision inspection 4013 5023 body shop framing line 4014 5024, and 5124 for open protocol rotating equipment reliability 4015 5025 grid substation 4016 5026 steel mini mill 4017 5027 tls edge verify tls is 0 by default, because a litmus edge ships a self signed certificate and verification would fail for a reason that has nothing to do with the connection being wrong set it to 1 anywhere the certificate is a real one these solutions send an api token over that connection support support\@litmus io mailto\ support\@litmus io