#1 Serial communication needs implementation

[Joshua Outwater]

Serial devices are not currently supported because the
communication has not been implemented.

[Joshua Outwater]

Logged In: YES
user_id=973913

Code for this was already written but needs to be modified
to fit into the new architecture of the library.

[Joshua Outwater]

Logged In: YES
user_id=973913

Currently integrating code. Still need to write code for
reading/writing packet.

[Joshua Outwater]

Logged In: YES
user_id=973913

Continuing to work on this. Having issues with the first
bytes of a packet getting lost when receiving a packet. For
some reason the DLE character is rarely coming through to
identify the start of a packet. There are also other cases
where I'm getting a false start of a packet. The DLE
character is found and followed by a invalid protocol ID.
This may be partially due to the way I'm sending ACK/NAK
packets. It could also be due to the USB<->Serial connector
I have to use. Things to try:

* Before writing a packet send a request to flush the
underlying buffer and then read the ACK/NAK packet from the
device. See if that solves the missing data problem.
* Improve the packet parser to identify invalid packet data
and skip over it.

[Joshua Outwater]

Logged In: YES
user_id=973913

An initial implementation is now available. I did basic
testing. Retrieving the device info, but I haven't run the
full gamut yet. Keeping this bug open until I've done that.