-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
error : 9 while connecting #20
Comments
I run GRBL 1.1g on my Eleksmaker with no issues.
It may be helpful if you provide a serial log from Octoprint. What is openbuildcontrols? |
I suspect root cause lies somewhere within the following:
|
hi, |
I use synman's octoprint-bettergrblsupport plugin with OpenBuilds Black Box controller. I'm betting that might be what ouinouin is using. Openbuilds has a web-based controller. So, here's some hope that it can be made to work.... |
I would love to see the raw octoprint serial log. Looks like line #s may be enabled which may be compounding the issue. |
my machine is a xcarve from 2015 or 2016 |
serial.log
|
here is the octoprint.log. |
Grbl Error #9 - G-code lock G-code commands are locked out during alarm or jog state. Check for the following: |
I'm pretty sure that'll fix it for you. This is rather interesting. My engraver will accept an M5 as its first command upon connection and respond accordingly:
But if I try to send the M5 again later (with "Disconnect from the printer" enabled via Serial Conn / Behaviors) it blows up if it is in an alarm state: Anyway, set "What to do on a firmware error" to "Cancel print but stay connected" and you should be fine. |
hmm... I need to figure out why M5 was ever chosen as an announce / hello command... possibly goes all the way back to the original GRBL plugin. At some point along the way it looks like I short-circuited the M115 to M5 translation. For the life of me I can't remember why, but perhaps I realized this previously.
Let me compare branches of code and dig a little more. At this point I'm not sure where the M5 is even coming from. |
Ok, so M5 as HELLO goes all the way back to mic159's implementation. I must have realized at some point that there are better commands ($$) than M5 to send as HELLO. https://github.com/mic159/octoprint-grbl-plugin/blob/master/README.md Please check this setting and let me know the value you have set: It's in Serial Connection --> Firmware & Protocol --> Advanced |
hi, |
I can confirm the CNC is moving and operational now :-).
indeed your plugin is a very good starting point to get remote control of the CNC. |
Octoprint itself uses the hello command to wake up the port. I suggest you leave that field blank as the plugin will simply send $$ given its built in printer gcode to grbl gcode conversion. It would be good to know what values you previously had (go back to my screenshots) as they'll answer some questions I still have about your specific implementation. Glad you got it working. I'll convert your suggestions above to individual feature requests. Also, I still have an open "bug" from about 4 months back related to spindle control. I haven't looked at it but acknowledge it needs to get fixed for CNC. I don't have an actual router/CNC so I'm relying on feedback to figure out how best to support it. Shell |
hi, here is the log while trying to connect :
Changing monitoring state from "Offline" to "Detecting serial port" Serial port list: [u'/dev/ttyACM0'] Connecting to: /dev/ttyACM0 Changing monitoring state from "Detecting serial port" to "Opening serial port" Connected to: Serial<id=0x69a46e30, open=True>(port='/dev/ttyACM0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor Starting baud rate detection... Changing monitoring state from "Opening serial port" to "Detecting baudrate" Trying baudrate: 115200 Send: M5 Recv: Baudrate test retry #1 Send: M5 Recv: Grbl 1.1g ['$' for help] Changing monitoring state from "Detecting baudrate" to "Operational" Recv: [MSG:'$H'|'$X' to unlock] Recv: ok Send: $$ Recv: error:9 Changing monitoring state from "Operational" to "Error: error:9" Send: M112 Send: N1 M112*32 Send: N2 M104 T0 S0*35 Send: N3 M140 S0*102 Changing monitoring state from "Error: error:9" to "Offline (Error: error:9)" Connection closed, closing down monitor
while in openbuildcontrols I got :
Checking for Updates [19:09:48] [ Update Available! ] OpenBuilds CONTROL 1.0.233. is available now. [19:09:48] [ Update Available! ] Download will start in 0 seconds (cancel) [19:09:48] [ Update Available! ] You will be prompted when its ready to be installed [19:09:54] [ connect ] PORT INFO: Port is now open: /dev/ttyACM0 - Attempting to detect Firmware [19:09:54] [ connect ] Checking for firmware on /dev/ttyACM0 [19:09:54] [ connect ] Detecting Firmware: Method 1 (Autoreset) [19:09:55] [ connect ] Detecting Firmware: Method 2 (Ctrl+X) [19:09:56] [ connect ] Detecting Firmware: Method 3 (others that are not supported) [19:09:56] [ ] Grbl 1.1g ['$' for help] [19:09:56] [ ] [MSG:'$H'|'$X' to unlock] [19:09:57] [ $$ ] $0=10 ;Step pulse time, microseconds [19:09:57] [ $$ ] $1=255 ;Step idle delay, milliseconds [19:09:57] [ $$ ] $2=0 ;Step pulse invert, mask [19:09:57] [ $$ ] $3=3 ;Step direction invert, mask [19:09:57] [ $$ ] $4=0 ;Invert step enable pin, boolean [19:09:57] [ $$ ] $5=0 ;Invert limit pins, boolean [19:09:57] [ $$ ] $6=0 ;Invert probe pin, boolean [19:09:57] [ $$ ] $10=1 ;Status report options, mask [19:09:57] [ $$ ] $11=0.020 ;Junction deviation, millimeters [19:09:57] [ $$ ] $12=0.002 ;Arc tolerance, millimeters [19:09:57] [ $$ ] $13=0 ;Report in inches, boolean [19:09:57] [ $$ ] $20=0 ;Soft limits enable, boolean [19:09:57] [ $$ ] $21=0 ;Hard limits enable, boolean [19:09:57] [ $$ ] $22=1 ;Homing cycle enable, boolean [19:09:57] [ $$ ] $23=3 ;Homing direction invert, mask [19:09:57] [ $$ ] $24=25.000 ;Homing locate feed rate, mm/min [19:09:57] [ $$ ] $25=750.000 ;Homing search seek rate, mm/min [19:09:57] [ $$ ] $26=250 ;Homing switch debounce delay, milliseconds [19:09:57] [ $$ ] $27=1.000 ;Homing switch pull-off distance, millmeters [19:09:57] [ $$ ] $30=12000 ;Maximum spindle speed, RPM [19:09:57] [ $$ ] $31=0 ;Minimum spindle speed, RPM [19:09:57] [ $$ ] $32=0 ;Laser-mode enable, boolean [19:09:57] [ $$ ] $100=40.000 ;X-axis steps per millimeter [19:09:57] [ $$ ] $101=40.000 ;Y-axis steps per millimeter [19:09:57] [ $$ ] $102=188.947 ;Z-axis steps per millimeter [19:09:57] [ $$ ] $110=8000.000 ;X-axis maximum rate, mm/min [19:09:57] [ $$ ] $111=8000.000 ;Y-axis maximum rate, mm/min [19:09:57] [ $$ ] $112=500.000 ;Z-axis maximum rate, mm/min [19:09:57] [ $$ ] $120=500.000 ;X-axis acceleration, mm/sec^2 [19:09:57] [ $$ ] $121=500.000 ;Y-axis acceleration, mm/sec^2 [19:09:57] [ $$ ] $122=50.000 ;Z-axis acceleration, mm/sec^2 [19:09:57] [ $$ ] $130=740.000 ;X-axis maximum travel, millimeters [19:09:57] [ $$ ] $131=790.000 ;Y-axis maximum travel, millimeters [19:09:57] [ $$ ] $132=100.000 ;Z-axis maximum travel, millimeters [19:09:57] [ $$ ] ok [19:09:57] [ $I ] [VER:1.1g.20181112:] [19:09:57] [ $I ] [OPT:V,15,128] [19:09:57] [ $I ] ok [19:09:58] [ autoupdate ] Starting update... Please wait [19:09:58] [ connect ] Firmware Detected: grbl version 1.1g on /dev/ttyACM0 [19:10:00] [ autoupdate ] Starting Download: v1.0.233 [19:10:13] [ autoupdate ] New update ready [19:10:42] [ disconnect ] PORT INFO: Port closed
version of GRBL is 1.1g
any test i can perform ?
The text was updated successfully, but these errors were encountered: