Dashboards and widgets

1. On Dashboards, choose New dashboard and type a name.
2. Open the new card. Choose Edit, then Add widget.
3. Pick a widget. The configuration sheet opens so you can set the title, tag or topic, and colors.
4. Drag the tile to move it. Drag the corner to resize it. Choose Done when the layout is right.
5. Edit, then the trash icon, deletes that dashboard. Widgets already on other dashboards are not affected.

Four boards are already there: North Field, Process Hall, Line Animation, and Widget Gallery. Widget Gallery has one of each widget. Copy the idea onto your own board by adding the same widget from the catalog.

The line is a widget machine, a conveyor, a quality station, an infeed sensor, a defect sensor, an outfeed sensor, a reject chute, and a good bin. Parts spawn at the machine and travel at the Rate you set. The belt and the parts share one speed, so the widgets stay on the belt.

• Start / Stop. Stop ends the run and opens a downtime row. Start closes it.
• Rate. Pieces per minute. This is the ideal rate used by performance.
• Defect. The next part is rejected at the defect sensor.
• Reason. Dropdown used for the next stop, and for a stop that is already open. Choices are Unplanned, Fault, No material, Changeover, and Break.
• Reset. Clears counts, the schedule progress, downtime, and the OEE Engine history for this topic.
• Topic. Default EET124/OEE/DrJeff. Every MES tile on the same topic follows this line.

MQTT is published as individual topics and as one flat JSON payload on the base topic. The values are running, rate, defect, made, good, reject, infeed, and outfeed. Example: EET124/OEE/DrJeff/good. The Ignition line also writes those values under the tag folder [default]MQTT Tags.

The SQL browser under the conveyor lists each table and the first 10 rows. In the preview those rows are the live line state. On the gateway they are the real database, using the external MySQL connection when that connection is enabled.

The MySQL Connection widget is the login for an external database. Enter host, port, database name, user, and password, then choose Save connection in the preview or Test and save in Ignition.

• A successful test sets mes_connection.enabled to 1.
• From then on, the line writes mes_snapshot, mes_event, mes_order, and mes_downtime to that database.
• The connection row itself stays in the project database so the gateway can find the login.
• If the test fails, MES keeps using the project database. The gateway needs the MySQL or MariaDB JDBC driver, which is the same driver the project database already uses.
• Leave the password field blank only when the database account has no password. Do not put the password in a widget title or an MQTT topic.

The OEE tile on the line shows overall equipment effectiveness since the last reset. The OEE Engine is different. It queries the history inside a time window and calculates OEE for that window only.

The interval defaults to 5 minutes. Change it on the widget, from 1 to 240 minutes. On the gateway the engine reads mes_event rows whose timestamp falls inside the window. It subtracts the oldest row in the window from the newest:

• Availability = run seconds gained ÷ (run seconds gained + down seconds gained).
• Performance = parts made in the window ÷ (rate × run minutes in the window). The result is capped at 100.
• Quality = good parts in the window ÷ parts made in the window.
• OEE = availability × performance × quality ÷ 10000.

The engine needs two samples in the window before it shows a number. Start the line and wait a few seconds. Reset clears the sample log, so the window starts over.