can you tell me what if a standard cat6 network cable wired to T568A will work between the POE and the CAM220 ip the run to the camera is 80ft.
thanks
Dennis
thanks
Dennis
↧
can220 ip installation
↧
Seatalk Fail / SmartPilot
Seatalk Fail Error
Equipment: Smart Pilot ST7001 & ST-50 Tri-Data
Blindly running new rubber fuel line under the floor I would have crossed over two cables.
I suspect the Fluxgate cabling would be the damaged cable as it snaked under the floor in I assume the same path as I ran the fuel line. The computer to sea talk ran pretty much parallel and not under the floor.
After running the last leg of the fuel line I received a Seatalk Fail error. Everything was in perfect running order prior to the fuel line installation so it sounds like it should be pretty simple. ((Yeah…complex electrical is not my strong suit))
Trouble shooting guides say to check cables and connections. Of course I can’t see beneath the floor so I have been checking the voltage at each end of the cables. The voltages all match from the course computer to the Controller and the Fluxgate. However, the blue FLUXGATE has no of very little voltage at the Smartpilot terminal hence the same reading at the FLUXGATE.
What should this reading be? I’m concerned that something may have shorted back to the computer?
I need to resolve this issue as I am looking to upgrade from the ST-50 to es9-Series equipment.
Equipment: Smart Pilot ST7001 & ST-50 Tri-Data
Blindly running new rubber fuel line under the floor I would have crossed over two cables.
I suspect the Fluxgate cabling would be the damaged cable as it snaked under the floor in I assume the same path as I ran the fuel line. The computer to sea talk ran pretty much parallel and not under the floor.
After running the last leg of the fuel line I received a Seatalk Fail error. Everything was in perfect running order prior to the fuel line installation so it sounds like it should be pretty simple. ((Yeah…complex electrical is not my strong suit))
Trouble shooting guides say to check cables and connections. Of course I can’t see beneath the floor so I have been checking the voltage at each end of the cables. The voltages all match from the course computer to the Controller and the Fluxgate. However, the blue FLUXGATE has no of very little voltage at the Smartpilot terminal hence the same reading at the FLUXGATE.
What should this reading be? I’m concerned that something may have shorted back to the computer?
I need to resolve this issue as I am looking to upgrade from the ST-50 to es9-Series equipment.
↧
↧
Troubleshooting a SeaTalk communications failure
SeaTalk communications failures (STLK FAIL) as reported on an autopilot's control head, ST60 Wind Instrument's LCD flashing two square boxes, or cessation of SeaTalk communications between all products, may occur as a result of any of the following:
- insufficient power due to depleted / degraded vessel batteries ... connect the vessel to shore power and fully charge the vessel's batteries. Upon completion of charging and while still connected to shore power, test communications between devices which have been interfaced to the SeaTalk bus.
- insufficient power due to line loss within SeaTalk bus ... in larger SeaTalk busses, sufficient line loss may result to reduce power below that which the SeaTalk communications circuity within the connected devices may operate. This may be overcome by installing more than one power insertion point within SeaTalk bus. Each power insertion point must be powered from the same 12 VDC power circuit and should be protected by a 3A fuse.
- insufficient power due to having joined the red lead of the SeaTalk cable interfacing a C/E-Series Classic MFD to the SeaTalk bus ... this problem is most commonly identified in systems which feature these MFDs and either use an autopilot or dedicated circuit to power the SeaTalk bus. In such systems, should the autopilot course computer or SeaTalk bus power not be switched ON when the the C/E-Series Classic MFD(s) is in the ON power state, then insufficient power will be supplied to the SeaTalk bus, resulting in SeaTalk communications failure. The problem may be eliminated by disconnecting the red lead of the SeaTalk cable which is interfacing the C/E-Series Classic MFD to the SeaTalk bus. The cable's red lead should then be insulated to prevent shorting.
- incorrectly wired SeaTalk bus ... while SeaTalk cables feature press-fit plugs or twist-locking plugs, spliced SeaTalk cables or terminals strips are commonly used to join devices to the SeaTalk bus. When joining SeaTalk Cables using splices or terminal strips, one need simply match leads of the same color (red to red, yellow to yellow, and shield to shield)
- failure of the SeaTalk communications circuitry within one or more device which has been interfaced to the SeaTalk bus.
In cases of SeaTalk communications circuitry failure, the device(s) having faulty SeaTalk communications circuitry may be identified through basic fault isolation. Accordingly, it would be recommended that the SeaTalk bus be reduced to two devices (ex. MFD and Raystar 125 GPS Sensor, autopilot course computer and autopilot control head, etc.) and upon verification that the two devices are communicating with one another, a third device would then be added to the SeaTalk bus. Should addition of the third device result in cessation of SeaTalk communications, then that device would be removed from the SeaTalk bus and the device would either be replaced or sent to Raymarine’s Product Repair Center to be bench checked / serviced. Should addition of the third device not result in cessation of SeaTalk communications, then additional devices will be added one by one to the SeaTalk bus and communications verified until SeaTalk communications with each device has been verified. Similarly, should the addition of any device(s) result in cessation of SeaTalk communications, then that device(s) will be removed from the SeaTalk bus and either replaced or sent to Raymarine’s Product Repair Center to be bench checked / serviced.
CRAFAQ#
- insufficient power due to depleted / degraded vessel batteries ... connect the vessel to shore power and fully charge the vessel's batteries. Upon completion of charging and while still connected to shore power, test communications between devices which have been interfaced to the SeaTalk bus.
- insufficient power due to line loss within SeaTalk bus ... in larger SeaTalk busses, sufficient line loss may result to reduce power below that which the SeaTalk communications circuity within the connected devices may operate. This may be overcome by installing more than one power insertion point within SeaTalk bus. Each power insertion point must be powered from the same 12 VDC power circuit and should be protected by a 3A fuse.
- insufficient power due to having joined the red lead of the SeaTalk cable interfacing a C/E-Series Classic MFD to the SeaTalk bus ... this problem is most commonly identified in systems which feature these MFDs and either use an autopilot or dedicated circuit to power the SeaTalk bus. In such systems, should the autopilot course computer or SeaTalk bus power not be switched ON when the the C/E-Series Classic MFD(s) is in the ON power state, then insufficient power will be supplied to the SeaTalk bus, resulting in SeaTalk communications failure. The problem may be eliminated by disconnecting the red lead of the SeaTalk cable which is interfacing the C/E-Series Classic MFD to the SeaTalk bus. The cable's red lead should then be insulated to prevent shorting.
- incorrectly wired SeaTalk bus ... while SeaTalk cables feature press-fit plugs or twist-locking plugs, spliced SeaTalk cables or terminals strips are commonly used to join devices to the SeaTalk bus. When joining SeaTalk Cables using splices or terminal strips, one need simply match leads of the same color (red to red, yellow to yellow, and shield to shield)
- failure of the SeaTalk communications circuitry within one or more device which has been interfaced to the SeaTalk bus.
In cases of SeaTalk communications circuitry failure, the device(s) having faulty SeaTalk communications circuitry may be identified through basic fault isolation. Accordingly, it would be recommended that the SeaTalk bus be reduced to two devices (ex. MFD and Raystar 125 GPS Sensor, autopilot course computer and autopilot control head, etc.) and upon verification that the two devices are communicating with one another, a third device would then be added to the SeaTalk bus. Should addition of the third device result in cessation of SeaTalk communications, then that device would be removed from the SeaTalk bus and the device would either be replaced or sent to Raymarine’s Product Repair Center to be bench checked / serviced. Should addition of the third device not result in cessation of SeaTalk communications, then additional devices will be added one by one to the SeaTalk bus and communications verified until SeaTalk communications with each device has been verified. Similarly, should the addition of any device(s) result in cessation of SeaTalk communications, then that device(s) will be removed from the SeaTalk bus and either replaced or sent to Raymarine’s Product Repair Center to be bench checked / serviced.
CRAFAQ#
↧
WI FI chirp Sonar
Hello,
just got my Wi Fi chirp down vision sonar setup and just installed it, my question is where is the noise suppressor that came with it suppose to be installed at? I don't even see it list on the list of contents.
just got my Wi Fi chirp down vision sonar setup and just installed it, my question is where is the noise suppressor that came with it suppose to be installed at? I don't even see it list on the list of contents.
↧
Product Selection Advice needed...
From Ray marines list...
- a list of the marine electronics products which are presently installed onboard the boat:
E120 (older generation)
Furuno Radar 1835
SIMRAD AP 28 Autopilot
I also have a RM A98 MFD that is NOT installed
- a list of the features/capabilities that you are seeking to add
I like the touchscreen and functionality of the A98 as well as the downchirp sounder so I would like to use that as a main unit...
- type of usage (serious fishing, cruising, offshore sailing, bay sailing, racing, etc.)
Fishing/Cruising.
- type vessel (displacement powerboat, planing powerboat, sailboat, etc.)
32 Blackfin Flybridge
- any physical constraints (ex. size of the display, desire for in-hull transducer, etc.)
None
- type of steering (cable, hydraulic, chain & sprocket, cable assisted hydraulic, fly by wire, tiller, etc.) ... a consideration for autopilots
Cable
- vessel length ... a consideration for depth transducers and autopilots
32
Anyways here is my situation.. I have the above installed and would like to stick with the newer generation A series stuff. If I were to install the A98 what else would I need other than a new transducer (I would like to switch to a Thru-Hull) I would need another display and probably a Radar. Any suggestions on which ones? Do I need a whole MFD (A98) or is there some type of stripped own "monitor" that would network with this to display things. How about networking, what type of extra stuff would I need to network two displays an a Radar (which I also need help chosing for this type of Vessel).
- a list of the marine electronics products which are presently installed onboard the boat:
E120 (older generation)
Furuno Radar 1835
SIMRAD AP 28 Autopilot
I also have a RM A98 MFD that is NOT installed
- a list of the features/capabilities that you are seeking to add
I like the touchscreen and functionality of the A98 as well as the downchirp sounder so I would like to use that as a main unit...
- type of usage (serious fishing, cruising, offshore sailing, bay sailing, racing, etc.)
Fishing/Cruising.
- type vessel (displacement powerboat, planing powerboat, sailboat, etc.)
32 Blackfin Flybridge
- any physical constraints (ex. size of the display, desire for in-hull transducer, etc.)
None
- type of steering (cable, hydraulic, chain & sprocket, cable assisted hydraulic, fly by wire, tiller, etc.) ... a consideration for autopilots
Cable
- vessel length ... a consideration for depth transducers and autopilots
32
Anyways here is my situation.. I have the above installed and would like to stick with the newer generation A series stuff. If I were to install the A98 what else would I need other than a new transducer (I would like to switch to a Thru-Hull) I would need another display and probably a Radar. Any suggestions on which ones? Do I need a whole MFD (A98) or is there some type of stripped own "monitor" that would network with this to display things. How about networking, what type of extra stuff would I need to network two displays an a Radar (which I also need help chosing for this type of Vessel).
↧
↧
e95 reboots when starting engine
I recently upgraded the E80 Classic MFD on my Beneteau 393 to an e95. I am now experiencing spontaneous reboots of the MFD whenever I start the diesel engine. This had never occurred with the E80 Classic. I assume it must be due to a transient voltage drop or surge that occurs when I engage the starter motor. Is this a known issue? Can you please suggest a way to diagnose/fix the problem? Thanks very much.
↧
Voyage Planner Scanning for my E127
My Voyage Planner is opened, my E127 is turned on. WiFi on both PC and E127 are turned on. yet my Voyage Planner scans, but can not find the E127, yet the E127 shows it is connected to my home Network. Any ideas?
Bill
Bill
↧
ST4000 plus w/ E80 as navigator over SeaTalk 1 bus
Hello all,
Has anybody used the E80 as the source of ST4000+ track information over the SeaTalk 1 bus. I want to allow the ST4000+ to continue to use the analog compass (which is directly connected to it) but discontinue use of the NMEA input terminals in favor of SeaTalk 1 bus. If this works, I should be able to put a Maretron SC300 fast heading sensor onto the NMEA 0183 bus for use by the E80 with the bridging function (heading) disabled.
phil
Has anybody used the E80 as the source of ST4000+ track information over the SeaTalk 1 bus. I want to allow the ST4000+ to continue to use the analog compass (which is directly connected to it) but discontinue use of the NMEA input terminals in favor of SeaTalk 1 bus. If this works, I should be able to put a Maretron SC300 fast heading sensor onto the NMEA 0183 bus for use by the E80 with the bridging function (heading) disabled.
phil
↧
Seatalk converter ST60+not on ng backbone
Installed Seatalk to Seatalk ng Converter. LED lights indicates "healthy" connection status. Depth does not repeat to a78 or P70 via ng backbone. Request MFD to find depth device and not found.
Advise, thanks, Alvin
Advise, thanks, Alvin
↧
↧
Navionics charts to E-120
I have a classic E-120 which has an older Navionics+ CF card installed. I'm going to be updating my system soon, but currently would feel more comfortable with a new Navionics card. I know there are card memory capacity issues, so what would your recommendation be?
↧
ECI-100 Question
Hello,
I was wondering is it true if I have an ECI-100 used for a motor from one boat and I buy a different boat and move the ECI-100 to the new boat that it has to be factory reset? So, the ECI-100 is so to say married to the first motor you use it on, is that correct and how can it be factory reset to allow it to be used on a different motor? Thanks.
I was wondering is it true if I have an ECI-100 used for a motor from one boat and I buy a different boat and move the ECI-100 to the new boat that it has to be factory reset? So, the ECI-100 is so to say married to the first motor you use it on, is that correct and how can it be factory reset to allow it to be used on a different motor? Thanks.
↧
Vessel icon appears to be incorrectly oriented
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.
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.
Once underway and making good way, the Chart application of MFDs operating within a system lacking a source of heading data will:
- orient the chart according to the Chart Orientation configuration setting
- offset the chart and vessel icon according to the Boat Position configuration setting
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 heading dependent features.
Should the MFD be interfaced to a source of heading data and the vessel icon incorrectly oriented and/or appear to be crabbing as the vessel is making way, then the system's heading data source would be deemed to be in need of calibration and alignment or need to be serviced/replaced. Should heading errors be detected, then the vessel's heading data source will need to be re-calibrated for deviation and then aligned to the correct heading. The owner's manual for the heading data source should be consulted for information concerning how to calibrate it for deviation and then align the compass. After doing so, then the heading should be tested against vessel's properly calibrated fluid filled compass (if so equipped) again. Should heading error continue to be detected then it is recommended that the heading data sensing device be serviced/replaced.
Before performing any calibration and alignment of a heading sensor, it is strongly recommended that the area around the heading sensor be inspected to ensure that all sources of magnetism (ex. ferrous materials, electric motors, high current carrying conductor have not been located within at least 3' of the heading sensor. The most common source of heading data onboard a vessel is an autopilot system. Other heading sources include the retired ST60+ Instrument Compass, Pathfinder Smart Heading System, and third party NMEA 0183 and NMEA 2000 GPS Compasses and magnetic heading sensors.
CRAFAQ#
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.
Once underway and making good way, the Chart application of MFDs operating within a system lacking a source of heading data will:
- orient the chart according to the Chart Orientation configuration setting
- offset the chart and vessel icon according to the Boat Position configuration setting
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 heading dependent features.
Should the MFD be interfaced to a source of heading data and the vessel icon incorrectly oriented and/or appear to be crabbing as the vessel is making way, then the system's heading data source would be deemed to be in need of calibration and alignment or need to be serviced/replaced. Should heading errors be detected, then the vessel's heading data source will need to be re-calibrated for deviation and then aligned to the correct heading. The owner's manual for the heading data source should be consulted for information concerning how to calibrate it for deviation and then align the compass. After doing so, then the heading should be tested against vessel's properly calibrated fluid filled compass (if so equipped) again. Should heading error continue to be detected then it is recommended that the heading data sensing device be serviced/replaced.
Before performing any calibration and alignment of a heading sensor, it is strongly recommended that the area around the heading sensor be inspected to ensure that all sources of magnetism (ex. ferrous materials, electric motors, high current carrying conductor have not been located within at least 3' of the heading sensor. The most common source of heading data onboard a vessel is an autopilot system. Other heading sources include the retired ST60+ Instrument Compass, Pathfinder Smart Heading System, and third party NMEA 0183 and NMEA 2000 GPS Compasses and magnetic heading sensors.
CRAFAQ#
↧
c127 "Follow From Here" Waypoint Issue
I am running a two station setup with a new c127 and a legacy C120 connected through a Seatalk to SeatalkNG converter. I use the c127 as the primary route navigation source and am running software version 17.45.
It appears that when a waypoint is used in more than one route the "Follow From Here" command is not available, even when only one route is shown on the MFD, or when the desired route is active. The only way to get to the current waypoint to start a route seems to be the "Advance Waypoint" function. That is very cumbersome because the dialog box disappears each time you advance to the next waypoint. If you have 100 waypoints in a route and are currently at waypoint 50 it's impractical to do it that way. When a waypoint is used in only one route the "Follow From Here" command is available and works properly.
Is there any way to initiate a "Follow From Here" command from a waypoint on a route when a waypoint is used in multiple routes?
Thanks in advance for any insight.
It appears that when a waypoint is used in more than one route the "Follow From Here" command is not available, even when only one route is shown on the MFD, or when the desired route is active. The only way to get to the current waypoint to start a route seems to be the "Advance Waypoint" function. That is very cumbersome because the dialog box disappears each time you advance to the next waypoint. If you have 100 waypoints in a route and are currently at waypoint 50 it's impractical to do it that way. When a waypoint is used in only one route the "Follow From Here" command is available and works properly.
Is there any way to initiate a "Follow From Here" command from a waypoint on a route when a waypoint is used in multiple routes?
Thanks in advance for any insight.
↧
↧
S100 Did I buy the wrong model?
Just bought an S100. It has the Sea Talk 3 pin plug on the base station. My current instruments are all Sea Talk ng products. Connectors are not compatable. A literature search shows a converter kit E22158 but reading the literature leaves me unsure if this will work. My S100 is E15024. My existing next gen gear is i50 E70059 depth, i50 E70058 speed, i60 E70061 analogue wind, c95 E70011 MFD, P70 E22166 autopilot controller, M81130 linear drive, E70096 EV1 evolution sensor, and E70099 ACU 200. All share the same backbone and 3 A06049 5 way connectors tie it all together. There is one blank plug on the 5 way connector that is wired to the EV1 and buss power supply and ties the other 2 A06049 connectors together so it is in the "middle" of the backbone. Wpould my S100 work if i buy the converter kit E22158 and plug it into the blank plug, then wire the S100's base station to the kit?
Regards
Rick Parish
Regards
Rick Parish
↧
Upgrading MFD
I'm considering upgrading from a Classic E-120 to either an eS97 or eS127. Rather than completely rewiring the helm, I'd like to have the option of doing the wotk in phases. Currently my RS130 is connected to the E120 via a SeaTalkng Converter. The only other connection to the E120 is from the transducer thru the DSM300 via SeaTalkHS.
The other instruments (ST60, Raypilot650, SmartPilot S3, Triducer)) are on a second basic network, with no connection to the E120. Ultimately, I'd put them (or their replacements) on the SeaTalkng network.
Could I connect the current transducer (Airmar B60-200-Ray 50/200) directly to the new MFD (via E85001), and get rid of the DSM300?
I have a feeling that this will be a bit more complicated than flush mounting the new MFD.
The other instruments (ST60, Raypilot650, SmartPilot S3, Triducer)) are on a second basic network, with no connection to the E120. Ultimately, I'd put them (or their replacements) on the SeaTalkng network.
Could I connect the current transducer (Airmar B60-200-Ray 50/200) directly to the new MFD (via E85001), and get rid of the DSM300?
I have a feeling that this will be a bit more complicated than flush mounting the new MFD.
↧
Suncover slipping down the display
Does anyone have any hints as to how to prevent this? After about four to six hours, in a variety of temperatures, the cover slips down the display so that the display is no longer protected from the sun.
↧
connect external gps source to SeatalkNG
I have the bare wire ends sea talk cable plugged into my SeatalkNG system. Can I hook the GPS NMEA outputs from my vhf into this system so the autopilot can steer to a waypoint?
which of the bare wires should be connected?
which of the bare wires should be connected?
↧
↧
Hardover time
I have installed an ST4000 wheel pilot w ACU100 and sea talk NG Backbone. How do I determine the hardover time setting? The manual suggests setting this, but gives no instruction for how to do it.
↧
How do I determine hard over to hard over time?
Hard over to hard over time may be determined by the following procedure:
1) disconnect the motor leads from the autopilot course computer
2) momentarily connect the motors leads to +12 VDC and ground while noting:
..... a)the direction of rudder/tiller movement and
..... b) which leads had been connected to +12 VDC and ground respectively
3) manually turn the wheel or move the tiller to the full extent of its movement in the direction which it had been caused to move in step 2
4) reverse the motor leads with respect their prior connections to ground and +12 VDC and then count the number of seconds required for the drive to move the rudder/tiller to hard over in the opposite direction that it had moved in step 2
CRAFAQ#
1) disconnect the motor leads from the autopilot course computer
2) momentarily connect the motors leads to +12 VDC and ground while noting:
..... a)the direction of rudder/tiller movement and
..... b) which leads had been connected to +12 VDC and ground respectively
3) manually turn the wheel or move the tiller to the full extent of its movement in the direction which it had been caused to move in step 2
4) reverse the motor leads with respect their prior connections to ground and +12 VDC and then count the number of seconds required for the drive to move the rudder/tiller to hard over in the opposite direction that it had moved in step 2
CRAFAQ#
↧
ST60+ Tridata VMG
I have a Raymarine ST60+ Tridata instrument which will display VMG information for a few seconds and then it reverts back to the current speed display function. Is there a way to have the VMG display that information continuously?
↧