try it on 1.13.2 firmware. if it is then settled. Does the LED on the large controller light up? is near the usb c port at me the led is breathing.
is the log file copied to the USB stick?
The following can be found in the log after updating!
34524,1970.01.01 00:00:34.524,INFO,SC,Application started!
34526,1970.01.01 00:00:34.526,DEBUG,SC,Build SDK version: 25
34531,1970.01.01 00:00:34.531,DEBUG,SC,FabScreen version: V1.13.2
34594,1970.01.01 00:00:34.594,DEBUG,SC,Reset overrides.
34647,1970.01.01 00:00:34.647,INFO,SC,SessionManager, load sessions...done
35132,1970.01.01 00:00:35.132,INFO,SC,Connecting serial port...
35169,1970.01.01 00:00:35.169,DEBUG,SC,Requesting module info...
35180,1970.01.01 00:00:35.180,DEBUG,SC,Machine model 3, size x 345 y 357 z 334
35182,1970.01.01 00:00:35.182,INFO,SC,onConnection, connected = true
35184,1970.01.01 00:00:35.184,INFO,SC,Enable heartbeat.
35192,1970.01.01 00:00:35.192,DEBUG,SC,HTTP server started.
35197,1970.01.01 00:00:35.197,WARN,SC,Module 0x03 version (v1.10.3 ) is invalid!
35215,1970.01.01 00:00:35.215,WARN,SC,Module 0x03 version (v1.10.3 ) is invalid!
35229,1970.01.01 00:00:35.229,WARN,SC,Module 0x05 version (v1.10.3 ) is invalid!
35236,1970.01.01 00:00:35.236,WARN,SC,Module 0x02 version (v1.10.3 ) is invalid!
35240,1970.01.01 00:00:35.240,WARN,SC,Module 0x03 version (v1.10.3 ) is invalid!
35245,1970.01.01 00:00:35.245,WARN,SC,Module 0x03 version (v1.10.3 ) is invalid!
35269,1970.01.01 00:00:35.269,DEBUG,SC,Set Enclosure lighting true
36205,1970.01.01 00:00:36.205,DEBUG,SC,Head type 3 found.
36343,1970.01.01 00:00:36.343,DEBUG,SC,Route: Create HomeFragment
36348,1970.01.01 00:00:36.348,DEBUG,SC,Route: Create LauncherFragment
36437,1970.01.01 00:00:36.437,DEBUG,SC,Laser Camera status true,A4:E5:7C:4A:23:9A
37014,1970.01.01 00:00:37.014,DEBUG,SC,Laser camera connected takes 540ms
37021,1970.01.01 00:00:37.021,DEBUG,SC,Laser Camera connected!
39573,1970.01.01 00:00:39.573,DEBUG,SC,NetworkManager: found Wi-Fi configuration #0 "Mc-net", state = ENABLED.
40476,1970.01.01 00:00:40.476,DEBUG,SC,Route: Create ControlLaserFragment
41005,1970.01.01 00:00:41.005,INFO,SC,update coordinate system...
41018,1970.01.01 00:00:41.018,INFO,SC,Coordinate system updated, CS#0 X = 0.0, Y = 0.0, Z =0.0
1646850628442,2022.03.09 18:30:28.442,DEBUG,SC,NetworkManager: found Wi-Fi configuration #0 "Mc-net", state = CURRENT.
1646850628444,2022.03.09 18:30:28.444,DEBUG,SC,NetworkManager: current Wi-Fi configuration is #0 "Mc-net"
1646850628459,2022.03.09 18:30:28.459,DEBUG,SC,Wi-Fi connected.
1646850628463,2022.03.09 18:30:28.463,DEBUG,SC,Start checking new versionā¦
1646850637102,2022.03.09 18:30:37.102,INFO,SC,update coordinate system...
1646850637120,2022.03.09 18:30:37.120,INFO,SC,Coordinate system updated, CS#0 X = 0.0, Y = 0.0, Z =0.0
1646850637122,2022.03.09 18:30:37.122,INFO,SC,update coordinate system... CS#1
1646850637182,2022.03.09 18:30:37.182,INFO,SC,Coordinate system updated, CS#1 X = 19.0, Y = 0.0, Z =0.0
1646850680064,2022.03.09 18:31:20.064,INFO,SC,Requesting G28...
1646850680067,2022.03.09 18:31:20.067,INFO,SC,update coordinate system... CS#0
1646850680107,2022.03.09 18:31:20.107,INFO,SC,Coordinate system updated, CS#0 X = 0.0, Y = 0.0, Z =0.0
1646850689411,2022.03.09 18:31:29.411,INFO,SC,update coordinate system... CS#1
1646850689457,2022.03.09 18:31:29.457,INFO,SC,Coordinate system updated, CS#1 X = 19.0, Y = 0.0, Z =0.0
37000,1970.01.01 00:00:37.000,INFO,SC,Application started!
37003,1970.01.01 00:00:37.003,DEBUG,SC,Build SDK version: 25
37005,1970.01.01 00:00:37.005,DEBUG,SC,FabScreen version: V1.13.2
37074,1970.01.01 00:00:37.074,DEBUG,SC,Reset overrides.
37123,1970.01.01 00:00:37.123,INFO,SC,SessionManager, load sessions...done
37730,1970.01.01 00:00:37.730,INFO,SC,Connecting serial port...
37774,1970.01.01 00:00:37.774,DEBUG,SC,Requesting module info...
37782,1970.01.01 00:00:37.782,INFO,SC,onConnection, connected = true
37784,1970.01.01 00:00:37.784,INFO,SC,Enable heartbeat.
37807,1970.01.01 00:00:37.807,DEBUG,SC,Machine model 3, size x 345 y 357 z 334
37816,1970.01.01 00:00:37.816,WARN,SC,Module 0x03 version (v1.10.3 ) is invalid!
Which module has 0x03?
Edited your log for better reading, use three backticks at the beginning and ending of code sections in the future. ```
This are your linear modules and tool head.
Did you read the article which brent serve?
Check your cabling and change like its described.
Do we think an update with Brentās inline power move update might be incoming sometime in the near future? I see that the pull request was merged with the main branch in January, and seeing that go live would be AWESOME. Thanks all!
@brent113 my understanding is that your laser inline code was implemented in the last firmware release but the touchscreen breaks running the laser over serial. Is that correct?
Itās not yet been released, just missed the 1.14.2 release date
If you build from Github include the pending pull request from @nivekmai as there are issues with the 10W laser
1 Like
Hmm, I should probably post the built firmware with my PR in here, will try to do that tomorrow when Iām back near a computer.
1 Like
After a job is completed, the machine attempts to start it again, repeating endlessly unless cancelled!
Have you been able to check if Laser Inline Power control is in the latest release?
I did a test, it is not in the latest release. So apparently theyāre still building with a private repo and not the public one, so any changes are not the same between the two.
I think I may have received a controller board with wrong firmware. Is there a way to flash it without using the touch screen?
Iāve been in contact with support, but thought Iād ping the firmware people here. When the new controller boots up, the led is slowly blinking, but neither the touch screen or Luban can connect. When I hook up a serial terminal to the micro USB link, it receives the text āHello world!ā repeatedly. Seems like maybe a demo firmware for the included MCU.
I searched around for an āunbrickā procedure, or something of that nature, but havenāt found it yet. I donāt have a JTAG programmer, but I could go the VSCode / PlatformIO route if necessary. But reading the github page makes it seem like even that path requires the touch screen to pull your firmware bin off usb and flash it. I canāt get the touch screen past its fail to connect error.
If you have a bad firmware flash, there is nothing that we can do to help. Only Support will be able to help you. They will most likely need to send you new device(s) (i.e. Controller and/or TouchPad).
Yes, but it requires soldering or otherwise attaching a programmer to the chip, going through an unlock procedure, and then reloading the bootloader using a binary dump. Itās not easy at all and requires familiarity with chip programmers.
I agree with @CNC-Maker you should work through support.
I too am having issues with the 10W on SMA350, whereby you go through every step from Snapmaker luban design to laser engraving, but the Setpoint isnāt remembered by machine and so when printing, it moves the head all the way to top right of platform to start engraving in one spot. whats that about?
I am currently having trouble with a currently running firmware update to v1.14.3 on my A350 this is my first firmware update and it seems to be stuck a what i can only guess as file number 977 and 1% of progress been like this for 30mins. Is this something i should be worried about?
Does Fade Height work now on the older A350?
Oh I was to quick with the new update!
Installed new firmware Snapmaker2_V1.15.11 an hour ago and now my A350 is in an update loop and I can not get out of it. Does anyone of you the same problem? It is updating the controller and the printing module and then it is starting all over again. Turning it off and on again results in the same loop. Am I the first to install this?
1 Like
@Alan Is the github repo still in sync with the latest update? I have some custom firmware modifications Iāve done and would like to rebase onto the top of the git repo, but Iām wary of losing features.
2 Likes