Topic: new object
While you are printing one object , can you load and slice another? oh in RH.
SD3, E3D hotend,linear bearing on x/y axis',pillow block bearing on y conneting rod, ball bearngs on front y axis, fan on y stepper motor.
Re: new object
If the computer is fast enough. I've tried to add to the end gcode while a print was running, and it didn't do the change so when you hit Run, I think the whole gcode is loaded into memory and sent from there. You can open a new gcode into the gcode window without changing the print.
You should have a fast computer however. I use a slow $40 pc I got from ebay, and if the CPU peaks I get pauses in the print.
Re: new object
Can you open two instances of RH? I use skeinforge and pronterface so I'm always slicing while I'm printing. Of course I'm printing from a laptop that was spec'd out to run solidworks well so not a lot is going to slow it down.
Re: new object
I have a cheap win7 x32bit netbook as my dedicated Solidoodle controller. (I'm waiting on my vikiLCD). It works, but it not any super computer, that's for sure!
I can open two instances of RH, use one for slicing and one for an active print. There are times though that I can tell the print job slows down from the extra processing overhead of slicing a new model.
If you have a newer 'puter thats x64bit with an i5/i7 processor, you should definitely be able to open at least two instances of RH. But if you know your 'puter is old and slow, then you're better off only doing one task at a time. Note that I said 'should' above, everyone has their own setup and I can't attest to idiosyncrasies of your own personalized system.
SD2 w/ mods: Rumba controller, ATX PSU, SD pro case, glass bed, with more to come...
Re: new object
I run 2 instances of RH to run 2 printers simultaneously. I have never seen even hesitation in my printers. I tend to slice and then print, slice and then print. Hardware is so cheap now that getting a quad or hex processor at 2.5 GHz is feasible.
When RH slices, that is saved in a file. When RH prints (runs a job), the gCode is pulled into memory, after which you can re-slice something and save it in that same global file. You can trip over your own two feet if you are not careful, but it usually works flawlessly.