Launch the ARSAS IEC 61850 Learning Center and SEO entry paths - #117
Merged
Conversation
masarray
marked this pull request as ready for review
July 29, 2026 01:07
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1b58970bd0
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| <section class="section section-tight" id="checklist"><div class="container comparison-grid"><article class="comparison-panel highlight"><span class="kicker">Before you start</span><h2>Collect four facts.</h2><ul><li>The approved IED IP address</li><li>The subnet mask and required gateway or route</li><li>Whether IEC 61850 MMS service is enabled on TCP port 102</li><li>Permission to connect from this engineering workstation</li></ul></article><article class="comparison-panel"><span class="kicker">Safety boundary</span><h2>Start read-only.</h2><p>Discovery and live monitoring should be separated from active control. Do not operate a breaker, change RCB configuration or modify the IED unless the procedure, authority and rollback plan explicitly permit it.</p></article></div></section> | ||
|
|
||
| <section class="section"><div class="container"><div class="section-head center"><span class="kicker">Step-by-step</span><h2>From IP address to one attributable value.</h2></div><div class="step-list"><article class="step"><span class="step-number">01</span><div><h3>Confirm the target and authority</h3><p>Record the IED name, IP address, bay or function, expected vendor/model and the approved purpose of the connection. This prevents a successful connection to the wrong device from being treated as success.</p></div></article><article class="step"><span class="step-number">02</span><div><h3>Prepare the Windows network interface</h3><p>Use an address in the approved subnet, or an approved routed path. Avoid changing plant network settings by trial and error. Keep the original adapter configuration so it can be restored.</p></div></article><article class="step"><span class="step-number">03</span><div><h3>Separate ping from IEC 61850 service</h3><p>Ping can prove basic IP reachability, but MMS uses TCP port 102. A device may answer ping while the service is disabled, blocked by a firewall or unavailable to your client.</p><div class="section-actions"><a class="btn" href="port-102-connection-failed.html">Troubleshoot port 102</a></div></article><article class="step"><span class="step-number">04</span><div><h3>Open ARSAS and choose General IEC 61850 Testing</h3><p>Select <strong>Add IED</strong>, then enter a clear device name, the approved IP address and TCP port 102 unless the project explicitly uses another endpoint.</p></div></article><article class="step"><span class="step-number">05</span><div><h3>Connect and wait for live discovery</h3><p>ARSAS establishes the MMS association and reads the server model. Do not judge success only from the TCP connection; confirm that Logical Devices, Logical Nodes, Data Objects and DataSets are actually discovered.</p></div></article><article class="step"><span class="step-number">06</span><div><h3>Read one point correctly</h3><p>Choose a familiar indication or measurement. Check the IED identity, full IEC reference, current value, quality, device timestamp and acquisition source. Capture diagnostics before changing anything when one field is missing or unexpected.</p></div></article></div></div></section> |
There was a problem hiding this comment.
When a user follows step 04, the Add IED dialog provides fields only for the runtime IP address and MMS port; it explicitly discovers the IEDName from the live model (IpConnectWizardWindow.xaml:36-51). Telling users to enter a clear device name therefore sends them looking for a control that does not exist and misrepresents how endpoint identity is established. Update this step and its Indonesian translation to explain that ARSAS resolves the device name during discovery.
Useful? React with 👍 / 👎.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Turn the ARSAS website into a useful search destination that sells the product, teaches the software and explains IEC 61850 in plain language without weakening engineering boundaries.
P0 — information architecture
learningandtutorialroles to the contextual search-authority engineP1 — benefit-led home pages
Rewrites the English and Indonesian home pages around user intent:
The hero now leads with the outcome:
Protocol terms such as MMS, Reporting, GOOSE and SCL appear after the benefit statement and link to the appropriate learning depth.
New bilingual SEO pages
Adds six canonical pages:
learning-center.htmlpusat-belajar-iec61850.htmlwhat-is-iec61850.htmlapa-itu-iec61850.htmlconnect-ied-ip-arsas.htmlcara-hubungkan-ied-ip-arsas.htmlLearning Center
What is IEC 61850?
Connect an IED by IP in ARSAS
SEO and localization
Engineering honesty
The learning pages separate observation, inference and independent verification. They do not claim that ARSAS replaces an approved FAT procedure, IED documentation, calibrated test equipment, plant authority or IEC 61850 conformance testing.
Automated validation at head
1b58970bd0e65df81701fcad321e0d5224fc3fefDeploy product website run 156 — success
Validate adoption and field proof run 48 — success
Build search growth queue run 57 — success
Build ARSAS run 774 — success
Additional gates — success