What's new

LaserWash 360 - Stuck in Bay Active

EaglesLaserWash

New member
Joined
Mar 24, 2013
Messages
2
Reaction score
0
Points
1
Location
Pennsylvania
I have been having a recurring problem with this. Every 100 washes or so, the error Vehicle Stuck in Bay - Gantry did not return home error occurs.

When this happens, the machine must be turned off and turned back on to clear the error.

The machine can be put into maintenance mode when the error occurs, but cannot be taken out of maintenance mode, because the machine is not in the home position.

Also, when this error occurs, the red X at the front of the bay stays lit as well as the green up arrow and the machine is continually telling the customer to exit, even though the car is already gone.

Have any of you seen this error and do you know how to fix it?

Thanks
 

sparkey

Active member
Joined
May 22, 2010
Messages
905
Reaction score
188
Points
43
Location
Ohio
I don't have a laser 360 but do have a razor which I think is pretty much the same. On the razor that would be an indication the stop or back-up eye is still blocked after the car leaves. I would check sensitivity and alignment of both.
 

koliver

PDQ Sales Engineer
Joined
Sep 4, 2007
Messages
145
Reaction score
15
Points
18
Location
DePere, WI
The LaserWash 360 has a Wash Abort Report that will give detailed information on what caused the abort. If you can get this, it will help us address the issue you are having.

From the sounds of it, one of the loading/unloading ultrasonics are not clearing after the vehicle leaves. This could be caused by misalignment, grating in the bay or even a pile of 3X Color Foam on the floor.

If you get the report or need help finding it, please don't hesitate to give our tech service department a call at (800) 227-3373.
 

EaglesLaserWash

New member
Joined
Mar 24, 2013
Messages
2
Reaction score
0
Points
1
Location
Pennsylvania
Our repair rep was here last week and looked at that report. It did not seem to give him much to work with.

Our repair rep was here again today and actually saw the error when it occurred. After discussing with PDQ reps directly, it looks like it may be the viper board (main computer board). I don't necessarily understand why this would be the case with a machine that is only 17 months old, but we will see.
 
Top