Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[CA] [CA11] a95 MFD connected to AirMar P79
01-28-19, 06:50 AM (This post was last modified: 01-28-19 07:40 PM by Chuck - Raymarine - Moderator.)
Post: #1
[CA11] a95 MFD connected to AirMar P79
In 1997, purchased the cream da la cream of Marine electronics ... still DO NOT have a Transducer giving me depth on my unit.... Reams of emails, hours on phone with three different companies, authorized technitions.

That being said... can anyone help that really knows.
Should be simple...right?
Connect a95 MFD with AirMar transducer.

Will to speak on phone with anyone, details, like pics, serial numbers, etc available on request

Thank you, Ted, sv Viator.... location Grenada
Find all posts by this user
Quote this message in a reply
01-28-19, 12:16 PM (This post was last modified: 01-28-19 12:32 PM by Chuck - Raymarine - Moderator.)
Post: #2
RE: [CA11] a95 MFD connected to AirMar P79
Welcome to the Raymarine Forum Ted,

P79 is the name given to a family of transducers produced by Airmar, each having unique characteristics. These include analog instrument variants, Smart NMEA 0183, Smart NMEA 2000, and fishfinder variants each unique to a specific manufacturer and fishfinding product. Please attach a photo of the transducer's identification tab (clearly showing all information printed on the tag) to your response.

Please note that interfacing an NMEA 0183 or NMEA 2000 Smart Depth Transducer to an a95 MFD will not support use of the LightHouse II software's fishfinder application. However, when the transducer is properly installed, the transducer has been properly interfaced, the transducer has been properly powered, and the vessel is in water having a depth of at least 3' beneath the transducer, then an operational NMEA 0183 or NMEA 2000 Smart Depth Transducer will support permitting the LightHouse II application's Depth data item to be populated when the MFD has been configured to display the Depth data item within a Databox, the Databar, or its Data application. As with all in-hull transducers, troubleshooting dashes reported for depth should commence with verifying that the transducer's reservoir is filled. Empty transducer reservoirs resulting from leakage will prevent the transducer from passing pings through hull.

As indicated within the FAQ found here, one may not simply interface a NMEA 2000 device to another NMEA 2000 device via a single cable to their respective SeaTalkng / NMEA 2000 communications interfaces. If properly interfaced to the transducer and the backbone has been properly powered, then the transducer should be listed within the Select Devices list of the Data Master MFD. Have you interfaced the P79 to the MFD via a powered and properly terminated SeaTalkng / NMEA 2000 backbone? If so, is the transducer listed within the MFD's Select Devices list? Please follow the instructions within the referenced FAQ to save this information to a microSD memory card and then attach the resulting Diagnostics...html file to your response to this post.

Should you not have interfaced the transducer via NMEA 0183 communications, then please respond with wire by wire detail regarding how you have interfaced the transducer to the MFD and how you have powered the MFD.

Should the system feature more than one source of Depth data (ex. i50 Depth, i50 Tridata, etc.) then the Data Sources feature of LightHouse II must be used to identify that your P79 should be used as the system's source of Depth data.
Find all posts by this user
Quote this message in a reply
03-06-19, 12:13 PM (This post was last modified: 03-06-19 12:23 PM by Chuck - Raymarine - Moderator.)
Post: #3
RE: [CA11] a95 MFD connected to AirMar P79
Ted,

To recap our phone conversation, the Diagnostics…html file which you had sent to me earlier today must have been created when only the a95 MFD’s circuit had been energized as it did not list any of your system’s other devices. During our phone conversation, the entire suite of electronics was energized and then instructions were provided to once again display the MFD’s Select Devices list (HOME->SET-UP->MAINTENANCE->SELECT DEVICES). Upon executing the specified command sequence, the Select Devices List not only listed the MFD, but also all three components of the Evolution autopilot (p70, ACU, & EV-1), proving that the Raymarine system was functioning properly and supporting SeaTalkng / NMEA 2000 communications. Unfortunately, the Airmar branded P79 Smart Transducer was not listed among these devices. Should the technician who had installed the Airmar branded P79 Smart Transducer onboard the vessel determined that the transducer was neither being detected by the Raymarine products nor providing depth to the system, then the installer should have interfaced a NMEA 2000 analyzer to the system (ex. Actisense NGT-1 & PC with NMEA Reader software, etc.) to the backbone. Upon doing so, the technician should have then been able to determine whether the Airmar branded P79 Smart Transducer was indeed communicating via the backbone and if so, determine what information was being transmitted by the Airmar branded P79 Smart Transducer to the backbone.

These symptoms would typically indicate a problem with one or more of the following:
- a problem with the cable assembly which is interfacing the Airmar P79 to the system’s SeaTalkng / NMEA 2000 bone
- a failure within the Unfortunately, the Airmar branded P79 Smart Transducer's SeaTalkng communications circuity
- total spur length exceeding the 6m maximum specified for SeaTalkng / NMEA 2000 spurs
- a failure of the spur socket of the T-Piece or 5-Way Connector which the Airmar branded P79 Smart Transducer has been connected to.

The only further recommendations that I may offer with regard to troubleshooting would be to:
- trace the P79's cable back to the 5-Way Connector or T-Piece that it has been connected to and to ensure that it has been connected to a spur (white) socket in one of these networking components.
- attach a label to the P79's cable, identifying that this cable is going to the P79. It would be a best installation practices to similarly label the other spur cables which have been connected the backbone's T-Pieces and 5-Way Connectors to assist in any further troubleshooting.
- ensure that the total length of the P79's cable and cable or adapter which has been connected to its cable does not cause the total combined cable length to exceed 6m.
- inspect the field installable DeviceNet plug which had been installed onto the transducer's cable. If the field installable DeviceNet plug is from Maretron, then information concerning the plug may be found here.
- verify that the spur socket into which the p79's cable is operational. This may be accomplished by unplugging the P79's cable from the spur socket within the 5-Way Connector or T-Piece that is connected to. The Spur cable from one of the system's other devices may then be unplugged from the socket within the 5-Way Connector or T-Piece to which it is presently connected and then plugged into the spur socket which hand been occupied by the p79's cable. The MFD's Select Devices list diagnostic feature would then be used to verify that the displayed list included Evolutions autopilot devices (p70, ACU, & EV-1). If so, then the spur socket previously used to connect the p79's cable would be deemed to be operational. If not, then the spur socket would be deemed to to not be operational.

Should each of the above have been verified, then it would appear that the Airmar branded P79 Smart transducer has suffered a failure of its NMEA 2000 communications circuitry and the transducer should be replaced.

The information which you had provided indicates that a field installable DeviceNet plug (presumably manufactured by Maretron) had been fitted onto the bare wire leads of the Airmar P79 Smart Transducer to then permit a SeaTalkng Spur to DeviceNet Adapter Cable to be mated to the Airmar P79 transducer’s cable assembly. The SeaTalkng to DeviceNet Spur Adapter should have then been connected to a spur socket (denoted by white locking ring) within one of the backbone’s T-Pieces or 5-Way Connectors. The easiest way to resolve the situation may be to simply replace the Airmar branded P79 transducer with the Raymarine branded P79S Smart Instrument Transducer (Raymarine Part #T70278) shown below, as our product support team is not equipped/trained to support troubleshooting third party devices beyond that which has been rendered to date.

The Raymarine branded P79S Smart Instrument Transducer (Raymarine Part #T70278) features a 6m cable with a plug (no bare wires) and simple plug to plug adapter to permit the transducer to be directly mated the backbone spur socket which the Airmar branded P79 transducer’s cable had been mated. Replacing the transducer should be a simple matter of
1) Removing the Airmar branded P79 Smart transducer from its housing
2) Verifying that the transducer reservoir has been filled to the proper level with RV antifreeze
3) Installing the Raymarine branded P79S transducer into the Airmar P79 transducer’s housing
4) Chasing the Raymarine branded P79S transducer’s cable to the backbone’s T-Piece or 5-Way Connector which the Airmar branded P79 Smart transducer had been connected
5) Installing the SeaTalkng Adapter onto the Raymarine branded P79S transducer’s cable
6) Unplugging the Airmar branded P79 Smart transducer from the backbone’s T-Piece or 5-Way Connector
7) Plugging the SeaTalkng Adapter into the available spur socket (white) within backbone’s T-Piece or 5-Way Connector
8) Securing the locking ring of the spur socket (white) into which the Raymarine branded P79S transducer’s cable has been connected.

NOTE: The total length of cable employed within the creation of a spur should not exceed 6m. In this case, should the transducer’s cable not be sufficiently long enough, then the backbone will need to be extended to close the distance gap between the transducer and the currently installed backbone. Should additional detail be required, please click here to view the FAQ addressing this subject.

Unfortunately, Raymarine, Inc. cannot sell products, including transducers, directly to the end users. Instead products must be purchased from an authorized Raymarine dealer. The good news that the street price of the Raymarine T70278 P79S Smart Instrument Transducer is much less than the $1000 which you had suggested during our phone conversation. West Marine lists the Raymarine T70278 P79S Smart Instrument Transducer for $349.99. It is recommended that this transducer be purchased or that continued support be sought through Airmar / Gemeco in troubleshooting the Airmar P79 Smart Transducer’s NMEA 2000 communications failure. Information concerning the wiring for Maretron's field installable DeviceNet plugs may be found here. If Airmar is providing another brand of field installable connector, then it is recommended that Airmar or Gemeco be contacted for information on the connector.
Find all posts by this user
Quote this message in a reply
03-06-19, 12:30 PM (This post was last modified: 03-21-19 01:30 PM by Chuck - Raymarine - Moderator.)
Post: #4
RE: [CA11] a95 MFD connected to AirMar P79
Update: The subject problem had resulted from the customer and/or independent marine electronics installer having incorrectly identified which variant of Airmar P79 transducer was being installed. Specifically, the problem had resulted from having installed the Smart NMEA 0183 variant of the P79 transducer as one would have installed the Smart NMEA 2000 variant of the P79 transducer. Initial contacts with Airmar, Inc. / Gemeco (initiated prior to contacting Raymarine) had failed to bring this information to light. Later contact with Airmar, Inc. / Gemeco identified the transducer as the Smart NMEA 0183 variant of the P79 transducer. Instructions were then provided regarding how the Smart NMEA 0183 variant of the P79 transducer may be interfaced to a switched 12VDC power circuit and to the NMEA 0183 Port 1 input leads of the a95 MFD's Power/NMEA 0183/Video Input Cable.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)