Indigo/Jon":16qvelwz said:
I have already been doing some of that type of information input as Port Captain for Traverse City (MI) for the Great Lakes Cruising Club, so I hope to be able to help keep the AC database updated for the area of Northern Michigan in which we typically sail.
We love you. Seriously. Starting June 2013, we're heading to the Great Lakes ourselves to bring as much attention to it as possible - to prompt the creation of more AC data. We have a good start of data through the Great Lakes (Georgian Bay, Michigan, etc) but could use some real local knowledge experts helping.
Indigo/Jon":16qvelwz said:
1. Will that "full wifi connectivity" include data for GPS, wind, depth etc which exists on the N2K network?
2. Will BCM therefore be able to show AIS targets?
3. Will the wifi transmissions allow for UDP, that some apps/programs require? The DMK Box will send UDP packets, but a person wouldn't need that additional box if Garmin's "full wifi connectivity" embraces UDP as well.
I can answer this based on what I know along with things I'm doing myself. My own software development obviously involves Garmin but they're one of 35 companies we're working with today on data support. A big thing that I'm working on is connectivity between devices and especially "legacy" devices that should have a few more years of use even if they don't have N2K or any of the new things that require new hardware. I want our data and especially route information to flow between any two devices. Right now everything is quite proprietary with respect to personal data on all of these charting devices. Environmental data (wind, GPS, depth) is very open and easy to integrate. But the average user doesn't care about the issues and data storage. They just want to plan their next passage and have it available everywhere.
Every company we're working with likes this connectivity. Even Garmin is interested in giving us access to that user data so we can push it to other places. It'll take some time to get there because connectivity isn't easy, technically or politically, but you should be able to tap in a route on your Garmin BCM, get back to the boat, and have it immediately available on your Raymarine, Coastal Explorer, your iPhone, and sitting on our server available for your family to see where you're going (optionally respecting privacy) as well as making your route available for others to share and use themselves even on their 8 year old Sitex chartplotter or The Capn running on XP - heaven forbid.
Your questions:
1. Garmin repeats GPS data on their Ethernet/WiFi network. I believe this is something new - I tested a few firmware updates as part of coming along with BCM. I know they certainly have the ability to put any data over that network/WiFi. GPS is there now. What this means is that if you have an iPad without GPS, you can use the live stream from the Garmin GPS driving the iPad/BCM. I can't see any reason why any other data couldn't be put on the network in the same way (wind, depth, etc) but I honestly don't know if that is being done today. More on connectivity below.
2. AIS - really the same as #1. The capability is certainly there to bridge the AIS data across the Garmin network. I don't know if they're doing it today because BCM does not support it today. I definitely do know that development hasn't ended on BCM. Far from it. I don't think I'm breaking any confidences to say that there is new AC functionality that we've assisted them in implementing for the next release of BCM - it's complete. Over the last 2 weeks I've been working on the 3rd version with even newer stuff being added involving AC. I know they intend to continue enhancement.
3. Garmin's initial connectivity is between BCM and Garmin equipment. They're not saying whether that is TCP or UDP. There is no reason it couldn't be both.
A little more on connectivity from my perspective.
There are two types of connectivity as I wrote about above - environmental data and user data. In the worst case, the environmental data is easy to put over the air. I have a DMK and a Chetco installed on my boat now - both are built in. Those devices sit on NMEA 2000 and/or NMEA 183 and gateway the data bidirectionally to Ethernet/WiFi. Both work as servers allowing many devices to connect and receive the streaming data - that's something special about them too. The existing iAIS and other ActiSense type of products are single shot - only one device can connect at a time. A real server is needed so I can get the raw data on my iPhone, Nexus 7, and PC at the exact same time. DMK and Chetco allow for this now. We're working with both companies.
Whether a particular product like BCM will allow for this type of environmental data to come in from other sources isn't clear. They could allow it. Or they could require that BCM be connected to a Garmin network to get it. I think that'll take time to iron out. All I can add is that it is quite definitely a marketing decision, not a technical one.
My development revolves around user data - the things created by people, not the environment. Those are things like routes, reviews, data updates, plans about where you're going, and information about the people you know who are along your travels. The existing ActiveCaptain part of that is in many products like BCM today. You can write a review or add a hazard comment right now - many have been streaming in from BCM for the last week. Our next data integration is with routes. Our server has support for it now. Our API's will allow apps like BCM to easily synchronize your personal routes with our server much like they synchronize anchorage details and reviews right now. Having bidirectional route data going to our server creates a path between any two products that then support our route API. So if you tap in that BCM route and synchronize (automatic on BCM), and then synchronize Coastal Explorer (also interested in supporting our route API) then your BCM route magically appears on your PC ready to drive your autopilot.
Getting connectivity of routes out to legacy products will is a part of our own Companion apps to be released as soon as I can! The Companion obviously syncs with our server but then has custom software for DMK and Chetco to move user data across to other devices that support NMEA 2000 or 183. Even routes can be moved across 183 serial connections so there is no reason that a route couldn't end up on a 10 year old chartplotter.
I dumped a lot here - sorry. I hope that answers more questions than it creates!