grasshopper

MrPLC Member
  • Content count

    4
  • Joined

  • Last visited

Community Reputation

1 Neutral

About grasshopper

  • Rank
    Hi, I am New!

Profile Information

  • Country United Kingdom
  1. PLC5 to RS Logix5000 advice needed

    Oh Christ!!!!!!!!
  2. PLC5 to RS Logix5000 advice needed

    I honestly cant see a conversion done here, simply for the cost implications and the view of 'if it aint broke, don't fix it'. I am fully aware that if it does break tho, we are in a mess and we will have 200 operators stood around doing nothing!!   I honestly never even considered a windows version of PLC5 - this could be an avenue to investigate as I cant see it being out of the realms of possibility expensive...   Thanks   Mike  
  3. PLC5 to RS Logix5000 advice needed

    Thanks all for you replies.   pcmccartney1 - Yes, the main intention is to try and make the 'engineering station' easier to use for the shift electricians and more user friendly than using the dos system that only uses F keys. As I said earlier, my Allen Bradley experience has been with Logix500 and this has always been adequate for minor program changes and bit forcing etc which is the only thing that day to day, month to month we will use it for other than IO fault finding. Your suggestion of having the engineering station with all the software versions sounds spot on tbh but I can imagine setting it up with licences etc will cost thousands of pounds. I think that this will be a sure fire way that the costs will never get approved (and possibly historically why it was never done by my predecessor).   Joe E - I understand what you mean about manually transcribing the code.   It seems that I (wrongly) assumed that having the code in Logix5000 would still allow connection to the old hardware (field racks and processors) via a DH+ card in the new PC, it would just make the reading and navigation of the code much more user friendly.   Obviously this has a low priority rating in regards to cost with the people who hold the purse strings, but I am trying to avoid us getting into the position where the only PC (engineering station) dies and then we have no access to the code or indeed the backups (which I now have on floppy disks!!)   I just want to get the point where I have a PC (that's not 30 years old) with a user friendly front end that I can back up after modifications easily.   The reason that I am looking at Logix5000 is that I have it on the laptop so I know I wont have to factor in that cost....    As Im sure you have all realised by now, this is my first foray into the program/operating system/networking side of PLCs. In my experience there has always been a device (laptop/PC) that has used windows based software (Logix500) to interrogate and modify projects.   Again, thanks for all your help, it seems like I need to think about other options than just simply relying on using logix5000 just because I already have it...…..    
  4. PLC5 to RS Logix5000 advice needed

    Hi. First of all, I haven't worked with Bradley PLCs for 7/8 years and when I have in the past Ive only used RS Logix500. I have recently changed jobs and have 'inherited' a minefield of very old Allen Bradley PLCs and software. Basically, I want to replace the 'engineering station' that is connected to the site PLC network via DH+ and is running PLC5 software through DOS. I have been given a laptop with RS logix5000 on, so I plan to convert the 'projects' for all processors to files that can be opened in logix5000 and then I can get another licence and upgrade the engineering station to a more user friendly version. To be able to use the translation tool, I need to create a .PC5 file from the project on the old engineering station. I have tried saving one of the processors code to a floppy disk, but it creates multiple files with .$xx extensions (or similar). Is it possible to create the .PC5 file directly from the PLC5 program on the engineering station? Is there another way of doing it that Im missing?   Obviously, I am up against a myriad of issues: 1. The engineering station only has floppy drive. 2. This PC Im typing at now doesnt have the Logix5000 software on it. 3. The laptop that has the Logix5000 has no internet connectivity, it does however have a virtual PC running XP and SLC500.   Any help on how to proceed is much appreciated, I feel like Im in a race against time because if the engineering station dies then we have no way to connect to the PLC network and interrogate the logic or IO.....   Thanks in advance    Mike