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
mission:resources:picoprint [2015-04-19 18:27] – [Electronic Components] chronomission:resources:picoprint [2016-03-16 12:29] (current) – [Electronic Components] chrono
Line 120: Line 120:
 === 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). 
  
 {{:mission:resources:picoprint-odroid-dual-head-wiring-diagramm.png|Felix 3.0 Dual-Head 3D Printer with Odroid C1 Wiring Diagram}} {{: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 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.+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]]. 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]].
Trace:

Page Tools