Modbus TCP MBTCP Aveva Wonderware SP2020 Basic Guide

Поділитися
Вставка
  • Опубліковано 19 жов 2024

КОМЕНТАРІ • 14

  • @tayyang2265
    @tayyang2265 6 місяців тому +1

    Thabk u so much, u saved me

  • @salaheldineghennai7743
    @salaheldineghennai7743 11 місяців тому

    Hello Sir, that is very great explanation, i just wanna know why you didnt use galaxy IDE

  • @zonaotomasi
    @zonaotomasi 2 роки тому

    Good one.
    Thank you for sharing.

  • @umairahmed3100
    @umairahmed3100 Рік тому +1

    How to configuration and requirements for SIdirect server

  • @OliverCHO-o1w
    @OliverCHO-o1w 2 місяці тому

    Is there Modbus Serial Driver? I need RS485 communication.

    • @automationcontrolhub
      @automationcontrolhub  2 місяці тому +1

      for RS485 with COM connection, you can install old modbus serial driver but there is some modification in configuration file since that driver no longer support recent version of SMC UI. You should edit the configuration as xml file and you good to go.

  • @trifff40
    @trifff40 8 місяців тому

    oi mbtcp in my smc dont appear, any solution sir please? i have downloaded the oi mbtcp driver sir

  • @scottgriffiths5315
    @scottgriffiths5315 2 роки тому +1

    You mean how to connect to Intouch HMI...

  • @umairahmed3100
    @umairahmed3100 Рік тому

    Can be configuration Aveva 2023 in to s7300 ,4000?

  • @tiapathe7109
    @tiapathe7109 4 місяці тому

    I follow your steps, but intouch don't show any data ,and log viewer show
    DASProtFail MBTCP Error in Reading from PLC for item New_TCPIP_PORT_000.New_ModbusPLC_000.40003 F
    DASProtFail MBTCP The PLC New_TCPIP_PORT_000.New_ModbusPLC_000 reported receiving an ILLEGAL DATA ADDRESS from the OI Server. PLC errorcode 02
    Do u mind tell me how to fix it?🥲🥲🥲

    • @automationcontrolhub
      @automationcontrolhub  4 місяці тому

      there are some possibility that could make illegal data addres happen :
      - the device id from modbus slave couldnt be reach by wonderware. Since I use demo version, it seems like only address 255 is allowed for configuration
      - the range of modbus address configured in wonderware more than what modsim (as a modbus slave) can be served or the range is offset. Kindly make sure wether you configured in 0 based or 1 based address.