## ###### ## ## ## ###
## ## ##### ## ## ## ## ###
## ## ## ## ###### ###### ## ##
___ / _ \ / /_\ \ | _ | | | | | \_| |_/
### ##### ## ## ## ## ## ## ## ## ### ##
IMPORTANT: enter the case-INsensitive alphabetic (no numbers) code AND WRITE SOME SHORT summary of changes (below) if you are saving changes. (not required for previewing changes). Wiki-spamming is not tolerated, will be removed, so it does NOT even show up in history. Spammers go away now. Visit Preferences to set your user name Summary of change: '''Developer notes to evaluate http://caraca.sourceforge.net/ ''' We don't want to duplicate their docs, but evaluate how it competes with HW implemented CAN (in LPC ARM) or modbus over serial (or profibus or similar). I know some people (Johan?) examined closely, please take some notes. '''Main questions:''' * how easy it is to integrate to our firmware? if costly, we might just want to drop ARM on every network-designated board and postpone CAN support for small uC-s * interrupt latency it introduces (important if the main task of uC is ignition control) * CPU clocks from userspace (not as costly as CPU clocks spent in interrupt, but still counts) for given baudrate. This changes in function of: ** minimal: if all frames are neglected (addressed to other nodes) ** if all frames are fully processed '''CPU overhead''' * Using HW uart (right?) so: 1 interrupt / byte on AVR (no FIFO) ** I assume bytes (at least for non-neglected frames) are immediately passed up to userspace, so interrupt handler is short (right?) * CRC calculation? Costlier (regarding CPU and flash) than modbus.org (modbus over serial) RTU checksum? * other costs ? bit stuffing or similar ? Optional: Add document to category: Wiki formatting: * is Bullet list ** Bullet list subentry ... '''Bold''', ---- is horizontal ruler, <code> preformatted text... </code> See wiki editing HELP for tables and other formatting tips and tricks.