logsense Beta — Field Analysis

Sign In

What do you need?

Choose a path. For a site failure with logs, use Analyse a problem.

Ask a question

Analyse a problem

Problem details

Primary symptom

When in the workflow?

Mid-delivery abort? — injection cut short mid-delivery

On-screen message / LED colours — exact wording if known

How often?

Incident time(s) — separate multiple times with commas

SRU–CRU link

Scanner involved?

Already tried

Result of steps tried — optional

General observations — all relevant observations from the injector system (SRU and CRU)

Logs

Attach files — select multiple: TAC/log archive plus error screenshots (.zip / .tar.gz / .log / .txt / .png / .jpg / …)

Uploading and analysing logs — this may take a minute…

A Few Questions Before the Report

The analyser needs a few additional details to produce a reliable report. Please answer the questions below based on what you observed.

Additional analysis

Not satisfied, or something missing? Add context and re-run on this session.

Safe-to-try workarounds

Only if you are happy with the analysis. Shown when confidence is ≥ 90%.

Are you happy with the analysis / answers?

Enter your feedback so developers can look into it — BETA Only — to make logsense better

What do you need? R&D

Choose a path. Spec / shall questions belong on the knowledge-base Ask tool.

R&D Ask R&D

This mode only fetches implementation-defined behaviour (source and learned rules), not spec-defined behaviour. Use it when you have a site complaint (or similar) and nothing to attach. For spec-defined behaviour, SwRS, or shall-questions, use http://go/askinject/. If you have logs or photos, go back and use R&D Analysis.

R&D Analysis R&D

When you are satisfied with the findings, generate the final report file.