-
Notifications
You must be signed in to change notification settings - Fork 98
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
Remove DTR toggle to make CONTROL more compatible with native USB on grblHAL #333
Comments
@swarfer - referring to https://openbuilds.com/threads/openbuilds-control-software.13121/page-82#post-138238 Line 1098 in 4800540
We do have DTR disabled. Does it still not work on the Pico? serialport/node-serialport#867 (comment) serialport/node-serialport#1605 (comment) |
still not connecting bCNC does connect to this device and reports |
[21:43:42] [ connect ] PORT INFO: Port is now open: COM7 - Attempting to detect Controller... [21:43:42] [ connect ] Attempting to detect Controller (1): (Autoreset) [21:43:42] [ ] ok [21:43:43] [ connect ] Attempting to detect Controller (2): (Ctrl+X) [21:43:43] [ ] GrblHAL 1.1f ['$' or '$HELP' for help] I think the reset triggers the "GrblHAL 1.1f ['$' or '$HELP' for help]" that we keep an eye out for? Line 1459 Lines 1455 to 1471 in 0f4f909
Don't see that string in the bCNC output. Will add a or "[VER:1.1f..." check maybe? |
Can you please test with draft https://github.com/OpenBuilds/OpenBuilds-CONTROL/releases/tag/untagged-1bdd758d4fa6a06826bb when you have a minute |
nope, Pico comes up as COM7 and CONTROL reports [06:52:15] [ 3D Viewer ] WebGL Support found! success: this application will work optimally on this device! maybe I need to update the grlHAL on this device and retest..... from bCNC a $I shows and it comes up in alarm state because there are no limits connected |
This time you have less output than before, but error 9 implies its already alarmed? |
i have now changed settings ($15 and $14 IIRC) so it does not boot in alarm state and now I see 'error:2' after connection fails. bCNC still 'just works' though the terminal does now show much, just a $# and the result and some OK's |
No description provided.
The text was updated successfully, but these errors were encountered: