从云端3D打印无法控制

嘿大家，
我们都知道从云中定期打印。
这就是当您点击连接到网络打印机的VM内的打印按钮时所执行的操作。
现在我们可以为此类工作流添加第三维。
许多CAD用户已经在为Solidworks或Autocad工作使用GRID加速的VDI会话。
您已经在远程环境中体验到同类最佳的DirectX或OpenGL CAD性能。
......但是当你制作一个物理原型时，你如何采取下一步？
您可以下载您的模型，并将其带到研讨会。
但是如果你有办法直接从云中的CAD模型转向现实生活中的对象呢？
然后你不必在巨大的（可能是敏感的）CAD文件周围进行操作，并且版本控制不会成为问题，因为你总是在最新的副本上运行。
借助GRID加速的VDI和3D打印机，您现在可以。
今天我在墨尔本大学的3D打印工作室进行了一项实验，我很高兴地报告它取得了巨大的成功。
我设法连接了UP！
加上2台打印机到VMware Horizo​​n View内部运行的VDI会话。
我的会话流式传输到Wyse P25零客户端端点。
这就是我做的。
将3D打印机的USB电缆插入零客户端设备后，它立即在VM内注册。
但是，我需要手动将Windows驱动程序更新指向安装了制造商软件的Drivers文件夹所在的位置。
在那之后安装驱动程序是快速和无痛的。
完成后，在VM内部运行的3D打印软件通过本地USB连接与3D打印机完美通信。
在我的GRID加速会话中，一切都很黄油。
当我在软件中旋转和缩放时，即使加载大型模型也对远程体验提出了很小的挑战。
当然，如果我需要进行任何更改，我可以直接进入我已经在后台打开的Solidworks（在同一个VDI会话中）。
看着设置，我真的很惊讶。
如果你追踪电线，它会：
3D打印机零客户端数据中心
这是一台移动并与现实世界交互的3D打印机---构建物理对象--​​-直接从云端发送命令。
如果我有无线设置，打印机将无法控制！
随着CUDA在云中运行GRID的强大功能，我可以看到这取代了机器人和其他自主设备上庞大，耗电的处理单元，这些处理单元需要根据实时输入做出瞬间决策。
当我进行进一步的实验时，我会回报。
如果您对此区域感兴趣，请随时通过电子邮件或社交媒体与我联系。
干杯，
麦克风



以下为原文

Hey everyone,

We all know regular printing from the cloud. It's just what you do when you hit the print button inside a VM, connected to a network printer. Now we can add the 3rd dimension to this type of workflow.

Many of you CADers out there will already be using GRID-accelerated VDI sessions for your Solidworks or Autocad work. You're already experiencing best-in-class DirectX or OpenGL CAD performance in a remote environment.

...but how do you take the next step when you're produce a physical prototype? You could download your model, and take it to the workshop. But what if you had a way to go directly from CAD-model-in-the-cloud to real-life object? Then you wouldn't have to lug around huge (and possibly sensitive) CAD files, and versioning wouldn't be an issue since you are always operating on the most up-to-date copy.

With the help of GRID-accelerated VDI and a 3D printer, now you can.

Today I conducted an experiment at the University of Melbourne's 3D printing studio, and am very happy to report that it was a big success. I managed to hooked up an UP! Plus 2 printer to a VDI session running inside VMware Horizon View. My session was streamed to a Wyse P25 zero client end point.

Here's what I did.

After plugging in the 3D printer's USB cable into the zero client device, it immediately registered inside the VM. However, I needed to manually point Windows driver update to the location where Drivers folder inside where the manufacturer's software had installed. Installation of the driver after that point was quick and pain-free.
Once done, the 3D printing software running inside the VM communicated perfectly with the 3D printer via the local USB connection.

Inside my GRID-accelerated session everything was buttery smooth. Even loading up big models presented little challenge to the remote experience when I rotated and scaled within the software. Of course, if I needed any changes made, I could jump straight into Solidworks which I already had open in the background (in the same VDI session).

Looking at the setup I was really quite amazed. If you trace the wires, it goes:

3D printer <--USB--> zero client <--Ethernet--> datacenter
Here was a 3D printer moving and interacting with the real world---building a physical object---being sent commands directly from the cloud. If I had a wireless setup, the printer would have been controlled out of thin air!

With the power of CUDA running on GRID in the cloud, I could see this replacing bulky, power-hungry processing units on robots and other autonomous devices that need to make split-second decisions based on real-world inputs on the fly.

I'll report back as I conduct further experiments.
Please don't hesitate to reach out to me via email or social media if you are interested in this area.

Cheers,
Mike