Octoprint 1.4.1

[rmhalvorsen]

Upgrading to octoprint 1.4.1 breaks usb connection, cannot connect to printer (Finder2.0) anymore.

Connection State: Offline (Error: No more candidates to test, and no working port/baudrate combination detected.)

[brendanm720]

I can confirm that this has broken the plugin. Here's the console readout.

It doesn't matter what I change the baud rate to.

Changing monitoring state from "Error: No more candidates to test, and no working port/baudrate combination detected." to "Offline (Error: No more candidates to test, and no working port/baudrate combination detected.)"

[brendanm720]

I'm probably going to downgrade back to my original version.

[brendanm720]

I finally got the Serial on the Finder 2.0 to work again with OctoPrint 1.3.12 and OctoPrint-Flashforge 0.1.17.

0.1.18 and 0.1.19 seemed to connect to the serial but it returned the results of the commands as bytes which something was not expecting. Please see the attached log for more info.

serial.log.2020-08-07_15-01-17.log

[TheMagicDick]

Ditto on the connection problem on 1.4.2.

I did get it to work again be rolling back to octoprint 1.3.12 and octoprint-flashforge 1.17

I also had to disconnect my printer from my polar cloud. I going to try to solve that by using the polar cloud plugin that also only works on older octoprint versions

[Mrnt]

Sorry for the delay in responding, have been busy. Will take a look.

[trejan]

Fix is at https://github.com/Mrnt/OctoPrint-FlashForge/pull/38

[Mrnt]

Thank you @trejan for doing this - merged into a new release.

@TheMagicDick @brendanm720 @rmhalvorsen Please try with ver 0.1.21

[geirme]

I tried to upgrade to 1.4.2 now after first updating the FlashForge plugin from 0.1.19 to 0.1.20

First the installation of the plugin failed with the message "TabError: inconsistent use of tabs and spaces in indentation" While trying to dive into the init.py file to se if any tabs should be replaced with white spaces instead suddenly i found a new update, versjon 0.1.21 and tried that one.

Magic then happened and it all works perfect now. I also finally get the autoconnect feature introduced in 1.4.1 working so when starting up octoprint it now automatically connects to my FlasForge (Finder 2.0) printer directly!

(I can now happly go to bed as the clock has passed 03:00 AM...)

[trejan]

Sorry. The tab/spaces was my mistake. Mrnt's version should be fixed now.

[geirme]

That explains the sudden raise in version number. Well, it seems to be working fine!

[eduncan911]

New install (on an x86 device, no RPi). First time using OctoPrint, and this plugin!

• Dremel 3D20
• OctoPrint 1.4.2 (per About screen)
• OctoPrint-FlashForge 0.1.21 (per Manage Plugins version)
• Ubuntu 20.04

Wiped and installed twice now; however, same error as OP.

I haven't connected the printer to this device yet though. If there's something I can do to check to see if it's working, let me know. I did find the following:

$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0424:2530 Microchip Technology, Inc. (formerly SMSC) BOSCH Dremel 3D Printer
Bus 001 Device 002: ID 0424:4603 Microchip Technology, Inc. (formerly SMSC)
Bus 001 Device 004: ID 2a89:8889 BOSCH BOSCH Dremel 3D Printer

Yep, that's all this device has connected via USB. ;)

I am installing per README, and followed the master zip file approach, as well as just searching Get more and installing that way.

Should I be specifying individual tags to download from within the Plugin Manager?

EDIT:

Nevermind! Looks like this was a number of permissions issues, unrelated to this thread.

[Mrnt]

@brendanm720 @TheMagicDick @trejan @geirme @rmhalvorsen closing as it should now be fixed..