HMI Pad Forums Old forum Common Support Requests (old) Modbus Exception 0B

This topic contains 1 reply, has 1 voice, and was last updated by  John 7 years ago. This post has been viewed 1359 times

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #20039


      Good morning. I am trying to use SM-one (to see if this works for me) on one of our large battery storage units. I can access the holding registers with other products, but am having trouble with SM-One (probably user error). Example is SOC, register 560 decimal. My csv file is:

      # %protocol modbus/tcp
      SOC_Value,UINT,HR560,”section=”"modbus/tcp”"; label=”"Battery SOC”";”

      This returns “Modbus Gateway target device failed to respond (modbus exception 0B)”.

      I am certain there is a value at this register, verified with another product. Any suggestions would be appreciated.



        This message implies communications were fine and your controller responded with a correct modbus error frame (exception 0B). However It is not clear what this means in the case of your PLC.

        Something to take into account is that ScadaMobile uses the Modbus Specification convention for registers so it considers numbering starting at 1, so first register is HR1, not HR0. This differs from modbus addresses as they always start by 0, so maybe you just need to offset your register number by one (i.e HR561 instead of HR560) in case 560 actually refers to a modbus address instead of a modbus register.

        Please also look at the manual of your controller to determine what could cause a modbus exception 0B in your controller response, this very possibly will give you a hint on what is going on.


      Viewing 2 posts - 1 through 2 (of 2 total)

      You must be logged in to reply to this topic.

      Copyright © SweetWilliam, S.L 2009-2013. All rights reserved.
      Science and Technology Park of the University of Girona, Emili Grahit, 91 (NarcĂ­s Monturiol building, Office P3-B03) 17003-Girona. Phone +34972183244