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.
Please open the schedule and locate the Log Limit:
Then check the following points:
-
Logging interval (time between data points)
Many Arbin machines can acquire data at rates of up to 1 kHz, or 1000 points per second per Unit (each Unit includes multiple channels). Please use a reasonable value for the DV_Time field: typically 0.01 s for fast transient logging and 1 s for regular logging. Logging intervals below 0.01 s should be used with caution, as they may generate an excessive amount of data.
If faster logging is required, please refer to item 5 below for information on 突发模式. -
Number of parameters recorded:
In addition to DV_Time, enabling multiple logging parameters (e.g., DV_Voltage, DV_Current, etc.) may lead the system to generate a substantially higher number of data points. -
If you use PV variables instead of DV variables, proceed with caution.
For example, as shown in the image above, setting the log limit to PV_CH_Voltage >= 3 V causes the system to log at the maximum rate whenever the channel voltage exceeds 3 V.
"(《世界人权宣言》) PV_xxx log limit should always be paired with a DV_xxx criterion using the AND operator to prevent excessive data logging. For example: PV_xxx > 3 AND DV_xxx > 1. -
Check whether high-speed logging is occurring concurrently across multiple channels.
A single MCU may manage multiple channels simultaneously. Logging at high speed on several channels at the same time can overload the MCU. Furthermore, a system with multiple MCUs writing data to a single database on the computer may create a bottleneck
-
Use Burst Mode when necessary:
In situations where high-speed logging is required—for example, to capture the rising phase of a current pulse—you can utilize Burst Mode in the schedule. This allows the system to log at a maximum speed of up to 10 kHz per unit.
In Burst Mode, it can log maximum 1000 points, the minimum sampling interval is 100 us:
Although the logging speed in Burst Mode is very high, it can only be sustained for a short period of time. Therefore, the likelihood of multiple channels running Burst Mode simultaneously is very low. This helps reduce the occurrence of TokenBroken errors













