Solardedge Modbus odd reading

Einklappen
X
 
  • Zeit
  • Anzeigen
Alles löschen
neue Beiträge
  • Not as smart as my home
    Azubi
    • 11.02.2024
    • 9

    #1

    Solardedge Modbus odd reading

    Hi All,

    Looking for some help please.

    I have a Solaredge inverter and Modbus Air to read the AC output of the SolarEdge system. All works ok except for when the wattage output drops to 299w the value gains an extra digit.

    ie

    Output reads 3000 when the system is outputing 300w

    Output reads 29900 when the system is outputting 299w

    This messes up the final reading as it becomes 2.9kw. Any idea why modbus gets an extra digit at that point and how to avoid / work with it?

    Thanks for your help.

    Not as smart as my home....
  • Labmaster
    Lox Guru
    • 20.01.2017
    • 2695

    #2
    I think without more information like screenshots of the full modbus configuration, solaredge modbus manual and so on its quite difficult to offer any help.

    Kommentar

    • RiverRaid
      LoxBus Spammer
      • 25.08.2015
      • 335

      #3
      Do you use the scale Factor?

      Kommentar

      • Not as smart as my home
        Azubi
        • 11.02.2024
        • 9

        #4
        Yes, I have been using the scale factor. That just removes the decimal point and the 2 decimal places. My issue is reading before it is manipulated in anyway. I am traverling now but will have another look in a week. I will see if it's the same problem if I use modbus TCP.

        Thanks

        Kommentar

        • Not as smart as my home
          Azubi
          • 11.02.2024
          • 9

          #5
          Just an update as I have now fixed the issue. I made two changes at the same time but I suspect the fix was due to the scale factor. The scale factor I was using turned out to be incorrect. It was 5 digits long and I just took that to be correct. Had to untick the 16 bit register etc. so I ended up with a scale factor of -1. I also changed the baud rate at the same time but I suspect the scale factor was the issue. All working now.

          Thanks for everyone input.

          Kommentar

          Lädt...