Luban 4.9.0 console responses not shown via network

Can anybody confirm? When I send GCode via the Luban Concole with 4.9.0 when connected to the machine via network, I do not see any responses, not even “ok”.
Did not check serial…

after i updated to version 4.9.0 i can’t import any files, or i can’t see it in the workingspace;

Same problem here. I get the same non-response via serial. I’m trying to query the state of the runout sensor (M412:). I’m trying to get a raw serial terminal connection to work (YAT). I’m connected but the responses don’t appear to be ASCII.

Also, same behavior when I downgraded Luban to 4.8.2. I’m running the latest Artisan firmware.

i was also having this problem with my snapmaker 2 a350.

I submitted an issue on github.

downgrading to the previous version restored the functionality.

I was using via wifi, not sure about usb. the lack of even the old OK was strange.

I opened a ticket on this and the answer is simply that console control via Luban for Artisan specifically is currently not supported (at all) and no estimate when that support will be added.

I tried connecting a generic serial terminal to the USB serial port (with the proper Windows driver installed, evidenced by the fact that Luban controls work over direct USB connection), but it was a no-go. I tried 115200 baud 8N1 and the terminal (YAT) reports unrecognized data.

4.9.1 is out and one of the listed bug fixes is in response to a report along the lines of ‘console responses not working, not even “ok”’. So the intrepid software developers fixed that problem… literally. When you connect to the Artisan over WiFi the console will echo “ok”, regardless of input. The console doesn’t actually process the commands or produce any meaningful output, it just echos “ok”… to anything … everything.

It’s 5:01pm somewhere and a dev is tossing back a beer thinking ‘crushed my defect list today’

1 Like

…10 points to Slytherin…

1 Like

Kinda get the feeling Luban is looking at you with a dismissive look going. “ok” waiting for you to leave. Maybe in the next update, it’ll echo “ok, and?” Maybe even a ¯\_(ツ)_/¯.

2 Likes

Maybe if I open a ticket “Console does not shrug.” we can get shruggy guy in the next release ¯\_(ツ)_/¯

2 Likes

That’s hilarious. I think it got lost in translation.
Guessing if @Hauke wrote - machine doesn’t confirm command execution (not command entry) by replying - ok like it does in 4.8.2 - it could’ve been better translated.
Hopefully there is a ticket somewhere that can be revived…

That would be amazing if it would do that when the result of a command execution is unexpected by controller :slight_smile: