NGR-3000 GNSS Navigator
NGR-3000 GNSS Navigator
GNSS equipment
NGR-3000
Warning
Keep away from heat source or direct sunshine.
Prohibition
Don’t open the equipment. Only qualified personnel should
work inside the equipment. Don’t disassemble or try to modify
the equipment.
Dangerous
Turn off the power immediately when smoke or fire is emitted.
Warning
Connect the earthing cord to ship’s body.
Observe the compass safe distance to prevent deviation of an
onboard magnetic compass.
Prohibited
Don’t open the equipment unless you have fully understood the
structure and circuits of the equipment. Only qualified
personnel should work inside the equipment. Don’t
disassemble or try to modify the equipment.
Dangerous
Turn off the power at power distribution board before
installation.
1. PRODUCT FEATURES
NGR-3000 is an IMO GNSS equipment of NSR’ new generation, compatible with GPS, Beidou
and Glonass system.
NGR-3000 GNSS equipment consists of a display unit and an antenna unit.
The high sensitive GNSS equipment tracks up to 50 satellites simultaneously. It ensures
optimum accuracy in determination of vessel position, course and speed.
The main features of NGR-3000 are:
• Comprehensive navigation data displays.
• Alarms: Loss of Position, loss of differential signal, HDOP Exceeded.
• Menu-driven operation.
• 7 inch, color LCD, touch screen operation with adjustable brightness.
• 3 GNSS data outputs, BAM/INS input/output.
• A DGNSS beacon receiver (external) may be connected to NGR-3000 to add DGNSS
function.
The product meets the requirements of relative IMO and IEC regulation & standards,
including IMO MSC.112 (73), MSC.302(87) , IEC61108-1, etc.
EQUIPMENT LIST:
Scope of Supply
No. Name Quantity Description
1 NGR-3000 Main Unit 1
2 NGA100 GNSS Antenna 1 Cable length 10m or 20m
3 Installation Materials
3.1 Mount Pole 1
3.2 Steel Tie 2
3.3 Accessories 1
4 Options
4.1 NDG-100 DGNSS Beacon
4.2 FB700 Flush Mount Brackets
4.3 NND-100 NMEA distributor
4.4 NND-200 NMEA distributor
2. OPERATIONAL OVERVIEW
When operated with knob, turn the knob to select an item on screen and press the knob to
confirm the selection.
Power ON/OFF.
PWR
To power OFF, press and hold this button more than 3 seconds.
NGR-3000 takes about 120 seconds to find position when turned on for the very first time.
2 NGR-3000 UM.E 20210716-05
NGR-3000 USER MANUAL
Thereafter, it takes about 15 seconds to find position each time the power is turned on.
After fixed, the accurate position (in latitude and longitude) appears on the display.
⑨ ⑩ ○
11
①
②
○
6
③
○
7
④
⑧
○
5
○
12
② Datum WGS84/PZ90
○
12 Speed over Ground SOG
Press the PWR button to turn on the power. Usually it will take about 2 minutes to find its
position when turned on for the very first time.
The equipment shows receiver status at the bottom of the screen.
Indication Meaning
GP-2D/ GP-3D GPS fix
GP-D2D/GP-D3D Differential GPS fix
GB-2D/GB-3D BDS fix
GB-D2D/GB-D3D Differential BDS fix
GL-2D/ GL-3D Glonass fix
GL-D2D/GL-D3D Differential Glonass fix
GN-2D/GN-3D GNSS fix
GN-D2D/GN-D3D Differential GNSS fix
Press and hold down the PWR button for 3s until the screen goes blank.
There are two ways to adjust the brightness and contrast of the LCD.
- Adjust the brightness in the [SYSTEM SETTING] by clicking [LCD/KEY DIMMER].
Note:
When the power is turned off, the last status of brightness is stored. Therefore, when the
power is turned on next time, the screen will display with the last brightness before
powered off.
Most operations of your unit are carried out through the menu. If you get lost in operation, press
the [PWR] button to return to the MAIN menu. Please refer to complete MENU TREE in the
Appendix.
In some instances, it is necessary to enter character data. The below example shows how to
rename a route by soft keyboard.
Operate the menus until the above screen is got. (Please refer to WAYPOINT/ROUTE)
1) When the first line is selected, click EDIT to locate the first character to edit.
Click RENAME to rename the route desired.
①
② ④
Basic data will be displayed in this mode, including position in latitude and longitude,
course, speed, date and time.
NGR-3000 takes about 120 seconds to find position when turned on for the very first time.
Thereafter it takes about 15 seconds to find position each time the power is turned on.
6 NGR-3000 UM.E 20210716-05
NGR-3000 USER MANUAL
After fixed, the accurate position (in latitude and longitude) appears on the display. If position
could not be found, loss of position will appear at alarm column.
The Plotter display traces own ship’s track, shows position, course, speed, and sets display
range.
You may increase or decrease the display range on the Plotter display. The range in the Plotter
display is available among 0.02, 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10, 20, 40, 80, 160 and 320 nautical
miles.
1) Click the [OPERATE] button. The pop-up menu appears.
2) Click “ZOOM IN” or “ZOOM OUT” to select range desired.
3) Click on any blank space to finish.
The Highway display provides a 3-D view of own ship’s route toward destination.
Navigation data is also shown.
3. NAVIGATION PLANNING
Often a trip from one place to another involves several course changes, requiring a series of
waypoints which you navigate to, one after another. The sequence of waypoints leading to the
ultimate destination is called a route. NGR-3000 can automatically advance to the next
waypoint on a route, so you do not have to change the destination waypoint repeatedly. NGR-
3000 can store 30 routes and each route may include up to 100 waypoints.
(2) Click PLOTTER in MENU, then click WAYPOINT/ROUTE in OPERATE to open the
menu.
Create a new waypoint with the position as own ship’s current position. The new waypoint
will be inserted before the waypoint which is selected by the current cursor.
ADD a waypoint
Add a waypoint to route from route list.
Click ADD to add the current position as a new waypoint to the route.
The screen will change to WAYPOINT LIST display.
DELETE a waypoint
Click the DELETE to delete the selected waypoint from the route.
Click the REVERSE to start navigation reversely. The screen will switch to plotter page.
4. ALARM
Select [NOTICE SETTING] in [NAVIGATION] to open the menu.
The XTE alarm warns you by an internal buzzer when own ship is off its intended route.
The speed alarm is activated when ship’s speed is higher (or lower) than the set value.
LOW: Alarm is activated when speed is lower than the speed set.
HIGH: Alarm is activated when speed is higher than the speed set.
You may activate the arrival alarm or the anchor watch alarm while they cannot be
activated together.
Arrival Alarm
The arrival alarm informs you that own ship is approaching a destination waypoint. The area
that defines an arrival zone is that of a circle which you approach from the outside of the
circle. The alarm will be activated if own ship enters the circle.
The anchor watch alarm sounds to warn you that own ship is moving beyond the set area.
Before setting the anchor watch alarm, set current position as destination.
NOTE:
Anchor watch alarm and arrival alarm are combined to serve a route. After a route is
finished while the destination is arrived at, keep the navigation on the route while setting
ANC. The anchor watch starts.
5. MENU SETTING
Total five modes can be selected: GPS & BDS, GPS & GLONASS, GPS, BDS, GLONASS.
5.1.2 2D/3D
Select 2D or 3D fix mode.
5.1.4 RAIM
5.1.4.1 RAIM
RAIM (Receiver Autonomous Integrity Monitoring) can be set ON or OFF.
When set ON, RAIM will display SAFE, UNSAFE or CAUTION in below conditions:
Those conditions may occur if an insufficient number of satellites are available, for
example 4 or 5 with 2 satellites "close" together in azimuth and elevation, causing the
geometry to degrade to the point that the RAIM calculation becomes unreliable. Note
that the resulting accuracy based on 4 or 5 satellites in use may be within the selected
accuracy level, but the RAIM algorithm cannot verify it.
Accuracy level is not of the indication of position accuracy while it is only the calculation
reference for RAIM.
5.1.5 Beacon/SBAS
The system will alarm if the condition of loss of differential signal occurs.
5.1.6 SMOOTHING
Change the COG and SOG averages to adjust the smoothness.
5.2.3 Day/Night
Click the icon at upper right corner to change the display between day mode and night mode.
5.3 Alert
When an error occurs, an alert will display on the current screen. The meanings of the
alert are stated as below:
3 3055 B WARNING Loss of differential signal DGPS input not detected, Check DGPS
Beacon, if No DGPS Beacon, change
setting from Beacon to OFF/SBAS
Alarm buzzer can be set by clicking [ON] and [OFF]. It controls the sound of alarms.
5.4 Diagnostics
The diagnostic test is to check software version, keypad and LCD for proper operation.
NOTE:
The navigation settings and GPS settings will restore to factory default while the waypoints
and routes registered remain unchanged.
6. INSTALLATION
The main unit can be installed on a table-top, on the overhead, or in a panel (optional flush
mounting brackets required). Refer to the drawings at the end of this manual for installation
instructions. When selecting a mounting location, keep in mind the following points:
Install the antenna unit by referring to the antenna installation drawings at the end of this manual.
When selecting a mounting location for the antenna unit, keep in mind the following points:
6.3 Cabling
The power cable with a rated capacity of 3A should be used. Pin definition for the connector is
showed above.
Suggest using the 3A Power Supply Unit (DC 24V output).
The default baud rate is 4800 bps, which can also be changed among4809/ 9600 / 19200 /
38400 bps.
6.3.3 Grounding
Ground the unit as follows to prevent interference:
This equipment can output navigation data to external equipment, in NMEA 0183 format. For
31 NGR-3000 UM.E 20210716-05
NGR-3000 USER MANUAL
Data sentences:
Up to five sentences may be selected for each port. If the selected sentences exceed 7
items, OVERFLOW will be indicated in the relative column. In this case, OUTPUT
ERROR will also be shown in displayed screens.
NMEA version
There are total five versions to be selected: NMEA1.5, NMEA2.0, NMEA2.3, IEC61162
Ed4, IEC61162 Ed5.
Baudrate
It can be 4800, 9600, 19200, 38400bps.
ACN: Equipment is operating normally, or for supervision of a connection between two units.
ALC: Cyclic alert list. The cyclic alert list transmission shall never stop. When all alerts are
in normal state the cyclic alert list is empty i.e. number of alert entries is 0.
ALF: Report an alert condition and the alert state of a device. An ALF message shall be
published for an alert each time the alert information in this sentence changes and on
alert request (see ALC – Cyclic alert list).
GNS: Fix data for GPS, GLONASS.
GBS: Support Receiver Autonomous Integrity Monitoring (RAIM).
GGA: GPS position fixing condition (time of fix, latitude, longitude, receiving condition,
number of satellites used, DOP).
HBT: The sentence is transmitted at regular intervals specified in the corresponding equipment
standard. The repeat interval may be used by the receiving unit to set the time-out
value for the connection supervision.
RMC: Generic navigational information (UTC time, latitude, longitude, ground speed, true
course, day, month, year).
VTG: Actual track and ground speeds.
ZDA: UTC time (day, month, year).
DTM: Datum reference.
GSA: GNSS receiver operating mode, satellites used in the navigation solution reported by
the GGA 2148 or GNS sentences, and DOP values.
RTE:Waypoint identifiers, listed in order with starting waypoint first, for the identified route.
BWC:Bearing and distance to waypoint – Great circle
RMB:Recommended minimum navigation information
XTE: Cross-track error, measured
WPL:Latitude and longitude of specified waypoint.
NOTE: As default, GNS, GBS, GGA, RMC, VTG, ZDA and DTM are selected.
1) The baud rate can be selected among 4800/ 9600/ 19200/ 38400bps.
2) The NMEA Version can be selected among 1.5/ 2.0/ 2.3/IEC61162 Ed4/IEC61162 Ed5.
DISPLAY SECTION
INPUT/OUTPUT DATA
POWER SUPPLY
24V DC: 0.25-0.5A
ENVIRONMENT CONDITION
OTHERS
$--ACN,hhmmss.ss,aaa,x.x,x.x,c,a*hh <CR><LF>
| | | | ||
| | | | | +--------------------------------- 6
| | | | +---------------------------- 5
| | | +-------------------------- 4
| | +------------------------- 3
| +----------------------- 2
+---------------------------- 1
NOTE 1: Release time of the alert command. (e.g. for VDR purposes), optional can be a null
field. Sender is allowed to use all alternatives defined in Table 5 Field type
summary. Receiver is allowed to ignore content of this field. If receiver does not
ignore this field it should support all alternatives defined in Table 5 Field type
summary.
NOTE 2: Used for proprietary alerts defined by the manufacturer. For standardized alerts this
should be a null field.
NOTE 3: The alert identifier is unique within a single alert source. The alert identifier is a
variable length integer field of maximum 7-digit integer. It identifies the type of the
alert e.g. a “lost target” alert. Standardized alerts use unique alert identifiers
described in equipment standards. Number range 10000-9999999 is reserved for
proprietary alerts. Alert Identifier examples: “001”, “2456789”, “245” .
NOTE 4: The alert instance identifies the current instance of an alert to distinguish alerts of
the same type (Alert identifier) and from the same source (e.g. dangerous target).
Alert instance is maximum 6-digit integer from 1 to 999999. The number of alert
instance can be freely defined by the manufacturer as long as it is unique for one
type of alert (alert identifier). It is not permitted to modify the alert instance within a
life cycle of a distributed alert (from ‘active & unacknowledged’ state until
‘normal’ state is reached). It can be also a null field, when there is only one alert of
that type.
NOTE 6: This field should be “C” and should not be null field. This field indicates a
command. A sentence without “C” is not a command.
41 NGR-3000 UM.E 20210716-05
NGR-3000 USER MANUAL
$--ALC, xx, xx, xx, x.x, aaa, x.x, x.x, x.x, ........, aaa, x.x, x.x, x.x*hh <CR><LF>
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | +---------------+----------- 7
| | | | | | | | +--+-------------------------- 6
| | | | +-----+----+---+------------------------------ 5
| | | +---------------------------------------------- 4
| | +--------------------------------------------- 3
| +------------------------------------------- 2
+------------------------------------------ 1
NOTE 1: The first field specifies the total number of sentences used for a message, minimum
value 1. The second field identifies the order of this sentence in the message,
minimum value 1, These cannot be null fields.
NOTE 2: The sequential message identifier relates all sentences that belong to a group of
multiple sentences (i.e. message). Multiple sentences (see Note 1) with the same
sequential message identifier, make up one message.
NOTE 3: Contains the number of alert entries transported within this sentence.
Each entry identifies a certain alert with a certain state. It is not allowed that an alert entry is
split between two ALC sentences.
NOTE 1: The first field specifies the total number of sentences used for a message, minimum
value 1. The second field identifies the order of this sentence in the message,
minimum value 1, These cannot be null fields. When the sentence number is 2, the
following Alert category, Alert priority and Alert state can be null fields.
NOTE 2: The sequential message identifier relates all sentences that belong to a group of
multiple sentences (i.e. message). Multiple sentences (see Note 1) with the same
sequential message identifier, make up one message.
NOTE 3: Time should represent the last time the data within the alert message has changed.
For example changing the alert text by in-/decrementing a contained counter or
count down should cause a revision of alert message and a new time. Time is an
optional field. The time-field is additional information about when this happened
and not used for decision making. There is no mandatory requirement for time
synchronization between the equipment. It should by either a null field (if not used)
or UTC (if used). Sender is allowed to use all alternatives defined in Table 5 Field
type summary. Receiver is allowed to ignore content of this field. If the receiver
does not ignore this field it should support all alternatives defined in Table 5 Field
type summary.
NOTE 4: The alert category is in compliance with the category definition as described in INS
Performance Standard (MSC.252(83)) and Bridge Alert Management Performance
Standard (MSC.302(87)):
C, Category C: Alerts that cannot be acknowledged on the bridge but for which
information is required about the status and treatment of the alerts,
e.g., certain alerts from the engine.
NOTE 5: Alert priority: Emergency Alarm: E, for use with Bridge alert management
Alarm: A
Warning: W
Caution: C
NOTE 7: Used for proprietary alerts defined by the manufacturer. For standardized alerts this
should be a null field.
NOTE 8: The alert identifier is unique within a single alert source. The alert identifier is a
variable length integer field of maximum 7-digit integer. It identifies the type of the
alert e.g. a “lost target” alert. Standardized alerts use unique alert identifiers
described in equipment standards. Number range 10000-9999999 is reserved for
proprietary alerts. Alert Identifier examples: “001”, “2456789”, “245” .
NOTE 9: The alert instance identifies the current instance of an alert to distinguish alerts of
the same type (Alert identifier) and from the same source (e.g. dangerous target).
Alert instance is maximum 6-digit integer from 1 to 999999. The number of alert
instance can be freely defined by the manufacturer as long as it is unique for one
type of alert (alert identifier). It is not permitted to modify the alert instance within a
life cycle of a distributed alert (from ‘active & unacknowledged’ state until
‘normal’ state is reached). It can be also a null field, when there is only one alert of
that type.
NOTE 10: The revision counter is the main method to follow up-to-date status. Revision
counter is also unique for each instance of alert. Revision counter starts with 1
and the step for increment is 1. The count resets to 1 after 99 is used. Revision
counter increments on each change of content of any field of the alert.
NOTE 11: The escalation counter is presenting the number of alert escalations after time
expiration during the state active-unacknowledged. The escalation counter starts
with 0 and the step for increment is 1. The count resets to 1 after 9 is used. The
alert escalation can be the escalation from warning into warning (activation of
audible signal only), the escalation from warning to alarm or the escalation from
alarm to alarm with activation of back-up navigator alarm
NOTE 12: This field is used for Alert title which is mandatory and for additional alert
description which is optional.
$--DTM,ccc,a,x.x,a,x.x,a,x.x,ccc*hh<CR><LF>
| | | | | | | | |
| | | | | | | | +--- 7
| | | | | | | +------ 6
| | | | | | +---------- 5
| | | | +--+------------- 4
| | +---+------------------- 3
| +------------------------- 2
+---------------------------- 1
1. Local datum W84 - WGS84
W72 - WGS72
S85 - SGS85
P90 - PE90
999 - User defined
IHO datum code
2. Local datum subdivision code
3. Lat offset, min, N/S
4. Lon offset, min, E/W
5. Altitude offset, m
6. Reference datum W84 - WGS84
W72 - WGS72
S85 - SGS85
P90 - PE90
7. Checksum
$--GBS, hhmmss.ss, x.x, x.x, x.x, xx, x.x, x.x, x.x, h, h *hh <CR><LF>
| | | | | | | |
| | | | | | | +--------------------------- 8
| | | | | | +------------------------- 7
| | | | | +--------------------------- 6
| | | | +------------------------- 5
| | | +------------------------ 4
| | +----------------------- 3
| +--------------------- 2
+---------------------------- 1
1. UTC time of the GGA or GNS fix associated with this sentence
2. Expected error in latitude (see Note 1)
3. Expected error in longitude
4. Expected error in altitude
5. ID number (see Note 2) of most likely failed satellite
6. Probability of missed detection for most likely failed satellite
7.Estimate of bias on most likely failed satellite
8.Standard deviation of bias estimate
1. UTC of position
2. Latitude, N/S
3. Longitude, E/W
4. Mode indicator
5. Total number of satellites in use, 00-99
6. HDOP
$--GGA,hhmmss.ss,llll.lll,a,yyyyy.yyy,a,x,xx,x.x,x.x,M,x.x,M,x.x,xxxx*hh<CR><LF>
| | | | | | | | | | | | | | |
| | | | | | | | | | | | | | +--------------- 11
| | | | | | | | | | | | | +------------------ 10
| | | | | | | | | | | | +--------------------- 9
| | | | | | | | | | +---+--------------------- 8
| | | | | | | | +---+------------------------- 7
| | | | | | | +------------------------------ 6
| | | | | | +---------------------------- 5
| | | | | +------------------------- 4
| | | +----+------------------------ 3
| +---+---------------------------------- 2
+-------------------------------------------- 1
1. UTC of position
2. Latitude, N/S
3. Longitude, E/W
4. GPS quality indicator (0: No fix, 1: GPS, 2: Differential, 8: Demo mode)
5. Number of satellite in use,00-12, may be different from the number in view
6. Horizontal dilution of precision
7. Antenna altitude above/below mean sea level, m
8. Geoidal separation, m
9. Age of differential GPS data
10. Differential reference station ID, 0000-1023
11. Checksum
$--GSA,a,x,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,x.x,x.x,x.x,h*hh<CR><LF>
| | | | | |
| | | | | +----------------- 6
| | | | +--------------------- 5
| | | +------------------ 4
| | +-------------------------------------------+------- 3
| +-------------------------------------- 2
+--------------------------------- 1
NOTE 1: Configured autonomous repeat interval in seconds. This field should be set to
NULL in response to a query if this feature is supported.
This field can be used can be used to indicate the current equipment status. This could be the
result of an built-in integrity testing function.
NOTE 3: The sequential sentence identifier provides a message identification number from 0
to 9 that is sequentially assigned and is incremented for each new sentence. The
count resets to 0 after 9 is used.
$--RMC,hhmmss.ss,A,llll.ll,a,yyyyy.yyy,a,x.x,x.x,xxxxxx,x.x,a,a,a*hh<CR><LF>
| | | | | | | | | | | |
| | | | | | | | | | | +-------------------- 9
| | | | | | | | | +--+------------------ 8
| | | | | | | | +-------------------------- 7
| | | | | | | +---------------------------- 6
| | | | | | +---------------------------- 5
| | | | +------+--------------------------- 4
| | +-- -+-------------------------------------- 3
| +---------------------------------------- 2
+-------------------------------------------- 1
S = Safe. when the estimated positioning accuracy (95 % confidence) is within the
selected accuracy level corresponding to the actual navigation mode, and/or
integrity is available and within the requirements for the actual navigation
mode, and/or a new valid position has been calculated within 1 s for a
conventional craft and 0,5 s for a high speed craft.
U = Unsafe when the estimated positioning accuracy (95 % confidence) is less than
the selected accuracy level corresponding to the actual navigation mode, and/or
integrity is available but exceeds the requirements for the actual navigation
mode, and/or a new valid position has not been calculated within 1 s for a
conventional craft and 0,5 s for a high speed craft.
$--VTG,x.x,T,x.x,M,x.x,N,x.x,K,a*hh<CR><LF>
| | | | | | | | | |
| | | | | | | | | +------- 6
| | | | | | | | +--------- 5
| | | | | | +--+----------- 4
| | | | +--+----------------- 3
| | +--+----------------------- 2
+--+----------------------------- 1
1. Course over ground, degrees true
2. Course over ground, degrees magnetic
3. Speed over ground, knots
4. Speed over ground, km/h
5. Mode indicator(see note)
6. Checksum
$--ZDA,hhmmss.ss,xx,xx,xxxx,xx,xx*hh<CR><LF>
| | | | | | |
| | | | | | +--------- 7
| | | | | +----------- 6
| | | | +-------------- 5
| | | +------------------ 4
| | +---------------------- 3
| +------------------------ 2
+--------------------------------- 1
1. UTC
2. Day, 01 to 31 (UTC)
3. Month, 01 to 12 (UTC)
4. Year (UTC)
5. Local zone hours, 00h to +-13h
6. Local zone minutes, 00 to +59 as local hours
7. Checksum
APPENDIX V DOC
Declaration of Conformity
0098/202X
NGR-3000
GPS equipment
(Product)
Item No.: MED/4.14.
to which this declaration relates conforms to the following standard(s) or normative document(s)
Regulations Testing standards
SOLAS 74 as amended, IEC 60945 (2002) incl. IEC 60945 Corr. 1 (2008),
Regulations V/18, V/19 & X/3, IEC 61108-1 Ed. 2.0 (2003),
IMO Res. A.694(17), IEC 61162-1 ed5.0 (2016-08), IEC 61162-2 ed1.0 (1998-09),
IMO Res. MSC.36(63), IEC 61162-3 ed1.2 Consol. with am1 ed. 1.0 (2010-11) and am2
IMO Res. MSC.97(73), ed. 1.0 (2014-07),
IMO Res. MSC.112(73), IEC 61162-450 (2018)
IMO Res.MSC.191(79), IEC 62288 Ed. 2.0 (2014-07)
IMO Res. MSC.302(87) IEC 62923-1 (2018), IEC 62923-2 (2018)
(Regulations)
We hereby declare that the product complies with the Directive 2014/90/EU and regulation (EU)
2020/1170.
www.nsrmarine.com
July, 2021