Pixel Device Connectivity

Prev Next

The CytoTronics Pixel device is an internet-connected device used on-site to acquire measurements from a removable 96- or 384-well plate reader.

Device Interfaces

Interface

Purpose

High speed bus

  • Power and data communications to the removable 96- or 384-well plate

Ethernet

  • Upload measurement data to the CytoTronics cloud platform.

  • Receive over-the-air (OTA) software updates and device configuration

USB

  • Allows configuration of the Ethernet interface (in case the default DHCP configuration is not sufficient)

Network Communications

The following diagram shows the network communication channels used by the Pixel device. All cloud communications are initiated from the Pixel device and protected by end-to-end encryption protocols.

The bulk of the communication is with the CytoTronics API server and Measurement Data Storage bucket (to query and create resources such as projects, experiments, measurements, etc). In case of a connection failure, the Pixel device will continue to operate its current experiment for up to 48 hours, queuing data to be uploaded once the connection is restored.

OTA Firmware Updates

CytoTronics uses an OTA update solution through mender.io. Pixel devices periodically poll this firmware update server for security patches and bug fixes and for updated device configuration. If newer firmware or device configuration is available, the device will download it and restart to apply the update.

Some examples of device configuration that can be deployed include:

  • Unique API Token that associates the device with one organization and provides the device with the minimum privileges required.

  • Activation of remote troubleshooting capabilities

OTA deployments are secured in the following ways:

  • Access to Mender is restricted to a minimal group of CytoTronics engineers

  • Admin accounts are authenticated against Microsoft 365 SSO with MFA enforced

  • Mender service accounts use minimal RBAC access privileges

  • All Mender account activities are recorded in an audit log

  • Planned for post-beta roll outs: Software Bill of Materials (SBOM) to be published for every firmware update