Closed d3d3d closed 2 years ago
This is related to #61 which will likely be reverted in an up and coming release. I've decided to replace auto sensing logic with simple "Invert" checkboxes in Plugin Settings.
I may work on this tonight. You'll see this issue touched when I take it on.
@d3d3d I nudged this one along.... if you subscribe to the release candidate branch, please grab 2.2.0rc2 and report back on results.
See here for more details on how to switch to the RC branch: https://github.com/synman/Octoprint-Bettergrblsupport/wiki/Bleeding-Edge-Updates
If you need to tweak axis direction while jogging / framing / probing
Same issue on rc2 after inverting XYZ with LLC set & rebooting Pi. Note that if URC is set draw frame does work correctly, but the of the direction arrows have inverted result.
Just noticed an error displayed on Octoprint and notification area when first connecting to the laser. The error was likely there before and I did not notice.
Grbl Error #20 Received Unsupported command Unsupported or invalid g-code command found in block.
Again Thank You, let me know what to do to help.
would need to see, at the least, what was in your terminal window to diagnose that #20 error. what happens when you don't invert anything.
The way the logic is built now, 2.2.0 RC2 with no inversion set works EXACTLY like versions prior to 2.1.0.
grbl error #20 occurs with and without XYZ inverted. I can recreate error #20 by sending M876 P1 to laser via terminal.
GCODE from terminal below, I disconnected after error to capture text easier...
Changing monitoring state from "Offline" to "Detecting serial connection"
Performing autodetection with 7 port/baudrate candidates: /dev/ttyACM0@115200, /dev/ttyACM0@250000, /dev/ttyACM0@230400, /dev/ttyACM0@57600, /dev/ttyACM0@38400, /dev/ttyACM0@19200, /dev/ttyACM0@9600
Trying port /dev/ttyACM0, baudrate 115200
Connecting to port /dev/ttyACM0, baudrate 115200
Handshake attempt #1 with timeout 2.0s
Connected to: Serial
Why would you want to send an M876 command? that is not a valid GRBL gcode command.
Look at dump: M876 P1 was sent to laser right after the $$ code when serial connection is first established...
My mistake XYZ should NOT be inverted on Aufero LS1. it works as before with RC2.
You must be sending that. It is NOT coming from BGS ...
talk about an obscure command too
Not sure what is going on, Disabled the BGS plugin and the GCODE M876 P1 is NO longer sent at serial connection... Will look further into this #20 error, perhaps it is Octoprint related. Will let you know.
Please go ahead and close #74, RC2 solved the Start Position issue.
Thanks again.
do you have any other plugins installed? maybe something left over from a prior 3d printer install?
I'm more than happy to take a look at your octoprint.log file if you'd like it reviewed? But yeah, I can assure you nothing in BGS would send that command.
I'm thinking another plugin is doing this... perhaps triggering off of something coming across the wire between your laser and BGS.
will close this issue but am here to help you figure out the M876 thing. You've peaked my curiosity.
Clean install Octoprint only BGS plugin., disabled Gina's GCODE Viewer...
lol Yeah, know what you mean 'peaked curiosity'. Looking into now, will keep you posted.
My Ortur Aufero LS 1 (firmware 1.87) Starting Position and Home Position is Lower Left Corner (LLC)
The plugins ver 2.1.3 and 2.2.0rc1 with starting point set to LLC behave as though the starting position is URC
Note: Laser works correctly with LLC starting point set using current version of Lightburn. No issue with prior plugin until the staring point feature was added.
Thank You for developing and supporting the plugin! Let me know how I can help.