Help Center · 24/5 engineer-backed support

Expert support for safety-critical testing

Backed by engineers who know ISO 26262, DO-178C, and your target hardware. From license setup to MC/DC interpretation on a constrained RTOS, you reach people who have shipped rigorous coverage, not a script reader.

Open a Ticket Contact Channels

We speak your standard

DO-178CAvionics ISO 26262Automotive IEC 61508Industrial

Support snapshot 24/5 online

First response<4h

P1 / critical<1h

ResolutionHigh

24/5

coverage

Live

desktop sessions

+91

phone & email

Get help fast

Start with self-serve, escalate when you need a human

Most questions are answered in the docs and tutorials. When you hit a target-specific or certification-specific wall, open a ticket and an engineer takes it from there.

Documentation

Install guides, CLI references, CI recipes and toolchain notes for every supported target.

FAQ & knowledge base

Answers to the questions teams ask most, licensing, target setup, coverage metrics and CI gating.

Open a ticket

Raise a support request with your version and target. An engineer who knows your standard responds.

Coverage & SLAs

Support sized for certification timelines

When an audit deadline is closing in, you cannot wait on a queue. Here's what RKValidate support commits to.

24/5 coverage

Engineer-staffed support across business hours, Monday through Friday, spanning major time zones.

Fast first response

Target first-response times measured in hours, typically under 4 hours for standard tickets.

Critical / P1 handling

Build-blocking and certification-crunch issues are prioritized for rapid engineer attention.

Live desktop sessions

Online desktop-sharing sessions to debug instrumentation, transports and coverage gaps together.

Response targets are guidance and may vary by support plan, severity and region. Talk to us about a plan that matches your program.

Open a ticket

Tell us what's happening, we'll route it to the right engineer

The more we know about your version, target and toolchain, the faster we can reproduce and resolve. Critical issues during a certification crunch are flagged for priority handling.

Include your RKTracer version and target environment
Attach compiler/cross-compiler and CI details where relevant
Set the right severity so urgent issues jump the queue

Prefer email? Reach support directly at support@rkvalidate.com and we'll create the ticket for you.

Open a support ticket

Submit your request and you'll get a unique ticket ID by email, with a private link to track the conversation and reply. No account needed.

Submit a ticket Track an existing ticket

Unique IDRKT-YYYY-XXXXXX Email + trackingno login required Attachmentslogs & reports

Knowledge base

Frequently asked questions

The fastest answers to the things teams ask most. For anything target- or standard-specific, open a ticket.

After downloading the trial, run the activation command with the key emailed to you, or point RKTracer at your floating-license server for team installs. Air-gapped and node-locked licenses are supported, if activation fails, send the generated request file to support@rkvalidate.com and we'll issue an offline license.

RKTracer instruments through your existing cross-compiler, so there's no separate on-device install. For targets with no file system, configure a transport, SWO, JTAG, UART or a RAM buffer, and coverage streams off the device. See the Documentation for per-toolchain (GCC, IAR, Keil, Green Hills, TI) setup recipes.

An MC/DC-covered decision means each condition has been shown to independently affect the decision's outcome. RKTracer's HTML report lists the specific condition pairs still needed to close any gap, and its AI test generation can synthesize cases that target exactly those uncovered combinations. For DAL-A / ASIL-D evidence questions, an engineer can walk through your report on a live session.

Add RKTracer's build, run, cover, report and gate steps to your pipeline. It emits HTML, XML, SonarQube and JUnit-style output, and the gate step fails the build below your coverage threshold (for example, MC/DC 100%). Recipes for Jenkins, Azure DevOps, GitLab CI and Bamboo are in the Documentation.

All compilers and cross-compilers, GCC, IAR, Keil/ARM, Green Hills, TI, and more, across 12 languages from bare-metal C to Rust and Swift. If you use a specialized toolchain, open a ticket with the compiler name and version and we'll confirm support.

Contact channels