BMS1060BT appears to switch off randomly within a few minutes

Issue#1: Our brand new BMS1060BT may perhaps be a dud? We don't have the (currently beta) smartphone app, so I have been trying to get it working via USB.

However, the BMS frequently appears to shut down. The longest run has been just under 10 minutes, the shortest just a few seconds.

If I press the BMS pushbutton, activity begins on the LED's, and the RoboBMS software detects the BMS. I can read and write configurations. However, within minutes (sometimes seconds) the BMS LEDs all go out, and RoboBMS reports that the USB connection has been lost. Press the button again, and the cycle repeats.

The problem occurs even if there is no other connection to the BMS except the USB. The problem has been reproduced on two laptops (one of which is used often with RoboRun and a GBL2660 without problems), and with two USB cables.

I checked the RotoboteQ website for a firmware update, however the listed file (v1.1) is older than that actually shipped in the product (v1.2).

Issue#2: Possible firmware issue? From RoboBMS >> Setup >> Battery Pack Parameters >> Cell Chemistry Type, so far as I can tell, selections of LiPo or LeFePO4 are ignored by the BMS (even if confirmed by a configuration Save and Load). The individual cell voltage readout bars on the Run screen seem to get their limits from Custom Chemistry Settings, even if the Cell Chemistry Type is not set to Custom.

#3: Configuration questions: Fail-safe regen diode when using GBL2660 and BMS1060 together...
Q1: For an application where an Emergency Stop activation opens the BMS1060 Load output circuit while the motors might still be turning (i.e. generating), since the BMS1060 will not short GBL2660 Vmot to ground (per GBL2xxx datasheet Fig 2 contactor/cut-off), can the required over-voltage protection be achieved simply by changing the diode wiring per the orange lines on the attached diagram? Or would it be better to add a second diode across BMS Pack+ to Load+?

Even though the BMS Load switch is solid-state, there would still seem to be benefit to retaining the resistor that was suggested for mechanical contacts, which would reducing arcing when connecting the battery pack (provided the BMS Load output is deactivated), and for reducing the BMS & GBL inrush current spike.
Q2: Is there any reason not to do this?

Thanks and kind regards,

IUL_NZ
New Zealand

I have to consult with our BMS engineer about the behavior you are experiencing. He is busy helping a few other customers for the next couple days, but we should have some recommendations for you by Wednesday.

Great ... that'll be good thanks Gabriel :)

Okay, our BMS is requesting two things to go over what is happening. The controller resetting and the graphics showing the wrong charge is probably related to your utility. Please post a screenshot of your BMS utility with the run tab so that we can confirm and I will have you email This email address is being protected from spambots. You need JavaScript enabled to view it. so that we can troubleshoot from there.

In terms of the question about the resistor for the mechanical contactor, this is not necessary to include with the BMS. It actually is there to provide a precharge to the input filtering capacitors in our controllers, and it should be implemented automatically in our BMS.