Skip to main content

Updates, crash reports and support

Application updates​

ScanaStudio checks for a new version at start-up and offers it in a banner. Accepting downloads the update, installs it and restarts into the new version, so there is nothing to fetch from the website by hand.

The mechanics differ slightly by platform. On Linux the update replaces itself and restarts. On Windows it hands over to the setup wizard. On macOS it replaces the application bundle and reopens it.

If an update fails, the message says why rather than only that it did not work. The check can be turned off under Settings â–¸ Updates.

Protocol script updates​

Scripts update separately from the application, against the online catalogue, and have their own switch in the same tab. This is deliberate: a decoder fix should not wait for a release of the software, and a machine that must not change should be able to hold both still.

The script manager is where updates are applied and where the catalogue can be synchronised on demand.

Firmware updates​

When a connected device carries firmware older than the software expects, ScanaStudio offers to update it. It is offered, never applied on its own, so it does not happen in the middle of something. The device's current firmware version is in Device info… in the Device card.

Do not disconnect the instrument while its firmware is being written.

Crash reports​

If ScanaStudio crashes, it says so at the next start-up and offers to send a report. Reports are opt-in, and you see the contents before anything leaves the machine: the report can be read, copied to the clipboard, or saved so you can attach it to an email instead.

Declining is remembered, so it does not ask again for the same crash. Whether it mentions crashes at all is under Settings â–¸ Report.

When you need help​

Useful things to include when you contact us:

  • The version, from About: both the ScanaStudio version and the protocol version it reports.
  • The device and its firmware, from Device info….
  • The log, from the Log view, if a script or the server reported something.
  • The workspace, saved as a .scana file. It carries the samples, the configuration and the decoders, which is usually enough for us to reproduce what you are seeing without the hardware.
  • The crash report, if there was a crash.

The contact page is the place to send it.