Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Esmart3 nuissances
#31
Hi, just joined the forum. I found this thread while looking for eSmart3 info. To make a long story short I read about the [not so] secret menu in the i-panda software and could't resist, as expected messed up the CC's configuration. Fortunately info posted by skagmo and jimbriam here and on github helped me write a program to get back my eSmart3 CC. Since I had the hard part (communications) done, I decided to write a program with the menu's functionality, called it ccpars. I've attached a zip with the linux binaries and instructions, tested with Fedora and Ubuntu. Soon as I clean up the source I'll post it to github.

The program has a couple of differences with "My Green Solar". First, it works, and second, it displays a reading of the voltages and currents so one can see the effect of making changes immediately. It makes calibration real easy.

Edit:

I updated the attachment to include a Windows version in addition to the linux program, and to correct the original. It gave the wrong names when asking for confirmation, this had no effect on the operation, the parameters were changed correctly.

Source code posted to github:

https://github.com/rcuetara/ccu/releases/tag/v0.1.0

Updated to accept any sequence from the charge controller. This may now work with 40A models, it works with 60A models.
Updated to correct message after parameter is chaged.


Attached Files
.zip   eSmart3-4.zip (Size: 37.28 KB / Downloads: 2)
Reply
#32
@rcuetara, this is great, I run my monitoring program with a box running Linux mint with wine installed and running the MyGreen software
This will certainly be awesome to run it natively on Linux
Looking forward to testing your code
I love my batteries, they give me power...
Reply
#33
I'm currently using a python script to get output from the esmart3, then using telegraf to dump the json output into influxdb. If you want to build your own script, I have the esmart protocol posted on my build page.

Here's my simple script. It's a hack job that was done in a couple hours but it's crude enough to dump the output.

Code:
#!/usr/bin/python

import serial
import sys
import json
import time
import string

ser = serial.Serial()
ser.port = "/dev/ttySI2"
ser.baudrate = 9600
ser.bytesize = serial.EIGHTBITS     #number of bits per bytes
ser.parity = serial.PARITY_NONE     #set parity check: no parity
ser.stopbits = serial.STOPBITS_ONE  #number of stop bits
#ser.timeout = none                 #block read
ser.timeout = 2                     #non-block read
ser.xonxoff = False                 #disable software flow control
ser.rtscts = False                  #disable hardware (RTS/CTS) flow control
ser.dsrdtr = False                  #disable hardware (DSR/DTR) flow control
ser.writeTimeout = 5                #timeout for write


try:
    ser.open()

except Exception, e:
    print "error open serial port: " + str(e)
    exit()

try:
    ser.flushInput()            #flush input buffer, discarding all its contents
    ser.flushOutput()           #flush output buffer, aborting current output and discard all that is in buffer

    out=dict()    
    command = '\xAA\x01\x01\x01\x00\x03\x00\x00\x1E\x32'
    ser.write(command)
    response = ser.read(100)
    if sys.getsizeof(response) < 36 :
        ser.write(command)
        response = ser.read(100)


    if  int(response[8].encode('hex'),16) > 0 :
        watts=int(float((256*ord(response[13])+ord(response[12])))/10*float((256*ord(response[15])+ord(response[14])))/10)
        #watthour below is based on a 15 second period. If your refresh is higher then update it.
        watthour=round(float(watts)/(3600/15),3)
    else:
        watts=0
        watthour=0
        
    out["Inverter2_mode"]=int(response[8].encode('hex'),16)
    out["pv2_input_voltage"]=float((256*ord(response[11])+ord(response[10])))/10
    out["pv2_battery_voltage"]=float((256*ord(response[13])+ord(response[12])))/10
    out["pv2_input_current_for_battery"]=float((256*ord(response[15])+ord(response[14])))/10
    out["pv2_input_watts"]=watts
    out["pv2_input_watthour"]=watthour
    out["pv2_heatsink_temperature"]=int(response[28].encode('hex'),16)
    out["pv2_batt_temperature"]=int(response[26].encode('hex'),16)

    print(json.dumps(out))
    ser.close()
except Exception, e:
    print "error reading inverter...: " + str(e)

    exit()
Reply
#34
(08-10-2019, 04:09 PM)wycito Wrote:
(07-18-2019, 08:56 PM)100fuegos Wrote: I finally could fix my controller. I sent an email to the ipanda team, used the address found in the App, teeling them exactly what happened. Basiccaly that I screwed it and it was totally my fault. After a week or so of waiting I received today an anwer with a program called "AccessPort.exe" and a very detailed set of instructions and images.

Basically you connect to the controller using their RS485 to USB cable and send a set of values provided by their support team. The whole process only takes 3 minutes and is very straight forward provided you have the right tools and instructions.

Thanks to all who tried to help.

I just Zeroed my load voltage settings within the factory menu, can you please share the instructions to set it correctly with the app iPanda provided?

Cheers
Wycito

 Just saw your message today. I was out of country for holidays unconnected from the world. Glad you fixed it too.
wycito likes this post
Reply
#35
(07-04-2019, 08:44 PM)DomingoRP Wrote: When I was messing round with it, Same thing happened to me. Disconnecting all of the cables, wait 5 minutes and then connect everything back. Another thing is that, select the voltage manually (12/24/36/48V) and make sure the LOAD is turned ON. If it is off, chances are it will be stuck on Standby Mode. This particular CC has scared me about 3 times already, making me think it had bought the farm, but messing around with the settings, brings it back.
I have messed up the voltage reading and the it does not accept any change always revert back to zero .can you tell me the email of the i panda team ? . I could not find it on the app
Reply
#36
(08-23-2019, 11:17 AM)kanchana Wrote:
(07-04-2019, 08:44 PM)DomingoRP Wrote: When I was messing round with it, Same thing happened to me. Disconnecting all of the cables, wait 5 minutes and then connect everything back. Another thing is that, select the voltage manually (12/24/36/48V) and make sure the LOAD is turned ON. If it is off, chances are it will be stuck on Standby Mode. This particular CC has scared me about 3 times already, making me think it had bought the farm, but messing around with the settings, brings it back.
I have messed up the voltage reading and the it does not accept any change always revert back to zero .can you tell me the email of the i panda team ? . I could not find it on the app
See post #30 in this thread

Cheers
I love my batteries, they give me power...
Reply
#37
I used the ipanda app you posted I did not fix my voltage setting it only works for the current setting. Any one know the contact details for them ?
Reply
#38
(08-23-2019, 05:48 PM)kanchana Wrote: I used the ipanda app you posted I did not fix my voltage setting it only works for the current setting. Any one know the contact details for them ?
I used this email listed under the mobile app:
mygreenservice  at hotmail.com
I love my batteries, they give me power...
Reply
#39
(08-23-2019, 05:48 PM)kanchana Wrote: I used the ipanda app you posted I did not fix my voltage setting it only works for the current setting. Any one know the contact details for them ?

Hi,

To change the battery voltage ratio back to the 1644 default use the sequence:

AA010002030403006C06D7

instead of the AA010002030407007E04C3 sequence in step 5 of the document in the link wycito posted.
Reply
#40
(08-24-2019, 02:50 PM)rcuetara Wrote:
(08-23-2019, 05:48 PM)kanchana Wrote: I used the ipanda app you posted I did not fix my voltage setting it only works for the current setting. Any one know the contact details for them ?

Hi,

To change the battery voltage ratio back to the 1644 default use the sequence:

AA010002030403006C06D7

instead of the AA010002030407007E04C3 sequence in step 5 of the document in the link wycito posted.

Thanks it worked. But now I am at the very beginning. instead of battery voltage of 56.2volats  esmart 3 shows 62.8 volts .  tried  your programme it exits giving an error ?. Serial number reading seems to be wrong my actual number is 2018031428616-3 . Any advice how to change the voltage reading with out messing it up again ?
Reply


Who read this thread?
80 User(s) read this thread:
Lookin4PoWeR (09-04-2019, 05:08 PM), ibikunle (10-29-2018, 11:58 PM), Generic (06-23-2019, 02:04 PM), Solardad (09-05-2019, 03:14 AM), stevelectric (11-08-2018, 07:53 AM), PaulDane (02-22-2019, 11:24 PM), cmmurphyj (11-08-2018, 02:23 PM), ajw22 (09-14-2019, 10:05 PM), DomingoRP (07-20-2019, 04:57 PM), iscience (05-02-2019, 05:48 AM), cahngalasz (11-09-2018, 02:03 AM), olde guido (12-29-2018, 04:04 PM), lifepo4_powerwall (11-03-2018, 06:36 PM), Beholder (07-20-2019, 08:49 PM), Tinker123 (09-01-2019, 12:23 PM), cowpen (11-06-2018, 06:00 PM), howardrya (11-06-2018, 01:33 PM), Wolf (09-04-2019, 11:11 AM), Bastler_Ro (11-08-2018, 08:15 AM), kevinjaye (06-23-2019, 02:59 PM), OffGridInTheCity (06-22-2019, 08:48 PM), TroyD (06-24-2019, 07:07 AM), Jacob89 (05-16-2019, 09:57 AM), Lotus260 (05-16-2019, 10:06 AM), billvon (06-23-2019, 02:28 AM), jimbriam (07-31-2019, 09:40 PM), Saiya (08-14-2019, 04:59 PM), berthfield (08-24-2019, 08:32 AM), rcuetara (09-14-2019, 04:32 PM), romcek (05-19-2019, 11:04 AM), rochv (06-01-2019, 09:59 PM), ma3006he (07-05-2019, 05:01 PM), TheBiz (06-28-2019, 01:10 PM), winny (09-12-2019, 10:50 AM), 100kwh-hunter (06-03-2019, 04:48 PM), energy_man (06-22-2019, 02:27 PM), boffin (07-24-2019, 12:04 PM), Doin it (08-24-2019, 03:16 PM), juanjo57 (06-04-2019, 08:58 AM), photon4 (10-25-2018, 03:14 AM), chuckp (09-04-2019, 08:27 PM), Mazlem (07-21-2019, 07:39 PM), Geek (09-06-2019, 03:25 AM), mr_hypno (10-19-2018, 01:41 PM), ChrisD5710 (10-19-2018, 07:37 AM), wycito (09-06-2019, 03:34 PM), not2bme (08-16-2019, 07:25 PM), CarelHassink (06-03-2019, 12:32 PM), Charly144 (09-07-2019, 02:50 PM), KtB (06-23-2019, 03:54 AM), Stefaan De Ridder (06-04-2019, 05:47 AM), daromer (08-16-2019, 06:50 PM), Sean (08-15-2019, 01:41 PM), Korishan (08-23-2019, 06:37 PM), PAF (06-03-2019, 01:23 PM), jdeadman (09-04-2019, 05:54 PM), wim (08-19-2019, 05:57 PM), watts-on (06-27-2019, 01:04 PM), jesusangel (10-20-2018, 07:50 AM), cnous3 (07-20-2019, 09:01 PM), djuro (10-22-2018, 02:38 PM), avm131 (08-24-2019, 05:23 PM), philsocal (08-22-2019, 09:51 PM), Bubba (07-04-2019, 08:48 PM), Cherry67 (06-23-2019, 12:21 PM), Walde (09-04-2019, 11:39 AM), Riplash (09-04-2019, 05:08 PM), 100fuegos (08-25-2019, 08:49 PM), Katarn_89 (05-30-2019, 03:58 AM), oldserg (06-13-2019, 01:02 PM), TimV (12-23-2018, 09:30 AM), HughF (09-04-2019, 08:55 AM), gpn (07-18-2019, 10:26 PM), Chablis_m (07-04-2019, 09:02 PM), kanchana (09-04-2019, 07:52 AM), rogales141 (07-06-2019, 01:43 PM), jonyjoe505 (10-20-2018, 04:35 PM), Redpacket (10-19-2018, 10:25 AM), Oliman (07-18-2019, 09:53 PM), hbpowerwall (07-23-2019, 09:42 PM)

Forum Jump:


Users browsing this thread: 2 Guest(s)