tPre-silicon Studio
PRE-SILICON STUDIO

Workspace APIs.
OTA when you need it.

Standalone simulation is available without credentials. Connecting an API is optional. Virtual OTA tests cloud workflows; physical flashing and bootloader testing still require real hardware.

Pre-silicon Studio works standalone without an account, subscription or credentials. Telematric telemetry and Telematric OTA are separate opt-ins. You can use your own backend or OTA tooling independently; this release does not implement other vendors' OTA APIs.

Connect telemetry

  1. In your Telematric workspace, activate the required Device cloud access and register a dedicated development device. Do not select a physical customer device for these tests.
  2. Create a dedicated development API key with devices:read and telemetry:write. Copy the workspace UUID and registered device UUID. A simulated hardware nickname is not the registered device ID.
  3. Open Cloud API / Connect workspace. Give your local project a name, choose Telematric public API, and enter the API base URL, workspace, device and API key. Choose None / bring your own OTA if you only want telemetry.
  4. Save & connect verifies the device using GET /v1/organizations/{workspace}/devices/{device}. Start/Resume or Step sends synthetic readings using POST /v1/telemetry/reading with x-api-key. An already-running simulation starts using the connected API after your explicit connection action.

Requests use documented APIs with no portal session or database access. The API verifies scopes, tenant boundaries, service access, quotas and rates. The studio does not create accounts, enroll hardware, activate a paid service or buy capacity. These requests and accepted readings count under the workspace's configured usage rules; synthetic data is real stored data when connected.

The native API accepts a defined metric set. Studio maps supported readings, including temperature, humidity, electrical measurements, flow and supported booleans. Pressure, vibration, orientation, cumulative-volume registers and other unmapped profile fields remain simulation data; this connection does not persist every displayed metric or create metering/billing records. No invented fallback temperature is submitted. Timestamps use UTC whole-second precision; retries preserve event identity and payload.

Base URL, browser origins and credentials

The hosted studio defaults to https://pre-silicon-studio.telematric.com/telematric-api, a fixed same-origin proxy to the supported Telematric public API routes. It forwards your supplied API credentials; it does not sign you in, supply server-side keys or bypass workspace checks. Only studio telemetry, device verification and OTA read/report/download paths are permitted. Cookies and account bearer sessions are not forwarded.

The default local base is http://localhost/Nuvetra/api/public; supply the base for your installation, not a filesystem path or telemetry route. HTTPS is required except loopback. No credentials in URL userinfo/query/fragment are allowed. Requests omit cookies and reject redirects.

A browser connection to another origin requires that API/proxy to explicitly permit the Studio origin and the needed headers (Content-Type, x-api-key, and x-powercell-ota-token for OTA). The studio does not enable wildcard CORS or bypass origin restrictions. Use a controlled same-origin backend proxy when needed, keeping keys on your server in production applications. The hosted same-origin proxy avoids requiring wildcard CORS. Other API origins must explicitly allow the browser origin, or use your own controlled proxy.

API keys and OTA tokens remain in page memory; saved projects, browser storage, scenario exports and generated firmware do not include them. The UI supports temporary development keys; browser memory is not a secret vault. Disconnect clears the session credentials and aborts outstanding requests. A request already accepted by a server cannot be undone by disconnecting. Never embed a workspace API key in firmware: physical boards should use their device credentials and documented SDK.

Project names/base/workspace/device metadata are saved locally (up to25 projects), not as shared cloud project records. Reload requires re-entry of credentials and explicit connection. Scenario imports always disconnect and do not inherit live authorization. Telemetry belongs to the selected registered device in the selected Telematric workspace; changing simulation presets does not retarget the API to a profile nickname.

Optional virtual OTA

Choose Telematric · virtual OTA target only when needed. Add firmware:read to the dedicated key, provide the enrolled target's separate64-hex OTA token, and enter the virtual installed version as major.minor.patch.

Current enrollment uses Telematric's existing PowerCell ESP32 socket/collector, esp32dev contract and supported binding. An existing registered device alone is insufficient: it must already have its supported binding and OTA enrollment. The studio does not create these or schedule deployments automatically. STM32/ThreadX targets are not emulated by this OTA client.

  1. Schedule a release for this dedicated development target through Telematric's normal dashboard/API workflow.
  2. Check for update reads the workspace firmware overview, verifies the selected target, and calls POST /v1/powercell/firmware/check with both the scoped API key and separate x-powercell-ota-token. A check can change the real deployment to downloading.
  3. Download & verify retrieves /v1/powercell/firmware/download/{deployment}. It checks the declared size, the existing1,310,720-byte maximum and SHA-256 digest. It never follows an arbitrary manifest URL or executes bytes.
  4. Simulate reboot, then Confirm healthy boot or Simulate rollback. The client reports the selected outcome and verifies deployment status through the workspace API. Confirmed version changes also update the virtual device's transmitted firmware label. A submitted outcome cannot be switched after an uncertain response; retry the same outcome or inspect the deployment in Telematric.
  5. Interrupt download reports a simulated failure. Stop virtual update resolves an offered/verified test as failed. If failure reporting fails, Retry failure report remains available. A stopped transfer restarts as a new test; there is no resumable-range/power-loss emulation in this release.

This uses real cloud deployment state for a virtual device. Closing/reloading/disconnecting does not automatically cancel or resolve a deployment; inspect/recover it in Telematric if the session ends mid-test. This is intentionally a dedicated test target workflow. It does not test real flash partitions, bootloader execution, secure boot, signature verification, power-loss safety or physical rollback.

Buffer and error behavior

Browser storage holds at most100 unsent readings per API base/workspace/device context. Standalone queues never flow into live projects, and one workspace/device cannot replay another's queue. Context changes abort in-flight fetches and discard stale response effects. Keys/tokens are not included in queue data. Old unscoped simulator queues are not automatically replayed.

Live telemetry is paced at a minimum1.1-second interval. 429 responses use Retry-After (bounded to one day for recheck); service/provider/network errors remain buffered. Authorization errors disconnect. Terminal payload errors are visibly rejected/removed rather than poisoning the queue forever. Overflow drops the oldest entry and emits a dropped-count warning. Browser storage can be cleared, unavailable or quota-limited: this is not physical LittleFS, a guaranteed archive or production device recovery.

Local verification