FAR2xx8 Connection

Configure the Radar

Set the FAR2xx8 IP Address

The PC communicates directly with the FAR2xx8 radar via its LAN1 port.

CLASS C ("ECDIS") IP

By default, the FAR2xx8 operates on a Class C network 192.168.31.x / 255.255.255.0 ("ECDIS network"). For most application, it is recommended to leave the radar with its default IP address (LAN1: 192.168.31.21 / SCAN: 192.168.31.101) and configure the computer IP address accordingly. Note that a GPS and Heading sensors need to be connected directly to the radar for the Anti Clutter Elimination (ACE Mode) to work properly, even in fixed application:

Note: If multiple radars are networked or inter-switched together, a unique Radar Number must be assigned to each radar processor and radar sensor. This can be done from the first page of the FAR2xx8 "Installation" menu.

IMO Mode

When TimeZero is interconnected to the FAR2xx8 via the network, the radar should be set to IMO Mode B or W. To set the IMO type, hold “HL OFF” and press the “MENU” key 5 times on the FAR2XX8. The “Radar Installation” menu will appear. Select “Installation” (5), then "Type" (6). Set to "B" or "W" ("W" is recommended).

SIO LAN Output

The FAR2xx8 SIO LAN Output should be turned OFF (which is the default setting on the FAR). To make sure this setting is OFF, right click on the [POSN] box located at the top right of the FAR2xx8 screen:

Select OFF for the “SIO Data LAN Output” (4).

Instruments (GPS, Heading, AIS, ...) need to be connected directly to the FAR2xx8 and to the computer. When connecting instruments to TimeZero (via NMEA0183 or NMEA2000), it is very important to make sure that the same GPS and Heading sources connected to the FAR radar are also used and connected to TimeZero. Connecting a different GPS and/or Heading source will result in radar overlay issue.

Configure the computer

TimeZero connects to the FAR2xx8 radar through an Ethernet connection (100Base-T) via the LAN1 port of the radar processor. The computer needs to have an IP address that “matches” the Radar Network (192.168.31.x / 255.255.255.0). We highly recommended using the following IP for the computer:

- 192.168.31.150 with a subnet mask of 255.255.255.0

Open the "Network Connections" control panel of your computer to adjust the IP address. Under Windows 10/11 you can press the combination shortcut Windows Key + R to open the Run dialog box. Type "ncpa.cpl" and click on "OK":

Double click on the Network Adapter connected to the radar (usually “Local Area Connection”).

Note: If you have multiple Area Connections (multiple Ethernet Cards) and if you don’t know which one is connected to the radar, you can temporarily disconnect the Ethernet Cable connected to the radar from the computer and look at which icon will display a red cross. This will indicate the LAN that has been disconnected from the computer, and thus the one that needs to be configured.

Select "Properties" on the "Local Area Connection Status" window. Double click on “Internet Protocol Version 4 (TCP/IPv4)”. Use the fix IP address 192.168.31.150 with a subnet mask of 255.255.255.0:

Once the computer's IP address has been assigned, it is recommended to Ping the IP address of the Radar Processor Unit (192.168.31.21 by default) and the Scanner unit (192.168.31.101 by default) to make sure the network is correctly set up. For more information on how to ping an Ethernet device, refer to the How To Ping chapter. Once connectivity has been confirmed, launch TimeZero.

Important Note about the Use of Managed Switches on Furuno Networks causing "No Sweep" radar error:
Managed or “smart” Ethernet switches are becoming increasingly common. However, when used on a Furuno network, these switches can cause communication issues due to features such as IGMP Snooping. In the absence of a proper IGMP Querier (which is not present on a Furuno Network), the IGMP Snooping feature of the switch may prevent UDP multicast data from being forwarded correctly. This can result in symptoms such as a Radar “No Sweep” status on the Radar Screen, even though the radar appears correctly detected. While some managed switches allow IGMP Snooping to be disabled, others enable this feature internally with no option to turn it off. In such cases, the only reliable solution is to replace the switch with a truly unmanaged Ethernet switch that does not implement IGMP Snooping or any traffic optimisation/QoS.