Mate3 Modbus

Mate3 and Mate3s communications devices for Outback Power

Mate3 Modbus

Postby LostPuppy on Mon Jul 17, 2017 6:48 pm

Hi,

I am unsuccessfully trying to use Modbus on the Mate3 (firmware 3.15.5). I am attempting to use python and pymodbus. Does anybody have experience using python with the Mate3? My current attempt to read a register is below.
Code: Select all
from pymodbus.client.sync import ModbusTcpClient as ModbusClient

client = ModbusClient('192.168.0.64', port=502)

rr = client.read_holding_registers(40001, 1)

When I reach the last command, I get a connection error.
Code: Select all
pymodbus.exceptions.ConnectionException: Modbus Error: [Connection] Failed to connect[192.168.0.64:502]

Is this because of my settings? I have SunSpec enabled and OpticsRE disabled. I can see that the IP of the mate is correct and so is the port. The Mate is connected directly to my Mac. But I can't ping the ipaddress of the Mate. Any help or code snippets would be greatly appreciated!
LostPuppy
Forum Member
 
Posts: 14
Joined: Fri Jul 07, 2017 10:27 am
My RE system: Mate3, Hub10, 2 FXR inverters, 2 FlexMax 60 CC

Re: Mate3 Modbus

Postby larrywa on Tue Jul 18, 2017 1:39 pm

Knowing nothing to help you with this, so far , I am starting to embark on a journey like this, or, as an alternative, trying to figure out how to scrape the Mate3 webpages served.

I am very interested in anything I can learn here. I have a lot of programming experience, but only about a year into python3, so far and choking somewhat but getting there.

My results will get shoved into an ISY994i home automation CPU for further crunching, notifications, and control of other household item based on how well the sun is doing today. I mostly only need monitoring functions and very little , if any, control.

I have been experimenting with another person's ISY994 bridge interrogator for modbus but the Mate3 only ever refuses connection.

I would be very interested in seeing what you have so far. I have some time to hack away at this to get it to work hopefully.
larrywa
Forum Guru
 
Posts: 351
Joined: Thu Jun 25, 2015 11:25 am
My RE system: FlexPower Two
2 x GVFX3648s,
2 x FM80s,
FNDC w/3 shunts,
Mate3 v3.015.005 (works excellent!)
Hub 10.3,
PV:1000W east@45, 600W west@45, 2400W south@19 deg.
Battery:48v @ 130Ahr Crown batteries, deep cycle <$380 for 6.25kWh

ISY994i HA, Insteon, X10, Philips Hue, MiLight bulbs & RGBW strips
WebControl 8 as weather station stuffing
ISY994 variables via REST interface

Raspberry Pi3 x 2, Pi1 B+

Re: Mate3 Modbus

Postby LostPuppy on Tue Jul 18, 2017 2:29 pm

Keep me posted if you figure anything out! I am thinking that I'll need to use pysunspec instead of pymodbus. But I'm still trying to figure out how it works.
LostPuppy
Forum Member
 
Posts: 14
Joined: Fri Jul 07, 2017 10:27 am
My RE system: Mate3, Hub10, 2 FXR inverters, 2 FlexMax 60 CC

Re: Mate3 Modbus

Postby larrywa on Tue Jul 18, 2017 5:57 pm

LostPuppy wrote:Keep me posted if you figure anything out! I am thinking that I'll need to use pysunspec instead of pymodbus. But I'm still trying to figure out how it works.

For sure.
I am not currently working on anythig but I have read some clues.

Python stuff is terrible, with poor documentation, and hearsay routines from mysterious places that have magical and hidden features. I still love the logical syntax though. :)
larrywa
Forum Guru
 
Posts: 351
Joined: Thu Jun 25, 2015 11:25 am
My RE system: FlexPower Two
2 x GVFX3648s,
2 x FM80s,
FNDC w/3 shunts,
Mate3 v3.015.005 (works excellent!)
Hub 10.3,
PV:1000W east@45, 600W west@45, 2400W south@19 deg.
Battery:48v @ 130Ahr Crown batteries, deep cycle <$380 for 6.25kWh

ISY994i HA, Insteon, X10, Philips Hue, MiLight bulbs & RGBW strips
WebControl 8 as weather station stuffing
ISY994 variables via REST interface

Raspberry Pi3 x 2, Pi1 B+

Re: Mate3 Modbus

Postby larrywa on Tue Jul 18, 2017 6:24 pm

LostPuppy wrote:Keep me posted if you figure anything out! I am thinking that I'll need to use pysunspec instead of pymodbus. But I'm still trying to figure out how it works.

Are you running python3 or python2.7?

pySunSpec looks like it was never upgraded to run on python3, in case you were attempting to. I have only programmed using python3.4 so I have some learning to do...maybe?
I wont have time for this for a week or so now. Babysitting grandchildren. :)
larrywa
Forum Guru
 
Posts: 351
Joined: Thu Jun 25, 2015 11:25 am
My RE system: FlexPower Two
2 x GVFX3648s,
2 x FM80s,
FNDC w/3 shunts,
Mate3 v3.015.005 (works excellent!)
Hub 10.3,
PV:1000W east@45, 600W west@45, 2400W south@19 deg.
Battery:48v @ 130Ahr Crown batteries, deep cycle <$380 for 6.25kWh

ISY994i HA, Insteon, X10, Philips Hue, MiLight bulbs & RGBW strips
WebControl 8 as weather station stuffing
ISY994 variables via REST interface

Raspberry Pi3 x 2, Pi1 B+

Re: Mate3 Modbus

Postby fatheadl on Thu Jul 20, 2017 7:14 am

Hi. I think the mate 3 defaults to getting an IP address by DHCP, and unless your local network is 192.168.0.x, and gives a .64 address to the mate 3, you'll get no connection. What's the IP address of the machine you're using to connect to the mate 3?
8 KC130TM, FM60, RTS, Samlex S1500-124, Mate3, FN-DC, 8 NSB170FT Blue AGM
User avatar
fatheadl
Forum Whiz
 
Posts: 39
Joined: Wed Dec 13, 2006 8:16 am
Location: Knigston, Jamaica

Re: Mate3 Modbus

Postby larrywa on Thu Jul 20, 2017 9:18 am

The IP address of the client machine isn't important. Whatever IP address the request comes from is what the Mate3 responds back to.

I have my Mate3 IP address set by my router DHCP reservation table, and DHCP enabled in my Mate3, so it is always at the same address and at the factory default. 192.168.0.64

Yes. The Mate3 IP address must be known. If he is writing python code I would assume he would know that, but it never hurts to jog certain clues.
larrywa
Forum Guru
 
Posts: 351
Joined: Thu Jun 25, 2015 11:25 am
My RE system: FlexPower Two
2 x GVFX3648s,
2 x FM80s,
FNDC w/3 shunts,
Mate3 v3.015.005 (works excellent!)
Hub 10.3,
PV:1000W east@45, 600W west@45, 2400W south@19 deg.
Battery:48v @ 130Ahr Crown batteries, deep cycle <$380 for 6.25kWh

ISY994i HA, Insteon, X10, Philips Hue, MiLight bulbs & RGBW strips
WebControl 8 as weather station stuffing
ISY994 variables via REST interface

Raspberry Pi3 x 2, Pi1 B+

Re: Mate3 Modbus

Postby fatheadl on Thu Jul 20, 2017 9:49 am

That's what i was trying to ascertain, if the address he's trying to connect to, is on the same network as his machine.
8 KC130TM, FM60, RTS, Samlex S1500-124, Mate3, FN-DC, 8 NSB170FT Blue AGM
User avatar
fatheadl
Forum Whiz
 
Posts: 39
Joined: Wed Dec 13, 2006 8:16 am
Location: Knigston, Jamaica

Re: Mate3 Modbus

Postby LostPuppy on Fri Jul 21, 2017 4:51 pm

Hey,

I got everything figured out for a direct connection to a laptop. I will try a remote connection soon.

I am having a problem with the ethernet connection, though. I can send a couple of commands. Then SunSpec disconnects and the ethernet reboots on the mate. I have to wait a minute for it to reconnect before I can send any more commands. Is this common? Is there a fix for this?

For anybody who was following this thread,

My settings are:
On the Mate3
OpticsRE - DISABLED
SUNSPEC - ENABLED
Settings -> System -> Ethernet Addressed: DHCP - disabled
Settings -> System -> Data Stream: Serial - diabled; Network - enabled; destination IP - (pick any IP, I use 192.168.0.81); dest Port - 57027

On the computer
You must set your computer to the static IP of your destination IP, in my case 192.168.0.81

My python code looks like this (python 2.7).
Code: Select all
from pymodbus.client.sync import ModbusTcpClient as ModbusClient

client = ModbusClient('192.168.0.64', port=502) #set to the IP address of the Mate

rr = client.read_holding_registers(40069, 1)

#40069 begins outback info, 1 is the number of registers you get. If you use 2 instead you will get back 40069 and 40070.
                                                                 
print rr.registers


After the initial block, I think it depends on what you have connected. I'm currently going through and figuring out what is at what address.
I'm using the AXS Port Sunspec Map, and reading a bunch of registers. After that, I'm looking for any of the DID numbers to know where that block begins.
LostPuppy
Forum Member
 
Posts: 14
Joined: Fri Jul 07, 2017 10:27 am
My RE system: Mate3, Hub10, 2 FXR inverters, 2 FlexMax 60 CC

Re: Mate3 Modbus

Postby fatheadl on Fri Jul 21, 2017 5:11 pm

Good, that’s an improvement. There’s a sunspec script on the pymodbus site, in examples/contrib. It should give you a list of connected devices.
8 KC130TM, FM60, RTS, Samlex S1500-124, Mate3, FN-DC, 8 NSB170FT Blue AGM
User avatar
fatheadl
Forum Whiz
 
Posts: 39
Joined: Wed Dec 13, 2006 8:16 am
Location: Knigston, Jamaica

Re: Mate3 Modbus

Postby fatheadl on Fri Jul 21, 2017 5:30 pm

If you disable opticsre, you’re going to see a 60sec 80sec cycling, meaning, it’ll connect for 80 seconds, disconnects for 60 seconds, or vice versa.
8 KC130TM, FM60, RTS, Samlex S1500-124, Mate3, FN-DC, 8 NSB170FT Blue AGM
User avatar
fatheadl
Forum Whiz
 
Posts: 39
Joined: Wed Dec 13, 2006 8:16 am
Location: Knigston, Jamaica

Re: Mate3 Modbus

Postby LostPuppy on Mon Jul 24, 2017 9:42 am

Aren't you supposed to have OpticsRE disabled, if you have Sunspec enabled?

Where did you find the information on the cycling?

I enabled opticsre and sunspec at the same time but I still get following:

I see connected (green light flashing on ethernet port and sunspec ready on the port screen). Then I read a register, and the Ethernet port resets (orange and green light go out (cant reach port screen), orange light comes back, (port screen reachable but sunspec says disabled) then green light starts flashing and sunspec switches to ready. Finally, I can send another command.
LostPuppy
Forum Member
 
Posts: 14
Joined: Fri Jul 07, 2017 10:27 am
My RE system: Mate3, Hub10, 2 FXR inverters, 2 FlexMax 60 CC

Re: Mate3 Modbus

Postby intellact on Mon Jul 24, 2017 11:35 am

LostPuppy wrote:Aren't you supposed to have OpticsRE disabled, if you have Sunspec enabled?

What works and what is supposed to work may be two different things with MATE3 networking. :wink: I can certainly corroborate the need for OPTICSre to be Enabled.

LostPuppy wrote:Where did you find the information on the cycling?

fatheadl probably discovered this the way we all did - through trial and error. The cycling phenomenon has been well-documented on this forum for a number of months, but the apparent solution (at least under 003.015.005) is more recent.

LostPuppy wrote:I enabled opticsre and sunspec at the same time but I still get following:

I see connected (green light flashing on ethernet port and sunspec ready on the port screen). Then I read a register, and the Ethernet port resets (orange and green light go out (cant reach port screen), orange light comes back, (port screen reachable but sunspec says disabled) then green light starts flashing and sunspec switches to ready. Finally, I can send another command.

Port screen? Are you browsing into the MATE3 at the same time as you are doing Modbus? :-k There may be nothing wrong with that, but have you tried without the port screen running?

(I wouldn't have ever noticed the network LED changes. Those lights are on the back of my MATE3 and I'm always looking at the front... :grin:)

You also mentioned in a PM (which I prefer to answer in the public forum):
LostPuppy wrote:I keep getting a connection error when I try to read a register from the Mate It will work maybe 50% of the time. I'll make sure that it is connected and ready, but
when I try to read a register, it just restarts the ethernet port.

Sorry - can't help you with this one - perhaps other python users can comment. I code with VB.Net and my register reads work every time. :-"
Andrew Welch, creator of WattPlot
User avatar
intellact
Forum Czar
 
Posts: 685
Joined: Mon Nov 28, 2005 4:20 am
Location: Ontario, Canada

Re: Mate3 Modbus

Postby LostPuppy on Mon Jul 24, 2017 12:02 pm

Thanks for your replies!

I may have been past the available blocks.

It seems to be behaving a lot better!
LostPuppy
Forum Member
 
Posts: 14
Joined: Fri Jul 07, 2017 10:27 am
My RE system: Mate3, Hub10, 2 FXR inverters, 2 FlexMax 60 CC

Re: Mate3 Modbus

Postby LostPuppy on Mon Jul 24, 2017 3:58 pm

Is it possible to use sunspec and opticsre simultaneously?
LostPuppy
Forum Member
 
Posts: 14
Joined: Fri Jul 07, 2017 10:27 am
My RE system: Mate3, Hub10, 2 FXR inverters, 2 FlexMax 60 CC

Re: Mate3 Modbus

Postby larrywa on Wed Jul 26, 2017 7:38 am

LostPuppy wrote:Hey,

I got everything figured out for a direct connection to a laptop. I will try a remote connection soon.

I am having a problem with the ethernet connection, though. I can send a couple of commands. Then SunSpec disconnects and the ethernet reboots on the mate. I have to wait a minute for it to reconnect before I can send any more commands. Is this common? Is there a fix for this?

For anybody who was following this thread,

My settings are:
On the Mate3
OpticsRE - DISABLED
SUNSPEC - ENABLED
Settings -> System -> Ethernet Addressed: DHCP - disabled
Settings -> System -> Data Stream: Serial - diabled; Network - enabled; destination IP - (pick any IP, I use 192.168.0.81); dest Port - 57027

On the computer
You must set your computer to the static IP of your destination IP, in my case 192.168.0.81

My python code looks like this (python 2.7).
Code: Select all
from pymodbus.client.sync import ModbusTcpClient as ModbusClient

client = ModbusClient('192.168.0.64', port=502) #set to the IP address of the Mate

rr = client.read_holding_registers(40069, 1)

#40069 begins outback info, 1 is the number of registers you get. If you use 2 instead you will get back 40069 and 40070.
                                                                 
print rr.registers


After the initial block, I think it depends on what you have connected. I'm currently going through and figuring out what is at what address.
I'm using the AXS Port Sunspec Map, and reading a bunch of registers. After that, I'm looking for any of the DID numbers to know where that block begins.

That is awesome!

But something doesn't seem right. The destination address: port on Mate3 is for the data streaming function. A modbus interrogation can come from any unknown source client provided all the security things are in place, usually just means it is connected on that hardware and talks nice to the modbus server.

Since you have things starting to function can you try to change the destination IP address:port adddress? It would be nice to know.

BTW: I spent a small amount of time on pysunspec but it is not compatible with python3 and would prefer not to switch gears now. I hope the pymodbus.client.sync is compatible with python3.
From the print statement used you are not running python3 either.

ADDENDED: I have tried to download pymodbus three different methods and they all result in install errors. I do have python 2.7 installed and working as well as python 3.4.
How and where did you aquire pymodbus from?
larrywa
Forum Guru
 
Posts: 351
Joined: Thu Jun 25, 2015 11:25 am
My RE system: FlexPower Two
2 x GVFX3648s,
2 x FM80s,
FNDC w/3 shunts,
Mate3 v3.015.005 (works excellent!)
Hub 10.3,
PV:1000W east@45, 600W west@45, 2400W south@19 deg.
Battery:48v @ 130Ahr Crown batteries, deep cycle <$380 for 6.25kWh

ISY994i HA, Insteon, X10, Philips Hue, MiLight bulbs & RGBW strips
WebControl 8 as weather station stuffing
ISY994 variables via REST interface

Raspberry Pi3 x 2, Pi1 B+

Re: Mate3 Modbus

Postby larrywa on Thu Jul 27, 2017 2:38 pm

Classic that as per the usual I find 90% of the python stuff online doesn't work.

However after trying many different approaches from many dfferent online sources I have combined much past knowledge and found this actually worked with the pymodbus3 package re-written for python3.

Since the install attempt to modify places that a non-superuser has no permissions sudo had to be used also.

sudo pip3 install -U pymodbus3

I haven't experimented with the code yet but, it seems to use the exact same syntax as the older pymodbus.


EDIT: I found that pymodbus3 doesn't have much support or docs out there and abandoned it now. I managed to switch to pymodbus.
See my following post for some results.
larrywa
Forum Guru
 
Posts: 351
Joined: Thu Jun 25, 2015 11:25 am
My RE system: FlexPower Two
2 x GVFX3648s,
2 x FM80s,
FNDC w/3 shunts,
Mate3 v3.015.005 (works excellent!)
Hub 10.3,
PV:1000W east@45, 600W west@45, 2400W south@19 deg.
Battery:48v @ 130Ahr Crown batteries, deep cycle <$380 for 6.25kWh

ISY994i HA, Insteon, X10, Philips Hue, MiLight bulbs & RGBW strips
WebControl 8 as weather station stuffing
ISY994 variables via REST interface

Raspberry Pi3 x 2, Pi1 B+

Re: Mate3 Modbus

Postby larrywa on Mon Jul 31, 2017 10:40 am

OK here is a starter for anybody wanting to use pymodbus to extract information from their Mate3 via the TCP/AXS port.

The data streaming enable, port or IP address is not related and makes no difference to the ModBus port. You can disable it.

This code follows the SunSpec protocol (no absolute register addressing) and scales the blocks of register links to allow Outback to move things around and it should still work properly.

I hope this helps somebody else out. This is written in python3 and could be converted to the older python2.
Best of luck.

Code: Select all
#!/usr/bin/env python3
# Outback Mate3 modbus interrogator
# written by larrylwa (from OpticsRE  forum) using pymodbus
# sudo pip3 install pymodbus
# Last update: July 30, 2017

import time
import urllib.request
import base64
from pymodbus.client.sync import ModbusTcpClient as ModbusClient

# ISY  parameters to be defined by user
ISY_username = 'XXXXXX'
ISY_password = 'XXXXXX'
ISY_IP = '192.168.0.161'

# Write ISY variable via REST interface
def writeISY(varPage, varAddress, varData):
    ISY_rest = "/rest/vars/set/%s/%s/%s" % (varPage, varAddress, varData)
    get_url = urllib.request.Request('http://' + ISY_IP + ISY_rest) #format the URL
    ISY_authorise = base64.b64encode((ISY_username+":"+ISY_password).encode('utf-8')) #encode it
    get_url.add_header("Authorization", 'Basic %s' % ISY_authorise.decode('utf-8'))
    try:
        r = urllib.request.urlopen(get_url)
        returned = r.read()
    except:
        report("*** ISY data send failed! ***")
    r.close()
    return

# Send Charge controller info to ISY994i HA box
def cc2isy(portNum, state, Vpv, Ipv, Ppv, Vbatt, Ibatt):
    varPage = 2
    if portNum == 4:
        stateReg, VpvReg, PpvReg, spareReg, VbattReg = 89,90,91,92,97
    elif portNum == 5:
        stateReg, VpvReg, PpvReg, spareReg, VbattReg = 93,94,95,96,97
    else:
        return -1
    writeISY(varPage, stateReg, state)
    writeISY(varPage, VpvReg, Vpv)
    writeISY(varPage, PpvReg, Ppv)
    writeISY(varPage, spareReg, -1)
    writeISY(varPage, VbattReg, Vbatt)
    return 0


# Report progress on screen
verbose = True # Set verbose = False  to shut off reporting

def report(result, timeMark = True):
    if verbose:
        if timeMark:
            print(time.strftime("%H:%M:%S"), result)
        else:
            print('        ', result)
    return


# Mate3 parameters to be defined by user
Mate3IP = '192.168.0.64'
Mate3Port = 502
startReg = 40000

# Mate3 connection
try:
    client = ModbusClient(Mate3IP, Mate3Port)
except:
    client.close()
    report("**** Couldn't connect to Mate3 ****")
    exit()


# Get and print CC registers of interest
def getCC(regBase):
    try:
        register = client.read_holding_registers(regBase + 2)
        portNum = int(register.registers[0])
        register = client.read_holding_registers(regBase + 8)
        Vbatt = 0.1 * int(register.registers[0])       
        register = client.read_holding_registers(regBase + 9)
        Vpv = 0.1 * int(register.registers[0])       
        register = client.read_holding_registers(regBase + 10)
        Ibatt = 0.1 * int(register.registers[0])     
        register = client.read_holding_registers(regBase + 11)
        Ipv = 1.0 * int(register.registers[0])       
        register = client.read_holding_registers(regBase + 12)
        state = int(register.registers[0])           
        register = client.read_holding_registers(regBase + 13)
        Ppv = int(register.registers[0])
    except:
        return -1
    # Report it
    stateDic = {0:'Silent', 1:'Float', 2:'Bulk', 3:'Absorb', 4:'Equal'}
    if state in stateDic:
        report('Port:%-1u   State:%s' % (portNum, stateDic[state]), False)
    else:
        report('Port:%-1u   State:unknown?? %-u' % (portNum, state), False)
    report('PV:   %4.1fV x %4.1fA = %4.0fW' % (Vpv, Ipv, Ppv), False)
    report('Batt: %4.1fV x %4.1fA ' % (Vbatt, Ibatt), False)
    report('-' * 29, False)
    return portNum, state, Vpv, Ipv, Ppv, Vbatt, Ibatt

           
# Device IDs definitions = (DID)
OB = 64110
CC = 64111
CCC = 64112
FX = 64118
FNRT = 64118
FNDC = 64119
OBSYS = 64120
TERM = 65535
 

# Read SunSpec header
def getSunSpec(baseReg):
    specStr = ''
    for chars in range(0, 2):
        spec = client.read_holding_registers(baseReg + chars)     
        specStr = specStr + chr(spec.registers[0] // 0x100) + chr(spec.registers[0] % 0x100)
    register = client.read_holding_registers(reg + 2)
    unit = int(register.registers[0])
    register = client.read_holding_registers(baseReg + 3)
    blockSize = int(register.registers[0])
    report('', False)
    report('%5s  HDR:%s:%-u  Size:%-3u'% (reg, specStr, unit, blockSize))
    return blockSize


# Get block
def getBlock(baseReg):
    register = client.read_holding_registers(baseReg)
    blockID = int(register.registers[0]) 
    #Peek at block style
    register = client.read_holding_registers(baseReg + 1)
    blockSize = int(register.registers[0])   
    if blockID == OB:
        report('%5s  DID:OB      Size:%-3u' % (reg, blockSize))
    elif blockID == CC:
        report('%5s  DID:CC      Size:%-3u' % (reg, blockSize))
        ccPort, ccState, ccVpv, ccIpv, ccPpv, ccVbatt, ccIbatt = getCC(baseReg)
       ### The next two lines are support for my ISY994i Home Automation box. Do what you want with the returned information
        if ccPort > 0:
            cc2isy(ccPort, ccState, ccVpv, ccIpv, ccPpv, ccVbatt, ccIbatt)
    elif blockID == CCC:
        report('%5s  DID:CCC     Size:%-3u' % (reg, blockSize))
    elif blockID == FX:
        report('%5s  DID:FX      Size:%-3u' % (reg, blockSize))
    elif blockID == FNRT:
        report('%5s  DID:FNRT    Size:%-3u' % (reg, blockSize))
    elif blockID == FNDC:
        report('%5s  DID:FNDC    Size:%-3u' % (reg, blockSize))
    elif blockID == OBSYS:
        report('%5s  DID:OBSYS   Size:%-3u' % (reg, blockSize))
    elif blockID == TERM:
        report('%5s  DID:TERM    Size:%-3u' % (reg, blockSize))
    else:
        report('%5s  DID:OTHER   Size:%-3u' % (reg, blockSize))
    return blockSize

   
# Interrogation loop
while(True):
    reg = startReg
    size = getSunSpec(reg)
    reg = reg + size + 4
    for block in range(0,25):
        size = getBlock(reg)
        if size > 0:
            reg = reg + size + 2
        else:
            break
    for i in range(0,4):
        time.sleep(5)
larrywa
Forum Guru
 
Posts: 351
Joined: Thu Jun 25, 2015 11:25 am
My RE system: FlexPower Two
2 x GVFX3648s,
2 x FM80s,
FNDC w/3 shunts,
Mate3 v3.015.005 (works excellent!)
Hub 10.3,
PV:1000W east@45, 600W west@45, 2400W south@19 deg.
Battery:48v @ 130Ahr Crown batteries, deep cycle <$380 for 6.25kWh

ISY994i HA, Insteon, X10, Philips Hue, MiLight bulbs & RGBW strips
WebControl 8 as weather station stuffing
ISY994 variables via REST interface

Raspberry Pi3 x 2, Pi1 B+

Re: Mate3 Modbus

Postby HarvSki on Fri Jan 12, 2018 11:06 am

So I'm trying to read some data from my Mate3 or the attached FXR on port1 but I'm finding it so confusing to work out what to ask for. This doc http://www.outbackpower.com/downloads/d ... P_NOTE.pdf shows me that I need DID 64110 start 407 for a voltage (I know I need a scale too) but how do I get this???

Thanks for any tips to get me going, btw I've got the code in the previous post running but it's not the right system #-o
HarvSki
Forum Junior Member
 
Posts: 2
Joined: Fri Jan 12, 2018 10:17 am
My RE system: Mate3 FXR


Return to Mate3 / Mate3s

Who is online

Users browsing this forum: No registered users and 1 guest