1 2013-11-06 01:46:30 (edited by muddtt 2013-11-06 01:48:18)
Re: Slicer and print software from phone
Nice! Surprised to see support for Windows Phone 
Windows Phone never gets anything interesting. This is a first.
My last 3 phones were Nokia and I'm using a Nokia Windows Phone now. Sadly, I'm moving onto both IOS and Android now.
- mark.burhop
- Member
- Offline
Re: Slicer and print software from phone
I just swapped out my iPhone fro the new Nokia 1020. I'm missing a few apps that I would have gotten with Android but I'm actually quite pleased with it. The only reason I might get rid of it is to get GoogleGlass (which I tried yesterday and was impressed).
Interestingly, Reptier is done in C# so should be somewhat friendly to being ported to a WinPhone. I'm not quite sure why you would do that (unless you don't have a computer like many people in developing nations) but it is cool.
It might get more fun when you can integrate a scanner into the phone.
SD2, glass bed, MK5 setup with E3D lite extruder
NX and Solid Edge CAD user
PI, Galileo, and arduino hacker
Code Monkey and Twitter user @burhop
NX and Solid Edge CAD user
PI, Galileo, and arduino hacker
Code Monkey and Twitter user @burhop
Re: Slicer and print software from phone
mark.burhop wrote:
I just swapped out my iPhone fro the new Nokia 1020. I'm missing a few apps that I would have gotten with Android but I'm actually quite pleased with it. The only reason I might get rid of it is to get GoogleGlass (which I tried yesterday and was impressed).
Interestingly, Reptier is done in C# so should be somewhat friendly to being ported to a WinPhone. I'm not quite sure why you would do that (unless you don't have a computer like many people in developing nations) but it is cool.
It might get more fun when you can integrate a scanner into the phone.
Except its actually slic3r that you need more than repetier host to be able to generate g-code... RH is the least of the issues in the chain.. it is far more an issue around the number crunching and RAM involved in slicing a model. Your best bet, in a phone, would be to setup a 'cloud' RH that can use API's to ship off the STL to an 'online' slicer that then ships the resultant g-code back to your phone.
But crunching models, particularly complex ones, on the phone is the biggest hurdle.. there is a surprising amount of grunt required to translate a mesh to linear gcode 
So anyway - if you want to tackle this at any stage, be concious that there is many abstracted layers here - Printer Control, Printer Configuration, Object Placement/Alignment, Then Slicing Parameters, Then Slicing it, and Finally, the brain dead simple act of streaming over usb-to-serial to your printer the resultant output.
You can actually achieve all of this right now... as long as you don't care to slice on the phone itself and ship in pre-factored gcode...