When something goes wrong
Most first-hour problems are one of four kinds. Each tool says where.
The program does not compile: naut check
Section titled “The program does not compile: naut check”naut check prints one line per problem, with the file, line and column:
program.st:12:5: undeclared identifier "LevelPc"Read it from the left: which file, where in it, what is wrong. The usual
causes are a misspelt tag or variable name, a type mismatch (cannot assign REAL to BOOL), or a missing ;. Fix the first one and run naut check
again; later errors are often caused by the first.
naut check is also what your continuous integration runs, so a project
that passes it locally passes there.
A test names something that does not exist: naut test
Section titled “A test names something that does not exist: naut test”sump_test.yaml:5 — given: no tag "Sensor" in this projectA test can only set and check tags the project declares. The name in the
test must match a name: in nautilus.yaml exactly. When a test fails an
expectation, it shows the line of the expectation, the virtual time, and
the value the tag really had, with a short history of it, so you can see
what the logic did.
The controller does not behave: naut run
Section titled “The controller does not behave: naut run”- Port in use.
tag api: localhost:8080 is in use (another naut run?), so this one is on localhost:8081. Another controller is already on that port.naut runmoved to the next free one and printed it; use that address, or stop the other controller. - A value you wrote did not stick. Writing an
inputis refused (see the last lesson); write the setpoint the logic reads, or force the input. not rendered: no Chrome, Chromium or Edge.naut checkandnaut hmi builddraw a screen in a browser to look for layout problems. With none on the machine they say so and carry on: the screen is still checked against your tags. Install one of those browsers, or ignore it.- A tag reads but the screen shows nothing. The name in the screen or
the logic is misspelt:
naut checkreports a name a screen binds that the project does not declare.
The install does not work
Section titled “The install does not work”“command not found”, a macOS security prompt, a Windows SmartScreen warning, and “address already in use” are covered, step by step, in the tutorial’s troubleshooting section.
Still stuck
Section titled “Still stuck”Ask in the project’s issue tracker with the command you ran and everything it printed.
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.