I have pins on the AC20 labeled Robnet going to the blue sockets on the back of the AP26 remotes. There's nothing into the yellow sockets on the AP26's.
From the Simrad setup PDF it appears an AP26 can have both blue Robnet and yellow Simnet connections into it simultaneously. But there's no Simnet input into the AC20 autopilot computer. I'm fine with continuing to use the blue Robnet connections to the AP26 remotes. Unless there's some other compelling reason to use Simnet for their communication? Or other N2K benefit?
I have GPS being provided via 0138 through a chartplotter. (GP320B->MFD12->0183). There's also an H2183 via MFD and a PG-700 via N2K (which seems partially redundant... but whatever that's another thread).
I don't need to eliminate the 0183 into the AC20 computer from the MFD12 as I'm not likely to be running autopilot without the plotter. At least not any time soon, as I don't plan on using anything else (PC, OpenCPN, etc) for navigation anytime soon. Not that there's anything wrong with that idea, just that I don't have that on my current 'to do' list.
It looks like I'd need to use something else to get the 0183 data in/out of the AC20.
The Simrad AT10 supposedly handles Simnet to/from 0183. But then I'd need to set up a Simnet network, as it would need power. I'm unclear if an AT10 could be powered off an N2k network using just the 24005729 adapter cable. I also get the impression that the AT10 is a tee device, not an endpoint. So I'd need to have it at the end of the N2K network... which is NOT where the AC20 computer is located.
So what, if any, benefits would I gain having the AP26 control units connected to the N2K network?
__________________
-- Bill Kearney
2005 Eastbay 47 FB - Solstice, w/Highfield CL360 tender
|