Open Vuego123 opened 2 years ago
scotthsl
commented
2 years ago Hi @Vuego123, Thank you for your feedback, and I am sorry to reply you so late, I have given this question to our support team and try to make our test team to reproduce this issue. Want to confirm if you still suffer this problem now?
Vuego123
commented
2 years ago Yes, the problem is still occurring.
I have made 2 videos of my problem:
Links to video:
All other settings, hardware setup and cabling... is the same in both videos. So only the firmware is different.
My machine settings:
I have been using my machine for 1 year without any problems.
I have done the following tests, without any luck:
unplugged enclosure
unplugged emergency button
switched linear rails between X, Y and Z
WIFI installation of v14.2
USB installation of both v14.2 and v14.1
switched between CNC, 3D print and laser modules
When I downgrade back to v13.2 everything works, however, I can't use the 10W laser with v13.2.
Your support team can give me extra instructions to test things if that helps to find the root cause. Please let me know if you need any logs from my machine.
I noticed other customers are complaining about the same problem (on facebook, github and snapmaker forum).
WennnnnT
commented
2 years ago Hello, may I ask whether there is a mixture of 2.5 generation and 2.0 generation modules on your machine? You can check the label information on the linear module, which is labeled 2.5 (second generation) and 2.0 (first generation) information. Although they are 8 lead, they are not compatible. Unsupported on V1.14.2
Vuego123
commented
2 years ago Where can I find the label information?
I can't find a label that is physically present on the linear modules. Do I need to look in the logs or in a menu on the touch screen?
Vuego123
commented
2 years ago Below you can find an extract of my bootlog. First the log states that it has found my X, Y and Z axis. Finally at the very bottom it says "Cannot detect any Linear Module!". That does not seem like it should be.
others < Scanning modules ... others < New Module: 0x20395ABC others < Module 0x00395ABC: v1.11.5 others < Got axis Z, endstop: 0 others < length: 356 mm, lead: 8 mm others < Function [ 0] <-> Message [ 3] others < New Module: 0x2000E304 others < Module 0x0000E304: v1.11.5 others < Got toolhead 3DP! others < Function [ 8] <-> Message [ 18] others < Function [ 9] <-> Message [ 19] others < Function [ 6] <-> Message [ 20] others < Function [ 7] <-> Message [ 21] others < Function [ 1] <-> Message [ 4] others < Function [ 10] <-> Message [ 22] others < Function [ 2] <-> Message [ 5] others < Function [ 16] <-> Message [ 23] others < probe: 0x1, filament: 0x1 others < set min_planner_speed:0.05 others < New Module: 0x00802FD2 others < Module 0x00802FD2: v1.11.5 others < Got EmergencyStop Module! others < Function [ 20] <-> Message [ 0] others < New Module: 0x203854AA others < Module 0x003854AA: v1.11.5 others < Got axis X, endstop: 0 others < length: 356 mm, lead: 8 mm others < Function [ 0] <-> Message [ 6] others < New Module: 0x00507AA0 others < Module 0x00507AA0: v1.11.5 others < Got Enclosure! others < Function [ 15] <-> Message [ 7] others < Function [ 18] <-> Message [ 24] others < Function [ 19] <-> Message [ 25] others < New Module: 0x20392112 others < Module 0x00392112: v1.11.5 others < Got axis Y, endstop: 0 others < length: 356 mm, lead: 8 mm others < Function [ 0] <-> Message [ 8] others < New Module: 0x20395C48 others < Module 0x00395C48: v1.11.5 others < Got axis Y, endstop: 0 others < length: 356 mm, lead: 8 mm others < Function [ 0] <-> Message [ 9] others < axis index:0 pitch:400.00 others < axis index:1 pitch:400.00 others < axis index:2 pitch:400.00 others < Model: unknow others < grid manual others < Cannot detect any Linear Module!
scotthsl
commented
2 years ago Hi @Vuego123 , Thanks for your feedback, from your bootlog I found a missing z-axis, is the machine missing a z-axis every time when it boots under v1.14.2? Also can you provide the bootlog for v1.13.2?
Thanks Scott
Vuego123
commented
2 years ago Bootlog for firmware v1.13.2 with exact same hardware setup:
M502
others < leveling OFF
echo:Hardcoded Default Settings Loaded
ok
M500
echo:Settings Stored (1064 bytes; crc 861)
ok
echo:Unknown command: "M1012"
M1999
others < will reboot machine
ok
echo:PowerUp
others < echo:Compiled: Sep 13 2021
echo: Last Updated: 2021-09-13 | Author: Snapmaker Team
echo:Compiled: Sep 13 2021
echo: Free Memory: 24543 PlannerBufferBytes: 1792
echo:V71 stored settings retrieved (1064 bytes; crc 861)
echo: G21 ; (mm)
echo:Filament settings: Disabled
echo: M200 D3.00
echo: M200 D0
echo:Steps per unit:
echo: M92 X400.00 Y400.00 Z400.00 E212.21
echo:Maximum feedrates (units/s):
echo: M203 X120.00 Y120.00 Z40.00 E25.00
echo:Maximum Acceleration (units/s2):
echo: M201 X3000.00 Y3000.00 Z100.00 E10000.00
echo:Acceleration (units/s2): P
Vuego123
commented
2 years ago 1 linear rail module is always missing in the bootlog. However with firmware v1.13.2 that does not seem to be a problem.
scotthsl
commented
2 years ago Hi @Vuego123 , Per your bootlogs from two version, I doubt that one of your Z-axes is not working properly, please contact our support team (support@snapmaker.com), they will assist you in troubleshooting and resolving the problem.
Thanks Scott
Rolzad73
commented
2 years ago I had re-setup my machine (A350 from the Kickstarter) about a month ago for 3D printing. The first thing I did was upgrade the firmware to the latest (v1.14.2) since it had been so long since I had used the machine.
Printing has been going fine up until today, when the Z axis stopped moving up in the middle of the print, jamming the PLA into itself. It then started moving up and down on Z axis about 5mm, in a bit of a fit. I hit the power switch at that point (not E-stop).
After I restarted the machine, I could get no movement on the device, no homing, no jog. I then took apart the machine, leaving the rails installed, and plugged in, but X-axis separated to see if it was a hardware issue. No movement. In my research I tried factory resetting and eventually came to this issue #218
I decided to downgrade the firmware to v1.13.2, and after rebooting the machine I could get homing and jogging again. I am now going through the calibration, etc. I expect to be printing again in a few minutes.
I have no logs to compare to help with the issue, because collecting the logs was causing reboots on the device before I upgraded.
Ingo-on-Github
commented
2 years ago Hi @Vuego123, could you resolve it? My 350 suddenly stopped working after I switched the 10W laser back to CNC. Had to downgrade from 14.2 (which shows the missing linear modules in the bootlog) to 13.2 and everything is fine again. Which somehow rules out a hardware issue. Going back to 14.1 and nothing moved again. Keen to hear how it played out for you?
karmavore
commented
2 years ago I'm having this exact same problem with my kickstarter A250. No linear motors or extruder motor were working under 14.1 and 14.2. I just reflashed 13.2 and its working fine again. This seems like a serious firmware issue.
Ingo-on-Github
commented
2 years ago @karmavore I received valuable guidance from the Snapmaker support team after I sent them the bootlogs of 13.2 (alive) and 14.2 (dead). The difference is that 14.2 will drop dead if one of the linear modules is failing. Whereas 13.2 will use all the linear modules still alive. In my case the cable of the right linear Z-module was lose (I guess I touched it as I vacuumed after a CNC job). The left linear module still worked and dragged the right module along. Once I was aware of this I could actually see the dragging with somewhat stuttering movement. After I fixed the cable - fortunately both Z-linear modules were still working fine - 14.2 is happy again.
So I would argue, that 14.2 has a better protection of the linear modules than 13.2 as it prevents a single linear module working for both (which can't be good if happening for an extended time). It would be much better, if the firmware would call out the missing linear module to direct the user to the root cause. The support person will pass this suggestion on the the technical team and request an update for the FAQ.
I hope this helps.
niksbha
commented
2 years ago Hii having the same problem with a new machine. Model A250T. after startup I get a direct update for firmware 1.14.2. and then the thing happned.
Ingo-on-Github
commented
2 years ago @niksbha: looks like one of your double-modules doesn't work. I hope checking the cables will help. Otherwise I would try to physically decouple the double modules (by removing the bed and the horizontal module and check who is moving under 13.2.
niksbha
commented
2 years ago yes, it might be the problem... currently, I have a downgrade firmware to 1.13.2 and start the machine. the auto home happens and the machine's z and x-axis move halfway then stop. also can't move any axis manually with the controller display toggle button.
suspect: Y-axis is not moved a once may be.
I don't know how to Bootlog to know if the axis is connected or not.
Ingo-on-Github
commented
2 years ago @niksbha connect Luban via USB cable and fire a M1999 command in the console.
niksbha
commented
2 years ago okay, thank you for your support.
The problem is almost solved by interchanging the dual cable splitter.
now all axis are moving by toggle, current firmware is 1.13.2
kubarbaz
commented
2 years ago Also same problem, broken Z axis. Is there a fix or do I have to buy a new one? I wouldn't know until this point if it was broken or not
karmavore
commented
2 years ago Yes, I had my bed misalign/"jump" whenever both were plugged in, so for the y axis I had one of the modules unplugged, and crazy enough with the older firmware it worked fine for 3d printing. This is why 14.2 would never run in my particular case, as 1 y-axis actuator was unplugged. After my x-axis started failing as well last month, I just caved and bought the new upgraded linear actuator bundle. They're so quiet, it's ridiculous and very smooth movement. I wish my snapmaker had shipped with the nicer actuators in the first place. Sad there isn't a buyback program, I have 5 original actuators now collecting dust.
On Fri, Jun 3, 2022 at 3:36 AM Ingo-on-Github @.***> wrote:
@karmavore https://github.com/karmavore I did received valuable guidance from the Snapmaker support team. The difference is that 14.2 will drop dead if one of the linear modules is failing. Whereas 13.2 will use all the linear modules still alive. In my case the cable of the right linear Z-module was lose (I guess I touched it as I vacuumed after a CNC job). The left linear module still worked and dragged the left module along. Once I was aware of this I could actually see the dragging somewhat stuttering movement. After I fixed the cable - fortunately both Z-linear modules were still working fine - 14.2 is happy again.
So I would argue, that 14.2 has a better protection of the linear modules than 13.2 as it prevents a single linear module working for both (which can't be good if happening for an extended time). It would be much better, if the firmware would call out the missing linear module to direct the user to the root cause. The support person will pass this suggestion on the the technical team and request an update for the FAQ.
I hope this helps.
— Reply to this email directly, view it on GitHub https://github.com/Snapmaker/Snapmaker2-Controller/issues/218#issuecomment-1145732492, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABM2KBJ2QYUMRNQ4Z762K5DVNG7Y3ANCNFSM5NYYTXNA . You are receiving this because you were mentioned.Message ID: @.***>
mhd-321
commented
1 year ago Any update on this issue other than downgrading? I'm facing the same problem...
karmavore
commented
1 year ago I completely replaced the linear actuators with a fully new set from Snapmaker (few hundred $$$) however I now have my complete original set sitting unused. 3 or 4 of these should be completely fine if you want to buy them from me. Venmo/offerup
On Tue, Oct 25, 2022, 5:42 PM mhd-321 @.***> wrote:
Any update on this issue other than downgrading? I'm facing the same problem...
— Reply to this email directly, view it on GitHub https://github.com/Snapmaker/Snapmaker2-Controller/issues/218#issuecomment-1291216748, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABM2KBJRCK2Q3NQOAO2PHPLWFBO4VANCNFSM5NYYTXNA . You are receiving this because you were mentioned.Message ID: @.***>
Rolzad73
commented
1 year ago I completely replaced the linear actuators with a fully new set from Snapmaker (few hundred $$$) however I now have my complete original set sitting unused. 3 or 4 of these should be completely fine if you want to buy them from me. Venmo/offerup … On Tue, Oct 25, 2022, 5:42 PM mhd-321 @.> wrote: Any update on this issue other than downgrading? I'm facing the same problem... — Reply to this email directly, view it on GitHub <#218 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABM2KBJRCK2Q3NQOAO2PHPLWFBO4VANCNFSM5NYYTXNA . You are receiving this because you were mentioned.Message ID: @.>
-reply to a reply-
I ended up doing the same thing. bought a new 2.0 set. They are a bit different though that the Z rails (up/down) are different and need to be placed in their correct position or again nothing will work with no indication why. It was my fault though for thinking they were all the same (and not reading the instructions)
In the end it works even though it cost $$. But I still do have my old 5 set (1 broken) that I THINK they could still be used for non-Z rails as replacements if anything goes wrong, but I haven't tested that theory.
In closing, it might be a good idea to have messaging or verbose logging that end-users can read easily to diagnose problems like this instead of just failing quietly as it does now.
Is anyone else having a problem with a moving the module after upgrading to v14.1 or v14.2 ?
After upgrading to v14.1 > system restarts, but none of the axis can move. Not via manually jogging and not via the homing function. I downgraded back to firmware v13.2 and everything works again.
A while later, I received the new 10W laser module and decided to upgrade to v14.2 > same problem occurs.
I found this youtube video from a user who is experiencing the same issue: https://www.youtube.com/watch?v=_nYk0uMm43o