User Tools

Site Tools

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
mission:resources:picoprint [2015/04/12 08:54] – [Electronic Components] chronomission:resources:picoprint [2016/03/16 12:29] (current) – [Electronic Components] chrono
Line 109: Line 109:
  
 All high-level functions like seeing (webcam) and user-level control & communication are handled by an embedded GNU/Linux board, which acts as cerebrum to conveniently host, maintain and access other open-source software components and offer networking out-of-the-box as well as a lot of flexibility. Many high-level features can be done in software, which replicates much faster in an all open-source environment. All high-level functions like seeing (webcam) and user-level control & communication are handled by an embedded GNU/Linux board, which acts as cerebrum to conveniently host, maintain and access other open-source software components and offer networking out-of-the-box as well as a lot of flexibility. Many high-level features can be done in software, which replicates much faster in an all open-source environment.
- 
-{{:mission:resources:picoprint-dual-head-wiring-diagramm.png|picoprint-dual-head-wiring-diagramm.png}} 
- 
-FIXME: This diagram is outdated and needs to be updated ASAP. 
  
 Although we love the Raspberry Pi and already have a few [[https://apollo.open-resource.org/tag:raspberry|projects]] featuring it, this robot called for a little more computing power, multicore architecture, 1G RAM and more GPIOs, SPI, I2C etc. which will become even more useful for future feature extensions.  Although we love the Raspberry Pi and already have a few [[https://apollo.open-resource.org/tag:raspberry|projects]] featuring it, this robot called for a little more computing power, multicore architecture, 1G RAM and more GPIOs, SPI, I2C etc. which will become even more useful for future feature extensions. 
Line 120: Line 116:
 The whole 2.0 duration of the setup was run on a [[http://www.watterott.com/en/Cubieboard2-Open-ARM-Box?x7ae9a=aedb9ba8f7b29ab7e49dbeaf24ce5bf5|Cubieboard2]] as basic underlying embedded Linux board for high-level interaction. Experience has been ok, timelapse rendering took still a considerable time though.  The whole 2.0 duration of the setup was run on a [[http://www.watterott.com/en/Cubieboard2-Open-ARM-Box?x7ae9a=aedb9ba8f7b29ab7e49dbeaf24ce5bf5|Cubieboard2]] as basic underlying embedded Linux board for high-level interaction. Experience has been ok, timelapse rendering took still a considerable time though. 
  
-{{:mission:resources:felix_3d_printer_7_cubieboard2.jpg|}} +{{:mission:resources:picoprint_schematics.png|Felix 2.0 3D Printer with Cubieboard2 Wiring Diagram}}
- +
-By hooking up the Cubieboard2/Odroid C1 to the 5V StandBy (purple) rail of the power supply, the robot is always online and ready to print with minimal power consumption. The full chain of Cubieboard2 (idle), USB Hub, USB Camera and USB Stick for additional storage needed for creation and storage of timelapse videos, draws something between 2 and 2.5 Watt (0.4-0.5A@5V). That's well below the Power Supply's StandBy Rail Maximum Rating of 2A while keeping the printer fully remote accessible. Here are a couple of notes about [[mission:resources:picoprint:software|cross-compiling and installing Gentoo on the Cubieboard]].+
  
 === Odroid C1 === === Odroid C1 ===
  
-With the 3.0 dis- and reassembly process the Cubieboard2 was replaced by an [[http://odroid.com/dokuwiki/doku.php?id=en:odroid-c1|Odroid C1]] Quad-Core ARMv7 (Cortex-A5) Board. Since the Odroid directly comes with 4 USB Ports the necessity for a separate USB switch fell away, not to mention the added I/O boost eMMC gives. With a custom, stripped down kernel and gentoo as OS, the cold boot time until octoprint is ready to use, is about 14 seconds (2s kernel + 12s init+dhcp+services). +With the 3.0 dis- and reassembly process the Cubieboard2 was replaced by an [[http://odroid.com/dokuwiki/doku.php?id=en:odroid-c1|Odroid C1]] Quad-Core ARMv7 (Cortex-A5) Board. Since the Odroid directly comes with 4 USB Ports the necessity for a separate USB-Hub fell away, not to mention the added I/O boost eMMC gives. With a custom, stripped down kernel and gentoo as OS, the cold boot time until octoprint is ready to use, is about 14 seconds (2s kernel + 12s init+dhcp+services). 
  
-The RGBW Status led is controlled directly via C1 GPIOs. With the power of 4 cores, the timelapse videos are no longer mjpgs since the C1 leaves enough reserves to render the videos with high quality x264 compression. A perfboard was strappend onto the the Odroid C1, for internal power distribution, additional connection terminals, the [[mission:log:2015:02:06:patching-kernel-ntp-to-fix-odroid-armv7a-chrony-adjtimex-bug|RTC hack]] and a couple of MOSFETs, to control the RGB Status LED and the table lighting LED stripe.+{{:mission:resources:picoprint-odroid-dual-head-wiring-diagramm.png|Felix 3.0 Dual-Head 3D Printer with Odroid C1 Wiring Diagram}} 
 + 
 +The RGBW Status led is controlled directly via C1 GPIOs. With the power of 4 cores, the timelapse videos are no longer mjpgs since the C1 leaves enough reserves to render the videos with high quality x264 compression. A perfboard was strapped onto the the Odroid C1, for internal power distribution, additional connection terminals, the [[mission:log:2015:02:06:patching-kernel-ntp-to-fix-odroid-armv7a-chrony-adjtimex-bug|RTC hack]] and a couple of MOSFETs, to control the RGB Status LED and the table lighting LED stripe. 
 + 
 +By hooking up the Cubieboard2/Odroid C1 to the 5V StandBy (purple) rail of the power supply, the robot is always online and ready to print with minimal power consumption. The full chain of Cubieboard2 (idle), USB Hub, USB Camera and USB Stick for additional storage needed for creation and storage of timelapse videos, draws something between 2 and 2.5 Watt (0.4-0.5A@5V). That's well below the Power Supply's StandBy Rail Maximum Rating of 2A while keeping the printer fully remote accessible. Here are a couple of notes about [[mission:resources:picoprint:software|cross-compiling and installing Gentoo on the Cubieboard]].
  
 ** Mounting ** ** Mounting **
Line 141: Line 139:
 {{:mission:resources:felix-3d-printer-ramps-board-with-odroid-c1-backpack2.jpg|Felix 3D Printer RAMPS board with Odroid C1 Backpack}} {{:mission:resources:felix-3d-printer-ramps-board-with-odroid-c1-backpack2.jpg|Felix 3D Printer RAMPS board with Odroid C1 Backpack}}
  
 +=== Cable & WIFI Network Access ===
 +
 +The Odroid C1 already provides Ethernet connectivity, which is accompanied by a USB WIFI Stick (embedded at the top of the Status-LED). The system can be configured to either join an existent WIFI network or act as an access point with its own WIFI network, if there is none available or other reasons (like security policies) prohibit connections. This is a great feature for impromptu class/workshop setups, when you can engage your audience to watch and interact with the printer using their own smartphones, tablets and laptops.
  
 === Power Buffer/Filter Hack === === Power Buffer/Filter Hack ===
Line 185: Line 186:
 \\ \\
 Having a microscope headcam could prove invaluable for remote machine operation. As soon as time permits we can begin to modify the head parts to accommodate for the energy chains and to place the microscope as well. It's then connected via USB to the Cubieboard via Linux UVC USB Drivers as well and can be accessed via /dev/video1.   Having a microscope headcam could prove invaluable for remote machine operation. As soon as time permits we can begin to modify the head parts to accommodate for the energy chains and to place the microscope as well. It's then connected via USB to the Cubieboard via Linux UVC USB Drivers as well and can be accessed via /dev/video1.  
- 
  
 === Table Lighting === === Table Lighting ===
Trace:

Page Tools