Jump to content

Flex727

MVP 2017
  • Content Count

    1,731
  • Joined

  • Last visited

  • Days Won

    127

Everything posted by Flex727

  1. Yes. The PID Config without Auto-tune is an older version that remains there for non-Enhanced Vision products. Your V570 is an Enhanced Vision product and should use the PID Auto-tune FBs. Besides the P, I, & D, be sure you enter values for: Sample Time Process Value Low & High Control Value Low & High and of course, target value.
  2. Oh, I see I may have misinterpreted your question. You would still use the PID Auto-tune even if you don't plan to use the Auto-tune functionality.
  3. Assuming you are using a Vision PLC (you also posted this question in the UniStream forum), then you can always determine and set P, I, & D, with or without Auto-tune. When you set up the PID Configuration, you assign operands to the P, I, & D. Just manually place values in those operands, either through HMI entry or Power-Up and you are good to go.
  4. To my knowledge, Ausman is correct. This function is only applicable when communicating between Unitronics Vision PLCs (doesn't work with UniStream either).
  5. There are example projects - you just have to download them separately. Go Here: https://unitronicsplc.com/Download/Support/UniLogic/UniLogic_Example_Projects.zip
  6. Moved to the correct forum. It looks like the help file could be a little more clear, but the bottom line is that the Vector: Store function always overwrites the register or bit at the location A+B. It will only overwrite A if B=0.
  7. Took a quick look at your master program. Using the Legal Entry bit is a good way to go here, but I would do it this way. You have a lot of superfluous stuff you don't need (timer, etc).
  8. I've been meaning to ask you, Joe. Do you have a preferred cigar brand?
  9. You're too kind. My approach, as is most of the other experienced members on this forum, is not just to answer questions, but to teach. More education helps the user and anyone else browsing these boards. I could have written your program for you in about 2 minutes flat, but you would not have benefited as much. We all learn best while doing, not watching.
  10. I haven't had time to review your code yet, but I'll make a general statement. Typically there isn't an easy or elegant way to have a master control in two different places. In any system there can only be one master if you want straightforward code, at least in my experience. If you need two different masters controlling the same thing you generally have to think it through very carefully and the algorithm will have to be tailored to the exact situation. You have to deal with communication timing and register overwrite. It can easily become a mess, especially if you don't fully understand the underlying mechanics. If someone smarter or more experienced than me comes along with elegance, I am definitely interested in learning along with you.
  11. You will also need to know the PLC name to connect with VisiLogic. That's also available from INFO Mode.
  12. -You don't need anything in the bottom part of the MODBUS Configuration in the slave. -You really don't need anything gating your SCAN_EX FB in the Slave. Just hang it directly on the left rail. -Place your MB 0 (Ready to connect) after you MODBUS Configuration, not before. You're NOT ready to connect until you've configured your MODBUS communications. It doesn't really matter since the config does occur before MB 0 gets used, but it's the principle of the thing. -Use a Direct Contact of SB 13 instead of a Positive Transition of SB 3. -You don't really need the delay timer TD 0. None of these things would stop your program from working, but I'm trying to help you with best programming practices. MODBUS is simple and straightforward. It's also very universal. I use it whenever possible. The only thing you have to watch for is getting all the details right. Once you've done that it's smooth sailing. Feel free to ask about any of these suggestions if you're curious.
  13. Just for clarity to everyone following this saga. The EXL-CAB295 is for the EX-A2X, NOT the EX-A1!
  14. I know this is a stupid question, but I've been caught by this. Do you by any chance have an Ethernet module installed in the PLC and is there any chance you're plugging the expansion cable into the Ethernet port instead of the expansion port?
  15. Store the value in a temporary location immediately after transferring it. Compare the new value to the stored value (+/-5). When the new value is greater than stored value +5 or less than the stored value -5, then send the new value and store it again to the temporary location.
  16. I just caught this. Sorry, I was referring to your rung comments in the PLC program. Have you had any luck in getting a single slave to communicate?
  17. Confirm that you are using the correct cable (it's not the same cable as that used with the EX-A2X) and confirm that you are plugging the correct end of the cable to the module and the correct end to the PLC (the cable can only be oriented one way). Also, confirm that the I/O modules are identical, and in the same order, as in the hardware configuration in the PLC program.
  18. What does "I went in to all the Socket Parameters" mean? In my post above I was suggesting you use Socket 2 in the slaves and initialize to 20261 - 20263. It doesn't matter which socket you use as long as the port number is correct. Also make sure they're all initialized to TCP Slave. The default for Socket 0 is UDP. My other suggestion is to limit your code to a single slave and get that working properly before trying to tackle communicating with 3 slaves simultaneously.
  19. What does this mean? I didn't see any glaring problems, but the issue with comms is that every single detail must be exactly right in order for everything to work. It requires going through every entry of every FB, loading into the PLCs, and observing operation - something I didn't have time to do.
  20. 1) When commenting, use full sentences. 2) Use the port numbers I suggested, Leave Socket 1 as 20256 for PC-PLC comms. 3) You cannot initialize more than one socket to the same port number. 4) Don't try to initiate a MODBUS command immediately on the heels of the previous one. Give it a little delay (maybe 20-50ms) You seem to be confusing local ports and remote ports. For simplicity, and to avoid confusion, I always use the same port number for master and slave, that way it's impossible to confuse them. Same port number for master and slave means the following: Master PLC: S0=20261, S2=20262, S3=20263 Slave 1 PLC: S2=20261 Slave 2 PLC: S2=20262 Slave 3 PLC: S2=20263
×
×
  • Create New...