Jump to content

Gabriel Franco

Members
  • Posts

    404
  • Joined

  • Last visited

  • Days Won

    20

Everything posted by Gabriel Franco

  1. Try a firmware roll-over, using the original one. If you are not sure about the version, open the applictaion and look under View | signature log menu, then install Visilogic version matching the one used previously.
  2. The best way is using data tables, as Kratmel mentioned. Also, you may use free utility included in Visilogic (DataXPort) or write your own code in Excel to exchange datatables with PLC
  3. I would check if the buffer (vector of MIs) is being used in another place on your program. If so, it would add undesired characters. Post your program here to take a look.
  4. Why don´t you un-dock the center toolbar (HMI standard toolbar? To zoom, use ctrl+i
  5. Its the way to remember to myself and to my coleagues that its madatory to set it in all programs using Ethernet. I set all requiered power up values in ladder rather than Visilogic option.
  6. MI1032 is the password entry variable: Mi1050/Mi1051/mi1052 are password values assigned to different roles, as you stated. How do I lock a button???? Use DisableMode (or DisableView) of the object you want to disable.
  7. PLC as Modbus RTU master (in this code, I´m using PLC port 2 as RS485, your case may be different): Reading registers from the slave. You must use a N.C contact of FunctionInProgress in series with your own reading conditions:
  8. Some time ago I used this code: according to password entered, set MI98 to a number defining the user level, so use this MI to lock different buttons.
  9. What I do is a kind of whatchdog: master writes continously 1 to an register (MI10); slaves resets it. In the example, I use T50 to detect comms lost with master and act acordingly.
  10. I would check: 1. Terminal resistors, only at the ends of the network. 2. Comms parameters, baud and so on. 3. Register numbers. 4. Delay time between readings of each slave.
  11. Set DNS provided by your ISP. If PLC is connected to the same network of your computer, then verify its DNS server in network connection details of Windows control panel
  12. I´m affraid no. As long as I remember, INFO mode is not accesible via remote operator neither remote access, so, you would be completely blind to perform SD actions from INFO mode. I would get a new unit, exchange CPU as Kratmel suggested then verify if project is burnt.
  13. Another option: use SD memory card and attempt CLONE ALL from INFO mode, so you can move program, OS, data, datatables to a new unit. I don´t remember if SD Password must be enable on ladder to be able to use this option.
  14. You can reconfigure the socket periodically, let´s say, every 5 minutes. This was my workaround some time ago.
  15. I suggest to double check wiring, network configuration (ID, baud and so on) on the meter side and register numbering, response timeout. Also, first try using a Modbus software. Any chance that 5000 is hex? If so, set decimal address.
  16. It´s a normal behavior. If you want your PLC act as slave (named server in Modbus TCP), you configure it under PLC Communications | Protocols | MODBUS | Slaves, either Ethernet or RS485. Then, it will be another slave in the network. If you want your PLC act as a master (named client in Modbus TCP), you must configure all your slaves under PLC Communications | Protocols | MODBUS | Masters, either Ethernet or RS485. Then, it will be the master in the network. All slaves must have unique IP (Ethernet) or ID (RS485).
  17. I would use two different MB, one for local control and another for Modbus commands. In ladder, use one or another based on your requirements (Modbus control enabled - remote control - or local control). In Vision family once you enable Modbus as a slave, you cannot restrict access to only desired operands, all of them can be read/writen using proper addresses.
  18. I´ve used it and not always gives too much information about how hot is the snap.
  19. Here you are using AV_001 as direct coil, it must be direct contact: IP address is missing for remote slave1: PLC is acting as Modbus TCP server or client? You set both modes up. Active bits are missing in coils periodic task.
  20. Mod add, pinned in "topics almost worth pinning" 1. Initialize the socket as usual, but using UDP instead TCP. 2. Configure Modbus TCP. 3. Execute Modbus function. There is not need to open socket nor wait for open connection. What I do here is to increase a pointer to read sequencialy all slaves. 4. Wait for response and process your data. I´ve used up to 4 sockets mixing TCP, UPD and TCP_Raw with no problems at all. Keep in mind that each socket acts as a logical port, so you may use each one with its own port number and protocol. UDP disadvantages: 1. Packages lost because of inherent lack of error check of UDP, but it´s compensated with more speed and less comms overhead. 2. Some devices only accept TCP connections.
  21. What I do is to use UDP instead of TCP (for the socket using Modbus). That way, there´s not need to open/close connection each time you need to communicate to the next slave. Be aware that some devices only accept TCP
×
×
  • Create New...