|Anonymous | Login | Signup for a new account||2019-03-23 12:15 UTC|
|Main | My View | View Issues | Roadmap | Repositories|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000676||Firmware||GP IO and GP code||public||2012-09-05 12:18||2012-09-07 12:45|
|Target Version||0.5.0||Fixed in Version|
|Summary||0000676: Allow configurable recording of any pin's state|
|Description||While not eating bucketloads of datalog bandwidth.|
Perhaps combine bits from ports into input state bytes/words. Or perhaps just let people log the ports on a port-by-port basis and leave it at that.
Worst case would be a single bit from each port combined into a single word. How slow/heavy is this?
|Tags||No tags attached.|
|Issue Type||New Feature|
|Risk of Breakage||very low|
|Right now with no pin state config change port H can be logged by inserting PTIH into the logging configuration. This is a good stop gap measure which will be put into use on the hotel fairly shortly.|
|Copyright © 2000 - 2011 MantisBT Group|