Jump to content

Isakovic

Privileged Member
  • Posts

    181
  • Joined

  • Last visited

  • Days Won

    12

Everything posted by Isakovic

  1. Hello cyrillic friend, If you want to go faster you need model V350-J-TR34. You could use separate 5V supply for fast outputs if you want to evade the use of resistors.
  2. Go to info mode to see what is happening with sockets and try to connect on other Port. I think other Sockets are activated by default on ports 20257, 20258 and 20259 but I'm not sure. Why did you initialize Socket as Client? It should be server if you want to connect through it. Also look at system integers for "Socket Keep Alive"
  3. Is register for position changing, MI12 in your example? If it is then outputs should be firing. Also, steppers can lose position if load is higher. If you have an encoder you could write your own code for positioning and move motor with high speed output instead of PTO functions ("High Speed Outputs (Step Control)" in "Hardware Configuration"). You could try this method for testing, if motor still doesn't move it might be wiring error.
  4. I can't see the program, so don't know if transition contacts would solve the problem. Post it if you can, or screenshots of area that troubles you. About setting bit from HMI. Once bit is set it will remain ON until reset command. When you add action for button "Set bit" for trigger "Press", add one more action "Reset bit" for trigger "Release" if you want it to behave like in VisiLogic. Or reset it in ladder. I wish there was an action "ON while hold", so bit would act like in good old VisiLogic.
  5. Hello, Is there an alternative to system registers SI103 - SI106 (TCP keep alive) for V700? I guess SI103-SI106 don't have a function in V700 since there are only 4 of them? Correct me if I'm wrong. Or do I have to make this function myself?
  6. It is possible. NET 1 Difference = Current Value - Previous Value NET 2 Previous Value = Current Value
  7. There is a "TCP connect" functon if you were referring to making ethernet connection.
  8. That was a great story. You went for Milli-Ohms, but met great resistance.
  9. You'll have to do it with Modbus, I don't know a better way. If you pack registers in sequential order you can read all you need in one command to have more elegant code. Also you can export displays from one project into another and change links to memory locations. If you need to send command from A to B from mirrored PLC, maybe you won't need to alter the code in B but just set bits and register with Modbus, depends of the code. There was a similar topic recently: http://forum.unitronics.com/topic/5425-vision-1210-multi-site-operationio/?tab=comments#comment-22731
  10. Did you, by accident, write values into registers for LCD control, you can see this when you connect to PLC. Also, I had similar blinking was I just placed "set string library" function block to be called unconditionally in every scan. See what happens if you put PLC into stop mode. What is scan time?
  11. I had a similar situation but with outputs. Each output controlled two valves, but one valve was getting negative from supply from NC contact of reley, and other one was getting it from NO contact, so that relay altered which group will be activated. So I got 14 valves from 8 outputs. Crude and patchy solution, but it was some pneumatic cleaner so nothing critical.
  12. You ain't using "Function in Progress" bit before Modbus command. I can't see the rest of the logic, maybe you took it into account. But if you didn't, that may be the reason why it drops messages when you go faster.
  13. Idea was something like this. Maybe SB80 needs to be in a separate net, I'm not sure, can't test it.
  14. You should filter the value a little bit before displaying it, analog input jumps a little bit up and down, it's normal, I guess if you display it immediately lcd will look blurry. Maybe take a couple of readings in short time and display the average, or update register that shows value every 2-3 seconds. I reckon value doesn't change drastically in time since it's level.
  15. I got this UDFB from support when asking about NTP. Maybe you need to modify it to suit you. It works. It was easier in VisiLogic. UniStream_070_RFC_1305_UDFB.ulpr
  16. Are you using RFC-1305 function for updating time. If it fails in reading network time it will just write 0? Or you accidental write to system registers for time? You said it's a bulky code.
  17. I've seen this once. Connection was breaking because there was a card reader on the network with the same IP address. What does "socket state 34" mean in your picture, I can't find it in help files? If you already tried with keep alive registers, maybe try the next sequence: When SB148 goes down (or some other condition that recognizes Ethernet problem) call socket close block, then delay, than initialize socket to UDP, then delay, then initialize it back to TCP. This resurrects blocked socket in my experience, maybe (probably) there's a more elegant solution. Are there any other client applications besides you accessing via VisiLogic?
  18. "Jazz generation 3" I don't know if Unitronics plans this, but there are applications where having 230V voltage for logic is convenient.
  19. Bundle all bits and registers into couple of consecutive registers with struct command, so you can send them all with one Modbus command. Of course, you have to unpack it on the other side.
  20. Usual workaround is to put an MI for user input and mask it to 1 decimal place. Then divide it with 10 in ladder to convert to float.
×
×
  • Create New...