-
Notifications
You must be signed in to change notification settings - Fork 17
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
Frequent cable errors from TI-84 + CE #40
Comments
Nope, that is clearly not intended functionality... when communication fails at such a rate, libti*+tilp are not usable. However, the thing is, I don't know what happens. It's news to me that it can happen on an older, non-Python Edition TI-eZ80 calculator. Did you try using another USB port on the computer, or (not to) plug on your calculator on some form of external USB hub, if you have that ? I know that this can impact communication, since my 89 Titanium does not work at all when plugged into a USB 3 port (it's not even detected at the USB level, so libticables doesn't get a chance to see it in the first place), but it works flawlessly, with the same USB cable, when plugged into an external USB 1.1 hub or a 2.0 port. |
Hmm, I have tried using different USB ports, but the error persists. Thanks for the help, I'll probably end up trying out some USB analyzers. |
Well, it seems I have fixed this problem after resetting my kernel configuration. Although I changed a multitude of settings, one that stands out to me as a possible solution is disabling |
I also get similar issues (though with much higher error rates than 1 in 3… more like 6 in 7 times) on my TI-84 Plus when attempting to restore a backup. Specifically, it gets all of the variable names and, at the very end, the PC sends a I am on Linux (Arch), and disabling Note that this only happens when restoring backups, and regularly sending files or listing contents works fine for me (there may be other broken operations but I have yet to find them). If you need any additional info or have anything I should test please let me know. System info:
|
Thanks for the report. It's interesting that the issue occurs on a 84+ as well. It reminds me of a corner case of multi-file transfers I fixed a while ago, long after fixing single file transfer of specific sizes on multiple models. The current commit ID for the fix I'm talking about is debrouxl/tilibs@36e7d8f . I never integrated it onto the main branch because of insufficient regression testing on other models. |
When using tilp, I will occasionally use a functionality such as
Dirlist
,Ready ?
or sending a file and be met with the following error:This occurs around 1/3 of the times I attempt to do something over the cable, but it doesn't seem to have any side effects either (I can still read/write to the file system perfectly when I don't get the error). Please let me know if this is intended functionality, or if there is anything I can do.
Calc OS: 5.3.0.0037
Tilp version: latest from the Gentoo repositories
The text was updated successfully, but these errors were encountered: