Frequently Asked Questions

There are many reasons for schedule stopping, here is a checklist of possible reasons:

1. Load voltage outside of safety limit.
2. Load voltage lower than Unreasonable Behavior Check voltage.
3. EIS function enabled but EIS device not correctly connected.
4. UPS function is enabled but UPS does not correctly connect.

Most voltage control requires an Innenwiderstand (IR) value of your load. This value can be obtained by an Innenwiderstand control step. If you encounter bad voltage control, try adding an IR step before the voltage control step.

First Check sdu writing issue:

1. Check sdu’s clamp setting, does the clamp limit current output?
2. Check step’s Max Current setting, does Max Current smaller than setting current and indicates a smaller current range?

   Then Check the Hardware issue:

3. If the current is almost zero, check Switching Power Supply’s air switch, is it turned on?
4. If charger/discharge current is less than the setting value:
   1. Check power V++ and V--, possibly Power supply module issue.
   2. In the manual calibration window, check multiple current points, if the output current value is always a certain portion of the set current value, it indicates there are some small current loops broken.
   3. Check the current output in different current range, more information could be get with Circuit diagram.(fuse burned, Main current loop broken, etc)
5. If charge current only drops when the voltage is high(For LBT21), it indicates V++ is too low, check V++.

This error indicates too much data logged at a very short period of time. Check the schedule, make sure the data log setting is appropriate.

This error indicates an IR(Internal Resistance) step can not get a valid result value. Typically because the Setting Current(Amp) is too small or the Time Period is too short. Try to increase the setting current and Time period(>50ms).

This error indicates Aux channel lost communication with IV channels. It usually happens when the Batch/Mapping file was created/modified without downloading to cycler. It could be solved by downloading Batch/Mapping file:

This checking will only be performed when Channel Based Voltage Clamp option is not checked in ArbinAdvSys.cfg, which means all IV channels on the same IV channel board share a single voltage clamp/voltage check. Then Mitspro needs to ensure all schedules in the same IV board channels have the same Voltage Clamp setting, if not, this “Conflict Clamp V” will pop up.

Recently, almost no Arbin system has shared Voltage clamp, so most of the time, this unsafe is due to wrong Advanced feature setting. Simply check Channel Based Voltage Clamp in ArbinAdvSys.cfg  would solve the issue.