10W Laser Module Not Working out of Box

Snapmaker 2.0
1

I am aware that there are others out there with issue not being able to get past the required initial calibration steps. Mine gets stuck on the calibration with the metal plate.

I’ve reached out to Snapmaker support and haven’t heard anything back. I’ve read all sorts of ideas to get it working and tried them and none work. I think it comes down to the bluetooth not working.

When I first started using the 1.6W module it worked fine. At some point it couldn’t auto calibrate and had me manual calibrate. Since manual calibration worked like a champ, I never figured I had an actual problem. But with the 10W now requiring the use of camera calibration, I think I’m hosed. Yes?

I have a Snapmaker 2.0 350A from the Kickstarter they did. Also have the enclosure as well. The CNC, 3DP, and 1.6W (minus auto calibration) all work fine.

Below is results from the console:

When 10W Laser Module is plugged in:

snapmaker-luban 4.5.0
Connected to /dev/tty.usbserial-1410
others < Compiled: Jun 14 2022, 11:43:22
others < PACKAGE: Snapmaker_V4.4.17
others < Module Ver:
others < Module 0x003A27A6: v1.11.5
others < Module 0x003935E4: v1.11.5
others < Module 0x00506BD6: v1.11.5
others < Module 0x003882EE: v1.11.5
others < Module 0x00394012: v1.11.5
others < Module 0x003A367C: v1.11.5
others < Module 0x00E06484: v1.11.5
others < linear X1 length: 356 mm, lead: 8 mm
others < linear Y1 length: 356 mm, lead: 8 mm
others < linear Z1 length: 356 mm, lead: 8 mm
others < linear Y2 length: 356 mm, lead: 8 mm
others < linear Z2 length: 356 mm, lead: 8 mm
others < failed to read BT info - 4!
others < failed to read BT info - 4!
others < failed to read BT info - 4!
others < failed to read BT version - 4!
G53
ok

When the 1.6W Module is Plugged in:

snapmaker-luban 4.5.0
Connected to /dev/tty.usbserial-1410
others < Compiled: Jun 14 2022, 11:43:22
others < PACKAGE: Snapmaker_V4.4.17
others < Module Ver:
others < Module 0x00394012: v1.11.5
others < Module 0x003882EE: v1.11.5
others < Module 0x00506BD6: v1.11.5
others < Module 0x0020E134: v1.11.4
others < Module 0x003A27A6: v1.11.5
others < Module 0x003935E4: v1.11.5
others < Module 0x003A367C: v1.11.5
others < linear X1 length: 356 mm, lead: 8 mm
others < linear Y1 length: 356 mm, lead: 8 mm
others < linear Z1 length: 356 mm, lead: 8 mm
others < linear Y2 length: 356 mm, lead: 8 mm
others < linear Z2 length: 356 mm, lead: 8 mm
others < failed to read BT info - 4!
others < failed to read BT info - 4!
others < failed to read BT info - 4!
others < failed to read BT version - 4!
G53
ok

I’ve tried factory resetting via M502 and M500 and got the below results that don’t seem to really do anything that I can tell:

M502
others < leveling OFF
others < set min_planner_speed:0.05
echo:Hardcoded Default Settings Loaded
ok

M500
echo:Settings Stored (1077 bytes; crc 6037)
ok

I also turned on developer mode via the touch screen and did the reset all under the preferences settings. That acted more like a factory reset as I have to do all initial calibration steps and had to put in the wifi again.

Any suggestions on what to do? Still waiting for Snapmaker support to reply.

2

At least firmware 1.14 installed?

3

I has installed v1.14.3 last month. I just installed the 1.14.5 version and tried the 10W laser initial calibration. No dice. It fails when it tries to fire up the camera to view the red laser on the metal calibration plate. It’s an instant fail, doesn’t even really try.

Since both my 1.6W and now this brand new 10W both show bluetooth issues, it makes me think I’ve got a problem with the actual Snapmaker’s bluetooth.

4

The Bluetooth server is in the Android TouchPad, which is why the camera only works with a WiFi connection to the TouchPad. You will need to work with Snapmaker Support to determine if your TouchPad is bad, as there isn’t anything that we can repair. While it is possible that the WiFi clients in each of the Laser Models is bad, it is highly unlikely. I suggest that you try is a Full Factory Reset, which includes the TouchPad. What you did above, only resets the Controller, which is not involved with the Bluetooth communications. You can search the forums for instructions on how to perform a Full Factory Reset.

1 Like
5

I have done the reset via TouchPad in developer mode.

Experiment > Preferences > Reset All

And also did the M502 and M500 via the Console in Luban software.

Didn’t help.

What is interesting is when in developer mode on the touchpad there is a Factory icon on the Home Screen. Tapping that gives you a list of things in Chinese. Using Google Translate via camera on my phone there is a button to test the bluetooth module. When I tap on that there is a message (still in Chinese) that says “bluetooth status: not connected”. There’s a button that says “Get a Photo Test” and when tapping that it tries something then a message shows “bluetooth not connected”

Looking like my touchpad bluetooth is not working?

6

Yeah, it looks like there is a problem with your TouchPad. Support should be able to very whether or not it is the TouchPad. If it is, Support should be able to tell you how much a new one will be. I think they’re like $100, but I could be way off. Best of luck…

7

Well, there is a new development, sadly.

I plugged in my newer 3D module and when it goes to load the filament, the gear inside is going the wrong way! Both load and unload go the same direction. I tried my original 3D module and it does the same. Le sigh…

I also tried swapping the tool head and Y-axis cables to see if it was the cable. Same as above.

Read on another discussion that these issues might be a sign that the controller HUB is busted, maybe?

Anyone know how to reprogram the controller to use the empty add-on port as the tool head port?

8

Unfortunately, it is beginning to sound like you may have plugged in one of the cables backwards, and that it has damaged the Controller as well. Have you opened a ticket with Support? They are the only ones who can help you at this point.