Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Develop #149

Merged
merged 18 commits into from
Dec 1, 2017
Merged

Develop #149

merged 18 commits into from
Dec 1, 2017

Conversation

LeonJung
Copy link
Contributor

@LeonJung LeonJung commented Dec 1, 2017

Jeff McBride and others added 18 commits October 30, 2017 20:50
This causes random trucated writes, where only 1 or 2 bytes of the packet
are transmitted by the USB serial chip. I'm not exactly sure why; perhaps
there is some kind of buffering that causes the flush command and write
command to make it to the USB device out-of-order.

In any case, I cannot see any reason why a flush should be necessary,
especially on the TX buffer, so it's easy to remove
…the default latency timer from 16 msec to 2 msec (now the latency timer should be adjusted by yourself... see port_handler_linux source code to see details) #116
Support getting of time on MacOSX/XCode versions that doesn't support
, and also solves'`Error compiling SDK on Mac OSX: "use of undeclared identifier 'CLOCK_REALTIME'" #141'
not to flush the tx buffer
/ Truncated packet transmission on OSX #142
…lved (test code is also in this issue bulletin) #124
…closure loop when the packet is too long to be in uint8_t appropriately
…closure loop when the packet is too long to be in uint8_t appropriately
… the effect on the other languages, such as matlab, labview is needed) #67 #107
@LeonJung LeonJung merged commit b34a0f1 into master Dec 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants