Tutorial: your first controller
This tutorial takes you from nothing installed to a motor start/stop program running on your laptop, with a live screen in your browser. It takes about an hour. You do not need any hardware.
You will:
- Install VS Code, the nautilus extension and the
nautcommand. - Create a project.
- Write a motor start/stop seal-in in ladder.
- Test it.
- Run it and use the built-in dashboard in your browser.
- Watch and force tags live in VS Code.
- Add a small Structured Text program.
- Build a simple operator screen (HMI).
- Build one file you can copy to a controller.
Each step is one action. Each says what you should see. If you do not see it, go to When something goes wrong at the end.
You need a computer running macOS, Windows or Linux and an internet connection.
Words used here:
- Controller: the program that runs your logic in a loop. nautilus runs it on your laptop.
- Scan: one pass of that loop. Here, one scan takes 100 ms.
- Tag: a named value, such as
MotorRun. - Terminal: the window where you type commands. On macOS it is Terminal. On Windows it is PowerShell. VS Code has one built in.
Part 1. Install
Section titled “Part 1. Install”1.1 Install VS Code
Section titled “1.1 Install VS Code”- Go to https://code.visualstudio.com/ and download VS Code for your system.
- Install it and open it.
You should see the VS Code welcome page.
1.2 Install the nautilus extension
Section titled “1.2 Install the nautilus extension”- In VS Code, click the Extensions icon on the left (four squares), or
press
Ctrl+Shift+X(macOS:Cmd+Shift+X). - In the search box, type
nautilus IEC 61131-3. - Click Install on the result named nautilus IEC 61131-3 by
joyauto. - A window asks Do you trust the publisher “joyauto”? Click Trust Publisher & Install.
- Click the result’s name to open its page.
You should see the extension’s page with an Uninstall button.
1.3 Install the naut command
Section titled “1.3 Install the naut command”naut is the nautilus tool. It creates, tests and runs projects. The
extension can install its own copy, but that copy is only for VS Code. You
need naut in a terminal too, so install it as follows.
- Open VS Code’s terminal: menu Terminal, then New Terminal.
- Find your system below and paste the commands.
macOS (also works on Linux). Paste this whole block, then press Enter:
v=$(curl -fsSL https://api.github.com/repos/joyautomation/nautilus/releases/latest | grep '"tag_name"' | cut -d'"' -f4)os=$(uname -s | tr A-Z a-z)arch=$(uname -m)[ "$arch" = x86_64 ] && arch=amd64[ "$arch" = aarch64 ] && arch=arm64curl -fsSLO "https://github.com/joyautomation/nautilus/releases/download/$v/nautilus_${v#v}_${os}_${arch}.tar.gz"tar xzf "nautilus_${v#v}_${os}_${arch}.tar.gz" nautsudo install -d /usr/local/binsudo install naut /usr/local/bin/nautThe last two lines ask for your computer password. Nothing appears while you type it. That is normal. Type it and press Enter.
Windows (PowerShell). Paste this whole block, then press Enter:
$v = (Invoke-RestMethod https://api.github.com/repos/joyautomation/nautilus/releases/latest).tag_name$arch = if ($env:PROCESSOR_ARCHITECTURE -eq "ARM64") { "arm64" } else { "amd64" }Invoke-WebRequest "https://github.com/joyautomation/nautilus/releases/download/$v/nautilus_$($v.TrimStart('v'))_windows_$arch.zip" -OutFile nautilus.zipExpand-Archive nautilus.zip -DestinationPath "$env:LOCALAPPDATA\nautilus" -Force[Environment]::SetEnvironmentVariable("Path", "$env:LOCALAPPDATA\nautilus;" + [Environment]::GetEnvironmentVariable("Path", "User"), "User")Then close the terminal and open a new one. Windows only reads the new
Path in a new terminal.
- Type this and press Enter:
naut versionYou should see a line like nautilus 0.19.0. If you see “command not
found” or “not recognized”, see
naut: command not found.
The same archives are on the
release page
if you would rather download by hand. The command is naut, not
nautilus, because many Linux desktops already have a file manager with
that name.
Part 2. Create a project
Section titled “Part 2. Create a project”- In the terminal, go to a folder for your work. For example:
cd ~/Documents- Create the project:
naut new motor --template minimal --language ldYou should see created motor/ — a manifest project, no Go required
and a short list of next steps.
- In VS Code, choose File, then Open Folder… (macOS: File, then
Open…). In the Open Folder window, pick the
motorfolder inDocumentsand click Open. - If VS Code asks Do you trust the authors of the files in this folder?, click Yes, I trust the authors. You made the folder a moment ago.
- If VS Code offers to install recommended extensions, click Install.
You should see these files in the Explorer on the left, among a few
others (README.md, AGENTS.md, CLAUDE.md, .gitignore and the
.github and .vscode folders):
nautilus.yaml: the project. It lists the tags and the programs.program.ld: your ladder program.motor_test.yaml: tests for your program.
Part 3. Write the motor start/stop
Section titled “Part 3. Write the motor start/stop”A motor start/stop uses a seal-in. The Start button turns the motor on. The motor’s own output then holds itself on, through a contact in parallel with Start. The Stop button breaks the rung and the motor drops out.
3.1 Declare the tags
Section titled “3.1 Declare the tags”- Click
nautilus.yamlin the Explorer. - Select everything (
Ctrl+A, macOSCmd+A) and replace it with:
name: motor
server: addr: "localhost:8080" online-edits: true
tasks: - program: program.ld scan: 100ms
tags: - { name: StartPB, role: setpoint, type: BOOL, init: false, desc: Start button (press = TRUE) } - { name: StopPB, role: setpoint, type: BOOL, init: false, desc: Stop button (press = TRUE) } - { name: MotorRun, role: output, type: BOOL, init: false, desc: Motor contactor }
driver: type: memory- Save (
Ctrl+S, macOSCmd+S).
What this says:
- There is one program,
program.ld. It runs every 100 ms. StartPBandStopPBare the two buttons. They aresetpointtags, so you can click them from a dashboard. A real button would be aninputtag wired to a field device.MotorRunis anoutput. The program writes it.driver: memorymeans there is no hardware. The tags live in memory.
3.2 Write the rung
Section titled “3.2 Write the rung”- Click
program.ld. - Replace everything with:
PROGRAM MotorLD RUNG seal_in (* Start or already running, and Stop not pressed *) [ StartPB | MotorRun ] /StopPB ( MotorRun )END_LDEND_PROGRAM- Save.
Read the rung from left to right:
[ StartPB | MotorRun ]is two contacts in parallel. Power passes ifStartPBis TRUE orMotorRunis TRUE./StopPBis a normally closed contact. Power passes ifStopPBis FALSE.( MotorRun )is the coil. It turnsMotorRunon when power reaches it.
3.3 See it as a ladder diagram
Section titled “3.3 See it as a ladder diagram”- Right-click the
program.ldtab at the top. - Choose Reopen Editor With…, then, in the list that appears, Ladder Diagram.
You should see the rung drawn with contacts and a coil, and a yellow offline pill at the top right (it turns green when a controller is running, in Part 5). To see the text, click Show Source in the editor’s title bar (the icon with a file and an arrow). The text opens beside the diagram.
3.4 Check it
Section titled “3.4 Check it”- In the terminal, make sure you are in the
motorfolder. VS Code’s Terminal, then New Terminal opens there. - Type:
naut check .You should see naut check: 1 file(s), 0 with errors.
To see an error, click Show Source to open the text, change StartPB in
the rung to StartPBX, save, and look at the Problems panel (menu
View, then Problems). You should see undeclared identifier "StartPBX". Change it back and save.
Part 4. Test it
Section titled “Part 4. Test it”Acceptance tests describe what the program must do. They run on a virtual clock, so they finish in milliseconds.
- Click
motor_test.yaml. - Replace everything with:
tests: - name: start button starts the motor and it stays on steps: - given: { StartPB: true } scans: 1 expect: { MotorRun: true } - given: { StartPB: false } scans: 1 expect: { MotorRun: true } # sealed in
- name: stop button drops the motor out steps: - given: { StartPB: true } scans: 1 - given: { StartPB: false } scans: 1 - given: { StopPB: true } scans: 1 expect: { MotorRun: false } - given: { StopPB: false } scans: 1 expect: { MotorRun: false } # stays off until Start- Save.
- In the terminal, type:
naut test -v .You should see two lines starting with ok, then 2 tests, 2 passed, 0 failed.
Each step says: set these tags (given), run this many scans (scans),
then check these tags (expect).
To see a failure, change MotorRun: true on the first expect to
MotorRun: false, save and run naut test . again. You should see a
failed test that says what it expected and what it got. Change it back.
Part 5. Run it and open the dashboard
Section titled “Part 5. Run it and open the dashboard”- In the terminal, type:
naut runYou should see:
nautilus · motor — dashboard + tag API on http://localhost:8080 — Ctrl+C to stopThe terminal stays busy. That is correct. The controller is running. Leave it running for the rest of Parts 5 to 7.
- Open a web browser and go to http://localhost:8080.
You should see the nautilus dashboard. Scroll to Live tags. You should
see StartPB, StopPB, MotorRun and the values false.
- In the Live tags table, click the toggle next to
StartPB.
You should see StartPB turn on and MotorRun turn on.
- Click the
StartPBtoggle again to turn it off.
You should see StartPB off and MotorRun still on. That is the
seal-in.
- Click the
StopPBtoggle on.
You should see MotorRun turn off.
- Click the
StopPBtoggle off.MotorRunstays off.
To stop the controller, click in the terminal and press Ctrl+C.
Part 6. Watch and force tags in VS Code
Section titled “Part 6. Watch and force tags in VS Code”Keep naut run going. If you stopped it, start it again.
6.1 Watch values live
Section titled “6.1 Watch values live”- In VS Code, open
program.ldas a ladder diagram (Part 3.3).
You should see the rung with live values and power flow. Wires that carry
power are highlighted. The status bar at the bottom right says nautilus:
live and the diagram has a green live pill. The project already points
at http://localhost:8080, so VS Code connects by itself.
- If you see offline instead, press
Ctrl+Shift+P(macOSCmd+Shift+P), typenautilus: Connect to Controller, and press Enter to accepthttp://localhost:8080. A message says nautilus: connected. - In the browser dashboard, click the
StartPBtoggle on and off.
You should see the rung light up in VS Code. After StartPB goes off, the
MotorRun contact keeps the rung lit.
6.2 Open the Live Values panel
Section titled “6.2 Open the Live Values panel”- Click the nautilus icon in the Activity Bar on the left (three horizontal lines).
You should see NAUTILUS: LIVE VALUES with a Tags group that lists every tag and its value.
6.3 Set a value
Section titled “6.3 Set a value”The motor is running after step 6.1. Stop it from VS Code.
- In the Live Values list, point at
StopPB. A lock and a pencil appear at the right of the row. Click the pencil. - Type
trueand press Enter.
You should see a message nautilus: set StopPB = TRUE and MotorRun go
off.
- Click the pencil next to
StopPBagain, typefalse, and press Enter.
A normal write happens once. The next write, from the dashboard or from the logic, replaces it.
6.4 Force a value
Section titled “6.4 Force a value”A force holds a tag at a value until you remove it. Technicians use forces to test an interlock before the real sensor is wired.
- In the dashboard, click the
StartPBtoggle on, then off. The motor runs again. - In VS Code, open
program.ldas text: click Show Source in the diagram’s title bar. If the text is too narrow to read, close the diagram on the left. - Right-click
StopPBin the rung. - Choose nautilus: Force…, type
true, and press Enter. A window asks Force StopPB (now FALSE) to TRUE on http://localhost:8080? Click Force.
You should see MotorRun go off, an amber F TRUE next to StopPB, a
Forces group in the Live Values list, and 1 force active in the
status bar at the bottom. The force holds StopPB at true, so the rung
cannot pass power.
- In the dashboard, click the
StartPBtoggle on.
You should see StartPB change but MotorRun stay off. Now try the
StopPB toggle. The controller refuses the write, because the tag is
forced.
- Click 1 force active in the status bar. In the list, choose Remove all forces, then click Remove All in the window that asks.
You should see the F TRUE disappear. StartPB is still on, so the motor
starts.
- In the dashboard, click the
StartPBtoggle off, then click theStopPBtoggle on and off. The motor ends up stopped.
Part 7. Add a Structured Text program
Section titled “Part 7. Add a Structured Text program”Structured Text (ST) is the text language of IEC 61131-3. You will add a second program that counts how many times the motor started. Ladder and ST can run side by side in one project.
7.1 Add the program
Section titled “7.1 Add the program”- In VS Code, choose File, then New Text File. Paste:
PROGRAM StatsVAR started : R_TRIG; (* TRUE for one scan when the motor starts *) starts : CTU; (* counts those scans *)END_VAR
started(CLK := MotorRun);starts(CU := started.Q, R := FALSE, PV := 32767);MotorStarts := starts.CV;END_PROGRAM- Save it as
stats.stin themotorfolder (Ctrl+S, macOSCmd+S).
R_TRIG is a rising-edge detector. It is TRUE for one scan when MotorRun
goes from off to on. CTU is an up-counter. It counts those pulses.
7.2 Tell the project about it
Section titled “7.2 Tell the project about it”- Click
nautilus.yaml. - Under
tasks:, add a second program, so it reads:
tasks: - program: program.ld scan: 100ms - program: stats.st scan: 100ms- Under
tags:, add one more line afterMotorRun:
- { name: MotorStarts, role: output, type: INT, init: 0, desc: Starts since power-up }- Save.
7.3 Add a test
Section titled “7.3 Add a test”- Click
motor_test.yaml. - Add this at the end of the file:
- name: every start is counted steps: - given: { StartPB: true } scans: 3 expect: { MotorStarts: 1 } - given: { StartPB: false, StopPB: true } scans: 3 expect: { MotorStarts: 1 } - given: { StartPB: true, StopPB: false } scans: 3 expect: { MotorStarts: 2 }- Save. Stop the controller if it is running (
Ctrl+Cin its terminal). - Run the tests:
naut test .You should see 3 tests, 3 passed, 0 failed.
7.4 Run it again
Section titled “7.4 Run it again”- Type
naut run. - Reload http://localhost:8080.
- Toggle
StartPBon, off, thenStopPBon, off, andStartPBon, off.
You should see MotorStarts count to 2. Press Ctrl+C in the terminal
when you are done.
To see the tags next to your ST code, open stats.st while the controller
is running. Each name shows its live value.
Part 8. Build a simple operator screen
Section titled “Part 8. Build a simple operator screen”The dashboard is for engineers. An operator screen (HMI) shows what the operator needs and nothing else. There are two ways to make one, and you need no code for the first. This part draws it: a motor symbol with Start and Stop buttons. Part 8.5 onward is the second way, a small web page in Svelte, for when a drawing is not enough. You can stop after 8.4.
8.1 Draw the screen
Section titled “8.1 Draw the screen”A screen is a file that ends in .mimic.json (a mimic is a process
diagram, the plant drawn as it is laid out). It lists what is on the screen,
where, and which tag each thing shows or writes. naut builds it
itself: there is nothing else to install.
- In
motor, create a file namedmotor.mimic.json(right-click an empty space in the Explorer, New File…) with this content:
{ "name": "Motor M-101", "canvas": { "width": 480, "height": 300 }, "equipment": [ { "id": "M1", "component": "Pump", "x": 160, "y": 40, "width": 120, "label": "M-101", "bind": { "running": "MotorRun" } }, { "id": "Start", "component": "CommandButton", "x": 100, "y": 200, "props": { "tag": "StartPB", "label": "Start", "kind": "start" } }, { "id": "Stop", "component": "CommandButton", "x": 260, "y": 200, "props": { "tag": "StopPB", "label": "Stop", "kind": "stop" } } ]}- Save.
What this says:
canvasis the size of the drawing. The screen scales it to fit the window.- Each item in
equipmentis a built-in component placed atx,y.Pumpis the pump symbol.bindconnects a part of it to a tag:"running": "MotorRun"means the pump looks running whileMotorRunis TRUE. CommandButtonis a push button. It writestrueto itstagfor a moment, like a real push button, thenfalse. Here the buttons write theStartPBandStopPBtags your ladder reads.
8.2 Check it
Section titled “8.2 Check it”naut checkYou should see screen motor.mimic.json: 3 equipment, 0 pipes and a last
line that ends 0 with errors. naut check builds the screen the way
naut run will and checks every tag it names against nautilus.yaml. Try
it: change MotorRun to MotorRunn in the file and run it again. You get
a warning that names MotorRunn as a tag the project does not declare.
Change it back. (If a warning about small text on the Diagnostics page
also appears, that page is naut’s own, not yours: ignore it.)
If you see not rendered: no Chrome, Chromium or Edge on this machine, the
screen was still checked against your tags; it just was not drawn in a
browser to look for layout problems. Install one of those browsers, or
ignore the line.
8.3 Run it
Section titled “8.3 Run it”- Type:
naut runYou should see hmi (the project's mimics, 3 pages, …) in the first line.
The three pages are your screen, Diagnostics and Alarms, which naut
adds.
- Open http://localhost:8080.
You should see Motor M-101 in the title bar, a green Connected, the pump with its name, and two buttons, Start and Stop.
- Click Start.
You should see the ring around the pump turn from dark to light grey. The
engineering dashboard (below) or http://localhost:8080/api/state shows
"MotorRun":true.
- Click Stop.
You should see the pump go dark again.
The engineering dashboard has moved to http://localhost:8080/_nautilus/.
8.4 Change the screen
Section titled “8.4 Change the screen”- In
motor.mimic.json, changeM-101in the pump’slabelto another name and save. - Stop
naut run(Ctrl+C) and start it again, then reload the page.
You should see the new name. The operator screens guide lists every component, how to draw pipes between them, and the editor in VS Code that lets you drag the pieces instead of typing numbers.
8.5 The same screen as code (optional)
Section titled “8.5 The same screen as code (optional)”A drawing covers a lot, but not everything. When you want your own layout,
your own text, or logic in the page, a screen can be a small web app,
written in Svelte, which naut also builds itself. The rest of this part
makes the same screen that way. Skip to Part 9 if the drawing is enough.
8.6 Create the page
Section titled “8.6 Create the page”- Make a folder named
hmiinsidemotor. In VS Code, right-click an empty space in the Explorer, choose New Folder…, and typehmi. - Inside it, make the folders
src, thensrc/routes, the same way. - In
hmi/src/routes, create a file named+page.svelte(right-click the folder, New File…) with this content:
<script> import '@joyautomation/nautilus-hmi/theme.css'; import { onMount } from 'svelte'; import { Pump, StatusPill, CommandButton, createRealtimeClient } from '@joyautomation/nautilus-hmi';
const rt = createRealtimeClient({ url: '/api/stream' }); onMount(() => { rt.start(); return () => rt.stop(); });
let tags = $derived(rt.frame?.tags ?? {}); const write = (name, value) => rt.writeTag(name, value);</script>
<main> <h1>Motor M-101</h1> <StatusPill kind={rt.connected ? 'good' : 'off'} label={rt.connected ? 'live' : 'no connection'} />
<Pump running={tags.MotorRun === true} speedPct={100} label="M-101" /> <p>{tags.MotorRun ? 'Running' : 'Stopped'} · starts: {tags.MotorStarts ?? 0}</p>
<div class="buttons"> <CommandButton tag="StartPB" label="Start" kind="start" {write} /> <CommandButton tag="StopPB" label="Stop" kind="stop" {write} /> </div></main>
<style> main { max-width: 24rem; margin: 2rem auto; font-family: system-ui, sans-serif; display: grid; gap: 1rem; justify-items: start; } .buttons { display: flex; gap: 0.75rem; }</style>What the page does: it opens a live connection to the controller
(createRealtimeClient), reads MotorRun and MotorStarts from it, draws
a pump symbol, and writes StartPB and StopPB when you press the
buttons. CommandButton presses a button for 0.4 s, like a real push
button.
The folder is laid out the way SvelteKit lays out an app: each page is a
+page.svelte under src/routes (src/routes/pumps/+page.svelte is the
page at /pumps), shared components go in src/lib, and files in
static are served as they are.
8.7 Tell the controller to serve it
Section titled “8.7 Tell the controller to serve it”- Click
nautilus.yaml. - Under
server:, add a line so it reads:
server: addr: "localhost:8080" online-edits: true hmi: hmi- Save.
8.8 Run it
Section titled “8.8 Run it”- Type:
naut runYou should see dashboard replaced by hmi (hmi/, 1 page, built in …) in
the first line: naut built the screen before it started. (server.hmi
wins over any *.mimic.json drawing, so this page replaces the one you
drew above.)
- Open http://localhost:8080.
You should see Motor M-101, a green live pill, a pump symbol, the text Stopped · starts: 0, and two buttons, Start and Stop.
- Click Start.
You should see the pump turn blue and the text change to Running · starts: 1.
- Click Stop.
You should see the pump stop and the text change to Stopped.
The engineering dashboard has moved to http://localhost:8080/_nautilus/.
8.9 Change the screen
Section titled “8.9 Change the screen”- In
hmi/src/routes/+page.svelte, changeMotor M-101in the<h1>to another name and save. - Stop
naut run(Ctrl+C) and start it again, then reload the page.
You should see the new name.
To check a screen without running it, type naut hmi build. It builds the
screen the same way and lists anything wrong with it, each with its file
and line.
The screen can import Svelte, the HMI kit
(@joyautomation/nautilus-hmi), the 3D kit
(@joyautomation/nautilus-hmi-3d), three and Threlte: naut carries
those. The same hmi folder also builds with SvelteKit and npm, if you add
its package.json and config, for a package naut doesn’t carry.
Part 9. Build one file to ship
Section titled “Part 9. Build one file to ship”- Stop the controller (
Ctrl+C). - In the project folder, type:
naut build .You should see built motor — a self-contained controller. The file
motor (on Windows, motor.exe) is the whole controller, with your logic
and your screen inside. Copy it to any computer with the same operating
system and run it.
Where to go next
Section titled “Where to go next”- Run the examples: real plant projects with a full HMI, and a 3D view.
- Your first program: a sump pump with a timer, written in Structured Text.
- Ladder, Structured Text, Function Block and SFC reference.
- Forcing and Testing.
- The HMI kit: every component you can put on a screen.
When something goes wrong
Section titled “When something goes wrong”naut: command not found
Section titled “naut: command not found”- Windows: you did not open a new terminal after installing. Close
every terminal and open a new one. If it still fails, run
$env:LOCALAPPDATA\nautilus\naut.exe version. If that works, the file is there and thePathsetting did not stick. Run the last line of the Windows install block again, then open a new terminal. - macOS: the install block needs your computer password. If you cancelled it, run the block again. If you do not have administrator rights, install into your home folder instead:
mkdir -p ~/bin && mv naut ~/bin/ && echo 'export PATH="$HOME/bin:$PATH"' >> ~/.zshrcThen open a new terminal.
- Any system:
nauthas to be in the same terminal you are typing in. VS Code’s own terminal (Terminal, New Terminal) is the safest choice.
macOS says “naut cannot be opened” or “Apple could not verify”
Section titled “macOS says “naut cannot be opened” or “Apple could not verify””The naut binary is not signed with an Apple developer certificate.
Downloading it with the curl commands above avoids the warning. If you
downloaded it with a browser and macOS blocks it, remove the quarantine
flag:
xattr -d com.apple.quarantine /usr/local/bin/nautOr open System Settings, then Privacy & Security, scroll to the
message about naut, and click Allow Anyway. Then run naut version
again and click Open when macOS asks.
Windows says “Windows protected your PC” or the file is blocked
Section titled “Windows says “Windows protected your PC” or the file is blocked”naut.exe is not signed with a Windows publisher certificate. If you
downloaded the zip in a browser, Windows marks it as from the internet.
Either click More info, then Run anyway, or unblock it once:
Unblock-File "$env:LOCALAPPDATA\nautilus\naut.exe"The PowerShell block in Part 1 downloads without that mark, so it does not normally appear.
Windows Defender Firewall asks about naut
Section titled “Windows Defender Firewall asks about naut”The controller listens only on localhost, so you can click Cancel or
allow Private networks only.
VS Code says it cannot start the language server
Section titled “VS Code says it cannot start the language server”The extension looks for naut itself. On macOS, VS Code started from the
Dock does not see the same PATH as your terminal. Fix it one of these
ways:
- Press
Ctrl+Shift+P(macOSCmd+Shift+P) and runnautilus: Install or Update the naut CLI. The extension keeps its own copy. - Or set the full path. Run
which naut(Windows:where.exe naut) in a terminal. Open VS Code Settings, search fornautilus.cliPath, and paste the path. - Or close VS Code and start it from a terminal with
code .in the project folder.
“address already in use” when running
Section titled ““address already in use” when running”Something else is using port 8080. naut run then moves to the next free
port and says which (tag api: localhost:8080 is in use ..., so this one is on localhost:8081); use that port in the addresses in this tutorial.
To pick the port yourself, change addr: "localhost:8080" in
nautilus.yaml to another, such as addr: "localhost:8090".
The test says “no tag MotorRun in this project”
Section titled “The test says “no tag MotorRun in this project””The tag is not declared in nautilus.yaml, or the name differs in spelling
or capital letters. Names are case sensitive.
The program faults with “undefined tag”
Section titled “The program faults with “undefined tag””A program read a tag before anything wrote it. Give every tag you read an
init: value in nautilus.yaml, as this tutorial does.
The screen shows “no connection”
Section titled “The screen shows “no connection””The controller is not running, or the screen is talking to a different
port. Start naut run and reload.
nautilus is free and open source (Apache 2.0), built by Joy Automation. For implementation or support on your site, see Joy Automation services. Privacy.