![]() mer files down to version 5.something it's the only version of View I need, really. According to Rockwell even version 20 is fully compatible with Windows 10.Īlso, with FactoryTalk View 10 they added the ability to import projects that use those old 32-bit Wacom SQL tag databases so there's no need to keep a VM with Version 6 on it just for conversions to 64 bit. I also have an implementation of DosBox running the SLC-150 software just in case.īut I'm currently running Windows 10 on my host and have versions 20, 24, 28, 30, and 32 installed of Studio 5000. I only have one separate VM for Rockwell stuff and it's a Windows XP 32-bit for the 20+ year old software. We haven't run this in a VM yet, I don't know if we have enough licenses to do that and they are EXPENSIVE. Any help is greatly appreciated! I have looked all over trying to figure out how people are fixing this and have come up with nothing. ![]() I've got a ticket in with Rockwell Support with our contract, not sure they will come back with something useful. All other versions of Rockwell worked fine before the v32 deployment. V24, v28 and v32 is the current setup we are trying to go with now. What issues did you have and what did you do to fix them? All I get is CRITICAL PROCESS DIED in the BSOD. ![]() I run the IT department and can't seem to figure it out, our PLC guys and guys in the field are having the same issues. Out of the 8 laptops we have tried to install Version 32, 4 of them have worked fine. We are having tons of issues with Rockwell causing BSODs on brand new laptops. ![]() I have been in startups with Rockwell startup techs that refuse to use it unless they're forced to. Drive executive always just works- it has it's limitations, but just works. As I'm sure you are aware, they are integrating the CCW feel into Studio. They cause the software to crash incessantly. The AOP's I have used for the 755's are instable to say the least. In order to tune the drives (if you need to) you have to afi the jsr for the drive control file, and do it from the keypad. Now the proper error message will be displayed and allow a safety signature reset. Then you will need to change it back, download, and re install your safety logic and download again. You will then need to delete any references to the safety tags in your safety routine, and download. Basically, if you have any issues during commissioning with safety signatures, you will need to go into the AOP, and set it from standard and safety, to standard only. The network STO is great once up and running, but Rockwell is well aware that it hasn't done a great job implementing it, and it's "actively being worked on". 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. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |