If ARStack Studio opens an SCL file but does not show the SV ID, multicast MAC or publisher configuration you expected, these steps help narrow down what happened.
Download the latest stable release. Check the installed version in Studio before comparing behavior with other engineering tools.
Use Open SCL with your .scd, .cid, .icd or .iid file. Successful XML import tells you the file was read; it does not automatically select an SV publisher or deploy it to the board.
Look for the file's IED, AccessPoint, logical device, SV control block and DataSet. If the file contains several publishers, select the intended SV stream before evaluating its fields.
For a stream configured in SCL, svID is commonly associated with SampledValueControl, while multicast MAC address and APPID appear in the relevant Communication/ConnectedAP/SMV/Address mapping. A valid file can have more than one candidate stream.
If the SV ID or MAC is blank, inspect the Studio stream selection and validation messages. A file that opens successfully might still lack a selectable deployment profile in the current reference workflow.
Choose 4I+4V Quick Start and verify that the supported SV publisher profile appears. This is a useful comparison against the imported SCL. For real network output, firmware on the ESP32-P4 must match the Studio release.
If the SV fields still do not appear:
- Note the ARStack Studio version and which SCL IED / stream you selected.
- Capture a screenshot of the import result and any validation messages.
- Share the smallest sanitized SCL file that reproduces the behavior, either through the bug report form or a private message/link to the maintainer when you are already in contact.
Remove project names, substation identifiers and other confidential engineering data before sharing files. We welcome files generated by different IEC 61850 engineering environments because they help make import workflows easier for everyone.