Jump to content

_PH

Members
  • Posts

    9
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by _PH

  1. To get Modbus TCP/IP comms established, I downgraded to Visilogic version 9.8.65 with OS 4.004(31). I could not get 9.8.95 with OS 4.10(48) to work. To get the TCP connection to close on inactivity, setting SI-105 (Socket 2 TCP/IP Keep Alive) to 10, seem to be the fix.
  2. Think I have the reconnect sorted out. After setting the socket keep alive to 10, am now able to reconnect an ended session. Now just need to sort out the proper Modbus address for MF-0.
  3. Sorted out the IP address settings and following one of the posts supplied have rolled back my OS. Now am running 9.8.65 software and 4.004(31) OS. I can get MDBus to latch onto the controller and see Modbus values after I complete a download but cannot reconnect after closing the MDBus session. Are there any tricks for triggering a CLOSE of the TCP/IP socket/connection? I have been going through the help file to figure a way out to trigger the CLOSE:TCP function but not coming up with anything viable. Link to forum post: 20220610_9-8-65.vlp
  4. I have been through the help and tutorials a few times now.
  5. I am also getting confused with how the IP addressing is supposed to be setup. Is the controller IP address set in the TCP/IP Project Settings or in the TCP/IP Card Init? This controller is connected to a cell modem, so it would technically be the Master on the local network I believe.
  6. So now with those changes, I can see the controller on the network but am not able to pull values from it via Modbus. I am direct connected to it, with no firewall issues. Am using MDBus to test the setup. Any ideas what I am doing wrong? 20220609_0700.vlp
  7. kratmel Thanks. That setup does look cleaner/simpler. I am not understanding IP/ID relationship though. Could you shed some light on that? This controller is the slave, so I am not sure why we need to set up slave in the Modbus IP Config block.
  8. Hello Have inherited a SM43-J-R20 unit that is supposed to be acting as a Modbus Slave to a SCADA system. Currently am having issues getting it to talk to the host. From what I have gleaned from the forums/tutorials, it seems to be setup correct but obviously isn't as it is not talking. Any help would be appreciated. 20220608_1620.vlp
×
×
  • Create New...