Skip to main content
Discussion Topic
User avatar

SnapMaker 2.0 Connection Errors

I’ve read a few posts on here from fellow snapmaker users and As a snapmaker 2.0 user myself, and an embedded developer, I can say that connected mode does not work with the snapmaker 2.0 A or AT series printers. The issue isn’t with the OS or Docker though, it’s the connection through NodeJS and the associated code. I’m looking into a fix for this myself, but if someone else beats me to is, Here’s the error below. I can provide whatever info is needed to help troubleshoot this if someone wants to colab on it also. The quicker it gets fixed the better in my opinion, it is afterall listed as a supported printer….

New Request: connect

--category: job

--origin: simcoe

trying: /dev/ttyUSB0 115200

Opening Serial, port: /dev/ttyUSB0, baud: 115200.

err Error

at /app/src/printer/actions/temperature/getTemperature.js:53:23

at /app/src/printer/controller/PrinterController.js:82:20

at errorListener (/app/node_modules/citra/Citra.js:98:5)

at Timeout.<anonymous> (/app/node_modules/citra/Citra.js:103:5)

at listOnTimeout (node:internal/timers:557:17)

at processTimers (node:internal/timers:500:7) {

status: 500,

info: 'Did not receive desired response.'

}

Reply to discussion Subscribe to discussion

Is this a worthwhile discussion?

Score 7
Add a comment

7 Replies

Most Helpful Answer
User avatar

Ok, So I spent the afternoon debugging this and was able to get it connected to the snapmaker 2.0 A350T here’s the connection output below. Temp and all the controls work now. I used a workaround to get this up and running, but I don’t think it’s a good “permanent” fix. Also, that isn’t my job after paying $$$ for this thing, but here’s the thing you couldn’t fix for the last….however long. So that’s where you come in Mosaic, I showed you the issue, please release an update to address this for all the Snapmaker Users (while I enjoy printing in connected mode now).

The issue is for some reason, the controller.sendAndListen function returns an error even when it’s successful. I got this working by removing the else from the ‘else if’ statement at /app/src/printer/actions/temperature/getTemperature.js:58 so that even if there is an error, as long as data is present it’s still returned. The error so far hasn’t affected anything but connection. It may even be timeout related, I admittedly didn’t look that far into it. After staring at code all day for my job and then this, I’m a little burnt.

Started Apollo Server!

New Request: state

--category: get

--origin: simcoe

New Request: connect

--category: job

--origin: simcoe

trying: /dev/ttyUSB0 115200

Opening Serial, port: /dev/ttyUSB0, baud: 115200.

T:28.10 /0.00 B:20.62 /0.00 @:0 B@:0

T:28.10 /0.00 B:20.62 /0.00 @:0 B@:0

ok

ok

getting autoreport temp cap..

FIRMWARE_NAME:Marlin SM2-4.4.16 (Github) SOURCE_CODE_URL:https://github.com/whimsycwd/SnapmakerMa... PROTOCOL_VERSION:1.0 MACHINE_TYPE:GD32F305VGT6 EXTRUDER_COUNT:1 UUID:cede2a2f-41a2-4748-9b12-c55c62f367ff

FIRMWARE_NAME:Marlin SM2-4.4.16 (Github) SOURCE_CODE_URL:https://github.com/whimsycwd/SnapmakerMa... PROTOCOL_VERSION:1.0 MACHINE_TYPE:GD32F305VGT6 EXTRUDER_COUNT:1 UUID:cede2a2f-41a2-4748-9b12-c55c62f367ff

Cap:SERIAL_XON_XOFF:0

Cap:SERIAL_XON_XOFF:0

Cap:BINARY_FILE_TRANSFER:0

Cap:EEPROM:1

Cap:BINARY_FILE_TRANSFER:0

Cap:EEPROM:1

Cap:VOLUMETRIC:1

Cap:VOLUMETRIC:1

Cap:AUTOREPORT_TEMP:1

got cap! [ 'AUTOREPORT_TEMP', true ]

got true

lets autoreport temp yo

Cap:AUTOREPORT_TEMP:1

Cap:PROGRESS:0

Cap:PRINT_JOB:1

constructor auto report temp true

Cap:AUTOLEVEL:0

Cap:AUTOLEVEL:0

Cap:Z_PROBE:1

Cap:LEVELING_DATA:1

Cap:BUILD_PERCENT:0

Cap:SOFTWARE_POWER:0

Cap:TOGGLE_LIGHTS:0

Cap:CASE_LIGHT_BRIGHTNESS:0

Cap:EMERGENCY_PARSER:0

Cap:PROMPT_SUPPORT:0

Cap:AUTOREPORT_SD_STATUS:0

Cap:THERMAL_PROTECTION:1

Cap:MOTION_MODES:0

Cap:CHAMBER_TEMPERATURE:0

ok

Cap:Z_PROBE:1

Cap:LEVELING_DATA:1

Cap:BUILD_PERCENT:0

Cap:SOFTWARE_POWER:0

Cap:TOGGLE_LIGHTS:0

Cap:CASE_LIGHT_BRIGHTNESS:0

Cap:EMERGENCY_PARSER:0

Cap:PROMPT_SUPPORT:0

Cap:AUTOREPORT_SD_STATUS:0

Cap:THERMAL_PROTECTION:1

Cap:MOTION_MODES:0

Cap:CHAMBER_TEMPERATURE:0

ok

ok

ok

T:29.00 /0.00 B:20.78 /0.00 @:0 B@:0

ok

T:29.00 /0.00 B:20.78 /0.00 @:0 B@:0

[ 'T:29.00', '/0.00', 'B:20.78', '/0.00', '@:0', 'B@:0' ]

ok

T:28.60 /0.00 B:20.78 /0.00 @:0 B@:0

T:28.60 /0.00 B:20.78 /0.00 @:0 B@:0

[ 'T:28.60', '/0.00', 'B:20.78', '/0.00', '@:0', 'B@:0' ]

T:28.40 /0.00 B:20.62 /0.00 @:0 B@:0

[ 'T:28.40', '/0.00', 'B:20.62', '/0.00', '@:0', 'B@:0' ]

T:28.00 /0.00 B:20.62 /0.00 @:0 B@:0

[ 'T:28.00', '/0.00', 'B:20.62', '/0.00', '@:0', 'B@:0' ]

T:28.20 /0.00 B:20.62 /0.00 @:0 B@:0

[ 'T:28.20', '/0.00', 'B:20.62', '/0.00', '@:0', 'B@:0' ]

T:28.30 /0.00 B:20.78 /0.00 @:0 B@:0

[ 'T:28.30', '/0.00', 'B:20.78', '/0.00', '@:0', 'B@:0' ]

T:28.20 /0.00 B:20.62 /0.00 @:0 B@:0

[ 'T:28.20', '/0.00', 'B:20.62', '/0.00', '@:0', 'B@:0' ]

T:28.20 /0.00 B:20.78 /0.00 @:0 B@:0

[ 'T:28.20', '/0.00', 'B:20.78', '/0.00', '@:0', 'B@:0' ]

T:28.40 /0.00 B:20.78 /0.00 @:0 B@:0

[ 'T:28.40', '/0.00', 'B:20.78', '/0.00', '@:0', 'B@:0' ]

T:28.30 /0.00 B:20.62 /0.00 @:0 B@:0

[ 'T:28.30', '/0.00', 'B:20.62', '/0.00', '@:0', 'B@:0' ]

T:28.40 /0.00 B:20.62 /0.00 @:0 B@:0

[ 'T:28.40', '/0.00', 'B:20.62', '/0.00', '@:0', 'B@:0' ]

T:28.60 /0.00 B:20.62 /0.00 @:0 B@:0

[ 'T:28.60', '/0.00', 'B:20.62', '/0.00', '@:0', 'B@:0' ]

T:28.70 /0.00 B:20.62 /0.00 @:0 B@:0

[ 'T:28.70', '/0.00', 'B:20.62', '/0.00', '@:0', 'B@:0' ]

T:28.40 /0.00 B:20.62 /0.00 @:0 B@:0

[ 'T:28.40', '/0.00', 'B:20.62', '/0.00', '@:0', 'B@:0' ]

T:28.00 /0.00 B:20.62 /0.00 @:0 B@:0

[ 'T:28.00', '/0.00', 'B:20.62', '/0.00', '@:0', 'B@:0' ]

T:28.70 /0.00 B:20.62 /0.00 @:0 B@:0

[ 'T:28.70', '/0.00', 'B:20.62', '/0.00', '@:0', 'B@:0' ]

T:28.70 /0.00 B:20.62 /0.00 @:0 B@:0

[ 'T:28.70', '/0.00', 'B:20.62', '/0.00', '@:0', 'B@:0' ]

T:28.30 /0.00 B:20.62 /0.00 @:0 B@:0

[ 'T:28.30', '/0.00', 'B:20.62', '/0.00', '@:0', 'B@:0' ]

T:28.00 /0.00 B:20.62 /0.00 @:0 B@:0

[ 'T:28.00', '/0.00', 'B:20.62', '/0.00', '@:0', 'B@:0' ]

T:28.40 /0.00 B:20.62 /0.00 @:0 B@:0

[ 'T:28.40', '/0.00', 'B:20.62', '/0.00', '@:0', 'B@:0' ]

T:28.30 /0.00 B:20.62 /0.00 @:0 B@:0

[ 'T:28.30', '/0.00', 'B:20.62', '/0.00', '@:0', 'B@:0' ]

T:28.10 /0.00 B:20.78 /0.00 @:0 B@:0

[ 'T:28.10', '/0.00', 'B:20.78', '/0.00', '@:0', 'B@:0' ]

T:28.60 /0.00 B:20.62 /0.00 @:0 B@:0

[ 'T:28.60', '/0.00', 'B:20.62', '/0.00', '@:0', 'B@:0' ]

T:28.40 /0.00 B:20.62 /0.00 @:0 B@:0

[ 'T:28.40', '/0.00', 'B:20.62', '/0.00', '@:0', 'B@:0' ]

Block Image

PS- You’re welcome!

Was this reply helpful?

Score 4

Comments:

Hi Jared,

Thank you for sharing this with the community! I will have our software team review this.

by

Thanks @hana. Testing it combined with the update that was released today and it's working well. Printing a few clownfish right now, I'll share later. Haven't had any connection issues, only splice breaks and did some tuning.

by

@hana I'm happy to test any changes the software team makes with the apollo server code if you don't have a snapmaker printer available for testing.

by

I would also be happy to test this.

by

Happy to help with testing too

by

Show 4 more comments

Add a comment
User avatar

Jared, you are a rock star, I hope they take this code and push it out to us…

Cant wait to try it out

Thank you

Was this reply helpful?

Score 2

Comments:

I second this!

by

Add a comment
User avatar

@hana Can you get this fixed in a firmware update! PLEASE!!!!!! So simple

Was this reply helpful?

Score 3

Comments:

@hana Yes please, I have a nice new shiny P3p and SM2 A350 just waiting to be friends and do some fine work together :)

by

Add a comment
User avatar

@bar_nz
They will be the best of friends when they fix that issue! Just finished this 2 day print in connected mode….Turned out great!

Block Image

Was this reply helpful?

Score 3

Comments:

UGH!!!!! @hana I want fish!!!!

by

@jallen2281 They are awesome, can wait to test this for myself, I have many projects just waiting to go :)

by

Hey @jallen2281 can you share more specifically how you get it up and running? CAn't wait for @hana ugh.... I want to use PrusaSlicer and P2PP and only works in connected mode. That way I don't have to waste so much filament I can use the fun settings there!!! :(

or @hana Can you provide timing or an update on this... come on it was handed to you!!!!

by

@jallen2281 Just joined, is there a post that shows how to connect the two together like you did or need to keep using it in accessory mode.

by

Add a comment
User avatar

Any updates from Mosaic people?

Was this reply helpful?

Score 2

Comments:

Not that I have seen :(

@hana Do we have any idea when this is going to be released to the SM users, we are all waiting and excited to get our SM-2 working with your product.

by

Add a comment
User avatar

Is this thread still monitored by Mosaic!

Was this reply helpful?

Score 0
Add a comment
User avatar

Hi everyone, we have a test firmware that will help to get Snapmaker printers work in Connected mode. If you’d like to try this firmware, please send me an e-mail at jonny@mosaicmfg.com and I can share this with you!

Was this reply helpful?

Score 3
Add a comment

Join the discussion

Author avatar Jared will be eternally grateful.
View Statistics:

Past 24 Hours: 1

Past 7 Days: 18

Past 30 Days: 68

All Time: 871

Contact Mosaic Support Team

© 2023 Mosaic Manufacturing Ltd.