The device on the machine and Luban indicate that they are connected via Wi-Fi, but after following the steps in the user manual, I am unable to “Send G-code to the machine via Wi-Fi.”
The G-code does appear to load in the workspace’ but the button in the software remains grayed out and I get the “NO” symbol when mousing over it.
Where did you create the g-code?
Do you have the appropriate head for the type of g-code you’re trying to send hooked up?
-S
1 Like
This is my 1st attempt at creating something with this machine so I am quite unfamiliar with it’s idiosyncrasies, but I did follow the manual to the best of my ability which included installing the proper head. I should have mentioned that I was able to transfer the file to a USB drive and run the machine in that fashion, however I would hope that this is not the normal method of running a program.
I am also wondering if there is a way to see the code as it is running - like a real cnc machine?
Thank you for your help.
Is Luban set to the correct model of SM?
Are you trying to send a file that’s larger than the size of your machine?
Is the file type right? .gcode for 3d, .cnc for cnc, .nc for laser.
If you can share your g-code, screen captures of Luban it can help us to troubleshoot.
There are 3 ways to run it. Run straight from Luban, send file over wifi and run from machine, use usb drive and run from machine. I don’t like first method because it ties up your computer and can fail in a whole bunch of ways. For me transferring over wi-fi (usually) is fastest and easiest. No matter where you create your g-code Luban doesn’t change it and just passes it along.
Unfortunately no way to see code running. You can use ncviewer.com or camotics to do a simulation. It’s a really good way to check and see if it’s doing what you expect.
-S
Thank you so much for your help! I am not sure what happened, but this morning when I began preparing the info you requested, the software began working as expected. I noticed that earlier in the Connection panel the Connect/Disconnect button remained in the Connect (blue) state in spite of clicking it several times. I thought this was perhaps an idyosyncracy of the software as the touchscreen was showing the Wi-Fi connection and the Disconnect button. I am happy that it is working, but would like to avoid future problems by knowing what I didn’t do.
Thank you again. I’m pretty sure we’ll be conversing again.
Bill
sometimes exiting luban or rebooting the snapmaker will fix that.
sometimes my machine acts like its connected but not actually do anything, same fix.
The wifi can be fluky with some peoples routers.
No rhyme or reason to it that anyone’s come up with.
Maybe not a great antenna and sensitive to interference?
-S
Even over USB sometimes luban just stops working right for me, shows connected but doesnt work unless i disconnect and reconnect.
Often it’s related to the screen lock turning on. screensaver, standby whatever modes. Results in a situation where the connection needs to be reset.
Yeah, I buy that explanation.
That’s definitely a problem. But seems to happen to some people even when they turn all that off.
-S
I think the easiest explanation is luban is not very good.
It isn’t but this would seem to be a hardware problem.
-S
It appears that I am getting a timeout error after 30000 mSec (30 sec) if there is no traffic over the connection. There is probably no need for the connection once the file is transferred, but it could be quite troublesome if you’re not aware of it (if this is what’s happening).
In my limited experience Luban and the firmware on the touchscreen need additional tuning. This seems a shame as the machine itself appears to be very well constructed.
While I am writing this, has anyone experienced a problem in stopping or pausing the machine from the touchscreen? I have tried to pause a running program several times which causes it to become unresponsive. Stopping the program has the same effect. The only success I’ve had is to cycle power and recover.
The firmware and luban are both in need of a lot of bug fixes.
What version of firmware do you have
version 1.9 is supposidly the most stable of the bunch.
That’s a known bug with 1.10. Cycling power is the fix. Hopefully it will be fixed if they ever release a new firmware. 1.9 doesn’t have it.
-S