Because I am writing this myself(ourselves technically, this project finally has the roommate looking at code) I assume that as long as the device can understand and get the libraries then I can send these packets with whichever protocol we choose, and can figure out. UDP when I was researching methods for remote writes seemed the best alternative, I am not sold on it at all.
- Reading over wiki articles has shown me the benefit of doing this correctly, error correction and the ability to poll state back through the socket will be nice
- Reviewing a few more TCP using templates and wiki articles before I go back to the device and look at my options
- This all started with attempting to direct wire a contact switch to my core (par or ser), after study though I felt it was cleaner to have this 0.02w device sitting on the network and watching various circuits. If it sees something it can tell DCE.
- We had simple logging of events going on a (precise) test machine where keystrokes where logged with time and "doorbell rung" on the local machine. This was done with modules though and not our own code.
- To add features to this device down the road I hope to take advantage of its parallel, serial, and usb-to-http://numato.com/8-channel-usb-gpio-module
I appreciate your time. I know you are not a fan of duck tape devices but it's what I have available to learn with and with each project I am learning a lot more about lmce and coding. Another 2 dozen walking coffee pot w/ voicemail builds and I may be able to actually help with some of the (3 million?) lines of LMCE code.