Jump to content

udubiel

Members
  • Posts

    4
  • Joined

  • Last visited

Everything posted by udubiel

  1. Do you mean Modbus instead of OPC? Modbus-TCP is normally on port 512. On a Vision350 you can use Socket 2, which is by default initialized for Modbus. But you can also use any other socket and any other free port number. In this case you have to call 'Socket Init' on your Vision and you also have to change the port number on your cfw011. cheers Udo
  2. No replies yet? So let me try to answer your questions. I know 4 different built-in screens in VisiLogic: Groups with pending alarms Alarms in Group Alarm Detail Alarm History You can call the screens with the according FBs in ladder. I recommend to start with the 'Show Groups' FB which loads display 'Groups with pending alarms' and then going more into detail. You don't have to download the displays. They are built-in -- and as far as I know is there no way to change them. You just can change the strings, if you want them in your native language. Look for String IDs above 1500 in String-Library 2. You also have to set String Library 2 (or 3, 4). The alarm displays look different in various Vision models. On a monochrome Vision130 they look very simple. On a Vision350 the look even better, like the images in VisiLogic-Help. On a Vision1210 they look very fine. As you can't modify the screens, there is no need to export them to other projects. You might copy your strings with copy-and-paste to other projects. If you are using VisiLogic alarms you have to take them as they are. If you are happy with them, then use it. If not, you have to build your own alarm screens, as many VisiLogic programmers did before Unitronics introduced alarms. I think many programmers are still using their own screens, because they want more flexibility. Maybe that's the reason, nobody answered by now.
  3. Thanks for your reply! I am not shure, if connection is lost, the socket is allready closed. With a Modbus-Master on a V1210 once I expierenced longer (~ 1min) delays before reconnect, when I removed ethernet cable and plugged it in again. I have shortened the delay by explicitly closing the socket. From then on I always used this in my Modbus-Sequence - not really shure, if this is really needed. On a Vision700 this proven procedure fails. I am getting the status bits with: And trying to close the socket with: I think it failes, because the socket status bits are not continuously ON during a cycle. In Online-Test I can see a flicker. But - nevertheless - my Modbus-Sequence is working even without socket close. By now reconnect times do not seem to be critical. Maybe the reconnect delay depends on Socket-Timeout-Values on both machines. With short timeouts, no socket close would be needed.
  4. What is a proper condition to close a socket on a Vision700? I have a Modbus-Master running on a Vision700 without user action. When connection to a slave is lost, I want to close the socket, so it can reconnect again.
×
×
  • Create New...