![]() Setting up a nice VM from scratch takes a lot of time, but in the end if makes easier to have the whole group of programmers using the same software versions. VMware Workstation PRO is our choice and we usually stay updated with the last version. The main VM is around 200 GB in size, but we're using pretty buffed up machines, so that's not an issue. ![]() We also use a different VM for Rockwell, but that's all. ), so I just stuck them on a nice Windows 7 VM and everything is working fine. Moreover I'm using tons of other OEM softwares (Keyence, Cognex, Atlas. I've set up my main virtual machine with tons of different software versions from Siemens Magic World: Simatic Manager, TIA Portal from V13 to V15.1 (and counting.) with all their addons, Scout and so on. Oops, computer broke, no biggie, copy VM to new machine, get back to work. It is way faster to copy a VM than to install a bunch of software, so Engineer one can do it, and then give the VM to engineers 2-5 also in the project. There are a lot of features that make VMs great. I've never had an SSD fail on me, I'm really curious what they're doing to make that a common occurrence. Maybe installing the new one breaks some carefully configured macro you barely got working ages ago. Maybe they can't be installed side by side. Maybe it doesn't work because of operating system compatibility. This would be analogous to needing Word 2003, 2010, and 365 on the same computer. ![]() It is often required when you need different versions of the same software to support different customers. I know lots of engineers who have multiple brands installed without VMs, but they are the exception rather than the rule. The test platform is "windows, our newest software, and nothing else" they don't care about bugs that affect anything else. It is also fairly common for industrial controls vendors to have bloated shit software where they don't fix non-critical bugs. It is less necessary now than 5-6 years ago, but it often makes sense. It saves me a ton of time for situations of data loss or upgrade.Ī lot of older packages don't play nice because they never let go of serial ports, and that was the only comm mechanism back in the day. Setup new base machine, re-copy backup VM's, restore customer files from backup. With VM's I can be back up and running in about 2 hours. That's days of me not working on projects. Before the VM's if my laptop crashed it was days of restoring and reinstalling software to get back up and running. Did RW just release a big update? No problem, George setup a VM for it and now everyone can download it at will.įour, my ability to recover. Three, it makes it easy to stay updated and in sync with the other techs in my office. I pretty much have my hands in many many different types of PLC's and SCADA systems and it would be a nightmare to have all that on one computer. Reduces the need to have a big bloated system with a ton of different programs. It allows me to keep types and projects separated. So it pretty much stops me from running 95% of the automation software out there. I have a four reason use case for having multiple VM's.įirst reason is I run Ubuntu as my base machine. Please click "report" on spam Related sub-reddits: (*) At mods' discretion, certain self-promotion submissions from people who contribute to this sub in other ways may be allowed and tagged with the "Self-promo" flair
0 Comments
Leave a Reply. |