Flashforge Creator Pro 2 - Not Showing Up In OctoPrint

[ThePie]

What is the problem?

Flashforge Creator Pro 2 not working with OctoPrint.

This is the first time using OctoPrint (and the first time trying to use this Creator Pro 2). I have this running on a Pi 4 with a camera.

What did you already try to solve it?

I created a profile and also checked the linux lsusb command (see below picture) and can see that the Pi 4 see's the printer.

Have you tried running in safe mode?

Yes

Did running in safe mode solve the problem?

No

Systeminfo Bundle

You can download this in OctoPrint's System Information dialog ... no bundle, no support!)

octoprint-systeminfo-20240809040233.zip (30.4 KB)

Additional information about your setup

OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible

[ThePie]

New users can only post 1 embed so here is the other image I was referring too.

[ThePie]

Ran through this guide and got most things working.

OctoPrint - Flashforge Creator Pro 2 - Tech blog with tips, tricks and hacks

Trying to figure out the following error message now.

Unexpected error while connecting to serial port FlashForge Creator Pro 2 3D Printer, port:1:4, baudrate 115200 from hook GPX: FileNotFoundError: '[Errno 2] No such file or directory: 'FlashForge Creator Pro 2 3D Printer, port:1:4'' @ comm.py:_open_serial:3944

[ThePie]

@MSmthng I noticed you had a similar issue. The version you recommended from your branch is also the same one that is published currently. (I did uninstall and try both but made no difference).

OctoPrint Version 1.10.2

Octo Pi Build 2024.06.18.085851 with "webcamd", based on OctoPi 1.0.0, running on Raspberry Pi 4 Model B Rev 1.5

Octoprint debug log has the below repeating every minute.

octoprint.log

2024-08-10 06:40:40,359 - octoprint.plugins.flashforge - DEBUG - detect_printer()
2024-08-10 06:40:40,361 - octoprint.plugins.flashforge - DEBUG - Unable to get device name LIBUSB_ERROR_ACCESS [-3]
2024-08-10 06:40:40,362 - octoprint.plugins.flashforge - DEBUG - Found device 'unknown device' with Vendor ID: 0X1D6B, USB ID: 0X0003
2024-08-10 06:40:40,368 - octoprint.plugins.flashforge - DEBUG - Found device 'FlashForge Creator Pro 2 3D Printer' with Vendor ID: 0X2B71, USB ID: 0X000E
2024-08-10 06:40:40,368 - octoprint.plugins.flashforge - INFO - Found a FlashForge FlashForge Creator Pro 2 3D Printer, port:1:4
2024-08-10 06:40:40,371 - octoprint.plugins.flashforge - DEBUG - Unable to get device name LIBUSB_ERROR_ACCESS [-3]
2024-08-10 06:40:40,372 - octoprint.plugins.flashforge - DEBUG - Found device 'unknown device' with Vendor ID: 0X0BDA, USB ID: 0XC811
2024-08-10 06:40:40,374 - octoprint.plugins.flashforge - DEBUG - Unable to get device name LIBUSB_ERROR_ACCESS [-3]
2024-08-10 06:40:40,376 - octoprint.plugins.flashforge - DEBUG - Found device 'unknown device' with Vendor ID: 0X2109, USB ID: 0X3431
2024-08-10 06:40:40,379 - octoprint.plugins.flashforge - DEBUG - Unable to get device name LIBUSB_ERROR_ACCESS [-3]
2024-08-10 06:40:40,380 - octoprint.plugins.flashforge - DEBUG - Found device 'unknown device' with Vendor ID: 0X1D6B, USB ID: 0X0002

Again, this is the error I am having. @foosel are you familair with this issue or any Flashforge communities that could be of assistance?

Unexpected error while connecting to serial port FlashForge Creator Pro 2 3D Printer, port:1:4, baudrate 115200 from hook GPX: FileNotFoundError: '[Errno 2] No such file or directory: 'FlashForge Creator Pro 2 3D Printer, port:1:4'' @ comm.py:_open_serial:3944

[MSmthng]

Hi, i was only able to get rid of this issue by shielding my cable and using one which was as short as possible. Since then is haven't faced this issue so far.

[ThePie]

I am using the cable below. However, I don't believe this is a cable issue as the Pi and CP2 can communicate with one another.

It seems there is some missing file or something that the GPX Plugin might be looking for?

https://www.amazon.com/gp/product/B0B9RQG2MH/

[Ewald_Ikemann]

Gold plated contacts do not make a good USB cable.

Choose one with ferrite beads/chokes

[ThePie]

I can agree with the ferret bead req. However, I can talk to the printer so this can't be a USB issue I am facing. I'll try the ferrite bead USB cable in a few days but don't expect any change in the issue of the mystery file not being found.

[b-morgan]

The recommendation for a higher quality USB cable is being made because the error you have shown us has historically occurred with serial communication errors caused by EMI.

In order to confirm that this is (or is not) YOUR issue, we need to see a serial.log.

[ThePie]

Tried the above suggested cable. Getting the same error. Logs are attached below.

plugin_GPX.log (869 Bytes)
serial.log (1.2 KB)

[b-morgan]

The serial log looks clean so I believe we are NOT dealing with an EMI related communications error. Thank you for providing it.

There are two plugins which attempt to deal with the communications protocol of the Flashforge printers, the one you are using, https://github.com/Mrnt/OctoPrint-FlashForge, and this one, https://github.com/markwal/OctoPrint-GPX.

You could give the other plugin a try (disable the current one as there can only be one) but if it fails switch back as the plugin you are using appears to be more up-to-date.

Verify that all the steps in the Tech blog were completed without error (i.e. no typos) and if so, I'd open an issue on its github repository and see if they can help. There is also a contact link on the Tech blog.

Flashforge expertise in this forum is limited as there aren't that many members that have one.

[ThePie]

Looks like I did need to disable the GPX plugin. That's the only step I was missing through all of this.

I can try to run a few test prints now.