Jump to content

Flex727

MVP 2023
  • Posts

    3,259
  • Joined

  • Last visited

  • Days Won

    236

Everything posted by Flex727

  1. I've never seen the second message you show, but that looks like you're trying to update VisiLogic, not the firmware on your PLC. To update the firmware on your PLC, connect the PLC with the computer running VisiLogic and confirm you have a connection (Connection/Get PLC Information), then select the 4th tab over (tool tip says Operating System), then click the Check button. After that, follow the prompts and be prepared to wait about 5 minutes while VisiLogic updates your PLC firmware. You should then be good to go.
  2. This is a Job Board. Are you looking to hire a programmer to handle this, or at least help? If so, please feel free to email me at blanier @ arc-controls . com (remove spaces). If you just want a few questions answered, post in the Vision PLC Series and VisiLogic forum and you should be able to get the help you need.
  3. IS this MODBUS? There are limitations in the MODBUS standard for register reads.
  4. Do I understand you correctly that you are trying to read 255 registers at once via MODBUS? I believe there is a limit to how many registers you can read with a single Read Holding Registers command (a MODBUS limit, not Unitronics). Try breaking it up into multiple reads.
  5. Just use any unused MI to hold the value that will change depending on the state of MB 31.
  6. If the connection is lost, the socket is already closed, is it not? Isn't the socket being open the definition of a connection? Just reconnect. In fact, if you gate the socket connect function with an inverted contact of a bit that is on when the socket is open, you can trigger a reconnect as often as you like and it will do nothing until the connection is lost.
  7. Perhaps I don't understand what you're doing because it seems simple and obvious what to do. Use a buffer MI to store the value you want to go to the analog output. Use two rungs, one with a direct contact of MB 31 to store MI 20 to your buffer MI and a second rung with an inverted contact of MB 31 to store MI 22 to the buffer MI. Use the buffer MI in the Linearization function block.
  8. Well, that's frightening. I use that frequently and had no idea I was at risk of removing an operand that was in use. Not horrible, I suppose, since it's only removing the description. It sounds like there may be a bug in that routine.
  9. Which elements are not being found under View / Operands Not Referenced in Project?
  10. This is rare, but I've seen it happen, too. I do what you do - change something else inconsequential. The other alternative is to select Download All & Burn, but that is rather lengthy. I know Unitronics is aware of this as it was mentioned by the instructor in a training course some years ago.
  11. Have you looked at the "Projected Memory Map" under the Build menu?
  12. Hmmm, I was thinking of the Vision products. I agree that I don't see any applicable display System Integers. It does sound like a hardware fail, but you should check with Unitronics Support for any procedure they might have to troubleshoot. Just email with your problem description above to: support@unitronics.com.
  13. In the top-left corner of the on-screen text entry keyboard are two arrow keys. Pressing one of them repeatedly will cycle through all the available characters.
  14. Have you gone online and checked the value of the System Integers for contrast and brightness?
  15. The "Numeric Password" would be a separate entry. Place an MB in the "Legal Entry"box then use that bit to SET another bit to be used to indicate a password has been successfully entered. You can then use the successful password bit to turn on or off a "Disable" bit for the entries you want to protect. To log out, RESET the successful password bit.
  16. I'd be very surprised if you can get anything meaningful on a 0-10V analog input from a 0-20mV sensor, especially if it is a 10-bit resolution input.
  17. Absolutely not. You have two networks in each of ladder rungs 1, 2, 3, 8, & 9, and you have three in ladder rung 7.
  18. I don't have an M90 handy to test your logic, but before anything else, break up your logic so that you only have 1 single network in each ladder rung.
  19. Pull the Snap-In module off and re-seat it. I've seen this problem occur when there is poor contact between the PLC and the Snap-In I/O. If you have an environment with some vibration, place some tape around the interface between the PLC and Snap-In module to help it maintain contact.
  20. That's interesting, I've never encountered a V260. Is that a Vision, or Enhanced Vision PLC? When you say "did not make a difference", are you saying the same motor still had the problem even when you switched outputs or switched wiring? Or did the problem move with the switch? When you say you swapped out a V260 for the V560, are you using the same Snap-In I/O module after the swap?
×
×
  • Create New...