Jump to content

Flex727

MVP 2023
  • Posts

    3,236
  • Joined

  • Last visited

  • Days Won

    234

Everything posted by Flex727

  1. I just tried it and it downloaded fine. What's the problem you're having?
  2. Yes, operand values are lost when the battery dies and mains power is removed. Keep the PLC powered up and the battery is irrelevant. There is a system operand that warns when the battery is low. To replace the battery in a V1210, simply open the battery door on the back, pop out the old battery, and pop in a new one (CR2450). No need to shut down the PLC. It is also possible to save the operands on an SD card if the PLC program has been set up to allow that. There are also other programming techniques to retain specific operand values.
  3. I have a V1210 in the field that connects to 15 different devices using MODBUS TCP with a single socket with this technique. It has been working flawlessly for 10 years without a hiccup. It takes a little over a minute to work its way to all 15, but it's functional.
  4. Normally, the SCADA is the Master and the PLC is the Slave. However, did you configure two different sockets as MODBUS Masters to connect to your redundant SCADAs?
  5. Go to 5:50 in this video to see how to connect to your PLC. Then select Upload rather than download as he does in the video.
  6. Moved to the Vision forum. Yes, you can connect with USB. Obtain and install VisiLogic, install the USB driver from within VisiLogic, then you can connect with a mini-USB cable. However, it is unlikely you'll be able to download the program to your PC. The program would have needed to be downloaded with the upload feature, but that is not the default. Go to the pinned posts in this forum (Vision) to learn how to do all this and review the VisiLogic Help once you get it installed.
  7. Right-click in the empty HMI window you're copying to and select paste.
  8. I currently have 11 different VisiLogic versions installed on my desktop and my laptop and it all works flawlessly. When setting up a new PC, I follow this procedure: 1) Install the oldest VisiLogic version first, then rename the folder in C:\Program Files (x86)\Unitronics\Unitronics VisiLogic_C to something else (such as Unitronics VisiLogic_C - 9865, for version 9.8.65). The folder name is what will show up in Version Swapper so you want to be able to recognize which version you're swapping to. 2) Install the next oldest version and repeat until all versions are installed and renamed. 3) Use the Version Swapper from the newest version (VisiLogicVersionSwapper.exe) I think the "swapper versions" available online do not need to be installed - just unzipped to the Unitronics folder (not sure).
  9. Also, all the warning messages regarding changing a bit and then reading the value in the same net indicates to me that you are overcrowding your ladder nets. Keep your nets as short and simple as possible. Break them up into smaller chunks whenever possible. The only thing you have to be mindful of is that coils cannot be duplicated (except for Set & Reset coils) and must have assignment in one ladder net only.
  10. The compile error tells you exactly what to do. Cut half the ladder rungs from the subroutine and place them in a newly created subroutine then call that subroutine immediately after the original one. I see that the problem exists with the Main Routine. I don't have version 9.9 installed yet so I can't look at your program, but if your Main Routine is too big then you have serious problems with your programming style. Subroutines exist to break up your code into manageable chunks, typically separated by function. The Main Routine should only have configuration function blocks, as needed, and the called subroutines. You shouldn't be putting your entire program into the Main Routine.
  11. The error message says to contact support. I highly recommend doing that. This forum is not support. It is a user forum staffed primarily by volunteers who are users just like you.
  12. In VisiLogic from the menu just above the ladder window, go to FB's / Loadcell / Help and it will take you directly to the Loadcell help page. There you can learn all about configuring, calibration, Tare, etc for your Loadcell module.
  13. Any critical value that the programmer knows will not need to be changed by the user should always be set in a power-up. That should be SOP.
  14. I don't use UniLogic often enough to remember enough detail to answer your question definitively, but one universal solution is to incorporate a "heartbeat" function within your communications. If the heartbeat stops changing for the appropriate period of time, then reset your bits (or registers).
  15. This is silly. You want flash memory to store data in the PLC? Unitronics has supplied the facility for adding flash memory to the PLC. An SD card is just additional flash memory for you to use as needed or as you see fit. Nothing artificial about it.
  16. Quit making me feel like an old man - my joints already do that!
  17. Require a password to change the value of SI 50 or password protect a button for SB 36, or place the button on a screen not accessible remotely.
  18. You can also save all the Operands to an SD card. You can do this from ladder and it only takes seconds for the operation to complete. You can also save a complete clone file to the SD card but that can take several minutes.
  19. Multiple problems: 1) Get rid of ladder rung 2. The SCAN_EX FB is for when the PLC is the slave. 2) With MODBUS you need to CONNECT to the slave device. Check the example projects that came with your VisiLogic installation to see the proper procedure for performing the connect function. 3) It looks like your vector that receives the data, starting at MI 12, is of length 4 yet you do not have 3 additional unassigned MIs for the data to go without overwriting MI 15.
  20. The Socket Initialization FB determines master or slave. Ignore the "Default:" statement in the MODBUS configuration FB. It is true that is the default, but the Socket Initialization overrides. You can use any of the 4 sockets for any purpose. Just initialize them the way you want them. It's best not to have two or more sockets set to the same port number. As I said, you appear to be using Socket 3 for your comms, but you are configuring your MODBUS to use socket 2. Change the MODBUS configuration to socket 3. And again, ignore the "Default:" statement that appears there, just choose the correct socket number.
×
×
  • Create New...