Quantcast
Channel: Raymarine forum - All Forums
Viewing all 8621 articles
Browse latest View live
↧

Diagnostics - a/c/e/eS/gS-Series MFD NMEA 0183 Buffer

September 26, 2016, 10:21 am
$
0
0
Should one of the MFD's NMEA 0183 ports be interfaced to a NMEA 0183 talker or listener and there be a suspected communications issue between the devices, then examining the MFD's NMEA 0183 port buffers may be very helpful in determining whether the MFD is transmitting data to or receiving data from the device supporting NMEA 0183 communications protocol. The list of supported NMEA 0183 output Sentence Indentifiers (TX) and input Sentence Identifiers may be found within the appendices of the latest version of the LightHouse MFDs Operation Instructions.

Executing the command sequence HOME->SET-UP->MAINTENANCE->DIAGNOSTICS->INTERFACES->NMEA 0183-x (where x is the number of the port that the NMEA 0183 device has been interfaced to)->BUFFER->DIRECTION->BOTH; START BUFFER will cause the displayed buffer to list the direction (TX or RX), time, and message content of all NMEA 0183 communications being transmitted and received by the MFD. When seeking to diagnose a problem with received data, it can be helpful to first configure the buffer to display only received (RX) NMEA 0183 communications by setting the buffer's Direction setting to RX. If requested, the buffer may be recorded to a microSD memory card by using the buffer's START RECORDING feature. Generally, it will only be necessary to record a minute or so of data for diagnostic purposes. Recording may be stopped by using the buffer's STOP RECORDING feature. The following file will be created and saved to your microSD memory card when buffer recording has been commanded:
----- NMEA0183-x_yyyyyy.log (where x is the NMEA 0183 Port number and yyyyyyy is the log number).

[Image: attachment.php?aid=593]

Should there be a concern that the MFD's NMEA 0183 port is not operational, then a wraparound test of the MFD's NMEA 0183 ports may be performed per the instructions within the FAQ found here.


CRAFAQ#

.png  Dump038.png (Size: 55.76 KB / Downloads: 3)
↧
Search

Diagnostics - a/c/e/eS/gS-Series MFD SeaTalkng / NMEA 2000 Buffer

September 26, 2016, 11:00 am
$
0
0
At the time that this FAQ was posted, the SeaTalkng / NMEA 2000 diagnostic buffer of the a/c/e/eS/gS-Series MFDs was limited to displaying and logging raw, untranslated (hexadecimal) data received by and transmitted by the Data Master MFD. Accordingly, if seeking to investigate a problem regarding SeaTalkng / NMEA 2000 communications within a system, it may be necessary to interface a NMEA 2000 bus analyzing tool (ex. Actisense NGT-1-USB w/Actisense NMEAReader PC software, etc.) as a spur device to the SeaTalkng / NMEA 2000 backbone to monitor and obtain detailed information concerning the system's SeaTalkng / NMEA 2000 communications. As many NMEA 2000 bus analyzer products (ex. NMEAReader) convert the raw SeaTalkng / NMEA 2000 data into translated data, such analyzers can be quite helpful in analyzing and identifying problems, and should be part of a properly equipped installer's / troubleshooter's tool kit. This is particularly true for SeaTalkng / NMEA 2000 communications problems involving third party devices (ex. engine system gateways, tank level sensors, fuel flow sensors, etc) having a NMEA 2000 communications interface.

[Image: attachment.php?aid=595]

As an example, the most common cause for failure of a Raymarine MFD to display data from a NMEA 2000 source of engine, tank level, or fuel flow sensor data is failure to configure the sensor's Instance Number (may require a third party display or third party computer application NMEA 2000 communications interface ... it is accordingly recommended that the device manufacturer be consulted regarding how to assign a NMEA 2000 Instance Number to the device(s)) in accordance the NMEA 2000 convention for instancing engines, tank level sensor, fuel flow sensors, etc.. In the NMEA 2000 convention, the port-most engine, tank level sensor, and fuel flow sensor will be assigned Instance Number "0". The engine, tank level sensor, and fuel flow sensor located closest to the port engine, tank level sensor, and fuel flow sensor will be assigned instance "1". The engine, tank level sensor, and fuel flow sensor located closest to and starboard of the engine, tank level sensor, and fuel flow sensor assigned instance "1" will in turn be assigned instance "2" ... and so on. Raymarine's a/c/e/eS/gS-Series MFDs feature support for interfacing up to five engines, fuel tank level sensors, and fuel flow sensors. As Raymarine products are neither designed to calibrate nor assign NMEA 2000 Instance Numbers to third party sensors having NMEA 2000 communications interfaces, it may be necessary to perform such calibrations or assignments using a third party display or a computer which has been interfaced to the SeaTalkng / NMEA 2000 backbone and is running software from the sensor's manufacturer.

The list of supported NMEA 2000 PGNs may be found within the appendices of the latest version of the LightHouse MFDs Operation Instructions. Executing the command sequence HOME->SET-UP->MAINTENANCE->DIAGNOSTICS->INTERFACES->N2K/STNG->BUFFER->DIRECTION->BOTH; START BUFFER from the system's Data Master MFD (HOME->SET-UP->DATA MASTER) will cause the displayed buffer to list the direction (TX or RX), time, and message content of all SeaTalkng / NMEA 2000 communications being transmitted and received by the MFD. When seeking to diagnose a problem with received data, it can be helpful to first configure the buffer to display only received (RX) SeaTalkng / NMEA 2000 communications by setting the buffer's Direction setting to RX. If requested, the buffer may be recorded to a microSD memory card by using the buffer's START RECORDING feature. Generally, it will only be necessary to record a minute or so of data for diagnostic purposes. Recording may be stopped by using the buffer's STOP RECORDING feature. The following file will be created and saved to your microSD memory card when buffer recording has been commanded:
----- N2K_yyyyyy.log (where yyyyyyy is the log number).

[Image: attachment.php?aid=594]


CRAFAQ#

.png  Dump039.png (Size: 45.87 KB / Downloads: 5)

.png  Clipboard02.png (Size: 161.64 KB / Downloads: 3)
↧
↧

ST600R

September 26, 2016, 11:06 am
$
0
0
I think I know the answer but wanted to double check. I'm going to install the new evo 400 on my sailboat and was wondering if there is a way to incorporate the ST600R into the system. Thanks.
↧

C80 Classic v5.16 firmware hang and boot loop with Navionics freshest data update

September 26, 2016, 12:10 pm
$
0
0
Hi, I'm not sure if this is the place to report this, but I thought I would try here.

I have a C80 (Classic) MFD using firmware 5.16 (which should be the latest available as of today).

After updating my CF card using the Navionics 'Freshest Data' and then trying the card in my C80, the MFD will hang.

The symptoms are that when the first notice screen is displayed, when the C80 is normally asking you to confirm with the OK button, you can't read the text as only a white blank window is showing. Button presses do nothing, the C80 is unresponsive, but will beep with some key presses.

If you wait long enough the C80 may reboot itself.

This boot loop continues forever.

I also tried to do a factory reset and this does not solve the problem.

I also tested my card on a friends C120 that also had firmware 5.16, it had the same problem. Yet my friend's C120 card (which was updated this just 3 or 4 months ago) worked perfectly in my C80.

My CF card is a 2GB Navionics card, where my friends was a 16 GB Navionics card.

Contacting Navionics about this, they had me send my CF card to them for analysis of the issue. I believe that they originally thought I had a bad CF card, even though I was able to update the card and also read it in two different USB CF card readers.

Their root cause analysis showed that after updating the card, the .BP2 files placed onto the card by their update were causing the C80 to hang. A work around is to manually delete all *.BP2 files from the card. Somehow the *.BP2 files are not compatible with the 5.16 firmware on the C80 Classic. They claimed that the .BP2 files contain information such as phone numbers and other information about marinas, etc. which is not used by the C80 Classic MFDs.

If you have this issue, as a work around to this issue, after performing a 'Freshest Data' update, delete all files that end in .BP2 from the card chip before trying to use it in your Classic MFD.

I hope this information helps you.

I'd like to know if it is possible that Raymarine could investigate this issue and possibly issue a new firmware to solve it, or work with Navionics to find some other method to resolve this issue?

I'm sure there still are a lot of us out there that have older boats with reliable Raymarine C70, C80 and C120 (classic) MFDs on board that would like to maintain compatibility with the Navionics freshest data updates.

I asked Navionics to see if they could change their web based "Freshest Data" updater to not install the .BP2 files on the Raymarine Classic MFDs if those files were not compatible with the Classic MFDs, but I'm not sure if they will consider this.
↧

ES78 Fuel Data

September 24, 2016, 7:20 pm
$
0
0
I am unable to get the fuel level gauge to work on my ES78. I get fuel flow (GPH), MPG, gallons used and gallons remaining. However, on the display for percentage left it remains blank. Do I need to have a fuel level sensor installed in my tank?
↧
↧

SL72 Plus

September 26, 2016, 10:31 am
$
0
0
Good afternoon. This is my first post. I have the combination GPS/ Radar SL72. Currently the radar works fine, but the GPS is frozen. It is stuck on 24 nm and it has the hour glass figure on a blank screen.

Any ideas how to fix this?

Thanks in advance.

Sean
↧

Source Identification with P70

September 26, 2016, 10:38 am
$
0
0
I have a P70 AP controlhead. SPX 30 Course Computer.

I have a B&G GPS

I connected the GPS via NMEA 0183 to the SPX 30

I connected the P70, i60 Wind and i60 depth as shown in the manual and online using the proper coded cables to make a SeaTalkng backbone.

Nothing is taking to the AP

When I select source nothing. Or I get a message saying the SPX30 doesn't support that.

I tried to start the commissioning process over but the Commissioning menu will not appear on the P70

What am I doing wrong?

Thanks
Bill
↧

C120 Classic MFD cursor key

September 27, 2016, 7:02 am
$
0
0
In the past, our MFD's left cursor button went inoperative. Our workaround, until we got to shore and shipped it off for repair, was to go around the world via large scale and right cursor to put the cursor where we needed it. The MFD was subsequently repaired, but is now experiencing this problem again. As this has been addressed before (but long out of warranty, I'm sure), does this spell the demise of this unit?

From my prior instance, I believe this to not be a user-serviceable, or, likely, even a local shop rep-serviceable, event. The tech, who I regard as very competent, declined to get inside the unit in this case.

So, I assume it will go back again. My recollection is foggy as to what was the issue, but I *think* that it was a ribbon cable. If that is a recurrent failure, it seems that some more permanent solution might have, by this time, be achieved.

Is there hope for my MFD? Is there anything =I= can do in the time between now and when we return to where we could comfortably wait while we ship it off?

L8R

Skip
↧
Search

ST 60+ STW adjustment

September 27, 2016, 7:09 am
$
0
0
We sent in our venerable ST60 speed log for repair; it was seriously enough compromised that we incurred the maximum flat rate.

The "repair" was actually "replace all but the housing," but with an ST60+ unit.

So, we have a new speed log. However, unless there's a different impeller for this or the original, we have a STW discrepancy on the order of close to 100%; we read 3 and change at what should be more like 6 and change, 4 and 8 and the like. At lower speeds, it's very much worse; 1's for 4-5, for example.

This unit was cleaned and inserted just before departure, so I very much doubt fouling.

I'm sure there is some key combination to adjust the compensation for speed, and that, like our other two speed transponders, one Raymarine and the other a very venerable Signet, you have to choose a sweet spot, as the translation isn't linear.

Thus, likely we'd try to adjust for a 'standard' 5 knots or so.

How do we do that?

Thanks.

Skip
↧
↧

Wonky reports on DS500X Fish Finder

September 27, 2016, 7:28 am
$
0
0
We previously had a different finder, which used a tri-sponder perfectly.

That is, it did depth, temperature and speed reliably.

When we installed the new unit (DS500X), we bought two adapter cables which let that transponder 'talk' to our unit.

It didn't do well, and the advice here at the time was to install the proper transponder - an Airmar B744. Enough internet time spent, and we had the proper unit with the right cable termination.

Except that:

The depth is very intermittent. Sometimes it's there, but mostly we get a flashing line dot line (feet and decimal). The good news is that when it DOES display, we've found it to be accurate, and with the available +/- adjustments, exactly right for water depth (as opposed to under the keel, the only choice I have on my other two depth sounders).

The temperature was previously fairly close, after the adjustments available in the setup menu. Now they routinely read in the high 100s - 160-180F - which isn't in the range of adjustment, never mind that this is new to this trip.

And, the speed is intermittent, as well. Despite being newly cleaned and installed just before our trip, mostly we get no speed (0.0), and when we DO register, it's under by perhaps half. That MAY be adjustable in the range available in the menu for adjustments. Our previous sounder had a wired impeller; this one is inductive, I presume, as there's no wire to the impeller, and a slot up the flap module to allow the transponder cable to come out.

The transponder is on the stem and about 3' deep. It should always see 'clean' water, with no turbulence or other flow issues. It was painted with transponder antifouling at installation, but likely even that is gone after repetitive cleanings.

This all sounds like an issue with the transponder, which would be a huge issue, as, of course, you can't replace it unless you're hauled, and we anticipate that won't be for at least a couple of years. Just by happenstance, I have a replacement (somehow different, as the length of the speed impeller plug is longer than the current one based on a different through-hull termination for securing the impeller).

Or, is there a series of checks and/or adjustments I can do to prove the transponder?

Thanks.

Skip
↧

Rudder reference for EV200

September 27, 2016, 7:57 am
$
0
0
I recently purchased an EV200 power autopilot package and it comes with a rudder reference transformer geared for inboard engines. A rudder reference is recommended for EV200, but is it required? My previous SPX10 worked okay without it. If I need to install a rudder reference, will the M81188 work on the EV200 or is there an adapter plate for outbooard engines to mount the rudder reference that came with the EV200?
↧

C-95 - AIS 650 GPS conflict

September 27, 2016, 8:23 am
$
0
0
I am using a C95 chartplotter connected over a Seatalk NG network to an ITC-5 (for wind and speed) and an AIS 650 transceiver. I am also using 2 x i70s displays and one p70 display for the autopilot. All gear is Raymarine.
I HAVE UPDATED ALL MY SOFTWARE FOR ALL MY RAYMARINE COMPONENTS with the latest update.

My problem is the two GPS receivers in the system (the one that connects to the AIS 650 and the internal one on the C-95) seem to conflict. I usually run both and use the internal settings on the i70s and the C-95 to select which GPS source to receive. Usually all units are set to read from the internal GPS on the C-95 except the AIS which cannot be made to accept an external signal other then the one from its own hardwired GPS antenna.

1st symptom: while running both AIS and Chart plotter, the chart plotter will loose its fix, shutdown and restart on its own. A thorough check of DC supply discarded that as a cause.

2nd symptom: When I switch off the internal GPS on the C-95 and try to select the AIS GPS as the source for fix in the DATA SOURCES menu under SET UP on the C-95, the AIS does not show up as a source choice. Although the AIS shows up as a DATA SOURCE option under the i70s set up menu.

3rd symptom: With the internal GPS in the OFF position, under the VIEW satellites menu in the SETUP for C-95 internal GPS, the display does not show any satellites BUT does show AIS 650 as GPS source !!

4th symptom: When using the C-95 internal GPS as DATA SOURCE and running the AIS 650 and its own GPS, under the PRO AIS2 app used to configure the AIS 650, the page displaying satellite signal shows no satellite at all. As soon as you switch the C-95 and its GPS off, the AIS PRO satellite page displays all satellite in view and shows a solid fix.

So there's a conflict somewhere but I have no idea how to solve it. All I want is ideally for the AIS GPS to be the sole source of positioning on board. And maybe strictly use the internal C-95 GPS as a back up if the AIS fails.
Any help much appreciated. Thx JB
↧

gps datum error

September 27, 2016, 9:46 am
$
0
0
When I go through the setup commands, specifically the data logs, all items show something besides auto except gps datum.I'm using a miniplex 3wi-2NK multiplexer to deliver the gps data to autopilot, and depth and speed from ST60 triad through seatalk1 to my EV400, newly installed autopilot via SeatalkNG. When I check data logs, each variable defines where the data is coming from. Depth was not coming across and the people at ShipModul, found a firmware problem and fixed that.
Everything is working marvelously, except when I get to data log for gps datum, it searches the network and finds nothing, so all I have is auto, therefore nothing is coming from the gps.

First, how important is ""gps datum'' value to autopilot? How will this loss affect performance? I want to know before I asked ShipModul to fix this problem.

One other item. When I add the rudder sensor to the EV400 system, do I have to reset the system and start over and lose the vessel adaptations the brain has made to the vessel or can I just go to commissioning and just recalibrate the rudder sensor?

Fred
↧
↧

Fault isolation of depth acquistion problem associated with a depth sounding product

September 27, 2016, 10:40 am
$
0
0
In the absence of an EDI transducer tester (relatively few marine electronics installers are so equipped), fault isolation of problems associated with a depth sounding product are typically accomplished by testing the depth sounding product with another compatible transducer which was known to be operational. In many cases, it is quite cost effective and more convenient for the customer to perform such fault isolation, as the cost of another compatible transducer may be close to or less than the cost of having a Certified Raymarine Installer visit the vessel to perform such fault isolation.

Transducers used for such testing are either suspended over the side of the hull or, in the case of non-cored fiberglass hulls less than one inch thick, placed on the inside of the hull atop a zipper locking plastic bag which has been completely filled with water. When performing such testing, the vessel must be located in water which is at least three feet in depth below the transducer, but not in a depth exceeding the maximum depth capability of the depth sounding product. Should the depth sounding product fitted with the test transducer be capable of reliably reporting depth using each of its supported frequency settings, then the currently installed transducer would be deemed to have been the cause of the depth related failure. However, should the depth sounding product fitted with the test transducer not be capable of reliably reporting depth using each of its supported frequency settings, then the fault may be rooted in both the transducer and/or the depth sounding product. Some EDI transducer testers are also capable simulating the output of a transducer to permit the depth sounding product to be tested. In the case of the latter, it would be recommended that the depth sounding product (if still supported) be sent to Raymarine’s Product Repair Center to be bench checked / serviced.


CRAFAQ#
↧

Pushrod extension for Tiller Pilot ST1000

September 27, 2016, 9:14 am
$
0
0
I Need to choose pushrod extension for Raymarine Tiller Pilot ST1000.
The distance from the mounting socket on the starboard to the center line (“C") is 705 mm about 27.8 in.
Which extension should I buy?
The D006 (for 27.2 in) or the D007 (for 28.2 in)
When motoring the propeller walks the the stern to port so the tiller has to be pulled to starboard to correct the course which make me think that the shorter extension may be better.
↧
Search

Cold weather and Ray e97

September 27, 2016, 5:04 pm
$
0
0
FINALLY having my Ray e97 and e127, ray star and Quantum radar networked and working fine, it is now time to pull the boat for the cold New England Winter. Temps average teens up here, but can go to 0 and below for a week at a time. My e97 is mounted in the dashboard of my 1994 Carver 390 CPMY. Can I just leave it there for the winter or should I remove it for the cold season and store inside where the temp is more moderate. I am concerned the cold can damage the screen as I have seen in some cases. if approved and left intact and damage occurs, is there any special warranty for repair?
↧

Images of equipment for diagrams

September 27, 2016, 5:48 pm
$
0
0
Are there images of the various pieces of equipment that I could download and then use to develop a network diagram for my new electronics system? I am currently using boxes and the images would be more meaningful as well as more attractive.
↧
↧

Adding a second chartplotter

September 27, 2016, 10:51 pm
$
0
0
Evening;

I am adding an eS78, Quantum radar, and AIS650 to my existing system (windvane with ITC-5, DST200 triducer, EVO autopilot with ACU-200/p70/EV-1, 3 i70 displays, Garmin GNT10 through a adapter cable, and a98 MFD). The MFD's have their own power supplies and the backbone is powered through the ACU-200.

I have everything connected with STng and the MFD's connected through Raynet and a 5 port switch.

Concept is that the a98 is in the cockpit and serves as primary GPS source, where the es78 is belowdecks and serves as data master. This is also the MFD that interfaced with Quantum radar.

I have a few questions about how to best operate this system, especially with regards to the wifi and networking:

1. The power layouts required me to power the AIS/VHF/AIS100 splitter, es78, and rest of the system from separate breakers. Is there a specific order they should be powered up in order to ensure that everything comes and shares data appropriately? In my initial bench testing, i had some issues getting the AIS650 to talk to the MFD and was unsure what i did that eventually fixed it (I was poking around in the NMEA input settings when it started talking to the MFD; i figured these would be irrelevant for a STng connected AIS system.)

2. Should I connect to the radar from the cockpit (a98) display as well, or rely on the Raynet switch to transfer all the data? will i be able to power up and standby the radar from that MFD?

3. For a multi-MFD system, what exactly does the 'data master' do? is that relevant only to ethernet stuff, or STng as well?

4. I attempted to select the GPS source, but got a message that the ACU-200 prevented that action. Is this normal? the p70 has GPS source set to 'auto.'

If i want to use Raycontrol for additional display or a wifi hotspot to get weather data, how does that interact with the wifi radar and 2 chartplotters wifis?
6. If i want to interface my Standard Horizon GSC1700 radio to the belowdecks (eS78) MFD with NMEA 0183 for the purposes of getting DSC data, will that be promulgated over the network as well? Any specific precautions/settings to make that work?

Thanks in advance for the assistance. Can post a diagram if requested.

Respectfully,

Heath
↧

GPS Connection

September 28, 2016, 3:23 am
$
0
0
Is this correct for wiring a NMEA version Raystar 120 to an AIS 650?

120 black to AIS yellow.
120 yellow to AIS gray

Then the AIS pink and purple to NMEA 4800 baud equipment such as radios.

Thank you.
↧

Smart Controller loses connection

September 28, 2016, 8:26 am
$
0
0
My smart controller loses the network connection every few minutes even when right alongside of the base unit. It is getting SeaTalk communication during these outages according to incoming voltage on the SeaTalk side. Any ideas?
↧
Viewing all 8621 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>