adiculiniute
New Member
- Joined
- Nov 6, 2021
- Messages
- 19
Question (pure curiosity) How or where did you find the string: "test='7EA1010000BE1855AA55' ?
That is the same app (MYApp) I was working with. I have been looking on the wireshark from my usb communcation, it is similar to Bluetooth, but manyb more cells are populated with a reasonable values(15 of 16). The cellvoltage are on other places than the standard protocol. But I cannot find eg total voltage .Ok. I have response from the seller. They don't have the protocol, but they send me a new (updated) link for the android app. Right now there are (or at least I have) 3 versions of the app - The best, full working version is "MY-APP-1116.apk". The rest of the apps "mybms_v1.2.4_20210803.apk" and "mybms_v1.3.25_20210926(2).apk" are not fully functional, for example I don't have the MOS, balance and cell temperatures displayed.
I was wondering if you can, install the MYApp1116, and try with this app to find that string, because this is may be more accurate, and has all the data.
Or if you dont have the time, tell me what software (links) you used to find that string.
Here is the link that the seller gaved me:
http://mysharegadget.com/947324863
What a unluck. What happens if you disconnect inverter? The voltage seems reasonable for about 100%. Why was it 15% before?. What is connected to give the high current of16A?Well, I guess my BMS is broken, all of the suden. Today I wired the battery bank to the inverter and I've installed the BMS too. After power on, it says DisMosError and it beeps continuosly. Attached you have a picture to see the error. Besides the Dismos error, the SOC is at 100% from 15% Why? It is broken already?
Hello! It's been quite a long time since I visit the forum, and this topic in particular.What a unluck. What happens if you disconnect inverter? The voltage seems reasonable for about 100%. Why was it 15% before?. What is connected to give the high current of16A?
Nice to see you again. I was busy installing the batteries in our Melex 252 a golfchart. It runs super on the batteries (48V, 130Ah). I have prepared a RPI Zero W and will try connect it directly to the cable (with some protection circuits).Hello! It's been quite a long time since I visit the forum, and this topic in particular.
I want you to know what it happened to my BMS. Well, I completely understand now, why it has been damaged, and lets say it's my fault.
So, somewhere in the docs, manuals that I received from the seller, I've read that before connecting the bms to the system, I must close the mosfets in the app, which I did. Then I connect the bms to the system, and with a precharge resistor, I charge the inverter capacitors to avoid sparks when connecting the load. (at least that was my intention And then I connect the battery to the inverter and power on the system.
Since the BMS had the mosfets in close position, the procedure of precharging the inverter capacitors has not occured (obviously, since there has been no current flow to the inverter). When I switched the power on, a large flow of current passed and at that moment the bms broke. So, I realized this latter on.
I spoked to the seller, and it confirmed that it is short circuit when connecting the load, and he suggested to me to send back the unit for a repair.
I did not wanted that, since the shipping costs and wait time is too long.
A friend of mine, says that if I open the BMS, I can inspect with a multimeter every mosfet (there are 36), and I can easily see what mosfet is broken.
So I open the BMS, I find the problematic mosfet, and I cut it's pins from the PCB. (I was too lazy to unsolder it nicely).
I want to tell you that the BMS is alive again (without 1 mosfet, It's power is reduced by about 15% - no bother).
Now, I am back from where I started it. It is very very frustrating not having the data from it to my dashboard.
Tell me that you have made some progress regarding the BT communication ?
i searched for the bms on the pi
[NEW] Device AA:BB:CC:A0:11:11 BMS-ANT16S-111
Paired it
[NEW] Device AA:BB:CC:A0:11:11 BMS-ANT16S-111
[bluetooth]# pair AA:BB:CC:A0:11:11
Attempting to pair with AA:BB:CC:A0:11:11
[CHG] Device AA:BB:CC:A0:11:11 Connected: yes
Request PIN code
[agent] Enter PIN code: 1234
[CHG] Device AA:BB:CC:A0:11:11 UUIDs: 00001101-0000-1000-8000-00805f9b34fb
[CHG] Device AA:BB:CC:A0:11:11 ServicesResolved: yes
[CHG] Device AA:BB:CC:A0:11:11 Paired: yes
Pairing successful
Trust
[bluetooth]# trust AA:BB:CC:A0:11:11
[CHG] Device AA:BB:CC:A0:11:11 Trusted: yes
then i edit your script "serverMacadress
serverMACAddress = 'AA:BB:CC:A0:11:11'
Traceback (most recent call last):
File "/bms/bmsnew.py", line 30, in <module>
Antw33 = ser.recv(140)
OSError: [Errno 9] Bad file descriptor
and i getimport socket
import time
import requests as req
from binascii import unhexlify
import struct
import sys
import serial
import bluetooth
from bluetooth import *
serverMACAddress = 'AA:BB:CC:A0:11:11'
port = 1
s = socket.socket(socket.AF_BLUETOOTH, socket.SOCK_STREAM, socket.BTPROTO_RFCOMM
s.connect((serverMACAddress,port))
test='DBDB00000000'
try:
s.send(test.decode('hex'))
except:
s.close()
time.sleep(1)
Antw33 = s.recv(140)
#SoC
data = (Antw33.encode('hex') [(74*2)75*2)])
print (data)
try:
resp = req.get(url+'SoC'+'?value='+str(int(data,16)))
except:
pass
Traceback (most recent call last):
File "/bms/bms1.py", line 22, in <module>
Antw33 = s.recv(140)
OSError: [Errno 9] Bad file descriptor
Lucky Guy. I am still struggeling, no problem to read but I need something to trigger the BMS to start to send.Hello again!
Good news! Thanks to "MrLaptop" - he gaved me his working code for our 2021 bms model. Initially it was for 8 cells, but I easly modified for 16 cells. All the data, except bms_power are OK. (Power is easy to calculate from amps*voltage, so it is not a problem.
The only problem is that, from time to time it has communication issues, so not every phyton script call returns values (It returns timeout errors). so the data is updated every 30sec to 2-3 minutes) If we somehow manage to overcome this issue, and have real time data from the BMS it will be perfect!!
It's already a good progress to have data, even if they are not in real time!
I post my modified code here: (and a printscreen from my arduino-blynk app with all the BMS data)
Thank you again MrLaptop!
Hi
just found the Solution - the Problem is python3 wich is included in the current raspbian ...
The problem is "test.decode('hex')"
This kind of decoding dont work on python3
im not a big programmer and dont find a Solution for this issue
So i changed to python2 and with python2 it works well ...