Separate names with a comma.
Discussion in 'Off Topic' started by colton81, May 14, 2017.
used once or 10k times. still used.
Yea and plus why would you only use it once then sell it? Hmm most people dont drop $600 on a printer and use it once then decide not use it ever again
If it is brand new and unused -- still no warranty.
For that same money you at least get a refurb warranty (which while not as good as new is at least still a warranty)
Never buy a used 3d printer unless you're willing to pay out of pocket to fix it.
If it was truly brand new then why not return it.
Also, that Monoprice Delta went up for pre-orders for $159 + $10 shipping in the US for just the printer, $259 + 410 shipping for the printer + 2 spools of filament + a Simplify3D license.
Because Robo charges a restocking fee for returns if they are done within 10 days of purchase, and you're stuck with it if it's been more than ten days, probably.
That assumes she bought it direct from Robo. And really restocking is likely a much smaller loss than getting $200-300 for it.
It's enough to make some people hesitate long enough to miss the deadline vs. trying to troubleshoot issues though, especially since you pay shipping + restocking to send it back.
Also, the kind of person that tries to sell a used 3d printer for full retail on ebay is also the kind of person that originally buys directly from Robo vs. the smarter venues of Amazon or a big retail store that carries it.
Still painting with a broad brush
So i got my arduino due in and trying to just figure out how to use it properly. What firmware does Robo use is it Marlin or MK4DUO? Still doing research on how to install everything but looks like i have to have the RADD really to test anything which i was wanting to make sure i can figure it out before i drop $100 on it
Marlin is what the Robos use. v1.0 is stock on the R series and v1.10 on the C2/R2
You will need to adjust the motherboard type in Marlin to match whatever you end up going with.
Well crap ok looks like marlin is compatible for the arduino due
32-bit support for Marlin is still experimental, so you're basically in the realm of "you're operating on your own research" for upgrading the Robo-manufactured frame to use a 32-bit controller.
Not to say it won't work, but you'll basically have to study how to modify the firmware to work properly for the build size/motor setup/homing switches/etc. the Robo uses.
So might be a stupid question but the image file that is used to install on the Pi could i just connect the pi to the due and hse the same image file pr would i have to have a complete new image file compatible with the due?
The image file for the Pi is independent of whatever is going on with the Arduino. All that Octoprint needs to know to connect is the baud rate and port.
I would go with Ramps-FD if you were trying to make this easy
Then it is just the Due the RAMPS-FD board and load the firmware (with minor tweaks)
The Pi and OctoPrint is still an excellent add-on, but not related to the control electronics
Well ot seems the v1 ramps fd was flawed and had saftey issues and they never released a v2 though it looks like it was in the works. So far it looks like the Radd is the only option but im seeing some people were having trouble getting it up and running. I did see someone on youtube had the arduino due and Radd working a independent dual extruder. But doesnt mention how or what he did
If you can sort out what motherboard type the Due and RADD is then you should be fine.
You could always hack a RAMPS to work with the Due
Personally I would start with the custom Marlin4Due code:
You are on a journey.
more time than output lol. Been there... good luck my friend.