G-code loads, but is grayed out, wont print

Did you do this bit? It doesn't see the printer at all. Not even an error :thinking:

Anything could have died there, only by process of elimination will you sort it I think. Different cable, different port, try plugging printer into a PC or something to see if it still works.

The printer will run from it's SD card. I changed cable between pi and printer. I removed and reinserted everything that moves.

I even tried to change the pw back to the default but it wouldn't let me - too close to what I am using.

Upon attempting connection Octoprint has 0 candidate printers to search for so it has nothing to find.
I enabled Virtual Printer and it reports 1 candidate printer which it connects to.
When I disable Virtual Printer it has 0 candidates
What happened to my printer spec. It appears to be there under Printer Setup.
This is from turning Virtual Printer on and off:

2021-04-02 02:01:55,156 - octoprint.server.util.flask - INFO - Passively logging in user ghb from ::ffff:192.168.1.227
2021-04-02 02:01:55,157 - octoprint.access.users - INFO - Logged in user: ghb
2021-04-02 02:01:55,196 - octoprint.server.util.sockjs - INFO - User ghb logged in on the socket from client ::ffff:192.168.1.227
2021-04-02 02:02:59,692 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Detecting serial connection"
2021-04-02 02:02:59,719 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.1.227
2021-04-02 02:02:59,746 - octoprint.util.comm - INFO - Serial detection: Performing autodetection with 0 port/baudrate candidates: 
2021-04-02 02:02:59,747 - octoprint.util.comm - INFO - Changing monitoring state from "Detecting serial connection" to "Error: No more candidates to test, and no working port/baudrate combination detected."
2021-04-02 02:02:59,748 - octoprint.util.comm - INFO - 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.)"
2021-04-02 02:02:59,816 - octoprint.plugins.action_command_notification - INFO - Notifications cleared
2021-04-02 02:03:01,521 - octoprint.plugins.tracking - INFO - Sent tracking event commerror_autodetect, payload: {'commerror_text': 'No more candidates to test, and no working port/baudrate combination detected.', 'throttled_now': False, 'throttled_past': True, 'throttled_mask': 851968}
2021-04-02 02:03:46,705 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.1.227
2021-04-02 02:03:47,517 - octoprint.server.util.sockjs - INFO - New connection from client: ::ffff:192.168.1.227
2021-04-02 02:03:47,662 - octoprint.server.util.flask - INFO - Passively logging in user ghb from ::ffff:192.168.1.227
2021-04-02 02:03:47,663 - octoprint.access.users - INFO - Logged in user: ghb
2021-04-02 02:03:47,848 - octoprint.server.util.sockjs - INFO - User ghb logged in on the socket from client ::ffff:192.168.1.227
2021-04-02 02:04:42,997 - octoprint.server.util.sockjs - INFO - New connection from client: ::ffff:192.168.1.227
2021-04-02 02:04:43,103 - octoprint.server.util.flask - INFO - Passively logging in user ghb from ::ffff:192.168.1.227
2021-04-02 02:04:43,104 - octoprint.access.users - INFO - Logged in user: ghb
2021-04-02 02:04:43,218 - octoprint.server.util.sockjs - INFO - New connection from client: ::ffff:192.168.1.227
2021-04-02 02:04:43,262 - octoprint.server.util.sockjs - INFO - User ghb logged in on the socket from client ::ffff:192.168.1.227
2021-04-02 02:04:43,281 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.1.227
2021-04-02 02:04:43,294 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.1.227
2021-04-02 02:06:33,987 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Detecting serial connection"
2021-04-02 02:06:34,012 - octoprint.util.comm - INFO - Serial detection: Performing autodetection with 1 port/baudrate candidates: VIRTUAL@115200
2021-04-02 02:06:34,012 - octoprint.util.comm - INFO - Serial detection: Trying port VIRTUAL, baudrate 115200
2021-04-02 02:06:34,115 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #1 with timeout 2.0s
2021-04-02 02:06:34,132 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-04-02 02:06:34,169 - octoprint.util.comm - INFO - Changing monitoring state from "Detecting serial connection" to "Operational"

I added a new printer and made it the default. It is also not recognized during Connect.
I tried Safe Mode.

Changing the printer profile in OctoPrint won't make a difference as to whether your Raspberry Pi will find the printer. As you showed with the lsusb command earlier the Pi is detecting no USB devices at all. OctoPrint can't affect this so you have to dig beyond here and to the system.

For the dmseg question, I still don't see an answer to this bit.

Try other USB devices. Camera, flash drive, any other USB device and see if the result under lsusb changes to show them.

Connect the printer to your PC. Does it recognise the device? Can you connect to it using something like Cura?

Does the USB cable work with other devices?

OK Octoprint is running!


I tried a USB cable connect to my PC as you suggested. PC saw it. I moved the same cable to the Pi and it worked. Two short cables I had tried were defective. I removed the tape from the red terminals and one of the two worked.The other I tossed. I re-taped it and it is working. If there is a problem connecting to the printer again, this is the first thing I will check.

That issue developed mid-stream. To address the g-code issue, I re-flashed OctoPrint. Etcher failed thrice, I used WIN32Disk Imager, a scary little program but it worked . I re-loaded the two Creality temperature Plug-Ins. At this time everything is working except the print time but I am not going to reload that Plug-in.

Thanks for your help, Charlie_Powell.

1 Like

To address the g-code issue, I re-flashed OctoPrint as you suggested. Etcher failed thrice, I used WIN32Disk Imager, a scary little program but it worked . I re-loaded the two Creality temperature Plug-Ins. At this time everything is working except the print time but I am not going to reload that Plug-in.

Thanks for your help, 5ft24.

what was scary about it if you don't mind me asking?

So glad I'm still on the previous version pre Python 3

Sure. This is in it's readme file:

This program is Beta, and has no warranty. It may eat your files,
call you names, or explode in a massive shower of code. The authors take
no responsibility for these possible events.

For some reason unknown to me it got involved with a D drive and a D "boot" drive. It states that it will only write to USB devices but you have to think "Am I about to format my C drive?"

:smiley:
I see