if not, what is the native output of the interface on the jkbms?
that sounds promising. I purchashed this https://www.amazon.ca/gp/product/B09C89S4PB/ref=ppx_yo_dt_b_asin_title_o06_s00?ie=UTF8&psc=1 . Do you happen to know which wire is tx and rx? I am pretty certain what red and black doThe output on the RS485 port on the BMS is TTL (RS232) - I know, confusing. You should be able to talk to it using a regular TTL/USB converter. The pin-out is in the description of my Gitrhub repo here: https://github.com/PurpleAlien/jk-bms_grafana
Once you have that hooked up, you can use the driver mentioned in this topic to have VenusOS interact with it.
that sounds promising. I purchashed this https://www.amazon.ca/gp/product/B09C89S4PB/ref=ppx_yo_dt_b_asin_title_o06_s00?ie=UTF8&psc=1 . Do you happen to know which wire is tx and rx? I am pretty certain what red and black do
On your GX device you can select which device will be your Battery Monitor. By default it will be your BMS using this driver, but you can select another.how will I determine which one shows the battery in the Vrm and remote
There must have been a error reading the BMS. Look at the log files to see what happened. If it happens again log an issue with the problem detail, driver version and include the part of the log file that show the problem.This occurred last night, any ideas why? 12V DC system with JBD BMS
The green meter is sitting here on my desk. I still have so solve a few VenusOS 2.80+ issues, and then I can continue with the ECS and also SMBS0 driver support.Any news about supporting the ECS LiPro BMS
Thanks for reporting. I will have a lookLowest Cell Voltage shows 0.780V and seems to be a static value
An Idea would be to donate on Github Louis for his fabuleus effortOK, small issue I am having now. I have all sorts of data but NO consumed aH even tho bluetooth app is tracking it. All other data seems good.
Any ideas?
These are really good news. Looking forward to this.The green meter is sitting here on my desk. I still have so solve a few VenusOS 2.80+ issues, and then I can continue with the ECS and also SMBS0 driver support.
The way things are labled can be confusing. UART is actually a group name. RS232, RS485 and TTL are all types of UARTs, but how these are sometimes marketed the UART is refering to TTL. If your JBD only has the port where Bluetooth is plugged in that is the TTL port.I find the whole UART/RS485/TTL thing very confusing
If you do not have the RS485 option, then you need to disconnect the bluetooth module to use that UART for the driver connection (mine has been running like that for 2 years - you only need the bluetooth for the setup initially). If you have the RS485 option then the driver can connect to that port and you can use the bluetooth on the UART port at the same time. It'c conveniant but not required.version with or without RS485
①:CANBUS interface (At present, only jk-B2A24S20P can customize the CANBUS function)
②:RS485 interface(At present, all JK BMS are configured with RS485 function by default)
③:LCD interface(Please check whether BMS has LCD interface before purchasing. If there is no interface, LCD cannot be used)
④:Heat Function interface(At present, the heating function customized by customers can be accepted, MOQ50pcs)
⑤:Temperature sensor
View attachment 80495