Failing to connect to the m3d micro+

[LeonFedotov]

Hello ive just got the micro+ and it works with their native windows app, the mac app is stuck on loading and M33 Fio is stuck at connecting.
is the micro+ using some other communication mechanism?
this is the terminal output, it seems like its stuck on detection?

Changing monitoring state from 'Offline' to 'Detecting serial port'
Connecting to: /dev/ttyACM0
Changing monitoring state from 'Detecting serial port' to 'Opening serial port'
Connected to: Serial<id=0x6c420a10, open=True>(port='/dev/ttyACM0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=None, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Starting baud rate detection
Changing monitoring state from 'Opening serial port' to 'Detecting baudrate'
Trying baudrate: 115200
Changing monitoring state from 'Detecting baudrate' to 'Offline'
Recv: ?

[donovan6000]

M33 Fio isn't compatible with Micro+ or M3D Pro printers.

[LeonFedotov]

@donovan6000 oh I see -_-
is it drastically different? can i help getting support?

[donovan6000]

I don't own or plan on buying a Micro+ printer, so I probably won't add support for it in M33 Fio. Here's a general overview of what needs to be done to support for Micro+ or M3D Pro printer if anyone's interested in doing so

[LeonFedotov]

@donovan6000 great, thanks for the info.

[ktrolin]

First of all, I really appreciate your work @donovan6000 & @foosel you guys are true philanthropists :)
Secondly, it might be obvious, but is it possible to connect the M3D micro+ as a default printer in octoprint (and not use the M33 Fio)?

[donovan6000]

@ktrolin The Micro 3D and Micro+ printers use repetier host protocol to receive G-code commands, so they won't work in OctoPrint by default. It is possible to use the Micro 3D printer with OctoPrint without using M33 Fio by installing a different firmware onto it.

The M3D Pro printer uses standard G-code protocol to receive G-code commands, so it can work in OctoPrint without any plugins. However the M3D Pro's firmware doesn't have builtin backlash compensation, so anything printed to it would be skewed.