This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
nenticom:nautical_gadgetry [2013/09/06 12:30] krisa created |
nenticom:nautical_gadgetry [2014/06/24 05:40] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Current Standards ====== | ||
+ | ==== NMEA 0813 ==== | ||
+ | * Well known | ||
+ | * Easily hacked | ||
+ | |||
+ | ==== NMEA 2000 (N2K) ==== | ||
+ | |||
+ | * Proprietary | ||
+ | * Standardizes PHY and cabling | ||
+ | * Must register and assign PGNs | ||
+ | * Must buy into the cartel | ||
+ | |||
+ | ====== New Standard ====== | ||
+ | |||
+ | * Wireless out of the box (using Flutter Wireless) | ||
+ | * IPv6-based too much data on wire? Too confusing? | ||
+ | * Open Standard | ||
+ | * Website to register vendor and data codes | ||
+ | * Benevolent dictators of standard | ||
+ | * We approve vendor and data codes | ||
+ | |||
+ | ==== Protocol Details ==== | ||
+ | |||
+ | * Easily tied into standard Ethernet | ||
+ | * L3 Protocol | ||
+ | * IPv6 | ||
+ | * Put data directly into IPv6 extension header (header 60 maybe)? | ||
+ | * Data grouped into multicast addresses | ||
+ | * L4 Protocol | ||
+ | * Existing one out there in RFC land? | ||
+ | * SCTP for life critical | ||
+ | * UDP or own raw protocol for normal traffic | ||
+ | * Author an RFC? | ||
+ | * Version number as part of header | ||
+ | * 1 - NMEA 0813 | ||
+ | * 2 - NMEA 2000 | ||
+ | * 4 - Reef41 | ||
+ | |||
+ | ==== Name Brainstorming ==== | ||
+ | |||
+ | === Company === | ||
+ | * Future Marine, LLC. | ||
+ | * Marine of Things, LLC. (MoT) | ||
+ | * Nauticom, LLC. | ||
+ | * Use Nenticom? | ||
+ | |||
+ | === Protocol === | ||
+ | |||
+ | * ReefCOM | ||
+ | * Reef41 (R41 protocol) | ||
+ | * Marine41 | ||
+ | * N41 | ||
+ | |||
+ | === Product Line === | ||
+ | |||
+ | * Coral | ||
+ | |||
+ | ====== Products ====== | ||
+ | |||
+ | * CoralWind | ||
+ | * Wind, sail, weather station related instruments | ||
+ | * Maybe a separate CoralWeather | ||
+ | * CoralPower | ||
+ | * Engine management | ||
+ | * CoralHead | ||
+ | * N2K gateway, hub for flutter devices | ||
+ | * One version could have wifi | ||
+ | * CoralPatch | ||
+ | * Flutter device that takes an existing device' | ||
+ | |||
+ | ===== Notes ===== | ||
+ | |||
+ | * Solar Power | ||
+ | * Sort of an open version of TikTack product line (now Raymarine) | ||
+ | * Doesn' | ||
+ | * In-line power | ||
+ | * Tap into power going to device being measured (with CoralPatch) | ||
+ | |||
+ | ====== Startup Resources ====== | ||
+ | * Protocol standard developer (embedded, protocols, C language) | ||
+ | * IOS/Android app developer for reading data | ||
+ | * Website, outsourced | ||
+ | * Test equipment | ||
+ | * N2K protocol reader equipment | ||
+ | * Office or hacker space with room for permanently located hardware | ||
+ | * Budget for marine conferences (travel, entrance fees) | ||
+ | |||
+ | ====== Benefits ====== | ||
+ | |||
+ | * Wireless from the start | ||
+ | * And Internet of Things based mentality | ||
+ | * Make it easy to put everything on a network | ||
+ | * Cost less than products with N2K markup | ||
+ | * Allow other companies to develop products around the protocol | ||
+ | |||
+ | ====== Challenges ====== | ||
+ | |||
+ | * Reverse N2K without getting sued? | ||
+ | * N2K has huge market share and is industry standard | ||
+ | * Mostly towards recreational market | ||
+ | * Getting the word out: marine conferences, | ||
+ | * Augment existing products or create own? | ||
+ | |||
+ | ====== Research ====== | ||
+ | |||
+ | * Arduino for CoralHead | ||
+ | * Protocol stacks on Arduino (IPv6) | ||
+ | * N2K interface in Arduino, |