I have a Garmin 4208, so maybe it is different, but I beleive I need some sort of external "heading sensor". Do you know if the E80 is just using GPS or whether it is using your autopilot's compass? How does the chart overlay work -- is it adequate?
Thanks

That's the threshold question I had (whether the fluxgate was a heading sensor of sorts) -- and the answer I was hoping for! I'll hook it up and go from there. I am most interested in using the MARPA parimeter alarm anyway so the precise target heading shouldn't be that crucial to that function. Thanks again.

You'll find the marpa lock is a problem as is the constant vector recalculations. I always end up turning it off in any conditions where I really need it.

I always wondered if I could feed cog into a mux and change it to heading and use it for marpa. While the accuracy might be a bit suspect for a small boat the damping associated with Cog calculations actually might help MARPA hmmmmm
Dave

__________________Check out my new blog on smart boat technology, networking and gadgets for the connected sailor! - http://smartboats.tumblr.com

Important issue is that its a fast heading sensor providing updates several times a second. My B & G heading sensor connected via NMEA @ 4800 baud (updates about twice in three seconds) to my Raymarine C80 worked, but gave very shaky data updates when using MARPA.

I would recommend therefore using Raymarine's own fast heading sensor. You only need one source so that should suffice for all other heading needs.

MARPA on the Raymarine E Series setup requires a heading sensor. The fluxgate is that sensor. If you are using the X series autopilot, the heading is stabilized by a laser gyro (inside the autopilot, not the fluxgate). I believe this also to be the case on the S3G systems. The more stable the heading source, the more accurate it can be. The narrower the radar beam, ditto.

However, the results you will get from MARPA require that you understand some of its limitations. When we used to plot targets on the radar screen with grease pencils, we used to put a cross over the target every three minutes. After six minutes we would draw a line joining the crosses and figure out if we were far enough at CPA. MARPA on this system tries to give you the answer much quicker. It takes into account every time the radar beam hits the target and the rate of change. This time is just simply too short, at least in the beginning, so you have to wait quite a bit to get a fairly decent vector. Feeding it anything else, like course, would be using incorrect information. I'm not sure you could anyway.

I hope I'm not preaching to the converted here....sorry if I do.

__________________Capn Morgan'If you can fill the unforgiving minute with sixty seconds' worth of distance run...'

I also have a 4208 and use my fluxgate compass as a heading indicator for MARPA. We've been very happy with it, especially leaving San Francisco Bay when the first time we saw the Golden Gate Bridge was when we were directly underneath it.

MARPA is not super accurate right now because we need to re-calibrate our compass. I'm not sure if that has to do with all the changes in magnetic variation it's seen since we brought it back from Mexico. Makes for an inaccurate CPA.

I will say that if there's just one target we're concerned about we usually just drop a bearing/range marker and watch that. Then I don't have to wonder if the software is working correctly.

I don't have a Raymarine autopilot, have a very old, but working alpha system. I do have a fluxgate that i purchased used. But I obviously need some other hardware to connect it to my E80 system to make Marpa work