The Nauti-Control controller includes a built-in settings page where you can configure WiFi, Bluetooth, autopilot behaviour, remote controls, services and debug options.
You can open the settings page using either the controller hostname or its IP address:
http://<your-controller>.local/setupor:
http://<controller-ip-address>/setupThe IP address can usually be found in your router, chart plotter hotspot, or the Nauti-Control app.
Saving the settings page will normally restart the controller so the new configuration can take effect.
Security Settings
The security settings protect access to the controller, its WiFi access point and Bluetooth connection.
| Setting | What it does |
|---|---|
| Web Admin Password | Protects the controller’s web pages, including Setup, Display and Debug. |
| Access Point Password | Protects the controller’s own WiFi network. This is the password used when connecting directly to the controller. |
| BLE PIN | A four-digit PIN required by the companion apps before they can read data or send commands over Bluetooth. |
For best security, change the default passwords and PIN during setup.
Network Identity
The mDNS Hostname is the name used to find the controller on your local network. For example, if the hostname is set to NAUTI-CONTROL, the setup page can normally be opened at:
http://NAUTI-CONTROL.local/setupIf the hostname does not work on your device or network, use the controller’s IP address instead.
WiFi Settings
Nauti-Control can connect to an existing boat WiFi network while also running its own access point for direct connection.
WiFi Client Mode
WiFi Client Mode allows the controller to join your boat router or chart plotter hotspot. You can configure the network name, WiFi password, DHCP, static IP address, subnet mask and gateway.
Use DHCP for the simplest setup. If you plan to use the web interface regularly, or connect navigation apps to the NMEA TCP/IP stream on port 8091, it is recommended to keep the controller on a fixed address. This can be done either by setting a static IP in the controller, or by creating a DHCP reservation in your router or chart plotter hotspot.
A fixed address makes it easier to reconnect later because the controller will always appear at the same IP address on your boat network.
Access Point Mode
The controller also runs its own WiFi access point so you can connect directly from a phone, tablet or computer, even without a boat router.
The default access point address is:
192.168.1.1You can change the access point name, password and WiFi channel. Changing the channel can help if there is interference from other WiFi networks in a marina.
Bluetooth Settings
Bluetooth Low Energy is used by the Nauti-Control companion apps on phones, tablets and smartwatches.
You can set the Bluetooth device name and the BLE security PIN. The PIN must be four digits. Leaving the field blank when saving keeps the current PIN unchanged.
Autopilot Settings
The autopilot settings control how Nauti-Control sends steering commands.
On NMEA 2000 versions, you can select the autopilot type. Options include Raymarine/SeaTalk-style commands, Simrad/B&G, and Simrad TP22/TP32 tiller pilot support.
The Lock Autopilot on Boot option is an important safety feature. When enabled, the controller starts locked every time it powers on. While locked, heading and mode commands from remotes, apps and the web interface are blocked.
Man Overboard and Cancel MOB commands are always allowed, even when the autopilot is locked.
Race Timer
The race timer stores the countdown duration used by the Start Timer remote button action for ST60 /Seatalk .
You can set the countdown minutes and seconds. These values are stored on the controller and shared with the companion apps.
Services
Nauti-Control lets you turn individual services on or off.
- Web Server serves the Setup, Home, Display, Debug and Update pages.
- NMEA TCP/IP streams NMEA 0183 data on port
8091for compatible navigation apps. - Bluetooth enables the BLE connection used by phones, tablets and smartwatches.
- 433 MHz RF Remote enables support for paired wireless remotes.
- NMEA 2000 enables the N2K interface on NMEA 2000 versions.
- SeaTalk enables the SeaTalk bus interface on SeaTalk versions.
Most users should leave the default services enabled. Turning off unused services can reduce radio activity and save a small amount of power.
433 MHz Remote Controls
The controller can learn and store multiple 433 MHz wireless remotes. Each remote can have its own name, and each button can be assigned a different function.
Common button actions include +1°, -1°, +10°, -10°, Auto, Standby, Track, Wind, Port Tack, Starboard Tack, MOB, Cancel MOB, Start Timer and Autopilot Lock.
After changing remote button settings, save the configuration and restart the controller if required.
For full remote setup instructions, see the Pairing Remotes guide.
Debug Logging
The Debug page is available at:
http://<controller-ip-address>/debugDebug logging should normally be left off. It is only needed when troubleshooting.
You can enable logging for radio, NMEA, SeaTalk, NMEA 2000, Bluetooth, general information and errors. Only enable the category you need, as too much logging can reduce performance.
Recommended Defaults
For most users, the recommended setup is:
- Set a secure web admin password.
- Set a secure WiFi access point password.
- Set a four-digit BLE PIN.
- Leave the WiFi access point enabled.
- Use DHCP for simple setup, or use a static IP/DHCP reservation if using web access or NMEA TCP/IP regularly.
- Leave Bluetooth enabled.
- Leave remote support enabled if using 433 MHz remotes.
- Keep debug logging off unless troubleshooting.
These settings provide a secure and reliable starting point for most Nauti-Control installations.
Leave a Reply
You must be logged in to post a comment.