Nothing moving after 1.14.2 upgrade

Hi I have several Snapmaker 2 350 3D printers.

I just upgraded one to V1.14.2 with no problems.
After doing some prints today, I updated another one.

Now I cannot get any of the drives on the one I just updated to move. AT ALL

I cannot do a callibration (no movement) and I cannot jog the head manually. It just sits in the home position.

My machine:
Touchscreen version 1.14.1
Controller version V4.4.16

I cycled power several times and re-ran the upgrade another time, with no change.

Hardware/electronic problems seem unlikely
 what has this firmware done?

1 Like

Sine there have been no replies
 an update.

The 1.14.x update is definately the problem.

I reverted back to 1.12.x and 1.13.x and the printer works fine for both of these, but if I try 1.14.1 or 1.14.2 then the printer stops moving.

I notice that the 1.14.x update has MANY more modules in it than the 1.13 an 1.12 I wonder if it is a memory problem?

Since we purchased all 3 printers at the sime time, why is this unit giving a problem?
Early on we had a touchscreen fail, so we were asked to send the touchscreen and controller back for testing. When we got them back, I assumed the controller was our original unit, but I’m wondering if it was an older model with less-memory (or other difference) that the new firmware does not like.

As a part of 14.1, checks were added to make sure the machine model was recognized before allowing movement. I wonder if something went wrong with that check with your printer.

Could you upload the log files for the problematic printer? Maybe those will give some insight into whether or not this is actually the issue.

As far as I’m aware, the controller design hasn’t changed, so I’d be surprised if it was a memory issue with an old controller.

I had the same issues with the 14.xx firmware.

+1 for the log files.
You could also observe the startup with a serial (usb) connection in the terminal of luban.
Surely its a bug about the recognition of the new linear modules.

1 Like

I don’t use luban. I slice my files using Cura, and simply load them from USB.

I have dumped the logs from the problem machine. Note I’ve tried several Firmware versions so the only actual 3D printing in the log is when I’m using 12.x or 13.x.

Also note, this printer is not online.

Snapmaker2-Logs.zip (365.3 KB)

When the SC2 log reports “FabScreen version: V1.14.x,” there is no printining hapenning

You could also observe with other serial terminals, there is no special need for luban.

You’re missing a Y module at startup. Check your connections. If you can’t make it work contact support.

233510,1970.01.01 00:03:53.510,INFO,SC-FW,Scanning modules ...
235483,1970.01.01 00:03:55.483,ERROR,SC-FW,No module on CAN1!
236485,1970.01.01 00:03:56.485,INFO,SC-FW,New Module: 0x203BBA00
236514,1970.01.01 00:03:56.514,INFO,SC-FW,Got axis X, endstop: 0
236534,1970.01.01 00:03:56.534,INFO,SC-FW,length: 356 mm, lead: 8 mm
236547,1970.01.01 00:03:56.547,INFO,SC-FW,Function [  0] <-> Message [  3]
236551,1970.01.01 00:03:56.551,INFO,SC-FW,New Module: 0x203BB9A6
236614,1970.01.01 00:03:56.614,INFO,SC-FW,Got axis Z, endstop: 0
236634,1970.01.01 00:03:56.634,INFO,SC-FW,length: 356 mm, lead: 8 mm
236647,1970.01.01 00:03:56.647,INFO,SC-FW,Function [  0] <-> Message [  4]
236649,1970.01.01 00:03:56.649,INFO,SC-FW,New Module: 0x2001AB3C
236671,1970.01.01 00:03:56.671,INFO,SC-FW,Got toolhead 3DP!
236695,1970.01.01 00:03:56.695,INFO,SC-FW,Function [  8] <-> Message [ 18]
236697,1970.01.01 00:03:56.697,INFO,SC-FW,Function [  9] <-> Message [ 19]
236701,1970.01.01 00:03:56.701,INFO,SC-FW,Function [  6] <-> Message [ 20]
236704,1970.01.01 00:03:56.704,INFO,SC-FW,Function [  7] <-> Message [ 21]
236712,1970.01.01 00:03:56.712,INFO,SC-FW,Function [  1] <-> Message [  5]
236715,1970.01.01 00:03:56.715,INFO,SC-FW,Function [ 10] <-> Message [ 22]
236719,1970.01.01 00:03:56.719,INFO,SC-FW,Function [  2] <-> Message [  6]
236722,1970.01.01 00:03:56.722,INFO,SC-FW,Function [ 16] <-> Message [ 23]
236725,1970.01.01 00:03:56.725,INFO,SC-FW,probe: 0x1, filament: 0x1
236729,1970.01.01 00:03:56.729,INFO,SC-FW,New Module: 0x203BB0EE
236743,1970.01.01 00:03:56.743,INFO,SC-FW,Got axis Y, endstop: 0
236762,1970.01.01 00:03:56.762,INFO,SC-FW,length: 356 mm, lead: 8 mm
236777,1970.01.01 00:03:56.777,INFO,SC-FW,Function [  0] <-> Message [  7]
236781,1970.01.01 00:03:56.781,INFO,SC-FW,New Module: 0x203BB984
236842,1970.01.01 00:03:56.842,INFO,SC-FW,Got axis Z, endstop: 0
236865,1970.01.01 00:03:56.865,INFO,SC-FW,length: 356 mm, lead: 8 mm
236877,1970.01.01 00:03:56.877,INFO,SC-FW,Function [  0] <-> Message [  8]
236882,1970.01.01 00:03:56.882,INFO,SC-FW,Model: unknow
237180,1970.01.01 00:03:57.180,ERROR,SC-FW,Cannot detect any Linear Module!

It works on prior firmware because it doesn’t verify to see if all the modules are installed properly. But, it also means your endstop won’t work reliably. This should get fixed, likely with a replacement module by support.

2 Likes

Thnaks for identifying the cause.

Check your connections

Can you be more specific? Which cable would have to be bad/loose in order for the system to be able to move, but not detect the endstop?

Aren’t the drives and endstops part of the same linear actuator (module??). Doesn’t the same cable feed both if it;s a CAN bus. Imagine that I don’t know where the cables go once they enter the actuators :slight_smile:

Actually as I read that section of the log, it does see X, Y and Z, several times. . But there is the issue:

235483,1970.01.01 00:03:55.483,ERROR,SC-FW,No module on CAN1!

and this

236882,1970.01.01 00:03:56.882,INFO,SC-FW,Model: unknow
237180,1970.01.01 00:03:57.180,ERROR,SC-FW,Cannot detect any Linear Module!

How should these be interpreted?

That you need to contact support. These logs are for their benefit when analyzing.

And on the topic of “Contact Support” how does one do that?

Email, Forum, Phone, Create a ticket?

Every time I follow a link to “Support” for Snapmaker 2.0 I end up in THIS forum.

This is one of the few product websites that the Firmware downloads are on a forum.
I was under the impression this WAS “support”.

support@snapmaker.com

You can also:

  1. Click on the Support link at the top of this page.
  2. Got to the bottom of Support page.
  3. Click on the blue Submit a request button.
  4. Follow the prompts in the zendesk popup in the lower left corner of your browser.
1 Like

Thank you. That was extremely helpfull.

When I get to that Support page I always make the mistake of clicking on my specific machine.

Phil.

I had exactly the same issue, no Y modules found. Even though its works fine on lower firmware versions.
Support told me to swap over the two splice modules ( the little box both linear modules plug into then splice to the controller) So basically swap all three cables over on each module from one to the other. This fixed mine right away and now works great on V1.14.2.
I still don’t understand why this worked because it was working fine on V1.13.2 and worked fine when I down graded back to that version. It is just something to do with V1.14.# firmware’s

They are working on code to prevent damage to the machine when a user makes an assembly mistake. On top of that, some hardware may be faulty, which these changes also detect.

The bottom line is, you should contact Support if you have an issue. Going back to a previous version may work, but it does mean that there is something wrong with your machine (assembly and/or hardware failure).

1 Like

OK. My issue is resolved.

There are 2 CAN Bus junction boxes in the base of the machine.

On one of these, there was a “partially” inserted cable (on the 2-connector side).
I assume this cable was used to determine an end stop, and was not working.

So the Rev 1.12 and 1.13 firmware was ignorant-of or ignoring this problem, whereas the 1.14 firmware saw this as a safety issue and inhibited the machine from moving.

In my case the solution was locating the loose connector and firmly inserting it.

For me, the real issue here was that bumping the Firmware rev took my machine from working to not working.


 Some friendly suggestions for the Snapmaker Programmers:

  1. I do think that there should have been some on-screen indication of the problem, rather than simply not moving.

  2. Possibly a non fatal “Warning” would have been more user-friendly since the machine has been working fine for several months without the connection.

  3. Since this is a pretty major change in machine operation, I think it should have been mentioned in the Firmware change log. (both the fact that new modules were being checked, and that a missing one can cause a system shutdown). Only a bad machine ID is mentioned in the change log

Also a question: Is downloaded 1.14.2 really 1.14.1 in the log? Is this a 1 vs. 0 issue?

.

Support helped me as soon as i sent them the log they asked for, don’t know how they read the numbers but they were right the system will not do anything until the diagnoses of the connections are correct. after rechecking the cables it worked instantly