123solar 1.7.0

[jeanmarc]

ls -l /dev/ttyUSB*
lsusb
Check about "Persistent names for devices"

[solarjerry]

rs-485 address?

[jeanmarc]

It is what you set in your inverter

[solarjerry]

Well, I did get this fscked problem fixed

[TonyP62]

There is a problem with this new version with the sdm120c drivers.
Into protocols , Port and RS485 are blocked and you cannot insert a value, so we must insert them into che protocol file. I have installed it with update and with a fresh installation but it is the same on Debian 8 (Jessie) and Debian 9 (Stretch) . In all installations i have see that 123solar stop to update with pvoutput.org site .
Don't updates with pvoutput with MeterN consumption or without .

Edit:
Checking into journalctl -r i see this:

Code: Select all

dic 06 14:18:51 tonysolar sdm120c[18283]: Response timeout gave up after 200321us
dic 06 14:18:51 tonysolar sdm120c[18283]: ERROR (110) Connection timed out, 1/1, Address 30001 [0000]
dic 06 14:18:51 tonysolar sdm120c[18283]: sdm120c -a 1 -b 9600 -vpcfi -q /dev/ttyUSB0
dic 06 14:18:51 tonysolar sdm120c[18283]: parent: sh(18282)
dic 06 14:18:51 tonysolar sdm120c[18283]: sdm120c v1.3.5.3
dic 06 14:18:51 tonysolar sdm120c[18281]: NOK

Why this error that previous versions don't have ?
This error also is into the 1.6.9 release.

Best Regards,
Tony

[jeanmarc]

Hi,
You can modify admin/admin_invt.php to allow the adress/port fields :

Code: Select all

// Allow fields
$portlist   = array(
    'aurora',
    '485solar-get',
    'fronius-fslurp',
    'sdm120c'
);
$adresslist = array(
    'aurora',
    '485solar-get',
    'SBFspot',
    'rklogger',
    'fronius-fslurp',
    'sdm120c'
);

The other journalctl error is from the sdm120c application.

[TonyP62]

Many Thanks Jean-Marc .
Now it's perfect. I hope you want insert the sdm120c protocol into the protocols list in the future. It'll be a great thing. About problems with the sdm120c driver, i have solved adding into the sdm120c.php file this parameters : -z10 & -j10 that are timeouts . I also added the -2 parameter for my SDM220C (SDM120C uses the -1). In this way the journalctl don't reveal errors.
Thanks.
Best regards,
Tony

[greenheaven]

Hi,
I've installed 123solar 1.7.0 on a raspberry pi3 to monitor my Aurora 2.5 inverter.
It looked to work nice at the beginning but some days on each morning I've to manually reboot the Raspberry in order to get 123solar to work. Sometimes it stop working also during the day.
I activated the debug mode and this is what I read on a file in the file /var/www/123solar/data/invt1/errors/de20180103-15:16:17.err

Code: Select all

aurora -b -a 2 -c -T -Y10 -l5 -w5000 -d0 -e /dev/ttyDTU0

szttyDevice: /dev/ttyDTU0
yDelay:     5
yTimeout    0 mS
yMaxRunTime ~
devLCKfile: </var/lock/LCK..ttyDTU0>
devLCKfileNew: </var/lock/LCK..ttyDTU0.24413>
Got Params

RunTime     20180103-15:16:17 v1.9.3
Endian    : Little
tm_gmtoff : yes
PID       : 24413

Attempting to get lock on Serial Port /dev/ttyDTU0...
Checking for lock
PID: 24413 COMMAND: "aurora" LckPID: 24413 LckCOMMAND: "aurora" LckPIDcommand "aurora" = me
Appears we got the lock.

Opening Serial Port /dev/ttyDTU0...
devLCKfile: </var/lock/LCK..ttyDTU0>
devLCKfileNew: </var/lock/LCK..ttyDTU0.24413>
Clearing Serial Port Lock (24413)... done.

20180103-15:16:17: aurora: Problem opening serial device, check device name.

I'm quite a newby and I wold appreciate any suggestion.
What should I check?
Thank you

[blinkingbee]

I have just installed 123solar and it's running successfully with a SunnyBoy SMA inverter. However although I can send a test using Pushover, alarms don't appear to be sent.

In looking at the code in SBF_spotchecks.php, I see :

// Alarms
// Functionality is not implemented in SBFspot yet

Is this the explanation for my lack of alarms? If so are there plans to implement this function for SMA inverters?

Merci a tous ...

[jeanmarc]

Hi,
You'd better ask the question to SBFspot developer if it is possible to retrieve alarms.