I hope the support will answer.
I have my printers in the Garage and normally i make my G Code in my office. But sometimes i use the PC in the Garage. So i need the 2 PCs installation. Thats a bad and not fair step.
You have a couple options now... Use the office machine to connect to the running version of S3d in the shop. It isn't too bad to do this. Or in the office machine save out a factory file and the file format your printer needs and save both to server. Go to shop and load factory file or print file as you normally would.Schwani wrote: ↑Fri Dec 23, 2022 1:20 pm Loosing a seat really messes with my work flow. Like many others, I prep, slice, and preview in the office. Save a factory file to a server. In the shop load the factory file, and print.
But without a second seat I can’t do that. In addition V4 doesn’t load v5 factory files, so that route is off the table too.
I get the license bit, there are better ways….
With this method, can you run S3D at same time on office and shop machines ? I don't think so.jfkansas wrote: ↑Wed Dec 28, 2022 6:43 pmYou have a couple options now... Use the office machine to connect to the running version of S3d in the shop. It isn't too bad to do this. Or in the office machine save out a factory file and the file format your printer needs and save both to server. Go to shop and load factory file or print file as you normally would.Schwani wrote: ↑Fri Dec 23, 2022 1:20 pm Loosing a seat really messes with my work flow. Like many others, I prep, slice, and preview in the office. Save a factory file to a server. In the shop load the factory file, and print.
But without a second seat I can’t do that. In addition V4 doesn’t load v5 factory files, so that route is off the table too.
I get the license bit, there are better ways….
That's a big yes and no.jeand wrote: ↑Thu Dec 29, 2022 2:39 amWith this method, can you run S3D at same time on office and shop machines ? I don't think so.jfkansas wrote: ↑Wed Dec 28, 2022 6:43 pmYou have a couple options now... Use the office machine to connect to the running version of S3d in the shop. It isn't too bad to do this. Or in the office machine save out a factory file and the file format your printer needs and save both to server. Go to shop and load factory file or print file as you normally would.Schwani wrote: ↑Fri Dec 23, 2022 1:20 pm Loosing a seat really messes with my work flow. Like many others, I prep, slice, and preview in the office. Save a factory file to a server. In the shop load the factory file, and print.
But without a second seat I can’t do that. In addition V4 doesn’t load v5 factory files, so that route is off the table too.
I get the license bit, there are better ways….
In general, it is bad practice to have a computer directly connected to a printer anyway.Instrumentation wrote: ↑Fri Jan 06, 2023 3:48 pmThat's a big yes and no.jeand wrote: ↑Thu Dec 29, 2022 2:39 amWith this method, can you run S3D at same time on office and shop machines ? I don't think so.jfkansas wrote: ↑Wed Dec 28, 2022 6:43 pm
You have a couple options now... Use the office machine to connect to the running version of S3d in the shop. It isn't too bad to do this. Or in the office machine save out a factory file and the file format your printer needs and save both to server. Go to shop and load factory file or print file as you normally would.
No:
You can't run v5 on the two different machines without buying it twice.
If you put you one v5 in the office, you can't decide to slice a v5 factory file on the garage/basement/shop computer that's still on v4.
Yes (IF):
Elsewhere on this forum, it's been stated that only one of your existing installations gets upgraded to v5, and the v4 installation is still valid and functional, and it will still run.
IF you use the Machine Control Panel function in v4, that will still send a Gcode file to your printer.
IF your workflow can substitute ".gcode" for ".factory", it's kind of the same. If you need to make modifications at the point of printing, you're SOL.
See Jake's comment: viewtopic.php?p=62723#p62723
For the record, this is a workaround, not a Good Thing(tm).