Upcoming Maintenance Alert:

The UBNT Community will be upgraded at 5pm MDT on April 25th. During this time the community forums will be set to read-only status.

Learn more

×
Reply
Ubiquiti Employee
Posts: 62
Registered: ‎11-08-2015
Kudos: 26
Solutions: 2

Indications for completing your first solar sunmax system

[ Edited ]

There are many useful information in the forum and documents on the website. But it seems not easy for a new one coming into sunmax to know how to go through the permit and complete a sunmax installation.  Besides, there are some fw change of sunmax's Gateway and the official installation guide has not finished yet. So, I try to make an indication as below, hope it would with some help.

Please refer to the link:

https://www.dropbox.com/s/0sc0secpd3pma7z/Sunmax%20products%20introduction.pdf?dl=0

 

New Member
Posts: 4
Registered: ‎08-03-2016

Sun MAx

Could you please tell me where I went wrong on the test questions??

I have 100% on the entire coruse, except:

 

New Member
Posts: 4
Registered: ‎08-03-2016

Re: Indications for completing your first solar sunmax system

Thank you for your prompt responce, the answers I submitted do not appear to be incorrect, but the website is still not passing the answers submitted as "correct"??

Ubiquiti Employee
Posts: 62
Registered: ‎11-08-2015
Kudos: 26
Solutions: 2

Re: Indications for completing your first solar sunmax system

@UBNT-Hyde

 

I hear that you are dealing with some of the same requirement about training material on the cloud. Could you also help with this?

 

 

 

Ubiquiti Employee
Posts: 21
Registered: ‎01-25-2017

Re: Indications for completing your first solar sunmax system

@systemaxnw5

 

Yes, I did the same test and also can't get the "Correct" result.

I will contact related colleague to get problem fixed.

New Member
Posts: 16
Registered: ‎07-23-2017
Kudos: 3

Re: Indications for completing your first solar sunmax system

 
New Member
Posts: 16
Registered: ‎07-23-2017
Kudos: 3

Re: Indications for completing your first solar sunmax system

My solarmax install tool for android does not recognize qr code of the panel? I've printed more expanded but same...
Ubiquiti Employee
Posts: 62
Registered: ‎11-08-2015
Kudos: 26
Solutions: 2

Re: Indications for completing your first solar sunmax system

[ Edited ]

ikoen@abv.bg

 

Could you post one of your QR code here, and let me try it?

New Member
Posts: 16
Registered: ‎07-23-2017
Kudos: 3

Re: Indications for completing your first solar sunmax system

 
image-0-02-05-e92dd007911784f041011bbce57aecfbfcd6d73a22b233135202aa9a63a5629e-V.jpg
New Member
Posts: 16
Registered: ‎07-23-2017
Kudos: 3

Re: Indications for completing your first solar sunmax system

I am far away from my system now. Not shure that this is the qr code of the panel. It might be from the gateway. There is the second problem. My android solarmax instaĺl answer me that the qr code of the gateway already is attached to other site. My system is brand new. How is it possible?

Ubiquiti Employee
Posts: 62
Registered: ‎11-08-2015
Kudos: 26
Solutions: 2

Re: Indications for completing your first solar sunmax system

[ Edited ]

You should be able to get QRcode in MI's box as below picture.

Please use your sunmax's android app to scan the QRcode of inverters. The concept is that you could read inverter's generation data to know the panel's status, not to scan the panel's QRcode. And, please also do the QRcode map for your future application. 

 

 

For the gateway QRcode, please also post it here, and I could check it in the system and correct the error in the system for you.

 

DSC_0056.JPG
DSC_0057 - 複製.JPG
Screenshot_2017-08-17-17-04-19.jpg
未命名.png
New Member
Posts: 16
Registered: ‎07-23-2017
Kudos: 3

Re: Indications for completing your first solar sunmax system

Ok, I will be able to do that after 3 days. Hope that the Ml's qrcode isn't lost by unpack. Thank you Very much
New Member
Posts: 16
Registered: ‎07-23-2017
Kudos: 3

Re: Indications for completing your first solar sunmax system

Now everything with my QRs seems to be OK. My site recognize all of them correctly, BUT....the gateway is still offline.  According to the post: https://help.ubnt.com/hc/en-us/articles/214483847-sunMAX-Solar-Gateway-Quick-Start-Guide I am waiting for my SM-PICO to goes online in the cloud, before conecting other devices to my site. This is not happend. Than i'm searching for the IP of SM-PICO in the local network. Than I switched routers DMZ to this IP to be shure that my SM-PICO will find the cloud without problems and without closed ports. Still nothing. 

Ubiquiti Employee
Posts: 62
Registered: ‎11-08-2015
Kudos: 26
Solutions: 2

Re: Indications for completing your first solar sunmax system

[ Edited ]

ikoen@abv.bg

 

Can you post your gateway information showing on your Android APP as below photo. So that, I can know if the cloud system have got recognized it.

Screenshot_2017-08-25-09-18-32.jpg
New Member
Posts: 16
Registered: ‎07-23-2017
Kudos: 3

Re: Indications for completing your first solar sunmax system

 
IMG_20170825_121949.jpg
New Member
Posts: 16
Registered: ‎07-23-2017
Kudos: 3

Re: Indications for completing your first solar sunmax system - LOG from the Gateway

1970-01-01 00:00:20 (none) syslog-ng[594]: syslog-ng starting up; version='3.0.5'
1970-01-01 00:00:20 (none) syslog: /etc/rc.common: line 143: log: not found
1970-01-01 00:00:20 (none) uboot-autoupdate: U-Boot image hashes match. No upgrade necessary.
1970-01-01 00:00:20 (none) syslog: uboot-autoupdate: U-Boot image hashes match. No upgrade necessary.
1970-01-01 00:00:20 (none) syslog: /etc/rc.common: line 143: log: not found
1970-01-01 00:00:20 (none) kernel: [ 20.130000] UBI: default fastmap pool size: 8
1970-01-01 00:00:20 (none) kernel: [ 20.140000] UBI: default fastmap WL pool size: 25
1970-01-01 00:00:20 (none) kernel: [ 20.150000] UBI: attaching mtd5 to ubi0
1970-01-01 00:00:20 (none) kernel: [ 20.300000] UBI: scanning is finished
1970-01-01 00:00:20 (none) kernel: [ 20.350000] UBI: attached mtd5 (name "overlayfs", size 14 MiB) to ubi0
1970-01-01 00:00:20 (none) kernel: [ 20.360000] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
1970-01-01 00:00:20 (none) kernel: [ 20.420000] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
1970-01-01 00:00:20 (none) kernel: [ 20.470000] UBI: background thread "ubi_bgt0d" started, PID 607
1970-01-01 00:00:20 (none) kernel: [ 20.580000] UBIFS: recovery needed
1970-01-01 00:00:20 (none) kernel: [ 20.760000] UBIFS: recovery completed
1970-01-01 00:00:20 (none) kernel: [ 20.760000] UBIFS: mounted UBI device 0, volume 0, name "ubi_volume"
1970-01-01 00:00:20 (none) kernel: [ 20.780000] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
1970-01-01 00:00:20 (none) kernel: [ 20.810000] UBIFS: reserved for root: 0 bytes (0 KiB)
1970-01-01 00:00:20 (none) kernel: [ 20.820000] UBIFS: media format: w4/r0 (latest is w4/r0), UUID D4048842-B279-42B5-A54A-8BCD8CA83613, small LPT model
1970-01-01 00:00:20 (none) ubiconnect: Successfully connected to overlayfs
1970-01-01 00:00:20 (none) syslog: ubiconnect: Successfully connected to overlayfs
1970-01-01 00:00:30 (none) kernel: [ 30.960000] UBI: attached mtd6 (name "stash", size 911 MiB) to ubi1
1970-01-01 00:00:30 (none) kernel: [ 30.970000] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
1970-01-01 00:00:31 (none) kernel: [ 31.010000] UBI: good PEBs: 7291, bad PEBs: 0, corrupted PEBs: 0
1970-01-01 00:00:31 (none) kernel: [ 31.070000] UBI: background thread "ubi_bgt1d" started, PID 621
1970-01-01 00:00:31 (none) kernel: [ 31.190000] UBIFS: recovery needed
1970-01-01 00:00:31 (none) kernel: [ 31.370000] UBIFS: recovery completed
1970-01-01 00:00:31 (none) kernel: [ 31.380000] UBIFS: mounted UBI device 1, volume 0, name "ubi_volume"
1970-01-01 00:00:31 (none) kernel: [ 31.390000] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
1970-01-01 00:00:31 (none) ubiconnect: Successfully connected to stash
1970-01-01 00:00:31 (none) syslog: ubiconnect: Successfully connected to stash
1970-01-01 00:00:32 (none) syslog: rc.common
1970-01-01 00:00:32 (none) rc.common[638]: ubnt-post-fw-upgr running
1970-01-01 00:00:32 (none) syslog: rc.common
1970-01-01 00:00:32 (none) rc.common[638]: ubnt-post-fw-upgr upgrade network config
1970-01-01 00:00:32 (none) syslog: rc.common
1970-01-01 00:00:32 (none) rc.common[638]: Restore default network config
1970-01-01 00:00:32 (none) syslog: rc.common
1970-01-01 00:00:32 (none) rc.common[638]: ubnt-post-fw-upgr done
1970-01-01 00:00:32 (none) syslog: ln: /etc/localtime: File exists
1970-01-01 01:00:33 (none) syslog: /etc/rc.common: eval: line 1: procd_add_mdns: not found
1970-01-01 01:00:33 (none) dropbear[768]: Not backgrounding
1970-01-01 01:00:33 (none) netifd: Interface 'lan' is enabled
1970-01-01 01:00:33 (none) netifd: Interface 'loopback' is enabled
1970-01-01 01:00:33 (none) netifd: Interface 'loopback' is setting up now
1970-01-01 01:00:33 (none) netifd: Interface 'loopback' is now up
1970-01-01 01:00:33 (none) netifd: Network device 'eth0' link is up
1970-01-01 01:00:33 (none) netifd: Interface 'lan' has link connectivity
1970-01-01 01:00:33 (none) netifd: Interface 'lan' is setting up now
1970-01-01 01:00:33 (none) netifd: Network device 'lo' link is up
1970-01-01 01:00:33 (none) netifd: Interface 'loopback' has link connectivity
1970-01-01 01:00:33 (none) netifd: lan (809): udhcpc (v1.22.1) started
1970-01-01 01:00:33 (none) syslog: ubnt-waitclock: start
1970-01-01 01:00:33 (none) ubnt-waitclock: start
1970-01-01 01:00:33 (none) syslog: ubnt-waitclock: spawned
1970-01-01 01:00:33 (none) ubnt-waitclock: spawned
1970-01-01 01:00:33 (none) netifd: lan (809): dhcp.script
1970-01-01 01:00:33 (none) dhcp.script[810]: [FALLBACK] Interface: eth0, IP: 192.168.0.100, Netmask: 255.255.255.0
1970-01-01 01:00:33 (none) netifd: Interface 'lan' is now up
1970-01-01 01:00:33 (none) ubnt-waitclock: waiting 267 more seconds for clock
1970-01-01 01:00:33 (none) netifd: lan (809): Sending discover...
1970-01-01 01:00:33 (none) syslog: ubntbox: start
1970-01-01 01:00:33 (none) ubntbox: start
1970-01-01 01:00:33 (none) syslog: ubntbox: spawned
1970-01-01 01:00:33 (none) ubntbox: spawned
1970-01-01 01:00:34 (none) firewall: Reloading firewall due to ifup of lan (eth0)
1970-01-01 01:00:34 (none) syslog: ubnt-init: ubnt-init running
1970-01-01 01:00:34 (none) ubnt-init: ubnt-init running
1970-01-01 01:00:34 (none) syslog: kmod: module is already loaded - ubnt-platform
1970-01-01 01:00:34 (none) syslog: module is already loaded - ubnt-platform
1970-01-01 01:00:34 (none) syslog: op: 00600e01 val: 000a8580
1970-01-01 01:00:34 (none) syslog: op: 06000e01 val: fffeffff
1970-01-01 01:00:34 (none) syslog: op: 06400e01 val: fff7ffff
1970-01-01 01:00:34 (none) syslog: op: 06300e01 val: 00004000
1970-01-01 01:00:34 (none) syslog: ubnt-init: Firmware image is stable
1970-01-01 01:00:34 (none) ubnt-init: Firmware image is stable
1970-01-01 01:00:34 (none) syslog: op: 01200e01 val: 00000000
1970-01-01 01:00:34 (none) syslog: op: 01240e01 val: 00002710
1970-01-01 01:00:34 (none) syslog: op: 01200e01 val: 75300090
1970-01-01 01:00:34 (none) syslog: {
1970-01-01 01:00:34 (none) syslog: "gateway_led": "ok"
1970-01-01 01:00:34 (none) syslog: }
1970-01-01 01:00:34 (none) syslog: {
1970-01-01 01:00:34 (none) syslog: "lan_led": "ok"
1970-01-01 01:00:34 (none) syslog: }
1970-01-01 01:00:34 (none) syslog: ubnt-init: ubnt-init done
1970-01-01 01:00:34 (none) ubnt-init: ubnt-init done
1970-01-01 01:00:34 (none) syslog: solar_agent-bootloader: start
1970-01-01 01:00:34 (none) solar_agent-bootloader: start
1970-01-01 01:00:34 (none) sunstatsd: spawning sunstatsd
1970-01-01 01:00:34 (none) syslog: sunstatsd: spawning sunstatsd
1970-01-01 01:00:34 (none) solar_agent: start
1970-01-01 01:00:34 (none) syslog: sunstatsd: spawned
1970-01-01 01:00:34 (none) sunstatsd: spawned
1970-01-01 01:00:34 (none) solar_agent: setting up solar_agent cert/keyfile
1970-01-01 01:00:34 (none) solar_agent: spawning solar_agent
1970-01-01 01:00:34 (none) syslog: mknod: /dev/flash0: File exists
1970-01-01 01:00:34 (none) solar_agent: spawned
1970-01-01 01:00:34 (none) syslog: module is already loaded - ubnt-platform
1970-01-01 01:00:34 (none) syslog: kmod: module is already loaded - ubnt-platform
1970-01-01 01:00:35 (none) syslog: - init complete -
1970-01-01 01:00:36 (none) netifd: lan (809): Sending select for 192.168.1.174...
1970-01-01 01:00:37 (none) netifd: lan (809): Lease of 192.168.1.174 obtained, lease time 600
1970-01-01 01:00:37 (none) netifd: Interface 'lan' has lost the connection
1970-01-01 01:00:37 (none) netifd: Interface 'lan' is now up
1970-01-01 01:00:37 (none) netifd: lan (809): dhcp.script
1970-01-01 01:00:37 (none) dhcp.script[996]: [DHCP] Interface: eth0, IP: 192.168.1.174, Netmask: 255.255.255.0, Gateway: 192.168.1.1, DNS: 192.168.1.1
1970-01-01 01:00:37 (none) netifd: lan (809): udhcpc.user: kick solar_agent
1970-01-01 01:00:37 (none) firewall: Reloading firewall due to ifup of lan (eth0)
1970-01-01 01:00:38 localhost INFO] sunstatsd: not configured to run. sleeping forever.
1970-01-01 01:00:39 (none) ubnt-waitclock: waiting 262 more seconds for clock
1970-01-01 01:00:44 (none) ubnt-waitclock: waiting 256 more seconds for clock
1970-01-01 01:00:47 localhost INFO] logging to syslog
1970-01-01 01:00:47 localhost INFO] Thu Jan 1 01:00:47 1970: solar_agent starting, cwd="/"
1970-01-01 01:00:48 localhost INFO] Acquiring agent lock...
1970-01-01 01:00:48 localhost INFO] ...lock acquired.
1970-01-01 01:00:48 localhost INFO] connecting to ble_daemon ws://127.0.0.1:11111/
1970-01-01 01:00:48 localhost INFO] connected to ble_daemon.
1970-01-01 01:00:49 localhost INFO] EthernetLinkMonitor: link is UP
1970-01-01 01:00:49 (none) ubnt-waitclock: waiting 251 more seconds for clock
2017-08-25 10:53:04 (none) -- MARK --
2017-08-25 10:53:04 (none) ubnt-waitclock: time is set
2017-08-25 10:53:11 (none) crond[747]: time disparity of 25060852 minutes detected
2017-08-25 10:57:47 (none) netifd: lan (809): Sending renew...
2017-08-25 10:57:47 (none) netifd: lan (809): Lease of 192.168.1.174 obtained, lease time 600
2017-08-25 10:57:47 (none) netifd: lan (809): dhcp.script
2017-08-25 10:57:47 (none) dhcp.script[2591]: [DHCP] Interface: eth0, IP: 192.168.1.174, Netmask: 255.255.255.0, Gateway: 192.168.1.1, DNS: 192.168.1.1
2017-08-25 10:57:58 localhost INFO] BLESupervisor._handle_data_timeout ELAPSED
2017-08-25 10:57:58 localhost INFO] ble_daemon exited with value -9
2017-08-25 10:57:58 localhost INFO] connecting to ble_daemon ws://127.0.0.1:11111/
2017-08-25 10:57:58 localhost INFO] connecting to ble_daemon ws://127.0.0.1:11111/
2017-08-25 10:57:58 localhost INFO] connecting to ble_daemon ws://127.0.0.1:11111/
2017-08-25 10:57:58 localhost INFO] connecting to ble_daemon ws://127.0.0.1:11111/
2017-08-25 10:58:37 localhost INFO] connecting to ble_daemon ws://127.0.0.1:11111/
2017-08-25 10:58:37 localhost INFO] connected to ble_daemon.
2017-08-25 11:00:36 localhost INFO] EthernetLinkMonitor: link is DOWN
2017-08-25 11:00:49 localhost INFO] EthernetLinkMonitor: link is UP
2017-08-25 11:02:47 (none) netifd: lan (809): Sending renew...
2017-08-25 11:02:47 (none) netifd: lan (809): Lease of 192.168.1.174 obtained, lease time 600
2017-08-25 11:02:47 (none) netifd: lan (809): dhcp.script
2017-08-25 11:02:47 (none) dhcp.script[3994]: [DHCP] Interface: eth0, IP: 192.168.1.174, Netmask: 255.255.255.0, Gateway: 192.168.1.1, DNS: 192.168.1.1
2017-08-25 11:03:37 localhost INFO] BLESupervisor._handle_data_timeout ELAPSED
2017-08-25 11:03:37 localhost INFO] ble_daemon exited with value -9
2017-08-25 11:03:37 localhost INFO] connecting to ble_daemon ws://127.0.0.1:11111/
2017-08-25 11:03:37 localhost INFO] connecting to ble_daemon ws://127.0.0.1:11111/
2017-08-25 11:03:38 localhost INFO] connecting to ble_daemon ws://127.0.0.1:11111/
2017-08-25 11:03:38 localhost INFO] connecting to ble_daemon ws://127.0.0.1:11111/
2017-08-25 11:03:38 localhost INFO] connecting to ble_daemon ws://127.0.0.1:11111/
2017-08-25 11:03:38 localhost INFO] connecting to ble_daemon ws://127.0.0.1:11111/
2017-08-25 11:03:38 localhost INFO] connected to ble_daemon.
2017-08-25 11:06:49 (none) user[5265]: using_default_creds
2017-08-25 11:06:49 localhost WARNING] ShardFileList.scan():
2017-08-25 11:06:49 localhost WARNING] missing location. using default sunrise/sunset: 1503630000 1503684000
2017-08-25 11:06:49 localhost WARNING] missing location. using default sunrise/sunset: 1503630000 1503684000
2017-08-25 11:06:49 localhost WARNING] ShardFileList.scan():
2017-08-25 11:06:49 localhost WARNING] missing location. using default sunrise/sunset: 1504148400 1504202400
2017-08-25 11:06:59 localhost WARNING] missing location. using default sunrise/sunset: 1503630000 1503684000
2017-08-25 11:07:09 localhost WARNING] missing location. using default sunrise/sunset: 1503630000 1503684000
2017-08-25 11:07:26 (none) user[5483]: using_default_creds
2017-08-25 11:07:31 (none) user[5518]: using_default_creds
2017-08-25 11:07:47 (none) netifd: lan (809): Sending renew...
2017-08-25 11:07:47 (none) netifd: lan (809): Lease of 192.168.1.174 obtained, lease time 600
2017-08-25 11:07:48 (none) netifd: lan (809): dhcp.script
2017-08-25 11:07:48 (none) dhcp.script[5610]: [DHCP] Interface: eth0, IP: 192.168.1.174, Netmask: 255.255.255.0, Gateway: 192.168.1.1, DNS: 192.168.1.1

Ubiquiti Employee
Posts: 62
Registered: ‎11-08-2015
Kudos: 26
Solutions: 2

Re: Indications for completing your first solar sunmax system - LOG from the Gateway

[ Edited ]

ikoen@abv.bg

 

This is a problem in cloud side which will take time to solve it. Before that, would you mind to move to a local monitoring version for temporary? Then you could have the system working at least. Please follow below introduction. Thanks.

 

https://www.dropbox.com/s/ouudrzx1bvd8ha5/Gateway%20setting%20for%20Sunmax%20system.pdf?dl=0

 

 

New Member
Posts: 16
Registered: ‎07-23-2017
Kudos: 3

Re: Indications for completing your first solar sunmax system - LOG from the Gateway

Please send me the instructions again. They are not available now

New Member
Posts: 16
Registered: ‎07-23-2017
Kudos: 3

Re: Indications for completing your first solar sunmax system - LOG from the Gateway

and some pictures of my system

IMG_20170910_134025.jpg
IMG_20170910_133912.jpg
IMG_20170910_133858.jpg
New Member
Posts: 16
Registered: ‎07-23-2017
Kudos: 3

Re: Indications for completing your first solar sunmax system - LOG from the Gateway

And this is the local monitoring

local monitoring.png
Reply