Steve Bailey

MrPLC Member
  • Content count

  • Joined

  • Last visited

Community Reputation

100 Excellent


About Steve Bailey

  • Rank

Contact Methods

  • Website URL http://
  • ICQ 0

Profile Information

  • Location Berkshire County, Massachusetts
  • Country United States

Recent Profile Visitors

14013 profile views
  1. Upload failed

    I've just about run out of ideas. The inability to upload either ladder logic or hardware configuration while still being able to upload data tables suggests that an OEM password is in place. But the message from Logicmaster is not what I've seen when I try to upload from a CPU with an OEM password. Another possibility is that the original programmer could have chosen to lock one or more of the program blocks. Program blocks can be view locked which prevents anyone from or edit locked which prevents anyone from modifying them. View locks and edit locks can be passworded or permanent. There is also the possibility that the program was not written in ladder logic, but in that case I think you can still upload the hardware configuration.
  2. Upload failed

    What CPU model?
  3. Upload failed

    What port on what module are you using for communications? The ports on a communications coprocessor module (IC697CMM711) can't be used for program upload or download.
  4. Upload failed

    It is possible that the original programmer set up an OEM password. If that is the case you won't be able to upload. The message in Logicmaster would be "Insufficient privilege for requested operation". An OEM password is one level higher than Level 4. It's also possible that the project file you opened is set for a different CPU model than the one actually in place. I think Logicmaster's prompt for that scenario is to ask if you want to modify the upload for compatibility with the CPU model in the project file, or words to that effect. It could also be a Logicmaster or Proficy version issue relative to the firmware version in the PLC. Details on the message you get when you try to upload will help narrow down the possibilities.
  5. GE Fanuc problem

    Upload the program logic and reference tables from the PLC. Create a new project file and copy what you just uploaded to it. Manually configure the CPU settings and module information in the new project file. Download to a spare CPU and install it in place of the one currently working. Once you are satisfied that it is working properly you can clear the memory in the original.
  6. GE Fanuc problem

    According to what is showing on the screen you are currently at level 4 access. Are you trying to assign a Level 4 password to a PLC that currently doesn't use one? What message do you get when you press "Y" from the screen shown? I think you need to stop the PLC in order to set a password. The password is part of hardware configuration and you have to stop the PLC to change hardware configuration.
  7. GE Fanuc problem

    Are you sure you set the password for level 4 and not for OEM protection? I'm also assuming you're not trying to use the colon ":" character as part of the password.
  8. GE Fanuc problem

    Is your problem that you can't remember the password you set back in 2017/ Or is it that you can't remember where in Proficy to enter the password for the access level you need?
  9. Restoring a WorkmasterII

     Try the model P70 v1.04. But it probably won't have the file for the WSI card. There is also a "discovery " program called IDMCA which will scan the Micro Channel bus for installed cards and report what it finds. A couple of years ago I helped a customer with Series Six PLCs in two different facilities put together a pair of functional Workmaster II computers from model P70s he picked up on ebay. I found a pair of 3.5" floppies, one llabeled "WMII System Config", the other "IDMCA". I'll try to make copies of them. I still have an old NT machine with a working 3.5" drive. The laptop with the hard drive that crashed (Windows XP) also had a 3.5" drive but it could not always read from the floppies after the NT laptop wrote to them. Email me at stephen dot bailey2 at verizon dot net with an address to send the floppies to. Where are you located? I'm expecting snow tomorrow also.
  10. Restoring a WorkmasterII

    Try here: I'll also look around for an old system disk with the file(s) for the WSI card. I had an old laptop that had a copy of the WMII system disk, but its hard drive died several months ago.
  11. GE online Catalog?

    This thread is more than fourteen years old. Also, given the context of this site, any GE catalogs are of limited relevance. GE has sold their PLC business to Emerson.
  12. Error 8287 Upload Ge Fanuc 90-30

    The upload process extracts the entire program. You can't exclude individual program blocks from the upload. Also, the uploaded program will not have any variable descriptions or rung comments. What software was used to create the backup project file you have? If you imported a Logicmaster or VersaPro project file into Proficy, when you go online with the PLC it will always show as not equal due to the change in software platform. You have to perform a download to achieve logic equality, even if the project file you imported is actually the same as the program running in the PLC. Try this. Open your backup project and try to find the offending rung in the subroutine. Correct the rung. Then get another CPU module. Download the corrected program to it and use it in place of the existing CPU350 to make sure if it correctly controls your machine. That way, if the backup program isn't the latest, you still have the correct version on the original CPU. Be sure to attach a battery to the CPU module when you remove it from the rack.
  13. 90-30 Rack Modules repeated loss/gain

    Since all of the modules in the rack are simultaneously dropping out and reappearing, the next most likely culprit is the baseplate and not the individual modules. Check also to make sure the expansion cables are tightly connected to the rack.
  14. ModBus RTU error code 263 (CRC)

    I have to concur with your conclusion. Unfortunately I know nothing about configuring a Beckhoff PLC so I can't offer any suggestions. The checksum calculation is a check on the integrity of the data transmitted between the two devices. The sending device includes a two-byte checksum in the message it sends. The receiving device performs the same calculation on the message it receives, compares the checksum it calculates against the checksum it receives, and returns a fault response if they don't match. That was the basis of my questions about Modbus RTU vs Modbus ASCII and byte swapping. The checksum calculation for a Modbus RTU transaction is different than the checksum calculation for Modbus ASCII. The checksum calculation will be different if one device takes the low byte of each message word before the high byte and the other device takes the high byte before the low byte.
  15. ModBus RTU error code 263 (CRC)

    The port setup looks OK. What command were you sending to the Beckhoff? The error code suggests that the checksum returned by the RTU slave is incorrect. If the Beckhoff shows a similar error when it receives the command from the VersaMax, it sounds like a difference in the way the checksum is calculated. Are you sure the Beckhoff is using Modbus RTU and not Modbus ASCII? Have you tried using Modbus master software running on your PC to test the Beckhoff's response? Edit: Or could the Beckhoff be interpreting the bytes in the opposite order of the way the VersaMax does?