Replies: 1 comment 12 replies
-
|
Hey, you are completely right, the "MOS lock in" means that either or both the charging and discharging ports have been disabled. This seems weird, when no other error is beeing thrown, as that protection feature should only activate when an over- or undervoltage is detected. Are your charge and discharge button on the overview on (green)? |
Beta Was this translation helpful? Give feedback.
12 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I have been experiencing some issues using your app (which looks amazing, BTW) in conjunction with my installed smart bluetooth BMS, which I would really appreciate some help on. I am simply testing my newly built 13S5P battery pack with the BMS installed, with no loading for any discharge testing. So right now, just interested in charging and balancing functions.
The app connects to the device with no issues and is able to read/write configuration data from/to it. (I've updated the start balance voltage to 3800mv to test balancing without fully charging.) Everything looks good but an error (MOS lock in) is highlighted (turns from green to red) when I access the "Protection" status screen. I'm thinking this may relate to the MOSFET circuitry being switch off, for some reason, which would likely cause the charging and/or discharge not to function. Please can you clarify what this relates to, what would likely have caused it, and what I should do to reset it. (I've tried disconnecting/re-connecting the BMS balance wire loom to try to reset the BMS to eliminate the error without success.)
The app has separate buttons on the Overview screen to invoke "Charging" and "Discharging" functions. Is this to support BMS boards that have discrete outputs for charging and discharging? On my BMS, both charge and discharge use the same (C-) output port on the PCB. When I try to invoke the "Charging" function, the BMS disconnects the C- output and charging is disabled. However, if I invoke the "Discharging" function (with no load attached) the battery looks to be charging ok. Even though the "MOS lock in" error is still evident. Is this expected behaviour? Should I simply ignore the "Charging" option in the GUI? Or am I missing something?
Thanks for any help or advice you're able to offer.
Regards, Ian
Beta Was this translation helpful? Give feedback.
All reactions