Laguna Troubleshooting Run Book

1) Reboot the rTC

• A) Connect to the Laguna Wi-Fi network.

• ~ Check bitwarden for credentials under Laguna Defaults.

• B) Go to 192.168.1.80

• C) Log into the rTC

• D) Go to the Tools along the left hand side.

• E) Click reboot the rTC

• 2) Confirm the error messages that appear after the rTC boots back up.

Error Messages

• Informational Message - an error like this won't keep the tunnel from running and can usually be ignored.

• Warning Message - an error like this will not keep the tunnel from running but seriously affects functionality.

• Critical Message - an error like this will keep the tunnel from running.

Dryers xx-yy Overload Fault

• If a dryer is forced off, it will throw this error.

• This can be the result of a motor being busted on a blower and someone forcing it off in the MCC. This type of error can usually be ignored.

Vehicle Profile Sensor (VPD/VPS) Fault

• The vehicle profile sensor is not working.

• There are quite a few things that could throw this error, but ultimately it won't stop the wash from running.

• A) Ghost car sent.

• B) VPS not installed but rTC is configured to have one.

• C) VPS is actually broken.

ECU 1911 not responding - 192.168.1.x

• The acc-node virtual node is not responding. This could be due to a power or data issue.

• 1) Check power connection.

• A) Device is powered by micro-USB and connects back to a power supply that in turn runs to the UPS/Battery Backup that's inside the MCC.

• B) Check the connection at the device.

• C) Check the connection at the power supply.

• D) Check the connection at the UPS/Battery Backup.

• E) Make sure the UPS/Battery Backup is on and powered.

• 2) Check network connection.

• A) Ensure network cable is connected to the accu-node.

• B) Ensure cable runs to internal rTC router.

• C) Ensure rTC router is powered on.

• IF you resolve the problem, the error should clear from the rTC screen on refresh.

PBS Not Responding

• The Push Button Station (PBS) is not talking to the rTC. The could be a power or data issue.

• While the PBS is not required to get the tunnel to run, retracts and queuing outside of Washify will be unavailable until it's back up and running.

• 1) Check status on the PBS.

• A) Check message on PBS for more details.

• B) Power and Network lights should be light.

• C) if either one of them are not, continue.

Network light not lit?

• 1) Reboot from the UPS/Battery Backup.

• A) There's an elongated power supply that should be plugged into the UPS.

• B) NOTE: Next step will cut power to the rTC so make sure the wash is not running.

• C) Unplug power cable.

• D) Wait 30 seconds

• E) Plug back in

• F) Wait up to 15 minutes for the PBS to reconnect.

• 2) Check ethernet connections from PBS into the Laguna rTC router.

• A) Is there a cable plugged in there with no link lights?

• ~Reseat it.

Power Light not lit?

• 1) Check power connections.

• A) Check terminals 309 (+) and 309a (-)

• B) Make sure wires are connected.

• 2) Check DC Power Supplies

• A) MCC lefthand door, about 2/3 of the way down.

• B) Make sure all Power supplies are showing a green light.

• C) If they aren't, could be a problem with the incoming power.

Temperature Issues

• Something could be shorting and causing the node to heat up. Either that or something did short and now the temperature sensor is broken. I have seen this only in tandem with the tunnel being down so not sure if it will take a node offline.

• 1) Check Spy -> Sensor measurements.

• 2) See what the sensor actually says it is.

• 3) If the temperature is showing as between 200 and 250, it might be a legitimate temperature issue and inspection of the node and the devices connected to it would be necessary.

• 4) If the value is something ridiculous like -400, one of the inputs/outputs could have shorted and the temperature sensor was damaged.

• A) If you believe the temperature sensor was damaged and that problem is now resolved, you can temporarily change the temp values so the error will clear and you can wash cars again.

• ~Log into the RTC admin page -> Creds in bitwarden

• ~Check I/O -> Node Temperature Limits -> Uncheck use same temp.

• ~ Adjust the specific node appropriate to the values you monitored in Sensor Measurements

Node Not Responding

• Most commonly happens when you're in the rtc working on something else and bump an ethernet cable. It will take the tunnel down.

• 1) Check ethernet connections to nodes.

• 2) Try a fresh cable if you're doubting it

Pulse Issues

• If you're lucky, sim pulse can be flipped on and everything will still work pretty well. Some settings I've seen work is a conveyor speed around 40hz and 4780-4800 pulses per hour. Reminder that once it's set and timing looks good don't touch the conveyor speed!

• If you're not lucky, the original measurements were inaccurate, and timing is terrible. The site won't be able to run reasonably until it has a real pulse without damaging cars.

Turning on Pulse Simulator

• 1) Log into the RTC admin page.

• 2) Go to Tools -> Simulators

• 3) Record current pulses per hour setting.

• 4) Turn on pulse simulator.

• 5) Adjust conveyor to a speed the site can reasonably run at until pulse is fixed.

• A) Recommended: 40hz

• 6) Test to verify device timing

• 7) Adjust Pulses per Hour in Tools -> Simulators

• A) Recommended: 4780-4800 pulses per hour.

• B) If devices are cycling too soon:

• ~ Physical car is moving slower than virtual.

• ~ Decrease pulses per hour.

• C) If devices are cycling late:

• ~Physical car is moving faster than virtual.

• ~Increase pulses per hour.

• D) Repeat testing and adjusting until timing looks good.

Testing the Pulse for Issues

• 1) Set dial on the node to 3 to see inputs as they trigger at the rTC.

• A) Default: 0 (aka Star Trek mode according to Dan)

• 2) If nothing on that node is working by jumpering terminals B and C

• A) Check inventory for nodes.

• 3) Check that the node and input is working by jumpering terminals B and C

• A) Pulse is normally wired to node 2 input 1

4) Check wiring.

• A) Wiring back to rtc should be as follows

• a) Input Terminal A= Positive wire = Brown

• b) Input Terminal B= Switch wire = Black

• c) Input Terminal C= Negative wire= Blue

• B) Check junction boxes for wire colors if the above colors don't match at the rtc.

5) Check that the pulse is working by removing the sensor and hooking it up directly to the rtc and testing.

• A) If it works here, could be bad wiring.

• a) Check junction boxes

• b) Check for breaks

• c) Check for conveyor wire running near pulse and relocate one as the conveyor wire has been known to interfere with the pulse.

• B) If it doesn't, the sensor is bad, or the input is bad.

• a) Swap to another input

• ~ Move the wiring to another input and make sure to update inputs in RTC Admin.

• ~ Make sure to update inputs in RTC Admin

• -Go to I/O -> Input Assignments

• -Under the first section select Pulse

• -Update the input assignment

• b) Sensor is bad

• -Replace the Sensor

6) Another option is to switch 24v power for the pulse if we're questioning the 11v

• A) Rewire positive and negative wires to 24v power on terminal 309 (positive) and 309a (negative)

• B) Leave Black Switch wire in B of whatever input the pulse is configured for.

Pulse Info

• 1) 10/30v DC NPN Switch is needed

• A) Example: https://www.eaton.com/us/en-us/skuPage.E57-12LE10-C.html (although not a good one)

Laguna Not Receiving Washes

• 1) Connect a device to the Laguna router network

• A) Password in Bitwarden

• B) If it's not listed individually, then it will be the settings under Laguna defaults

• 2) Connect to the Laguna Router

• 3) Navigate to WAN -> Virtual Server/Port Forwarding

• 4) Add a Port Forwarding rule with the following settings:

• A) Service Name: RTC Controller

• B) Port Range: 20250

• C) Local IP: 192.168.1.80

• D) Local Port: 20250

• E) Protocol: TCP