Go beyond the result.
Understand the test.

Communication Studio works with configured devices in a common workspace. Connect to the selected device, use supported smart actions, send a command and inspect transmit/receive history. Cyclic operations and Byte Lab help investigate repeated traffic and interpret values with the required byte order and scaling.

Communication Studio Inside the software

Enlarge

Configure maintenance items, counters and service limits in Fixture Maintenance. Review which items are due, perform the required work and use the authorised verification or reset action to update their status.

The history records counter and maintenance activity for later review. Confirm any configured due-action or production hold before returning the fixture to use; changing a counter does not itself prove the physical work was performed.

Service Records keeps the service session, engineer, work summary, type, status and follow-up information together. Use it to document an investigation, record the work performed and close out the session with the relevant findings.

Filter and review available service analytics and permitted exports when investigating recurring issues. Fixture counters describe maintenance usage and due status; service records describe the work and its follow-up.

Prepare saved bus operations and cyclic communication using supported adapters. CAN Analyzer / UDS brings diagnostic traffic, supported DBC decoding, signal views and trace evidence into the investigation workflow.

Choose the relevant CAN/analyzer or LIN entitlement and confirm adapter compatibility. Message definitions and diagnostic procedures remain specific to the product being tested.

The CAN Calibration workspace combines configured steps, parameters and calculations with the supported communication and diagnostic operations. Review the preview and monitored responses against the approved calibration method before use on a product.

Calibration requires its own entitlement; that entitlement includes CAN access. The software workflow still needs the product procedure, compatible interface and reference conditions appropriate to the measurement.

Custom CRC provides a specialist workspace for supported C# checksum methods, parameters and byte data, with related tables, timers and reusable packages. Use known test vectors to establish the expected output before relying on a method in communication or programming.

Custom CRC requires the relevant licence. Method development and imported packages require an engineering review.

General Programming stores the provider configuration around the approved programming tool and target. Specify the tool path, firmware or project inputs, timeout, expected replies and relevant checksum settings. Readiness checks identify required items before execution, and tool output supplies evidence for the result.

General Programming and UDAQ firmware programming are specialist licensed capabilities. The latter is separate from ordinary UDAQ relay or I/O control.

Vision profiles organise regions, segments, masks and groups around the image areas that matter. Select supported checks, set thresholds and compare results with reviewed reference samples.

Optics, lighting, exposure, fixture repeatability and calibration are part of the inspection configuration. Validate representative good and failing products on the actual camera setup.

Configure a supported Windows/shared, LAN, COM or file-drop print route. Label workflows include designer/PRN and supported raw TSPL, ZPL or EZPL formats. Log-only or dry-run operation helps review the intended output before physical printing.

Set the applicable serial-counter scope, collision handling and PASS, FAIL or other configured trigger for the plan/DUT. Label-scan verification can hold the workflow until the configured check is satisfied.

Printer access requires the appropriate licence and a compatible route. Confirm the rendered label, scanner readability and serial behaviour with the intended printer and media.

The licensed wiring workspace supports schematics, panel and fixture sheets with component libraries, pins, connections, junctions and labels. Panel work can use scaled dimensions, DIN rails, ducts and mounting clearances; fixture work can record pin and cable-core mappings.

• Review connections, no-connect markers and the relevant design checks.
• Use supported numbering and BOM, wire, cable, terminal or continuity exports.
• Prepare review packages and revision records for the design.
• Use the released/read-only state where the reviewed project requires it.

These tools help maintain engineering documentation alongside the station. Electrical design approval and comparison with the built fixture remain part of the project’s verification.

Open Admin / Testing → Health to run a health check and review the Machine Health findings. The AI Preventive Advisor presents guidance based on the available report; use it to prioritise investigation and maintenance rather than treating it as a guarantee of fault prediction.

Failure Forensics Evidence retains diagnostic context for investigation. Authorised users can refresh the evidence, manage its retention and export the available health or support package. Review the evidence alongside actual station behaviour before deciding on corrective work.

Application Log contains Activity Log, Debug Log, Advanced Audit and Test Log. Activity Log connects recorded actions to user sessions and saved setting changes; Debug Log and Test Log help investigate technical messages, exceptions and test events.

Use the relevant search, date and type filters and permitted export tools. Requested actions and confirmed saved changes are distinct records. Old and new field values are available where a change was recorded.

Create and maintain user accounts with the appropriate role and employee details. Enable or disable access and assign the permitted pages and actions for operation, maintenance or configuration work.

Review permissions together with the issued licence and station responsibilities. Use Activity Log to inspect recorded changes to settings; a role name alone does not mean every action is available.

General settings hold station and machine identity and the applicable execution, result, operator-flow and diagnostic policies. Shift Master maintains the configured shift definitions used by the production setup.

Report settings define the output root, folder and filename templates and supported formats. Check the configured shift times, report paths and record association with a representative run before production handover.

Configure the backup destination and available automatic backup settings, and use the manual database backup action when required. Review backup availability before service work or an update.

Use the Web Installer for a new installation and the in-app Update page for an existing installation. Review the release information and follow the approved backup, verification and recovery procedure. Confirm the station’s configuration, retained records and required customer files after maintenance.

RAJU BROS AI Assistance (Beta)

The licensed sequence-assistance workflow can help draft content from supported documents or structured inputs such as CSV/workbooks. Review the proposed device mappings, commands, limits and timing before incorporating a draft into an executable flow.

Assistance is a starting point for engineering work. It does not validate the hardware, approve a specification or replace the staged testing of a sequence.