chrishelen
N/A
Hi, i am trying to get my garmin 72 handheld to talk to my raymarine sd400x fishfinder via a nmea cable, i think i have wired it up correctly but no data is showing on the fishfinder, what am i doing wrong?
NMEA
- Thread starter chrishelen
- Start date
RestlessL
Well-Known Member
Garmin units need to be set to output NMEA, and not Garmin protocol.
chrishelen
N/A
how would i do that?
Tranona
Well-Known Member
If you have the handbook the instructions of the menu to access are there.
chrishelen
N/A
Thanks for that but I have a manual, and have followed the instructions to a tee, but still a blank screen.i think i might have to re check my wires in the morning.
Independence
Well-Known Member
I'd tele them.
I'm not particularly good on that sort of thing myself and tele them Monday to ask a similar question. I found them very patient and helpful with good down to earth explainations like 'connect the black wire to the brown one'.
I'm not particularly good on that sort of thing myself and tele them Monday to ask a similar question. I found them very patient and helpful with good down to earth explainations like 'connect the black wire to the brown one'.
chrishelen
N/A
Thats a good idea, those are the sort of instructions i can understand.
Refueler
Well-Known Member
NMEA standard says that you can connect cables without any damage occurring. According to the standard that means you can try out different combinations of NMEA cables connected - just don't mix up power with it !!
Another area that sometimes knocks it out - if ground is made on both units when only one needs it. Other set-ups need both units ground connected ... we are talking screen ground NMEA here - not bonding etc.
Another area that sometimes knocks it out - if ground is made on both units when only one needs it. Other set-ups need both units ground connected ... we are talking screen ground NMEA here - not bonding etc.
FullCircle
Well-Known Member
Its not that Nige.
The menu system needs to be set to NMEA4800 rather than GARMIN as an output signal.
The wires are the easy bit.
The menu system needs to be set to NMEA4800 rather than GARMIN as an output signal.
The wires are the easy bit.
misterg
Well-Known Member
OK, what have you connected to what?
(Is it a ds400x ff ??)
FF connections:
Pin No. Function Color
1 Battery negative – Black
2 Battery positive + (10.0VDC to 18.0VDC) Red
3 NMEA Input + White
4 N MEA Input – Green
5 CGND Gray
6 NMEA Output + Yellow
7 NM EA Output – Brown
GPS72 connections:
Red Power
Black Gnd
White NMEA in
Brown NMEA out
Assuming you want data from the GPS to the FF I would connect:
FF white --> GPS Brown
FF Green --> GPS Black
Go to the GPS setup menu and set the 'interface' tab to NMEA/NMEA - default is Garmin (all from memory)
(Could also connect:
FF Yellow --> GPS White
FF Brown --> GPS Black
if you wanted data from FF to GPS)
HTH
Andy
(Is it a ds400x ff ??)
FF connections:
Pin No. Function Color
1 Battery negative – Black
2 Battery positive + (10.0VDC to 18.0VDC) Red
3 NMEA Input + White
4 N MEA Input – Green
5 CGND Gray
6 NMEA Output + Yellow
7 NM EA Output – Brown
GPS72 connections:
Red Power
Black Gnd
White NMEA in
Brown NMEA out
Assuming you want data from the GPS to the FF I would connect:
FF white --> GPS Brown
FF Green --> GPS Black
Go to the GPS setup menu and set the 'interface' tab to NMEA/NMEA - default is Garmin (all from memory)
(Could also connect:
FF Yellow --> GPS White
FF Brown --> GPS Black
if you wanted data from FF to GPS)
HTH
Andy
Lyonesse
New Member
Sailsoft has a good and clear drawing on how to make a Garmin NMEA connection cable.Go to www.sailsoft.nl, choose menu item "How to connect your GPS to your PC" at the left and click "Garmin" at the bottom of that page.
Wunja
Well-Known Member
Looking at the manuals, you have a slightly more fundamental problem than the wiring.
The fishfinder will only receive BWC, BWR, GLL, ZDA, RMB, VTG, HDG, HDT sentances. The GPS will only send GPRMC, GPGGA, GPGL, GPBWC, GPVTG, GPXTE, GPRMB and optionally GPGSA, GPGSV, GPWPL, GPRTE. Therefore your GPS isn't saying anything that interests the fishfinder.
However, all is not lost. The fishfinder sends DPT, MTW and VHW sentences which your GPS can understand. This means you can use some of the depth related alerts on the GPS.
The fishfinder will only receive BWC, BWR, GLL, ZDA, RMB, VTG, HDG, HDT sentances. The GPS will only send GPRMC, GPGGA, GPGL, GPBWC, GPVTG, GPXTE, GPRMB and optionally GPGSA, GPGSV, GPWPL, GPRTE. Therefore your GPS isn't saying anything that interests the fishfinder.
However, all is not lost. The fishfinder sends DPT, MTW and VHW sentences which your GPS can understand. This means you can use some of the depth related alerts on the GPS.
chrishelen
N/A
Thanks for all the replys, i thought the FF might not be compatable with the GPS, back to the drawing board i guess.
Danny
Well-Known Member
[ QUOTE ]
The fishfinder will only receive BWC, BWR, GLL, ZDA, RMB, VTG, HDG, HDT sentances. The GPS will only send GPRMC, GPGGA, GPGL, GPBWC, GPVTG, GPXTE, GPRMB and optionally GPGSA, GPGSV, GPWPL, GPRTE. Therefore your GPS isn't saying anything that interests the fishfinder.
[/ QUOTE ]Should be OK then! The fishfinder understands the RMB sentence (minimum nav info sentence) and the GPS sends it. No problem.
The fishfinder will only receive BWC, BWR, GLL, ZDA, RMB, VTG, HDG, HDT sentances. The GPS will only send GPRMC, GPGGA, GPGL, GPBWC, GPVTG, GPXTE, GPRMB and optionally GPGSA, GPGSV, GPWPL, GPRTE. Therefore your GPS isn't saying anything that interests the fishfinder.
[/ QUOTE ]Should be OK then! The fishfinder understands the RMB sentence (minimum nav info sentence) and the GPS sends it. No problem.
alan
Well-Known Member
"RMB - The recommended minimum navigation sentence is sent whenever a route or a goto is active. On some systems it is sent all of the time with null data. The Arrival alarm flag is similar to the arrival alarm inside the unit and can be decoded to drive an external alarm. Note the use of leading zeros in this message to preserve the character spacing. This is done, I believe, because some autopilots may depend on exact character spacing. "
RMB - Recommended Minimum Navigation Information
To be sent by a navigation receiver when a destination waypoint is active.
14
1 2 3 4 5 6 7 8 9 10 11 12 13| 15
| | | | | | | | | | | | | | |
$--RMB,A,x.x,a,c--c,c--c,llll.ll,a,yyyyy.yy,a,x.x,x.x,x.x,A,m,*hh<CR><LF>
Field Number:
1) Status, A= Active, V = Void
2) Cross Track error - nautical miles
3) Direction to Steer, Left or Right
4) TO Waypoint ID
5) FROM Waypoint ID
6) Destination Waypoint Latitude
7) N or S
8) Destination Waypoint Longitude
9) E or W
10) Range to destination in nautical miles
11) Bearing to destination in degrees True
12) Destination closing velocity in knots
13) Arrival Status, A = Arrival Circle Entered
14) FAA mode indicator (NMEA 2.3 and later)
15) Checksum
Example: $GPRMB,A,0.66,L,003,004,4917.24,N,12309.57,W,001.3,052.5,000.5,V*0B
This sentence does not contain current lat and long for instance.
This may/or not be of interest to the fishfinder. Depends on what info the OP was actually trying to get into the FF.
RMB - Recommended Minimum Navigation Information
To be sent by a navigation receiver when a destination waypoint is active.
14
1 2 3 4 5 6 7 8 9 10 11 12 13| 15
| | | | | | | | | | | | | | |
$--RMB,A,x.x,a,c--c,c--c,llll.ll,a,yyyyy.yy,a,x.x,x.x,x.x,A,m,*hh<CR><LF>
Field Number:
1) Status, A= Active, V = Void
2) Cross Track error - nautical miles
3) Direction to Steer, Left or Right
4) TO Waypoint ID
5) FROM Waypoint ID
6) Destination Waypoint Latitude
7) N or S
8) Destination Waypoint Longitude
9) E or W
10) Range to destination in nautical miles
11) Bearing to destination in degrees True
12) Destination closing velocity in knots
13) Arrival Status, A = Arrival Circle Entered
14) FAA mode indicator (NMEA 2.3 and later)
15) Checksum
Example: $GPRMB,A,0.66,L,003,004,4917.24,N,12309.57,W,001.3,052.5,000.5,V*0B
This sentence does not contain current lat and long for instance.
This may/or not be of interest to the fishfinder. Depends on what info the OP was actually trying to get into the FF.
Wunja
Well-Known Member
GPRMB sentence is the same as RMB?
Well that's me learned somthing!
/forums/images/graemlins/blush.gif
Well that's me learned somthing!
/forums/images/graemlins/blush.gif
alan
Well-Known Member
I think the GP just indicates the navigation device that is sending the RMB sentence ..... in this case a GPS receiver.
If you look at the first 'frame' of the NMEA sentence format: $--RMB,
you will see two blanks before the RMB which are for (I believe) the sending device ..... in this case GP for GPS. [Don't ask me what other possibilities there are though but I'm sure somebody else knows!!!!]
Just out of interest I looked up other "headers" :
Here are the NMEA-standard sentences. The names are listed without the
"talker ID", a two-character prefix that identifies the type of the
transmitting unit. By far the most common talker ID is "GP",
identifying a generic GPS, but all of the following
are well known:
GP Global Positioning System receiver
LC Loran-C receiver
II Integrated Instrumentation
IN Integrated Navigation
EC Electronic Chart Display & Information System
CD Digital Selective Calling (DSC)
If you look at the first 'frame' of the NMEA sentence format: $--RMB,
you will see two blanks before the RMB which are for (I believe) the sending device ..... in this case GP for GPS. [Don't ask me what other possibilities there are though but I'm sure somebody else knows!!!!]
Just out of interest I looked up other "headers" :
Here are the NMEA-standard sentences. The names are listed without the
"talker ID", a two-character prefix that identifies the type of the
transmitting unit. By far the most common talker ID is "GP",
identifying a generic GPS, but all of the following
are well known:
GP Global Positioning System receiver
LC Loran-C receiver
II Integrated Instrumentation
IN Integrated Navigation
EC Electronic Chart Display & Information System
CD Digital Selective Calling (DSC)
misterg
Well-Known Member
[ QUOTE ]
Looking at the manuals, you have a slightly more fundamental problem than the wiring.
[/ QUOTE ]
I really don't think there'll be a problem - the Garmin outputs the GLL sentence
Actual GPS72 output:
<font class="small">Code:</font><hr /><pre>$PGRME,27.5,M,23.2,M,36.0,M*18
$PGRMZ,292,f,3*12
$PGRMM,WGS 84*06
$GPRMC,150840,A,5317.6658,N,00324.7915,W,0.0,62.6,250408,4.4,W,D*2D
$GPRMB,A,,,,,,,,,,,,A,D*0E
$GPGGA,150840,5317.6658,N,00324.7915,W,2,05,3.7,88.7,M,50.9,M,,*63
$GPGLL,5317.6658,N,00324.7915,W,150840,A,D*5A
$GPBOD,,T,,M,,*47
$GPBWC,150840,,,,,,T,,M,,N,,D*76
$GPVTG,62.6,T,67.0,M,0.0,N,0.0,K*4D
$GPXTE,A,A,,,N,D*54</pre><hr />
The $PGRM sentences are Garmin proprietary, the $GP ones are NMEA.
Either RMC, GGA or GLL are understood by pretty much anything.
Andy
Looking at the manuals, you have a slightly more fundamental problem than the wiring.
[/ QUOTE ]
I really don't think there'll be a problem - the Garmin outputs the GLL sentence
Actual GPS72 output:
<font class="small">Code:</font><hr /><pre>$PGRME,27.5,M,23.2,M,36.0,M*18
$PGRMZ,292,f,3*12
$PGRMM,WGS 84*06
$GPRMC,150840,A,5317.6658,N,00324.7915,W,0.0,62.6,250408,4.4,W,D*2D
$GPRMB,A,,,,,,,,,,,,A,D*0E
$GPGGA,150840,5317.6658,N,00324.7915,W,2,05,3.7,88.7,M,50.9,M,,*63
$GPGLL,5317.6658,N,00324.7915,W,150840,A,D*5A
$GPBOD,,T,,M,,*47
$GPBWC,150840,,,,,,T,,M,,N,,D*76
$GPVTG,62.6,T,67.0,M,0.0,N,0.0,K*4D
$GPXTE,A,A,,,N,D*54</pre><hr />
The $PGRM sentences are Garmin proprietary, the $GP ones are NMEA.
Either RMC, GGA or GLL are understood by pretty much anything.
Andy
Refueler
Well-Known Member
[ QUOTE ]
Its not that Nige.
The menu system needs to be set to NMEA4800 rather than GARMIN as an output signal.
The wires are the easy bit.
[/ QUOTE ]
Few posts up and OP says they've followed all in the manual etc. - so it appears that they've already set to NMEA 0183 etc.
I know about the garmin protocol bit - I have an etrex and it's a pain that depending on PC program I want to run - I have to change from one to other ..... but that's getting away from OP. /forums/images/graemlins/wink.gif
Taking that they've changed to NMEA0183 - then it's down to testing combo's of connections etc. as I posted ...
Its not that Nige.
The menu system needs to be set to NMEA4800 rather than GARMIN as an output signal.
The wires are the easy bit.
[/ QUOTE ]
Few posts up and OP says they've followed all in the manual etc. - so it appears that they've already set to NMEA 0183 etc.
I know about the garmin protocol bit - I have an etrex and it's a pain that depending on PC program I want to run - I have to change from one to other ..... but that's getting away from OP. /forums/images/graemlins/wink.gif
Taking that they've changed to NMEA0183 - then it's down to testing combo's of connections etc. as I posted ...