Jump to content

Flex727

MVP 2023
  • Posts

    3,325
  • Joined

  • Last visited

  • Days Won

    241

Posts posted by Flex727

  1. 1 hour ago, Vinicius said:

    What happens with the timer 2, is that, when it ends, and in the display is showing "00:00", right? So when I leave the screen and go back after, still is showing "00:00". But when it starts, it changes to 00:04, 00:03, 00:02....

    This is normal operation. The Preset gets loaded into the Current when the timer start is initiated or if the timer is reset. If you want the timer current to show 00:04 when you go to the screen, do a timer reset at screen load.

  2. 9 hours ago, Gugun said:

    Is it very very safe to replace the battery when V570 powered on, without back up data before?

    I don't think it's safe EVER to run a PLC without some backup precautions haven been taken. Eventually something will happen requiring need for a backup.

    9 hours ago, Gugun said:

    How many seconds can we replace the battery without losing data when the V570 is on (because I don't have a PLC program).

    The battery is only used when the 24V power is disconnected from the PLC. If the PLC is powered on, then there is no time limit for replacing the battery.

  3. I've also successfully extended the expansion cable with a standard Cat 5 Ethernet cable. Note: extended, not replaced, as the pinout is different between the expansion cable and an Ethernet cable - you have to use an Ethernet coupler and a straight-thru Ethernet cable and make sure the direction is correct per the labeling on the expansion cable.

    And as Joe suggests, these modifications are problematic in high noise environments.

  4. Reset is a soft boot (like ctrl-alt-del on a PC in the olden days). Initialize loads a zero into every operand.

    I've never found Initialize & Reset to do much, however, loading a blank project often does wonders to correct all sorts of issues with the PLC. If your PLC is acting up, by all means try the Initialize & Reset routine, as it's quick and easy. But if the problem persists, load a blank project, THEN Initialize & Reset, then re-load your original project. That sequence has never failed me when it's anything other than an actual hardware failure.

  5. I'm having trouble understanding how this could be a problem. This error message is new (didn't exist in previous versions of UniLogic) and is very annoying. A compile warning should not be generated for every single instance of a standard function block used in a normal way. This type of warning belongs in the Help file, not on compile.

    @Cara Bereck Levy, can you take a look at this? Feel free to PM me if you want more details.

  6. Anyone want to attempt to interpret this warning alarm?

    "Inserting rows to an 'Indexed Data Table' when the insert index in a small number can increase scan time and cause a CPU Watchdog."

    Is there a typo in the message? This warning didn't exist in an earlier version of UniLogic and I'm not sure what to do about it.

  7. My personal policy is to ALWAYS avoid conditional subroutines. There just isn't any good reason for them. Write your code so that every ladder rung is executed on every scan and you will avoid unnecessary grief.

    17 hours ago, viscoelastic said:

    Under that circumstance would it still be bad practice to reuse coils that were in another routine even though they cant be called at the same time?

    In VisiLogic with Vision PLCs, you have 8192 coils. Are you running out?

  8. - MODBUS Config MUST be activated by a Positive Transition (or SB 2).
    - You cannot initialize multiple sockets to the same port number. Remember that the Port number in the Socket Initialization FB is for the PLC. You assign the Port number you are connecting to in the MODBUS Configuration and the Connect functions. The PLC port numbers and the slave device port numbers are unrelated.
    - Do NOT place more than one logic thread in a ladder rung (such as you have in rungs 6-8 & 14.
    - Your 3 slave devices need to have different IP addresses, which is placed in the 3 MODBUS config blocks and the Connect blocks (each MODBUS Config must match with the corresponding Connect).
    - The R.H.R. must be associated with the corresponding Configuration block.

    The sequence you want for MODBUS TCP is as follows:
    1) Initialize Ethernet card
    2) Initialize Socket
    3) Configure MODBUS TCP
    4) Set a bit to connect the socket to the slave
    5) Perform the Socket Connect
    (All of these are usually activated by SB 2)
    6) Reset the connect bit at the end of the connect rung
    7) After connection is established, perform the R.H.R. (or other MODBUS command) communication at the required interval.

    You can read from 3 different slave devices simultaneously if they each use a different socket. Each socket is independent.

    In order to read multiple registers, they either need to be addressed closely enough to read a vector that includes all the data you want, even if you don't need some of the data in between, or you will need multiple R.H.R. functions that are called separately with a small time interval to allow each read to complete.

    There are example projects that came with your VisiLogic installation that show this in detail. They included projects specifically for the V700. Take a look at those for help on this.

×
×
  • Create New...

Important Information

This site uses cookies. By clicking I accept, you agree to their use.