SunSpec Modbus writes fail in 003.011.000

Post Reply
LorenAmelang
Forum Whiz
Posts: 37
Joined: Mon Oct 26, 2009 10:51 pm
My RE system: (being majorly revised...)

SunSpec Modbus writes fail in 003.011.000

Post by LorenAmelang » Sun Sep 20, 2015 6:22 pm

Since it looks like there is hardly any activity here, I've posted this in the Mate 3 thread:

http://www.outbackpower.com/forum/viewt ... =39&t=8176

Sasquatch
Forum Member
Posts: 17
Joined: Mon May 04, 2015 4:48 pm
My RE system: http://www.m2group.com/SolarPowerWeb/
Location: Green Bay, WI
Contact:

Re: SunSpec Modbus writes fail in 003.011.000

Post by Sasquatch » Mon Sep 28, 2015 6:13 am

003.011.00 Address Map:

40069 Outback Block
40491 Outback System Control Block

It appears that in 003.011.00, SunSpec device blocks get inserted at 40520
OPTICS Packet Statistics and everything plugged into the hub immediately follow the SunSpec device blocks
(75 registers further back from 003.007.00 with an FX connected)

For example:
An FX inverter shows up at 40630 when connected directly to AXSport or on any hub port.
Other devices appear at different addresses depending on which hub port they are connected.

Charge Controller with no inverter (hence no SunSpec device block):
OPTICS Packet Statistics 40520
Port 1 MX60 40578
Port 2 FN-DC 40696

FX Inverter:
40520 SunSpec Single Phase Inverter (only shows up when FX is connected)
40572 OPTICS Packet Statistics
Port 1 FX 40630
Port 2 MX60 40735
Port 3 FN-DC 40853

40520 SunSpec Single Phase Inverter (only shows up when FX is connected)
40572 OPTICS Packet Statistics
Port 1 FX 40630
Port 2 FN-DC 40735
Port 3 MX60 40867

I am sure that these will all shift again when I hook up the Radian later this week.
I have web version of this system running online at:
http://www.m2group.com/SolarPowerWeb/

It is formatted for Firefox or Safari w/Adobe Flash plugin (not smartphones)

LorenAmelang
Forum Whiz
Posts: 37
Joined: Mon Oct 26, 2009 10:51 pm
My RE system: (being majorly revised...)

Re: SunSpec Modbus writes fail in 003.011.000

Post by LorenAmelang » Sun Dec 06, 2015 6:52 pm

I guess OutBack's "Notify me" function just doesn't work! I certainly never heard about this post.

I only have one FM80, and no hub involved, so I guess this doesn't apply to me. I did notice the Modbus addresses moved between 001.005.000 and 003.011.000, but I've learned not to trust any documentation. I always use the shell program to dump everything from my own system, and double-check each write address by reading it first.

Certainly would make communication difficult if one device disappearing changed the addresses of all the others!

Sasquatch
Forum Member
Posts: 17
Joined: Mon May 04, 2015 4:48 pm
My RE system: http://www.m2group.com/SolarPowerWeb/
Location: Green Bay, WI
Contact:

Re: SunSpec Modbus writes fail in 003.011.000

Post by Sasquatch » Sun Jan 03, 2016 9:04 am

The Outback world starts at register 40069 no matter what firmware rev is on the AXS port.
Each device has a unique value in the first register of it's block so I wrote a loop that executes at startup, reading every register from 40069 - 41000 and writes the starting address of each device that it finds to an index of starting registers.
The Simply Modbus TCP Client 7.1 is handy for locating and writing to the AXS port. I use that instead of a Mate 3 for configuration.

I have a Radian along with a FN-DC that you can see in action at;
http://www.m2group.com/SolarPowerWeb/

Post Reply