Older Auto pilot and Axiom

No, the EV1 is in my center bilge about midship under the sole...same place the old fluxgate compass resided. Engine room is a BAD BAD place for a magnetic compass!!!

EV-1 location in a 410 Sundancer...you can see the old fluxgate compass...haven't pulled it yet

20201201_162836.jpg
20201201_162857.jpg
20201201_162903.jpg
 
My fluxgate compass is under the inner bunk against the inner stateroom wall in the second stateroom. Not quite on centerline but attached "sideways" not facing forward. Would the EV-1 be fine there or should I relocate it more on centerline?
 
My fluxgate compass is under the inner bunk against the inner stateroom wall in the second stateroom. Not quite on centerline but attached "sideways" not facing forward. Would the EV-1 be fine there or should I relocate it more on centerline?

the only requirement is that it has to be aligned with the centerline of the boat. The mount can be fore-aft of side to side as long as the arrow points forward.

I think that would work at least from distance from things that would interfere with the compass.
 
I believe when I set it up I checked for updates but will confirm when I'm at the boat again.
Turns out it was the “community edits” option that was slowing down the rendering. Disabled and it’s much faster now.
 
Turns out it was the “community edits” option that was slowing down the rendering. Disabled and it’s much faster now.

Glad you got it solved. After spending some time with the Axiom, I like it, but there is a learning curve. Since its a touch screen a lot of things require a "touch and hold" to bring up a sub menu. For example you can change the boat icon, and vectors (where you'll be in 1 3 or 6 minutes) by touching on the boat icon to get the sub menu. For me its been pretty responsive. Learning it took some "sittin' and drinkin'.

Community edits??? Interesting. Was it trying to go online and update those in real time, or is that something that's downlowded during a map update?
 
Last edited:
Glad you got it solved. After spending some time with the Axiom, I like it, but there is a learning curve. Since its a touch screen a lot of things require a "touch and hold" to bring up a sub menu. For example you can change the boat icon, and vectors (where you'll be in 1 3 or 6 minutes) by touching on the boat icon to get the sub menu. For me its been pretty responsive. Learning it took some "sittin' and drinkin'.

Community edits??? Interesting. Was it trying to go online and update those in real time, or is that something that's downlowded during a map update?
It was downloaded during activation of the card (about a 30mb file).

The more I play around with the setup i don't really see the need to immediately update the AP. Aside form being able to engage a route from the MDF are their any other perks? Once I add the devicenet cable to connect to the seatalk converter I'll be able to follow a route from the st7000 by using the track mode. From what I understand I will have to acknowledge arrivals and next waypoints from the head unit?
 
Last edited:
It was downloaded during activation of the card (about a 30mb file).

The more I play around with the setup i don't really see the need to immediately update the AP. Aside form being able to engage a route from the MDF are their any other perks? Once I add the devicenet cable to connect to the seatalk converter I'll be able to follow a route from the st7000 by using the track mode. From what I understand I will have to acknowledge arrivals and next waypoints from the head unit?

That is the general idea, you basically have a 2 screen operation to follow a route. The Heading Hold funtion still works the same.

For me, this upgrade is about getting to a 2 touchcreen MFD setup, without all the little LCD screens all over the dash. (my screens are so old, they need repair and some are not repairable). Plus for me, I could never get the old AP to track a route without wondering all over the place.

The other thing I like is the data available on the new screen is infinitely better presented. I could not see the green LCD's and what was displayed at night.

Bottom line, if it works to your satisfaction, there really isnt a need to ever upgrade.
 
It was downloaded during activation of the card (about a 30mb file).

The more I play around with the setup i don't really see the need to immediately update the AP. Aside form being able to engage a route from the MDF are their any other perks? Once I add the devicenet cable to connect to the seatalk converter I'll be able to follow a route from the st7000 by using the track mode. From what I understand I will have to acknowledge arrivals and next waypoints from the head unit?
I'm in the same place you are. I upgrade to a VesselView 502 and Axiom+ 12 from my SmartCraft and E120 and left my ST8002 AP in place. I mostly use Auto mode but would like to use Track mode. I'm not terribly concerned about having to press "track" on the ST8002. Are you saying that a single devicenet cable to the converter (E22158) fully links the ST AP to the Axiom MFD?
 
I'm in the same place you are. I upgrade to a VesselView 502 and Axiom+ 12 from my SmartCraft and E120 and left my ST8002 AP in place. I mostly use Auto mode but would like to use Track mode. I'm not terribly concerned about having to press "track" on the ST8002. Are you saying that a single devicenet cable to the converter (E22158) fully links the ST AP to the Axiom MFD?
Yes, received and tested the cable today
 
Here what you get. This is in the manual and show some good installation diagrams, and has a list of all the parts you might need.

B806C562-B39E-4803-BF62-01A4D50EFBB8.jpeg


If you already have a properly powered and terminated SeaTalkNG network, you just add this converter. The SeaTalk network cable plugs into the squarish 3 pin connector on one of the SeaTalk instruments, and the other into the center yellow plug.

In practice, I’ve use a short (.4m) SeaTalkNG backbone cable (blue connector)to add this converter since I already had the SeaTalkNG network. Be sure to order one of those, or a longer on if you need it.

if you don’t have a SeaTalkNG network, there is a power cord that plugs into one of the spur ports, 2 backbone terminators, and is everything you need to get this up in running.
 
Here what you get. This is in the manual and show some good installation diagrams, and has a list of all the parts you might need.

View attachment 95865

If you already have a properly powered and terminated SeaTalkNG network, you just add this converter. The SeaTalk network cable plugs into the squarish 3 pin connector on one of the SeaTalk instruments, and the other into the center yellow plug.

In practice, I’ve use a short (.4m) SeaTalkNG backbone cable (blue connector)to add this converter since I already had the SeaTalkNG network. Be sure to order one of those, or a longer on if you need it.

if you don’t have a SeaTalkNG network, there is a power cord that plugs into one of the spur ports, 2 backbone terminators, and is everything you need to get this up in running.
I pulled my dash apart only to realize that I’m out of room to connect another seatalkng cable.

Just as I slowly learn marine networking, some clarification requested from the experts. My current situation is my autopilot and autopilot head are running on a seatalk1 network that is not networked to the seatalkng network at all (at least it seems that way by following the cables and given that I’m not getting waypoint data sent to the autopilot in Track mode).

I have a properly powered seatalkng network from my Axiom+ connected via the converter to radar and transducer. The guys that installed my axiom+ appear to have done the correct work to make basic navigation work but failed to incorporate the autopilot. My course computer has no empty seatalk1 slots open. So if the course computer is networked to the autopilot head via seatalk1 and the other side of that head goes seatalk1 to seatalkng via a converter, does that effectively connect everything?

Maybe another way to ask is do these ports send and receive everything everywhere or is there an order of operations? Are the two seatalk1 ports on the back of the st8002 different or are both two way and identical in function?

Am I making sense?
 
The Axiom+ connections should be pretty simple. See the drawing below. 1) Should be your RayNet connection to your Radar. 2) Is probably open. 3) Would be your SeaTalkNG network and power. 4) Is an optional ground. and 5) Is your RealVison sonar connection.

3) The SeatalkNG cable is what you should be following.

upload_2020-12-12_16-46-59.png


Your old autopilot and course computer is on a Seatalk1 network. You need to make sure that you have a E22158 Seatalk1 to SeatalkNG converter. Your Seatalk1 cable would probably have the wide flat three pin connector on one end and a round white SeaTalkNG connector on the other and be black with a white stripe. It would connect to the center yellow connector on the SeatalkNG converter.

The white connectors can be used for other SeatalkNG items. My E140W currently connects to my system through a white connector. The blue connectors on the end are used to connect to other SeatalkNG backbone items. Below is the E22158 Seatalk1 to Seatalk converter

upload_2020-12-12_17-1-21.png

So the SeatalkNG cable out of the Axiom+ (#3 above) should connect to the white connector and the remaining blue connector either goes further down the chain or is terminated with the blue plugs. Unused connectors should be covered with those plugs. Your Seatalk1 network (course computer and autopilot) should connect to the yellow connector.

Now your Axiom+ might run to other connectors and then be connected to the converter.

upload_2020-12-12_16-57-11.png


Does this make sense?
 
Last edited:
The Axiom+ connections should be pretty simple. See the drawing below. 1) Should be your RayNet connection to your Radar. 2) Is probably open. 3) Would be your SeaTalkNG network and power. 4) Is an optional ground. and 5) Is your RealVison sonar connection.

3) The SeatalkNG cable is what you should be following.

Your old autopilot and course computer is on a Seatalk1 network. You need to make sure that you have a E22158 Seatalk1 to SeatalkNG converter. Your Seatalk1 cable would probably have the wide flat three pin connector on one end and a round white SeaTalkNG connector on the other and be black with a white stripe. It would connect to the center white connector on the SeatalkNG converter.
View attachment 96196

Your old autopilot and course computer is on a Seatalk1 network. You need to make sure that you have a E22158 Seatalk1 to SeatalkNG converter. Your Seatalk1 cable would probably have the wide flat three pin connector on one end and a round white SeaTalkNG connector on the other and be black with a white stripe. It would connect to the center yellow connector on the SeatalkNG converter.

The white connectors can be used for other Seatalk1 items. My E140W currently connects to my system through a white connector. The blue connectors on the end are used to connect to other SeatalkNG items. Below is the E22158 Seatalk1 to Seatalk converter

View attachment 96198
So the SeatalkNG cable out of the Axiom+ (#3 above) should connect to the blue connector and the remaining blue connector either goes further down the chain or is terminated with the blue plugs. Unused connectors should be covered with those plugs.

View attachment 96197

Does this make sense?
Hello and thanks. I do understand all this already. I have the e22158 kit but it is not connected to my course computer. It is connected to the Axiom, VCM100 radar and Merc smarcraft system.

The S2 course computer and ST8002 appear to be completely segmented from the seatalkng network, on their own seatalk1 network along with my vhf radio (which would also explain why my vhf is not getting gps data). As the st8002 has two seatalk1 connections on it, one connected to the S2. I’m basically asking if I can connect the second seatalk1 ports on the st8002 to a seatalkng converter and effectively network the course computer to the seatalkng network. Do these protocols operate like tcp/ip in that all packets are broadcast everywhere. Or is the data in seatalk directional or do different devices carry or rebroadcast different data? I just don’t know anything about the protocol.
 
Make sure it is an E22158 and not SeatalkNG connector. Not this one but the one I showed previously with the yellow center connector. You cannot connect Seatalk1 to this version.

upload_2020-12-12_17-57-15.png


I believe those Seatalk1 ports on the ST8002 are "pass through" so you can "daisy chain" them together. It is like that on my Seatalk 1 instruments. So that should work for you.

Steve.
 
Make sure it is an E22158 and not SeatalkNG connector. Not this one but the one I showed previously with the yellow center connector. You cannot connect Seatalk1 to this version.

View attachment 96200

I believe those Seatalk1 ports on the ST8002 are "pass through" so you can "daisy chain" them together. It is like that on my Seatalk 1 instruments. So that should work for you.

Steve.
Got it on the difference between the converter block and the 5-way STng block. Thanks. Since my current converter block is out of space, I have a second converter block. So I can bring the ST->STng cable from the second port on the ST8002 to the new block. I'm assuming that putting a spur/power cable (the blue/black ones) between the two converter blocks will network the two.

I'll give it a try tomorrow. I didn't have a spur cable handy so picked one up on my way home from the boat today. If I can get waypoint data to the autopilot from the Axiom, I can be done with the helm for a bit.
 
Here is what mine looks like. It was installed when I got the boat. The top blue one link the two together. The black and red cable on the right is power to the Seatalk network. The white cable in the yellow connector on the right is my GPS receiver. The black cable in the white connector under it is my E140W. The black and white cable in the yellow connector on the left connects to the Seatalk1 network. You can see the Seatalk1 block on the lower left. My Ray240 VHF and the autopilot connect through it. The course computer is the black item on the far left.

upload_2020-12-12_18-45-17.png
 
Last edited:
Here is what mine looks like. It was installed when I got the boat. The top blue one link the two together. The black and red cable on the right is power to the Seatalk network. The white cable in the yellow connector on the right is my E140W. The black cable in the white connector under it is my GPS receiver. The black and white cable in the yellow connector on the left connects to the Seatalk1 network. You can see the Seatalk1 block on the lower left. My Ray240 VHF and the autopilot connect through it. The course computer is the black item on the far left.

View attachment 96207
Yup. That's what mine will look like tomorrow once I had the second converter block. I'll have the same blanks in my second block as well.
 
Just so you guys understand that the seatalkNG is not going to translate anything to the the AP CC. Your auto pilot CC will only understand Seatalk(1) and nmea0183 data even converted data. Routing and goto information needs to be connected to Seatalk/0183 data that is not translated from NG or N2k. GPS location data and heading/fluxgate info will translate just fine.

I have an SPX10 CC (slightly newer) that has SeatalkNG on board and that will not read routing and goto info at all. Even though it is bridged correctly. I have gone round and round with RM tech support for hours and testing of all sorts with them. there response was it really only supports nmea 1083, unless you have older system like the ones your referring to that support SeaTalk(1) for routing and goto correctly, but still won't know what to do with converted N2K/NG data. RM tech support actually talked me out of buying there converter for this.

Now, I am not saying your wasting your time, and it depends on what your trying to achieve from this as well. But if your successful in getting the routing and goto info to work with the converter, please post back on this. I currently have everything working just fine, just want to get rid of NMEA1083/SeaTalk all together. But I am all Garmin except for the AP, you guys have the Axiom maybe that makes the difference? I am about to switch over to Garmin for the AP based on the other thread about that anyway, but would like to wait another year to that and still complete my conversions. Thanks.

EDIT: This is with Garmin to Raymaine SPX CC. I guess the Axiom works a little better as it is Raymarine to Raymarine.
 
Last edited:
Just so you guys understand that the seatalkNG is not going to translate anything to the the AP CC. Your auto pilot CC will only understand Seatalk(1) and nmea0183 data even converted data. Routing and goto information needs to be connected to Seatalk/0183 data that is not translated from NG or N2k. GPS location data and heading/fluxgate info will translate just fine.

I have an SPX10 CC (slightly newer) that has SeatalkNG on board and that will not read routing and goto info at all. Even though it is bridged correctly. I have gone round and round with RM tech support for hours and testing of all sorts with them. there response was it really only supports nmea 1083, unless you have older system like the ones your referring to that support SeaTalk(1) for routing and goto correctly, but still won't know what to do with converted N2K/NG data. RM tech support actually talked me out of buying there converter for this.

Now, I am not saying your wasting your time, and it depends on what your trying to achieve from this as well. But if your successful in getting the routing and goto info to work with the converter, please post back on this. I currently have everything working just fine, just want to get rid of NMEA1083/SeaTalk all together. But I am all Garmin except for the AP, you guys have the Axiom maybe that makes the difference? I am about to switch over to Garmin for the AP based on the other thread about that anyway, but would like to wait another year to that and still complete my conversions. Thanks.
Unless I’m missing something, correctly getting routing/goto information in this setup is precisely what @Irie308 has confirmed works above.
 
Unless I’m missing something, correctly getting routing/goto information in this setup is precisely what @Irie308 has confirmed works above.

I think my issue is I have an in between AP from Raymarine. One where they were trying to force people to use there protocol. The ST800x systems seem to be better suited for this conversion even though an older system. The past two years all I have learned about RM is to stay away, even though they have nice features, Garmin really has it over Raymarine sorry to say.

Sorry for my previous post if it is irrelevant to what you were talking about. Although anyone with an SPX CC this will not work for you. Thank you Raymarine.
 

Forum statistics

Threads
112,950
Messages
1,422,877
Members
60,932
Latest member
juliediane
Back
Top