A350 not detecting modules

Snapmaker 2.0 Getting Started
1

Hi there, I have an A350 with the following

Hardware:

  • 1.6w laser module
  • Single head print module
  • CNC module
  • Enclosure
  • 4 axis cnc rotary
  • Air purifier
  • E-stop (not currently connected due to no free can bus ports)

Software:

  • Firmware file version 1.20.3
  • Touchscreen Version 1.19.1
  • Controller Version 4.7.2

After attaching the 4 axis cnc rotary (also the first time I installed the CNC module), the enclosure stopped being detected.

I have the enclosure plugged into Add on 3 as described in the manual.

Other strange things I have noticed.
Even when my heated bed is not attached, the printer is reporting the heated bed is attached.

Should I try downgrading my firmware? Has anyone else seen an issue like this?
I see a few other threads about enclosure not being detected but none seem actionable/suggested installing beta firmware that is years old.

Things I have tried:

  • Downgrading to firmware 1.18.2
  • Upgrading back to 1.20.3
  • Swapping the ports on the enclosure and air purifier
  • Disconnecting hall sensors on enclosure (someone in an old thread said bad hall sensors might cause the enclosure not to be detected).

Edit: Logs attached (semi redacted):
FW_0.log.doc (279.7 KB)
SC_0.log.doc (983.1 KB)

2

Hey, I would suggest to reinstall the same firmware, maybe with no toolhead connected, maybe only with cnc connected.

You surely know to connect the toolheads while the machine is powered off?

Its hard to tell, sometimes this sort of firmware glitch appears, after figuring around it starts to work at some point…

May you share your logs over a fileshare or something else?

3

Hi Chris, thank you for the response.

Yes cables have only been unplugged when the machine is off.
I attached my logs to the initial post just now, and listed exactly which firmwares I have tried to upgrade and downgrade.

Attempting a reinstall without a toolhead connected now.

4

It seems your cnc toolhead was not properly detected, check connections?

5

20240923_143326
20240923_1433261920×2560 354 KB

I have no idea why, but that 4th firmware install (1.20.3 to 1.20.3) seems to have done it after a power cycle.

(I did do that reinstall without the toolhead connected, maybe that was the trick)

I don’t know if that was the solution but I’m going to mark it as such since things are working again. I’m a little afraid to change out any modules after this.

6

Generally when updating firmware you should do it with the module attached, but when you change to a new module later, re-check the FW is up to date.

7

I think the problem comes from the module upgrading routine. If you connect a (new) module the first time, even if it’s old, it upgrades the module firmware.
If you connect more than one (new) module it seems faulty.
I will forward this to the firmware developers.

Glad it helped you!