ETAS ISOLAR

AutoC reads and writes ECUC configuration through ETAS RTA-CAR / ISOLAR-B. You need the ISOLAR install directory and a project path that contains .project and EcucValueCollection_Generated.arxml.

Tested versions

RTA-CAR / ISOLAR-AB
RTA-CAR 9.1.0 / ISOLAR-AB 9.1.0
RTA-CAR 9.2.0 / ISOLAR-AB 9.2.0
RTA-CAR 12.1.2 / ISOLAR-AB 12.1.2

On first use, AutoC installs the ISOLAR-B plugin automatically. No extra setup is needed in most cases.

Other platform versions

If your ISOLAR-AB / RTA-CAR version is not listed above and Verify in Project info fails, please contact us so we can evaluate support.

Open the project and set paths

1. Open a project — pick the RTA-CAR project root.
2. Open Settings → Install paths and set the ISOLAR-AB install root (it contains ISOLAR-AB_CLI.exe).
3. Open Settings → ETAS ISOLAR and fill in what you need:

Field	Value
Project path	Folder with .project; usually the open project
OS project (RTA-OS)	Optional; standalone OS .rtaos file (may live outside the ETAS project; not a folder). When set, merged with Os already in ISOLAR
Data ARXML	Optional exclude patterns; leave empty to scan all .arxml under the ETAS project (skips paramdefs/; ASW excluded)
External modules	Optional; EB+ETAS mixed projects — Configuration sync
Auto-assign params	Optional; param SHORT-NAMEs auto-assigned at generate (e.g. CanIfTxPduId)

4. Click Save, then Reload.

Success: an ETAS card under Project → Project info. Use Verify or Generate on a module (save runs first). For mixed projects, Save MCAL on the EB card.

Advanced

Data ARXML — ECUC value files used when chat edits parameters. Always discovered under the ETAS project path. Skip unwanted paths with exclude patterns on Settings → ETAS ISOLAR → Data ARXML. Different scan root from ASW (the open project) — see ASW.

OS project (RTA-OS) — Some projects configure Os in a standalone OS project. Set Settings → ETAS ISOLAR → OS project (RTA-OS) to the .rtaos file. AutoC loads every ARXML listed there and merges it with Os already in ISOLAR. For ISOLAR to validate the Os you just edited, that ARXML must already be in the ISOLAR project (linked or the same file).

Auto-assign params — Some scalar parameters fail Verify with missing values, but ISOLAR assigns them at Generate; do not set them by hand (e.g. CanIfTxPduId).

• Symptom: Verify in Project info reports multiplicity / missing-value errors while the field stays empty in ISOLAR until generate.
• Configure: Settings → ETAS ISOLAR → Auto-assign params, then save and reload.
• Effect: Those parameters drop out of the editable list; Verify ignores missing-value errors for them.

Still failing: Troubleshooting.

Configuration sync

In mixed projects, EB configures MCAL and ETAS configures the RTA-CAR stack. Unlike DaVinci, you must declare External modules on the ETAS side so Save on an EB module in Project info can sync MCAL into ETAS ECUC ARXML.

1. Set paths as above and in EB tresos, then save and reload
2. Open Settings → ETAS ISOLAR → External modules and enter ETAS module config names (e.g. Can_0, not the EB name Can_43_FLEXCAN)
3. Edit EB MCAL, then Save that EB module in Project → Project info

What you change	In Project info
EB MCAL listed under External modules	EB module Save (syncs ETAS ECUC ARXML)
ETAS-owned stack (EcuC, CanIf, PduR …)	ETAS module Verify or Generate

Module config names may differ (EB Can_43_FLEXCAN ↔ ETAS Can_0), but container SHORT-NAMEs should match (e.g. CanConfigSet_0) — sync writes by container path.

	Notes
Use	ETAS module config SHORT-NAME from ETAS_Project.arxml or *_EcucValues.arxml
Not	EB plugin names (e.g. Can_43_FLEXCAN)
vs Exclude modules	External modules = not loaded by ETAS, but ARXML mirror target for EB save

Missing Java compiler

Most users can skip this. Follow it only if AutoC reports that no Java compiler was found.

Check the Java that ships with ISOLAR first, then download a matching JDK.

1. Check ISOLAR’s Java version (replace with your install path):

# Try this first (common on 9.2 / 12.x)
& "C:\ETAS\RTA-CAR_x.x.x\ISOLAR-AB_x.x.x\javalibs\jdk\bin\java.exe" -version

# If that path does not exist (common on 9.1, jre only)
& "C:\ETAS\RTA-CAR_x.x.x\ISOLAR-AB_x.x.x\jre\bin\java.exe" -version

Note the major version, e.g. 1.8.0_… → 8, 11.0.x → 11.

2. Download and install a JDK with the same major version (must include javac, not a JRE-only package):

Version you saw	Download
8 (1.8.0_…)	Eclipse Temurin 8
11	Eclipse Temurin 11

If -version fails or the output looks wrong, install JDK 8.

3. Set JAVA_HOME to the JDK install folder (it must contain bin\javac.exe).

Temporary (current PowerShell window only):

$env:JAVA_HOME = "C:\Program Files\Eclipse Adoptium\jdk-8.0.xxx-hotspot"

Permanent (then open a new terminal and restart AutoC):

setx JAVA_HOME "C:\Program Files\Eclipse Adoptium\jdk-8.0.xxx-hotspot"

4. Confirm and retry:

& "$env:JAVA_HOME\bin\javac.exe" -version

Start AutoC again, or click Verify in Project info (that installs the plugin).