Universal WiFi Throttle - Connection Issues

Overview

There are two network connections that the throttle must make in order to communicate to your command station: A WiFi connection and a Server connection.

• WiFi - The WiFi connection is your access point, router, or WiFi device.

• Server - A server functions as the translator between your throttle and command station. This is often a computer running a JMRI WiThrottle protocol server.

Tip: Some devices like Digitrax LNWI and MRC WiFi Module function as both the WiFi and the Server simultaneously.

Troubleshooting the WiFi connection

This section will help you troubleshoot your network connection after a “No WiFi found” error. If no WiFi is found, there are a few likely causes:

Problem: Your router or WiFi network is not turned on or is otherwise inoperational.

Solution: Restart your WiFi device or router, and check for error messages or warning lights.

Problem: You have not yet connected to a WiFi network.

Solution: Follow the steps in the Connecting to a WiFi section to establish a connection.

Problem: Your WiFi password was entered incorrectly.

Solution: You will see the “Wrong WiFi Password” prompt. Double-check and re-enter your password.

Troubleshooting the Server Connection

This section will help you troubleshoot your server connection in the event the 'Server not found' prompt is displayed.

Problem: Throttle cannot connect to JMRI WiThrottle server.

Solution: Reboot your computer and command station, open JMRI, and start the WiThrottle server [Top menu: Actions > Start WiThrottle server]. Once complete, select "Try Again" on the throttle. If you are running JMRI on a Windows PC, make sure JMRI is allowed through the Windows Firewall or the throttle will not connect.

Problem: Command station does not respond to throttle input.

Solution: If your throttle is on and appears to be operational, but there is no response from your command station, restart the command station and check your power and data connections.

Problem: The wrong connection mode is selected.

Solution: Use the menu option labeled 'Auto-detect LCC/WT' or 'Change LCC/WT Mode' and select the correct connection mode. An asterisk (*) will appear next to the active mode.

Tip: Until TCS releases the Command Station, JMRI, LNWI, and all other potential connections communicate via the WiThrottle protocol. If your connection mode is set to "LCC" for the connection to your layout, change this to "WT" for WiThrottle protocol. LCC mode will be directly supported by the TCS Command Station and other LCC devices, and is currently used for throttle firmware updates with the TCS DEPOT software.

Problem: mDNS failed to find the WiThrottle server.

Solution: MDNS is a WiFi protocol which is used to automatically load the IP address and Port number of a server connection. mDNS does not work with all WiFI networks and can fail. If you use phone apps, you may be familiar with manually entering the IP address and Port number of your JMRI WiThrottle server. The UWT-100 is also capable of doing this. Select "Set IP address" from the 'Server not found' menu and set the IP address and port number as indicated on your WiThrottle protocol server window in JMRI. After entering the IP address and Port number once, the throttle will retain this information when reconnecting in future sessions.

Troubleshooting an LNWI Connection

If you are unable to establish a connection with your LNWI device, follow the steps below:

1. As simple as this sounds, turning the LNWI device off and on again will often solve connection issues.

2. Ensure that the number of connections to a specific LNWI devoce is not greater than four. LNWI devices have a limit of four connected devices at one time - including phones running apps like WiThrottle and Engine Driver. Turn off or disconnect one of the devices connected to the LNWI and see if the problem disappears.

3. Check that your saved LNWI device is turned on. In situations where there are multiple LNWI devices in use, the throttle may be configured to connect to one that is not available.

This page was moved from stagingtcsdcc:en:UWT-100 Connection Issues. Its edit history can be viewed at UWT-100 Connection Issues/edithistory