June 2023 Update: If you are receiving an error about overflowing the rom like this: "/usr/lib/gcc/arm-none-eabi/8.3.1/../../../arm-none-eabi/bin/ld: out/klipper.elf section .text' will not fit in region rom' /usr/lib/gcc/arm-none-eabi/8.3.1/../../../arm-none-eabi/bin/ld: region `rom' overflowed by 242 bytes collect2: error: ld returned 1 exit status" Make sure you are disabling i2C when compiling the firmware. See here for the latest instructions: github.com/VoronDesign/Voron-Hardware/blob/master/V0_Display/Documentation/Setup_and_Flashing_Guide.md Update: Screen Smearing: If anyone noticed the "smearing" on the screen (on the white text) this is a known issue. To get rid of it, simply uncomment the line for "vcomh" in your DisplayEncoder.cfg file, and set the value to 31. (So the line should read vcomh: 31). Special thanks Voron Discord user GopherOnTheRoad V0.968 for letting me know about this! Also, add this setting if you need to fix your screen offset: x_offset: 2 Thanks to Voron Discord user Jon V2.1755 V0.870 for the tip! I also have a follow on video planned soon, to go over customizing the screen and will provide a link to the customizations I have found to be beneficial. (Bed Leveling, Additional temperatures, etc.)
Thanks for the video, just what i have been waiting for . lots of voron videos on yutube but i could not find one like this that explains how to set the dislay up. Thanks.
great video. one small thing is you can get rid of the black plastic at the base of the LCD pins, you can either try to pry it off using a flat tool or you can crush it with a pair of snips and remove it. Either way it'll make for a cleaner, more secure connection.
Thanks for watching! Those fans are still a WIP- it has been a long time in the coming for them, and I've put that project on hold at the moment. However, I do plan on picking up again soon. They are basically 5015 fans, powered by the Klipper Extender to add additional cooling when I print lower temp materials like PLA, and can also be helpful for pushing speeds. I've noticed some very marginal improvements with my testing so far (mostly bridging tests). I want to make sure I can demonstrate a significant enough improvement before I get them out in the wild, so more testing is ahead, and also some additional design tweaks.
Hi Greg. You can disable the octoprint menu if you’re not using octoprint. I did. But I’ve never been able to get the SD card menu to show anything at all. What does yours have in it? Can you start a print etc? I might be missing something in the config but I don’t know what.
Thanks-definitely planning on tweaking some of the options, I may do a follow up video too with more info. It looks to have all the files that I have uploaded in the directory are there on the SD card menu. Do you have the virtual SD card option enabled?
I am having a similar issue. I mirrored your video here and only certain options mine executes. Mine will do everything but print from the SD card option even though it displays all the files in the directory. Any ideas ?
@@newreefer92 I did manage to get it to work on my V0.1. I discovered you can’t have any files in submenus which is a shame. If you do then the sd card menu is blank. This means having more than a handful of files is a pain. To get it to print you need to go to sd card menu then click on the file you’d like to print. Then go back (…) out of the menu. Then go back in to the sd card menu and start printing should be the first menu option with all the gcode files below. Not brilliant. Having said all this I think I have you’re issue with my trident. I have all the print files showing but the start printing option never appears no matter what I do. Feel like all this needs an overhaul.
Greg is this screen dependent on OctoPrint? Like I am using DUETPI with a Raspberry Pi, with the Duet Mini 5+... I wondered if i plugged this into the Pi, would it work? Probably not?
Thanks! Yes, here you go for the printed parts. I will add to the description of video also. github.com/VoronDesign/Voron-Hardware/tree/master/Klipper_Expander/CAD Best of luck!
Can't seem to get the board to show up in lsusb . I've tried connecting with the micro USB and with the jst-xh connectors and neither works. I made sure the boot pins are bridged when I plug it in. I've also checked with a multimeter when I'm connecting through micro USB that I'm getting 5V between GND and 5V pins, and the 2 data pins also have non-zero voltage. Did I miss something or is it a defective unit? How do I debug it?
Hi, for fly-gemini the user was "fly" and the pass "mellow". I already flash the lcd and added the .cfg. When restart the firmware de log says: mcu 'display': Unable to open serial port: [Errno 11] Could not exclusively lock port /dev/serial/by-id/usb-Klipper_stm32f405xx_2A002A000E47323032383135-if00: [Errno 11] Resource temporarily unavailable. Can you help me with that please?
I wish I could help you but I am not familiar with that board or error. I have a new mellow fly board on my next build and if I come across anything I will try to check back. Best of luck and hope you can resolve itZ
It Will Not Print From Display... i can home all, change temps, retract or reload filament, but it will not print from display. no info on how to make this work. its frustrating. followed all guides to the letter.
Thanks for commenting on this. I also noticed that my latest Voron 0.2 that I put this same config on also doesn't have the print option anymore, and I'm not sure why. My guess is that something has changed in the underlying klipper that requires me to change the config.
Ok, I figured out the issue. I am not sure what may have changed, but it's possible that the newer versions of klipper do not have the SD card enabled by default. Here is how you can add it: Go to this link and copy the line 163-167 and add to your configuration file (either printer.cfg, or your display include file). This section is called ### menu virtual sdcard ### github.com/Klipper3d/klipper/blob/master/klippy/extras/display/menu.cfg
I'm somewhat confused why you need an STM32 to drive basically an I2C OLED display and monitor a rotary encoder and button. The Pi should be able to do that itself, no? Why tie up a USB port for something that could be done also via a couple (well, maybe 5) GPIO pins of the Pi?
Sure, you can configure a display connected directly to the Raspberry Pi. I personally have not seen anyone do this on a Voron 0 but that doesn't mean it hasn't been done. It is more common to see direct connections to the Pi on larger machines like the Trident or Voron 2.4 that use the ribbon cable and a touch screen, or use the LCD pins directly to the controller if using a 12864 type screen. Due to how the Pi and touch screen is mounted, it wouldn't be as easy to run a ribbon cable around. With the Voron 0 there are a lot of choices limited by space and form factor, and not necessarily software. With that in mind, I like this option because it is a small display / small profile that works great with the V0, and small controller boards like the BTT Pico that don't have pins for LCD controllers. The Voron 0 is so small that you aren't going to have a lot of USB devices on it, so it's not a concern using one of them for this purpose. There is also some good community support for installing this display (available housing, etc.). There is also a Voron display (Simple Display) that doesn't use a USB, and uses GPIO pins directly on the controller, which doesn't use a separate STM32 to your point as well (but doesn't connect to the Pi). Thanks for watching and commenting!
Your channel is legitimately the biggest help when building a v0, kudos
Thanks!!! Appreciate the feedback :)!
This video saved me again, when Klipper failed to update on the V0 Display!
same here, Greg is such a treasure.
June 2023 Update:
If you are receiving an error about overflowing the rom like this: "/usr/lib/gcc/arm-none-eabi/8.3.1/../../../arm-none-eabi/bin/ld: out/klipper.elf section .text' will not fit in region rom'
/usr/lib/gcc/arm-none-eabi/8.3.1/../../../arm-none-eabi/bin/ld: region `rom' overflowed by 242 bytes
collect2: error: ld returned 1 exit status"
Make sure you are disabling i2C when compiling the firmware. See here for the latest instructions:
github.com/VoronDesign/Voron-Hardware/blob/master/V0_Display/Documentation/Setup_and_Flashing_Guide.md
Update: Screen Smearing:
If anyone noticed the "smearing" on the screen (on the white text) this is a known issue. To get rid of it, simply uncomment the line for "vcomh" in your DisplayEncoder.cfg file, and set the value to 31. (So the line should read vcomh: 31). Special thanks Voron Discord user GopherOnTheRoad V0.968 for letting me know about this! Also, add this setting if you need to fix your screen offset: x_offset: 2 Thanks to Voron Discord user Jon V2.1755 V0.870 for the tip! I also have a follow on video planned soon, to go over customizing the screen and will provide a link to the customizations I have found to be beneficial. (Bed Leveling, Additional temperatures, etc.)
Thanks for the video, just what i have been waiting for . lots of voron videos on yutube but i could not find one like this that explains how to set the dislay up. Thanks.
Awesome informational video. Thanks for walking us thru the install and setup.
Just ordered this screen, a new build plate, and the aluminum composite plates for my V0.1. :) Will be using this video as I put the screen together.
This video was for great help, you're the man Greg!
Glad to hear.. thanks for watching!
Great video. That looks like a really sharp and solid little display.
Thanks.. So far so good! I am looking forward to customizing it a bit more.
great video. one small thing is you can get rid of the black plastic at the base of the LCD pins, you can either try to pry it off using a flat tool or you can crush it with a pair of snips and remove it. Either way it'll make for a cleaner, more secure connection.
Glad you figured out that USB issue. It's annoying how that color "standard" is anything but standard lol
Haha.. yes and thanks again for the assistance there, and also the awesome design!
I need more info about those fans and shrouds you have on the sides of your voron! I need that!
Thanks for watching! Those fans are still a WIP- it has been a long time in the coming for them, and I've put that project on hold at the moment. However, I do plan on picking up again soon. They are basically 5015 fans, powered by the Klipper Extender to add additional cooling when I print lower temp materials like PLA, and can also be helpful for pushing speeds. I've noticed some very marginal improvements with my testing so far (mostly bridging tests). I want to make sure I can demonstrate a significant enough improvement before I get them out in the wild, so more testing is ahead, and also some additional design tweaks.
Awesome video Greg, thanks!
One thing that didn't work for me is the wire color, I flip the 2 data wires, so is bk-gn-wh-rd for me.
It's working, thanks Greg, very, very helpful.
Greart video , now have a working display! Thanx Greg
Awesome.. glad to hear you got it working! Thanks for the comment.
Hi Greg. You can disable the octoprint menu if you’re not using octoprint. I did. But I’ve never been able to get the SD card menu to show anything at all. What does yours have in it? Can you start a print etc? I might be missing something in the config but I don’t know what.
Thanks-definitely planning on tweaking some of the options, I may do a follow up video too with more info. It looks to have all the files that I have uploaded in the directory are there on the SD card menu. Do you have the virtual SD card option enabled?
I am having a similar issue. I mirrored your video here and only certain options mine executes. Mine will do everything but print from the SD card option even though it displays all the files in the directory. Any ideas ?
@@newreefer92 I did manage to get it to work on my V0.1. I discovered you can’t have any files in submenus which is a shame. If you do then the sd card menu is blank. This means having more than a handful of files is a pain. To get it to print you need to go to sd card menu then click on the file you’d like to print. Then go back (…) out of the menu. Then go back in to the sd card menu and start printing should be the first menu option with all the gcode files below. Not brilliant. Having said all this I think I have you’re issue with my trident. I have all the print files showing but the start printing option never appears no matter what I do. Feel like all this needs an overhaul.
@@bonjipoo Thank you for help! I will give it a shot and see if that works!
Awesome video!
Greg is this screen dependent on OctoPrint? Like I am using DUETPI with a Raspberry Pi, with the Duet Mini 5+... I wondered if i plugged this into the Pi, would it work? Probably not?
Great video. would you be able to put a link to the printed parts? thank you
Thanks! Yes, here you go for the printed parts. I will add to the description of video also. github.com/VoronDesign/Voron-Hardware/tree/master/Klipper_Expander/CAD Best of luck!
Can you adjust z offset from the display?
Hi Greg thank you for this video. Do you have a sorce for the connectors? Is the installing for using it with the usb cable the same?
Can't seem to get the board to show up in lsusb . I've tried connecting with the micro USB and with the jst-xh connectors and neither works. I made sure the boot pins are bridged when I plug it in. I've also checked with a multimeter when I'm connecting through micro USB that I'm getting 5V between GND and 5V pins, and the 2 data pins also have non-zero voltage. Did I miss something or is it a defective unit? How do I debug it?
Try swapping the data pins. I know the colors of the pins for data are sometimes reversed or different depending on the cable you get. Best of luck!
@@GregsMakerCorner Good callout. But that doesn't affect using the micro usb cable, right? I can't get it to show up even with micro usb.
@@michaelmao6180same. Did you ever get this to work?
Hi, for fly-gemini the user was "fly" and the pass "mellow". I already flash the lcd and added the .cfg. When restart the firmware de log says: mcu 'display': Unable to open serial port: [Errno 11] Could not exclusively lock port /dev/serial/by-id/usb-Klipper_stm32f405xx_2A002A000E47323032383135-if00: [Errno 11] Resource temporarily unavailable.
Can you help me with that please?
I wish I could help you but I am not familiar with that board or error. I have a new mellow fly board on my next build and if I come across anything I will try to check back. Best of luck and hope you can resolve itZ
Thank you great explanation
It Will Not Print From Display...
i can home all, change temps, retract or reload filament, but it will not print from display. no info on how to make this work. its frustrating. followed all guides to the letter.
Thanks for commenting on this. I also noticed that my latest Voron 0.2 that I put this same config on also doesn't have the print option anymore, and I'm not sure why. My guess is that something has changed in the underlying klipper that requires me to change the config.
Ok, I figured out the issue. I am not sure what may have changed, but it's possible that the newer versions of klipper do not have the SD card enabled by default.
Here is how you can add it:
Go to this link and copy the line 163-167 and add to your configuration file (either printer.cfg, or your display include file). This section is called ### menu virtual sdcard ###
github.com/Klipper3d/klipper/blob/master/klippy/extras/display/menu.cfg
I'm somewhat confused why you need an STM32 to drive basically an I2C OLED display and monitor a rotary encoder and button. The Pi should be able to do that itself, no? Why tie up a USB port for something that could be done also via a couple (well, maybe 5) GPIO pins of the Pi?
Sure, you can configure a display connected directly to the Raspberry Pi. I personally have not seen anyone do this on a Voron 0 but that doesn't mean it hasn't been done. It is more common to see direct connections to the Pi on larger machines like the Trident or Voron 2.4 that use the ribbon cable and a touch screen, or use the LCD pins directly to the controller if using a 12864 type screen. Due to how the Pi and touch screen is mounted, it wouldn't be as easy to run a ribbon cable around. With the Voron 0 there are a lot of choices limited by space and form factor, and not necessarily software.
With that in mind, I like this option because it is a small display / small profile that works great with the V0, and small controller boards like the BTT Pico that don't have pins for LCD controllers. The Voron 0 is so small that you aren't going to have a lot of USB devices on it, so it's not a concern using one of them for this purpose. There is also some good community support for installing this display (available housing, etc.). There is also a Voron display (Simple Display) that doesn't use a USB, and uses GPIO pins directly on the controller, which doesn't use a separate STM32 to your point as well (but doesn't connect to the Pi).
Thanks for watching and commenting!