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

[CA11] AIS target interception zone

$
0
0
Can the red box shown on the chart which appears to be the AIS target interception zone be disabled or turned off?

Our application is an Axiom 9 running the latest Lighthouse III software and an AIS700.

[CA11] Having problems with my thruhulls on axiom pro

$
0
0
I just got a new boat built and added the Raymarine axiom 12 pro and had the 2 12degree brass RV thruhulls put in. They were working amazing for about 4 months and now they will only work for about 2 hrs and then says transducer is not detected. If anyone has any suggestions please let me know. I have updated my system to the newest update from Raymarine.
Thanks so much

[CA11] a75, NMEA 183 and Seatalk1 integration

$
0
0
I need to connect st40 depth, st40 wind, st40 speed and a Standard Horizon GX2200 to a MFD A75. Can you please tell me what converters and cables do I need? Thanks in advance.

[TG11] Moving Homescreen App Icons

$
0
0
Hi - new Axiom 9 owner here with a question :)

So over the weekend I spent a lot of time creating my pages and settings with the custom overlays I would like to use. By default they were created on the far right homescreen page.

Once I got everything the way I wanted, I deleted the default app pages that come with the unit. I assumed my newly created custom app pages would migrate to the initial home screen but they did not.

So now every time I power up, I have to scroll right to see the App Icons. So my question is:

1 - Is there any way to drag my App Icons to different home screen pages? If no,
2 - Is there a way I can copy my overlay & Page settings so if I have to re-create my screens, I can just "Paste" the overlays, instead of having to add them 1 by 1 all over again?
3 - if the answer to both the above questions is NO, can this feature be added in a future update? I really hope I didnt waste 2hrs!

Thanks in advance!

Peter.

LED lighting Radio Frequency Interference RFI

$
0
0
Radio Frequency Interference RFi takes many forms and is a term generally used to cover the impact of uncontrolled Radio frequency emissions from one piece of equipment adversely affecting the performance of another piece of equipment.
Please look at this link for further information also this link here gives more background information on general interference,
The increasing use of LED lighting onboard vessels has coincided with an increase in interference affecting the performance of onboard VHFs, AIS, GMDSS and GPS systems. There are various published articles referring to one of the causes of the interference being attributed to the LED lighting systems themselves, whether the power supply, the transformers or even the lighting drivers themselves.

Examples range from situations where a maritime rescue coordination center in one port was unable to contact a ship that was involved in a traffic separation scheme incident by VHF radio. The ship involved was experiencing very poor AIS reception. AIS is dependent of using the VHF frequencies on the VHF radios for their communication links and are often integrated into the VHF transceivers. Other ships have experienced degradation of the VHF receivers, including AIS, caused by their LED navigation lights. The problem can be particularly severe when the LED lighting is installed near to the VHF antenna which has been shown to compound the reception problems which could account for the focus on navigation light sources of LEDs.

In a second example a customer installed two new LED spreader lights and both his VHF radios cut out when the lights are turned on. The power bar screen looked like he was transmitting on one of the radios and the other one just appeared dead even with local weather on. He never had any problems the previous year using halogen lights with the same wiring set-up.

A Final example was another customer just installed an LED tri-colour and an LED anchor light simply by changing a lightbulb. However, whenever the light is turned on (either one) he can only hear static on all stations on his VHF, no matter where the squelch is set.

LEDs don’t produce RF noise, however the LED drivers do. Although LEDs are efficient, the brighter ones do create heat which must be dissipated. As with any diode, a constant forward voltage applied sufficient to heat the device will cause current to increase, and if not limited will cause thermal runaway, causing it to fail. To avoid this problem, electronic LED drivers are necessary to regulate the current and maintain specified luminosity as input voltages vary and the LED heats up.
Low power LEDs that dim when voltage is reduced do not have regulators and will not cause RF interference. When regulators are used, LED drivers are normally part of the LED package itself.

The most efficient LED drivers operate with high switching frequencies which are necessary to reduce heat generated by the drivers as well as to minimize current consumption. The downside to this energy efficient LED driver switching circuitry is the generation of radio interference at higher frequencies. Switching circuitry has long been a source of HF interference.

Isolating the cause
It may be possible to test for the presence of LED interference by using the following procedures:
1. Turn off all equipment onboard to create a full ‘quiet ship’ condition, this includes electronic navigation equipment, onboard domestic equipment, heaters, refrigeration, lighting systems, power generation equipment, pumps, fans and any other electric motors as well as engines. Disconnect any external power sources to effectively shut the vessel down.
2. Turn the vhf radoio on, if possible only use a hand held vhf to eliminate any possible power supply induced interference
3. Tune the vhf to a ‘quiet’ channel for example channel 13
4. Adjust the VHF radio’s squelch control until the radio just outputs audio noise.
5. Re-adjust the VHF radio’s squelch control until the audio noise is quiet, only slightly above the noise threshold.
6. Turn on the LED light(s).
7. If the radio now outputs audio noise, then the LED lights are causing interference and depending on the level of this interference it could prove difficult to receive valid signals on that channel. If the radio does not output audio noise, then the LED lights are not causing a problem.

If the interference noise is found to have been raised, then it is likely that both shipboard VHF marine radio and AIS reception are being degraded by LED lighting.

Currently there is no EMC standard widely recognized by manufacturers of shipboard LED navigation and deck lighting.
Until a standard for shipboard LED lighting installed within three meters of VHF antennas is recognized, the best solution may simply be to ensure that any LED light purchased is warranted and then to perform EMC tests once installation is completed.

In short, those who may be considering use of LED vs incandescent lighting onboard their boats or have boats which have been manufactured with LED or CCFL lighting, please note that LED and CCFL lighting may interfere with receivers within marine electronics (ex. GPS receiver circuitry), communications equipment (VHF radio receivers, AIS receivers), and AM/FM receivers within entertainment systems. If experiencing such issues, the customer should test there systems under quiet ship conditions (to now include switching off all LED and CCFL lighting. Should the problem persist, then the customer may need to revert to incandescent lighting onboard the vessel.

RAYFAQ#

'76 Mako Transducer Location - Dragonfly 7

$
0
0
Need some help with proper transducer location. I mounted it initially at the bottom of the bilge, with it shooting through the hull. I had no issue with reading bottom at speed, but did lose some of the advertised bottom clarity that was advertised.

I have since mounted the transducer on the transom and now lose the depth at anything just over fast trolling speeds. As soon as I slow down, the reading comes back. I have attached some pictures of my transom and mounting. The boat is a '76 Mako 23' center console with a full flotation bracket. Any guidance would be greatly appreciated.

[Image: IMG_0256_zps4acwaoog.jpg]

[Image: IMG_0255_zpsmdjteyrr.jpg]

[CA11] LNC provided with new AxiomPro

$
0
0
Recently bought AxiomPro with LNC came with charts dated 2015. They also do not provide any depth definition. How do we update to latest version?

[CA11] Bridging AIS650 to e120-widescreen

$
0
0
Hi All,

We are having an issue with the mentioned link. The AIS unit functions correctly but it isn't speaking to the e120 via the SeaTalkng/NMEA 2000 network. We have thought about speaking linking them VIA nmea 0183 but this is quite difficult due to the cable configuration. Is there anything that we are missing?

On another note, we are not able to carry out the software updates on the e120 widescreen. As instructed, the software is downloaded from the website and placed on the root of the SD card. The unit is rebooted but nothing happens. Again, anyone have any ideas?

Many thanks,
Rom

[CA11] P70 Software Date via eS 127

$
0
0
Can the P70 update be downloaded directly to my MFD eS127? Set-Up>Maintenance>Check Online For Updates

My MFD is updated to LTII Ver 19.03

Thank You

[CA11] Headroom for retractable depth insert

$
0
0
I'm looking for a thru-hull type transducer, preferably bronze, for my depth-only i40. The web site shows P/N M78717 with a B17 housing, and a retractable insert. How much "headroom" is required to withdraw the sensor?

[CA11] Troubleshooting EV-1

$
0
0
I have a EV-100 Evolution Wheel Autopilot with EV-1 Sensor Core, p70 Autopilot Control Head, and ACU-100 Actuator Control Unit. The system worked great all season. Half way through the last sail, I got a "No Pilot" error. On the P70 i went to MENU->SET-UP->DIAGNOSTICS->ABOUT SYSTEM to see which components were talking on the network. Only the P70 and ACU100 were seen.

No lights on the EV-100. I verified the terminators were seated. I tried moving the EV-1 connection to a different port on the block. I tried a completely different cable. Still nothing.

It seems odd that this one component would fail while in use.

What other troubleshooting steps should I take?

Is there a way to check the EV-1 standalone, by itself?

I haven't seen any additional steps described in the manuals or troubleshooting guides.

Any help is appreciated.

KBG

[CA11] I40 wind unit on a sailboat

$
0
0
Hello,

I have a sailboat on which we have installed a Raymarine system that includes:

I40 Wind
Evolution Auto Pilot
Axiom MFD

My question is in regards to the I40 wind. I purchased this unit after reading the Raymarine website that says:

"Apparent wind speed and direction and true wind speed and direction.
Talks to your autopilot to steer your boat to a selected apparent wind angle."

and

"Big displays for smaller powerboats, yachts and RIBs, these compact yet powerful SeaTalk instrument displays offer full integration with Raymarine autopilots and navigation equipment and can be surface or trunnion mounted."

Based on this I thought it would be perfect for us. Since installing the unit and being on this form I have seen mention that the "I40 wind unit is not meant for sailboats". I am hoping you can clarify this? If the unit is capable of both true and apparent wind speed and direction and also capable of integrating with our autopilot, why is it not ideal for a sailboat?

Thank you!

[CA11] MFD e125-e127 to Vesselview 1.5 Cummins

$
0
0
For the experts and gurus, I need your advice, I have a Raymarine electronics (e125 and e127) on my boat and Cummins QSB5.9 engines with SmartCraft vesselview 1.5 displays, I am looking for a cable or interface or the way to connect the SmartCraft vesselview 1.5 with the Raymarine system in order to see the engines information on the MFD. I contact the company where I placed the original purchase of the SmartCraft vesselview, but they don’t sale it, can you tell me what I need, we’re to buy it,
I searched in this blog but I have not found the specific solution.

Thank you in advance for your advice and your time.

[TG11] ST2000+ not heading correctly in track mode

$
0
0
Hi There,
I have an ST2000+ tiller pilot interfaced (by via ST1 to STNG converter) with ST60+ instruments and an A70D Plotter/MFD.
Communication seems to be working ok, pilot pop ups appear on the ST60 displays and wind and track data appear on the ST2000+ When it is in the appropriate modes.

I can set up a route or waypoint and enter in to track mode ok.
However, I have noticed one glitch when the autopilot is in track mode.

Although BTW, Heading and COG all appear to be sensible, the autopilot seems to want to head 10-15 degrees to port of the BTW. I have tried this on a range of track headings.
I suspect that the error is that magnetic variation (about 13E here) is being applied once too often somewhere in the system.
I have variation in auto on the ST 60+ Graphic and on the A70D plotter.

Could you please advise the correct variation settings for each instrument/display and let me know if there are any other configuration changes I should check out and correct?
I am planning further test in the next few days, so if there’s anything I need to do to get you more data to work with please let me know.
Regards
Dave Davies.

redundant data on SeaTalk1 to SeaTalkng converter kit E22158

$
0
0
I have some questions regarding SeaTalk1 to SeaTalkng conversion:

I have an existing SeaTalk 1 based system ,consisting of an S3G course computer, 1 ST7002+, 1 ST6000+, 1 ST600R, 1 smart controller w. Base station, 1 ST60 Multi, ST60 Speed, ST60 Depth, ST 60 Wind, ST 60 close hauled, and 1 ST70 instrument.

I would like to connect this ST1 net to a NMEA2000 net in order to achieve the following:

Receive from ST1: apparent wind speed and direction, speed through water, depth below transducer, rudder angle.
Transmit to ST1: GNSS pos data, SOG, COG, variation, time and date, XTE, navigation data (active WP etc.) and
true heading from a sat compass.

I’m going to use a SeaTalk1 to SeaTalkng converter kit E22158. (I tried the ST70 for that purpose, but it freezes after some time).

Looking at the PGN-list of the E22158, it seems that all data I’d like to bring across would be covered. However I do not know what the behaviour would be if some data are redundant, but from different sources.

My first concern is heading: The S3G puts heading info onto ST1, and so would the converter. My preference would be to have the sat-compass true heading available on the ST70 to properly calculate set and drift, but have the course computer stick to its own jaw rate assisted flux-gate. The later works rather well that way, and I’m not sure it would do better with an external heading. I’m not even sure the S3G would pick up heading from another ST1 source, I only know that it would do so when fed via its NMEA183 port.

My other concern is regarding GPS / GNSS data, as I might have two sources providing it to the N2k backbone.
Would the converter simply pass both on to ST1, or would it stick to the first one seen? If this is a problem I could certainly switch off output on the backup GPS.

[DG11] Waypoint import improvements, LH3 sw release v3.8.97

$
0
0
Hi
Can you describe the all details about the "Waypoint import improvements" made in the brand new LH3 sw release v3.8.97.

I suggest that you make a very detailed description how it works in the LH 3 handbook, especially the restrictions are undocumented in the LH manuals. I had to google quite a lot to find out that waypoint names can have maximum 16 characters, all waypoint names must be unique and that the comment field can have max 32 characters. These restriction are too restrictive. I understand that the available memory is an issue, but its better to have more quality information than 10´000 unique waypoints.

I have all my waypoints generated om my PC running OpenCPN. The text stored in the description field is not the same field used by LH3. I suggest that you make next version of LH3 more compatible with OpenCPN so the description field could be transferred between OpenCPN and LH3.

Best regards and Thanks
Stefan

ST60+ Low Depth Alarm Setting Blocked?

$
0
0
Hi There,
I have ST60+ depth, speed, wind and Graphic displays connected via ST1 (which are in turn interfaced with an A70D MFD and A ST2000+ pilot via ST1 to STng converters).
I don’t seem to be able to get access to set the low depth alarm setting on the ST60+ instrument.

Could you please advise what might be blocking my access to this setting?


Regards
Dave Davies

[CA11] c90W Trackwheel

$
0
0
While out on a sail the other day, the trackwheel on my C90W MFD fell off. It appears that it must have been somehow stuck onto the membrane that was underneath it that seals the 5 selection buttons (left, Right, Up, Down, and OK).

My questions is what should I use to glue it back into position? Is there a special glue that won't damamge the watertight integrity of the memberane but will hold the wheel in place?

[CA11] ST5000+ as secondary control?

$
0
0
I have a Raymarine 400G with the ST6000+ control head. The system is working fine but I need to add a secondary control up in the tower. I have a ST5000+ head that I bought locally. I tried a quick test by plugging it into the SeaTalk network but the 5000+ could not seem to find the rudder information. Is this unit not capable of running as a control head only or are there some settings I need to change?
Thanks
Lee

[CA11] Airmar transducer/e97 issue

$
0
0
The Airmar P319 Transducer ceased working on our Zodiac 753. We are using an e97 as master MFD and an e95 slave display.
A new transducer P319 was purchased and wired in temporarily to ensure function prior to mounting it.
We have checked all cables for continuity and tried to run diagnostics but get the following error:
"The following devices are preventing data source selection: ISO(05 6c 7a e7 00 8c 8c c0) CAN(43)"
We have the following devices connected as well:
4kW 18" HD Color Radome (SeaTalkHS)
Raymarine i70 Display (STng)
Raymarine RS-150 (STng)
Raymarine AIS650 (STng)
as well as the e95 slave MFD

The cabling from the MFD is as follows: from the rear of the e97, Airmar E66066 connected to a MM-Ray 33-624-01 (Airmar Transducer Cable # C47...CC1225 ROHS 11/17) then to the cable that is hardwired to the transducer.

We are not receiving any transducer/depth information, we have gone into the "Fishfinder" settings and selected the correct transducer but still no luyck...please help!
The software version running on the e97 is v17.46-00404
Viewing all 8621 articles
Browse latest View live