As is, pyharp assumes a request-reply interface between PC and Harp device where messages strictly follow a PC-issued request. In reality, the Harp protocol defines a spec for "event" messages issued from pc-to-device at any time, and the current pyharp package breaks if any of these "event" messages are sent. Accommodating the asynchronous part of the protocol into the pyharp package makes it fully-compliant with Harp protocol.
References:
As is, pyharp assumes a request-reply interface between PC and Harp device where messages strictly follow a PC-issued request. In reality, the Harp protocol defines a spec for "event" messages issued from pc-to-device at any time, and the current pyharp package breaks if any of these "event" messages are sent. Accommodating the asynchronous part of the protocol into the pyharp package makes it fully-compliant with Harp protocol.
References: