Hello.
I've got my ACE2Pro from Kobra X combo (flashed to 1.1.31 fw version already), so I do not have an Anycubic cable with usb-rs485 (ch343-based) converter.
I'm trying to connect my ACE2Pro using ordinary usb-rs485 (ch340-based) converter, I can see an ACE2Pro in Snapmaker's cli, it's name is:
/dev/serial/by-path/platform-fed00000.usb-usb-0:1.3.3:1.0-port0
And I can verify connectivity via my PC (I can see that ACE2Pro is connected and can update it's status in test .py script).
But I can't get it working with U1_1.4.1-paxx12-19_multiACE0.97.3b firmware, always getting "Error [multiACE] USB unstable, expected 2 ACEs, found 1 - ACE inactive, Klipper continues. FIRMWARE_RESTART required after reconnecting"
My ch340-based adapter has PID&VID=1a86:7523, and looks like MultiACE is hard-coded to PID&VID=%Anycubic ch343-based cable%. Can it be changed to use any ch340-based adapters?
Hello.
I've got my ACE2Pro from Kobra X combo (flashed to 1.1.31 fw version already), so I do not have an Anycubic cable with usb-rs485 (ch343-based) converter.
I'm trying to connect my ACE2Pro using ordinary usb-rs485 (ch340-based) converter, I can see an ACE2Pro in Snapmaker's cli, it's name is:
/dev/serial/by-path/platform-fed00000.usb-usb-0:1.3.3:1.0-port0
And I can verify connectivity via my PC (I can see that ACE2Pro is connected and can update it's status in test .py script).
But I can't get it working with U1_1.4.1-paxx12-19_multiACE0.97.3b firmware, always getting "Error [multiACE] USB unstable, expected 2 ACEs, found 1 - ACE inactive, Klipper continues. FIRMWARE_RESTART required after reconnecting"
My ch340-based adapter has PID&VID=1a86:7523, and looks like MultiACE is hard-coded to PID&VID=%Anycubic ch343-based cable%. Can it be changed to use any ch340-based adapters?