Jump to content

Flex727

MVP 2023
  • Posts

    3,325
  • Joined

  • Last visited

  • Days Won

    241

Posts posted by Flex727

  1. One of the nice things about Unitronics PLCs is there are several ways to communicate with them from your computer. Tell us exactly what method you are using, what type of cable, what version of Windows you are using, etc, and someone will help you troubleshoot.

    One other thing, mind if I ask why you would attempt to use the BETA version of the software, rather than the released version, if you are new to the software?

  2. 16 hours ago, Lacey said:

    I need to read multiple Modbus registers from a non Unitronics controller. These registers are not consecutive registers. What is the best way to do this? Multiple Read Holding Registers (3) one after another? Rung examples of your ideas would be most helpful and appreciated.

    Unitronics MODBUS communications are very forgiving in my experience. If the registers are non-consecutive, but not too far apart it's probably easier to read the entire vector that encompasses the data you want and then select what you need via ladder (as Ausman suggests above). If the registers are too spread out (total vector >120 registers) then you can certainly do consecutive reads. If there are a large number of them, then set up timers to read them individually, but if you just need a small number read, they can be read in the same cycle. The example below shows both a read and write in the same PLC cycle (using MODBUS TCP/IP). The second one just waits until the first one is complete (due to MB 20).

    If you're not sure, just try it - you won't break anything.

    image.png.6059a4d0e488bbc7ccdb333da4c56f01.png

  3. In your Master program your MODBUS Config and MODBUS Read DT you are identifying the slave IP address as 172.16.0.0, but your slave is 172.16.0.1.

    Also in your Slave program, delete the line from your MODBUS config (Index 0) where you identify a slave IP address - that's what gets entered into the Master config, not the Slave config. It probably just ignores it, but delete it anyway.

  4. 49 minutes ago, Roho said:

    you hit stop when the motor is off and the off timer just keeps on going

    I presume that the only reason you care is that next time you hit START you want it to stay stopped until the off timer completes the previous cycle. If that's the case, given the logic you currently have in place, it looks to me like the easiest way would be to add a latch bit that indicates the status of the last press of the start or stop button, as follows:

    image.png.77b12e089bef50724ca732882b9892ac.png

  5. 2 hours ago, Roho said:

    I'm sorry to bother ya'll, I'm just fumbling my way through this and realized a little help would be necessary.  Thanks for any and all help you can give.

    Help is what we're here for, especially when you're attempting to work your way through it and not just asking for someone to write your program for you. I'm not sure why the Timer section of the help file got lost, but I'm sure Cara will get it fixed. I recommend not using the Beta version of the software for your first program.

    Were my suggestions on how to deal with the timer issues clear? I'm attaching a pdf of the Timers section from a previous version of VisiLogic that should help you understand the 3 different types of timer that VisiLogic offers. While it's fewer than the 15,000  :) different types A-B offers, these 3 (TD, TE, & TA) WILL get every job done with some careful thought.

    Timers.pdf

×
×
  • Create New...

Important Information

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