Tools: Hypercube 300: Difference between revisions

From Tampa Hackerspace
Jump to navigation Jump to search
(Initial writeup; problem#1; This sucks)
Line 2: Line 2:


==  Accessing the Hypercube ==
==  Accessing the Hypercube ==
* From within the Tampa Hackerspace network, the Hypercube #1 can be accessed by browsing to _____________
* From within the Tampa Hackerspace network, the Hypercube #1 can be accessed by browsing to http://hypercube1/
* Remotely, printer status can be viewed by logging in to THS's Slack and viewing the #3d_printer_status channel.
* Remotely, printer status can be viewed by logging in to THS's Slack and viewing the #3d_printer_status channel.



Revision as of 02:06, 28 July 2018

Last revision 20180728020642 by Leebc

Accessing the Hypercube

  • From within the Tampa Hackerspace network, the Hypercube #1 can be accessed by browsing to http://hypercube1/
  • Remotely, printer status can be viewed by logging in to THS's Slack and viewing the #3d_printer_status channel.

Building the Hypercube

Hypercube 300....and it uses CoreXY motion mechanics.


Problems we've encountered

Hypercube bed is all the way down and does not want to move

Resolution by @adrianm1972:

  • The Z motors were a little out of alignment with the z lead screw nuts on the best. It ran fine at the top of its range because the lead screws are unsupported up there and that masks the alignment problem. At the bottom of its movement range everything is bolted to the frame and the slight misalignment cause binding that the Z stepper motors could not overcome.
  • We brought the bed all the way down, loosened the Z motor mounts and let everything pull itself into natural alignment then tightened everything up.