My tridata depth display only shows horizontal bars. I've checked the wiring connection and see a white wire and 2 black wires. Not sure if they are connected properly or the corresponding male connection.
↧
Tridata depth display not working
↧
Selected Sounder Unavailable
I have an ES97 MFD. It's less than a year old. I took the boat out yesterday and it seemed to take longer than usual to start. When it did, the sounder was not working. The whole time I was out it kept trying to turn the sonar on and then displaying the message "Selected Sounder Unavailable". I went back to the boat this morning and tried resetting the sounder and resetting the system. Same issue "Selected Sounder Unavailable". When you go to the channel setting there is no choice shown for which sounder to select. So I thought since I still have the C97 this unit replaced, and the connections are the same, I would try plugging that in to see if there was an issue with the transducer. I did and the sonar worked fine - no issue.
I think I need to send my ES97in for repair but I wanted to check and make sure there is nothing else I could try before I do. I was planning on upgrading the sounder to the CP370 but would still want the internal one in the ES to function. I also noticed the unit was very warm when I was checking the wiring - not sure if that is normal or not.
I think I need to send my ES97in for repair but I wanted to check and make sure there is nothing else I could try before I do. I was planning on upgrading the sounder to the CP370 but would still want the internal one in the ES to function. I also noticed the unit was very warm when I was checking the wiring - not sure if that is normal or not.
↧
↧
Selected Sounder Unavailable
I am attaching the log file for the issue I revealed in my prior post. I have lots of these. All pretty much the same....
![.log]()
SONAR_1350.log (Size: 136.6 KB / Downloads: 0)
SONAR_1350.log (Size: 136.6 KB / Downloads: 0)
↧
E80 and E120 conflict
Hello
I have two display on my sailboat E80 and E120, and autopilot ST7002
Depth, speed and wind gages ST60+
Maine problem both display want to be a master, I can't choose one master and second is master OFF. They not allowed me to do it. When I placed CF-card to E120 I lost my WIND gage, after I placed it back to E80, wing gage is returning back , but only for one day and now out again. What to do for solving this problem ? Where is to start ? I readed manual, reset to factory setting both chartplotters, doen't help me. Thanks in advance.
I have two display on my sailboat E80 and E120, and autopilot ST7002
Depth, speed and wind gages ST60+
Maine problem both display want to be a master, I can't choose one master and second is master OFF. They not allowed me to do it. When I placed CF-card to E120 I lost my WIND gage, after I placed it back to E80, wing gage is returning back , but only for one day and now out again. What to do for solving this problem ? Where is to start ? I readed manual, reset to factory setting both chartplotters, doen't help me. Thanks in advance.
↧
Control head compatibility
I currently have an Autohelm Type 100 autopilot controlled by a ST6000+ control head. Works great. I would like to upgrade the control head to a Raymarine p70R if the system/unit is compatible. Q1: Is it compatible? Q2: if it's compatible, can it interface with my Garmin 1242 xsv plotter over the Garmin NMEA 2000 network? Need any adapters?
Thanks for your help.
Thanks for your help.
↧
↧
Garmin's acquisition of Navionics and its implications for Raymarine customers
Garmin's acquisition of Navionics and its implications for Raymarine customers
The fact is that Garmin's acquisition is expected to have a very limited, if any, impact at all to Raymarine and its customers.
• Garmin has clearly stated within their press release that they intend to have Navionics run as an independent company within Garmin.
• Raymarine been in contact with Navionics at various management levels and they all reiterated the point above.
• There is a precedence with FUSION Entertainment Ltd. You may recall that Garmin acquired FUSION three years ago. FUSION, to date, has been run completely independently from the rest of Garmin and kept its brand. They continue to invest with Raymarine to have their products be compatible with Raymarine products.
• Raymarine will continue to offer Navionics cartography within the the same products.
RAYFAQ#
The fact is that Garmin's acquisition is expected to have a very limited, if any, impact at all to Raymarine and its customers.
• Garmin has clearly stated within their press release that they intend to have Navionics run as an independent company within Garmin.
• Raymarine been in contact with Navionics at various management levels and they all reiterated the point above.
• There is a precedence with FUSION Entertainment Ltd. You may recall that Garmin acquired FUSION three years ago. FUSION, to date, has been run completely independently from the rest of Garmin and kept its brand. They continue to invest with Raymarine to have their products be compatible with Raymarine products.
• Raymarine will continue to offer Navionics cartography within the the same products.
RAYFAQ#
↧
mast connection
Would you have an suggestions on a quality method to have a raynet to raynet radar connection at the base of a deck stepped mast.
If one was to use a Radar cable with the 12 volt power connectors as the first cable do the extension cables need to be radar cables or can one use any raynet cable?
I am looking for a weather proof connection at the deck of my sailboat.
David
If one was to use a Radar cable with the 12 volt power connectors as the first cable do the extension cables need to be radar cables or can one use any raynet cable?
I am looking for a weather proof connection at the deck of my sailboat.
David
↧
Getting boat heading data with Axion unit
My Axion 9 is my only boat electronic device.
It does not show any heading data. Obviously, this makes it harder to navigate using the Axiom electronics. My old old Raymarine Fishfinder/GPS provided heading.
No options are found/offered under the Settings/Network/Data Sources menu.
The Axiom 9 unit is the source for "depth" and "GPS."
Can't the Axion internal GPS be used as a heading source?
Do I have to buy another device just to be able to use my Axiom to have heading data to navigate to a waypoint?
It does not show any heading data. Obviously, this makes it harder to navigate using the Axiom electronics. My old old Raymarine Fishfinder/GPS provided heading.
No options are found/offered under the Settings/Network/Data Sources menu.
The Axiom 9 unit is the source for "depth" and "GPS."
Can't the Axion internal GPS be used as a heading source?
Do I have to buy another device just to be able to use my Axiom to have heading data to navigate to a waypoint?
↧
Instruction Manual
I received and installed my Quantum Radome which is presented on my Raymarine E7 chartplotter. I've never had radar before and I can't find an instruction manual showing how to operate the system. Please help.
Thanks,
JM
Thanks,
JM
↧
↧
Ray 70 VHF can’t listen weather forecast
Hi
I bought a Ray 70 vhf with ais ( west marine -Fort Lauderdale )
When I put it to »Weather mode » I access to the weather ten (10) channels.
Here in Fort Lauderdale the continuous weather forecast is on th Chanel 1 ( 162 550 ) My problem is when I’m on the channel 1 on the Weather mode I can’ listen to it.
I’d like to know how to listen to it. It’s first time in my life I can’t get the weather forecast with a vhf. Help would be appreciated.
Thank you.
I bought a Ray 70 vhf with ais ( west marine -Fort Lauderdale )
When I put it to »Weather mode » I access to the weather ten (10) channels.
Here in Fort Lauderdale the continuous weather forecast is on th Chanel 1 ( 162 550 ) My problem is when I’m on the channel 1 on the Weather mode I can’ listen to it.
I’d like to know how to listen to it. It’s first time in my life I can’t get the weather forecast with a vhf. Help would be appreciated.
Thank you.
↧
Axiom / Axiom Pro MFD cannot be configured to Head Up chart orientation
Axiom / Axiom Pro MFD cannot be configured to Head Up chart orientation
Two of the most commonly confused navigational terms are heading and course over ground (COG). Heading is the angular designation of the orientation of the vessel with respect to true or magnetic north ... in short, it is the direction in which the vessel is pointed. COG is the angular designation give to the direction in which the vessel is moving over the earth with respect to magnetic to true north. As indicated within this definition of COG, the vessel must be in motion to express the direction of its movement. Depending upon the vessel's speed and leeway (resultant of current and wind vectors), heading and COG may be very close or very different in value. Generally speaking, heading and COG will be closer in value as the speed of the vessel increases, thereby reducing the effects of leeway. Correspondingly, slower moving vessels will be more affected by leeway and as such slower moving vessels will typically display greater differences in the values reported for heading and COG.
Raymarine MFDs are not designed with an internal heading sensor. One may determine whether the Raymarine system has been interfaced to a source of heading data by configuring the MFD to display the "Heading" data item within the MFD's Databar, a Databox, or within one of the Data application's Data Panels. Should the reported value of "Heading" data item be ---, then one may assume that the Raymarine system has not been interfaced to a source of heading data.
GPS sensing devices are typically designed to function as source of heading data unless the product has been specifically designed, manufactured, and marketed as a GPS compass or has combined multiple sensors within a single device (ex. Airmar 220WX Weatherstation, Airmar GH2183, etc.). Accordingly, most GPS sensing devices are instead most commonly a source of COG data rather than heading data. Using the definition above, a stationary vessel (ex. one which is tied to a dock, mooring, etc.) has no COG. Additionally, when maneuvering or operating at very slow speeds, COG can be somewhat inaccurate due to update rates.
In systems lacking a source of heading data (ex. autopilot, instrument compass, GPS compass, etc.) where the vessel is stationary or operating below a speed that an accurate COG can be determined, the Chart application of an Axiom / Axiom Pro MFD operating with the latest available Raymarine product software updates will
- replace the vessel icon with a black dot, providing a visual cue that the system has no heading data or accurate COG to correctly orient a vessel icon.
- position the black dot (indicating the vessel's position) at the center of the Chart application's display
- orient the chart to North Up ... however, the orientation specified within the chart orientation listed within the titlebar will specify "(Head-Up)"
- changes to the Chart Orientation configuration setting (MENU->SETTINGS->VIEW & MOTION->CHART ORIENTATION) will be accepted, however the displayed chart will remain oriented North Up ... however, the orientation specified within the chart orientation listed within the titlebar will specify the selected chart orientation
- changes to the Boat Position configuration setting (MENU->PRESENTATION->VIEW & MOTION->BOAT POSITION) will be accepted, however, the black dot will continue to positioned within the middle of the displayed chart.
Once underway and making good way, the Chart application of the Axiom / Axiom Pro MFDs operating within a system not including a source of heading data will
- replace the black dot with a vessel icon oriented in the direction of COG
- orient the chart according to the Chart Orientation configuration setting
- offset the chart and vessel icon according to the Boat Position configuration setting
- the chart orientation specified within the Chart application will persist should the MFD be switched OFF and then switched ON.
Head-Up vs Course-UP Chart orientation ... Like the confusion over Heading and COG, many operators of systems lacking a Heading data source erroneously assume that the Chart application should be configured to Course-Up orientation rather than Head-Up orientation when seeking to have the system orient the chart in the direction in which the vessel is moving. Head-Up chart orientation is most commonly used by those operating in pilotage waters and/or to have all items displayed within the Chart application to be displayed relative to the vessel's head. In contrast Course-Up is associated with the the Chart application's navigation features (i.e. Go To Cursor/Waypoint and Follow Route). Should the system be commanded into navigation mode through execution of one of the aforementioned commands and should the Chart application then be commanded into Course-Up, then the displayed chart will be oriented to match that of the navigational course line to the waypoint/cursor position, which may or may not be the direction in which the vessel is moving over ground (COG) or pointed (heading).
It is not necessary to interface a heading data source to the system unless it is desired to have the vessel icon be properly oriented when the vessel is stationary or operating at maneuvering speeds or should one desire to utilize one of the system's heading dependent or heading enhanced features. Raymarine recommends that accurate 10Hz or greater heading data be supplied to any system using using any of (but not limited to) the following Radar and Chart application features:
- MARPA
- AIS Targets Displayed within the Radar Application
- Waypoints Displayed within the Radar Application
- North Up or Course Up orientation within the Radar Application
- Radar Overlay within the Chart Application .. may be used with COG alone.
- Heading Vector within the Chart Application
- Vessel Icon Orientation within the Chart Application (will default to COG when no heading data source is detected)
- Heading Databar and Data application data items
- Other features dependent on accurate, stable heading data.
It is generally recommended that Axiom / Axiom Pro MFDs consider installation of a Raymarine Evolution EV-1 CCU (Evolution Heading Sensor / Roll & Pitch Sensor / Rate of Turn Sensor / Course Computer) should it be desired to interface the MFD to a source of heading data. Not only is the EV-1 CCU designed to provide accurate and stable heading to the system, but may also form the basis of a future Evolution autopilot system. You will also find that the price of an EV-1 CCU is similar to that of other devices which simply sense heading.
RAYFAQ#
Two of the most commonly confused navigational terms are heading and course over ground (COG). Heading is the angular designation of the orientation of the vessel with respect to true or magnetic north ... in short, it is the direction in which the vessel is pointed. COG is the angular designation give to the direction in which the vessel is moving over the earth with respect to magnetic to true north. As indicated within this definition of COG, the vessel must be in motion to express the direction of its movement. Depending upon the vessel's speed and leeway (resultant of current and wind vectors), heading and COG may be very close or very different in value. Generally speaking, heading and COG will be closer in value as the speed of the vessel increases, thereby reducing the effects of leeway. Correspondingly, slower moving vessels will be more affected by leeway and as such slower moving vessels will typically display greater differences in the values reported for heading and COG.
Raymarine MFDs are not designed with an internal heading sensor. One may determine whether the Raymarine system has been interfaced to a source of heading data by configuring the MFD to display the "Heading" data item within the MFD's Databar, a Databox, or within one of the Data application's Data Panels. Should the reported value of "Heading" data item be ---, then one may assume that the Raymarine system has not been interfaced to a source of heading data.
GPS sensing devices are typically designed to function as source of heading data unless the product has been specifically designed, manufactured, and marketed as a GPS compass or has combined multiple sensors within a single device (ex. Airmar 220WX Weatherstation, Airmar GH2183, etc.). Accordingly, most GPS sensing devices are instead most commonly a source of COG data rather than heading data. Using the definition above, a stationary vessel (ex. one which is tied to a dock, mooring, etc.) has no COG. Additionally, when maneuvering or operating at very slow speeds, COG can be somewhat inaccurate due to update rates.
In systems lacking a source of heading data (ex. autopilot, instrument compass, GPS compass, etc.) where the vessel is stationary or operating below a speed that an accurate COG can be determined, the Chart application of an Axiom / Axiom Pro MFD operating with the latest available Raymarine product software updates will
- replace the vessel icon with a black dot, providing a visual cue that the system has no heading data or accurate COG to correctly orient a vessel icon.
- position the black dot (indicating the vessel's position) at the center of the Chart application's display
- orient the chart to North Up ... however, the orientation specified within the chart orientation listed within the titlebar will specify "(Head-Up)"
- changes to the Chart Orientation configuration setting (MENU->SETTINGS->VIEW & MOTION->CHART ORIENTATION) will be accepted, however the displayed chart will remain oriented North Up ... however, the orientation specified within the chart orientation listed within the titlebar will specify the selected chart orientation
- changes to the Boat Position configuration setting (MENU->PRESENTATION->VIEW & MOTION->BOAT POSITION) will be accepted, however, the black dot will continue to positioned within the middle of the displayed chart.
Once underway and making good way, the Chart application of the Axiom / Axiom Pro MFDs operating within a system not including a source of heading data will
- replace the black dot with a vessel icon oriented in the direction of COG
- orient the chart according to the Chart Orientation configuration setting
- offset the chart and vessel icon according to the Boat Position configuration setting
- the chart orientation specified within the Chart application will persist should the MFD be switched OFF and then switched ON.
Head-Up vs Course-UP Chart orientation ... Like the confusion over Heading and COG, many operators of systems lacking a Heading data source erroneously assume that the Chart application should be configured to Course-Up orientation rather than Head-Up orientation when seeking to have the system orient the chart in the direction in which the vessel is moving. Head-Up chart orientation is most commonly used by those operating in pilotage waters and/or to have all items displayed within the Chart application to be displayed relative to the vessel's head. In contrast Course-Up is associated with the the Chart application's navigation features (i.e. Go To Cursor/Waypoint and Follow Route). Should the system be commanded into navigation mode through execution of one of the aforementioned commands and should the Chart application then be commanded into Course-Up, then the displayed chart will be oriented to match that of the navigational course line to the waypoint/cursor position, which may or may not be the direction in which the vessel is moving over ground (COG) or pointed (heading).
It is not necessary to interface a heading data source to the system unless it is desired to have the vessel icon be properly oriented when the vessel is stationary or operating at maneuvering speeds or should one desire to utilize one of the system's heading dependent or heading enhanced features. Raymarine recommends that accurate 10Hz or greater heading data be supplied to any system using using any of (but not limited to) the following Radar and Chart application features:
- MARPA
- AIS Targets Displayed within the Radar Application
- Waypoints Displayed within the Radar Application
- North Up or Course Up orientation within the Radar Application
- Radar Overlay within the Chart Application .. may be used with COG alone.
- Heading Vector within the Chart Application
- Vessel Icon Orientation within the Chart Application (will default to COG when no heading data source is detected)
- Heading Databar and Data application data items
- Other features dependent on accurate, stable heading data.
It is generally recommended that Axiom / Axiom Pro MFDs consider installation of a Raymarine Evolution EV-1 CCU (Evolution Heading Sensor / Roll & Pitch Sensor / Rate of Turn Sensor / Course Computer) should it be desired to interface the MFD to a source of heading data. Not only is the EV-1 CCU designed to provide accurate and stable heading to the system, but may also form the basis of a future Evolution autopilot system. You will also find that the price of an EV-1 CCU is similar to that of other devices which simply sense heading.
RAYFAQ#
↧
i50 Tridata erratic speed readings
i50 Tridata with depth, speed (ST800-P120) and wind transducers connected installed below deck at nav station. Individual wind, depth, speed displays networked and set as repeaters in cockpit. Depth and wind functioning properly. Repeaters functioning properly.
Speed readings are erratic. Motoring at 4-5 knots the speed reading will jump to 8 knots then back to 4, then jump to 14 knots then back to 4. At times, sitting dockside it has read 1-1.5 knots with no current present at slack tide.
Done to date: At suggestion of Raymarine tech support have done multiple speed calibration runs over a measured nautical mile to no avail. Also as suggested by support checked the transducer paddle wheel with a compass to ensure correct polarity of magnets. Have done a dockside calibration for speed offset. Have replaced display. Have replaced transducer. All to no avail as the unit still has erratic readings.
This is installed on a very basic Island Packet 32. The only 110v systems on the boat are a water heater, battery charger and outlets. While motoring no 110v is present. While motoring the only current present is the alternator charging batteries. When reading speed at dockside there is no shore power present, no charging going on. The wiring and transducer runs are following the previous installation of instruments (autohelm) that were in use for at least 15 ish years with no such problems. When replacing the transducer I even installed it into the thru hull fitting and ran the transducer wire directly to the tridata from the bilge, through the cabin bypassing any and all existing wire runs with no difference. I ran it to the speed display in the cockpit and made it the master with no difference.
At this point I have no idea what to check or do to resolve this. From raymarine what I am getting is send everything back to them for service. I have a hard time believing two sets of displays and transducers are at fault. I'm not past thinking I have somehow missed something that is causing this but feel fairly certain the integrity of the install is pretty good.
Little help?
Speed readings are erratic. Motoring at 4-5 knots the speed reading will jump to 8 knots then back to 4, then jump to 14 knots then back to 4. At times, sitting dockside it has read 1-1.5 knots with no current present at slack tide.
Done to date: At suggestion of Raymarine tech support have done multiple speed calibration runs over a measured nautical mile to no avail. Also as suggested by support checked the transducer paddle wheel with a compass to ensure correct polarity of magnets. Have done a dockside calibration for speed offset. Have replaced display. Have replaced transducer. All to no avail as the unit still has erratic readings.
This is installed on a very basic Island Packet 32. The only 110v systems on the boat are a water heater, battery charger and outlets. While motoring no 110v is present. While motoring the only current present is the alternator charging batteries. When reading speed at dockside there is no shore power present, no charging going on. The wiring and transducer runs are following the previous installation of instruments (autohelm) that were in use for at least 15 ish years with no such problems. When replacing the transducer I even installed it into the thru hull fitting and ran the transducer wire directly to the tridata from the bilge, through the cabin bypassing any and all existing wire runs with no difference. I ran it to the speed display in the cockpit and made it the master with no difference.
At this point I have no idea what to check or do to resolve this. From raymarine what I am getting is send everything back to them for service. I have a hard time believing two sets of displays and transducers are at fault. I'm not past thinking I have somehow missed something that is causing this but feel fairly certain the integrity of the install is pretty good.
Little help?
↧
I60 cabling
With an I60 wind it can be wired directly to the wind vane or the wind vane connected to a wind pod or a ICT-5 and the data feed via STNG.
My question: if the wind vane transducer is hard wired to the I60 ( analogue ) and the I60 is connected via STng to a network, will all of the data flow to network from the I60 be the same as if the transducer was connected to the network via a wind pod or a ICT-5?
Is there a preferred method, given that I am replacing a St60 wind and the wiring is place from the vane. I wish to maximize the features available both to and from the I60.
Thanks
David
My question: if the wind vane transducer is hard wired to the I60 ( analogue ) and the I60 is connected via STng to a network, will all of the data flow to network from the I60 be the same as if the transducer was connected to the network via a wind pod or a ICT-5?
Is there a preferred method, given that I am replacing a St60 wind and the wiring is place from the vane. I wish to maximize the features available both to and from the I60.
Thanks
David
↧
↧
Ray50 - Ray52
Hello Chuck
I am in the market for a new vhf and trying to decide on one or the other.
Currently my system consists a78 and ev-200 and p70r.
My thoughts would be the 50 as I could use the a78 for gps data.
Not sure what the benefits would be in purchasing the 52 except if I was going to use as stand alone. Please correct me if I am wrong
Thanks for your help once again
Jeff
I am in the market for a new vhf and trying to decide on one or the other.
Currently my system consists a78 and ev-200 and p70r.
My thoughts would be the 50 as I could use the a78 for gps data.
Not sure what the benefits would be in purchasing the 52 except if I was going to use as stand alone. Please correct me if I am wrong
Thanks for your help once again
Jeff
↧
New autopilotEV400 SAIL to existing system
Hi
I am looking for a new autopilot ... the raymarine evolution 400 seems about right for our 48’sailing ketch with a weight of 18 tonnes.
Presently I have a raymarine C120 chart plotter and raymarine wind and transducers of the same generation as the chart plotter.
Will the c120 will interface with the evolution autopilot Through seatalk 1 to seatalkNG?
The wind / deapth Instruments 60+ would probably need an ITC-5 in order to communicate with the new ev400 autopilot?
The existing installation of wind + depth stlll work fine and I don’t want to replace them ...
I could imagine adding a new i70 at the helm to display AIS from my C120
Could you please suggest the components needed to complete the system.
I am looking for a new autopilot ... the raymarine evolution 400 seems about right for our 48’sailing ketch with a weight of 18 tonnes.
Presently I have a raymarine C120 chart plotter and raymarine wind and transducers of the same generation as the chart plotter.
Will the c120 will interface with the evolution autopilot Through seatalk 1 to seatalkNG?
The wind / deapth Instruments 60+ would probably need an ITC-5 in order to communicate with the new ev400 autopilot?
The existing installation of wind + depth stlll work fine and I don’t want to replace them ...
I could imagine adding a new i70 at the helm to display AIS from my C120
Could you please suggest the components needed to complete the system.
↧
E-120 chart plotter question
I have an E-120 and was wondering if anyone knew the setting to display a line from the bow of the boat to show the heading out to the edge of the display so I can see where I will go 10 miles away.
Thanks
Thanks
↧
Upgrading ST40 to i50/i60 system
I am planning on upgrading my existing RayMarine ST40 Depth and Speed instruments with a Raymarine i50 / i60 Depth, Speed and Wind Systems Pack. My hope is that I can use the existing wiring and the transducers for speed and depth (as there is nothing wrong with them) and only run the mast wire for the wind.
Does anyone know if that will work, or will I have to do a complete rewire?
Does anyone know if that will work, or will I have to do a complete rewire?
↧
↧
AIS 350 install
I have a Ray218 VHF radio connect to my MFD via NEMA 0183. I would like to add an AIS350 to receive position data. If I connect the Nema 0183 wires on the AIS350 to the RAY218's Nema 0183 wires will that suffice for the network connection? What about the Antenna? How can these devices share the VHF antenna? Right now its plugged into the RAY218. There is a diagram in the manual that shows the antenna connected into the AIS350 but not to the VHF which seems to imply the VHF can share through the AIS350's Nema connection.
↧
A65 & EV100 Power Installation ???
Hi, I have an A65 GPS/FF combo, old but love it! On the way is EV100 Autopilot w power hyd pump...going on 23' V8 power boat (ocean going).
1. Do I need to?
2. Should I ?
3. Can I ?
Connect the Autopilot to the A65 ???
Why or why not to connect it ? And how to do it?
Also, the only Port open on the back of the A65 is the "AUX" port....the others have the Power, GPS, Sonar and nmea/VHF attached to them.
thx in advance
Justin
![.jpg]()
20160606_164213.jpg (Size: 115.9 KB / Downloads: 1)
1. Do I need to?
2. Should I ?
3. Can I ?
Connect the Autopilot to the A65 ???
Why or why not to connect it ? And how to do it?
Also, the only Port open on the back of the A65 is the "AUX" port....the others have the Power, GPS, Sonar and nmea/VHF attached to them.
thx in advance
Justin
20160606_164213.jpg (Size: 115.9 KB / Downloads: 1)
↧
CP370 Data Drops with Axiom 12
I have a dual HS and Raynet bus system connecting basic Axiom 12 with no sonar to CP370 and P70 autopilot display and control(I have full new autopilot as well on Raynet). My CP370 is interfaced to the Axiom via an 8 channel HS switch and is combined with Quantum Radar (also not working- but another topic) and 3 CAM 220 IP cameras.
When I boot the Axiom 12 (3.2.97) and my CP370 (software is 1 rev back) I see depth displayed on the P70. However when I choose the Chart App I lose depth on the chart and the P70. I can only see depth if I display a chart app and the fishfinder app. If I turn off the fishfinder app and choose any other set of apps no depth is available.
There are no other busses attached to the system.
I also have a Quantum radar that I cannot update software along with the CP370 because Axiom does not support HS software upgrade path. As a result my Quantum radar is non-functional because I cannot apply the update to solve the test bench issue.
VERY frustrating. What can be done about my depth problem and is there any guess about when we might see HS update support?
When I boot the Axiom 12 (3.2.97) and my CP370 (software is 1 rev back) I see depth displayed on the P70. However when I choose the Chart App I lose depth on the chart and the P70. I can only see depth if I display a chart app and the fishfinder app. If I turn off the fishfinder app and choose any other set of apps no depth is available.
There are no other busses attached to the system.
I also have a Quantum radar that I cannot update software along with the CP370 because Axiom does not support HS software upgrade path. As a result my Quantum radar is non-functional because I cannot apply the update to solve the test bench issue.
VERY frustrating. What can be done about my depth problem and is there any guess about when we might see HS update support?
↧