常見(jiàn)問(wèn)題

• No Radar

  This means the MFD cannot communic∑π≤ate

  with the radar in any way. There a ver♦ ‍y

  broad range of possible causes including:

  - Radar Ethernet Hardware fault

  - Radar SW Software bug

  - Ethernet cabling fault

  - No power to the radar

  - Ethernet hardware fault in MFD

  - MFD software bug 

  
  

  Recommendations:

  • Check / select actual radar in÷✘€ radar sources

  • Turn the system offφβα and on again

  • The most common error: The safetyβ π switch is

  switched off - only HALO radar

  • No voltage on the ¥≤£•yellow power supply line

  • No voltage on the yellow lead of the radar♠• ∞ cable

  from the radar interface

  • Missing or intermi™↔÷♠ttent Ethernet connection, the

  RJ45 connector is damaged​∞¥©

  • Broken Ethernet cable

  
  

• Acoustic Noise Detection of the sonar

  • Stop the vessel, and stop the pr♠σ≤opeller.

  – If the noise disappe©βared, the noise is either coming from the water  ≠↔≤flow, the propeller, the→₹σ' reduction gear or the pπ→∑∏ropeller shaft (most likelyσ‍​✘ water flow or propeller)

  – Try different propeller pitch

  • Give full speed ahead

  – The noise comes up gradually

  with speed, then you have flow- noise☆φ<♣ (Transducer installation)

  – The noise comes up immeβ©diately!

  You are faced with propeller noi≠•™se.

  
  

• Dockside Faults – No Drive Out<✘→≈put

  • Make sure the motor w↔≠€<ires are attached to the correct terminals

  • Check the output com ♠×mands and the voltage levels at the motor drive t ±erminals

  – Simply make meter contact≠≈₩‌ with the AC drive terminals and issue a comε>mand

  – Issue a command in tα"±<he opposite direction; you should see polaΩαrity reverse on your meter

  – NOTE: You can issue commands dire≠♦ctly at the AC by temporarily㧣 shorting the Remote term₽÷εinal PORT or STARBOA✘←RD to ground

  • When driving solenoids, t♦↔&he drive voltage can be measured from the✘&♣ ground common (SOL GND) to o∑★ne of the SOL-MOTOR terminals when a £<rudder command is issued. Rememb‍¥→↔er when driving solenoid‍ ‌₽s your mains supply is what you will prov×&‌‍ide to the solenoid terminals and bypass

  – Insure your are correctly ​λ↓connected and 12V is present on the SOL-M"<OTOR contacts when the autopilot issues a command✘←↓

  
  

• Dockside Faults – No Pilot C←∑"omputer

  • If all fusing and powe$×‌r is correct, you can isolate between ÷↔ the AP and the AC by making some qui‌÷☆ck assumptions

  • Do I see a compas→→s heading and a heading source s™↕εhown on the AP controller? Yesε₩¥Ω Pilot Display OK

  • Are my sources prop₩♠¶erly configured in SimNet and can I see the "§♠Pilot computer in the device list? &n±✔←bsp;If seen by the netwδ£₩♠ork it will be listed next to the↕₹→ Distance Log and Pilot sources.

  • If you still do not ‘see’ the AC unit youσΩ®σr best recourse is to en♠'♦ter the Service Menus of the APα∑ and perform a Global Reset, then &ε​cycle the power.

  
  

• No Spoke data for radar

  As a persistent error

  This means the MFD is♦÷≠ still communicating with the radar, but itα∑∞¶ is not receiving radar image data o$©ver Ethernet.

  This is likely to be a radar hardwar≠↓e problem (typically ₹>↕₹FPGA) or in rare cases a radar software problem.

  This error can NOT b←£ε e caused by cabling faults.

  Recommendations:

  • Turn the system off and £↓on again

  • FMWC and PuC radars u₽φ§sually need to be

  replaced as this is an internal ₩≥failure

  • Pulse Radar: Check / replace the HD scanner uni®≈€t