DoESLiverpool
Octopi not working for 3D printer Marcus
Octopi unable to connect to the printer. The following messages are being displayed:
No serial port found, are you sure your printer is physically connected and supported? Try refreshing and if that doesn't help please see the FAQ.
Could not autodetect your printer No working connection parameters could be found. Are you sure your printer is physically connected and supported? Refer to the FAQ for help in debugging this.
No more candidates to test, and no working port/baudrate combination detected.
Apparently there is a known intermittent issue with the USB connection between the pi and the printer. Moving it around might help.
I took the controller apart on this printer and couldn’t see any bad solder connections, so I suspect that the USB connector has failed internally.
Given that the SD card has failed on this board as well, I would suggest that we source a replacement controller to get this printer working again, then look at fitting some replacement parts to keep this original controller as a spare.
The specific controller for this printer is a Creality 3D V4 5.3.
I found a few UK based suppliers, but non appear to have this board in stock at present. I did find a vendor selling this controller on Alibaba, which is not a bad price. Other overseas suppliers are looking for $70-90 for this controller, so at £33.99 + £1.83 shipping, the item below looks to be a good option.
https://www.aliexpress.com/item/1005007406219810.html
I've ordered the board from AliExpress. Delivery March 5 - 12. Total cost £42.61 inc. shipping and 20% VAT
@Knottyashcreative has upgraded the firmware, and asked me to run a test print. The bed and nozzle heated up ok but nothing actually printed, although Octopi reported that it had.
Checked Octopi - it is running the latest version.
Ran a print via SD card. It seems to be running fine.
Trying the file CCR6SE_3DBenchy.gcode from the Octopi server doesn't recreate this problem, the machine is printing fine.
What was the file you were having problems with?
I had fully re calibrated the system and then eventually, SD card worked but never got time to check octopi
On Thu, 3 Apr 2025, 13:10 huffeec, @.***> wrote:
Trying the file CCR6SE_3DBenchy.gcode from the Octopi server doesn't recreate this problem, the machine is printing fine. What was the file you were having problems with?
— Reply to this email directly, view it on GitHub https://github.com/DoESLiverpool/somebody-should/issues/2014#issuecomment-2775586518, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN3A54BG7IOIPPT3M23VPNT2XUQKXAVCNFSM6AAAAABXQLZCXSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONZVGU4DMNJRHA . You are receiving this because you were mentioned.Message ID: @.***> [image: huffeec]huffeec left a comment (DoESLiverpool/somebody-should#2014) https://github.com/DoESLiverpool/somebody-should/issues/2014#issuecomment-2775586518
Trying the file CCR6SE_3DBenchy.gcode from the Octopi server doesn't recreate this problem, the machine is printing fine. What was the file you were having problems with?
— Reply to this email directly, view it on GitHub https://github.com/DoESLiverpool/somebody-should/issues/2014#issuecomment-2775586518, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN3A54BG7IOIPPT3M23VPNT2XUQKXAVCNFSM6AAAAABXQLZCXSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONZVGU4DMNJRHA . You are receiving this because you were mentioned.Message ID: @.***>
Trying the file
CCR6SE_3DBenchy.gcodefrom the Octopi server doesn't recreate this problem, the machine is printing fine. What was the file you were having problems with?
Octopi seems to be working now. It might be that I didn't wait long enough (needed 16 minutes).
The printer firmware seems to be set to a smaller size bed. It only printed part of a large area print I tried to print this morning.
I ran the mesh validation and it created a grid approx. 250x250mm on the front left hand size of the bed. When I homed the print head it went to the centre of this grid.
@Knottyashcreative has updated the motherboard firmware and I've now updated the touchscreen firmware. The touchscreen now responds, but I haven't had a chance to try a print yet. Note: the touchscreen repository contains instructions for using formatting and partitioning an SD card larger than 16MB so you can have it as FAT32 and 4096 sector size).
@JackiePease says that the temperature is not staying at the right temperature for the print to be successful. it raises to the right temp, then drops below the right level for the print.
I have reflashed the firmware in case there was an issue, printing from Octoprint with a file prepared in Cura works fine. Although I suspect the credit should go to @pyrosyndicate for cleaning the hot end.
The temperature issue described above may relate to the PID tuning which is part of the firmware install process and referred to in this issue for the firmware. I've set values but it can be run through the terminal in Octopi if there are more issues.