volkmarnissen
commented
2 years ago Today I did another test. This time, the bed was heated before printing. I assume, the firmware of the printer "forgets" to heat the bed if the hotend is already on target temperature.
I started with prusa slicer upload and print. However, in the fiberpunk web ui, the terminal showed some output, but it was not visible, that the printer is preparing for print. You saw the temperatures rising, but the "Print file:" field was empty. Later, when it started printing, the field contained an abbreviated file name.
So, these are the issues:
- Directly after uploading and starting print, the filename should be visible in the UI.
- The full file should be shown. The abreviation is only partly helpful.
- A status field would make sense.
- An unexperienced end user doesn't understand set SDIO SetSPI buttons. Can't this be detected automatically?
- The same is true for mount/unmount SD. I was not aware whether this is about the "fake SD card" or the internal SD card and I didn't know when to use it. I know, that there is a documentation on your web site, but I am also sure, that the system can encounter it automatically.
Additionally: I encountered a very slow upload compared to octopi. I assume this is due to limitations of ESP32. However, this is not so convinient.
fiber-punk
Describe the bug When I used fiberpunk node for the first time, the bed did not heat up. I am not so familiar with this printer. May be it's an issue with the firmware.
To Reproduce Steps to how it happened:
Expected behavior I expected the bed to be heated up because this is stated in the gcode file.
Desktop (please complete the following information):
Additional context I am new to fiberpunk and I am new to anycubic. So I don't know, where the problem is. Please confirm, that it's not an fiberpunk issue if possible.