Jump to content

Flex727

MVP 2023
  • Posts

    3,231
  • Joined

  • Last visited

  • Days Won

    233

Flex727 last won the day on March 14

Flex727 had the most liked content!

About Flex727

Profile Information

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Flex727's Achievements

UniGuru

UniGuru (4/4)

390

Reputation

  1. Stop doing that. Stay with the VisiLogic version you originally programmed the software with. Unless there is a specific feature you require or a specific bug fix that has hindered you, do NOT routinely update to the latest VisiLogic version. PLCs are not like PCs where you always want the latest version of the app.
  2. This is very confusing. The PLC never requires an O/S update on its own. In fact, we recommend that the programmer never update the O/S once the PLC is in production. If your PLC will not boot properly when power cycled, then you have another problem that must be addressed. If you are periodically removing mains power and the program is lost, then it sounds like you need to replace the battery. I don't believe that causes the O/S to be lost, so there may be another issue at play. All that said, though it's not recommended by Unitronics, it is possible to update the software and/or firmware via ethernet.
  3. Likely because Unitronics starts their addressing at zero and the other device begins at one. This is a common issue.
  4. Never say never, but in general it's bad practice. The reason is that it's easy to leave coils in "limbo" causing unexpected results. If you're very careful and know what you're doing it can work fine. That said, don't do it anyway. Yes, this is the proper way, IMO.
  5. Thank you for the link! I checked it out and it seemed to go deeper into smaller bits of best practices instead of creating a baseline from where to restructure my program. I can't really seem to find a answer to problems I currently am encountering, but I will post a question in this forum if this is more appropriate. I hope you caught this message:
  6. There is an entire forum here on this board dedicated to this question. https://forum.unitronics.com/forum/61-best-programming-practices/
  7. As Dan correctly points out, transition contacts are limited in your PLC program. The reason for this is that in order for the transition contact to work properly, memory must be set aside to "remember" the state of the bit operand on the previous scan. The size of the block of memory set aside for transition contacts varies by PLC model from 256 to 1024, but sometimes the actual compiled number of transition contacts is greater than what you can count in ladder due to the result of the STL translation from ladder that actually gets compiled.
  8. The .vlp file typically does NOT have the operational parameters you're looking for.
  9. Did you review the Help entry as Joe suggested? It is very clear and performing the action you need is very simple. Please keep in mind that this is a user forum staffed by volunteers with actual full time jobs. This is not official Unitronics Support.
  10. I've seen this in the past when the Snap-In module works loose. Be sure it's snapped in tightly and consider a bit of duct tape to hold it tight. This is especially a problem in a high vibration environment.
  11. You can find the IP Address in INFO Mode (see the Help file for more information). However, if this is a new PLC that does not have a program in it, you are better off connecting with a USB cable until you get a program downloaded that has Ethernet initialization and IP Address assignment.
  12. Aus, UniLogic is a totally different beast when it comes to button presses. In VisiLogic, pressing a button activates the associated MB. The MB is on for as long as the button stays pressed and turns off when the button is released. It doesn't work that way in UniLogic. Button presses can have a variety of "Actions" associated with them and there is no action that performs like a button press in VisiLogic. If you want the button to behave the way it does in VisiLogic, then you Set the operand on press and Reset the operand on release. This is totally independent of Set & Reset you are familiar with in ladder.
  13. Copy the VisiLogic folder (in the C:\Windows\Program Files (x86)\Unitronics folder) of the 1st instance (the one that is currently working) on top of the VisiLogic folder of the 2nd instance (the one with the error message) and allow all the files to replace or copy over. That should solve your problem. I keep a working copy of every VisiLogic folder (I have 23) on another drive ready to replace any corrupt VisiLogic folder at a moments notice. I haven't seen the exact error you're experiencing, but I've had my share over the years of corrupted VisiLogic files and this is the best solution I've found.
×
×
  • Create New...