Difference between revisions of "FTDI Linux USB latency"
From Granite Devices Knowledge Wiki
| [checked revision] | [checked revision] |
| Line 12: | Line 12: | ||
{{Warning|Depending on the system, the USB latency might default back to 16 ms after system startup or device reconnection. }} | {{Warning|Depending on the system, the USB latency might default back to 16 ms after system startup or device reconnection. }} | ||
| + | |||
| + | [[Category:Argon_troubleshooting]] | ||
| + | [[Category:Argon_wiring]] | ||
| + | [[Category:IONI_troubleshooting]] | ||
| + | [[Category:IONICUBE]] | ||
| + | [[Category:Setup_guides]] | ||
| + | [[Category:Signals]] | ||
| + | [[Category:SimpleMotion]] | ||
| + | [[Category:Technology]] | ||
| + | [[Category:Troubleshooting]] | ||
Latest revision as of 10:11, 25 July 2018
FTDI Linux USB latency[edit | edit source]
By default, FTDI chip introduces 16 ms delay to reading from a USB port. In practice this means, that SimpleMotion update rate stays too low.
Latest version of the SimpleMotion library tries to change this automatically. However, due to permissions etc. it might be required to do this manually.
USB latency setting[edit | edit source]
Check "/sys/bus/usb-serial/devices/ttyUSB0/latency_timer" and change the value to 1.
This can be done with e.g. the following terminal command with administrator permissions:
- echo 1 > /sys/bus/usb-serial/devices/ttyUSB0/latency_timer
 | Depending on the system, the USB latency might default back to 16 ms after system startup or device reconnection. |
