German version
Products
News
Demo software
Applications
Literature
Links
Events
Updates
About us
Imprint
Contact
Home

visit us


16.2.2011
Munich
The battery book

Further information

>> Products >> BaSyTest software >> Test plan editor

BaSyTest Software

The test plan editor

The test plan editor is a simple to use tool to define and edit test regimes. A test regime is describe by a table. Each row of the table defines one step of t he test plan. The following figure shows an example of a test plan.


The editor has the following features:

  • Unlimited number of steps
  • Unlimited number of nested loops
  • Jumping targets are defined by labels
  • The use of subroutines is possible
  • Complete syntax checking
  • Free definable registration format
  • Editing is supported by wizards
  • Export of test plans to ASCII, HTML, XLS und DOC

The command describes what happens within a step. A Command can be a standard command (i.e. Charge, Discharge ..) or can also be a subroutine.

command

Parameter

Description

Charge

I, U, P

Charge with the parameters of the parameter field

Discharge

I, U, P

Discharge with the parameters of the parameter field

Pause

 ---

Open circuit, OCV relays is open, current =0

Ramp-i

I1: Start value
Slope: slope
I2: limitation

Current ramp with limitation

Ramp-u

U1: Startwert
Slope: Slope
U2: Begrenzung

Voltage ramp with limitation

Set

Ah-Set, W-Set, t-Set,
Ah-Ch-Set, Ah-Dis-Set,
Wh-Ch-Set, Wh-Dis-Set

Setting of counters and timers

Cycle-Start

-----

Begin of loop

Cycle-End

Anzahl, Count

End of loop

@..........

different

Subroutine

Extern*

-----

Connect battery with external load/charger

* The Extern command only works in combination with the option „external load/charger“. (See hardware documentation)

In near future other commands will be added.

The registration format

The registration format describes what data will be stored. The registration data has the following meaning:

Value

Description

DataSet *

Number of dataset

Time[h] *

Time in hours since start of test

DateTime

True date and time

t-Set[h]

Settable timer

Line*

Line number of test plan

State*

State information
1: normal, 2: Last data of step

U[V]*

Voltage

I[A]*

Current

AH[Ah]

Ah (charge + discharge) since start of test

Wh[Wh]

Wh (charge + discharge) since start of test

Ah-Charge

Ah (charge) since start of test

Ah-Discharge

Ah (discharge) since start of test

Wh-Charge

Wh (charge) since start of test

Wh-Discharge

Wh (discharge) since start of test

Ah-Step

Ah of the step

Wh-Step

Wh of the step

Ah-Set

Settable Ah counter (charge + discharge)

Wh-Set

Settable Wh counter (charge + discharge)

Ah-Charge-Set

Settable Ah counter (charge)

Ah-Discharge-Set

Settable Ah counter (discharge)

Wh-Charge-Set

Settable Wh counter (charge)

Wh-Discharge-Set

Settable Wh counter (discharge)

Ah-Cyc-Charge

Ah charged within the actual loop (sum of all cycles)

Ah-Cyc-Discharge

Ah discharged within the actual loop (sum of all cycles)

Wh-Cyc-Charge

Wh charged within the actual loop (sum of all cycles)

Wh-Cyc-Discharge

Wh charged within the actual loop (sum of all cycles)

Ah-Cyc-Charge-0

Ah charged within the actual loop (only actual cycle)

Ah-Cyc-Discharge-0

Ah discharged within the actual loop (only actual cycle)

Wh-Cyc-Charge-0

Wh charged within the actual loop (only actual cycle)

Wh-Cyc-Discharge-0

Wh discharged within the actual loop (only actual cycle)

P[W]

Power

Cyc-Count

Cycle counter

R_dc, R_dc

Internal resistance

Level

Level in case of nested subroutines

Aux1**

Auxiliary Channel 1

Aux2**

Auxiliary Channel 2

Aux3**

Auxiliary Channel 3

Aux4**

Auxiliary Channel 4

*: This data is always stored
**: The names of Aux1 - Aux4 can be changed by the basytec.ini file

The use of subroutines

Subroutines are helpful to carry out tasks that are needed more than one time. On the one hand side, subroutines increase the clearness of test programs and on the other hand side testetd subroutines increase the reliability. It is possible to pass over variables to a subroutine. Nested subroutines are also allowed.

Subroutine names do always start with @. The following figure shows an example:


It is possible to open subroutines. Then all steps of the opened subroutine are displayed within the main test program.

Next: Starting of tests                          Back to the overview