Erratic output from ACU 400
|
11-06-17, 10:25 AM
Post: #8
|
|||
|
|||
RE: Erratic output from ACU 400
Andy,
Q1. Going back to my original question, how can I check to see if the EV1 is working correctly, eg is it getting a good enough signal? The manual tells me the correct led sequence to show that it is networked on the stng network, but does this also show that it has a clear enough sky view or that it is functioning properly? It currently shows a constant green light. A1. The EV-1/EV-2 CCUs are not GPS sensing devices and as such, recommendations for GPS sensing devices (ex. providing an unobstructed view of the skies overhead) do not apply to the EV-1/EV-2 CCU. From a sensing standpoint, the EV-1/EV-2 CCUs are designed to function as the autopilot course computer, as well as to function as the system's magnetic north seeking sensor and roll/pitch/yaw sensor. Communications with the EV-1/EV-2 CCU with the other system's components which have been interfaced to the SeaTalkng / NMEA 2000 backbone may be verified by listing the devices sensed by the autopilot's control head (MENU->SET-UP->DIAGNOSTIC->ABOUT SYSTEM). Following the brief cruise to determine the deviation table, the maximum sensed deviation may be access via the command sequence MENU->SET-UP->DIAGNOSTIC->ABOUT PILOT. It is desirable that this value be less than ten degrees. Should this value be greater than ten degrees, then another installation location which is farther from magnetic fields will need to be found for the EV-1/EV-2 CCU. Q2. We did the factory reset, dockside calibration and auto learn linearisation for the autopilot again but the same problem occurs. The pilot starts off holding an ok course then the wheel starts to turn port/starboard rapidly. The speed is set to SOG like you suggested. A2. I was not suggesting that the Speed instrument be set to SOG, but rather that the autopilot's Speed Input setting be configured to SOG. Should the latter have been satisfied, then please indicate whether a rudder reference transducer has been installed. If so and when tide dockside or at a mooring with the autopilot in Standby mode, examine the rudder bar displayed on the autopilot's control head to verify that it moves in the correct direction when rudder is applied. Q3. Another problem we had with the pilot was that we couldn’t get it to sail to the windvane, in windvane mode the display showed the correct wind angle but as soon as it took over it put the wheel hard over and we had to press standby to regain steerage. We will be taking the pilot and the itc5 to a service center on Monday to get them bench tested and at least check to see if the fault is in the hardware. A3. With respect to Wind Vane mode, selection of this mode is not dependent upon wind data. This mode is dependent upon the Vessel Hull Type setting having been configured to one of the sailing vessel options (SAIL, SAIL (SLOW TURN), or SAIL CATAMARAN). That said, should Wind Vane mode be selected and the system does not detect a source of wind, then the autopilot control head will alert the user that no wind source was detected, effectively preventing its use in this mode. |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
Erratic output from ACU 400 - Andy Laws - 10-31-17, 11:40 AM
RE: Erratic output from ACU 400 - Chuck - Raymarine - Moderator - 10-31-17, 02:33 PM
RE: Erratic output from ACU 400 - Andy Laws - 11-01-17, 08:31 AM
RE: Erratic output from ACU 400 - Chuck - Raymarine - Moderator - 11-01-17, 10:01 AM
RE: Erratic output from ACU 400 - Andy Laws - 11-01-17, 10:46 AM
RE: Erratic output from ACU 400 - Chuck - Raymarine - Moderator - 11-01-17, 01:05 PM
RE: Erratic output from ACU 400 - Chuck - Raymarine - Moderator - 11-06-17 10:25 AM
|
User(s) browsing this thread: 1 Guest(s)