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

Remove DTR toggle to make CONTROL more compatible with native USB on grblHAL #333

Open
petervanderwalt opened this issue Sep 18, 2023 · 7 comments

Comments

@petervanderwalt
Copy link
Contributor

No description provided.

@petervanderwalt
Copy link
Contributor Author

petervanderwalt commented Apr 9, 2024

@swarfer - referring to https://openbuilds.com/threads/openbuilds-control-software.13121/page-82#post-138238

hupcl: false // Don't set DTR - useful for X32 Reset

We do have DTR disabled. Does it still not work on the Pico?
serialport/node-serialport#867 (comment)
serialport/node-serialport#1605 (comment)

@swarfer
Copy link
Collaborator

swarfer commented Apr 11, 2024

still not connecting
[18:44:48] [ connect ] PORT INFO: Port is now open: COM7 - Attempting to detect Firmware
[18:44:48] [ connect ] Checking for firmware on COM7
[18:44:48] [ connect ] Detecting Firmware: Method 1 (Autoreset)
[18:44:48] [ ] ok
[18:44:48] [ connect ] Detecting Firmware: Method 2 (Ctrl+X)
[18:44:49] [ connect ] Detecting Firmware: Method 3 (others that are not supported)
[18:44:49] [ ] error:9
[18:44:52] [ connect ] ERROR!: No supported firmware detected - See https://docs.openbuilds.com/doku.php?id=docs:blackbox:faq-usb-connection-failed for more details. Closing port COM7
[18:44:52] [ disconnect ] PORT INFO: Port closed

bCNC does connect to this device and reports
$I
[VER:1.1f.20230810:]
[OPT:VNSL,35,1024,3,0]
[AXS:3:XYZ]
[NEWOPT:ENUMS,RT+,SED,RTC]
[FIRMWARE:grblHAL]
[NVS STORAGE:*FLASH]
[FREE MEMORY:227K]
[DRIVER:RP2040]
[DRIVER VERSION:230810]
[DRIVER OPTIONS:SDK_1.5.0]
[BOARD:https://github.com/Expatria-Technologies/PicoBOB]
ok

@petervanderwalt
Copy link
Contributor Author

petervanderwalt commented Apr 11, 2024

[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

OpenBuilds-CONTROL/index.js

Lines 1455 to 1471 in 0f4f909

// Machine Identification
if (data.indexOf("Grbl") === 0) { // Check if it's Grbl
debug_log(data)
status.comms.blocked = false;
if (data.indexOf("GrblHAL") === 0) {
status.machine.firmware.type = "grbl";
status.machine.firmware.platform = "grblHAL"
status.machine.firmware.version = data.substr(8, 4); // get version
} else if (data.indexOf("FluidNC") != -1) { // Grbl 3.6 [FluidNC v3.6.5 (wifi) '$' for help]
status.machine.firmware.type = "grbl";
status.machine.firmware.platform = "FluidNC"
status.machine.firmware.version = data.substr(19, 5); // get version
} else {
status.machine.firmware.type = "grbl";
status.machine.firmware.platform = "gnea"
status.machine.firmware.version = data.substr(5, 4); // get version
}

Don't see that string in the bCNC output. Will add a or "[VER:1.1f..." check maybe?

@petervanderwalt
Copy link
Contributor Author

@swarfer added 0d76d6e

Can you please test with draft https://github.com/OpenBuilds/OpenBuilds-CONTROL/releases/tag/untagged-1bdd758d4fa6a06826bb when you have a minute

@swarfer
Copy link
Collaborator

swarfer commented Apr 20, 2024

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!
[06:52:16] [ websocket ] Bidirectional Websocket Interface Started Succesfully
[06:52:17] [ update ] Checking for Updates
[06:52:17] [ update ] You are already running OpenBuilds CONTROL 1.0.372
[06:52:26] [ connect ] PORT INFO: Port is now open: COM7 - Attempting to detect Controller...
[06:52:26] [ connect ] Attempting to detect Controller (1): (Autoreset)
[06:52:26] [ ] ok
[06:52:26] [ connect ] Attempting to detect Controller (2): (Ctrl+X)
[06:52:27] [ connect ] Attempting to detect Controller (3): (others)
[06:52:27] [ ] error:9
[06:52:30] [ connect ] ERROR!: No Response from Controller - See https://docs.openbuilds.com/doku.php?id=docs:blackbox:faq-usb-connection-failed for troubleshooting information. Closing port COM7
[06:52:30] [ disconnect ] PORT INFO: Port closed

maybe I need to update the grlHAL on this device and retest.....
nope, that did not change anything

from bCNC a $I shows
$I
[VER:1.1f.20240416:]
[OPT:VNMSL,100,1024,4,0]
[AXS:4:XYZA]
[NEWOPT:ENUMS,RT+,ES,EXPR,SED,RTC]
[FIRMWARE:grblHAL]
[SIGNALS:HSEP]
[NVS STORAGE:*FLASH]
[FREE MEMORY:219K]
[DRIVER:RP2040]
[DRIVER VERSION:240408]
[DRIVER OPTIONS:SDK_1.5.0]
[AUX IO:2,0,0,0]

and it comes up in alarm state because there are no limits connected
after inverting all needed pins so it does not start in alarm CONTROL does not connect but reports error:2 instead of :9

@petervanderwalt
Copy link
Contributor Author

[06:52:27] [ ] error:9

This time you have less output than before, but error 9 implies its already alarmed?
But surely Ctrl+X should have cleared the Alarm?

@swarfer
Copy link
Collaborator

swarfer commented Apr 24, 2024

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

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

No branches or pull requests

2 participants