How To: Modbus RTU & Modbus TCP

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

КОМЕНТАРІ • 10

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

    I appreciate how much time and effort you put into creating your videos. They are very helpful and have helped me become a better trader.

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

      You are welcome. Good luck in your current and future projects!

  • @PURGE-3000
    @PURGE-3000 5 місяців тому

    How come we can’t use the plc table and data types ?

  • @andersonrivas9545
    @andersonrivas9545 3 місяці тому

    Yo tengo un problema de comunicación me dice timeout error

  • @EDUARDO-fc9rj
    @EDUARDO-fc9rj 7 місяців тому

    I am having a problem communicating my PLC with Drive via Modbus connection. I start by opening the port and there is no problem, but then when I want to use the Modbusmaster I fill in all the data correctly but it gives me two errors: 1 in the Trigger it does not allow me to assign any boolean to the switch and with the MCB I put an array in int format to fill in the communication fields but when compiling it marks Modbusmaster: argument expected. Do you have any idea what it could be?

    • @LionsIndy
      @LionsIndy 7 місяців тому

      This is probably complex enough where you should probably contact tech-support and see if one of the application engineers can help you get to the bottom of it.
      I'm sorry it took me a few days to see your comment, I've been working on a project and am behind - my apologies.

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

    Hi, im tryin to replicate this very same example, but using a gateway and modbus TCP/IP, the horner gets the correct information (Bit 4 modbus status), but yet i dont get any response from it, in fact the Modbuspoll says, Gateway target device failed to respond, is a HE-XT106VC

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

      I managed to get response on RS232 not geting any out of RS485....

  • @andersonrivas9545
    @andersonrivas9545 3 місяці тому

    I get a communication problem timeout error?

    • @LionsIndy
      @LionsIndy 2 місяці тому

      Several potential causes for a communications timeout. If communications had previously been established - it could mean a new problem with a cable (i.e. wire being cut) or maybe the other device being powered down. It is probably more likely that you had never established comms to being with, and in that case it could be a number of things. A wiring problem, a baud rate / data bits / stop bits mismatch (for RTU) or an IP address mismatch (for IP). On the list of RTU wiring issues - you'd need to look at pinout, termination, bias, etc. Feel free to contact our support team if these hints fix your issue.