You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@edgent.apache.org by "Dale LaBossiere (JIRA)" <ji...@apache.org> on 2017/05/10 15:07:04 UTC

[jira] [Created] (EDGENT-411) enhance connectors.serial - missing things?

Dale LaBossiere created EDGENT-411:
--------------------------------------

             Summary: enhance connectors.serial - missing things?
                 Key: EDGENT-411
                 URL: https://issues.apache.org/jira/browse/EDGENT-411
             Project: Edgent
          Issue Type: Improvement
          Components: Connectors
            Reporter: Dale LaBossiere


Serial connector seems to be adding a bit of structure for a cmd request/response protocol to a SerialDevice that's attached to a system via a SerialPort.  

It's hard to make sense of it until seeing it used in samples.connectors.elm327.Elm327Streams (and elm327.runtime) and sample.connectors.odb2.Obd2Streams - that is, a particular cmd request/response protocol to a device connected via a serial port.  And there's no sample implementation of SerialDevice or SerialPort in the repo.

At a high level it strikes me that the SerialConnector should offer a general SerialDeviceStreams at the conceptual level of the of Elm327Streams.  And we really need some doc (or sample) of a SerialDevice/SerialPort.

And what about a non-periodic (non-poll) form of non-static cmd list invocation?  e.g., sending commands in a TStream - something like {{static TStream<JsonObject> sendCommands(SerialDevice, TStream<Cmd>)}}.

And maybe there are other forms of use of a serial device - e.g., maybe the device/port just emits records on its own, not a bounded response to a "cmd".




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)