Skip to main content

Management

Cordatus provides a range of management features designed to optimize your AI workflow. These tools empower you to effortlessly supervise your edge devices, eliminating the necessity for physical access.

Jetson Power Modes

Based on the application requirements, the Jetson platform presents various power modes, known as nvpmodels, offering a fine-tuned balance between performance and power consumption.

These nvpmodels comprise preconfigured setups, allowing developers to choose the best mode for specific needs. For detailed information, consult the NVIDIA Jetson Documentation.

Follow these steps to remotely manage your Jetson device's power mode:

Using Web App

  1. Go to the Devices page using the left menu.
  2. Click the Metrics icon to open the Summary modal.
  3. Visit the Jetson Control Center tab, specific to Jetson devices, to see the available performance modes.
  4. Identify the active performance mode, marked with a green background. Change the performance mode by clicking on the preferred option.

Power Modes on Web

Jetson Power Modes on Web

 

Using Client

  1. Go to the Monitor page through the left menu.
  2. Click Control, specific to Jetson devices, to access the control tab. This tab displays the available performance modes.
  3. Identify the active performance mode, marked with a blue background. Change the performance mode by clicking on the preferred option.

Power Modes on Client

Jetson Power Modes on Client

 

Remote SSH Connection

SSH, or Secure Shell, is a secure network protocol used for remote access and communication between computers. Even over unsecured networks like the Internet, SSH ensures the encrypted transmission of data, making it a reliable choice for remote system and application management.

Cordatus simplifies the process of securely connecting and managing all your devices, eliminating the need for additional configuration. To establish an SSH connection with your device, follow these steps:

  1. Go to the Devices page in the Web App's left menu.
  2. Click the ellipsis icon under the Actions column, next to the metrics icon, to reveal actions.
  3. Select Connect via SSH, triggering the Connect remote device via SSH modal.
  4. Copy the SSH command by clicking the Copy icon.
  5. Open a new terminal.
  6. Paste the copied SSH command. If using ctrl+v encounters issues, right-click in the terminal and select paste.
  7. Replace [USERNAME] with your client device's username.
  8. Execute the command.
  9. Enter the password for your client device's user when prompted.
  10. Confirm the SSH connection's success by checking the username at the command line, matching the connected device's user.

Remote Desktop Connection

  1. Go to the Devices page in the Web App's left menu.
  2. Click the ellipsis icon under the Actions column, next to the metrics icon, to reveal actions.
  3. Select the Remote Desktop button, prompting the Active Windows modal.
  4. You'll see options for each screen and open window on your device. Choose a specific window or screen from the options presented for your device.
  5. Click Start Remote Desktop.
  6. Your remote desktop connection will be successfully established.

 

info

The remote desktop feature is only for connecting remote devices. Trying to connect using the web browser on the device you want to connect to won't work.

Accessing Logs

  1. Go to the Devices page in the Web App's left menu.
  2. Click the ellipsis icon under the Actions column, next to the metrics icon.
  3. Choose the Download Logs button.
  4. The renderer.log file will be downloaded automatically.

 

note

When requesting support, make sure to include the renderer.log file for a thorough examination of the issue.

Disabling/Enabling Logs

If you wish to disable/enable Client or Stream Engine logs:

  1. Click on the user icon on the top right corner of the client.
  2. Click on the Settings button on the menu that opens up.
  3. On the General tab, toggle the Enable Client Logs or Enable Stream Engine Logs to enable or disable respective logs.