# Live Monitoring

Engine features live, in-browser debugging of operational systems via backoffice. All debug messages are outputted to the browser console (F12 or Ctrl+Shift+I, then Console tab).

Ensure that the Console logging is set to enable Verbose messages, as highlighted below:

![](https://lh5.googleusercontent.com/gC3SWQZi72o9VJN20__6t2Gm98EOkW6auqqcK-7hlmHqhAwyKX287Ideh3hOr2lWWVkH6eCk2QixB9vti4vlp-uwA3ZR8Ur6jdAnmARPaPBXMMfkEqTtHdi18R_WuNAgV2ADXWRi)

## Viewing Debug Messages

Debugging is done from the Systems section. Select the system to debug and then click the Device tab.

![](https://lh3.googleusercontent.com/bUE_wgSIhyteqyXzLPOUkay0LDrCYC9v2NY4NFanjqRMMLOaoXQ_NYuqZuUEK8oIu6lCwZSIzSgcHbMhvcv14PTa1OXN_nthiB2w6QD3-PKBdKcZ9QshWlr2_dydBlxfkzQLKNMC)

The checkbox (6) on the the left of the Class type enables live debugging output for this Device to the browser console. Pressing the Eye symbol (7) next to the device name will instantly output the device’s current status information to the console to assist in troubleshooting scenarios.

## Sending Manual Commands

The About tab of the System page contains a drop down list (9) that allows the selection of a device to send a manual control command to.

![](/files/-LftdEzRzI1ozTeJJSc4)

The device’s response to these commands will be output to the bottom of right of the window and (if enabled - above) to the browser console.

Some commands will require parameters. When blank, the text field will describe the type of parameter required by the function.

In the event that Engine is not able to send a command to the device, an error message (red instead of blue) will appear at the bottom of the screen with the details.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://engine.place.technology/developer-guide/drivers/debugging.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.